[ http://issues.apache.org/jira/browse/DERBY-1382?page=all ]
Fernanda Pizzorno updated DERBY-1382:
-------------------------------------
Attachment: derby-1382.diff
derby-1382.stat
derby-1382-doc.diff
The attached patch (derby-1382.diff) fixes the implementation of LOBS so as to
make it also work for scrollable result sets. This has been done by only
clearing "extdtaPositions_" after checking that there is another row to parse
(NetCursor.calculateColumnOffsetsForRow_()), and clearing "extdtaPositions_"
and "extdtaData_" before retreiving new rows (ResultSet.flowGetRowset()). The
patch also adds tests for clobs and blobs to jdbcapi/blobclob4BLOB.java.
"extdtaPositions_": key = column position, value = index into extdtaData_
"extdtaData_": queue to hold EXTDTA data that hasn't been correlated to its
column #
Derby-1382-doc.diff removes
"Scrollable cursors (ResultSet.TYPE_SCROLL_SENSITIVE or
ResultSet.TYPE_SCROLL_INSENSITIVE) are not supported using the network client
if the result set contains LOB data. TYPE_FORWARD_ONLY must be specified for
result sets containing LOB data."
from the admin guide.
I have successfully run derbyall with this patch. Can someone please reveiw it?
> client: lobs fails silently with result sets of type TYPE_SCROLL_INSENSITIVE
> ----------------------------------------------------------------------------
>
> Key: DERBY-1382
> URL: http://issues.apache.org/jira/browse/DERBY-1382
> Project: Derby
> Type: Bug
> Components: JDBC, Network Client
> Versions: 10.1.1.0, 10.2.0.0, 10.1.2.0, 10.1.1.1, 10.1.1.2, 10.1.2.1,
> 10.1.3.0, 10.1.2.2, 10.1.2.3, 10.1.2.4
> Reporter: Dag H. Wanvik
> Assignee: Fernanda Pizzorno
> Fix For: 10.2.0.0
> Attachments: Main.java, derby-1382-doc.diff, derby-1382.diff, derby-1382.stat
>
> The documentation for 10.1
> (http://db.apache.org/derby/docs/10.1/adminguide/cadminappsclientdiffs.html)
> states:
> "Scrollable cursors (ResultSet.TYPE_SCROLL_SENSITIVE or
> ResultSet.TYPE_SCROLL_INSENSITIVE) are not supported using the
> network client if the result set contains LOB
> data. TYPE_FORWARD_ONLY must be specified for result sets containing
> LOB data."
> Unfortunately, this is not signalled when one tries to use it, it just fails
> silently,
> cf. repro program. Either this should be implemented, or we should throw a
> not implemented exception. For JDBC4 compliancy, it needs to be fixed, I
> think.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
