From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Range Types, constructors, and the type system |
Date: | 2011-06-28 14:58:14 |
Message-ID: | BANLkTimW6cpAi7BNPGgqSn3Z9je7io6GfQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 27, 2011 at 11:42 PM, Jeff Davis <pgsql(at)j-davis(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2011-06-28 15:00:54 | Re: [v9.2] Fix leaky-view problem, part 1 |
Previous Message | Joe Conway | 2011-06-28 14:52:58 | Re: pgsql: Branch refs/heads/REL9_1_STABLE was removed |