Timeline for Optimizing a MySQL "IN" query
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2020 at 9:05 | history | edited | CommunityBot |
Commonmark migration
|
|
| Apr 13, 2017 at 12:42 | history | edited | CommunityBot |
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
|
|
| Dec 12, 2015 at 13:21 | vote | accept | Scott Deerwester | ||
| Dec 4, 2015 at 20:59 | comment | added | RolandoMySQLDBA | Based on the comment on the values, anyone of those TTY values will trigger a table scan. Please try out other values besides those nine TTYs. | |
| Dec 4, 2015 at 20:49 | comment | added | Scott Deerwester | Empty set (0.63 sec) | |
| Dec 4, 2015 at 20:36 | history | edited | RolandoMySQLDBA | CC BY-SA 3.0 |
added 7 characters in body
|
| Dec 4, 2015 at 20:35 | comment | added | paparazzo | @jkavalik We don't know but this is worth a try | |
| Dec 4, 2015 at 20:35 | history | edited | RolandoMySQLDBA | CC BY-SA 3.0 |
added 532 characters in body
|
| Dec 4, 2015 at 20:10 | comment | added | jkavalik | We don!t know the reason yet.. If the reason was very long IN list and/or the values covering a big part of the table, then all those unions might take more time than a table scan.. And if it was quoting mismatch then it is just not necessary. | |
| Dec 4, 2015 at 20:02 | history | answered | RolandoMySQLDBA | CC BY-SA 3.0 |