Re: CREATE RULE problem/question requesting workaround

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: CREATE RULE problem/question requesting workaround
Дата
Msg-id 22353.1070815585@sss.pgh.pa.us
обсуждение исходный текст
Ответ на CREATE RULE problem/question requesting workaround  (Chris Travers <chris@travelamericas.com>)
Ответы Re: CREATE RULE problem/question requesting workaround  (Chris Travers <chris@travelamericas.com>)
Список pgsql-general
Chris Travers <chris@travelamericas.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

В списке pgsql-general по дате отправления:

Предыдущее
От: Michael Glaesemann
Дата:
Сообщение: Re: user defined variable per session
Следующее
От: Chris Travers
Дата:
Сообщение: Re: CREATE RULE problem/question requesting workaround