db-ddlutils-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Dudziak (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (DDLUTILS-47) An identity column should be an primary key
Date Tue, 15 Nov 2005 08:47:28 GMT
     [ http://issues.apache.org/jira/browse/DDLUTILS-47?page=all ]
     
Thomas Dudziak reopened DDLUTILS-47:
------------------------------------


Ah, ok, now it is clear what the problem is. For Derby and other dbs, you are right, the PK
should be there. For Hsqldb, this leads to problems with older versions, and according to
the docs the field is automatically a PK column (http://hsqldb.sourceforge.net/doc/guide/ch09.html#create_table-section).

> An identity column should be an primary key
> -------------------------------------------
>
>          Key: DDLUTILS-47
>          URL: http://issues.apache.org/jira/browse/DDLUTILS-47
>      Project: DdlUtils
>         Type: Bug
>  Environment: Tested on Hsql and Derby
>     Reporter: Juliano Julio
>     Assignee: Thomas Dudziak
>     Priority: Blocker

>
> An identity column should be a primary key too! The method shouldGeneratePrimaryKeys
on SqlBuilder don't allow this.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message