db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suran Jayathilaka (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3741) SQL LENGTH function materializes CLOB into memory
Date Mon, 11 Aug 2008 19:02:46 GMT

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

Suran Jayathilaka updated DERBY-3741:

    Attachment: derby.log

Attaching derby.log file from the failed tests. This file is from the 

Before running the test, I had cleaned the tests folder.

I used the following commands to run the tests.

set CLASSPATH=..\classes;..\tools\java\junit.jar;..\tools\java\jakarta-oro-2.0.8.jar
java -XX:MaxPermSize=128M -Xmx1024M -Xms512M -Dderby.tests.trace=true junit.textui.TestRunner

> 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-mergeto-10.4.diff,
derby-3741-multibyte_test.diff, derby-3741_multibyteclobtest_update_diff.txt, derby.log, 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