Timeline for Getting this SQL Error: GROUP BY incompatible with sql_mode=only_full_group_by
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 29, 2019 at 11:00 | comment | added | KSPR | This is the easiest solution to get it running if you work localy on MAMP | |
| May 8, 2018 at 22:18 | comment | added | Brad Bell♦ |
@biko, if you're using initSQLs, it will execute whatever the value is on every request no matter the MySQL version.
|
|
| May 8, 2018 at 9:42 | comment | added | biko | @BradBell Just curious.. does the initSQLs solution still run an extra query even if we are running MySQL5.6? | |
| Jun 22, 2017 at 18:02 | comment | added | ingernet |
HEADS UP to Cloud SQL users - when you config the DB in the GCP console, the sql_mode flag is a drop-down menu, and only accepts one value. I found out from this blog page that TRADITIONAL may work as an alias for the strict values you want, and none of the strict values you don't want. More on TRADITIONAL on the MySQL 5.7 reference page.
|
|
| Mar 30, 2017 at 22:34 | comment | added | mention79 | None of the solutions suggested are working for me. Is there any new issues as to why? My site is mentiondesign.co.uk | |
| Jan 19, 2017 at 9:40 | comment | added | Alexander Holsgrove | Thanks, the initSQLs allowed me to carry on working without having to mess about installing an older MySQL version or updating Craft to 3.x | |
| Sep 29, 2016 at 22:39 | history | edited | Brad Bell♦ | CC BY-SA 3.0 |
added 793 characters in body
|
| Jul 5, 2016 at 0:22 | comment | added | Routhinator | "Impractical to backport" - Then don't. Best practice for Mysql 5.7 is to set the sqlmode in your DB drive on connect. Craft installations should not require setting this on the entire database instance in my.cnf, which is terrible practice. You should be implementing the one line change required to set this when you call the database connection. dev.mysql.com/doc/refman/5.7/en/sql-mode.html | |
| May 12, 2016 at 0:47 | comment | added | Brad Bell♦ | @adrienne It gets messy because the query is so dynamic. Element types can set any custom select and order by values, so those would have to be wrapped in ANY_VALUE depending on what the GROUP BY specifies. | |
| May 11, 2016 at 23:24 | comment | added | adrienne | Brad, you might be able to do a check for whether the server is running 5.7.5+ and add ANY_VALUE() to your columns if so? dev.mysql.com/doc/refman/5.7/en/… | |
| Apr 28, 2016 at 3:24 | comment | added | Luke Holder | Another reference: mattstauffer.co/blog/… | |
| Jan 18, 2016 at 19:36 | history | edited | Brad Bell♦ | CC BY-SA 3.0 |
added 2 characters in body
|
| Jan 13, 2016 at 3:04 | comment | added | Brad Bell♦ | Fair enough! Added a note to craftcms.com/docs/requirements | |
| Jan 12, 2016 at 9:13 | comment | added | Tom Davies | This bit me today and feels important enough to me that it should be mentioned in the main Craft install docs somewhere, especially as MySQL 5.7.5+ usage is on the up (I hit this with a box provisioned via Laravel Forge) | |
| Oct 26, 2015 at 17:19 | history | answered | Brad Bell♦ | CC BY-SA 3.0 |