XA is for distributed transactions which, as you correctly said, are not
supported by PostgreSQL. However, there is a fake XA implementation from
Exolab (which you can find under the CVS repo) that can be used (with some
minor modifications) as long as you can guarantee that the connections
participating in one single transaction are really from one single
_DataSource_ (ie. same host, same port, same database instance, same user
and of course no other database product in the same transaction).
I do not know what your needs are exactly and what tyres is useful for, but
most of the application servers (including the free ones: JBoss and HP-AS)
offer a way to use database without the optional XA JDBC interface.
Peter
> -----Original Message-----
> From: bala_tbn@yahoo.com [mailto:bala_tbn@yahoo.com]
> Sent: Thursday, March 07, 2002 10:14 AM
> To: pgsql-jdbc@postgresql.org
> Subject: [JDBC] Transactions?
>
>
> Hi,
> I have a basic question on JDBC for postgresql.
>
> Here's my scenario.
>
> 1) Start a transaction.
> 2) Get ONE OR MORE connections and perform operations(on
> different objects).
> 3) If anyone fails, rollback all the operations, else commit
> all the operations.
>
> I read that Postgresql doesn't support distributed transactions.
> But that is not a problem for me. We are having all the operations
> in the same database. Previously we were using EJB and Oracle and
> it was working fine. Now, we have plain Java(not EJB) and postgresql.
> So we thought of using some transaction managers like tyrex.
> But they ask for JDBC drivers which support transaction(XA, I think).
> I dont see any XA related files in JDBC driver I downloaded from
> site.(jdbc.postgresql.org).
>
> How to solve this problem?
>
> Regards,
> Balakrishnan.
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>