Re: operator precedence issues
От | Andres Freund |
---|---|
Тема | Re: operator precedence issues |
Дата | |
Msg-id | 20130830224852.GA11360@awork2.anarazel.de обсуждение исходный текст |
Ответ на | operator precedence issues (Merlin Moncure <mmoncure@gmail.com>) |
Ответы |
Re: operator precedence issues
|
Список | pgsql-hackers |
Hi, On 2013-08-30 17:35:04 -0500, Merlin Moncure wrote: > "When a schema-qualified operator name is used in the OPERATOR syntax, > as for example in: > SELECT 3 OPERATOR(pg_catalog.+) 4; > the OPERATOR construct is taken to have the default precedence shown > in Table 4-2 for "any other" operator. This is true no matter which > specific operator appears inside OPERATOR()." > > That rule seems intentionally designed to make it impossible to to > override mathematical behaviors. Mainly curious -- was that > intentional? You can change your search_path to include your schema before an explicitly listed pg_catalog afair. Not nice, but should work... Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: