V2 /
LiquibaseFixesOccasionally Liquibase needs to be 'tweaked' due to back-porting of changes or removing old unused tools. A good reference point for this is available here: http://www.liquibase.org/manual/command_line Environment setupIn order to apply Liquibase operations to the database, make a working directory that has the following files in it. These are part of the CONGO distribution, and should be easy to locate: dbs@nimitz:~/liquibase$ ls -l total 1288 -rw-r--r-- 1 dbs dbs 31421 2011-05-30 11:32 install.changelog.xml -rw-r--r-- 1 dbs dbs 567247 2011-05-30 11:09 liquibase-core-1.8.1.jar -rw-r--r-- 1 dbs dbs 703265 2011-05-30 11:09 mysql-connector-java-5.1.6.jar Generic command structure:The format of the command line is the same for all operations, just use the different commands to make changes to the db: java -jar liquibase-core-1.8.1.jar --driver=com.mysql.jdbc.Driver --changeLogFile=install.changelog.xml --url="jdbc:mysql://boomer/databasename" --username=username --password=password --classpath=.:./mysql-connector-java-5.1.6.jar changelogSync Sync : To reset the MD5 fingerprintsAfter making a manual change to the database or to the install.changelog.xml, you can force the database to have the 'correct' checksums (and stop Liquibase from trying to re-apply all the changes) Use the command 'changelogSync' with the above Java command to force a correct MD5? fingerprint on the database. |