| 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:16:57 |
| Message-ID: | 41e2ee2e-3f27-4f2c-86b0-8252411fdc75@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-08-27 18:27:42 | Re: Strange behaviors with ranges |
| Previous Message | Jean-Christophe BOGGIO | 2024-08-27 18:13:46 | Re: Strange behaviors with ranges |