db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6906) Allow a GENERATED column to explicitly specify NO CYCLE
Date Sat, 15 Oct 2016 22:03:20 GMT

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

Bryan Pendleton commented on DERBY-6906:

A good place to start learning about this is to look at DERBY-6852.

This specific JIRA issue suggests altering the Derby SQL grammar so
that a CREATE TABLE statement can specify NO CYCLE for an IDENTITY column.

Having a close read of the code changes made by https://svn.apache.org/r1756287
should give you some guidance about precisely what part of the code
is involved for this.

> 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: Improvement
>          Components: SQL
>    Affects Versions:
>            Reporter: Bryan Pendleton
>            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