视频1 视频21 视频41 视频61 视频文章1 视频文章21 视频文章41 视频文章61 推荐1 推荐3 推荐5 推荐7 推荐9 推荐11 推荐13 推荐15 推荐17 推荐19 推荐21 推荐23 推荐25 推荐27 推荐29 推荐31 推荐33 推荐35 推荐37 推荐39 推荐41 推荐43 推荐45 推荐47 推荐49 关键词1 关键词101 关键词201 关键词301 关键词401 关键词501 关键词601 关键词701 关键词801 关键词901 关键词1001 关键词1101 关键词1201 关键词1301 关键词1401 关键词1501 关键词1601 关键词1701 关键词1801 关键词1901 视频扩展1 视频扩展6 视频扩展11 视频扩展16 文章1 文章201 文章401 文章601 文章801 文章1001 资讯1 资讯501 资讯1001 资讯1501 标签1 标签501 标签1001 关键词1 关键词501 关键词1001 关键词1501 专题2001
MySQL关于exists的一个bug
2020-11-09 20:46:03 责编:小采
文档


今天碰到一个关于exists很奇怪的问题

第一个语句如下:

SELECT
count(1)
FROM
APPLY t
WHERE
EXISTS (
SELECT
r.APPLY_ID
FROM
RECORD r
WHERE
t.APPLY_ID = r.APPLY_ID
);

产生的结果是:584

第二个语句如下:

SELECT
count(1)
FROM
APPLY t
WHERE
EXISTS (
SELECT
max(r.FINISH_TIME)
FROM
RECORD r
WHERE
t.APPLY_ID = r.APPLY_ID
);

产生的结果是:432382

确实相当奇怪,对于exist子句来说,其判断的是子查询的值是否存在,也就是说,列名,和对列名求最大值没什么区别啊。

包括MySQL官方文档中也提到

Traditionally, an EXISTS subquery starts with SELECT *, but it could begin with SELECT 5 or SELECT column1 or anything at all. MySQL ignores the SELECT list in such a subquery, so it makes no difference.

大意就是MySQL会自动忽略到SELECT的列表。

后来在自己的环境测试了一下,确实是MySQL的一个bug

测试环境:MySQL 5.6.31,5.7.14

mysql> create table t3(id int,t datetime);
Query OK, 0 rows affected (0.44 sec)
mysql> insert into t3 values(1,'20160812');
Query OK, 1 row affected (0.16 sec)
mysql> select 1 from dual where exists (select id from t3 where id=2);
Empty set (0.15 sec)
mysql> select 1 from dual where exists (select max(id) from t3 where id=2);
+---+
| 1 |
+---+
| 1 |

很明显,id等于2的列不存在,但是第二条语句还是当做TRUE来处理了。

也确认了下两条语句的执行计划和改写后的SQL

第一个语句

mysql> EXPLAIN EXTENDED select 1 from dual where exists (select id from t3 where id=2);
+----+-------------+-------+------------+------+---------------+------+---------+------+------+----------+------------------+
| id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
+----+-------------+-------+------------+------+---------------+------+---------+------+------+----------+------------------+
| 1 | PRIMARY | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | Impossible WHERE |
| 2 | SUBQUERY | t3 | NULL | ALL | NULL | NULL | NULL | NULL | 1 | 100.00 | Using where |
+----+-------------+-------+------------+------+---------------+------+---------+------+------+----------+------------------+
2 rows in set, 2 warnings (0.00 sec)
mysql> show warnings;
+---------+------+-------------------------------------------------------------------+
| Level | Code | Message |
+---------+------+-------------------------------------------------------------------+
| Warning | 1681 | 'EXTENDED' is deprecated and will be removed in a future release. |
| Note | 1003 | /* select#1 */ select 1 AS `1` from DUAL where 0 |
+---------+------+-------------------------------------------------------------------+ 

第二个语句

mysql> EXPLAIN EXTENDED select 1 from dual where exists (select max(id) from t3 where id=2);
+----+-------------+-------+------------+------+---------------+------+---------+------+------+----------+----------------+
| id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
+----+-------------+-------+------------+------+---------------+------+---------+------+------+----------+----------------+
| 1 | PRIMARY | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | No tables used |
| 2 | SUBQUERY | t3 | NULL | ALL | NULL | NULL | NULL | NULL | 1 | 100.00 | Using where |
+----+-------------+-------+------------+------+---------------+------+---------+------+------+----------+----------------+
2 rows in set, 2 warnings (0.00 sec)
mysql> show warnings;
+---------+------+-------------------------------------------------------------------+
| Level | Code | Message |
+---------+------+-------------------------------------------------------------------+
| Warning | 1681 | 'EXTENDED' is deprecated and will be removed in a future release. |
| Note | 1003 | /* select#1 */ select 1 AS `1` from DUAL where 1 |
+---------+------+-------------------------------------------------------------------+
2 rows in set (0.00 sec) 

执行计划及改写后的SQL确实有所不同,看来,确实是MySQL的一个bug了。

于是,给官方提了个bug

http://bugs.mysql.com/bug.php?id=82562

总结

建议写exists语句时,子查询中直接用*,而不用对列进行任何函数操作,避免碰到官方bug,

事实上,对于abs,floor函数又没问题

mysql> select 1 from dual where exists (select abs(id) from t3 where id=2);
Empty set (0.07 sec)
mysql> select 1 from dual where exists (select floor(id) from t3 where id=2);
Empty set (0.00 sec)

以上所述是小编给大家介绍的MySQL关于exists的一个bug ,希望对大家有所帮助,如果大家有任何疑问请给我留言,小编会及时回复大家的。在此也非常感谢大家对脚本之家网站的支持!

您可能感兴趣的文章:

  • MySQL exists 和in 详解及区别
  • mySQL中in查询与exists查询的区别小结
  • 安装mysql出错”A Windows service with the name MySQL already exists.“如何解决
  • MySQL的子查询中FROM和EXISTS子句的使用教程
  • MYSQL IN 与 EXISTS 的优化示例介绍
  • mysql not in、left join、IS NULL、NOT EXISTS 效率问题记录
  • UCenter info: MySQL Query Error SQL:SELECT value FROM [Table]vars WHERE noteexists
  • mysql insert if not exists防止插入重复记录的方法
  • MySQL: mysql is not running but lock exists 的解决方法
  • mysql exists与not exists实例详解
  • 下载本文
    显示全文
    专题