[
https://issues.apache.org/jira/browse/DERBY-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Øystein Grøvlen resolved DERBY-1629.
------------------------------------
Resolution: Duplicate
Fix Version/s: 10.3.0.0
It seems like this issue is a duplicate of DERBY-1440. At least, Knut Anders
patch removes the check in lang/ProcedureInTriggerTest here mention by Myrna,
and which seems to fit the original description of the problem. I am not quite
sure I understand all the comments made on this JIRA, and whether there are
other issues here, but since the original problem seems to be solved, I suggest
this JIRA should be closed.
> Exceptions thrown by code in procedures or triggers are not handled/thrown
> correctly by Derby
> ---------------------------------------------------------------------------------------------
>
> Key: DERBY-1629
> URL: https://issues.apache.org/jira/browse/DERBY-1629
> Project: Derby
> Issue Type: Bug
> Components: JDBC, SQL
> Reporter: David Van Couvering
> Priority: Minor
> Fix For: 10.3.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.
-
You can reply to this email to add a comment to the issue online.
