| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: functional call named notation clashes with SQL feature |
| Date: | 2010-05-31 14:59:15 |
| Message-ID: | 12885.1275317955@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tom Lane wrote:
>> So as far as I can tell, no one is opposed to replacing "expr AS name"
>> with "name := expr" in the named-parameter syntax. Obviously we had
>> better get this done before beta2. Is anyone actually working on the
>> code/docs changes? If not, I'll pick it up.
> If we eventually are going to want to support the ANSI standard "=>"
> syntax, I am thinking we should just do it now. The larger question is
> what justification do we have of not supporting "=>".
Not breaking hstore, as well as any third-party modules that might be
using that operator name. Did you not absorb any of the discussion
so far?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2010-05-31 15:07:15 | Re: functional call named notation clashes with SQL feature |
| Previous Message | Simon Riggs | 2010-05-31 14:43:20 | Re: PG 9.0 release timetable |