[
https://issues.apache.org/jira/browse/DERBY-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255009#comment-13255009
]
Kim Haase commented on DERBY-5505:
----------------------------------
Thanks for mentioning that performance issue, Kristian.
I think the information should be added to the "Prepared statements and
streaming columns" topic
(http://db.apache.org/derby/docs/dev/ref/rrefjavsqlprst.html). I notice that
the Java SE API docs (http://docs.oracle.com/javase/6/docs/api/) for
PreparedStatement.setAsciiStream et al. have the following note:
"Note: Consult your JDBC driver documentation to determine if it might be more
efficient to use a version of setAsciiStream which takes a length parameter."
I could add a note in the examples saying that we are using the 2-arg form for
simplicity, but if performance is an issue the 3-arg form may be preferable.
But we really need to say that in the rrefjavsqlprst topic. Do we have any
information to provide about the circumstances that might affect performance?
> BLOB and CLOB Reference Manual topics could use some fixes
> ----------------------------------------------------------
>
> Key: DERBY-5505
> URL: https://issues.apache.org/jira/browse/DERBY-5505
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.8.2.2
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Minor
> Attachments: DERBY-5505-2.diff, DERBY-5505-2.zip, DERBY-5505.diff,
> DERBY-5505.stat, DERBY-5505.zip, blobex.java, blobex.java, clobex.java,
> clobex.java, create.sql, fence.jpg, greentea.jpg, seeds.jpg
>
>
> The Reference Manual documentation on BLOBs and CLOBs has some gaps that I
> would like to fill as a result of my efforts to insert a BLOB into a table
> column. This should affect the following topics:
> CAST function (rrefsqlj33562.dita)
> CLOB data type (rrefclob.dita)
> BLOB data type (rrefblob.dita)
> A comment will provide further details.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
