| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: remove undocumented assign syntax from plpgsql doc |
| Date: | 2014-01-15 20:47:13 |
| Message-ID: | 32425.1389818833@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Wed, Jan 15, 2014 at 05:39:22PM +0100, Pavel Stehule wrote:
> Uh, I see it in the documented syntax:
> OPEN <replaceable>bound_cursorvar</replaceable> <optional> ( <optional>
> <replaceable>argument_name</replaceable> := </optional> <---
> <replaceable>argument_value
It is there, if you look into read_cursor_args().
This appears to be the only place in pl_gram.y where we don't treat '='
and COLON_EQUALS interchangeably.
I was about to suggest that we should accept "=" here too, but on second
thought that could break existing code, if anyone's using boolean equality
expressions in cursor arguments. So we'd better accept the inconsistency.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-01-16 21:40:36 | Re: remove undocumented assign syntax from plpgsql doc |
| Previous Message | Bruce Momjian | 2014-01-15 20:36:04 | Re: remove undocumented assign syntax from plpgsql doc |