db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2529) Client PreparedStatement/CallableStatement implementations need to use locators
Date Tue, 24 Apr 2007 13:38:15 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491284

V.Narayanan commented on DERBY-2529:

I have been working on converting the following methods related to Blob to use locators.


setBlob and setObject are taken care of by the DRDA work done as part of
https://issues.apache.org/jira/browse/DERBY-2506. If the Blob object is
locator enabled then isLocator() would return true and the locator would
automatically be sent.

In the case of setBinaryStream, Layer B streaming is used to send the data
to the network server hence there is no significant performance improvement
in use a locator here to transfer the stream.

We neither need to change setBytes since in this case the overhead
of executing a stored procedure(BLOBCREATELOCATOR) to get a valid locator value,
then transferring the Bytes to the Blob(BLOBSETBYTES stored procedure) would
not be necessary when this can be done in one set of a Bytes transfer.

I expect a similar situation for Clob methods mentioned too.

I intend to close this JIRA as won't fix unless there is any objection
from the community.

> Client PreparedStatement/CallableStatement implementations need to use locators
> -------------------------------------------------------------------------------
>                 Key: DERBY-2529
>                 URL: https://issues.apache.org/jira/browse/DERBY-2529
>             Project: Derby
>          Issue Type: Sub-task
>            Reporter: V.Narayanan
>         Assigned To: V.Narayanan

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message