Embedded Files
Liquibase is designed to work in source-controlled environments. By keeping Liquibase changelog files and database scripts in a source code repository, users can leverage standard version control functions such as check-in, check-out, branching, and merging.
It is important to establish a repository structure that aligns with how each team implements and manages database changes. This consistency ensures that teams can effectively collaborate and maintain the integrity of their database migrations.
There are multiple ways to structure your existing SQL repository or create a new dedicated repository for database changes. In this implementation guide, we will review:
Organize changes by objects: Tracking every object and its history of changes is popular for new teams working with databases and using Liquibase starting day 1.
Organize changes by release: Tracking changes made during each release is popular for teams with database changes not tracked in a source code repository before adopting Liquibase.
In the following pages, we will go into more detail organizing changes by objects or releases and branching strategies.
What to do next
What to do next
Page updated
Report abuse