Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-5961

Developer's guide mentions SQL state 40XL2 which is no longer used

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.9.1.0
    • Fix Version/s: 10.9.2.2, 10.10.1.1
    • Component/s: Documentation
    • Labels:
      None

      Description

      DERBY-5564 removed the SQL state 40XL2. Conditions that previously reported that SQL state, now report 40XL1. The old SQL state is still mentioned in the developer's guide: http://db.apache.org/derby/docs/dev/devguide/cdevconcepts32861.html

      1. DERBY-5961.diff
        0.7 kB
        Kim Haase
      2. cdevconcepts32861.html
        7 kB
        Kim Haase

        Issue Links

          Activity

          Hide
          knutanders Knut Anders Hatlen added a comment -

          Closing. Thanks, Kim!

          Show
          knutanders Knut Anders Hatlen added a comment - Closing. Thanks, Kim!
          Hide
          chaase3 Kim Haase added a comment -

          The fix has appeared in the Latest Alpha Manuals, so this issue could be closed.

          Show
          chaase3 Kim Haase added a comment - The fix has appeared in the Latest Alpha Manuals, so this issue could be closed.
          Hide
          chaase3 Kim Haase added a comment -

          Thanks, Knut!

          Committed DERBY-5961.diff to documentation trunk at revision 1403361.
          Merged to 10.9 docs branch at revision 1403376.

          Show
          chaase3 Kim Haase added a comment - Thanks, Knut! Committed DERBY-5961 .diff to documentation trunk at revision 1403361. Merged to 10.9 docs branch at revision 1403376.
          Hide
          knutanders Knut Anders Hatlen added a comment -

          Thanks, Kim, the patch looks good. +1 to commit.

          I agree that it's not important to backport this fix, as no real harm is done if an application checks for both of the SQL states.

          Show
          knutanders Knut Anders Hatlen added a comment - Thanks, Kim, the patch looks good. +1 to commit. I agree that it's not important to backport this fix, as no real harm is done if an application checks for both of the SQL states.
          Hide
          chaase3 Kim Haase added a comment -

          Attaching DERBY-5961.diff and cdevconcepts32861.html, with a small change to the "Programming applications to handle deadlocks" topic. I also fixed a font inconsistency.

          Show
          chaase3 Kim Haase added a comment - Attaching DERBY-5961 .diff and cdevconcepts32861.html, with a small change to the "Programming applications to handle deadlocks" topic. I also fixed a font inconsistency.
          Hide
          chaase3 Kim Haase added a comment -

          Thanks for noticing this, Knut. Since it's a fairly harmless error, I would guess there's no need to port a fix back farther than 10.9, though the fix to DERBY-5564 was ported back to 10.5. We're trying to keep 10.8 stable while preparing the 10.8.3 release, I think. If I should do a more complete backport, let me know.

          Show
          chaase3 Kim Haase added a comment - Thanks for noticing this, Knut. Since it's a fairly harmless error, I would guess there's no need to port a fix back farther than 10.9, though the fix to DERBY-5564 was ported back to 10.5. We're trying to keep 10.8 stable while preparing the 10.8.3 release, I think. If I should do a more complete backport, let me know.

            People

            • Assignee:
              chaase3 Kim Haase
              Reporter:
              knutanders Knut Anders Hatlen
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development