| Key: |
DERBY-598
|
| Type: |
Improvement
|
| Status: |
Closed
|
| Resolution: |
Duplicate
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Sunitha Kambhampati
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
all
|
|
Issue Links:
|
Duplicate
|
|
|
|
This issue is duplicated by:
|
|
DERBY-1693
Out of Memory Error with derby.language.logStatementText=true
|
|
|
|
|
|
|
| Urgency: |
Normal
|
| Resolution Date: |
17/Aug/06 04:41 PM
|
|
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.
|
|
Description
|
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. |
Show » |
|
Ensure that with derby.language.logStatementText.true, values set by streams are not materialized
DERBY-1693is a duplicate of this issue. But since there is more discussion on derby-1693, marking this as duplicate.