Yes, it's easy for data like this to slip through with the volume of
email on this list. I'm not sure how to resolve that, there's just
going to be some amount of lossiness in the system...
David
Myrna van Lunteren wrote:
On 8/1/06, David Van Couvering (JIRA) <derby-dev@db.apache.org> wrote:
[
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".
[snip]
Someone was going to get around to telling me that, right? :)
Actually, I did send a message wondering about this, but it was a
reply to one of the failure reports, you must've missed it.
http://www.nabble.com/Regression-Test-Failure%21---Derby-426908---Sun-DBTG-tf2026368.html#a5572398
:-)
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
