Bug 813165

Summary:	Upgrade Liquibase to version 2.0
Product:	[Retired] Zanata	Reporter:	Carlos Munoz <camunoz>
Component:	Component-Persistence, Maintainability, Deployment	Assignee:	Carlos Munoz <camunoz>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ding-Yi Chen <dchen>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.5	CC:	jwulf, sflaniga, zanata-bugs
Target Milestone:	---
Target Release:	1.6-alpha-1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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