| From: | Florian Pflug <fgp(at)phlo(dot)org> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Range Types - typo + NULL string constructor |
| Date: | 2011-09-22 00:40:29 |
| Message-ID: | 1DD0DC02-6FAA-444A-B2A8-1CE04A677059@phlo.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-09-22 00:42:58 | Re: citext operator precedence fix |
| Previous Message | Robert Haas | 2011-09-22 00:35:02 | Re: [v9.2] make_greater_string() does not return a string in some cases |