| From: | "Denis Lussier" <denis(at)enterprisedb(dot)com> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Feature request from irc... |
| Date: | 2005-06-29 04:08:22 |
| Message-ID: | B319CFEC3B80D3408CA36F99ADE840940F28FD@edb-dc1.Edb-net.EnterpriseDB.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I personally think it's an interesting idea. Is there a business scenario where you want/need to do this?? I think it'd be kinda cool for a trigger to be able to write out an audit record with the dml sql (along with the typical old, and new value stuff). Perhaps this is already doable??
________________________________
From: pgsql-hackers-owner(at)postgresql(dot)org on behalf of Christopher Kings-Lynne
Sent: Tue 6/28/2005 11:54 PM
To: Hackers
Subject: [HACKERS] Feature request from irc...
Is it possible for a pl/pgsql trigger function to look at the sql
command that caused it to be triggered? If not, is this an idea?
Chris
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-06-29 04:09:35 | Re: Open items |
| Previous Message | Christopher Kings-Lynne | 2005-06-29 04:06:26 | Re: Feature request from irc... |