POSTED 04 Jun 2009 by Nathan Voxland
It is, obviously, a question near to my heart and I very much agree with the answer of “YES”. I also like that “use liquibase” has a few up votes and isn’t too far down the page…
It is great to see the concept getting some attention. I know that managing your database changes is just as vital as managing your code changes, yet the discussion, tool support, and interest is significantly higher for code version control than it is for database version control. There are endless articles and podcasts on SVN vs. Git, source control best practices, and mocking of people still using CVS and VSS, but basically no mention of Liquibase vs. ActiveMigrations, database changeset best practices, or mocking of people manually managing their database changes or using database diff tools.
I know Liquibase has saved my butt as many times as SVN has, and I want it to be able to help as many other developers as possible. The first step, however, is learning that there are tools out there that will help them.