[
https://issues.apache.org/jira/browse/DERBY-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan closed DERBY-1341.
----------------------------------
Closing issue.
> LOB set method(s) are currently no supported, but part of the Java 1.4 JDBC
> interface
> -------------------------------------------------------------------------------------
>
> Key: DERBY-1341
> URL: https://issues.apache.org/jira/browse/DERBY-1341
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 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
> Environment: all
> Reporter: Keith McFarlane
> Assignee: Anurag Shekhar
> Fix For: 10.3.1.4
>
> Attachments: derby-1341-blob-forreview.diff, derby-1341.diff,
> LobStreamTest.java, releaseNote.html, releaseNote.html, releaseNote.html,
> releaseNotes-v2.html, releaseNotes.html
>
>
> 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.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
