From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: WIP: RangeTypes |
Date: | 2011-01-18 00:09:12 |
Message-ID: | 4D34DA28.4000703@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 1/17/11 1:09 PM, Jeff Davis wrote:
> I feel like I'm making this too complicated. Should I just scope out
> NULL range boundaries for the first cut, and leave room in the
> representation so that it can be added when there is a more thorough
> proposal for NULL range boundaries?
Well, NULL range boundaries aren't usable with Temporal, and yet I wrote
a whole scheduling application around it. So I think it's OK to have
them as a TODO and raise an error for now. Heck, we had arrays which
didn't accept NULLs for years.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2011-01-18 00:14:23 | Re: Moving test_fsync to /contrib? |
Previous Message | Tom Lane | 2011-01-17 23:59:14 | Re: WIP: RangeTypes |