db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harshvardhan Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6903) ALTER TABLE ALTER COLUMN resets CYCLE option of IDENTITY column
Date Wed, 24 May 2017 02:50:04 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Harshvardhan Gupta updated DERBY-6903:
--------------------------------------
    Issue Type: Sub-task  (was: Bug)
        Parent: DERBY-6904

> ALTER TABLE ALTER COLUMN resets CYCLE option of IDENTITY column
> ---------------------------------------------------------------
>
>                 Key: DERBY-6903
>                 URL: https://issues.apache.org/jira/browse/DERBY-6903
>             Project: Derby
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 10.13.1.0
>            Reporter: Bryan Pendleton
>            Priority: Minor
>
> Using ALTER TABLE with the SET INCREMENT BY or SET RESTART WITH
> options to make a change to a GENERATED ... BY IDENTITY column resets the CYCLE option
of that column to "off".
> Some test cases demonstrating this behavior were added as part of
> the DERBY-6852 change revision 1756287
> The problem occurs when the ALTER TABLE code drops and recreates
> the underlying SEQUENCE object, and does not preserve the CYCLE
> option of the underlying SEQUENCE object.
> I believe the correct behavior would be for the ALTER TABLE code
> to read the current CYCLE option of the underlying SEQUENCE object
> first, and then create the new SEQUENCE object with the same value
> for the CYCLE option.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message