From: George Weaver <gweaver@shaw.ca>
To: Aaron Bono <postgresql@aranya.com>
To: John DeSoi <desoi@pgedit.com>
Cc: Thusitha Kodikara <kthusi@yahoo.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Triggers using PL/pgSQL
Date: Mon, 31 Jul 2006 11:16:42 -0500
Message-ID: <006601c6b4bc$b74f0ba0$6400a8c0@Dell4500> (raw)
References: <20060731041644.32247.qmail@web56610.mail.re3.yahoo.com>
<bf05e51c0607302152k2801caflc9040d99af7b2816@mail.gmail.com>
<7F7548C8-249E-44E2-8205-6C055671DA19@pgedit.com>
<bf05e51c0607310759m64d39c45n73aa6060c871b46f@mail.gmail.com>
----- 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: gweaver@shaw.ca, postgresql@aranya.com, desoi@pgedit.com, kthusi@yahoo.com
Subject: Re: Triggers using PL/pgSQL
In-Reply-To: <006601c6b4bc$b74f0ba0$6400a8c0@Dell4500>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox