For must Liquibase end users, Liquibase 3.1 is a drop-in replacement for any Liquibase 3.0 version.
If you are using
For developers of Liquibase extensions, there has been some Java API changes that may impact your code.
With certain builds in 3.0.x, using
With 3.1.0, this bug is fixed, but if you have changeLogs that have already ran, liquibase may attempt to re-execute them because the filepath column is part of the changeSet identifier and it now sees it as different.
You can resolve the problem in one of two ways:
Set a “logicalFilePath” in the included changeLogs equal to the full path as it was stored before
Manually update your DATABASECHANGELOG table to strip off the extra portion of the path. The SQL will vary by database, but an example for mysql would be:
update DATABASECHANGELOG set FILENAME=REPLACE(filename, 'c:\my\root\path', '')
If you are using Liquibase with Cache, MaxDB or DB2 for iSeries, support has been moved out of Liquibase core and into extensions.
To re-enable support for these databases, install the corresponding extension:
The liquibase.executor.Executor queryForList methods now return
List<Map<String, ?>> rather than just
There is a new
addReservedWords(words) method to implement. If extending AbstractJdbcDatabase, the default implementation should work for you.
The following methods were removed from liquibase.database.Database in favor of extensible service implementations:
|checkDatabaseChangeLogTable(updateExistingNullChecksums, databaseChangeLog, contexts)||liquibase.changelog.ChangeLogServiceFactory.getInstance().getChangeLogService(database).init()|
New methods were added to the LockService interface:
The class liquibase.lockservice.LockServiceImpl has been renamed to liquibase.lockservice.StandardLockService, although a deprecated placeholder with the old name was introduced for backwards compatibility.
New methods were added to the ChangeExecListener interface:
A new replaces() method was added to SnapshotGenerator. The default implementation in JdbcSnapshotGenerator is a no-op which should work for most uses.
CommandLineResourceAccessor now returns null if a file does not exist rather than throwing an IOException. This behavior now matches the other ResourceAccessors.
An IOException should only be thrown by a ResourceAccessor if the file exists but there is a problem reading it.