[
https://issues.apache.org/jira/browse/DERBY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683918#action_12683918
]
Rick Hillegas commented on DERBY-712:
-------------------------------------
Hi Suran. This is terrific. I would be delighted to mentor you as you implement
this feature. I have added this project as one of Derby's Summer of Code
possibilities: http://wiki.apache.org/general/SummerOfCode2009#derby-project
Now that you are ready to code, I would recommend starting with the catalog
work:
1) Add the new SYSSEQUENCES and SYSPERMS tables
2) Add upgrade logic and tests to support the creation of these catalogs in old
(10.5 and earlier) databases
The SYSROLES table was just added to Derby in 10.5 and should serve as a good
example of how to add a new catalog.
Feel free to pepper me with questions. 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
> Attachments: 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.
