Re: Bug? Function with side effects not evaluated in CTE

Поиск
Список
Период
Сортировка
От Rowan Collins
Тема Re: Bug? Function with side effects not evaluated in CTE
Дата
Msg-id 525F2BD2.4070209@gmail.com
обсуждение исходный текст
Ответ на Re: Bug? Function with side effects not evaluated in CTE  (Merlin Moncure <mmoncure@gmail.com>)
Ответы Re: Bug? Function with side effects not evaluated in CTE  (Adam Jelinek <ajelinek@gmail.com>)
Re: Bug? Function with side effects not evaluated in CTE  (Merlin Moncure <mmoncure@gmail.com>)
Список pgsql-general
On 17/10/2013 00:06, Merlin Moncure wrote:
That being said, I do think it might be better behavior (and still
technically correct per the documentation) if volatile query
expressions were force-evaluated.

This sounds reasonable for a "yes or no" case like this, but wouldn't it raise the question of how many times the function should be evaluated?

What if the query looked more like this:

with tt_created as
(
    select fn_new_item(foo) as item
    from some_huge_table
)
select item
from tt_created
limit 10


Should the CTE be calculated in its entirety, running the function for every row in some_huge_table? Or should it run at most 10 times?

Which is desired would depend on the situation, but there's no real way to indicate in the syntax.
-- 
Rowan Collins
[IMSoP]

В списке pgsql-general по дате отправления:

Предыдущее
От: John R Pierce
Дата:
Сообщение: Re: pg_hba.conf broken after cluster upgrade
Следующее
От: Adrian Klaver
Дата:
Сообщение: Re: pg_hba.conf broken after cluster upgrade