[
https://issues.apache.org/jira/browse/DERBY-6959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162259#comment-16162259
]
ASF subversion and git services commented on DERBY-6959:
--------------------------------------------------------
Commit 1808071 from [~rhillegas] in branch 'code/trunk'
[ https://svn.apache.org/r1808071 ]
DERBY-6959: Require Standard SET keyword when changing the cycling behavior of
an identity column; commit derby-6959-01-ab-requireSETkeyword.diff.
> 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
> Assignee: Rick Hillegas
> Fix For: 10.14.0.0
>
> Attachments: derby-6959-01-aa-requireSETkeyword.diff,
> derby-6959-01-ab-requireSETkeyword.diff, derby-6959-02-aa-setCycleDocs.diff,
> rrefsqlj81859.html
>
>
> 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)
