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 "Kristian Waagan (JIRA)" <de...@db.apache.org> on 2006/08/22 12:07:15 UTC
[jira] Closed: (DERBY-598) Ensure that with
derby.language.logStatementText.true, values set by streams are not
materialized
[ http://issues.apache.org/jira/browse/DERBY-598?page=all ]
Kristian Waagan closed DERBY-598.
---------------------------------
Closing this. See previous comment by Sunitha.
> Ensure that with derby.language.logStatementText.true, values set by streams are not materialized
> -------------------------------------------------------------------------------------------------
>
> Key: DERBY-598
> URL: http://issues.apache.org/jira/browse/DERBY-598
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0
> Environment: all
> Reporter: Sunitha Kambhampati
> Fix For: 10.2.1.0
>
>
> Currently, running an app with derby.language.logStatementText=true , will print string representation of the parameter values. For values set by streams, it is not a good idea to do that - as for really large data , out of memory exceptions can occur as a result.
> Some placeholder for the stream or the hashcode/class name of the stream can be used instead to represent the parameter value.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira