From: | Vatsal <vatsal(dot)avasthi(at)wipro(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
Cc: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Trigger within Transactions |
Date: | 2003-10-17 16:22:01 |
Message-ID: | 1066407747.5095.36.camel@M3-113824 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
I am back with one more query.
In my application, for notification purposes, i fire a trigger on table
informing the user about the change in table,
this works fine for atomic operations but not fit for compound
operations i.e. till the time a transaction successfully commits,
the trigger should not be fired or some mechanism should be there so
that we can buffer up fired triggers and pass it to the user at one go,
so that it looks likes a part of a transaction.
in short, how to make triggers transaction aware?
i saw similar questions on hackers list but couldnt get satisfying
reply,
please help
thanks in advance
regards
vatsal
**************************Disclaimer************************************
Information contained in this E-MAIL being proprietary to Wipro Limited is
'privileged' and 'confidential' and intended for use only by the individual
or entity to which it is addressed. You are notified that any use, copying
or dissemination of the information contained in the E-MAIL in any manner
whatsoever is strictly prohibited.
***************************************************************************
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2003-10-17 16:32:15 | Re: Cygwin? or paid version from SRA? |
Previous Message | Jan Poslusny | 2003-10-17 16:05:42 | Re: Perl and Postgres |