db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-2350) Use of XML values in the action statement of a trigger throw exceptions.
Date Tue, 31 Jul 2007 23:00:59 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Mike Matrigali resolved DERBY-2350.

       Resolution: Fixed
    Fix Version/s:

fixed in trunk and 10.3 branch.

Fix XML in triggers by changing code generation to generate different code
in the case of XML of the form when referencing old and new column values.:
CAST (org.apache.derby.iapi.db.Factory::
getString(<colPosition>) AS CLOB)

Also change XML.setValueFromResult() to validate the character stream and
set the xType as appropriate after parsing the stream.

> Use of XML values in the action statement of a trigger throw exceptions.
> ------------------------------------------------------------------------
>                 Key: DERBY-2350
>                 URL: https://issues.apache.org/jira/browse/DERBY-2350
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:
>            Reporter: Daniel John Debrunner
>            Assignee: Mike Matrigali
>             Fix For:
>         Attachments: d2350_v2.patch, derby-2350.diff
> A  trigger like, where V, V1 and V2 are columns of type XML will thrown an exception
when fired.
>                 REFERENCING NEW_TABLE AS N
>                 FOR EACH STATEMENT  
>                 INSERT INTO T_ACTION_STATEMENT(A, V1, ID, V2) 
>                 SELECT 'I', V, ID, V FROM N
> ERROR 38000: The exception 'java.sql.SQLException: An attempt was made to get a data
value of type 'java.lang.Object' from a data value of type 'XML'.' was thrown while evaluating
an expression.
> Most likely because triggers are implementing using VTIs and hence JDBC ResultSets and
XML is not supported through JDBC yet.
> TriggerTest shows this issue, see the comment with the bug number to reproduce.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message