Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <716874569.150451265726488194.JavaMail.jira@brutus.apache.org>
Date: Tue, 9 Feb 2010 14:41:28 +0000 (UTC)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4542) Avoid materialization where possible
 when cloning CollatorSQLClob
In-Reply-To: <769950135.123691265650347993.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-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Waagan updated DERBY-4542:
-----------------------------------

    Attachment: derby-4542-1a-avoid_materialization.diff

Attached a fix as patch 1a, which asks SQLClob to clone the value as long as materialization isn't forced.

Regression tests just started.
Patch ready for review.

> Avoid materialization where possible when cloning CollatorSQLClob
> -----------------------------------------------------------------
>
>                 Key: DERBY-4542
>                 URL: https://issues.apache.org/jira/browse/DERBY-4542
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions: 10.3.3.0, 10.4.2.0, 10.5.3.0, 10.6.0.0
>            Reporter: Kristian Waagan
>            Priority: Minor
>         Attachments: ClobCollationTest.java, derby-4477-workaround.diff, derby-4542-1a-avoid_materialization.diff
>
>
> Cloning a CollatorSQLClob results in always materializing the value. Since CLOBs can be very large, this should be avoided. There should now be sufficient functionality to do this, see SQLClob.

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