Timeline for SELECT with where between not working as expected
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 8, 2021 at 4:52 | comment | added | Freedo | you can delete your comments now. I'll remove this later | |
| Feb 4, 2021 at 19:45 | comment | added | Rick James |
@Freedo - Your example is caught between a rock and a hard space: Server names are arbitrary strings, yet the query is applying some "meaning" (namely 'C' followed by a number) to those strings. If it were "group C, server number 89", then having 2 columns would make the WHERE obvious and efficient. And "24H" could be another 'group' name. Freelance: mysql at rjweb dot org .
|
|
| Feb 4, 2021 at 7:51 | vote | accept | Freedo | ||
| Feb 4, 2021 at 7:42 | vote | accept | Freedo | ||
| Feb 4, 2021 at 7:51 | |||||
| Feb 3, 2021 at 19:04 | comment | added | Rick James |
@Freedo - There's a lot of TEXT columns; they may lead to performance issues (because of how large columns are stored 'off record'). Anyway, I added a 4th way to do the query; this is simple enough to explain to a DBA and depend on him to "meet the problem halfway" rather than depending on some complex SQL to do all the work.
|
|
| Feb 3, 2021 at 19:01 | history | edited | Rick James | CC BY-SA 4.0 |
added 390 characters in body
|
| Feb 3, 2021 at 17:30 | comment | added | Rick James |
@Freedo - Are there 3 ways to identify a server? id, server, and server_name?
|
|
| Feb 3, 2021 at 8:07 | history | edited | Rick James | CC BY-SA 4.0 |
added 155 characters in body
|
| Feb 2, 2021 at 16:19 | history | edited | Rick James | CC BY-SA 4.0 |
added 138 characters in body
|
| Feb 2, 2021 at 5:25 | review | Low quality posts | |||
| Feb 2, 2021 at 8:10 | |||||
| Feb 2, 2021 at 5:05 | history | answered | Rick James | CC BY-SA 4.0 |