From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
Cc: | 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:28:34 |
Message-ID: | AANLkTimzQsE7LJ6jc8Bi0bXvU9PynU=+zOwBv2X=vRyV@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Nov 17, 2010 at 7:08 PM, Jaime Casanova <jaime(at)2ndquadrant(dot)com> wrote:
> On Thu, Sep 30, 2010 at 7:46 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> Hello
>>
>> this patch implement a new iteration construct - iteration over an
>> array. The sense of this new iteration is:
>> * a simple and cleaner syntax
>
> 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? unnest() flattens the whole
array into scalars irregardless of dimensions:
select unnest(array[array[1,2],array[3,4]]);
unnest
--------
1
2
3
4
If yes, then +1 (unless there is some other problem) otherwise -1.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-11-18 05:47:05 | Re: final patch - plpgsql: for-in-array |
Previous Message | Jeroen Vermeulen | 2010-11-18 05:21:32 | Re: Indent authentication overloading |