Horton

Re: Range Types - typo + NULL string constructor

Florian G. Pflug <fgp@phlo.org>

View thread
From: Florian Pflug <fgp@phlo.org>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Erik Rijkers <er@xs4all.nl>, pgsql-hackers@postgresql.org
Date: 2011-09-22T00:40:29Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Replace the "New Linear" GiST split algorithm for boxes and points with a

On Sep21, 2011, at 19:02 , Jeff Davis wrote:
> On Wed, 2011-09-21 at 13:24 +0200, Florian Pflug wrote:
>> I've thought about this some more, and came to realize that the question
>> here really is whether
>> 
>>  floatrange(0, 'Infinity'::float, '[)')
>> 
>> and
>> 
>>  floatrange(0, NULL, '[)')
>> 
>> are the same thing or not.
> 
> The unbounded side of a range is never equal to a value in the data
> type's domain, so no, it's not the same.
> 
> I think that we pretty much settled on just using an empty string for
> infinity in the other thread, right? So that makes this a non-issue.

Agreed.

best regards,
Florian Pflug