[
https://issues.apache.org/jira/browse/DERBY-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532065
]
Knut Anders Hatlen commented on DERBY-3098:
-------------------------------------------
Hi Øystein,
The patch looks correct to me and the test plan also sounds good. I'm just
wondering how this works when the transaction isolation level is READ
UNCOMMITTED. Will a reader have to wait if another transaction has locked a
large lob exclusively, but not if the lob is small?
> LOB locks are not released after free().
> ----------------------------------------
>
> Key: DERBY-3098
> URL: https://issues.apache.org/jira/browse/DERBY-3098
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.2.2.0, 10.3.1.4
> Environment: Any
> Reporter: Øystein Grøvlen
> Assignee: Øystein Grøvlen
> Attachments: derby-3098fix.diff
>
>
> When getBlob/getClob is called on the ResultSet, the current row is
> locked if the JDBC driver does not cache the entire LOB value in
> memory. This is done to prevent the Blob/Clob object from being
> changed. Until now, this lock has been held to the end of the
> transaction.
> JDBC4 introduced free() methods for the Blob/Clob class. The locking
> should be changed so that the locks is releases when the Blob/Clob
> object is freed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
