2.6.0 upgrade script has index, column add in wrong order, related to SAK-16554

Description

The current conversion script reads

– Further Improve the Performance of the Email Archive and Message API. Note you have to run a bash conversion script on your old mail archive data for it to
– appear in the new mail archive. The script is in the source as mailarchive-runconversion.sh. Please see the SAK for more information on this script or SAK-16554 for
– updates to this script.

CREATE INDEX IE_MAILARC_SUBJECT ON MAILARCHIVE_MESSAGE
(
SUBJECT ASC
);
ALTER TABLE MAILARCHIVE_MESSAGE ADD COLUMN (
SUBJECT VARCHAR (255) NULL,
BODY LONGTEXT NULL
);

This fails when I apply it, because the column subject does not exist and therefore cannot be indexed.

I had to flip the order to

ALTER TABLE MAILARCHIVE_MESSAGE ADD COLUMN (
SUBJECT VARCHAR (255) NULL,
BODY LONGTEXT NULL
);
CREATE INDEX IE_MAILARC_SUBJECT ON MAILARCHIVE_MESSAGE
(
SUBJECT ASC
);

Activity

Matthew Jones August 20, 2009 at 1:43 PM

This was also confirmed by this email:
http://collab.sakaiproject.org/pipermail/sakai-dev/2009-July/002439.html

This is fixed in trunk and in 2.6.x.

Fixed

Details

Priority

Affects versions

Fix versions

Components

Assignee

Reporter

Environment

the lastest svn pull of sakai, sakai_2_6_0_mysql_conversion.sql, current as of revision 65133

Created August 11, 2009 at 9:25 AM
Updated December 14, 2021 at 3:58 PM
Resolved August 20, 2009 at 1:43 PM