[DERBY-1341] LOB set method(s) are currently no supported, but part of the Java 1.4 JDBC interface

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.0.2.0, 10.0.2.1, 10.0.2.2, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.3.1.4
• Fix Version/s: 10.3.1.4
• Component/s: JDBC
• Environment: all
• Urgency: Normal
• Issue & fix info: Release Note Needed
• Assignee: Anurag Aggarwal
• Reporter: Keith McFarlane
• Created: 23/May/06 18:38
• Updated: 25/May/10 09:44
• Resolved: 13/Jun/07 16:11

Description

JDBC LOB . getBtypes methods are not implemented in any Derby version to date: there is a "place-holder" method that throws a SQLException reporting that the methods are not implemented.

It would be excellent to have any efficient Derby implementation of the getBytes LOB methods that provide "random-access" to the binary // character content of database large objects. The specific context is implementing a Lucene Directory interface that stores indexing data (index files) and other binary data in a local encrypted Derby instance.

A work around is to write an encrypted RandomAccessFile implementation as a file-sdystem buffer, perhaps writing to the database on closure. An efficient Derby implementation of LOB . getBytes would avoid this an make for a clean design. I can think of several reasons why random-access to LOBs would be valuable in a "hostile" client environment.

Issue Links

• incorporates: DERBY-2730 Implement not implemented Embedded methods Blob.getBinaryStream(long pos, long length) and Clob. getCharacterStream(long pos, long length)
• is related to: DERBY-1615 Rewrite the Clob implementation in the client driver

Sub-Tasks

• provide set methods for blob in embeded driver: Closed
• Provide set methods for clob for embedded driver: Closed
• provide encryption support for temporary files used by lob if the data base is encrypted: Closed
• Cleanup of Clob control/support structures: Closed
• Implement Clob.truncate for embedded driver: Closed