JBAS-2129 Delay 3.2 copy alert migration

They are not compliant with XUL.  Research pending.

They can be migrated later.

Signed-off-by: Bill Erickson <berickxx@gmail.com>

diff --git a/KCLS/sql/schema/deploy/2.12-3.2-db-upgrade-data.sql b/KCLS/sql/schema/deploy/2.12-3.2-db-upgrade-data.sql
index c0a7d3b..fad5728 100644 (file)
--- a/KCLS/sql/schema/deploy/2.12-3.2-db-upgrade-data.sql
+++ b/KCLS/sql/schema/deploy/2.12-3.2-db-upgrade-data.sql
@@ -62,6 +62,8 @@ UPDATE config.copy_alert_type
 SET active = TRUE
 WHERE id IN (4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17);
 
+/*
+-- KCLS JBAS-2129 disable copy alert updates for now.
 SELECT CLOCK_TIMESTAMP(), 'Updating copy alert messages';
 
 SELECT CLOCK_TIMESTAMP(), 'Copying copy alert messages to normal checkout copy alerts...';
@@ -81,6 +83,7 @@ AND   alert_message <> '';
 SELECT CLOCK_TIMESTAMP(), 'Clearing legacy copy alert field; this may take a while';
 UPDATE asset.copy SET alert_message = NULL
 WHERE alert_message IS NOT NULL;
+*/
 
 
 /*