Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1991764049.1228994386623.JavaMail.jira@brutus>
Date: Thu, 11 Dec 2008 03:19:46 -0800 (PST)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Resolved: (DERBY-3978) Clob.truncate(long) in the client
 driver doesn't update the cached Clob length
In-Reply-To: <1394791479.1228744964319.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kristian Waagan resolved DERBY-3978.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.3.1

Regression tests on the 10.3 branch ran successfully.
Backported with revision 725662.

This concludes the work on this issue. Awaiting confirmation from test runs before closing.

> Clob.truncate(long) in the client driver doesn't update the cached Clob length
> ------------------------------------------------------------------------------
>
>                 Key: DERBY-3978
>                 URL: https://issues.apache.org/jira/browse/DERBY-3978
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>    Affects Versions: 10.3.3.0, 10.4.2.0, 10.5.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>             Fix For: 10.3.3.1, 10.4.2.1, 10.5.0.0
>
>         Attachments: derby-3978-1a-regression_tests.diff, derby-3978-2a-update_length.diff
>
>
> The client driver caches the Clob length, but doesn't update it when Clob.truncate is called.
> I will attach a few regression tests, where one of them demonstrates the issue. The fix is also very simple; update the cached length.

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