db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2496) Implement Blob support for Locators
Date Fri, 08 Jun 2007 05:25:26 GMT

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

Myrna van Lunteren commented on DERBY-2496:
-------------------------------------------

This issue needs a releasenote.
Also, a decision/action re SuicideOfStreamingTest is pending.

Can the check for invalid locator with getNextException() and getSQLState() be implemented
before 6/14? Does it need to be?
If not, please make a separate issue so this can be closed...


> Implement Blob support for Locators
> -----------------------------------
>
>                 Key: DERBY-2496
>                 URL: https://issues.apache.org/jira/browse/DERBY-2496
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Network Client, Network Server
>            Reporter: Øystein Grøvlen
>            Assignee: Øystein Grøvlen
>             Fix For: 10.3.0.0
>
>         Attachments: blob-followup.diff, blob-followup_v2.diff, blob-followup_v2.diff,
blob.diff, blob_v2.diff, blobtestfix.diff, enableblobloc.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.


Mime
View raw message