Re: anyelement -> anyrange

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: anyelement -> anyrange
Дата
Msg-id CAKFQuwYWN3M7fv5ukV_LidpAqM6EgO9gaSVsvdmRsov3-Tpfkw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: anyelement -> anyrange  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Ответы Re: anyelement -> anyrange  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Список pgsql-hackers
On Tue, Aug 16, 2016 at 7:47 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
On 8/15/16 10:12 PM, Tom Lane wrote:
Jim Nasby <Jim.Nasby@BlueTreble.com> writes:
Any reason why we can create a function that accepts anyelement and
returns anyarray, but can't do the same with anyrange?

Because there can be more than one range type over the same element
type, so we couldn't deduce which one should be used for anyrange.

The other direction (inferring anyelement from anyrange) does work.

Is there an actual use case for that? I'm not seeing what it would be...


lower() and upper() both use it.

David J.
 

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

Предыдущее
От: Jim Nasby
Дата:
Сообщение: Re: anyelement -> anyrange
Следующее
От: Jim Nasby
Дата:
Сообщение: Re: [Patch] Temporary tables that do not bloat pg_catalog (a.k.a fast temp tables)