In this tutorial, we will cover a few simple mechanisms Liquibase uses to track, version, and deploy changes to get an understanding of how Liquibase works.
Liquibase tracks which changeSets have or have not been deployed in a tracking table called a
DATABASECHANGELOG. If your database does not already contain a tracking table, Liquibase will create it for you.
Liquibase also prevents conflicts from different callers’ updates on a secondary table called
changelogs and tracking tables allow Liquibase to:
Liquibase also has advanced features such as contexts, labels, and preconditions to precisely control when and where a changeSet is deployed.
Note: To assist with projects where you are not starting with a blank database, Liquibase has a feature to generate a changelog to represent the current state of the database schema.
In this tutorial we covered: