db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: [jira] Updated: (DERBY-898) setAutoCommit(false) is not working properly for local connection with ClientXADataSource
Date Fri, 03 Feb 2006 21:28:38 GMT
Bryan Pendleton wrote:

> Is this something specific to XA distributed transactions, or is it
> just a
> fundamental aspect of how the Network Server behaves that all transaction
> control should be performed by the client?
>
It is the same for all connections. The transactional control is
performed by the client.
The server side connection is always autocommit false, but  in
XADatabase.java  it was not being set properly as it is in Database.java.


I think that we could probably see a significant performance 
improvement if autocommit is true if we switched to a different model
and sent an EXCSQLSET command of some sort with setAutoCommit(),  This
would be similar to Oyvind's implemetnation for setQueryTimeout.  Right
now,  with autocommit true there is an extra round trip to the server
with each statement, because the client has to send the statement
followed by the commit. Of course we would need to take care to do the
right thing for older clients.

Kathey









Mime
View raw message