You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@roller.apache.org by "Juergen Kellerer (JIRA)" <ji...@apache.org> on 2010/01/09 16:24:54 UTC

[jira] Created: (ROL-1855) Automatic table creation fails on HSQLDB

Automatic table creation fails on HSQLDB
----------------------------------------

                 Key: ROL-1855
                 URL: https://issues.apache.org/jira/browse/ROL-1855
             Project: Roller
          Issue Type: Bug
          Components: Database Access & Data Model
    Affects Versions: 5.0
         Environment: Ubuntu 8.04 LTS, Sun JDK 1.6, Tomcat 6.0.20, HSQLDB 2.0 RC8
            Reporter: Juergen Kellerer
            Assignee: Roller Unassigned
            Priority: Minor


When Tomcat and Roller is set up with HSQLDB, I get a complaint when Roller tries to create its tables.
The exact message is "Unexpected token 'DEFAULT'" and comes up during the execution of the create table script for the table "webpage".

The bug is caused by a mistake in the keyword order and can be fixed by replacing:
  action          varchar(16) not null default 'custom'
with:
  action          varchar(16) default 'custom' not null

After this change all tables are created just fine.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (ROL-1855) Automatic table creation fails on HSQLDB

Posted by "Dave Johnson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ROL-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dave Johnson resolved ROL-1855.
-------------------------------

    Resolution: Fixed

Author: snoopdave
Date: Sat Feb 27 03:00:43 2010
New Revision: 916898

URL: http://svn.apache.org/viewvc?rev=916898&view=rev
Log:
Fixes Automatic table creation fails on HSQLDB
https://issues.apache.org/jira/browse/ROL-1855

> Automatic table creation fails on HSQLDB
> ----------------------------------------
>
>                 Key: ROL-1855
>                 URL: https://issues.apache.org/jira/browse/ROL-1855
>             Project: Roller
>          Issue Type: Bug
>          Components: Database Access & Data Model
>    Affects Versions: 5.0
>         Environment: Ubuntu 8.04 LTS, Sun JDK 1.6, Tomcat 6.0.20, HSQLDB 2.0 RC8
>            Reporter: Juergen Kellerer
>            Assignee: Dave Johnson
>            Priority: Minor
>             Fix For: 5.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When Tomcat and Roller is set up with HSQLDB, I get a complaint when Roller tries to create its tables.
> The exact message is "Unexpected token 'DEFAULT'" and comes up during the execution of the create table script for the table "webpage".
> The bug is caused by a mistake in the keyword order and can be fixed by replacing:
>   action          varchar(16) not null default 'custom'
> with:
>   action          varchar(16) default 'custom' not null
> After this change all tables are created just fine.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (ROL-1855) Automatic table creation fails on HSQLDB

Posted by "Dave Johnson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ROL-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dave Johnson reassigned ROL-1855:
---------------------------------

    Assignee: Dave Johnson  (was: Roller Unassigned)

> Automatic table creation fails on HSQLDB
> ----------------------------------------
>
>                 Key: ROL-1855
>                 URL: https://issues.apache.org/jira/browse/ROL-1855
>             Project: Roller
>          Issue Type: Bug
>          Components: Database Access & Data Model
>    Affects Versions: 5.0
>         Environment: Ubuntu 8.04 LTS, Sun JDK 1.6, Tomcat 6.0.20, HSQLDB 2.0 RC8
>            Reporter: Juergen Kellerer
>            Assignee: Dave Johnson
>            Priority: Minor
>             Fix For: 5.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When Tomcat and Roller is set up with HSQLDB, I get a complaint when Roller tries to create its tables.
> The exact message is "Unexpected token 'DEFAULT'" and comes up during the execution of the create table script for the table "webpage".
> The bug is caused by a mistake in the keyword order and can be fixed by replacing:
>   action          varchar(16) not null default 'custom'
> with:
>   action          varchar(16) default 'custom' not null
> After this change all tables are created just fine.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (ROL-1855) Automatic table creation fails on HSQLDB

Posted by "Juergen Kellerer (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ROL-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juergen Kellerer updated ROL-1855:
----------------------------------

    Fix Version/s: 5.0

> Automatic table creation fails on HSQLDB
> ----------------------------------------
>
>                 Key: ROL-1855
>                 URL: https://issues.apache.org/jira/browse/ROL-1855
>             Project: Roller
>          Issue Type: Bug
>          Components: Database Access & Data Model
>    Affects Versions: 5.0
>         Environment: Ubuntu 8.04 LTS, Sun JDK 1.6, Tomcat 6.0.20, HSQLDB 2.0 RC8
>            Reporter: Juergen Kellerer
>            Assignee: Roller Unassigned
>            Priority: Minor
>             Fix For: 5.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When Tomcat and Roller is set up with HSQLDB, I get a complaint when Roller tries to create its tables.
> The exact message is "Unexpected token 'DEFAULT'" and comes up during the execution of the create table script for the table "webpage".
> The bug is caused by a mistake in the keyword order and can be fixed by replacing:
>   action          varchar(16) not null default 'custom'
> with:
>   action          varchar(16) default 'custom' not null
> After this change all tables are created just fine.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.