[ http://issues.apache.org/jira/browse/DERBY-1616?page=comments#action_12424956 ] David Van Couvering commented on DERBY-1616: --------------------------------------------
Finally tracked down the source of this problem. I was very confused because the output files were showing "SQL Exception" while the code definitely sh owed it should be saying "java.sql.SQLException". Then I discovered that the .tmp files had the right output, whereas the .out files did not. It turns out that for JDK 6, because there are so many different *types* of exceptions, in Sed.java we have replaced the specific exception class name with "SQL Exception: ". I suspect this was to avoid having to have a different set of output files for JDK 6. Someone was going to get around to telling me that, right? :) Re-running derbyall, thanks for your patience. > Lots of jdk1.6 regression test failures with diffs because of SQL Exception > instead of java.sql.SQLException > ------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1616 > URL: http://issues.apache.org/jira/browse/DERBY-1616 > Project: Derby > Issue Type: Bug > Affects Versions: 10.2.0.0 > Environment: jdk16 /windows. > Reporter: Sunitha Kambhampati > Fix For: 10.2.0.0 > > Attachments: derbyall_report.txt > > > jdk16 derbyall derbyall: 19 failures > derbyall/derbyall.fail:lang/compressTable.sql > derbyall/derbyall.fail:lang/nestedCommit.sql > derbyall/derbyall.fail:lang/outparams.java > derbyall/derbyall.fail:lang/procedure.java > derbyall/derbyall.fail:lang/procedureInTrigger.sql > derbyall/derbyall.fail:tools/importExportThruIJ.sql > derbyall/derbyall.fail:tools/ieptests.sql > derbyall/derbyall.fail:tools/iepnegativetests.sql > derbyall/derbyall.fail:jdbcapi/statementJdbc20.java > derbyall/derbyall.fail:jdbcapi/statementJdbc30.java > derbyall/derbyall.fail:jdbcapi/parameterMapping.java > derbyall/derbyall.fail:i18n/iepnegativetests_ES.sql > > derbyall/derbynetclientmats/derbynetclientmats.fail:jdbc4/ClosedObjectTest.junit > > derbyall/derbynetclientmats/derbynetclientmats.fail:jdbc4/UnsupportedVetter.junit > > derbyall/derbynetclientmats/derbynetclientmats.fail:jdbc4/VerifySignatures.junit > derbyall/encryptionAll/encryption.fail:stress/stress.multi > derbyall/encryptionAll/storemats.fail:store/streamingColumn.java > derbyall/storeall/storeall.fail:store/TransactionTable.sql > derbyall/storeall/storemats.fail:store/streamingColumn.java -- 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
