[jira] Updated: (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

["Kristian Waagan (JIRA)" <ji...@apache.org>]

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

Kristian Waagan updated DERBY-3574:
-----------------------------------

    Affects Version/s: 10.4.1.4
                       10.3.3.0
        Fix Version/s: 10.4.1.4

Updating affects and fix versions.
I plan to port this to the 10.4 branch, as it also fixes the bug reported as DERBY-3469.

> 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.3.3.0, 10.4.1.4, 10.5.0.0
>            Reporter: Kathey Marsden
>            Assignee: Tiago R. Espinha
>            Priority: Trivial
>             Fix For: 10.4.1.4, 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.