Learn how to make database changes, manage various code versions and update different environments with Liquibase.

Do you want to stop frustration caused by manual database updates? Do you know that there is a free tool to help you out? If your answer is YES, it means that you might benefit from this course.

I start from the very beginning of using Liquibase. You should have some database and SQL knowledge. Basics of Java will increase your final satisfaction as I will also show you Liquibase integration with Spring Boot. I believe in practice so there will be mostly coding with some necessary theory. You will have many chances to try using Liquibase yourself because I included some exercises for you as well.

Get ready for an exiting journey to through Liquibase functionalities.

Go to the course

 

liquibaseCoursePromo

 

data type mapping smallDesigning a database, you have to choose data types for columns. It is not neutral which one is used. When you use Liquibase, you use an additional abstraction layer as it has its own data types. They are mapped to data types proper to a specific database engine later during scripts execution process. Choosing a data type, you should keep in mind the final data type on your database engine.

How to fail Liquibase changeset when prerequisites are missing

checklistIndex creation should not start when there is not enough disk space. An old table should not be dropped until it is completely empty. A database upgrade may happen only if a DBA has changed a default value of some setting. Many database upgrades have some prerequisites. If they are not met, the whole change should not even start. You may write a checklist during development and follow it on the upgrade but there is a better way - preconditions in Liquibase.

Environments in Liquibase changesets

envUsually, database changes go through a pipeline of environments. For example, they are developed at developers' laptops, checked into a repository, deployed to the development environment, pushed to the test environment and finally propagated to the production. Ideally, the changes should be applied to all these environments in the same way but in real life there are some exceptions.

Database compare by Liquibase >Do you have a way to compare two databases to check whether they are the same or they differ? And if they differ, would you like to know what is the difference? What would you say if I told you that Liquibase can do it and even generate an update script to make them the same? Oh, yes, it can. I am going to show you how to use it.

diffDo you have a way to compare two databases to check whether they are the same or they differ? And if they differ, would you like to know what is the difference? What would you say if I told you that Liquibase can do it and even generate an update script to make them the same? Oh, yes, it can. I am going to show you how to use it.