遇见 mysql Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggre 问题

这是因为mysql5.7及以上版本的mysql中,对于 group by 的这种聚合操作,如果在select 中的列,
没有在group by 中出现,那么这个SQL是不合法的,因为列不在group by的从句中,所以对于设置了这个mode的数据库,在使用group by 的时候,就要用MAX(),SUM(),ANT_VALUE()的这种聚合函数,才能完成GROUP BY 的聚合操作。

查询以后发现是因为only_full_group_by设置的原因,下边我们将其进行关闭:

1. 第一种的解决办法是直接在mysql中进行设置,如下:
mysql> select @@global.sql_mode;
+-----------------------------------------------------------------------------------------------------------------------+
| @@global.sql_mode                                                                                                     |
+-----------------------------------------------------------------------------------------------------------------------+
| ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION |
+-----------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

在这里插入图片描述

mysql> SET @@global.sql_mode ='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION’;

将@@global.sql_mode重新设置后,再进行查询:

mysql> SELECT @@GLOBAL.sql_mode;
+----------------------------------------------------------------------------------------------------+
| @@GLOBAL.sql_mode                                                                                  |
+----------------------------------------------------------------------------------------------------+
| STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION |
+----------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

注:mysql8没有NO_AUTO_CREATE_USER这个模式;这种方式有个缺陷数据库每次重启都会恢复到之前的模式

4.第二种方式:修改配置文件

创建my.cnf文件,vim /etc/my.cnf,将下边的内容拷贝到my.cnf中。

# Example MySQL config file for medium systems.  
  #  
  # This is for a system with little memory (32M - 64M) where MySQL plays  
  # an important part, or systems up to 128M where MySQL is used together with  
  # other programs (such as a web server)  
  #  
  # MySQL programs look for option files in a set of  
  # locations which depend on the deployment platform.  
  # You can copy this option file to one of those  
  # locations. For information about these locations, see:  
  # http://dev.mysql.com/doc/mysql/en/option-files.html  
  #  
  # In this file, you can use all long options that a program supports.  
  # If you want to know which options a program supports, run the program  
  # with the "--help" option.  
  # The following options will be passed to all MySQL clients  
  [client]
  default-character-set=utf8
  #password   = your_password  
  port        = 3306  
  socket      = /tmp/mysql.sock   
  # Here follows entries for some specific programs  
  # The MySQL server  
  [mysqld]
  sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION'
  character-set-server=utf8
  init_connect='SET NAMES utf8
  port        = 3306  
  socket      = /tmp/mysql.sock  
  skip-external-locking  
  key_buffer_size = 16M  
  max_allowed_packet = 1M  
  table_open_cache = 64  
  sort_buffer_size = 512K  
  net_buffer_length = 8K  
  read_buffer_size = 256K  
  read_rnd_buffer_size = 512K  
  myisam_sort_buffer_size = 8M  
  character-set-server=utf8  
  init_connect='SET NAMES utf8' 
# Don't listen on a TCP/IP port at all. This can be a security enhancement,  
# if all processes that need to connect to mysqld run on the same host.  
# All interaction with mysqld must be made via Unix sockets or named pipes.  
# Note that using this option without enabling named pipes on Windows  
# (via the "enable-named-pipe" option) will render mysqld useless!  
#   
#skip-networking  
 
  # Replication Master Server (default)  
  # binary logging is required for replication  
  log-bin=mysql-bin  
 
    # binary logging format - mixed recommended  
    binlog_format=mixed  
 
      # required unique id between 1 and 2^32 - 1  
      # defaults to 1 if master-host is not set  
      # but will not function as a master if omitted  
      server-id   = 1  
 
    # Replication Slave (comment out master section to use this)  
    #  
    # To configure this host as a replication slave, you can choose between  
    # two methods :  
    #  
    # 1) Use the CHANGE MASTER TO command (fully described in our manual) -  
    #    the syntax is:  
    #  
    #    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,  
    #    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;  
    #  
    #    where you replace <host>, <user>, <password> by quoted strings and  
    #    <port> by the master's port number (3306 by default).  
    #  
    #    Example:  
    #  
    #    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,  
    #    MASTER_USER='joe', MASTER_PASSWORD='secret';  
    #  
    # OR  
    #  
    # 2) Set the variables below. However, in case you choose this method, then  
    #    start replication for the first time (even unsuccessfully, for example  
    #    if you mistyped the password in master-password and the slave fails to  
    #    connect), the slave will create a master.info file, and any later  
    #    change in this file to the variables' values below will be ignored and  
    #    overridden by the content of the master.info file, unless you shutdown  
    #    the slave server, delete master.info and restart the slaver server.  
    #    For that reason, you may want to leave the lines below untouched  
    #    (commented) and instead use CHANGE MASTER TO (see above)  
    #  
    # required unique id between 2 and 2^32 - 1  
    # (and different from the master)  
    # defaults to 2 if master-host is set  
    # but will not function as a slave if omitted  
    #server-id       = 2  
    #  
    # The replication master for this slave - required  
    #master-host     =   <hostname>  
    #  
    # The username the slave will use for authentication when connecting  
    # to the master - required  
    #master-user     =   <username>  
    #  
    # The password the slave will authenticate with when connecting to  
    # the master - required  
    #master-password =   <password>  
    #  
    # The port the master is listening on.  
    # optional - defaults to 3306  
    #master-port     =  <port>  
    #  
    # binary logging - not required for slaves, but recommended  
    #log-bin=mysql-bin  
 
      # Uncomment the following if you are using InnoDB tables  
      #innodb_data_home_dir = /usr/local/mysql/data  
      #innodb_data_file_path = ibdata1:10M:autoextend  
      #innodb_log_group_home_dir = /usr/local/mysql/data  
      # You can set .._buffer_pool_size up to 50 - 80 %  
      # of RAM but beware of setting memory usage too high  
      #innodb_buffer_pool_size = 16M  
      #innodb_additional_mem_pool_size = 2M  
      # Set .._log_file_size to 25 % of buffer pool size  
      #innodb_log_file_size = 5M  
      #innodb_log_buffer_size = 8M  
      #innodb_flush_log_at_trx_commit = 1  
      #innodb_lock_wait_timeout = 50  
 
        [mysqldump]  
        quick  
        max_allowed_packet = 16M  
 
          [mysql]  
          no-auto-rehash  
          # Remove the next comment character if you are not familiar with SQL  
          #safe-updates  
          default-character-set=utf8   
 
        [myisamchk]  
        key_buffer_size = 20M  
        sort_buffer_size = 20M  
        read_buffer = 2M  
        write_buffer = 2M  
 
          [mysqlhotcopy]  
          interactive-timeout
