Posted 09 Jan 2014 by Nathan Voxland
Liquibase 3.1.0 has been released. For most people 3.1 is a drop in replacement for 3.0.
If you use
<includeAll> with relative paths or are running against MaxDB, DB2 for iSeries, or InterSystems Cache make sure you read the upgrade guide.
Besides bugfixes, 3.1 adds the following major features:
One of the most requested features is the ability to use Liquibase when you do not have direct access to the database. We have always had updateSql support, but it still required a database connection to know what has been ran and what type of database to generate SQL for.
With the new “offline” support, you can now define a database connection URL like “offline:mysql” or “offline:oracle?version=11.1” when you run updateSql.
In offline mode, the change history is tracked in a local csv file which can be controlled with the “changeLogFile” URL parameter. For example: offline:mysql?changeLogFile:/home/db/changelog.csv
For more information, see the offline database documentation
With 3.1, you can now create extensions that manage changelog history tracking differently than the standard “DATABASECHANGELOG” table. For example, https://github.com/liquibase/liquibase-filechangelog allows you to manage your changelog history using a local file rather than a table in the database.
<foreignKeyConstraintExists>now supports checking based on table and column definition. Not just constraint name