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

Exceptions thrown by code in procedures or triggers are not handled/thrown correctly by Derby

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: 10.3.1.4
    • Component/s: JDBC, SQL
    • Labels:
      None
    • Urgency:
      Normal
    • Issue & fix info:
      Release Note Needed
    • Bug behavior facts:
      Regression

      Description

      In Java SE 6 runtime environments, an application may not get the SQL Exception with SQL State 38000 when execution of a trigger or procedure fails with an exception caused by Derby internals. Instead, they will get the underlying exception with it's SQL State. For an example of this, see lang/procedureInTrigger.sql, which has different output for Java SE 6 (encoded in the master/jdk16/procedureInTrigger.out file) than for other Java SE runtimes.

        Attachments

        1. DERBY-1629_j9canon.diff
          0.9 kB
          Myrna van Lunteren

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                davidvc David Van Couvering
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: