Re: unclear about row-level security USING vs. CHECK
От | Robert Haas |
---|---|
Тема | Re: unclear about row-level security USING vs. CHECK |
Дата | |
Msg-id | CA+TgmoY2RqLhM7P9xpd=DPUXd_qBDVMYO1BztEM+P=sjRGbYfg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: unclear about row-level security USING vs. CHECK (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: unclear about row-level security USING vs. CHECK
|
Список | pgsql-hackers |
On Sat, Sep 26, 2015 at 9:46 PM, Peter Eisentraut <peter_e@gmx.net> wrote: > On 9/23/15 3:41 PM, Stephen Frost wrote: > I see. But it is a bit odd to hide this very fundamental behavior > somewhere in a paragraph that starts out with something about roles. > > There is also a mistake, I believe: DELETE policies also take both a > CHECK and a USING clause. > > I still find something about this weird, but I'm not sure what. It's > not clear to me at what level this USING->CHECK mapping is applied. I > can write FOR ALL USING and it will be mapped to CHECK for all actions, > including INSERT, but when I write FOR INSERT USING it complains. Why > doesn't it do the mapping that case, too? We are really pushing our luck only hammering this stuff out now. But I think I agree with Peter's concerns, FWIW. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: