LiquiBase

It is LiquiBase 1.0’s first birthday, but you get the gift: LiquiBase 1.7.0 is now available.

Major changes include:

• Added loadData change which allows importing of data from CSV files
• Added support for changelog parameters for more dynamic and flexible change logs
• Allow preconditions in changeSet tags to act as sanity checks during a database update
• Can export data with generateChangeLog
• Added markNextChangeSetRan command
• Added validCheckSum tag to changeSet
• Can use any refactoring tags or reference previous changeSets inside a rollback tag
• Allow custom preconditions
• RowMapper interface is now public
• Misc bug fixes

The core library can be downloaded from http://www.liquibase.org/download while the Maven, Grails, and IntelliJ plug-ins can be installed from their respective plug-in managers.

LiquiBase 1.6.1 has been released.

This is primarily a bug fix release, but also includes a release of the 1.6 version to the Maven (still propagating), Grails, and IntelliJ repositories.

Download LiquiBase 1.6.1 from: http://www.liquibase.org/download

The LiquiBase team is proud to announce the 1.6.0 LiquiBase Core release.

This release focuses primarily on Hibernate integration which allows you to use the diffChangeLog functionality available with the command line and Ant to automatically generate LiquiBase change sets based on new Hibernate mapping information.

This functionality is similar to what is offered with hbm2ddl, but with the added ability to control and modify the changes before they are applied. For more information, see http://www.liquibase.org/manual/hibernate

Additional functionality includes a new “tagDatabase” tag, a “primaryKeyName” attribute on the column tag, as well as many bug fixes.

NOTE: Due to a bug in the change set md5 checksum generation in pre-1.6 releases, existing md5sum information needs to be cleared out of the databasechagelog table before running 1.6 for the first time. This can be done by running “liquibase clearCheckSums” or by running “UPDATE DATABASECHANGELOG SET MD5SUM=NULL”

Upgrading is simply a matter of replacing the liquibase.jar file. To take advantage of newer change log features, change your XSD declaration to:

<databasechangelog xmlns=”http://www.liquibase.org/xml/ns/dbchangelog/1.6″
xsi=”http://www.w3.org/2001/XMLSchema-instance”
schemalocation=”http://www.liquibase.org/xml/ns/dbchangelog/1.6
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-1.6.xsd”>

LiquiBase 1.6 can be downloaded from http://www.liquibase.org/download and, as always, let us know if you have any questions or issues.

The Maven and Grails plug-ins will be updated over the next week.

LiquiBase 1.5.2 has been released.

Changes include:

• Fixed bug with runOnChange and MD5sum check
• Handles generating changelog for tables with composite primary keys
• Other minor bug fixes

The LiquiBase core library can be downloaded via http://www.liquibase.org/download.

The Maven, Grails, and IntelliJ plug-ins have been updated and can be downloaded via their respective plug-in manager.

LiquiBase Core 1.5.1 has been released along with the initial 1.5.x series Grails and IntelliJ plugins.

Changes to the core library are minor bug fixes including:

• Fixed failOnError logic
• Improved serial column detection in Postgres
• Rollback connections before close for DB2
• Other minor bug fixes

The LiquiBase core library can be downloaded, as usual, from http://www.liquibase.org/download. The Grails and IntelliJ plugins are installed via their respective plugin managers

The 1.5 Maven plugin should be released next week after further testing.

LiquiBase Core 1.5.0 is now available for download from http://www.liquibase.org/download

1.5.0 includes a major refactoring which should not affect most users except for the following items:

BREAKING CHANGES

---

• Servlet Migrator: The web.xml parameter names have changed. See http://www.liquibase.org/manual/servlet_listener for more information.
• If you used the “database.migrator.should.run”, it is must now be changed to “liquibase.should.run”
• If you have extended or embedded LiquiBase classes or calls directly in your code, changes will be necessary.

BACKWARDS-COMPATIBLE CHANGES

---

