Upgrade path from 2.0.x -> 3.0.x

I’ve noticed that 

Attribute : referencesUniqueColumn in attribute group addForeignKeyConstraintAttrib has gone in 3.0.x and also the XSD in 3.0.x in following link

http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.0.xsd still has this attribute.

I’ve seen in the documentation that upgrade from 2.0.x and 3.0.x is like a drop in replacement which is NOT TRUE.

I’ve experienced following configuration breaks when I upgrade to 3.0.x

        <addForeignKeyConstraint baseColumnNames=“othertable1_id” baseTableName=“maintable”

                                 constraintName=“fk1” deferrable=“false” initiallyDeferred=“false”

                                 onDelete=“NO ACTION” onUpdate=“NO ACTION” referencedColumnNames=“id”

                                 referencedTableName=“othertable1” referencesUniqueColumn=“false” />


I think we should improve the documentation and/or re-check if there is anything we should concern when upgrade from 2.0.x to 3.0.x.

It wasn’t really being used in 2.0 so it was taken out of 3.0, but I put it back into 3.0.2 to better support backwards compatibility. It is a no-op as it more or less was in 2.0, I’ll work on updating the docs.


I think that was the essence of issue https://liquibase.jira.com/browse/CORE-1344.  If you agree you might want to mark it as implemented.

Just tried it and it handled my pillow test much better than 3.0.1.

Great !! thank you, and I’m looking forward for 3.0.2 release. :wink:

Yes, 1344 should have been in there. I marked it as closed in 3.0.2.

BTW, 3.0.2 is out now just haven’t gotten to the official announcement yet.