--On 13. Oktober 2005 02:44:34 -0400 Chris Spencer
[EMAIL PROTECTED] wrote:
I understand that, but my point was when you call transaction.commit(),
you don't necessarily know what you're committing. One thread may be
ready to commit. Another may not be. If one thread calls
Chris Spencer wrote:
I understand that, but my point was when you call transaction.commit(),
you don't necessarily know what you're committing.
Yes you do, each thread has its own connection to the database, and this
connection has an independent view of the database from any other thread.
On 10/13/05, Chris Spencer [EMAIL PROTECTED] wrote:
I understand that, but my point was when you call transaction.commit(),
you don't necessarily know what you're committing. One thread may be
ready to commit. Another may not be. If one thread calls
transaction.abort(), they may be aborting
[Jeremy]
The default transaction manager maintains a separate
transaction for each thread. When you call
transaction.commit() from thread T1, it
commits the transaction for thread T1. It has no effect
on other thread's running transactions.
My apologies if this has been mentioned already
