Hello.
Daniel John Debrunner wrote:
Hard upgrade works currently, I checked in a manual test under java/testing/org/apache/derbyTesting/upgradeTests.
Do you means that upgrade=true option surely update DD_Version in database ? If so, I might mistake what happened at my testing.
Any way , I will check hardupgrade test again.
Best regards.
/*
Tomohito Nakayama
[EMAIL PROTECTED]
[EMAIL PROTECTED] Naka
http://www5.ocn.ne.jp/~tomohito/TopPage.html*/
----- Original Message ----- From: "Daniel John Debrunner" <[EMAIL PROTECTED]>
To: "Derby Development" <[email protected]>
Sent: Friday, May 13, 2005 1:23 AM
Subject: Re: Patch again for DERBY-167.
TomohitoNakayama wrote:Hello.
I send new patch for DERBY-167. Please review it again.
I have one question.
There seems to be NO implementation to update externalized DD_Version. So now, hardupgrade does not works and we can't use BY DEFAULT .
Should it be implemented in this task ?
I have hesitation about updating version info myself ....
I don't understand your question.
In the previous e-mails I had thought that the only upgrade change required was the checkVersion if specifying BY DEFAULT.
Hard upgrade works currently, I checked in a manual test under java/testing/org/apache/derbyTesting/upgradeTests. It doesn't run as part of the test harness and thius is not part of derbyall. This is because it boots several JVMs sequentially with different class paths (e.g. old version and new version). There is a shell script to run the test, runphases.ksh
Dan.
-- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.9 - Release Date: 2005/05/12
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.9 - Release Date: 2005/05/12
