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 "Tiago R. Espinha (JIRA)" <ji...@apache.org> on 2008/04/15 22:56:21 UTC

[jira] Resolved: (DERBY-3574) With client, attempting to get the lob length after commit or connection close if there was a call to length() before commit does not throw an exception

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

Tiago R. Espinha resolved DERBY-3574.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.5.0.0

Issue resolved. Final revision regarding this issue: 648409 .

> With client, attempting to get the lob length after commit  or connection close if there  was a call to length() before commit does not throw an exception
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3574
>                 URL: https://issues.apache.org/jira/browse/DERBY-3574
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client, Newcomer
>    Affects Versions: 10.5.0.0
>            Reporter: Kathey Marsden
>            Assignee: Tiago R. Espinha
>            Priority: Trivial
>             Fix For: 10.5.0.0
>
>         Attachments: derby3574-testfix.patch, derby3574-testfix.patch, derby3574-wtest.patch, derby3574.patch, TestLobLength.java
>
>
> Attempting to get call Blob/Clob.length() after commit or connection close does not fail if there was a previous call to length().  If no previous call was made an exception is thrown as expected.
> See attached program TestLobLength for repro with commit.  If you comment out the two lines to get the length before the commit we get the expected exception.

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