[DERBY-595] Using derby.language.logStatementText=true can mask certain exceptions and lead to incorrect behavior in some cases

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.2.1.6, 10.3.1.4
• Fix Version/s: 10.2.2.1, 10.3.1.4
• Component/s: SQL
• Environment: all
• Assignee: Mayuresh Nirhali
• Reporter: Sunitha Kambhampati
• Created: 02/Oct/05 11:26
• Updated: 05/Jul/10 17:12
• Resolved: 25/Apr/07 10:58

Description

Using derby.language.logStatementText=true can mask certain exceptions and lead to incorrect behavior.

I observed this with tests using streams, where if valid (expected) exceptions are raised when DVD.getString() is called, the exception gets eaten up when this property is set.

See
1)in GenericParameter.toString()
try
{
return value.getString();
}
catch (StandardException se)
{
return "unexpected exception from getString() - " + se;
}
}

2)in GenericPreparedStatement.execute(), where pvs.toString() is called for the parameters.
________

Reproduction: Run the test jdbcapi/resultsetStream.java , with derby.language.logStatementText=true and expected error exceptions wont be thrown for the error cases.

I looked at the tests that use streams , only the store/streamingColumn.java uses derby.language.logStatementText=true. I'll file another bug to resolve this test.