Re: Proposal: plpgsql - "for in array" statement

From: Darren Duncan <darren(at)darrenduncan(dot)net>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Subject: Re: Proposal: plpgsql - "for in array" statement
Date: 2010-09-29 01:43:18
Message-ID: 4CA299B6.5070306@darrenduncan.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera wrote:
> What about
>
> FOR EACH var IN array_expr LOOP ...
>
> I think this requires reserving EACH, which could cause a regression for
> working code. Maybe there's a way to make it work?

What about saying FOR-EACH instead?

A good general solution that I'd expect to not cause regressions is to separate
multiple-word keywords with dashes rather than spaces.

Since unquoted identifiers don't have dashes, I think, and moreover because the
whole FOR-EACH would occupy the first position of the statement rather than the
first two, there should be no ambiguity.

Parsing should be easier, too, because keywords formatted like this would just
be a single term rather than having infinite variations due to embedded whitespace.

-- Darren Duncan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-09-29 01:55:45 Re: Proposal: plpgsql - "for in array" statement
Previous Message Itagaki Takahiro 2010-09-29 01:33:21 Re: [RRR] [HACKERS] Commitfest: The Good, The Bad, and the Ugly