Subject | Firebird and java XA transaction support questions |
---|---|
Author | David Jencks |
Post date | 2001-05-22T18:12:25Z |
Hi,
After spending several days looking at the source, experimenting with the
new jgds, and getting confused, I have some questions.
1. Is it possible to do work on the same transaction, in one db, through
more than one connection/dbhandle? If not, how hard is this to implement?
2. Is it possible to add dbs to a transaction that is started but not yet
prepared? ( I know this is a little like read committed transaction
isolation, but the java xa stuff only supports adding resources one at a
time to a transaction, not all at once like isc_start_transaction and
isc_start_multiple). Again, if not, how hard is this to implement?
2.5 With a multi-db transaction, can you call commit on a different
connection/db handle than you started the transaction on?
3. Am I correct in thinking that isc_prepare_transaction2 will allow me to
store an externally generated xid for use in recovery?
Many thanks
david jencks
After spending several days looking at the source, experimenting with the
new jgds, and getting confused, I have some questions.
1. Is it possible to do work on the same transaction, in one db, through
more than one connection/dbhandle? If not, how hard is this to implement?
2. Is it possible to add dbs to a transaction that is started but not yet
prepared? ( I know this is a little like read committed transaction
isolation, but the java xa stuff only supports adding resources one at a
time to a transaction, not all at once like isc_start_transaction and
isc_start_multiple). Again, if not, how hard is this to implement?
2.5 With a multi-db transaction, can you call commit on a different
connection/db handle than you started the transaction on?
3. Am I correct in thinking that isc_prepare_transaction2 will allow me to
store an externally generated xid for use in recovery?
Many thanks
david jencks