LiquiBase 1.9.0 Released
LiquiBase 1.9.0 has been released!
Major features include:
- <modifySql> support
- <includeAll> support
- Sybase Adaptive SQL Anywhere support
- Paths in <include> can be relative to changelog using the “relativeToChangeLog” attribute
- <stop> support
- runInTransaction attribute for changeSet
- Stronger validation in .xsd
- Better Derby support (drop column, rename column)
- Bug fixes
If you are using the standard LiquiBase library, upgrading is simply a matter of replacing the liquibase.jar file. If you are using Grails, Maven, or the IntelliJ plugin, an updated version should be available via standard plugin repository within in the next day.
NOTE: DUE TO A BUG IN THE “ADD NOT NULL CONSTRAINT” AND “DROP NOT NULL CONSTRAINT” CODE, YOU WILL GET CHECKSUM VALIDATION ERRORS FOR EXISTING CHANGESETS THAT USE THOSE TAGS.
To solve the problem, either:
- Add the <validCheckSum> tag to the failing changesets specifying the old MD5 sum (the one listed in the validation failed message)
- Or, run “UPDATE DATABASECHANGELOG SET MD5SUM=NULL”
To take advantage of newer change log features, change your XSD declaration to:
<databasechangelog xmlns=”http://www.liquibase.org/xml/ns/dbchangelog/1.9″
xsi=”http://www.w3.org/2001/XMLSchema-instance”
schemalocation=”http://www.liquibase.org/xml/ns/dbchangelog/1.9
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-1.9.xsd”>
Download LiquiBase 1.9 from:
http://www.liquibase.org/download
As usual, make sure you let us know if you have any questions, problems, or ideas. Also, thank you to everyone who submitted bug reports and patches over the last couple months.
Paul Szulc:
Very very cool!! Thx liqubase team. I will go right on to check if my bug is fixed in the new release.
8 January 2009, 1:21 amRegards
nvoxland:
We tried to hit most of the major bogs for this release. If your bug hasn’t been resolved, be sure to let us know.
8 January 2009, 9:29 amchet:
I have a question about changing the xsd declarations. Do i have to change it in all the old changelog files that will probably never be modified again? Or can i leave them with the old XSD and use the new XSD only in the new changelog files? What about the main.xml file that uses only the include element. Can its XSD be left alone or does it have to be updated? Is there a guide listing the besting practices for these kinds of upgrades?
Thanks.
8 January 2009, 11:47 amNathan Voxland:
You do only need to change the XSDs for changelog files that will be using new functionality. LiquiBase will continue to run just fine against any of the XSDs (or even no XSD).
We are working on a best practices page, this is definitely something good to add. Thanks for the question.
9 January 2009, 5:27 pmNikita:
Almost all of my bugs founded in 1.8.0 fixed in this release. Thanks!
10 January 2009, 8:48 am