From: Mark Stosberg <mark@summersault.com>
To: pgsql-sql@postgresql.org
Subject: Need help revoking access WHERE state = 'deleted'
Date: Thu, 28 Feb 2013 11:37:39 -0500
Message-ID: <kgo14h$vm3$1@ger.gmane.org> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>
We are working on a project to start storing some data as "soft deleted"
(WHERE state = 'deleted') instead of hard-deleting it.
To make sure that we never accidentally expose the deleted rows through
the application, I had the idea to use a view and permissions for this
purpose.
I thought I could revoke SELECT access to the "entities" table, but then
grant SELECT access to a view:
CREATE VIEW entities_not_deleted AS SELECT * FROM entities WHERE state
!= 'deleted';
We could then find/replace in the code to replace references to the
"entities" table with the "entities_not_deleted" table
However, this isn't working, I "permission denied" when trying to use
the view. (as the same user that has had their SELECT access removed to
the underlying table.)
We are not stuck on this design. What's a recommended way to solve this
problem?
Mark
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
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: mark@summersault.com
Subject: Re: Need help revoking access WHERE state = 'deleted'
In-Reply-To: <kgo14h$vm3$1@ger.gmane.org>
* 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