Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <4432661.1184681524626.JavaMail.jira@brutus>
Date: Tue, 17 Jul 2007 07:12:04 -0700 (PDT)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2789) DatabaseMetaData
 .locatorsUpdateCopy() should return true
In-Reply-To: <8216343.1181304805857.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-2789?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513252 ]=20

Dag H. Wanvik commented on DERBY-2789:
--------------------------------------

I notice that for a 10.2 client, when running with a 10.3 server, the
answer is still wrong, because the value is hardcoded in the client
(am.DatabaseMetaData#locatorsUpdateCopy). So a fix for 10.2 client
 should be easy.


> DatabaseMetaData .locatorsUpdateCopy() should return true
> ---------------------------------------------------------
>
>                 Key: DERBY-2789
>                 URL: https://issues.apache.org/jira/browse/DERBY-2789
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.2.2.0
>         Environment: Any
>            Reporter: =C3=98ystein Gr=C3=B8vlen
>            Assignee: =C3=98ystein Gr=C3=B8vlen
>             Fix For: 10.3.0.0
>
>         Attachments: derby-2789.diff, derby-2789.stat
>
>
> Since updates made to a BLOB or CLOB value in Derby is made on a copy, Da=
tabaseMetaData .locatorsUpdateCopy() call should return true.  For the embe=
dded driver the functionality to update a LOB value is new in 10.3. For the=
 client driver, updates have been possible in prior releases, and locatorsU=
pdateCopy() has returned false.  That behavior was wrong since the client u=
pdated a main-memory copy, not the values in the database.  For 10.3, the c=
lient will use a locator based implementation which will rely on the behavi=
or of the embedded driver.  Hence, locatorsUpdateCopy() should return true =
in both cases.

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