From: | "Richard Sydney-Smith" <richard(at)ibisaustralia(dot)com> |
---|---|
To: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Table History |
Date: | 2004-12-17 06:23:32 |
Message-ID: | 002101c4e400$f0164220$13dd8a90@athlon2000 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
A database I maintain has a central transaction table ( FTRANS)
I would like an second table FTRANS_IMAGE to maintain a historical view
of ftrans. So if records in FTRANS are altered we can trace the effect
of those changes in FTRANS_IMAGE.
I expect this has been done MANY times and I wonder if a general purpose
trigger exists or if not then can someone point me to an example set of
triggers?
I would like to trace an action code "Edit" or "Delete" in FTRANS_IMAGE
in additional to the common fields.
thanks muchly
Richard Sydney-Smith
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com)
Version: 6.0.799 / Virus Database: 543 - Release Date: 19/11/2004
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2004-12-17 06:52:09 | Re: FUNCTION, TRIGGER and best practices |
Previous Message | Josh Berkus | 2004-12-17 05:43:32 | Re: FUNCTION, TRIGGER and best practices |