db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-712) Support for sequences
Date Mon, 17 Aug 2009 16:32:14 GMT

    [ https://issues.apache.org/jira/browse/DERBY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744124#action_12744124
] 

Rick Hillegas commented on DERBY-712:
-------------------------------------

Hi Suran,

Thanks for the new create_drop_seequence_c.patch. I have a couple comments:


SequenceDescriptor.drop() - I would also add a call to dm.clearDependencies() as is done in
the corresponding code in TriggerDescriptor.

org.apache.derbyTesting.functionTests.tests.lang._Suite.suite() - This method still needs
to add SequenceTest to its list of tests. This is what wires SequenceTest into the regression
tests so that it is not just a standalone test.

SequenceTest - It does not appear to me that this test is running with authentication turned
on. Take a look at GeneratedColumnsPermsTest for an example of how to do this. You should
be able to get user-specific connections by calling openUserConnection() rather than by calling
DriverManager.getConnection(). Once you have made this change, it will be interesting to see
what happens to the test cases you have commented out. This will also be a good foundation
for adding GRANT/REVOKE tests when you get to that part of the project.

Thanks!
-Rick


> Support for sequences
> ---------------------
>
>                 Key: DERBY-712
>                 URL: https://issues.apache.org/jira/browse/DERBY-712
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>         Environment: feature request 
>            Reporter: Tony Dahbura
>            Assignee: Suran Jayathilaka
>             Fix For: 10.6.0.0
>
>         Attachments: altertable.diff, catalogs_a.patch, catalogs_b.patch, catalogs_c.patch,
catalogs_d.patch, catalogs_e.patch, catalogs_f.patch, catalogs_f_2.patch, catalogs_g.diff,
catalogs_h.diff, create_drop_sequence_a.patch, create_drop_sequence_b.patch, create_drop_sequence_c.patch,
create_sequence_a.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.


Mime
View raw message