From: Bryce Nesbitt <bryce1@obviously.com>
To: sql pgsql <pgsql-sql@postgresql.org>
Subject: Re: Proposed archival read only trigger on rows - prevent history modification
Date: Tue, 12 Feb 2008 00:25:46 -0800
Message-ID: <47B1580A.7050703@obviously.com> (raw)
In-Reply-To: <771732.23057.qm@web54301.mail.re2.yahoo.com>
References: <771732.23057.qm@web54301.mail.re2.yahoo.com>
Yes, the view approach has some advantages. But it still leaves the
underlying tables naked to modification.
And since the most likely error is... well... me (or another admin) at
the SQL prompt, we want underlying tables protected also.
chester c young wrote:
> instead of triggers I use update-able views and permissions.
>
> 1. all dml goes through the view
> 2. use rules on the view to do dml to the table
> 3. in rules prevent updating all/any columns when whatever
> 4. grant dml to view to your pgconnect user
> 5. revoke dml from table to your pgconnect user
>
> imho another instance where rules rule. for example, you can easily
> fit logging into the same view.
>
--
----
Visit http://www.obviously.com/
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: bryce1@obviously.com
Subject: Re: Proposed archival read only trigger on rows - prevent history modification
In-Reply-To: <47B1580A.7050703@obviously.com>
* 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