[
https://issues.apache.org/jira/browse/DERBY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718882#action_12718882
]
Rick Hillegas commented on DERBY-712:
-------------------------------------
My regression test run finished. As expected, the catalogs_b.patch introduces a
number of errors, largely related to the fact that the existing tests need to
be made aware of the new catalogs:
Failures in tests run under the old harness:
altertable
compressTable
dropcrash2
Failures in JUnit tests:
SystemCatalogTest
DatabaseMetaDataTest
PrimaryKeyTest
ViewsTest
metadataMultiConnTest
OfflineBackupTest
CollationTest
GrantRevokeDDLTest
DMDBugsTest
ToolScripts
> Support for sequences
> ---------------------
>
> Key: DERBY-712
> URL: https://issues.apache.org/jira/browse/DERBY-712
> Project: Derby
> Issue Type: New Feature
> Components: SQL
> Environment: feature request
> Reporter: Tony Dahbura
> Assignee: Suran Jayathilaka
> Fix For: 10.6.0.0
>
> Attachments: catalogs_a.patch, catalogs_b.patch,
> SequenceGenerator.html
>
>
> 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.
