[ http://issues.apache.org/jira/browse/DERBY-595?page=comments#action_12461512 ] Bryan Pendleton commented on DERBY-595: ---------------------------------------
I notice that DERBY-1693 has added a getTraceString() method to DataValueDescriptor. Does that make it easier to fix this bug? Could we, for example, arrange it so that exceptions from getTraceString were safe to swallow in the logging code, but exceptions from getString would still show through to the user? > Using derby.language.logStatementText=true can mask certain exceptions and > lead to incorrect behavior in some cases > ------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-595 > URL: http://issues.apache.org/jira/browse/DERBY-595 > Project: Derby > Issue Type: Bug > Components: SQL > Affects Versions: 10.0.2.0, 10.1.1.0, 10.0.2.1 > Environment: all > Reporter: Sunitha Kambhampati > > 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. -- 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
