How to add Flyway to an existing project

After my talk about combining Flyway, Hibernate, and jOOQ at the JavaLand conference, one of the participants asked me how to add Flyway to an existing application that’s already deployed in production. This is a common question because database migrations get often ignored for new projects. And that’s understandable. You don’t need it for the first installation, and there are many more urgent tasks you need to work on.

But ignoring your database migration, in the beginning, creates new problems later on. For your first update, you not only need to add Flyway to your project, but you also need to define an update process that works with your existing database and can set up a new one from scratch. Luckily, Flyway provides a simple solution for this:
You start by generating a DDL script of your existing database. This will be the first migration script for all new installations.
After that, you need to baseline your existing database so that Flyway knows that it doesn’t have to execute the 1st migration script.

After that, there is no difference between your project and one that used Flyway from the beginning. You can define the next migration steps as SQL scripts or Java classes, and Flyway will execute them automatically to migrate an existing database or create a new one.



Like my channel? Subscribe!
➜ http://bit.ly/2cUsid8

Read the accompanying post: https://thorben-janssen.com/flyway-migration-existing-database/

Want to connect with me?
Blog: https://thorben-janssen.com/
Twitter: https://twitter.com/thjanssen123
Facebook: https://www.facebook.com/thorbenjanssenofficial
Linkedin: https://www.linkedin.com/in/thorbenjanssen/