Want to use Liquibase™ across your enterprise? Try our enterprise version
2018 Survey

Liquibase 3.2.1 Released

POSTED 18 Jul 2014 by Nathan Voxland

Liquibase 3.2.1 has been released. As usual, it can be downloaded from the Liquibase download page and is available in the Maven repository as org.liquibase/liquibase-core.

3.2.1 is purely a bugfix release. The only potential update issue could be a fix for incorrect checksums introduced in 3.2.0. If you used defaultValueNumeric, defaultValue or used createProcedure or sql tags you may have seen unexpectedly changed checksums with 3.2.0. With 3.2.1, those have been reverted back to the correct 3.1.x version. If you are updating from 3.1.x it will be a smoother update from 3.2.0. If you already updated to 3.2.1 and manually fixed your checksums in the databasechangelog table, they will need to be updated again.

Full change log:

  • CORE-1844 - bulkFetch of foreign keys on Oracle is very slow
  • CORE-1918 - Multiple comment blocks in changesets no longer works
  • CORE-1920 - SpringLiqubase includeAll is not including files
  • CORE-1922 - 3.2.0 Regression due to CORE-1721
  • CORE-1923 - Error raised: Unknown Reason when doing tagging via command line
  • CORE-1930 - Snapshot command returns no information on MSSQL
  • CORE-1933 - (3.0.8 -> 3.2.0) pom.xml: 2Mb of superfluous dependencies
  • CORE-1934 - file path in databasechangelog is absoulte since liquibase 3.2.0 when using includeAll inside a jar
  • CORE-1936 - NullPointerException while diffing database against hibernate.cfg.xml
  • CORE-1938 - defaultValueNumeric=”0” or defaultValue=”0” is translated to 0.0
  • CORE-1940 - Maximum Oracle Sequence fails to be parsed as a BigInteger
  • CORE-1944 - NullPointerException when tagging through Ant before applying changesets
  • CORE-1947 - Liquibase dependency to jetty-servlet/velocity should be <optional>true</optional>

  • CORE-1950 - Checksum validation failed after Liquibase upgrade (3.1.1 -> 3.2.0)
  • CORE-1957 - Using VARCHAR2 column type fails for Hsqldb running in oracle syntax mode
  • CORE-1960 - “Could not find implementation of liquibase.logging.Logger” starts appearing after migration from 3.1.1 to 3.2.0
  • CORE-1970 - NullPointerException on rollback with <sqlFile> tag
  • CORE-1746 - Support <sqlFile> parameters
  • CORE-1951 - Regression on 3.2.0 : –diffTypes=data generates Unknown Reason Exception

UPDATE: There is still a couple checksum issues updating from 3.1.1 to 3.2.1. I’ll get those fixed up in a 3.2.2 release today or tomorrow.


Missing, incomplete or wrong information? Please send a pull request