David Fetter wrote:
It occurs to me that this might be a place to demo table inheritance
too, to ease automating the creation, etc. of the auditing
infrastructure :)
It certainly makes the creation of the audit table painless :
CREATE TABLE emp_audit(
operation char(1) NOT NULL,
On Fri, Dec 03, 2004 at 10:14:48AM +1300, Mark Kirkwood wrote:
> Tom Lane wrote:
>
> >Mark Kirkwood <[EMAIL PROTECTED]> writes:
> >
> >
> >>This patch adds another plpgsql trigger example to the chapter. It
> >>uses the emp table again, but shows how to audit changes into
> >>another table (emp_a
Patch applied. Thanks.
---
Mark Kirkwood wrote:
> Tom Lane wrote:
>
> >Mark Kirkwood <[EMAIL PROTECTED]> writes:
> >
> >
> >>This patch adds another plpgsql trigger example to the chapter. It uses
> >>the emp table ag
Tom Lane wrote:
Mark Kirkwood <[EMAIL PROTECTED]> writes:
This patch adds another plpgsql trigger example to the chapter. It uses
the emp table again, but shows how to audit changes into another table
(emp_audit).
Should be an AFTER trigger, else you may be recording the wrong data, or
ev
Mark Kirkwood <[EMAIL PROTECTED]> writes:
> This patch adds another plpgsql trigger example to the chapter. It uses
> the emp table again, but shows how to audit changes into another table
> (emp_audit).
Should be an AFTER trigger, else you may be recording the wrong data, or
even an event that
