Re: operator dependency of commutator and negator, redux

Поиск
Список
Период
Сортировка
Искать
От
Brendan Jurd
Тема
Re: operator dependency of commutator and negator, redux
Дата
Msg-id
CADxJZo0HHSadQcK-aeqrG0Rnph46hRTDN_HTACp55a+fdJ_HnQ@mail.gmail.com
Ответ на
Список
Дерево обсуждения
operator dependency of commutator and negator, redux Tom Lane <tgl@sss.pgh.pa.us>
Re: operator dependency of commutator and negator, redux Brendan Jurd <direvus@gmail.com>
Re: operator dependency of commutator and negator, redux Tom Lane <tgl@sss.pgh.pa.us>
Re: operator dependency of commutator and negator, redux Robert Haas <robertmhaas@gmail.com>
Re: operator dependency of commutator and negator, redux Tom Lane <tgl@sss.pgh.pa.us>
Re: operator dependency of commutator and negator, redux Dimitri Fontaine <dimitri@2ndQuadrant.fr>
On 20 December 2012 11:51, Tom Lane  wrote:
>
> While reconsidering the various not-too-satisfactory fixes we thought of
> back then, I had a sudden thought.  Instead of having a COMMUTATOR or
> NEGATOR forward reference create a "shell" operator and link to it,
> why not simply *ignore* such references?  Then when the second operator
> is defined, go ahead and fill in both links?


Ignore with warning sounds pretty good.  So it would go something like this?

# CREATE OPERATOR < (... COMMUTATOR >);
WARNING: COMMUTATOR > (foo, foo) undefined, ignoring.
CREATE OPERATOR

# CREATE OPERATOR > (... COMMUTATOR <);
CREATE OPERATOR


Cheers,
BJ


В списке pgsql-hackers по дате отправления
От: Ronan Dunklau
Дата:
От: Gavin Flower
Дата:
FAQ