[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587682#action_12587682 ]
Tiago R. Espinha commented on DERBY-3574: ----------------------------------------- Thank you Kathey, that made my life much easier. Added a new patch with all the changes and some more fixes to comments. > 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 > Attachments: derby3574-blob-java.patch, derby3574-clob-java.patch, > derby3574-connection-java.patch, derby3574-lob-java.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.