db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1629) Exceptions thrown by code in procedures or triggers are not handled/thrown correctly by Derby
Date Fri, 13 Apr 2007 17:40:15 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488725
] 

Myrna van Lunteren commented on DERBY-1629:
-------------------------------------------

When this gets fixed, the if (!JDBC.vmsupportsJDBC4) check in test lang/ProcedureInTriggerTest
should be removed.

> 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
>         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.


Mime
View raw message