LiquiBase Core 1.5.1 + Grails and IntelliJ Plugins Released

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 Released

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

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.

Japanese Documentation Complete

I would like to thank Yasuo Honda for all his hard work on the Japanese translation of the LiquiBase documentation. He was also a great help in determining the best wiki tool to use to support translations.

If you are interested in assisting with translating the LiquiBase documentation, feel free to edit the site wiki directly, or contact the documentation mailing list for more information.

You can view the Japanese translation by starting at http://www.liquibase.org/ja/home or by clicking the “ja” box on any page.

Official Maven Support

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

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

LiquiBase 1.4.1: Core, IntelliJ, and Grails

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 Overview Videos

I have made two LiquiBase overview videos available to help explain what LiquiBase is and some of its capabilities. One is very brief (6 minutes) while the other is a more in-depth 30 minute video.

I’m planning on adding additional videos in the future. If you have a suggestion on a topic you would like covered, please let us know.

The videos are available in the new training section of the website.

LiquiBase at JavaOne? Cross your Fingers!

I submitted a JavaOne 2008 session into the call for papers. I went for a combination of LiquiBase usage and general database change management. Let’s hope I’m selected!

LiquiBase Core 1.4.0 Released

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

Initial LiquiBase IntelliJ IDEA Plug-in Released

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.

LiquiBase Grails Plugin

The newest version of LiquiBase now has a Grails plug-in available. To install the plug-in, simply run “grails install-plugin liquibase”.

Full documentation on the Grails plug-in is available at http://www.liquibase.org/manual/latest/grails.html