Dyre Tjeldvoll (JIRA) wrote:
Somehow I expected that you would say just that :) If you look closely you will see that
the issue was created with "Fix Version" 10.3.
Thanks Dyre for thinking ahead on this. My radar is on pure reflex.
Best I just try to shut the darn thing down for the nex
This has been a requirement since JDBC 1.0 and at there are no plans to
change this given the complexity of the autocommit issue with various
vendors. It is expected the applications that are well behaved will
know what mode they are in and invoke the correct methods.
-lance
Daniel John Debr
[
http://issues.apache.org/jira/browse/DERBY-1654?page=comments#action_12426941 ]
Dyre Tjeldvoll commented on DERBY-1654:
---
I think you are making a very good point. And I only discovered this because I
was trying to port an app developed w
[
http://issues.apache.org/jira/browse/DERBY-1654?page=comments#action_12426938 ]
Daniel John Debrunner commented on DERBY-1654:
--
I think the behaviour mandated by the spec is a useability problem. If I want
to write a generic metho
[
http://issues.apache.org/jira/browse/DERBY-1654?page=comments#action_12426936 ]
Dyre Tjeldvoll commented on DERBY-1654:
---
Somehow I expected that you would say just that :) If you look closely you will
see that the issue was created with
[
http://issues.apache.org/jira/browse/DERBY-1654?page=comments#action_12426932 ]
Kathey Marsden commented on DERBY-1654:
---
We might need to be careful with regard to existing appication impact on this
one. Is anyone planning on fixing thi
