[
https://issues.apache.org/jira/browse/DERBY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683527#action_12683527
]
Suran Jayathilaka commented on DERBY-712:
-----------------------------------------
Hi Rick,
First of all thank you very much for posting this detailed functional
specification.
For the Computer Science degree course I am following in my university, we're
supposed to complete a research or implementation based project. Having had a
wonderful experience working with the Derby community last year, I decided to
contribute to Derby as fulfillment of this requirement, and selected this
issue, i.e. Adding sequence generators for Apache Derby. In the days since I
assigned this issue to myself, I did some background research and submitted a
project proposal, literature survey and interim report which were accepted by
the university project committee. My plan was to begin the implementation work
immediately after the semester exams which have only just finished.
Although I haven't been able to produce any work I can share with the
community, I am now ready to begin with the coding, and would be very much
obliged if you'd be willing to act as a mentor to me during the implementation
process.
Furthermore, since Google Summer of Code 2009 is starting, I would like to
submit a proposal for implementing sequence generators for Derby, and would
like to have your feedback.
Thanks!
Suran
> 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.