————————————————   

此配置已经做好了设置,直接使用即可,就是直接多加下边这一行配置:

在这里插入图片描述

2.2 重启mysql服务,再次查看:

在这里插入图片描述

3.成功~~
### 问题分析 MySQL版本5.7及之后,默认启用了`sql_mode=only_full_group_by`模式[^2]。该模式要求在`GROUP BY`子句中,所有非聚合字段必须出现在`GROUP BY`列表中,或者这些字段必须是函数依赖的。如果违反这一规则,就会出现类似`Expression #2 of SELECT list is not in GROUP BY clause and contains nonaggregated column`的错误。 以下是解决此问题的详细方法: --- ### 解决方案 #### 方法一:修改SQL查询语句 通过调整SQL查询语句,确保所有非聚合字段都包含在`GROUP BY`子句中。例如: ```sql SELECT column1, column2, column3, COUNT(*) FROM table_name GROUP BY column1, column2, column3; ``` 上述查询语句将`column1`, `column2`, 和`column3`添加到`GROUP BY`子句中,从而满足`ONLY_FULL_GROUP_BY`的要求[^2]。 --- #### 方法二:禁用`ONLY_FULL_GROUP_BY`模式 可以通过修改MySQL的配置文件或临时更改`sql_mode`来禁用`ONLY_FULL_GROUP_BY`模式。 **步骤:** 1. **查找MySQL配置文件** 在Windows系统中,配置文件通常位于`C:/ProgramData/MySQL/MySQL Server x.x/my.ini`[^3];在Linux系统中,配置文件可能位于`/etc/mysql/my.cnf`或`/etc/my.cnf`。 2. **编辑配置文件** 打开配置文件,找到`sql_mode`设置行。例如: ```ini sql_mode = ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,... ``` 将`ONLY_FULL_GROUP_BY`从`sql_mode`中移除。修改后的内容如下: ```ini sql_mode = STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,... ``` 3. **重启MySQL服务** 在命令行中执行以下命令以重启MySQL服务(Windows示例): ```bash net stop mysql net start mysql ``` 或者直接重启计算机以确保配置生效。 4. **验证更改** 登录MySQL并运行以下命令,确认`sql_mode`中不再包含`ONLY_FULL_GROUP_BY`: ```sql SELECT @@sql_mode; ``` --- #### 方法三:使用`ANY_VALUE()`函数 MySQL提供了`ANY_VALUE()`函数,用于明确指定某些字段可以忽略`ONLY_FULL_GROUP_BY`的限制。例如: ```sql SELECT column1, ANY_VALUE(column2), COUNT(*) FROM table_name GROUP BY column1; ``` 在此示例中,`column2`被包装在`ANY_VALUE()`函数中,表示即使它不在`GROUP BY`子句中,也可以安全地使用[^2]。 --- ### 注意事项 - 修改数据库配置文件会影响整个数据库实例的行为,需谨慎操作。 - 如果选择禁用`ONLY_FULL_GROUP_BY`模式,可能会导致查询结果不一致,特别是在数据存在多值的情况下[^3]。 - 推荐优先考虑修改SQL查询语句以符合标准,而不是禁用严格模式。 --- ### 示例代码 以下是一个完整的示例,展示如何解决`Expression #2`错误: ```sql -- 原始查询(报错) SELECT category, product_name, price, COUNT(*) FROM products GROUP BY category; -- 修改后的查询(方法一:添加所有非聚合字段到GROUP BYSELECT category, product_name, price, COUNT(*) FROM products GROUP BY category, product_name, price; -- 修改后的查询(方法三:使用ANY_VALUE()函数) SELECT category, ANY_VALUE(product_name), ANY_VALUE(price), COUNT(*) FROM products GROUP BY category; ``` ---
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值