[Rt-commit] rt branch, 4.4/new-cf-columns-on-upgrade, created. rt-4.4.2-40-g6261f39

[Jim Brandt]

The branch, 4.4/new-cf-columns-on-upgrade has been created
        at  6261f39d4a776d7bd545ce94410af6fb66826346 (commit)

- Log -----------------------------------------------------------------
commit 6261f39d4a776d7bd545ce94410af6fb66826346
Author: Jim Brandt <jbrandt at bestpractical.com>
Date:   Fri Sep 22 11:31:43 2017 -0400

    Add docs regarding UniqueValues missing column warning
    
    An upgrade step in 4.3.6 creates a new custom field for
    CFs that have a category but no CF defined for the BasedOn
    field. Creating the new CF before the new CF columns are
    added in the 4.4.2 upgrade fails. Add docs with a workaround
    since this should impact relatively few users.

diff --git a/docs/UPGRADING-4.4 b/docs/UPGRADING-4.4
index 3d8c3ba..a9cb65f 100644
--- a/docs/UPGRADING-4.4
+++ b/docs/UPGRADING-4.4
@@ -593,6 +593,26 @@ of your database before making updates.
 
 =back
 
+* Unknown column 'UniqueValues' warnings
+
+If you have custom fields that use the "Category" feature, you may see warnings
+like this during your upgrade:
+
+    [warning]: DBD::mysql::st execute failed: Unknown column 'UniqueValues' in 'field list'
+
+RT 4.4.2 adds some new columns to CustomFields, but an earlier upgrade step tries
+to add a custom field before these new columns have been added. You can create the columns
+before running the upgrade with the following:
+
+    sbin/rt-setup-database --action schema --datadir etc/upgrade/4.4.2
+
+The upgrade script will still attempt to create the columns again at the end when
+running the 4.4.2 upgrade, producing messages like:
+
+    DBD::mysql::st execute failed: Duplicate column name 'UniqueValues'
+
+This just means the columns are already there and no other steps are required.
+
 =back
 
 =cut

-----------------------------------------------------------------------