db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3741) SQL LENGTH function materializes CLOB into memory
Date Mon, 04 Aug 2008 15:58:44 GMT

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

Kathey Marsden updated DERBY-3741:

    Attachment: derby-3741_multibyteclobtest_update_diff.txt

I am attaching a patch that makes a  couple minor modifiications to the test.  It changes
the pageCacheSize to 100 so the test can be run with low memory configurations and it also
changes the test to check the contents of the stream when it reads it back in.    I'd go ahead
and commit this change, but one thing I noticed was that the client test for the large clob
seems really slow. 525000ms vs 9578ms  for embedded.  So the test will add about 9 minutes
to the suite.   Two  questions:

1) Is there a client bug logged that would explain the extreme difference?
2) Is it acceptable to check in this test since it adds so much time to suites.All. One option
to shorten the run is to only run for embedded.  For this bug we are mostly testing that LENGTH
 is returning the right value for multibyte characters and not consuming too much memory,
so for that an embedded run would have us covered.

> SQL LENGTH function materializes CLOB into memory
> -------------------------------------------------
>                 Key: DERBY-3741
>                 URL: https://issues.apache.org/jira/browse/DERBY-3741
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:,,
>            Reporter: Kathey Marsden
>            Assignee: Suran Jayathilaka
>         Attachments: ClobMemTest.java, derby-3741-1.diff, derby-3741-2.diff, derby-3741-multibyte_test.diff,
derby-3741_multibyteclobtest_update_diff.txt, LargeLengthClob.zip
> Similar to DERBY-3732, the SQL LENGTH function also materializes CLOB's into memory.
 See attached repro.

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

View raw message