Re: Range Types, constructors, and the type system - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Range Types, constructors, and the type system
Date
Msg-id BANLkTimW6cpAi7BNPGgqSn3Z9je7io6GfQ@mail.gmail.com
Whole thread Raw
In response to Re: Range Types, constructors, and the type system  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Range Types, constructors, and the type system
List pgsql-hackers
On Mon, Jun 27, 2011 at 11:42 PM, Jeff Davis <pgsql@j-davis.com> wrote:
> So, in effect, RANGEINPUT is a special type used only for range
> constructors. If someone tried to output it, it would throw an
> exception, and we'd even have enough information at that point to print
> a nice error message with a hint.

I don't think I like the idea of throwing an error when you try to
output it, but the rest seems reasonably sensible.

> Actually, this is pretty much exactly Florian's idea (thanks again,
> Florian), but at the time I didn't like it because "pair" didn't capture
> everything that I wanted to capture, like infinite bounds, etc. But
> there's no reason that it can't, and your point made me realize that --
> you are effectively just using TEXT as the intermediate type (which
> works, but has some undesirable characteristics).

What undesirable characteristics?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed
Next
From: Andrew Dunstan
Date:
Subject: Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed