Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 43273 invoked from network); 13 May 2005 14:20:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 May 2005 14:20:21 -0000 Received: (qmail 17774 invoked by uid 500); 13 May 2005 14:24:30 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 17707 invoked by uid 500); 13 May 2005 14:24:29 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 17679 invoked by uid 99); 13 May 2005 14:24:28 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=HTML_50_60,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from basil.ocn.ne.jp (HELO smtp.basil.ocn.ne.jp) (222.146.51.83) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 13 May 2005 07:24:28 -0700 Received: from [192.168.0.32] (p14064-adsan10honb5-acca.tokyo.ocn.ne.jp [61.118.68.64]) by smtp.basil.ocn.ne.jp (Postfix) with ESMTP id 408ACF1C for ; Fri, 13 May 2005 23:19:57 +0900 (JST) Received: from 127.0.0.1 (AVG SMTP 7.0.308 [266.11.9]); Fri, 13 May 2005 23:21:26 +0900 Message-ID: <000e01c557c7$0c333c80$2000a8c0@Arkat> From: "TomohitoNakayama" To: "Derby Development" Subject: upgrading trouble ... (Re: Patch again for DERBY-167.) Date: Fri, 13 May 2005 23:21:21 +0900 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=======AVGMAIL-4284B7E66C5C=======" X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --=======AVGMAIL-4284B7E66C5C======= Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01C55812.794CA950" ------=_NextPart_000_000A_01C55812.794CA950 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Hello. I describe detail ... I tried to hard upgrade database , whose name is "oldver"and created by derby10.0.2.1 , to version of current developing derby as next. Judging from derby10.0.2.1 could connect to oldver after upgrading, I think hard updating version oldver was failed. //And my modification of DERBY-167 does not work though hard upgrade was executed. ============================ 中山智仁@Arkat ~/derbyUser/20050513 $ ijOld.bat c:\ProgramDev\derbyUser\20050513>set DERBY_INSTALL=C:\ProgramDev\derby10.0.2.1\lib\ c:\ProgramDev\derbyUser\20050513>set DERBY_INSTALL=C:\ProgramDev\derby10.0.2.1\lib\ c:\ProgramDev\derbyUser\20050513>FOR %X in ("C:\ProgramDev\derby10.0.2.1\lib\") DO SET DERBY_INSTALL=%~sX c:\ProgramDev\derbyUser\20050513>SET DERBY_INSTALL=C:\PROGRA~2\DERBY1~1.1\lib\ c:\ProgramDev\derbyUser\20050513>set CLASSPATH=C:\PROGRA~2\DERBY1~1.1\lib\\derby.jar;C:\PROGRA~2\DERBY1~1.1\lib\\derbytools.jar; c:\ProgramDev\derbyUser\20050513>java -Dij.protocol=jdbc:derby: org.apache.derby.tools.ij ij version 10.0 (C) Copyright IBM Corp. 1997, 2004. ij> connect 'jdbc:derby:oldver;create=true'; ij> exit; 中山智仁@Arkat ~/derbyUser/20050513 $ ij.bat c:\ProgramDev\derbyUser\20050513>set DERBY_INSTALL=c:\ProgramDev\derby\trunk\ c:\ProgramDev\derbyUser\20050513>set DERBY_INSTALL=c:\ProgramDev\derby\trunk\jars\sane c:\ProgramDev\derbyUser\20050513>FOR %X in ("c:\ProgramDev\derby\trunk\jars\sane") DO SET DERBY_INSTALL=%~sX c:\ProgramDev\derbyUser\20050513>SET DERBY_INSTALL=c:\PROGRA~2\derby\trunk\jars\sane c:\ProgramDev\derbyUser\20050513>set CLASSPATH=c:\PROGRA~2\derby\trunk\jars\sane\derby.jar;c:\PROGRA~2\derby\trunk\jars\sane\derbytools.jar; c:\ProgramDev\derbyUser\20050513>java -Dij.protocol=jdbc:derby: -Dderby.database .allowPreReleaseUpgrade=true org.apache.derby.tools.ij ij version 10.1 ij> connect 'jdbc:derby:oldver;update=true'; URL Attribute [update=true] Attribute is unknown to Derby. ij> connect 'jdbc:derby:oldver;upgrade=true'; ij(CONNECTION1)> exit; 中山智仁@Arkat ~/derbyUser/20050513 $ ijOld.bat c:\ProgramDev\derbyUser\20050513>set DERBY_INSTALL=C:\ProgramDev\derby10.0.2.1\lib\ c:\ProgramDev\derbyUser\20050513>set DERBY_INSTALL=C:\ProgramDev\derby10.0.2.1\lib\ c:\ProgramDev\derbyUser\20050513>FOR %X in ("C:\ProgramDev\derby10.0.2.1\lib\")DO SET DERBY_INSTALL=%~sX c:\ProgramDev\derbyUser\20050513>SET DERBY_INSTALL=C:\PROGRA~2\DERBY1~1.1\lib\ c:\ProgramDev\derbyUser\20050513>set CLASSPATH=C:\PROGRA~2\DERBY1~1.1\lib\\derby.jar;C:\PROGRA~2\DERBY1~1.1\lib\\derbytools.jar; c:\ProgramDev\derbyUser\20050513>java -Dij.protocol=jdbc:derby: org.apache.derby.tools.ij ij version 10.0 (C) Copyright IBM Corp. 1997, 2004. ij> connect 'jdbc:derby:oldver'; ij> ============================ And more, if I does not execute mitaken command "connect 'jdbc:derby:oldver;update=true';", I didn't see above phenomena. //And my modification of DERBY-167 works after hard upgrade. And more I wonder why prompt was showd as "ij(CONNECTION1)>"..... Best regards. /* Tomohito Nakayama tomonaka@basil.ocn.ne.jp tomohito@rose.zero.ad.jp Naka http://www5.ocn.ne.jp/~tomohito/TopPage.html */ ----- Original Message ----- From: "TomohitoNakayama" To: "Derby Development" Sent: Friday, May 13, 2005 6:56 AM Subject: Re: Patch again for DERBY-167. > 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 > tomonaka@basil.ocn.ne.jp > tomohito@rose.zero.ad.jp > > Naka > http://www5.ocn.ne.jp/~tomohito/TopPage.html > > */ > ----- Original Message ----- > From: "Daniel John Debrunner" > To: "Derby Development" > 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 >> > ------=_NextPart_000_000A_01C55812.794CA950 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable =EF=BB=BF
Hello.
 
I describe detail = ...
 
 
I tried to hard upgrade = database , whose=20 name is "oldver"and created by derby10.0.2.1 ,
to version of current = developing=20 derby as next.
 
Judging from derby10.0.2.1 = could connect=20 to oldver after upgrading,
I think hard updating version=20 oldver was failed.
//And my modification of = DERBY-167 does=20 not work though hard upgrade was executed.
 
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D
 
 
=E4=B8=AD=E5=B1=B1=E6=99=BA=E4=BB=81@Arkat = ~/derbyUser/20050513
$=20 ijOld.bat
 
c:\ProgramDev\derbyUser\20050513>set=20 DERBY_INSTALL=3DC:\ProgramDev\derby10.0.2.1\lib\
c:\ProgramDev\derbyUser\20050513>set=20 DERBY_INSTALL=3DC:\ProgramDev\derby10.0.2.1\lib\
c:\ProgramDev\derbyUser\20050513>FOR %X=20 in ("C:\ProgramDev\derby10.0.2.1\lib\")
DO SET=20 DERBY_INSTALL=3D%~sX
c:\ProgramDev\derbyUser\20050513>SET=20 DERBY_INSTALL=3DC:\PROGRA~2\DERBY1~1.1\lib\
c:\ProgramDev\derbyUser\20050513>set=20 CLASSPATH=3DC:\PROGRA~2\DERBY1~1.1\lib\\derby.jar;C:\PROGRA~2\DERBY1~1.1\= lib\\derbytools.jar;
c:\ProgramDev\derbyUser\20050513>java=20 -Dij.protocol=3Djdbc:derby:  org.apache.derby.tools.ij
ij = version 10.0 (C)=20 Copyright IBM Corp. 1997, 2004.
ij> connect=20 'jdbc:derby:oldver;create=3Dtrue';
ij> exit;
 
 
=E4=B8=AD=E5=B1=B1=E6=99=BA=E4=BB=81@Arkat = ~/derbyUser/20050513
$=20 ij.bat
c:\ProgramDev\derbyUser\20050513>set=20 DERBY_INSTALL=3Dc:\ProgramDev\derby\trunk\
c:\ProgramDev\derbyUser\20050513>set=20 DERBY_INSTALL=3Dc:\ProgramDev\derby\trunk\jars\sane
c:\ProgramDev\derbyUser\20050513>FOR %X=20 in ("c:\ProgramDev\derby\trunk\jars\sane") DO SET=20 DERBY_INSTALL=3D%~sX
c:\ProgramDev\derbyUser\20050513>SET=20 DERBY_INSTALL=3Dc:\PROGRA~2\derby\trunk\jars\sane
c:\ProgramDev\derbyUser\20050513>set=20 CLASSPATH=3Dc:\PROGRA~2\derby\trunk\jars\sane\derby.jar;c:\PROGRA~2\derby= \trunk\jars\sane\derbytools.jar;
c:\ProgramDev\derbyUser\20050513>java=20 -Dij.protocol=3Djdbc:derby: = -Dderby.database
.allowPreReleaseUpgrade=3Dtrue=20 org.apache.derby.tools.ij
ij version 10.1
ij> connect=20 'jdbc:derby:oldver;update=3Dtrue';
URL Attribute = [update=3Dtrue]
  =20 Attribute is unknown to Derby.
ij> connect=20 'jdbc:derby:oldver;upgrade=3Dtrue';
ij(CONNECTION1)> = exit;
 
=E4=B8=AD=E5=B1=B1=E6=99=BA=E4=BB=81@Arkat = ~/derbyUser/20050513
$=20 ijOld.bat
c:\ProgramDev\derbyUser\20050513>set=20 DERBY_INSTALL=3DC:\ProgramDev\derby10.0.2.1\lib\
c:\ProgramDev\derbyUser\20050513>set=20 DERBY_INSTALL=3DC:\ProgramDev\derby10.0.2.1\lib\
c:\ProgramDev\derbyUser\20050513>FOR %X=20 in ("C:\ProgramDev\derby10.0.2.1\lib\")DO SET = DERBY_INSTALL=3D%~sX
c:\ProgramDev\derbyUser\20050513>SET=20 DERBY_INSTALL=3DC:\PROGRA~2\DERBY1~1.1\lib\
c:\ProgramDev\derbyUser\20050513>set=20 CLASSPATH=3DC:\PROGRA~2\DERBY1~1.1\lib\\derby.jar;C:\PROGRA~2\DERBY1~1.1\= lib\\derbytools.jar;
c:\ProgramDev\derbyUser\20050513>java=20 -Dij.protocol=3Djdbc:derby:  org.apache.derby.tools.ij
ij = version 10.0 (C)=20 Copyright IBM Corp. 1997, 2004.
ij> connect=20 'jdbc:derby:oldver';
ij>
 
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D
 
And more, if I does not = execute mitaken=20 command "connect 'jdbc:derby:oldver;update=3Dtrue';",
I didn't see above phenomena.=20
//And my modification of = DERBY-167 works=20 after hard upgrade.
 
And more I wonder why = prompt was=20 showd as "ij(CONNECTION1)>".....
 
 
Best regards.
 
 
 
/*
 
         Tomohito=20 Nakayama
         tomonaka@basil.ocn.ne.jp
         tomohito@rose.zero.ad.jp
 
        =20 Naka
         http://www5.ocn.ne.jp/~tomohito/TopPage.html
 
*/
----- Original Message ----- =
From: "TomohitoNakayama" = <tomonaka@basil.ocn.ne.jp>
To: "Derby Development" = <derby-dev@db.apache.org>
Sent: Friday, May 13, 2005 = 6:56=20 AM
Subject: Re: Patch again for=20 DERBY-167.

> Hello.
>
> Daniel John = Debrunner=20 wrote:
>> Hard upgrade works currently, I checked in a manual = test=20 under
>> = java/testing/org/apache/derbyTesting/upgradeTests.
>=20
> Do you means that upgrade=3Dtrue option surely update = DD_Version in=20 database ?
> If so, I might mistake what happened at my = testing.
>=20
> Any way , I will check hardupgrade test again.
>
> =
> Best regards.
>
> /*
>=20
>         Tomohito=20 Nakayama
>         = tomonaka@basil.ocn.ne.jp
>         tomohito@rose.zero.ad.jp
>
>        =20 Naka
>         http://www5.ocn.ne.jp/~tomohito/TopPage.html
>
> */
> ----- Original = Message -----=20
> From: "Daniel John Debrunner" <djd@debrunners.com>
> To: "Derby Development" <derby-dev@db.apache.org>
> Sent: Friday, May 13, 2005 1:23 AM
> = Subject: Re:=20 Patch again for DERBY-167.
>
>
>> = TomohitoNakayama=20 wrote:
>>> = Hello.
>>>
>>>
>>> I=20 send new patch for DERBY-167.
>>> Please review it=20 again.
>>>
>>>
>>> I have one=20 question.
>>>
>>> There seems to be NO = implementation to=20 update externalized DD_Version.
>>> So now, hardupgrade does = not=20 works and we can't use BY DEFAULT  = .
>>>
>>> Should=20 it be implemented  in this task ?
>>>
>>> I = have=20 hesitation about updating version info myself = ....
>>
>> I=20 don't understand your question.
>>
>> In the previous = e-mails=20 I had thought that the only upgrade change
>> required was the=20 checkVersion if specifying BY = DEFAULT.
>>
>>
>> Hard=20 upgrade works currently, I checked in a manual test under
>>=20 java/testing/org/apache/derbyTesting/upgradeTests. It doesn't run = as
>>=20 part of the test harness and thius is not part of derbyall. This = is
>>=20 because it boots several JVMs sequentially with different class=20 paths
>> (e.g. old version and new version). There is a shell = script to=20 run the
>> test, runphases.ksh
>>
>>=20 Dan.
>>
>>
>>
>>
>>
>&= gt; --=20
>> No virus found in this incoming message.
>> = Checked by AVG=20 Anti-Virus.
>> Version: 7.0.308 / Virus Database: 266.11.9 - = Release=20 Date: 2005/05/12
>>
> ------=_NextPart_000_000A_01C55812.794CA950-- --=======AVGMAIL-4284B7E66C5C======= Content-Type: text/plain; x-avg=cert; charset=us-ascii Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-Description: "AVG certification" 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 --=======AVGMAIL-4284B7E66C5C=======--