| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Andreas Joseph Krogh <andreak(at)officenet(dot)no> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Why is NULL = unbounded for rangetypes? |
| Date: | 2013-09-01 17:51:33 |
| Message-ID: | 1378057893.21540.18.camel@jdavis |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 2013-08-30 at 11:22 +0200, Andreas Joseph Krogh wrote:
> But I agree that returning NULL would be OK, then it would be easy to
> catch in queries when starting playing with range-types in queries.
> Having it implicitly mean infinity comes as a surprise, to me at
> least.
Agreed. This was discussed at the time, and the original version of
Range Types experimented with other means of specifying unbounded ranges
in order to avoid this possible confusion.
Unfortunately, everything we tried was awkward one way or another; and
we eventually made the decision to go with greater convenience, even if
it could cause some confusion.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2013-09-01 18:01:11 | Re: Adding ip4r to Postgresql core? |
| Previous Message | Jeff Davis | 2013-09-01 17:35:57 | Re: Dump/Reload pg_statistic to cut time from pg_upgrade? |