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

From Tom Lane
Subject Re: Proposal: plpgsql - "for in array" statement
Date
Msg-id 28950.1285707807@sss.pgh.pa.us
Whole thread Raw
In response to Re: Proposal: plpgsql - "for in array" statement  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: Proposal: plpgsql - "for in array" statement  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Commitfest: The Good, The Bad, and the Ugly
Next
From: Sergey Burladyan
Date:
Subject: UTF8 regexp and char classes still does not work