From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Darren Duncan <darren(at)darrenduncan(dot)net> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: plpgsql - "for in array" statement |
Date: | 2010-09-29 02:27:08 |
Message-ID: | 4CA2A3FC.3070505@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 09/28/2010 09:31 PM, Darren Duncan wrote:
> 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?
>
> Code that quotes all of its identifiers, such as with:
>
> FOR EACH "var" IN "array_expr" LOOP ...
>
> ... would also gain a significant amount of future-proofing since then
> the language can add keywords at will, without there being conflicts
> with user-defined identifiers.
>
> Similarly, quoting identifiers also carries present-day advantages as
> then one can name identifiers whatever is most suitably descriptive
> for them without worrying whether the language has a pre-defined
> meaning for the used words.
>
> The quoting also has the nice bonus of making them case-sensitive.
>
>
This doesn't help in the least if the array is an expression rather than
simply a variable - we're not going to start quoting expressions.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2010-09-29 02:32:17 | Re: Proposal: plpgsql - "for in array" statement |
Previous Message | Robert Haas | 2010-09-29 02:16:51 | Re: [RRR] [HACKERS] Commitfest: The Good, The Bad, and the Ugly |