db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tiago Aurélio Rodrigues Espinha (JIRA) <j...@apache.org>
Subject [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
Date Sat, 05 Apr 2008 20:03:24 GMT

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

Tiago Aurélio Rodrigues Espinha updated DERBY-3574:
---------------------------------------------------

    Attachment: derby-3574.patch

I believe this will fix the issue. The patch is just for Clob.java but the same has to be
done for Blob.java, I'll do it as soon as someone with more experience than me can confirm
if it's the correct way to do it.

I ran the test before and after, and it did pass with that change, but it's my first time
here so any guidance is appreciated.

> 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
>            Priority: Trivial
>         Attachments: derby-3574.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.


Mime
View raw message