db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-5162) CLOB INOUT arg set to NULL by procedure does not preserve NULL value when re-invoked
Date Tue, 29 Mar 2011 22:59:05 GMT

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

Rick Hillegas resolved DERBY-5162.
----------------------------------

          Resolution: Fixed
       Fix Version/s: 10.8.0.0
    Issue & fix info: [Repro attached]  (was: [Repro attached, Patch Available])

Tests passed cleanly except for known Heisenbugs. Committed derby-5162-01-aa-restoreToNull.diff
at subversion revision 1086798.

> CLOB INOUT arg set to NULL by procedure does not preserve NULL value when re-invoked
> ------------------------------------------------------------------------------------
>
>                 Key: DERBY-5162
>                 URL: https://issues.apache.org/jira/browse/DERBY-5162
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, SQL
>    Affects Versions: 10.8.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>             Fix For: 10.8.0.0
>
>         Attachments: derby-5162-01-aa-restoreToNull.diff, z.java
>
>
> If a procedure sets an INOUT CLOB arg to NULL and is then re-invoked, the NULL is not
preserved. Instead, the procedure sees the same CLOB that it saw in the last invocation. This
bug was disclosed during the testing of the fix for DERBY-2515. I will attach a repro.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message