Re: Not understanding this behavior of a subselect + volatile function
От
Brian Palmer
Тема
Re: Not understanding this behavior of a subselect + volatile function
Дата
Msg-id
269E9100-26E6-44C7-8325-0CAF481EF3E8@codekitchen.net
Ответ на
Список
Дерево обсуждения
Not understanding this behavior of a subselect + volatile function Brian Palmer <brian@codekitchen.net>
Re: Not understanding this behavior of a subselect + volatile function Tom Lane <tgl@sss.pgh.pa.us>
Re: Not understanding this behavior of a subselect + volatile function Brian Palmer <brian@codekitchen.net>
Re: Not understanding this behavior of a subselect +
volatile function Chris Angelico <rosuav@gmail.com>
Re: Not understanding this behavior of a subselect + volatile function Brian Palmer <brian@codekitchen.net>
Re: Not understanding this behavior of a subselect +
volatile function Chris Angelico <rosuav@gmail.com>
Re: Not understanding this behavior of a subselect + volatile function Brian Palmer <brian@codekitchen.net>
On May 26, 2012, at 7:45 PM, Chris Angelico wrote: > I'd be inclined to treat it like C and avoid referencing and > altering a variable in one expression (eg arr[i++]=i; is a bad idea). I agree, we're already working on changing it to a two-step process where we select f1(), and then select * where a = $a . I'm still really curious about what's going on here though. Thanks for the insight! -- Brian
В списке pgsql-general по дате отправления
От: Chris Angelico
Дата:
От: Tom Lane
Дата: