Timeline for MySQL Grouping Error
Current License: CC BY-SA 3.0
11 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/
|
|
| Apr 13, 2017 at 12:13 | history | edited | CommunityBot |
replaced http://serverfault.com/ with https://serverfault.com/
|
|
| Aug 6, 2013 at 16:56 | comment | added | RolandoMySQLDBA |
Even if they are strings, as long as the format of the timestamp is maintained as YYY-MM-DDTHH:MM:SS, and the column is indexed as @ypercube hinted at, you should be fine.
|
|
| Aug 6, 2013 at 16:54 | comment | added | Jacobm001 | @RolandoMySQLDBA: No problem, thanks for a shot in the dark. I often hesitate to do on other sites because people love their down-votes! Can I actually use the greater/less than statements here? The data is unfortunately not stored as a date, but rather as an indexed varchar. | |
| Aug 6, 2013 at 16:48 | history | edited | RolandoMySQLDBA | CC BY-SA 3.0 |
added 22 characters in body
|
| Aug 6, 2013 at 16:45 | comment | added | ypercubeᵀᴹ |
I suggest you also change the R.usageWhen LIKE "2012-07-08T12:%" to (R.usageWhen >= '2012-07-08T12:00:00' AND R.usageWhen < '2012-07-08T13:00:00') so index use is possible.
|
|
| Aug 6, 2013 at 16:41 | comment | added | Jacobm001 | It's not the answer, but it got me to the answer. Apparently, each computer is listed under every division. ARGH! | |
| Aug 6, 2013 at 16:41 | vote | accept | Jacobm001 | ||
| Aug 6, 2013 at 16:41 | history | edited | RolandoMySQLDBA | CC BY-SA 3.0 |
added 22 characters in body
|
| Aug 6, 2013 at 16:35 | history | answered | RolandoMySQLDBA | CC BY-SA 3.0 |