[ROL-1538] Issues with mysql upgrade scripts going from 1.3 to 2.0

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0, 3.1
• Fix Version/s: 3.1.1, 4.0
• Component/s: Data Model & JPA Backend
• Environment: mysql 4.1, tomcat 5.5
• Browser Version: N/A
• Database: mysql 4.1
• JDK Version: N/A
• O/S Version: RHEL4
• Assignee: David Johnson
• Reporter: Eric L. Wittle
• Created: 20/Aug/07 11:17
• Updated: 05/Jan/13 20:47
• Resolved: 08/Sep/07 16:00

Description

I had to modify the 130-to-200-migration.sql script in a few ways to avoid errors in later migration scripts and/or get my roller install to work when I was done. The following are the statements I added:

– ELW 8/16/07
alter table website add column isenabled tinyint(1) default 1;
update website set isenabled=1;
alter table website modify isenabled tinyint(1) default 1 not null;

The following are the statements I commented out because they threw errors on my database:

– ELW 8/16/07 alter table webpage drop index webpage_name_index;
– ELW 8/16/07 alter table webpage drop index webpage_link_index;
– ELW 8/16/07 alter table website drop index website_isenabled_index;

Not sure how many 1.X roller installs are left out there, so this may not be worth fixing, but probably is worth having around in case anyone else runs into it.

-Eric