Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <606730238.175571265795307876.JavaMail.jira@brutus.apache.org>
Date: Wed, 10 Feb 2010 09:48:27 +0000 (UTC)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Resolved: (DERBY-4543) CLOB values incorrectly stored on
 disk using the old header format
In-Reply-To: <1335471441.147271265712928074.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kristian Waagan resolved DERBY-4543.
------------------------------------

          Resolution: Fixed
    Issue & fix info:   (was: [Patch Available])

Committed patch 1a to trunk with revision 908418.
I don't expect more work on this issue, unless something pops up during review.

> CLOB values incorrectly stored on disk using the old header format
> ------------------------------------------------------------------
>
>                 Key: DERBY-4543
>                 URL: https://issues.apache.org/jira/browse/DERBY-4543
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Store
>    Affects Versions: 10.6.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>             Fix For: 10.6.0.0
>
>         Attachments: derby-4543-1a-clob_hdr_format_fix.diff
>
>
> The logic determining whether CLOB values should be stored using the old (pre 10.5) or the new header format has two bugs, which sometimes causes the old format to be used even though the new one should be used.
> The naming of the relevant methods are also problematic, as we're not really interested in whether we are in soft-upgrade mode or not. If you soft-upgrade from 10.5 to 10.6, the new header format should still be used.
> The consequences of these bugs are potential loss of performance for certain operations on CLOB values and in some cases it might cause a crash if the source stream cannot be rewinded/reset.

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