[Roller-JIRA] Resolved: (ROL-1363) Migration Oracle database 3.0 to 3.1 partitialy failed

["David Johnson (JIRA)" <no...@atlassian.com>]

     [ http://opensource.atlassian.com/projects/roller/browse/ROL-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Johnson resolved ROL-1363.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 4.0

Fix ed in 3.1 branch (control.vm) and in 4.0 (macros.vm).

> Migration Oracle database 3.0 to 3.1 partitialy failed
> ------------------------------------------------------
>
>                 Key: ROL-1363
>                 URL: http://opensource.atlassian.com/projects/roller/browse/ROL-1363
>             Project: Roller
>          Issue Type: Bug
>          Components: Configuration & Settings
>    Affects Versions: 3.1
>         Environment: Oracle
>            Reporter: Boris
>            Assignee: Roller Unassigned
>             Fix For: 3.1.1, 4.0
>
>
> There is a bug in oracle db script: 300-to-310-migration.sql
> -- The rag_group_subscription table has been simplified and no longer needs a 
> -- primary key but we don't want to drop the field just yet because that would 
> -- make it impossible to abort a 3.1 upgrade and return to 3.0. 
> alter table rag_group_subscription drop id not null;
>     alter table rag_group_subscription drop id not null
>                                             *
> ERROR at line 1:
> ORA-00905: missing keyword
> alter table rag_group_subscription drop primary key;

-- 
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