[
https://issues.apache.org/jira/browse/DERBY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723241#action_12723241
]
Rick Hillegas commented on DERBY-712:
-------------------------------------
Hi Suran,
The altertable.diff indicates that the test was run under the old harness using
the Derby client. Looking through the output of a full test run, which I
launched earlier today, I only see altertable.sql logged once--as an embedded
test. Are you sure that you are supposed to run this test under the Derby
client?
The dropcrash2 test is one of the Store tests which is never run standalone. It
depends on the setup performed by tests which run before it in the
storerecovery suite, so dropcrash2 is only run as part of that suite. You run
that suite like this:
java org.apache.derbyTesting.functionTests.harness.RunSuite storerecovery
Hope this helps,
-Rick
> 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: altertable.diff, catalogs_a.patch, catalogs_b.patch,
> catalogs_c.patch, catalogs_d.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.
