Timeline for How to select blocks with sequential data and aggregate the ids
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 23, 2019 at 15:36 | vote | accept | Attyla Fellipe | ||
| Jan 21, 2019 at 12:01 | comment | added | Attyla Fellipe | Yes, this is right! | |
| Jan 18, 2019 at 21:50 | history | edited | Erwin Brandstetter | CC BY-SA 4.0 |
fix tag, format, typos
|
| Jan 18, 2019 at 21:41 | comment | added | Erwin Brandstetter | If there was only one machine, would sequential IDs indicate a continuous block, no matter the actual gap between end & start, only interrupted by "planned" rows? | |
| Jan 18, 2019 at 21:37 | answer | added | Erwin Brandstetter | timeline score: 1 | |
| Jan 17, 2019 at 14:43 | answer | added | McNets | timeline score: 1 | |
| Jan 17, 2019 at 14:33 | comment | added | Attyla Fellipe | min & max date of each block! I just mention the difference of 3s between the endDate and the startDate of NEXT RECORD because this is the only criteria that I could think that makes the data sequential i.e how you can know that this record belongs to a specific block. | |
| Jan 17, 2019 at 14:26 | comment | added | McNets | Do you need min & max date of each block of un-planned id's or is it necessary to calculate date_diff of each row and consider a block those where enddate - stardate < 3 s? | |
| Jan 17, 2019 at 14:20 | history | edited | Attyla Fellipe | CC BY-SA 4.0 |
edited body
|
| Jan 17, 2019 at 14:05 | review | First posts | |||
| Jan 17, 2019 at 14:25 | |||||
| Jan 17, 2019 at 14:00 | history | asked | Attyla Fellipe | CC BY-SA 4.0 |