Re: FOR-IN-EXECUTE: FOR does not replanned on each entry to the FOR loop
От | |
---|---|
Тема | Re: FOR-IN-EXECUTE: FOR does not replanned on each entry to the FOR loop |
Дата | |
Msg-id | 039601c890f6$b6945c70$1200a8c0@kharkov.localhost обсуждение исходный текст |
Ответ на | FOR-IN-EXECUTE: FOR does not replanned on each entry to the FOR loop (<Eugen.Konkov@aldec.com>) |
Список | pgsql-bugs |
Sorry, docs have confusing me. I think 'each entry' means each iterations of loop. So maybe it is need to fix doc. to describe for-in-execute more clearly thx ----- Original Message ----- From: "Euler Taveira de Oliveira" <euler@timbira.com> To: <Eugen.Konkov@aldec.com> Cc: <pgsql-bugs@postgresql.org> Sent: Friday, March 28, 2008 5:43 PM Subject: Re: [BUGS] FOR-IN-EXECUTE: FOR does not replanned on each entry to the FOR loop > Eugen.Konkov@aldec.com wrote: > >> FOR and WHILE results differ >> WHILE returns two rows >> but FOR returns only one. >> and it seems that FOR does not replanned on each entry to the FOR loop >> While docs says: >> 38.6.4. Looping Through Query Results >> .... >> This is like the previous form, except that the source query is specified >> as a string expression, which is evaluated and replanned on each entry to >> the FOR loop >> > You are confusing things. The statement above talks about FOR rec IN > EXECUTE query_string LOOP ... END LOOP. There is no WHILE. > When you're using WHILE, the EXECUTE is actually evaluated inside the loop > and not in the loop condition (that's why you're seeing another > iteration). > > > -- > Euler Taveira de Oliveira > http://www.timbira.com/
В списке pgsql-bugs по дате отправления: