From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> |
Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: FOREACH-IN-ARRAY (probably for 9.2?) |
Date: | 2010-12-17 17:15:57 |
Message-ID: | AANLkTik3Q5J=M8hTY8L5cm04GKjjy2uz6Aq9Kquxoh3X@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/12/17 Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>:
> On Sat, Dec 18, 2010 at 02:03, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
>>> FOREACH scalar-variable IN ARRAY array-expression
>>> FOR_EACH scalar-variable IN ARRAY array-expression
>>> FOR_SLICE array-variable [DEPTH n] IN ARRAY array-expression
>>> FOREACH scalar-variable IN ARRAY array-expression
>>> FOREACH array-variable SLICE n IN ARRAY array-expression
>> FOREACH scalar IN ARRAY arr_exp DIMS in dim_var
>
> It should be not a main subject, but I remember there was a discussion
> that "IN ARRAY array-expression" looks redundant for a literal array:
>
> IN ARRAY ARRAY[1, 3, 5]
>
> Are there any improvement for the issue?
yes. It know it. The reason for this is bigger space for possible
future features related to FOREACH loop.
Regards
Pavel
>
> --
> Itagaki Takahiro
>
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2010-12-17 17:21:35 | Re: proposal: FOREACH-IN-ARRAY (probably for 9.2?) |
Previous Message | Tom Lane | 2010-12-17 17:15:10 | Re: proposal: FOREACH-IN-ARRAY (probably for 9.2?) |