Re: SE-PostgreSQL and row level security
| От | Tom Lane |
|---|---|
| Тема | Re: SE-PostgreSQL and row level security |
| Дата | |
| Msg-id | 16239.1234796031@sss.pgh.pa.us обсуждение |
| Ответ на | Re: SE-PostgreSQL and row level security ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
| Ответы |
Re: SE-PostgreSQL and row level security
Re: SE-PostgreSQL and row level security Re: SE-PostgreSQL and row level security Re: SE-PostgreSQL and row level security |
| Список | pgsql-hackers |
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> Gregory Stark <stark@enterprisedb.com> wrote:
>> And it doesn't accomplish anything since the covert
>> channels it attempts to address are still open.
> Hyperbole. We're not very likely to go the SE-* route, but I can say
> that we've got some of the issues it addresses, and it is a very
> different thing for someone to know, for example, that there is a
> paternity case 2009PA000023 in a county, and for them to know what the
> case caption is (which includes the names).
Which is something you could implement with standard SQL column
permissions; and could *not* implement with row-level access
permissions. Row-level is all or nothing for each row.
regards, tom lane
В списке pgsql-hackers по дате отправления: