db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-284) Show warning message , if hard upgrade was not executed because upgrade=true was designated on or after 2nd connection.
Date Wed, 17 Aug 2005 00:43:54 GMT
     [ http://issues.apache.org/jira/browse/DERBY-284?page=all ]

Mike Matrigali updated DERBY-284:
---------------------------------

      Component: JDBC
    Description: 
Show warning message , 
if hard upgrade was not executed.
This happens when upgrade=true was designated on or after 2nd connection.


In the mail of "Re: upgrading trouble ... (Re: Patch again for DERBY-167.)",
Daniel John Debrunner wrote:

> The upgrade=true has to be set on the connection that boots the
> database, the first connection to the database. In your example where
> you use update=true, that booted the old database in soft upgrade mode.
> Hard upgrade did not happen because the connection with the correct
> upgrade=true was not the first so it was a normal connection to the
> database.
> 
> A warning if the upgrade has no effect might be a good idea, either
> no-upgrade required or upgrade on booted database not possible.
> 
> Dan.



  was:
Show warning message , 
if hard upgrade was not executed.
This happens when upgrade=true was designated on or after 2nd connection.


In the mail of "Re: upgrading trouble ... (Re: Patch again for DERBY-167.)",
Daniel John Debrunner wrote:

> The upgrade=true has to be set on the connection that boots the
> database, the first connection to the database. In your example where
> you use update=true, that booted the old database in soft upgrade mode.
> Hard upgrade did not happen because the connection with the correct
> upgrade=true was not the first so it was a normal connection to the
> database.
> 
> A warning if the upgrade has no effect might be a good idea, either
> no-upgrade required or upgrade on booted database not possible.
> 
> Dan.



    Environment: 

> Show warning message , if hard upgrade was not executed  because upgrade=true was designated
on or after 2nd connection.
> ------------------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-284
>          URL: http://issues.apache.org/jira/browse/DERBY-284
>      Project: Derby
>         Type: Improvement
>   Components: JDBC
>     Reporter: Tomohito Nakayama
>     Priority: Trivial

>
> Show warning message , 
> if hard upgrade was not executed.
> This happens when upgrade=true was designated on or after 2nd connection.
> In the mail of "Re: upgrading trouble ... (Re: Patch again for DERBY-167.)",
> Daniel John Debrunner wrote:
> > The upgrade=true has to be set on the connection that boots the
> > database, the first connection to the database. In your example where
> > you use update=true, that booted the old database in soft upgrade mode.
> > Hard upgrade did not happen because the connection with the correct
> > upgrade=true was not the first so it was a normal connection to the
> > database.
> > 
> > A warning if the upgrade has no effect might be a good idea, either
> > no-upgrade required or upgrade on booted database not possible.
> > 
> > Dan.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message