Derby
  1. Derby
  2. DERBY-284

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

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Trivial Trivial
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: JDBC
    • Urgency:
      Low

      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

          Activity

          Mamta A. Satoor made changes -
          Labels derby_triage10_11
          Urgency Low [ 10053 ]
          Gavin made changes -
          Workflow jira [ 42599 ] Default workflow, editable Closed status [ 12802422 ]
          Knut Anders Hatlen made changes -
          Link This issue is duplicated by DERBY-4254 [ DERBY-4254 ]
          Knut Anders Hatlen made changes -
          Link This issue is part of DERBY-5970 [ DERBY-5970 ]
          Mike Matrigali made changes -
          Component/s JDBC [ 11407 ]
          Environment
          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.

          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.

          Tomohito Nakayama made changes -
          Field Original Value New Value
          Priority Major [ 3 ] Trivial [ 5 ]
          Tomohito Nakayama created issue -

            People

            • Assignee:
              Unassigned
              Reporter:
              Tomohito Nakayama
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development