| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Jean-Christophe BOGGIO <postgresql(at)thefreecat(dot)org>, Torsten Förtsch <tfoertsch123(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Strange behaviors with ranges |
| Date: | 2024-08-27 18:27:42 |
| Message-ID: | cbf220ba-469d-4dc2-9231-14457c4e9ad1@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 8/27/24 11:16 AM, Adrian Klaver wrote:
>
>
> On 8/27/24 11:13 AM, Jean-Christophe BOGGIO wrote:
>> Le 27/08/2024 à 19:51, Torsten Förtsch a écrit :
>>> I guess this query comes back non-empty:
>>>
>>> SELECT * FROM paliers JOIN tmp_limitcontrats USING(idcontrat) WHERE
>>> qtep1 >= qtep2
>>
>> Yes, it is empty if I keep tmp_limitcontrats to idcontrat=1003
>>
>> Otherwise, you are right, there are irregular data but not that I'm
>> concerned with in that particular case.
>>
>
> ?:
> SELECT numrange( qtep1+1 , qtep2, '[]') AS rangep FROM paliers JOIN
> tmp_limitcontrats USING(idcontrat) where qtep1+1 < qtep2
>
Actually that should be:
qtep1+1 <= qtep2
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Christophe BOGGIO | 2024-08-27 19:54:24 | Re: Strange behaviors with ranges |
| Previous Message | Adrian Klaver | 2024-08-27 18:16:57 | Re: Strange behaviors with ranges |