Timeline for How to run my query on a one-to-many relation to run efficiently
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 15, 2020 at 18:56 | history | edited | Vajk Hermecz | CC BY-SA 4.0 |
Added in missing data field and sample generation for vehicle table
|
| Sep 15, 2020 at 18:48 | vote | accept | Vajk Hermecz | ||
| Sep 15, 2020 at 18:47 | vote | accept | Vajk Hermecz | ||
| Sep 15, 2020 at 18:48 | |||||
| Sep 11, 2020 at 12:52 | history | edited | Vajk Hermecz | CC BY-SA 4.0 |
Fixing table names in examples
|
| Sep 9, 2020 at 23:34 | answer | added | jjanes | timeline score: 1 | |
| Sep 9, 2020 at 23:29 | comment | added | jjanes | You should make your example runnable by using the same table names throughout it, and referencing only columns you create. Also, your select seems to be missing the central "order by". | |
| Sep 9, 2020 at 19:15 | comment | added | Akina | A subquery with GROUP BY kills the ability to use the index effectively. Do backward - join then group. | |
| Sep 9, 2020 at 19:09 | history | asked | Vajk Hermecz | CC BY-SA 4.0 |