[ http://issues.apache.org/jira/browse/DERBY-1629?page=comments#action_12440571 ] Daniel John Debrunner commented on DERBY-1629: ----------------------------------------------
I think there may be a correction to the SQL spec for the correct way to handle exceptions. I don't have the details, just saw it while I was searching for something else. The correction is in an official SQL standard correction document which modifies the text in SQL Part 13 which itself modifies the SQL/Foundation spec. Thus it's sometimes confusing to realise what exactly is expected :-) > Exceptions thrown by code in procedures or triggers are not handled/thrown > correctly by Derby > --------------------------------------------------------------------------------------------- > > Key: DERBY-1629 > URL: http://issues.apache.org/jira/browse/DERBY-1629 > Project: Derby > Issue Type: Bug > Components: JDBC, SQL > Reporter: David Van Couvering > Priority: Minor > Fix For: 10.2.2.0 > > Attachments: DERBY-1629_j9canon.diff > > > 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
