[
https://issues.apache.org/jira/browse/DERBY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suran Jayathilaka updated DERBY-712:
------------------------------------
Attachment: createseq_args_bind_a.diff
This draft patch contains the binding changes for the optional clauses of
Sequence creation. I've added some tests to SequenceTests but there are more
creation scenarios that need to be covered. Please review and comment.
What is the correct SQLState code to be used for Exception messages in cases
like the INCREMENT BY value being given as '0' or the MINVALUE being larger
than MAXVALUE? In this patch I used message ID "22008.S"
(LANG_INVALID_FUNCTION_ARGUMENT) for such scenarios.
Also, I noticed that the START WITH and INCREMENT BY options are order bound,
i.e. they have to appear just after the DATATYPE, and INCREMENT BY has to
follow START WITH if both are present. Is this a valid constraint or does the
parser code need to be modified?
> 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, derby-712-03-ac-usagePrivilege.diff,
> derby-712-04-aa-dblook.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.
