[
https://issues.apache.org/jira/browse/DERBY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-712:
--------------------------------
Attachment: catalogs_h.diff
Hi Suran,
The failures occur during the test of soft-upgrade. The initial failure is
caused because the test is trying to drop a schema. In doing so, the data
dictionary checks to see whether the schema is empty. Since you added a new
kind of schema object (sequences) and logic to check whether SYSSEQUENCES is
empty, the data dictionary tries to scan SYSSEQUENCES. But in soft-upgrade
mode, this table doesn't exist. It is only created during hard upgrade. That's
what results in the funny -1 conglomerate id, which raises the initial
exception.The fix is to only scan SYSSEQUENCES if the data dictionary is at
level 10.6 or greater. I added this check on top of the changes you made to
DD_Version and have uploaded the resulting patch: catalogs_h.diff
With this patch, the upgrade tests run cleanly for me. So does standalone
DatabaseMetaDataTests. I am running the full regression tests now.
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, 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.
