[
http://opensource.atlassian.com/projects/roller/browse/ROL-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Johnson updated ROL-1538:
-------------------------------
Assignee: David Johnson (was: Roller Unassigned)
Fix Version/s: 4.0
3.1.1
> Issues with mysql upgrade scripts going from 1.3 to 2.0
> -------------------------------------------------------
>
> Key: ROL-1538
> URL:
> http://opensource.atlassian.com/projects/roller/browse/ROL-1538
> Project: Roller
> Issue Type: Bug
> Components: Database Access & Data Model
> Affects Versions: 2.0, 3.1
> Environment: mysql 4.1, tomcat 5.5
> Reporter: Eric L. Wittle
> Assignee: David Johnson
> Fix For: 3.1.1, 4.0
>
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/roller/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
