db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6906) Allow a GENERATED column to explicitly specify NO CYCLE
Date Thu, 01 Jun 2017 22:03:05 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033790#comment-16033790

ASF subversion and git services commented on DERBY-6906:

Commit 1797283 from [~bryanpendleton] in branch 'code/trunk'
[ https://svn.apache.org/r1797283 ]

DERBY-6904: Enhance ALTER TABLE to allow CYCLE option to be changed
DERBY-6905: Enhance SYS.SYSCOLUMNS to report the CYCLE value
DERBY-6906: Allow a GENERATED column to explicitly specify NO CYCLE

This patch was contributed by Harshvardhan Gupta (harshvardhan145 at gmail dot com)

The patch adds the CYCLE property as a fundamental property associated
with a column similar to current increment value, current increment step etc.

 *  SYS.SYSCOLUMNS extended to hold the cycle value of identity column.
 *  Extended the grammar to accept "cycle","no cycle" in alter clause
    and changed the underlying column descriptor and sequencing objects.
 *  ALTER clause not involving cycle option (i.e increment and restart)
    won't affect the cycle option.

The code flow for the upgrade handling was modelled after Derby-534
for introducing a new in column SYSTRIGGERS. There are new behaviors
for SYSCOLUMNS in both soft- and hard-upgrade scenarios.

> Allow a GENERATED column to explicitly specify NO CYCLE
> -------------------------------------------------------
>                 Key: DERBY-6906
>                 URL: https://issues.apache.org/jira/browse/DERBY-6906
>             Project: Derby
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions:
>            Reporter: Bryan Pendleton
>            Assignee: Harshvardhan Gupta
>            Priority: Minor
> DERBY-6852 added the ability for a GENERATED IDENTITY column
> to specify that it should have CYCLE behavior, utilizing the underlying
> CYCLE behavior of the SEQUENCE object.
> A column which does not wish to have CYCLE behavior is specified
> by omitting the the CYCLE keyword.
> It would be nice to allow a GENERATED IDENTITY column to
> explicitly specify that it should have NO CYCLE behavior.

This message was sent by Atlassian JIRA

View raw message