You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "David Van Couvering (JIRA)" <de...@db.apache.org> on 2006/08/04 23:20:14 UTC
[jira] Updated: (DERBY-1629) Exceptions thrown by code in
procedures or triggers are not handled/thrown correctly by Derby
[ http://issues.apache.org/jira/browse/DERBY-1629?page=all ]
David Van Couvering updated DERBY-1629:
---------------------------------------
Summary: Exceptions thrown by code in procedures or triggers are not handled/thrown correctly by Derby (was: StandardException.unexpectedUserException() does not correctly catch internally generated exceptions as of JDK 1.6)
> 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
> Reporter: David Van Couvering
> Priority: Minor
> Fix For: 10.2.0.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