Re: CREATE RULE problem/question requesting workaround

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Chris Travers <chris(at)travelamericas(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: CREATE RULE problem/question requesting workaround
Date: 2003-12-07 16:46:25
Message-ID: 22353.1070815585@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Chris Travers <chris(at)travelamericas(dot)com> writes:
> Is there any way to try to enforce a rewrite
> rule in such a away as to do the select query as normal, but if
> necessary raise an exception (to abort the select)?

No.

You need to rethink your permissions design. One idea that you *can*
make work is to have a view that everyone can read, but are only able to
see selected rows in. pg_stats works that way, and I think there are
examples in the information schema as well.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-12-07 17:39:01 Re: CREATE RULE problem/question requesting workaround
Previous Message Chris Travers 2003-12-07 16:05:08 Re: CREATE RULE problem/question requesting workaround