Re: anyelement -> anyrange
От
David G. Johnston
Тема
Re: anyelement -> anyrange
Дата
Msg-id
CAKFQuwYWN3M7fv5ukV_LidpAqM6EgO9gaSVsvdmRsov3-Tpfkw@mail.gmail.com
Ответ на
Re: anyelement -> anyrange (Jim Nasby)
Список
Дерево обсуждения
anyelement -> anyrange Jim Nasby <Jim.Nasby@BlueTreble.com>
Re: anyelement -> anyrange Tom Lane <tgl@sss.pgh.pa.us>
Re: anyelement -> anyrange Jim Nasby <Jim.Nasby@BlueTreble.com>
Re: anyelement -> anyrange "David G. Johnston" <david.g.johnston@gmail.com>
Re: anyelement -> anyrange Jim Nasby <Jim.Nasby@BlueTreble.com>
Re: anyelement -> anyrange Tom Lane <tgl@sss.pgh.pa.us>
Re: anyelement -> anyrange Corey Huinker <corey.huinker@gmail.com>
Re: anyelement -> anyrange Jim Nasby <Jim.Nasby@BlueTreble.com>
Re: anyelement -> anyrange Corey Huinker <corey.huinker@gmail.com>
Re: anyelement -> anyrange Jim Nasby <Jim.Nasby@BlueTreble.com>
Re: anyelement -> anyrange Corey Huinker <corey.huinker@gmail.com>
Re: anyelement -> anyrange "David E. Wheeler" <david@justatheory.com>
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
Дата:
