Re: Proposal: plpgsql - "for in array" statement - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Proposal: plpgsql - "for in array" statement
Date
Msg-id AANLkTikV_avOiHNnsHtEv87ze-QDURuNXScA4eiM-Gex@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: plpgsql - "for in array" statement  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
2010/9/28 Tom Lane <tgl@sss.pgh.pa.us>:
> Pavel Stehule <pavel.stehule@gmail.com> writes:
>> 2010/9/28 Tom Lane <tgl@sss.pgh.pa.us>:
>>> Sure it can: it could be a parenthesized top-level query.  In fact,
>>> that's what plpgsql will assume if you feed it that syntax today.
>
>> no - there are not any legal construct FOR r IN (..)
>
> You are simply wrong, sir, and I suggest that you go read the SQL
> standard until you realize that.  Consider for example
>
>        for r in (SELECT ... FROM a UNION SELECT ... FROM b) INTERSECT (SELECT ... FROM c) LOOP ...
>
> The parentheses here are not merely legal, they are *necessary*, else
> the semantics of the UNION/INTERSECT operations change.
>

ok, then probably one variant is for-in-array array_expr. Is there agreement?

Regards

Pavel Stehule




>                        regards, tom lane
>


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: I: About "Our CLUSTER implementation is pessimal" patch
Next
From: Itagaki Takahiro
Date:
Subject: Re: I: About "Our CLUSTER implementation is pessimal" patch