On Tue, Sep 28, 2010 at 4:39 PM, Pavel Stehule <pavel.steh...@gmail.com> wrote: > 2010/9/28 Tom Lane <t...@sss.pgh.pa.us>: >> Pavel Stehule <pavel.steh...@gmail.com> writes: >>> 2010/9/28 Tom Lane <t...@sss.pgh.pa.us>: >>>> As an example, is this a for-in-query or a >>>> for-in-array? >>>> >>>> FOR v IN (SELECT arraycol FROM tab) LOOP ... >> >>> This is a subquery - so it is a for-in-array - should return one row >>> with one column. >> >> That's not obvious at all. It's legal right now to write that, and it >> will be interpreted as for-in-query. > > but it has not a sense.
It has a very fine sense. It's completely obvious to me what that means, and you're proposing to break it. In a word: no. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
