From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: final patch - plpgsql: for-in-array |
Date: | 2010-11-18 05:47:05 |
Message-ID: | 20429.1290059225@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> On Wed, Nov 17, 2010 at 7:08 PM, Jaime Casanova <jaime(at)2ndquadrant(dot)com> wrote:
>> i will start the review of this one... but before that sorry for
>> suggesting this a bit later but about using UNNEST as part of the
>> sintax?
> Does for-in-array do what unnset does?
Yes, which begs the question of why bother at all. AFAICS this patch
simply allows you to replace
for x in select unnest(array_value) loop
with
for x in unnest array_value loop
(plus or minus a parenthesis or so). I do not think we need to add a
bunch of code and create even more syntactic ambiguity (FOR loops are
already on the hairy edge of unparsability) to save people from writing
"select".
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stuart Bishop | 2010-11-18 05:49:14 | Re: Indent authentication overloading |
Previous Message | Merlin Moncure | 2010-11-18 05:28:34 | Re: final patch - plpgsql: for-in-array |