Document Messages which may appear during migration

Talk to me (Tom) about this

Notes from talk with Tom:
Problems may occur when upgrading from HSQL to MySQL or PostgreSQL.

• If you have data in your database created by older versions of Crucible, you may have fields with too much data in them, as HSQL does not enforce this.
• Hence, when you upgrade you will get a log warning stating that data in a particular field is too long and has been truncated.
• There are two cases to consider for data truncation:
  1. Data is truncated for a db column which is a key (i.e. revision ID). If this is the case, the upgrade will fail. This would typically occur if customer used ClearCase which creates long revision names. To address this, customer will need to raise a support request.
  2. Data is truncated for a non-key field. Typically for a revision name. For example, if a review is created from a comment message, the revision name may be too long and will be truncated. The customer does not need to do anything to address this, although they may want to rename the field.

Error string for scenario 1:
"The value of column <table name.column name>, has a length of <length> which is greater than the maximum allowed length for this column of <max size of column>. As this column is part of a unique index, the migration cannot be completed."
Error string for scenario 2:
"Truncating value of column <table name.column name> from '<old value>' to '<value>' because its length of <length of old value> is greater than the maximum allowed length for this column of <max size of column>."

Pages to update:

• http://confluence.atlassian.com/display/CRUCIBLE/Migrating+to+an+External+Database