[DERBY-284] Show warning message , if hard upgrade was not executed because upgrade=true was designated on or after 2nd connection.

• Type: Improvement
• Status: Open
• Priority: Trivial
• Resolution: Unresolved
• Component/s: JDBC
• Labels: derby_triage10_11
• Urgency: Low
• Assignee: Unassigned
• Reporter: Tomohito Nakayama
• Created: 14/May/05 07:42
• Updated: 18/Jul/13 17:40

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.

Issue Links

• is duplicated by: DERBY-4254 If upgrade is not performed when connecting with the upgrade=true atribute is specified, Derby should produce a warning
• is part of: DERBY-5970 Check that connection attributes have legal values.