| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | 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-07 20:08:34 |
| Message-ID: | CA+TgmoYEY0SnGSVik5gm9r+T6kFOTg3vwMCq3EGVyY4HwgjP-A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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"?
Oh. Well, I guess we could change that. I don't think it's a
problem, myself. I thought he was talking about something in the SGML
markup.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2015-01-07 20:09:56 | Re: Possible typo in create_policy.sgml |
| Previous Message | Stephen Frost | 2015-01-07 20:06:48 | Re: Possible typo in create_policy.sgml |