Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <25548166.1178195475731.JavaMail.jira@brutus>
Date: Thu, 3 May 2007 05:31:15 -0700 (PDT)
From: =?utf-8?Q?=C3=98ystein_Gr=C3=B8vlen_=28JIRA=29?= <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-2496) Implement Blob support for Locators
In-Reply-To: <6069414.1175082933159.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DERBY-2496?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

=C3=98ystein Gr=C3=B8vlen updated DERBY-2496:
-----------------------------------

    Attachment: blob-followup_v2.diff

Reattaching the patch since I forgot to grant license.

> Implement Blob support for Locators
> -----------------------------------
>
>                 Key: DERBY-2496
>                 URL: https://issues.apache.org/jira/browse/DERBY-2496
>             Project: Derby
>          Issue Type: Sub-task
>            Reporter: =C3=98ystein Gr=C3=B8vlen
>         Assigned To: =C3=98ystein Gr=C3=B8vlen
>         Attachments: blob-followup.diff, blob-followup_v2.diff, blob-foll=
owup_v2.diff, blob.diff, blob_v2.diff
>
>
> DERBY-2347 adds the possibility to send locators between client and serve=
r instead of LOB values.  This has not been activated yet, since the client=
 implementation does not currently support locators.  This report is for su=
pporting the locators for Blob objects.  Another JIRA issue will be made fo=
r 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 Locato=
r implementation cannot be exposed until everything has been done.  At leas=
t, doing just step 1, gives testing errors because tests use Blobs fetched =
from DB as parameters to prepared statements.   I would guess tests for upd=
atable result sets, needs the combination of 1. and 3.

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