I’ve been having challenges migrating to Liquibase for the following reason –
We have developers that make sql changes, then keep the sql changes in an SCM (subversion, SourceAnywhere/SourceSafe, etc). When they need to work on something, they check out the SQL object, make changes, run on the DEV database, then commit back.
Liquibase is a much better tracking tool, particularly for promotion-style changes (dev->test->production). However, I’m a little stuck on how to merge the two worlds together without doing a lot of duplicate copy-paste of SQL code.
Would it be feasible/good idea to have SCM-based changes as part of the tracking mechanism in Liquibase?
Or, alternatively, maybe a shell/tool to connect to different SCM’s and pull the sql scripts out to create an equivalent change script for Liquibase parsing out the actual sql from the scripts directly into the change (with reference to the actual SCM location just for future reference – maybe in the database log table as well?). To get even fancier, maybe even pull out the commit notes to become liquibase change notes…