Subject | Re: [IB-Architect] Firebird and java XA transaction support questions |
---|---|
Author | Jim Starkey |
Post date | 2001-05-22T18:35:15Z |
At 02:12 PM 5/22/01 -0400, David Jencks wrote:
transmission layers.
transactions with the various database handles and returns a
handle to the encapsulated stuff. At commit time it does the
appropriate song and dance.
If you want to do XA stuff, skip the isc_multi_transaction.
Jim Starkey
>Hi,No. The handle is officially opaque and in practice encapsulated by
>
>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?
>
transmission layers.
>2. Is it possible to add dbs to a transaction that is started but not yetThere is no magic with isc_start_multiple. It starts independent
>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?
>
transactions with the various database handles and returns a
handle to the encapsulated stuff. At commit time it does the
appropriate song and dance.
If you want to do XA stuff, skip the isc_multi_transaction.
>2.5 With a multi-db transaction, can you call commit on a differentAbsolutely not.
>connection/db handle than you started the transaction on?
>
>3. Am I correct in thinking that isc_prepare_transaction2 will allow me toI don't think so.
>store an externally generated xid for use in recovery?
>
Jim Starkey