db-ddlutils-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Juliano Julio (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DDLUTILS-47) An identity column should be an primary key
Date Mon, 14 Nov 2005 20:22:28 GMT
    [ http://issues.apache.org/jira/browse/DDLUTILS-47?page=comments#action_12357622 ] 

Juliano Julio commented on DDLUTILS-47:
---------------------------------------

Exactly! That is the point! If I setPrimaryKey(true) and setAutoincrement(true) this suppose
to generate:

create table TABLE_NAME
(PK_NAME int generated always (or default) as identity 
...,
PRIMARY KEY (PK_NAME)
);

But the ddlutils isn't work like this... this is the reason:

     * Determines whether we should generate a primary key constraint for the given
     * primary key columns. By default if there are no primary keys or the column(s) are 
     * all auto increment (identity) columns then there is no need to generate a primary key

     * constraint.

> 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