Thanks, Lance. I understand the motivation for the method. My
question, is how do we respond to it. It appears like result sets are
closed if the severity of the exception is high enough, but that's not
what this API seems to be asking about it. It seems to ask if *any*
SQLException is a
Yep false is a winner here in this case.
David W. Van Couvering wrote:
Thanks, Lance. I understand the motivation for the method. My
question, is how do we respond to it. It appears like result sets are
closed if the severity of the exception is high enough, but that's not
what this API
David W. Van Couvering wrote:
That said, I am trying to answer the question to the new metadata call
autoCommitFailureClosesAllResultSets()
where the javadoc states
Retrieves whether a SQLException while autoCommit is true inidcates
that all open ResultSets are closed, even ones that
Hi, all (and especially Lance). I just ran this test:
- Create a statement that is scrollabe and read-only
- Execute a select on the statement
- Attempt to update the row, catch the exception
- Call rs.beforeFirst(). Looking at the embedded code, if the result
set is closed, this should cause
This method was added as various drivers and database vendors all do
this differently. In some cases autocommit is handled explictly by the
drivers themselves, not the backend.
autocommit has been very problematic over the years and somedays it
would be great it it never existed
