You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2017/09/10 19:52:00 UTC

[jira] [Updated] (DERBY-6959) Require the Standard SET keyword in the syntax for changing the cycle behavior of identity columns

     [ https://issues.apache.org/jira/browse/DERBY-6959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas updated DERBY-6959:
---------------------------------
    Summary: Require the Standard SET keyword in the syntax for changing the cycle behavior of identity columns  (was: Required the Standard SET keyword in the syntax for changing the cycle behavior of identity columns)

> Require the Standard SET keyword in the syntax for changing the cycle behavior of identity columns
> --------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6959
>                 URL: https://issues.apache.org/jira/browse/DERBY-6959
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.14.0.0
>            Reporter: Rick Hillegas
>             Fix For: 10.14.0.0
>
>
> The correct syntax for changing the cycling behavior of an auto-increment column is...
>   ALTER TABLE ALTER COLUMN $columnName SET [NO] CYCLE
> ...according to the 2016 SQL Standard, part 2, sections 11.20 (<alter identity column specification) and 11.72 (<sequence generator definition>). This is also the syntax used by DB2 (see https://www.ibm.com/support/knowledgecenter/en/SSEPEK_10.0.0/sqlref/src/tpc/db2z_sql_altertable.html). Right now Derby does not accept the required SET keyword. We should bring Derby into compliance with the Standard. I will attach a patch to do this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)