[
https://issues.apache.org/jira/browse/DERBY-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906477#comment-15906477
]
Harshvardhan Gupta commented on DERBY-6904:
-------------------------------------------
Update on previous comment -
I tested with various scenarios by creating database without and with the new
changes using IJ. Whenever I try to access any of the databases created without
my changes through the patched version I get this error -
"In a base table there was a mismatch between the requested column number 9 and
the maximum number of columns 9.". Note that we increased the number of columns
in SYSCOLUMNs from 9 to 10 in this patch.
Should we incorporate a update strategy when older databases are accessed by
this patched version?
> 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
> Attachments: 6904.diff, columnMismatch, compareDbName
>
>
> 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)
