Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 39098 invoked from network); 9 Feb 2010 15:01:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Feb 2010 15:01:50 -0000 Received: (qmail 16490 invoked by uid 500); 9 Feb 2010 15:01:49 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 16428 invoked by uid 500); 9 Feb 2010 15:01:49 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 16420 invoked by uid 99); 9 Feb 2010 15:01:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Feb 2010 15:01:49 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Feb 2010 15:01:48 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id C7D6929A0014 for ; Tue, 9 Feb 2010 07:01:28 -0800 (PST) Message-ID: <92409624.150561265727688817.JavaMail.jira@brutus.apache.org> Date: Tue, 9 Feb 2010 15:01:28 +0000 (UTC) From: "Kristian Waagan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-4543: ----------------------------------- Issue & fix info: [Patch Available] > 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.