The JayBird java driver for firebird provides jta-based xa transaction
support, normally used via the jta transaction manager in an app server.
(recovery hasn't been tested extensively, but is there).

The transaction log format used by the internal firebird transaction
manager is not IMO very compatible with external transaction management:
the JayBird driver uses its own format. I suspect this is the reason the
sql prepare is missing.

You can already do multi-firebird-db transactions with 2pc using the
internal firebird transaction manaager.

If you do the 2pc commit protocol using sql rather than a transaction
manager, how will you recover from failures?

david jencks

On 2002.12.03 04:28:26 -0500 David Garamond wrote:
> i'm looking at the ib 6.0 sql reference manual the other day and noticed
> that there's no sql command like "PREPARE COMMIT" or "PREPARE
> TRANSACTION" (which will be an interface to
> isc_prepare_transaction[2]()). would it be a good idea to provide a sql
> interface to this API function? i would very much like to utilize
> IB/FB's ability to do 2-phase commit with other databases/external
> transaction mechanisms.
>
> --
> dave
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>
>