| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Adam Jensen <hanzer(at)riseup(dot)net>, pgsql-sql(at)lists(dot)postgresql(dot)org |
| Subject: | Re: interval origami |
| Date: | 2018-12-01 13:24:25 |
| Message-ID: | eed7d93d-2db6-c5af-8623-fa5f492b2e4d@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On 11/30/18 4:02 PM, Adam Jensen wrote:
> On 11/30/18 3:19 PM, Adam Jensen wrote:
>> The 'numrange' type with the 'overlaps' and 'intersection' operators
>> seem to cover the fundamental computations in a very natural way.
>
> Actually, those operators might not be entirely sufficient. Given two
> ranges like this:
>
> 10.0|39.0|interesting
> 15.0|21.0|fail
>
> Something like the negative or inverse of the intersection is needed:
>
> 10.0|15.0|interesting
> 21.0|39.0|interesting
Perhaps overkill, but if you represent your timeline as actual line
segments, perhaps PostGIS would be useful. E.g.:
https://postgis.net/docs/manual-2.5/ST_Difference.html
HTH,
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Jensen | 2018-12-01 20:37:46 | Re: interval origami |
| Previous Message | Adam Jensen | 2018-12-01 00:45:35 | Re: interval origami |