[DERBY-1629] Exceptions thrown by code in procedures or triggers are not handled/thrown correctly by Derby

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Fix Version/s: 10.3.1.4
• Component/s: JDBC, SQL
• Urgency: Normal
• Issue & fix info: Release Note Needed
• Bug behavior facts: Regression
• Assignee: Unassigned
• Reporter: David Van Couvering
• Created: 02/Aug/06 00:13
• Updated: 21/Jan/11 17:49
• Resolved: 24/May/07 20:49

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.

Issue Links

• relates to: DERBY-1729 Invoking Java stored procedure that contains GRANT or REVOKE statement with CONTAINS SQL should fail.
• relates to: DERBY-2545 testModifiesSql(org.apache.derbyTesting.functionTests.tests.lang.ProcedureInTriggerTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<3800[0]> but was:<3800[1]>