Postgres Pro
Downloads
Home   >   mailing lists

Re: anyelement -> anyrange - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: anyelement -> anyrange
Date
Msg-id 6b13eaae-2c63-87e0-2925-eebf80c63b4a@BlueTreble.com
Whole thread Raw
In response to Re: anyelement -> anyrange  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: anyelement -> anyrange  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
Tree view 
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...
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)   mobile: 512-569-9461

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Server crash due to SIGBUS(Bus Error) when trying to access the memory created using dsm_create().
Next
From: "David G. Johnston"
Date:
Subject: Re: anyelement -> anyrange