[ https://issues.apache.org/jira/browse/DERBY-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494202 ]
Kristian Waagan commented on DERBY-595: --------------------------------------- Merged fix ('derby595_v2.diff') to 10.2 with revision 536104. Ran derbyall without failures (1.6). > Using derby.language.logStatementText=true can mask certain exceptions and > lead to incorrect behavior in some cases > ------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-595 > URL: https://issues.apache.org/jira/browse/DERBY-595 > Project: Derby > Issue Type: Bug > Components: SQL > Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.2.1.6, 10.3.0.0 > Environment: all > Reporter: Sunitha Kambhampati > Assigned To: Mayuresh Nirhali > Fix For: 10.2.3.0, 10.3.0.0 > > Attachments: derby595.diff, derby595_v2.diff > > > 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. - You can reply to this email to add a comment to the issue online.