Jim Archer <[EMAIL PROTECTED]> writes:
> I need to flag a record when it is updated or when it is a new insert.
> Then I SELECT for the changed records and do something not related to
> Postgres. Easy enough, I created a trigger procedure and fired it on
> INSERT OR UPDATE and modify NEW to set
L PROTECTED]
Sent by: cc:
[EMAIL PROTECTED]Subject: [GENERAL] How to know
a record has been updated, then reset the flag?
--On Thursday, November 18, 2004 3:15 PM +0900 Michael Glaesemann
<[EMAIL PROTECTED]> wrote:
Would it work to drop and readd the trigger within a transaction? Would
that make it multi-user safe? I can't think of another way to bypass an
update trigger.
I had that idea too, and I have no idea. :-(
On Nov 18, 2004, at 2:53 PM, Jim Archer wrote:
This is a multi-user environment, so I can't really drop the trigger
and readd it.
Would it work to drop and readd the trigger within a transaction? Would
that make it multi-user safe? I can't think of another way to bypass an
update trigger.
Mich
Hi All...
I'm been fighting this problem for a few days now, and it seems like it
should be simple. But the solution has eluded me so far...
I need to flag a record when it is updated or when it is a new insert.
Then I SELECT for the changed records and do something not related to
Postgres. E
