Timeline for Design database to query a date range for scheduling
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 7, 2020 at 22:23 | history | edited | CommunityBot |
added [query-performance] to 2412 questions - Shog9 (Id=1924)
|
|
Apr 13, 2017 at 12:42 | history | edited | CommunityBot |
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
|
|
Dec 21, 2012 at 15:43 | vote | accept | Hernán Eche | ||
Dec 14, 2012 at 14:58 | history | edited | Hernán Eche | CC BY-SA 3.0 |
typo
|
Dec 14, 2012 at 14:42 | answer | added | Mike Sherrill 'Cat Recall' | timeline score: 2 | |
Dec 14, 2012 at 14:12 | comment | added | Hernán Eche | @ypercube it depends, on the first approach the table will contain id's and date ranges, etc, for same id (because there are multiple ranges for every id) so ranges will not overlap, but of course they will overlap for different id's. In the second approach they will not overlap by design because the idea is to identify (on insert) if the range was already used (slow insert) and assign a unique id for that range to reuse in the first table. | |
Dec 14, 2012 at 14:04 | review | First posts | |||
Dec 14, 2012 at 14:18 | |||||
Dec 14, 2012 at 14:00 | comment | added | ypercubeᵀᴹ |
Will the (begin_time, end_time) intervals overlap or not?
|
|
Dec 14, 2012 at 13:49 | history | asked | Hernán Eche | CC BY-SA 3.0 |