Re: to be a multirange or not be, that's the question

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: to be a multirange or not be, that's the question
Дата
Msg-id CAKFQuwZLmmpaB_08+vE48YLSbk6e+tGCrLUh+rE2D2Q9X_kL_w@mail.gmail.com
обсуждение исходный текст
Ответ на to be a multirange or not be, that's the question  (Jaime Casanova <jcasanov@systemguards.com.ec>)
Список pgsql-hackers
On Saturday, November 6, 2021, Jaime Casanova <jcasanov@systemguards.com.ec> wrote:
Ok, subject was a bit philosophical but this message I just found is
quite confusing.

"""
regression=# select cast(null as anyrange) &> cast(null as anymultirange);
ERROR:  argument declared anymultirange is not a multirange type but type anymultirange
"""


I get that it is hard to parse but it is unambiguously correct.  It does seem to presume that one understands how polymorphic pseudo-types work (the supplied query was written without that knowledge applied).  I can envision some improvements here though it would depend a lot on the actual implementation.  I’m also curious as to why we get as far the operator invocation when casting literals to polymorphic pseudo-types is supposedly an invalid thing to do.

David J.

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Jaime Casanova
Дата:
Сообщение: to be a multirange or not be, that's the question
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: [PROPOSAL] new diagnostic items for the dynamic sql