db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4542) Avoid materialization where possible when cloning CollatorSQLClob
Date Tue, 09 Feb 2010 14:41:28 GMT

     [ 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:,,,
>            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.

View raw message