Mysql版本導致GROUP BY分組異常
阿新 • • 發佈:2020-12-20
Mysql版本導致GROUP BY分組異常
一、異常資訊
Expression #2 of SELECT list is not in GROUP BY clause and contains nonaggregated column ‘ecpnew.m.id’ which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by
二、資料庫版本
版本 1
版本 2(出事版本)
三、SQL
select count(m.material_name) realSorageNumber ,m.*
from tb_material_inventory m
left join
tb_catalog c on m.catalog_buss_key = c.buss_key
where m.catalog_buss_key in (
SELECT
buss_key
FROM
(
SELECT
@ids AS _ids,
( SELECT @ids := GROUP_CONCAT( id ) FROM tb_catalog WHERE FIND_IN_SET( parent_id, @ids ) ) AS cids,
@l := @l + 1 AS LEVEL
FROM
tb_catalog,
( SELECT @ids := #{catalogId}, @l := 0 ) b
WHERE
@ids IS NOT NULL
) id,
tb_catalog DATA
WHERE
FIND_IN_SET( DATA.id, _ids )
ORDER BY
LEVEL,id
)
and m.warehouse_buss_key = #{bussKey}
GROUP BY m.catalog_buss_key
該處使用的url網路請求的資料。
四、解決方案
1、修改Mysql配置檔案(不建議採用)
原配置檔案
select @@global.sql_mode;
結果:ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
修改配置(將ONLY_FULL_GROUP_BY去掉)
set @@global.sql_mode ='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION';
2、修改SQL
MySQL也提供了any_value()函式來抑制ONLY_FULL_GROUP_BY值被拒絕
<select id="selectMaterialByRoot" resultType="com.luke.admin.entity.vo.MaterialInventoryVO">
select count(m.material_name) realSorageNumber , <include refid="anyValue"/>
from tb_material_inventory m
left join
tb_catalog c on m.catalog_buss_key = c.buss_key
where m.catalog_buss_key in (
SELECT
buss_key
FROM
(
SELECT
@ids AS _ids,
( SELECT @ids := GROUP_CONCAT( id ) FROM tb_catalog WHERE FIND_IN_SET( parent_id, @ids ) ) AS cids,
@l := @l + 1 AS LEVEL
FROM
tb_catalog,
( SELECT @ids := #{catalogId}, @l := 0 ) b
WHERE
@ids IS NOT NULL
) id,
tb_catalog DATA
WHERE
FIND_IN_SET( DATA.id, _ids )
ORDER BY
LEVEL,id
)
and m.warehouse_buss_key = #{bussKey}
GROUP BY m.catalog_buss_key
</select>
<sql id="anyValue">
any_value(m.id) as id ,
any_value(m.material_name) as material_name ,
any_value(m.catalog_buss_key) as catalog_buss_key,
any_value(m.catalog_name) as catalog_name,
any_value(m.rfid) as rfid,
any_value(m.warehouse_buss_key) as warehouse_buss_key,
any_value(m.warehouse_name) as warehouse_name,
any_value(m.manufacture_date) as manufacture_date,
any_value(m.expiration_date) as expiration_date,
any_value(m.model) as model,
any_value(m.storage_number) as storage_number,
any_value(m.reason_name) as reason_name,
any_value(m.storage_location) as storage_location,
any_value(m.specifications) as specifications,
any_value(m.material_img) as material_img,
any_value(m.material_type) as material_type,
any_value(m.factory_id) as factory_id,
any_value(m.factory_name) as factory_name,
any_value(m.material_state) as material_state,
any_value(m.batch) as batch,
any_value(m.company) as company,
any_value(m.create_time) as create_time,
any_value(m.update_time) as update_time,
any_value(m.description) as description
</sql>
五、總結
mysql5.7.x版本,預設是開啟了 only_full_group_by 模式的,但開啟這個模式後,原先的 group by 語句就報錯,關閉這個模式是不可取的。MySQL 5.7.5和up實現了對功能依賴的檢測。如果啟用了only_full_group_by SQL模式(在預設情況下是這樣),那麼MySQL就會拒絕選擇列表、條件或順序列表引用的查詢,這些查詢將引用組中未命名的非聚合列,而不是在功能上依賴於它們。