[
https://issues.apache.org/jira/browse/DERBY-6959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6959:
---------------------------------
Attachment: derby-6959-02-aa-setCycleDocs.diff
Attaching derby-6959-02-aa-setCycleDocs.diff. This updates the Reference Manual
section on ALTER TABLE to include the SET keyword in the grammar for changing
the cycling behavior of an identity column. Also attaching the generated html
output: rrefsqlj81859.html
Touches the following file:
M src/ref/rrefsqlj81859.dita
> 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
>
>
> 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)
