0

在 SQL 模式“ STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION”的 MySQL 5.6.13 中，以下查询可以正常工作，但会出现警告：

UPDATE Company SET company_CurrentYearValueGBP = COALESCE((
SELECT SUM(
(COALESCE(salesdata_Month01Amount,0) / IF(salesdata_ExchangeRate<>'',salesdata_ExchangeRate,1) ) + 
(COALESCE(salesdata_Month02Amount,0) / IF(salesdata_ExchangeRate<>'',salesdata_ExchangeRate,1) ) + 
(COALESCE(salesdata_Month03Amount,0) / IF(salesdata_ExchangeRate<>'',salesdata_ExchangeRate,1) ) + 
(COALESCE(salesdata_Month04Amount,0) / IF(salesdata_ExchangeRate<>'',salesdata_ExchangeRate,1) ) + 
(COALESCE(salesdata_Month05Amount,0) / IF(salesdata_ExchangeRate<>'',salesdata_ExchangeRate,1) ) + 
(COALESCE(salesdata_Month06Amount,0) / IF(salesdata_ExchangeRate<>'',salesdata_ExchangeRate,1) ) + 
(COALESCE(salesdata_Month07Amount,0) / IF(salesdata_ExchangeRate<>'',salesdata_ExchangeRate,1) ) + 
(COALESCE(salesdata_Month08Amount,0) / IF(salesdata_ExchangeRate<>'',salesdata_ExchangeRate,1) ) + 
(COALESCE(salesdata_Month09Amount,0) / IF(salesdata_ExchangeRate<>'',salesdata_ExchangeRate,1) ) + 
(COALESCE(salesdata_Month10Amount,0) / IF(salesdata_ExchangeRate<>'',salesdata_ExchangeRate,1) ) + 
(COALESCE(salesdata_Month11Amount,0) / IF(salesdata_ExchangeRate<>'',salesdata_ExchangeRate,1) ) + 
(COALESCE(salesdata_Month12Amount,0) / IF(salesdata_ExchangeRate<>'',salesdata_ExchangeRate,1) ) + 
0) FROM SalesData 
WHERE salesdata_SalesDataTypeID = 3 
AND salesdata_CompanyID = company_ID 
AND salesdata_SalesYearID = 6 
AND NOT salesdata_IsBeingProcessed 
),0)

输出：

0 row(s) affected, 5 warning(s):
 1265 Data truncated for column 'company_CurrentYearValueGBP' at row 127
 1265 Data truncated for column 'company_CurrentYearValueGBP' at row 127
 1265 Data truncated for column 'company_CurrentYearValueGBP' at row 127
 1265 Data truncated for column 'company_CurrentYearValueGBP' at row 127
 1265 Data truncated for column 'company_CurrentYearValueGBP' at row 127
 Rows matched: 1470  Changed: 0  Warnings: 5

在 SQL 模式“ STRICT_TRANS_TABLES”的 MySQL 5.7.14 中，相同的查询正在创建以下错误：

Error Code: 1292. Truncated incorrect DECIMAL value: ''

我理解为什么会发生错误（因为比较 salesdata_ExchangeRate<>''），但是任何人都可以解释为什么在 MySQL 5.6 中即使启用了严格模式，查询只会产生警告而不是因错误而中止？两个版本之间的行为似乎不同。

更新 1 在 MySQL 5.6.13 和 MySQL 5.7.14 上创建了一个具有以下结构的简单表：

结构

添加了以下记录：

记录

运行以下查询会在 MySQL 5.7.14 中重现相同的错误：

UPDATE testtable 
SET testtable_CalculatedValue = IF(testtable_DecimalValue<>'',testtable_DecimalValue,0) 
WHERE testtable_ID > 0

Error Code: 1292. Truncated incorrect DECIMAL value: ''

在 MySQL 5.6.13 中，testtable_CalculatedValue 按预期设置为 1.35。

4

1 回答 1

0

设置：

mysql> CREATE TABLE so53868586 (
         id INT AUTO_INCREMENT,
         deci  DECIMAL(12,2) DEFAULT NULL,
         calc DECIMAL(12,2) DEFAULT NULL,
         PRIMARY KEY(id)
     ) ENGINE=InnoDB;
Query OK, 0 rows affected (0.02 sec)

mysql> SET @@sql_mode = "STRICT_TRANS_TABLES";
Query OK, 0 rows affected (0.00 sec)

mysql> INSERT INTO so53868586 (deci)
         VALUES (1.35), (NULL), (0), (12345);
Query OK, 4 rows affected (0.00 sec)
Records: 4  Duplicates: 0  Warnings: 0

测试

mysql> SELECT * FROM so53868586;
+----+----------+------+
| id | deci     | calc |
+----+----------+------+
|  1 |     1.35 | NULL |
|  2 |     NULL | NULL |
|  3 |     0.00 | NULL |
|  4 | 12345.00 | NULL |
+----+----------+------+
4 rows in set (0.00 sec)

mysql> 
mysql> UPDATE so53868586 SET calc = IF(deci <> 0, deci, 0)
         WHERE id > 0;
Query OK, 4 rows affected (0.00 sec)
Rows matched: 4  Changed: 4  Warnings: 0

mysql> 
mysql> SELECT * FROM so53868586;
+----+----------+----------+
| id | deci     | calc     |
+----+----------+----------+
|  1 |     1.35 |     1.35 |
|  2 |     NULL |     0.00 |
|  3 |     0.00 |     0.00 |
|  4 | 12345.00 | 12345.00 |
+----+----------+----------+
4 rows in set (0.01 sec)

（那是使用 5.6.22。）

5.7.15 得到了相同的结果，但抱怨SET @sql_mode与

mysql> show warnings;
+---------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Level   | Code | Message                                                                                                                                                                 |
+---------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Warning | 3135 | 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release. |
| Warning | 3090 | Changing sql mode 'NO_AUTO_CREATE_USER' is deprecated. It will be removed in a future release.                                                                          |
+---------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

我是否未能重现您的测试用例？

我在 5.7.15（或附近的任何地方）的变更日志中看不到任何相关内容，但您可以考虑更新。（5.7.14 是 2 年前发布的。）

于 2019-01-02T20:21:01.780 回答