[
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-03-aa-usagePrivilege.diff
Attaching derby-712-03-aa-usagePrivilege.diff. This patch adds support for the
USAGE privilege on sequences. While I was in there, I also made it illegal to
drop a schema that contains sequences. I am running regression tests now.
Touches the following files:
M java/engine/org/apache/derby/impl/sql/compile/NextSequenceNode.java
M java/engine/org/apache/derby/impl/sql/execute/DDLConstantAction.java
Wire in checking for the USAGE privilege.
M java/engine/org/apache/derby/impl/sql/catalog/DataDictionaryImpl.java
Fixed a bug which prevented us from detecting that a schema has sequences in it.
A
java/testing/org/apache/derbyTesting/functionTests/tests/lang/SequencePermsTest.java
M java/testing/org/apache/derbyTesting/functionTests/tests/lang/_Suite.java
Regression tests for USAGE privilege on sequences.
M java/testing/org/apache/derbyTesting/junit/JDBC.java
Made the CleanDatabaseTestSetup decorator drop sequences too when it is
dropping schema objects.
> 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, derby-712-02-aa-privilegeNodeCleanup.diff,
> derby-712-03-aa-usagePrivilege.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.
