Re: operator precedence issues

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: operator precedence issues
Дата
Msg-id
15949.1378217592@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
operator precedence issues Merlin Moncure <mmoncure@gmail.com>
Re: operator precedence issues Andres Freund <andres@2ndquadrant.com>
Re: operator precedence issues Merlin Moncure <mmoncure@gmail.com>
Re: operator precedence issues Andres Freund <andres@2ndquadrant.com>
Re: operator precedence issues Tom Lane <tgl@sss.pgh.pa.us>
operator precedence issues Merlin Moncure <mmoncure@gmail.com>
Re: operator precedence issues Tom Lane <tgl@sss.pgh.pa.us>
Andres Freund  writes:
> On 2013-09-03 08:59:53 -0500, Merlin Moncure wrote:
>> While playing around with Andres's trick, I noticed that it works but
>> will not match against operators taking "any" although those will
>> match with explicit schema declaration (FWICT it goes through the
>> search_path trying to explicitly match int/int operator then goes
>> again matches "any").  That's pretty weird:

> Not surprising. We look for the best match for an operator and
> explicitly matching types will be that. If there were no operator(int,
> int) your anyelement variant should get called.

Yeah, this has exactly nothing to do with operator precedence.
Precedence is about which operator binds tighter in cases like "A+B*C".
		regards, tom lane


В списке pgsql-hackers по дате отправления
От: Andres Freund
Дата:
Сообщение: Re: operator precedence issues
От: Blake Smith
Дата:
FAQ