db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-3888) ALTER TABLE ... ADD COLUMN cannot add identity columns
Date Wed, 21 May 2014 07:23:39 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004439#comment-14004439

Knut Anders Hatlen commented on DERBY-3888:

Also, 11.11 <add column definition>, syntax rule 2b case i, describes how a new identity
column is populated, and it doesn't make any distinction between GENERATED ALWAYS and GENERATED
BY DEFAULT. The current code doesn't allow adding an identity column generated by default
to a non-empty table, but it doesn't look like the standard has such a limitation.

> ALTER TABLE ... ADD COLUMN cannot add identity columns
> ------------------------------------------------------
>                 Key: DERBY-3888
>                 URL: https://issues.apache.org/jira/browse/DERBY-3888
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>              Labels: derby_triage10_10
>         Attachments: reenable-v2.diff, reenable.diff
> ALTER TABLE .. ADD COLUMN cannot be used to add an identity column. There is code to
handle identity columns, but it is disabled in the parser. See this thread on derby-user:
> http://mail-archives.apache.org/mod_mbox/db-derby-user/200708.mbox/%3C46C5DAA9.8080507@sbcglobal.net%3E
> The code was disabled for DB2 compatibility. Since DB2 compatibility is not a goal for
Derby, we should see if we could re-enable it.

This message was sent by Atlassian JIRA

View raw message