[
https://issues.apache.org/jira/browse/DERBY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723107#action_12723107
]
Rick Hillegas commented on DERBY-712:
-------------------------------------
Hi Suran,
Thanks for the revised patch with test fixes. I haven't re-run the tests with
this patch but in general the changes to the tests look good. A couple points:
o In GrantRevokeDDLTest, it looks like the name of SYSPERMS has been
mis-spelled.
o There's a new println in JDBC. That may be ok but it looks like it might be a
piece of debug scaffolding which wasn't removed before the patch was generated.
Thanks!
> 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, catalogs_c.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.
