Details
Description
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.
Attachments
Attachments
Issue Links
- incorporates
-
DERBY-4513 Forbid NEXT VALUE FOR clause in certain contexts
- Closed
-
DERBY-4580 Cannot use dblook on soft-upgraded database: Table/View 'SYS.SYSSEQUENCES' does not exist.
- Closed
-
DERBY-4539 Make it possible to put the optional clauses of a CREATE SEQUENCE statement in the arbitrary order allowed by the SQL Standard
- Closed
-
DERBY-4487 Add dblook support for SEQUENCEs
- Closed
-
DERBY-4565 Create concurrency test to stress sequence generators.
- Closed
- is blocked by
-
DERBY-5151 Don't leak unused identity/sequence values on abnormal exit.
- Open
- is depended upon by
-
DERBY-4568 Documentation needed for sequence generators
- Closed
- is related to
-
DERBY-6494 NEXT VALUE FOR should be illegal inside a COALESCE expression
- Open
-
DERBY-4437 Concurrent inserts into table with identity column perform poorly
- Closed
-
DERBY-5426 Improve the error raised by too much contention on a sequence/identity.
- Closed
- relates to
-
DERBY-4393 lang.SequenceTest fails w/ "Sequence 'ALPHA_SEQ' already exists." on phoneME/cvm
- Closed
-
DERBY-5254 The keywords introduced by the CREATE SEQUENCE work are treated as reserved rather than unreserved.
- Closed
-
DERBY-103 Global Oracle/Axion style sequence generator
- Closed