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] Resolved: (DDLUTILS-47) An identity column should be an primary key
Date Mon, 14 Nov 2005 20:02:28 GMT
     [ http://issues.apache.org/jira/browse/DDLUTILS-47?page=all ]
     
Thomas Dudziak resolved DDLUTILS-47:
------------------------------------

    Resolution: Won't Fix

Derby and othr databases support a special type of column - IDENTITY in Derby, autoincrement
in MySQL - where the database automatically determines the value of the column if not explicitly
specified. You're right that most of the time this is only applicable to primary key columns.
However, this is not always the case. For databases like Oracle, the auto-increment is implemented
via a sequence, and there is no requirement that the column need to be a primary key.
Hence, you need to specify both autoincrement and primarykey for the column for databases
that require it.

> 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