[
https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586867#action_12586867
]
Tiago R. Espinha commented on DERBY-3574:
-----------------------------------------
Okay, so what do we know at this point:
- Both my solution and Narayanan's don't work since they both rely on a free()
being invoked client-side, upon a commit(); . This would require for all the
Lobs to be stored in a list so that they could then be freed. Undesirable
solution.
- Knut's solution will most likely work. So unless someone objects to it, I
believe it is the way to go. Perhaps instead of a counter I'd create a new UUID
upon each commit, that would uniquely identify each transaction, but those are
implementation details.
> 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: 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.
