| From: | "Charles Ambrose" <jamjam360(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | A generic trigger to log chanes on database tables |
| Date: | 2006-11-23 16:32:30 |
| Message-ID: | 61ca079e0611230832i4744b831j6436f72d8f6c7130@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi!
Is there a way that I could create a trigger that logs the changes (updates,
deletes) of a table? I mean, I want to put in a table the changes to any
table in a database and also put in the table the column that was modified
and the corresponding value.
My audit table looks like this:
Table name: TableChangesLog
Columns: ChangeID int not null auto_increment --> Primary Key of table
TableName -> Name of table modified
ColumnName -> Column modified
ColumnValue -> The original value
Operation -> "Update" or "Delete"
My idea is to create a generic trigger that will log all changes for all
database tables.
Is this possible?
Thanks in advance ...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2006-11-23 16:49:10 | Re: IS it a good practice to use SERIAL as Primary Key? |
| Previous Message | Tom Lane | 2006-11-23 16:27:06 | Re: COPY FROM : out of memory |