From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | depesz(at)depesz(dot)com |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Atul Chojar <achojar(at)airfacts(dot)com>, pgsql-general(at)postgresql(dot)org, Li <lilian(dot)ying(at)airfacts(dot)com>, Andy Yoder <ayoder(at)airfacts(dot)com> |
Subject: | Re: Different handling of PL/pgSQL for-loop variables in 8.3.7 vs. 8.2.7 ??? |
Date: | 2009-06-11 12:17:33 |
Message-ID: | 162867790906110517m221cc714w4abc61167ab23e8e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
2009/6/11 hubert depesz lubaczewski <depesz(at)depesz(dot)com>:
> On Thu, Jun 11, 2009 at 12:45:56PM +0200, Pavel Stehule wrote:
>> generally - modification of cycle's control variable isn't good
>> technique, because it's should be broken by some optimizations. When
>
> i would argue then that these optimizations are broken, then.
>
>> you would to modify this some variables, then use "while-loop"
>> instead.
>
> while technically possible, i find for loops much more straight forward,
> and clearer to understand.
>
sure, forloop is clean, but not when you do some alchemy with control
variables. When you need increase step, then use BY clause. But I
thing, so it's easy protect users by marking control variables as read
only variable.
regards
Pavel Stehule
> Best regards,
>
> depesz
>
> --
> Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
> jid/gtalk: depesz(at)depesz(dot)com / aim:depeszhdl / skype:depesz_hdl / gg:6749007
>
From | Date | Subject | |
---|---|---|---|
Next Message | Emanuel Calvo Franco | 2009-06-11 15:01:10 | Re: Sobre Actualizacion |
Previous Message | hubert depesz lubaczewski | 2009-06-11 11:00:17 | Re: Different handling of PL/pgSQL for-loop variables in 8.3.7 vs. 8.2.7 ??? |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2009-06-11 12:22:25 | Re: queries on xmin |
Previous Message | Brett Henderson | 2009-06-11 12:13:29 | Re: queries on xmin |