Timeline for query optimization: time intervals
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 12, 2013 at 19:42 | comment | added | Nico | alright, i got your point. in case of intersecting intervals in one table, results got mad. will check this. | |
| Feb 12, 2013 at 19:31 | comment | added | Nico | I checked this out again, see this fiddle which has completely overlapping intervals in all three tables. it returns correct results, as i can see. could you provide a case in which wrong results are returned? feel free to adjust demo data in fiddle! | |
| Feb 12, 2013 at 16:04 | comment | added | ErikE | I have another idea I haven't had time to get working. For what it's worth, your query returns wrong results with overlapping ranges in all tables. | |
| Feb 12, 2013 at 15:23 | comment | added | Nico | Runtime is definetely much higher than 1st approach. I had no time to check if further indices may decrease it yet. Will check as soon as possible! | |
| Feb 9, 2013 at 7:38 | history | answered | ErikE | CC BY-SA 3.0 |