db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-712) Support for sequences
Date Sat, 13 Feb 2010 15:12:28 GMT

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

Rick Hillegas updated DERBY-712:
--------------------------------

    Attachment: derby-712-06-aa-restrictedDrops.diff

Attaching derby-712-06-aa-restrictedDrops.diff. This patch limits DROP SEQUENCE to RESTRICTed
drops. This makes the syntax conform to the current behavior. The DROP SEQUENCE statement
raises an error if any triggers or views mention the sequence. This is NOT the behavior described
by the functional spec. The spec called for CASCADEd drops. The spec will be revised after
this syntax change is checked in. Tests passed cleanly for me.

Touches the following files:

----------

M      java/engine/org/apache/derby/impl/sql/compile/sqlgrammar.jj

Require the RESTRICT keyword in DROP SEQUENCE statements.

----------

M      java/engine/org/apache/derby/iapi/sql/dictionary/SequenceDescriptor.java

Added a comment noting the RESTRICTed behavior of sequence drops.

----------

M      java/testing/org/apache/derbyTesting/functionTests/tests/lang/SequencePermsTest.java
M      java/testing/org/apache/derbyTesting/functionTests/tests/lang/GeneratedColumnsHelper.java
M      java/testing/org/apache/derbyTesting/functionTests/tests/lang/SequenceTest.java
M      java/testing/org/apache/derbyTesting/functionTests/tests/lang/UDTPermsTest.java
M      java/testing/org/apache/derbyTesting/functionTests/tests/lang/SequenceGeneratorTest.java
M      java/testing/org/apache/derbyTesting/junit/JDBC.java

Alter the tests to reflect this syntax change.


> Support for sequences
> ---------------------
>
>                 Key: DERBY-712
>                 URL: https://issues.apache.org/jira/browse/DERBY-712
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>         Environment: feature request 
>            Reporter: Tony Dahbura
>            Assignee: Suran Jayathilaka
>             Fix For: 10.6.0.0
>
>         Attachments: altertable.diff, catalogs_a.patch, catalogs_b.patch, catalogs_c.patch,
catalogs_d.patch, catalogs_e.patch, catalogs_f.patch, catalogs_f_2.patch, catalogs_g.diff,
catalogs_h.diff, create_drop_sequence_a.patch, create_drop_sequence_b.patch, create_drop_sequence_c.patch,
create_drop_sequence_d.patch, create_sequence_a.patch, createseq_args_bind_a.diff, createseq_args_bind_b.diff,
derby-712-02-aa-privilegeNodeCleanup.diff, derby-712-03-aa-usagePrivilege.diff, derby-712-03-ac-usagePrivilege.diff,
derby-712-04-aa-dblook.diff, derby-712-05-af-sequenceGenerator.diff, derby-712-05-al-sequenceGenerator.diff,
derby-712-06-aa-restrictedDrops.diff, SequenceGenerator.html, sequences_next_value_a.patch
>
>
> Would like to see support added for sequences.  This would permit a select against the
sequence to always obtain a ever increasing/decreasing value.  The identity column works fine
but there are times for applications where the application needs to obtain the sequence number
and use it prior to the database write.  Subsequent calls to the table/column would result
in a new number on each call.
> SQL such as the following:
> SELECT NEXT VALUE FOR sequence_name FROM sometable ; would result in a next value.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message