|Subject||Re: [Firebird-Java] Yet about (Jaybird 2.0.1 + JDBC 3.0) x 1.5.5|
> But, think about this: it's very normal in systems, not only mine but...as I said, I have not seen many systems that run in auto-commit mode.
> also other codes I see on Internet and developers, to use many
> Statements in the same Connection, without setting up the properties
> ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_READONLY and
> ResultSet.HOLD_CURSORS_OVER_COMMIT for each one. Then, imagine all these
> people changing these millions of code. I think this is a crazy way for
> many of them.
Even more, in most cases there is external transaction management and the
Java code runs in transaction. In this case this limitation does not apply.
But in order to help those that experience problems we will add the switch.
It does not come for free - the cost is memory.
> Then, SUN should think about this before changing the rules ofNot sure... One has to check previous versions of JDBC drivers of Oracle,
> development on each new version of specs, are you agree???
DB2, MS SQL Server and Sybase before making any conclusions. It might well
be that those drivers limited as written in the specification. Since I do
not know for sure, I can neither agree nor disagree :)