Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Audit Trigger puzzler
- From: David Kerr <dmk(at)mr-paradox(dot)net>
- To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
- Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
- Subject: Re: Audit Trigger puzzler
- Date: Mon, 31 Aug 2009 08:48:24 -0700
- Message-id: <20090831154824.GC87434@mr-paradox.net> <text/plain>
On Fri, Aug 28, 2009 at 08:07:40PM +0100, Simon Riggs wrote: - - On Fri, 2009-08-28 at 08:50 -0700, David Kerr wrote: - - > so, is there a way in a trigger to know if edited_by is expressly - > being set in the update statement? it seems like if I can know that, - > then i should be able to figure it out. - - No, but you could use a before trigger to reset the value to NULL prior - to each update, then your after trigger would work. hmm, that's probably not worth it. fireing two triggers just to get an edited_by column filled in. Thanks Dave
- References:
- Audit Trigger puzzler
- From: David Kerr
- Re: Audit Trigger puzzler
- From: Simon Riggs
- Audit Trigger puzzler
- Prev by Date: Re: Looking for "proper" escape string syntax from pg_get_constraintdef
- Next by Date: Re: Query and the number of row result
- Previous by thread: Re: Audit Trigger puzzler
- Next by thread: High load on commit after important schema changes
- Indexes: