Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
DERBY-2347 adds the possibility to send locators between client and server instead of LOB values. This has not been activated yet, since the client implementation does not currently support locators. This report is for supporting the locators for Blob objects. Another JIRA issue will be made for Clob.
This work will be made in several steps:
1. Blob methods and ResultSet.getXXX methods
2. PreparedStatement and CallableStatement methods
3. ResultSet.updateXXX methods
4. Connection.createBlob()
There is dependencies between these steps and it might be that the Locator implementation cannot be exposed until everything has been done. At least, doing just step 1, gives testing errors because tests use Blobs fetched from DB as parameters to prepared statements. I would guess tests for updatable result sets, needs the combination of 1. and 3.
Attachments
Attachments
Issue Links
- blocks
-
DERBY-2506 Adding the locator information to FD:OCA descriptor (FDODSC) andFD:OCA data (FDODTA) of the SQLDTA objects
- Closed
-
DERBY-2587 Connection.createClob() and Connection.createBlob() need to return locator support enabled LOB objects in the NetworkClient
- Closed
-
DERBY-2702 Enable Clob locator support between NetworkServer and NetworkClient and modify tests that experience changed behaviour due to this(enabling Clob Locators).
- Closed
- is part of
-
DERBY-208 Add support to retrieve lobs for Network Server by locator rather than matierializing the LOB
- Closed
- relates to
-
DERBY-6923 Passing a ClientClob or ClientBlob from another connection to an INSERT statement results in 'null' being written.
- Open