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 Tue, 07 Jul 2009 18:56:14 GMT

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

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

Hi Suran,

We are getting very close with this patch but there is still a little more work to do. Now
you need to add upgrade logic which will create the new catalogs in old databases which are
hard-upgraded to 10.6. This is really easy to do.

The test failures in the DatabaseMetaData cases occur when those cases are run as part of
the upgrade tests. You need to add some upgrade logic to DD_Version.doFullUpgrade(). That
logic will create the new SYSSEQUENCES and SYSPERMS catalogs in old databases. You will want
to add these catalogs if the original database version is 10.5 or earlier. Look for the addition
of SYSROLES as a template for how to do this.

To verify that you have done this correctly, you will want to run the upgrade tests. The following
works for me:

java -XX:MaxPermSize=128M -Xmx512m -DderbyTesting.oldReleasePath=$OLD_RELEASE_DIRECTORY junit.textui.TestRunner
org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite

where $OLD_RELEASE_DIRECTORY is the full pathname of the directory which holds your old Derby
releases. That directory should have a directory for each previous release on which you want
to test upgrade. For instance, my old release directory has the following subdirectories (for
the purposes of this work, you could probably just get away with the 10.5.1.1 release):

10.0.2.1
10.1.1.0
10.1.2.1
10.1.3.1
10.2.1.6
10.2.2.0
10.2.2.1
10.3.1.4
10.3.2.1
10.3.3.0
10.4.1.3
10.4.2.0
10.4.2.1
10.5.1.1

Each of those subdirectories, in turn, should hold the jar files for that release.

I think that you did not trip across these test failures because when you run the JUnit tests,
you don't set the -DderbyTesting.oldReleasePath flag on the command line. That's what triggers
the upgrade tests. To make sure that you always run the upgrade tests as part of your regression
test run, make sure to use that flag. E.g.:

java -XX:MaxPermSize=128M -Xmx512m -DderbyTesting.oldReleasePath=$OLD_RELEASE_DIRECTORY  junit.textui.TestRunner
org.apache.derbyTesting.functionTests.suites.All

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,
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