• Servlet Migrator: The classes to reference in web.xml have changed to liquibase.servlet.LiquibaseStatusServlet and liquibase.servlet.LiquibaseServletListener. The old classes are now simply subclasses of the new and are deprecated so they should work.
• Spring Migrator: The class to reference in your spring config has changed to liquibase.spring.SpringLiquibase. The old class still exists as a subclass of the new so existing configurations should continue to work.
• Command Line: The “migrate” command has been changed to “update”.
  “migrate” is now an alias for “update” so existing calls should continue to work

ENHANCEMENTS

---

IMPROVED SCHEMA SUPPORT
There is now a “defaultSchemaName” parameter available for setting default schema. This schema will be used for all ambiguous database objects as well as for storing the databasechangelog and databasechangeloglock tables.

IMPROVED ANT TASKS
Ant support has been greatly expanded and now covers most of the functionality available in the command line application. See http://www.liquibase.org/manual/ant for more information.

NEW COMMANDS

• changeLogSync
• updateCount
• updateCountSQL

NEW REFACTORINGS

• update change
• delete change

OTHER CHANGES

---

• Custom Database implementations can be specified with the databaseClassName parameter
• “replaceIfExists” attribute added to createView
• createTable can specify uniqueConstraintName
• Setting value/valueNumeric/valueBoolean/valueDate on addColumn will update all existing rows with the given value
• Database table comments saved to generated change log
• Changelog file comparisons are case-insensitive on windows
• Output warning of old schema version
• Added comments tag to generated SQL output
• Rollback commands can specify contexts
• XSDs are not pulled from network
• Handles Postgres datatypes better
• Bug fixes

Upgrading

---

Upgrading is simply a matter of replacing the liquibase.jar file. To take advantage of newer change log features, change your XSD declaration to:

<databasechangelog xmlns=”http://www.liquibase.org/xml/ns/dbchangelog/1.5″
xsi=”http://www.w3.org/2001/XMLSchema-instance”
schemalocation=”http://www.liquibase.org/xml/ns/dbchangelog/1.5
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-1.5.xsd”>

Depending on feedback received from this release, the 1.5.0.0 releases of the various plug-ins (Maven, Grails, IntelliJ, Eclipse) should be released over the next few days.

As usual, be sure to let us know if you have any questions or issues.

Thanks to Peter Murray, we now have working Maven support and good documentation.

See http://www.liquibase.org/manual/maven for more information.

LiquiBase Core 1.4.1 has been released. This is primarily a bug fix release.

Upgrading is simply a matter of replacing the liquibase.jar file.

Download LiquiBase Core 1.4.1 from:

http://www.liquibase.org/download.html

The IntelliJ plug-in has also been updated to support 1.4.1. It can be installed or updated through the IntelliJ plug-in manager.

The Grails plug-in has also been updated to support 1.4.1. It is installed through the standard grails plug-in infrastructure.

As usual, let me know of any issues or suggestions you have

LiquiBase 1.4.0 has been released. Major features include:

• IntelliJ Plug-in Support
• Added support for specifying schemas in change log
• MaxDB/SAPDB Support
• Refactored Code
• Can specify data types as java.sql.Types.*
• Support for composite foreign keys
• Improved Maven support
• Bug Fixes

Upgrading is simply a matter of replacing the liquibase.jar file. To take advantage of newer change log features, change your XSD declaration to:

<databasechangelog xmlns=”http://www.liquibase.org/xml/ns/dbchangelog/1.4″;
xsi=”http://www.w3.org/2001/XMLSchema-instance”;
schemalocation=”http://www.liquibase.org/xml/ns/dbchangelog/1.4
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-1.4.xsd”;>

Download LiquiBase 1.4 from:

http://www.liquibase.org/download.html

For you IntelliJ IDEA users out there, there is now a LiquiBase plugin available through the Intellij plug-in manager.

Like the Eclipse plug-in, the IntelliJ plugin allows you to refactor your database like you refactor code using a “Refactor” context menu on database objects. These changes are automatically saved to a change log file.

A “LiquiBase” context menu on the database explorer allows you to migrate your database, roll back changes, generate documentation, and more.

Additional refactoring and better documentation will be added in upcoming releases.

As usual, please let us know if you have any questions or suggestions.