[ http://issues.apache.org/jira/browse/DERBY-1629?page=comments#action_12425356 ] David Van Couvering commented on DERBY-1629: --------------------------------------------
I think what you described is in the SQL spec is not what is happening in this code right now, and should be fixed. And I think you're right that this does not require us to know whether the exception is a Derby exception or not, who knows, the procedure could be calling some other backend database. That simplifies things I think. > StandardException.unexpectedUserException() does not correctly catch > internally generated exceptions as of JDK 1.6 > ------------------------------------------------------------------------------------------------------------------ > > Key: DERBY-1629 > URL: http://issues.apache.org/jira/browse/DERBY-1629 > Project: Derby > Issue Type: Bug > Reporter: David Van Couvering > Priority: Minor > Fix For: 10.2.0.0 > > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
