[
https://issues.apache.org/jira/browse/DERBY-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-284:
----------------------------------
Urgency: Low
Labels: derby_triage10_11 (was: )
> Show warning message , if hard upgrade was not executed because upgrade=true
> was designated on or after 2nd connection.
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-284
> URL: https://issues.apache.org/jira/browse/DERBY-284
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Reporter: Tomohito Nakayama
> Priority: Trivial
> Labels: derby_triage10_11
>
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
