Bug 813165 - Upgrade Liquibase to version 2.0
Summary: Upgrade Liquibase to version 2.0
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Component-Persistence, Maintainability, Deployment
Version: 1.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 1.6-alpha-1
Assignee: Carlos Munoz
QA Contact: Ding-Yi Chen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-17 06:23 UTC by Carlos Munoz
Modified: 2015-04-01 07:39 UTC (History)
3 users (show)

Fixed In Version: 1.6.1-SNAPSHOT (20120606-0019)
Doc Type: Bug Fix
Doc Text:
Cause Liquibase is a tool used to track and to apply changes to the database schema during a Zanata version upgrade. In cases where the Zanata database user account does not have sufficient privileges to update the database schema, a database administrator can use Liquibase with sufficient privileges to update the schema. Consequence Version 1 of Liquibase had a bug that prevented some foreign key constraints from being created during a schema update. Change The version of Liquibase used to track and perform Zanata database schema changes has been updated to version 2. Result System administrators performing an upgrade of a Zanata installation should now use Liquibase 2 to apply database schema updates.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-22 00:58:05 UTC

Attachments (Terms of Use)

Description Carlos Munoz 2012-04-17 06:23:36 UTC 
Upgrade Liquibase to the latest 2.x stable release.
Comment 1 Joshua Wulf 2012-04-20 06:43:07 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause
    Liquibase is a tool used to track and to apply changes to the database schema during a Zanata version upgrade. In cases where the Zanata database user account does not have sufficient privileges to update the database schema, a database administrator can use Liquibase with sufficient privileges to update the schema.
Consequence
    Version 1 of Liquibase had a bug that prevented some foreign key constraints from being created during a schema update. 
Change
    The version of Liquibase used to track and perform Zanata database schema changes has been updated to version 2.
Result
    System administrators performing an upgrade of a Zanata installation should now use Liquibase 2 to apply database schema updates.
Comment 2 Ding-Yi Chen 2012-06-07 05:34:28 UTC 
Verified Zanata version 1.6.1-SNAPSHOT (20120606-0019)

Liquibase version is 2.0.3
Comment 3 Sean Flanigan 2015-04-01 07:39:02 UTC 
These are the changes we made for this upgrade:

https://github.com/zanata/zanata-server/commit/27cdcab3f4ec78dde1cb9bd4fbbd1fe35d517b29
https://github.com/zanata/zanata-server/commit/c90176a0988a4a6f3b56b4efbbc142b8be63eb00
Note You need to log in before you can comment on or make changes to this bug.