[
https://issues.apache.org/jira/browse/DERBY-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895674#comment-15895674
]
Harshvardhan Gupta commented on DERBY-6904:
-------------------------------------------
Hi Bryan,
I am new to Derby development and would like to take this project as a ramp up
task to start contributing to Derby. I built the source code and ran the tests.
Also, I examined the code changes as part of introducing the cycle option in
DERBY-6852. The grammar for create statement was extended to support CYCLE or
NO CYCLE to be passed in the definition of identity columns and underlying
column definitions and sequencing logic updated to support it.
The following logical steps should be good for this task -
1) Extend the ALTER TABEL ALTER COLUMN grammar to optionally specify the
cycling options.
2) Reflect the changes if any in the underlying Sequence Object.
I'll also fix DERBY-6903 along with this task which is a closely related bug
which resets the cycling option to default if the sequence object is modified
using ALTER COLUMN statements.
> Enhance ALTER TABLE to allow CYCLE option to be changed.
> --------------------------------------------------------
>
> Key: DERBY-6904
> URL: https://issues.apache.org/jira/browse/DERBY-6904
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.13.1.0
> Reporter: Bryan Pendleton
> Priority: Minor
>
> It would be nice to have a variant of the ALTER TABLE statement,
> similar to the SET INCREMENT BY or SET RESTART WITH variants,
> that allowed a user to change the CYCLE option on an IDENTITY column.
> I think that the code flow for this could be closely modelled on the
> code flow for the SET INCREMENT BY variant: after the statement
> is parsed, we simply need to drop and recreate the underlying SEQUENCE
> object with the desired CYCLE option (and preserving all the other
> aspects of the underlying SEQUENCE object.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
