[
http://issues.apache.org/jira/browse/DERBY-1061?page=comments#action_12370067 ]
Kristian Waagan commented on DERBY-1061:
I tried the repro script with unpatched trunk, 'derby-1061_v2' diff and
'derby-1061-david.diff'. For me, running on Gentoo
[
http://issues.apache.org/jira/browse/DERBY-1061?page=comments#action_12370068 ]
Knut Anders Hatlen commented on DERBY-1061:
---
Committed revision 385291.
Anurag, please check if this solves the problem for you, and resolve/close the
issue if it
[
http://issues.apache.org/jira/browse/DERBY-1061?page=comments#action_12369741 ]
David Van Couvering commented on DERBY-1061:
In regards to your question of why not go to SQLException directly? the value
is that when you construct a
[
http://issues.apache.org/jira/browse/DERBY-1061?page=comments#action_12369744 ]
David Van Couvering commented on DERBY-1061:
OK, I see the issue, and I see what you're trying to do to solve it.
However, I think the better approach is to
[
http://issues.apache.org/jira/browse/DERBY-1061?page=comments#action_12369745 ]
David Van Couvering commented on DERBY-1061:
By the way, Anurag, thanks for catching this bug and making the effort to fix
it even though your fix to DERBY-1059
[
http://issues.apache.org/jira/browse/DERBY-1061?page=comments#action_12367992 ]
Anurag Shekhar commented on DERBY-1061:
---
runnning test case jdbcapi/connectionJdbc20.java exposes this bug
SqlException while fetching message results in recursive
[
http://issues.apache.org/jira/browse/DERBY-1061?page=comments#action_12367994 ]
Anurag Shekhar commented on DERBY-1061:
---
I didn't notice that SqlException doesn't extends from SQLException.
How about creating a SQLException in Sqlca itself with out
