[Building Sakai] Upgrading msgcntr to v2.7.5 conversion scripts

[Bryan Holladay]

It doesn't matter what it's named, so you can change it to any name you want.

-Bryan

On Tue, Sep 6, 2011 at 9:54 AM, George Pipkin <gpp8p at virginia.edu> wrote:
> Hi Bryan:
>
>   Unfortunately this script does not run properly on our version of mysql.
>  Here's
> what I get:
>
> mysql> CREATE UNIQUE INDEX PRIMARY USING BTREE ON MFR_UNREAD_STATUS_T(ID);
> ERROR 1064 (42000): You have an error in your SQL syntax; check the manual
> that corresponds to your MySQL server version for the right syntax to use
> near 'PRIMARY USING BTREE ON MFR_UNREAD_STATUS_T(ID)' at line 1
>
> Thinking that PRIMARY might be a reserved word, I quoted it but got this:
>
> mysql> CREATE UNIQUE INDEX `PRIMARY` USING BTREE ON MFR_UNREAD_STATUS_T(ID);
> ERROR 1280 (42000): Incorrect index name 'PRIMARY'
> mysql>
>
>
> Any ideas on how to get around this ?
>
>
>                        - George Pipkin
>                            U.Va.
>
>
> On 8/31/11 4:59 PM, Bryan Holladay wrote:
>>
>> CREATE INDEX MFR_UNREAD_STATUS_I2 USING BTREE
>>     ON MFR_UNREAD_STATUS_T(MESSAGE_C, USER_C, READ_C);
>>
>> CREATE INDEX MFR_UNREAD_STATUS_I1 USING BTREE
>>     ON MFR_UNREAD_STATUS_T(TOPIC_C, MESSAGE_C, USER_C, READ_C);
>>
>> CREATE UNIQUE INDEX PRIMARY USING BTREE
>>     ON MFR_UNREAD_STATUS_T(ID);
>>
>> ALTER TABLE MFR_UNREAD_STATUS_T
>>     ADD CONSTRAINT TOPIC_C
>>     UNIQUE (TOPIC_C, MESSAGE_C, USER_C);
>>
>> ALTER TABLE MFR_MESSAGE_T
>>     ADD CONSTRAINT FK80C1A316A2D0BE7B
>>     FOREIGN KEY(surrogateKey)
>>     REFERENCES MFR_TOPIC_T(ID);
>>
>> ALTER TABLE MFR_TOPIC_T
>>     ADD CONSTRAINT FK863DC0BE74C7E92B
>>     FOREIGN KEY(of_surrogateKey)
>>     REFERENCES MFR_OPEN_FORUM_T(ID);
>>
>> ALTER TABLE MFR_OPEN_FORUM_T
>>     ADD CONSTRAINT FKC17608478B5E2A2F
>>     FOREIGN KEY(surrogateKey)
>>     REFERENCES MFR_AREA_T(ID);
>>
>> ALTER TABLE MFR_AREA_T
>>     ADD CONSTRAINT MFR_AREA_CONTEXT_UUID_UNIQUE
>>     UNIQUE (CONTEXT_ID, TYPE_UUID);
>>
>>
>
>