Re: Possible typo in create_policy.sgml

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Possible typo in create_policy.sgml
Date: 2015-01-29 12:46:55
Message-ID: 20150129124655.GP3854@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Dean Rasheed (dean(dot)a(dot)rasheed(at)gmail(dot)com) wrote:
> On 29 January 2015 at 04:00, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> > * Robert Haas (robertmhaas(at)gmail(dot)com) wrote:
> >> On Wed, Jan 7, 2015 at 3:06 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> >> > If I'm following correctly, Peter's specifically talking about:
> >> >
> >> > [ USING ( <replaceable class="parameter">expression</replaceable> ) ]
> >> > [ WITH CHECK ( <replaceable class="parameter">check_expression</replaceable> ) ]
> >> >
> >> > Where the USING parameter is 'expression' but the WITH CHECK parameter
> >> > is 'check_expression'. He makes a good point, I believe, as
> >> > "expression" is overly generic. I don't like the idea of using
> >> > "barrier_expression" though as that ends up introducing a new term- how
> >> > about "using_expression"?
> >>
> > I've gone ahead and made this minor change.
>
> Don't forget the ALTER POLICY page. This and some of the other things
> being discussed on this thread ought to be copied there too.

Ah, yeah, good point, will address soon.

Thanks!

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-01-29 13:47:50 Re: Possible typo in create_policy.sgml
Previous Message Bruce Momjian 2015-01-29 12:22:29 Re: jsonb, unicode escapes and escaped backslashes