Re: Function call order dependency

Поиск
Список
Период
Сортировка
Искать
От
pgsql@mohawksoft.com
Тема
Re: Function call order dependency
Дата
Msg-id
45309.64.119.130.186.1220458259.squirrel@mail.mohawksoft.com
Ответ на
Список
Дерево обсуждения
Function call order dependency pgsql@mohawksoft.com
Re: Function call order dependency "Stephen R. van den Berg" <srb@cuci.nl>
Re: Function call order dependency Tom Lane <tgl@sss.pgh.pa.us>
Re: Function call order dependency pgsql@mohawksoft.com
Re: Function call order dependency "Robert Haas" <robertmhaas@gmail.com>
Re: Function call order dependency pgsql@mohawksoft.com
Re: Function call order dependency pgsql@mohawksoft.com
Re: Function call order dependency Tom Lane <tgl@sss.pgh.pa.us>
Re: Function call order dependency pgsql@mohawksoft.com
> pgsql@mohawksoft.com writes:
>> For example I'll use the Oracle "contains" function, though this is not
>> exactly what I'm doing, it just illustrates the issue clearly.
>
>> select *, score(1) from mytable where contains(mytable.title, 'Winding
>> Road', 1) order by score(1);
>
>> The "contains" function does a match against mytable.title for the term
>> 'Winding Road' and both returns and saves an integer score which may be
>> retrieved later using the "score(...)" function.
>
> This is just a bad, bad idea.  Side-effects in a WHERE-clause function
> are guaranteed to cause headaches.  When (not if) it breaks, you get
> to keep both pieces.

I was kind of afraid of that. So, how could one implement such a function
set?

В списке pgsql-hackers по дате отправления
От: Joshua Drake
Дата:
От: Alvaro Herrera
Дата:
FAQ