[
https://issues.apache.org/jira/browse/DERBY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749939#action_12749939
]
Rick Hillegas commented on DERBY-712:
-------------------------------------
Thanks for the new patch, Suran.
> For now, is it correct to only invalidate for
> DependencyManager.USER_RECOMPILE_REQUEST and to add actions for
> DependencyManager.REVOKE_PRIVILEGE etc. after GRANT/REVOKE functionality has
> been added? If this revision looks ok I will start running the regression
> tests.
Sounds good to me.
> After enabling authentication for SequenceTest, the current tests run fine.
> What other test scenarios should be added to this test class?
I think the tests you have now are adequate. As you add more functionality,
there will be more to test.
By the way, the test failed for me when I ran it against jar files. That is
because a ClassNotFoundException was being raised when the engine tried to
fault in CreateSequenceNode. That, in turn, was because the same property name
was being used for CreateSequenceNode and DropSequenceNode in
DBMSnodes.properties. The test ran cleanly for me after I made the following
change to DBMSnodes.properties:
-derby.module.cloudscapenodes.gw=org.apache.derby.impl.sql.compile.DropSequenceNode
+derby.module.cloudscapenodes.gx=org.apache.derby.impl.sql.compile.DropSequenceNode
I am running the full regression tests now. Thanks.
> 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_drop_sequence_d.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.
