From: | George Weaver <gweaver(at)shaw(dot)ca> |
---|---|
To: | Aaron Bono <postgresql(at)aranya(dot)com>, John DeSoi <desoi(at)pgedit(dot)com> |
Cc: | Thusitha Kodikara <kthusi(at)yahoo(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Triggers using PL/pgSQL |
Date: | 2006-07-31 16:16:42 |
Message-ID: | 006601c6b4bc$b74f0ba0$6400a8c0@Dell4500 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-php pgsql-sql |
----- Original Message -----
From: Aaron Bono
To: John DeSoi
<snip>
>I don't think so but there was some discussion a week or two ago about
>mixing variables and using execute. I am curious, does anyone >know what
>the "best" approach is?
>Also, I did not address deletions. If you still need to delete from the
>table, you will need to get rid of the foreign key on the history table.
> >You will also need to decide how the history table will reflect the
>recording of those deletions.
You may want to refer to:
http://www.varlena.com/GeneralBits/104.php (Logging Audit Changes with
Composite Typed Columns).
It provides a very concise way of tracking all changes, possible qualifying
as a "best approach"?
Regards,
George
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Hofer | 2006-07-31 19:48:38 | connection pool |
Previous Message | Milen A. Radev | 2006-07-31 16:12:30 | Re: Triggers using PL/pgSQL |
From | Date | Subject | |
---|---|---|---|
Next Message | Aaron Bono | 2006-07-31 19:34:49 | Re: primary keys as TEXT |
Previous Message | Milen A. Radev | 2006-07-31 16:12:30 | Re: Triggers using PL/pgSQL |