db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <j...@apache.org>
Subject [jira] Created: (DERBY-3098) LOB locks are not released after free().
Date Wed, 03 Oct 2007 07:42:51 GMT
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.3.1.4, 10.2.2.0
         Environment: Any
            Reporter: Øystein Grøvlen
            Assignee: Øystein Grøvlen


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.


Mime
View raw message