[ 
https://issues.apache.org/jira/browse/DERBY-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Øystein Grøvlen updated DERBY-2496:
-----------------------------------

    Attachment: blob-followup_v2.diff

> Rick Hillegas commented on DERBY-2496:
> --------------------------------------
> 
> Thanks for the changes, Øystein. I am afraid I'm having some
> trouble applying blob-followup.diff. My patch tool could not apply
> the changes in BlobLocatorInputStream. So I tried applying them by
> hand. I ended up with compile errors in Blob.java because:

Sorry about that.  I do not understand how I got that to compile.  I
have attached a new version of the patch, blob-followup_v2.diff where
I make sure to catch the SqlException.  I also updated my sandbox, so
hopefully you will be able to apply this version.


> Implement Blob support for Locators
> -----------------------------------
>
>                 Key: DERBY-2496
>                 URL: https://issues.apache.org/jira/browse/DERBY-2496
>             Project: Derby
>          Issue Type: Sub-task
>            Reporter: Øystein Grøvlen
>         Assigned To: Øystein Grøvlen
>         Attachments: blob-followup.diff, blob-followup_v2.diff, blob.diff, 
> blob_v2.diff
>
>
> 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.

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

Reply via email to