Re: more RLS oversights - Mailing list pgsql-hackers

From Robert Haas
Subject Re: more RLS oversights
Date
Msg-id CA+TgmoaLwu7FkJ_w8XNdsbxBCf+=OCNpJH7UYQomYusA=dJGCA@mail.gmail.com
Whole thread Raw
In response to Re: more RLS oversights  (Joe Conway <joe.conway@crunchydata.com>)
Responses Re: more RLS oversights
List pgsql-hackers
On Wed, Jul 29, 2015 at 4:57 PM, Joe Conway <joe.conway@crunchydata.com> wrote:
> On 07/29/2015 01:26 PM, Robert Haas wrote:
>> On Wed, Jul 29, 2015 at 3:58 PM, Alvaro Herrera
>> <alvherre@2ndquadrant.com> wrote:
>>> I think this reads a bit funny.  What's a "POLICY USING" clause?  I
>>> expect that translators will treat the two words POLICY USING as a
>>> single token, and the result is not going to make any sense.
>>>
>>> Maybe "in a policy's USING and WITH CHECK expressions", or perhaps "in
>>> policies's USING and WITH CHECK exprs", not sure.
>>
>> Yeah, I don't see why we would capitalize POLICY there.
>
> The equivalent message for functions is:
>   ".. are not allowed in functions in FROM"
>
> So how does this sound:
> "... are not allowed in policies in USING and WITH CHECK expressions"
> or perhaps more simply:
> "... are not allowed in policies in USING and WITH CHECK"

Awkward.  The "in policies in" phrasing is just hard to read.  Why not
just "in policy expressions"?  There's no third kind that does allow
these.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: dblink: add polymorphic functions.
Next
From: Alvaro Herrera
Date:
Subject: Re: more RLS oversights