This post originated from an RSS feed registered with Java Buzz by Marc Logemann. Original Post: Integrating LiquiBase 1.2 into our product Feed Title: Logemann Blog Feed URL: http://feeds.feedburner.com/LogemannBlog Feed Description: Marc Logemann's thoughts on java and other stuff Latest Java Buzz Posts Latest Java Buzz Posts by Marc Logemann Latest Posts From Logemann Blog

Now i finally found the time to play around with LiquiBase. I am following this project for quite some time. To be more detailed on this, i was on the way creating a database migration tooling as open source myself but just a few days before i wanted to start on it (and after my project got accepted on java.net) they launched their initial version and most of the things they thought out was also on my plan. So i decided to not re-invent the wheel here. Perhaps i can give some input here and there in the future, lets see.

So the last 2 hours i setup a test project and started by generating a changeset xml file of our current product database by using the changelogSyncSQL command of the command line migrator. After that i ve done some minimal migration with the Ant migrator and this looked also quite good. In our product we will use the ServletListener approach. The goal is that the customer gets a screen on first usage after the update, telling him that the database will be migrated now.

I ve not tested everything you can test but enough to be sure that this could work quite well with our product. So far i only stumbled upon some documentation errors and i am wondering why they re-invented an <include> tag when there is xinclude which should do the same out of the box from xml parser perspective. But there is one problem no tool in the world can solve: Developers tend to make db changes directly in the test database and then forget applying those changes to metadata files like the changeset file of LiquiBase. One of the developers is writing this blog entry right now…