Jon,
Thanks for the reply.
As i explained earlier, I am using java (via hibernate) to control the
overall transaction.
I cannot have begin/rollback statements for dblink_exec.
Only when the entire method call from java succeeds I want the transaction to
be commited.
I dont want a
rom: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of carty mc
Sent: Tuesday, April 01, 2008 6:56 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] dblink ,dblink_exec not participating in a Transaction??
Just to clarify few things in the above posting.
My Main DB Clien
e);
select * from log;
--you see a new row
select fn_test(true)
--ERROR: division by zero
select * from log;
--you see that a new row wasn't inserted.
Jon
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of carty mc
Sent: T
On Tue, Apr 1, 2008 at 7:56 PM, carty mc <[EMAIL PROTECTED]> wrote:
> In this case the updates that were made using dblink_exec are not getting
> rolled back in Database B.
And they won't be. dblink isn't transactional in that way. Your best
bet is to put all the data into one database and use
Just to clarify few things in the above posting.
My Main DB Client is java (using hibernate) which has Main Transaction
Manager.
This one controls the overall transaction
Work flow is as follows:
1)java program updates a table in Database A
2) As a result Trigger procedure defined for th
How I can make dblink to participate in transaction so that remote changes made
by dblink can only be committed if only local transaction succeds.
Here is my current scenario:
I am using two databases A & B. In Database A, I have trigger procedure
written for a Table . In this trigg
