[
https://issues.apache.org/jira/browse/DERBY-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harshvardhan Gupta updated DERBY-6904:
--------------------------------------
Attachment: compareDbName
columnMismatch
Some of the existing tests are failing with one of the following reasons -
1)Engine Shutdown: Expected XJ015 but was XSCH5 in method assertSQLState
Referring to https://db.apache.org/derby/docs/10.2/ref/rrefexcept71493.html , I
think this error is mostly due to addition of a new column in SYSCOLUMNS which
is not there in existing DB jars when they are brought to memory in test
packages. (HSCH5 is a heap class SQLState)
2) compareDatabaseNames throws mismatch error while building a connection. I
think these errors are a direct result of the above error when shutdown is not
clean.
I am attaching both the error stacks for reference. Please take a look at the
error stacks and give your inputs.
> 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)
