You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2012/10/02 07:25:08 UTC
[jira] [Updated] (DERBY-2465) Clob data type should use
getCharacterStream() to read a column data from a VTI instead of
getString().
[ https://issues.apache.org/jira/browse/DERBY-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamta A. Satoor updated DERBY-2465:
-----------------------------------
Urgency: Normal
Labels: CLOB derby_triage10_10 (was: CLOB)
> Clob data type should use getCharacterStream() to read a column data from a VTI instead of getString().
> ---------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2465
> URL: https://issues.apache.org/jira/browse/DERBY-2465
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.3.1.4
> Reporter: Suresh Thalamati
> Labels: CLOB, derby_triage10_10
> Attachments: derby2465_v1.diff, derby.log
>
>
> Currently clob data is read as String. This can consume lot of memory when lot
> of rows read from a VTI resultset. I think it would consume less memory if
> data is read using streams.
> org.apache.derby.iapi.types.SQLClob.java does not implement
> setValueFromResultSet() that is used by the VTI to read the data, it defaults
> to super class SQLChar.java implementation, which reads the data using
> getString().
> One case I noticed the current implementation uses lot of memory is when doing import of clobs(DERBY-378).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira