From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, jani(dot)rahkola(at)iki(dot)fi, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Documentation of return values of range functions lower and upper |
Date: | 2020-11-18 13:49:10 |
Message-ID: | 27d690d8-0987-5f2b-a2da-fc2ec7c19e3c@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 2020/11/12 17:14, Laurenz Albe wrote:
> On Wed, 2020-11-11 at 18:19 +0100, Laurenz Albe wrote:
>>> Table 9.54 in page
>>> https://www.postgresql.org/docs/current/functions-range.html states that the
>>> functions lower and upper return NULL if the requested bound is infinite. If
>>> the element type of the range contains the special values infinity and
>>> -infinity, this is not correct, as those values are returned if explicitly
>>> used as either bound.
>>
>> +1
>>
>> Perhaps it would be better to say
>>
>> NULL if the range is empty or has no lower/upper bound
I agree this description looks a bit confusing. But according to the section
"Infinite (Unbounded) Ranges" (*1), we already call "lower/upper bound
omitted" just infinite. So I don't think the current description is incorrect.
(*1)
https://www.postgresql.org/docs/devel/rangetypes.html#RANGETYPES-INFINITE
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2020-11-18 16:28:44 | Re: Documentation of return values of range functions lower and upper |
Previous Message | David G. Johnston | 2020-11-16 22:00:22 | Re: timed messages |