db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Dudgeon <tdudg...@informaticsmatters.com>
Subject Re: [jira] Resolved: (DERBY-1489) Provide ALTER TABLE DROP COLUMN functionality
Date Mon, 09 Oct 2006 08:34:47 GMT
Bryan, thanks for all your help with this.
I've done tests similar to 2 and 4 and that seemed to work fine.
I do have some more questions relating to upgrading, but I think this is 
more appropriate for the users list so I've started a new topic there.

Thanks again for all your help.


Bryan Pendleton wrote:
>>> Unsupported upgrade from '10.2' to '10.3 beta'.
>>> Is this a problems with the 10.2, or the 10.3 beta?
> It is the 10.3 trunk that is refusing the upgrade. The 10.2 database is 
> fine.
> Here's some more details:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200504.mbox/%3c42694E55.5060500@debrunners.com%3e

> http://db.apache.org/derby/papers/versionupgrade.html
>>> If its with 10.2 how do I make sure the database files can be upgraded?
> Since the issue is with the trunk, not with 10.2, this may not matter, but
> if you want to test how your databases will respond to upgrade, several
> ideas come to mind:
> 1) Set the special flags and verify that you can upgrade from 10.2. to 
> trunk
> 2) Build a copy of the trunk code in which you turn off the alpha and beta
> flags so that your local copy believes it is a true released copy of 10.3,
> and then upgrade from 10.2 to your special 10.3.
> 3) Create the database using 10.2 and upgrade it *to* 10.2 by passing the
> upgrade flag. I believe this should be a no-op, but it's still a test.
> 4) Backport your changes to 10.1, and then test that you can upgrade a
> 10.1-created database to 10.2. This is obviously more work, but it should
> give you increased confidence that you can upgrade such a database.
> Hope this helps,
> thanks,
> bryan

View raw message