db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2789) DatabaseMetaData .locatorsUpdateCopy() should return true
Date Tue, 17 Jul 2007 14:12:04 GMT

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

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:
>         Environment: Any
>            Reporter: Øystein Grøvlen
>            Assignee: Øystein Grøvlen
>             Fix For:
>         Attachments: derby-2789.diff, derby-2789.stat
> Since updates made to a BLOB or CLOB value in Derby is made on a copy, DatabaseMetaData
.locatorsUpdateCopy() call should return true.  For the embedded 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 locatorsUpdateCopy() has returned false.  That behavior was wrong since
the client updated a main-memory copy, not the values in the database.  For 10.3, the client
will use a locator based implementation which will rely on the behavior of the embedded driver.
 Hence, locatorsUpdateCopy() should return true in both cases.

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

View raw message