From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: plpgsql - "for in array" statement |
Date: | 2010-09-28 20:24:30 |
Message-ID: | AANLkTim-WdzUxM5=BJVLqvCFn9jG+7VcwpR43CCUgcFm@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/9/28 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> 2010/9/28 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>>> But I guess you could get around that if you had to by putting the ARRAY
>>> expression inside parens, and it would be a pretty darn unusual case
>>> anyway. So this is probably the best choice.
>
>> I don't agree - There isn't reason for complicating proposed syntax.
>
> Yes, there is. The syntax you propose is flat out ambiguous: there are
> two possible legal interpretations of some commands. That's not
> acceptable, especially not when it's so easily fixed.
>
what are you thinking? The subquery cannot be interpreted different.
There are not possible use a isolated subquery as query. And subquery
have to return one row, one column.
Pavel
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-09-28 20:32:50 | Re: Proposal: plpgsql - "for in array" statement |
Previous Message | Tom Lane | 2010-09-28 20:19:32 | Re: Proposal: plpgsql - "for in array" statement |