Problem description

Here is a screenshot of the error:

1140 - In aggregated query without GROUP BY, expression
 #1 of SELECT list contains nonaggregated column 'supermarket.Order.Province';
  this is incompatible with sql_mode=only_full_group_by

Translated: In an aggregation query without group BY, expression #1 of the SELECT list contains a non-aggregated column’
The reason is: when the sql_mode of mysql is only_full_group_by, if the group by is not used and the aggregate function appears after the select, then all selected should be the aggregate function, otherwise an error will be reported.

Problem traceability

There is a STRICT mode in mysql5.7 or above, and in this mode, the default setting of the date value is not allowed to be all 0 values. Therefore, to solve this problem, you need to modify the value of sql_mode.

Solution 1

This solution is a quick solution of two commands. MySQL will be invalid after restarting (can be understood as temporary)

select version(), @@sql_mode;

SET sql_mode=(SELECT REPLACE(@@sql_mode,'ONLY_FULL_GROUP_BY',''));

Check it out again:select version(), @@sql_mode;

Then enter our command to test
Here is the corresponding SQL statement

SELECT
  `province`,
	`City`,
	SUM(`Sales`) as  Total sales
FROM
	 	Order   
ORDER BY
	 Province

The mission is done!

Solution 2

Find the mysql configuration file
my.ini

The ones under Linux are also very different, just find the corresponding configuration directory ~

After saving the file, use the command line to restart the MySQL database service:

Stop/start: net stop mysql/net start mysql

After execution, execute in the database

set @@global.sql_mode = `STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION`;

This is executed in navicat, the effect is the same ~

In useselect @@global.sql_modeONLY_FULL_GROUP_BY does not exist in the query result

Write to our SQL language and execute perfectly~

appendix:

An introduction to several common SQL_mode values ​​is attached:

 Several commonmodeintroduce 

ONLY_FULL_GROUP_BY：
 Appear inselectStatement,HAVINGConditions andORDER BYThe column in the statement must beGROUP BYor depend onGROUP BYcolumn function column. 

NO_AUTO_VALUE_ON_ZERO：
 This value affects the insertion of the self-growing column. Under default settings, insert0orNULLRepresents the generation of the next self-growth value. If the user
 The value you want to insert is0, and the column is self-growing, then this option is useful. 

STRICT_TRANS_TABLES：
 In this mode, if a value cannot be inserted into a transaction table, the current operation will be interrupted and no restrictions will be imposed on non-transaction tables

NO_ZERO_IN_DATE：
 This mode affects whether the month and day in the date are allowed to be included0. If this mode is enabled,2016-01-00It is not allowed, but0000-02-01It is allowed. Its actual behavior is subject to strict modeImpact of whether it is turned on1。

NO_ZERO_DATE：
 Set this value, the mysql database does not allow insertion of zero dates. Its actual behavior is subject to strict
modeImpact of whether it is turned on2。

ERROR_FOR_DIVISION_BY_ZERO：
 existINSERTorUPDATEDuring the process, if the data is divided by zero, an error rather than a warning is generated. like 
 If this pattern is not given, MySQL returns when the data is divided by zero.NULL

NO_AUTO_CREATE_USER：
 prohibitGRANTCreate a user with empty password

NO_ENGINE_SUBSTITUTION：
 If the required storage engine is disabled or not compiled, an error is thrown. If this value is not set, use the default storage engine instead and throw an exception

PIPES_AS_CONCAT：
 Will"||"Be regarded as a string concatenation operator rather than a or operator, which is the same as Oracle database and is also similar to the string concatenation function Concat

ANSI_QUOTES：
 After ANSI_QUOTES is enabled, strings cannot be quoted in double quotes because they are interpreted as identifiers