MySQL 索引失效常见的几种情况
来源:SegmentFault
时间:2023-01-19 20:17:39 178浏览 收藏
来到golang学习网的大家,相信都是编程学习爱好者,希望在这里学习数据库相关编程知识。下面本篇文章就来带大家聊聊《MySQL 索引失效常见的几种情况》,介绍一下MySQL,希望对大家的知识积累有所帮助,助力实战开发!
我们上篇文章简单分析了下InnoDB行锁,文中有提及索引失效时,行锁会升级为表锁,今天我们这篇文章来聊一聊常见的索引失效的几种情况:
还是和往常一样,我们先建一张表:
CREATE TABLE `user_info` ( `id` int(11) DEFAULT NULL auto_increment, `name` varchar(255) DEFAULT NULL, `nick` varchar(255) DEFAULT NULL, `sex` char(2), `score` int(3), KEY `idx_id` (`id`), KEY `idx_sex` (`sex`), KEY `idx_name_score_nick` (`name`, `score`, `nick`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8
insert into user_info values (1, '杨过', 'yangguo', '1', 90); insert into user_info values (2, '小龙女', 'xiaolongnv', '0', 88); insert into user_info values (3, '黄药师', 'huangyaoshi', '1', 75); insert into user_info values (4, '郭襄', 'guoxiang', '0', 66); insert into user_info values (5, '何足道', 'hezudao', '1', 50); insert into user_info values (6, '独孤求败', 'duguqiubai', '1', 55); insert into user_info values (7, '方东白', 'fangdongbai', '1', 88); insert into user_info values (8, '赵敏', 'zhaomin', '0', 75); insert into user_info values (9, '程灵素', 'chenglingsu','0', 66);
MySQL [wakka]> select * from user_info; +----+--------------+-------------+------+-------+ | id | name | nick | sex | score | +----+--------------+-------------+------+-------+ | 1 | 杨过 | yangguo | 1 | 90 | | 2 | 小龙女 | xiaolongnv | 0 | 88 | | 3 | 黄药师 | huangyaoshi | 1 | 75 | | 4 | 郭襄 | guoxiang | 0 | 66 | | 5 | 何足道 | hezudao | 1 | 50 | | 6 | 独孤求败 | duguqiubai | 1 | 55 | | 7 | 方东白 | fangdongbai | 1 | 88 | | 8 | 赵敏 | zhaomin | 0 | 75 | | 9 | 程灵素 | chenglingsu | 0 | 66 | +----+--------------+-------------+------+-------+ 9 rows in set (0.00 sec)
索引失效的第一种常见情况:对字段进行运算,比如对name字段截取操作
MySQL [wakka]> explain select * from user_info where name = '程灵素'; #name字段原本有索引 +----+-------------+-----------+------------+------+---------------------+---------------------+---------+-------+------+----------+-------+ | id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra | +----+-------------+-----------+------------+------+---------------------+---------------------+---------+-------+------+----------+-------+ | 1 | SIMPLE | user_info | NULL | ref | idx_name_score_nick | idx_name_score_nick | 768 | const | 1 | 100.00 | NULL | +----+-------------+-----------+------------+------+---------------------+---------------------+---------+-------+------+----------+-------+ 1 row in set, 1 warning (0.00 sec) MySQL [wakka]> explain select * from user_info where substr(name, 2, 2) = '灵素'; #对name字段进行运算 +----+-------------+-----------+------------+------+---------------+------+---------+------+------+----------+-------------+ | id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra | +----+-------------+-----------+------------+------+---------------+------+---------+------+------+----------+-------------+ | 1 | SIMPLE | user_info | NULL | ALL | NULL | NULL | NULL | NULL | 9 | 100.00 | Using where | +----+-------------+-----------+------------+------+---------------+------+---------+------+------+----------+-------------+ 1 row in set, 1 warning (0.00 sec)
索引失效的第二种常见情况:范围查询右边的列不能够使用索引
MySQL [wakka]> explain select * from user_info where name = '郭襄' and score = 66 and nick = 'guoxiang'; #索引用到了name,score,nick三个字段 +----+-------------+-----------+------------+------+---------------------+---------------------+---------+-------------------+------+----------+-------+ | id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra | +----+-------------+-----------+------------+------+---------------------+---------------------+---------+-------------------+------+----------+-------+ | 1 | SIMPLE | user_info | NULL | ref | idx_name_score_nick | idx_name_score_nick | 1541 | const,const,const | 1 | 100.00 | NULL | +----+-------------+-----------+------------+------+---------------------+---------------------+---------+-------------------+------+----------+-------+ 1 row in set, 1 warning (0.00 sec) MySQL [wakka]> explain select * from user_info where name = '郭襄' and score explain select * from user_info where name = '郭襄' and score = 66; +----+-------------+-----------+------------+------+---------------------+---------------------+---------+-------------+------+----------+-------+ | id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra | +----+-------------+-----------+------------+------+---------------------+---------------------+---------+-------------+------+----------+-------+ | 1 | SIMPLE | user_info | NULL | ref | idx_name_score_nick | idx_name_score_nick | 773 | const,const | 1 | 100.00 | NULL | +----+-------------+-----------+------------+------+---------------------+---------------------+---------+-------------+------+----------+-------+ 1 row in set, 1 warning (0.00 sec) #我们可以看到第二个SQL的key_len和第三个SQL的key len一样长度
索引失效的第三种常见情况:数值型字符字段没有用引号
MySQL [wakka]> explain select * from user_info where sex = '0'; +----+-------------+-----------+------------+------+---------------+---------+---------+-------+------+----------+-------+ | id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra | +----+-------------+-----------+------------+------+---------------+---------+---------+-------+------+----------+-------+ | 1 | SIMPLE | user_info | NULL | ref | idx_sex | idx_sex | 7 | const | 4 | 100.00 | NULL | +----+-------------+-----------+------------+------+---------------+---------+---------+-------+------+----------+-------+ 1 row in set, 1 warning (0.00 sec) MySQL [wakka]> explain select * from user_info where sex = 0; #这样做,相当于字段做了一层隐式类型转换,前面我们第一点说过,如果字段进行运算,则索引还小 +----+-------------+-----------+------------+------+---------------+------+---------+------+------+----------+-------------+ | id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra | +----+-------------+-----------+------------+------+---------------+------+---------+------+------+----------+-------------+ | 1 | SIMPLE | user_info | NULL | ALL | idx_sex | NULL | NULL | NULL | 9 | 11.11 | Using where | +----+-------------+-----------+------------+------+---------------+------+---------+------+------+----------+-------------+ 1 row in set, 3 warnings (0.00 sec)
索引失效的第四种常见情况:or分隔的条件,如果or前面的列有索引,or后面的列没索引,则涉及的索引都失效
MySQL [wakka]> select * from user_info where name = '方东白' or nick = 'xiaolongnv'; +----+-----------+-------------+------+-------+ | id | name | nick | sex | score | +----+-----------+-------------+------+-------+ | 2 | 小龙女 | xiaolongnv | 0 | 88 | | 7 | 方东白 | fangdongbai | 1 | 88 | +----+-----------+-------------+------+-------+ 2 rows in set (0.00 sec) MySQL [wakka]> explain select * from user_info where name = '方东白' or nick = 'xiaolongnv'; +----+-------------+-----------+------------+------+---------------------+------+---------+------+------+----------+-------------+ | id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra | +----+-------------+-----------+------------+------+---------------------+------+---------+------+------+----------+-------------+ | 1 | SIMPLE | user_info | NULL | ALL | idx_name_score_nick | NULL | NULL | NULL | 9 | 20.99 | Using where | +----+-------------+-----------+------------+------+---------------------+------+---------+------+------+----------+-------------+ 1 row in set, 1 warning (0.00 sec)
索引失效的第五种常见情况:like %开头
MySQL [wakka]> explain select * from user_info where name like '%白'; +----+-------------+-----------+------------+------+---------------+------+---------+------+------+----------+-------------+ | id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra | +----+-------------+-----------+------------+------+---------------+------+---------+------+------+----------+-------------+ | 1 | SIMPLE | user_info | NULL | ALL | NULL | NULL | NULL | NULL | 9 | 11.11 | Using where | +----+-------------+-----------+------------+------+---------------+------+---------+------+------+----------+-------------+ 1 row in set, 1 warning (0.00 sec)
相反,如果like 后缀%的话,是可以用到索引的
MySQL [wakka]> explain select * from user_info where name like '杨%'; +----+-------------+-----------+------------+-------+---------------------+---------------------+---------+------+------+----------+-----------------------+ | id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra | +----+-------------+-----------+------------+-------+---------------------+---------------------+---------+------+------+----------+-----------------------+ | 1 | SIMPLE | user_info | NULL | range | idx_name_score_nick | idx_name_score_nick | 768 | NULL | 1 | 100.00 | Using index condition | +----+-------------+-----------+------------+-------+---------------------+---------------------+---------+------+------+----------+-----------------------+ 1 row in set, 1 warning (0.00 sec)
如果喜欢我的文章,欢迎关注我的公众号:“码农漫谈”,专注Web开发,后台开发,DB和架构

好了,本文到此结束,带大家了解了《MySQL 索引失效常见的几种情况》,希望本文对你有所帮助!关注golang学习网公众号,给大家分享更多数据库知识!
声明:本文转载于:SegmentFault 如有侵犯,请联系study_golang@163.com删除
相关阅读
更多>
-
499 收藏
-
244 收藏
-
235 收藏
-
157 收藏
-
101 收藏
最新阅读
更多>
-
404 收藏
-
101 收藏
-
265 收藏
-
209 收藏
-
446 收藏
-
339 收藏
-
285 收藏
-
259 收藏
-
374 收藏
-
475 收藏
-
483 收藏
-
462 收藏
课程推荐
更多>
-
- 前端进阶之JavaScript设计模式
- 设计模式是开发人员在软件开发过程中面临一般问题时的解决方案,代表了最佳的实践。本课程的主打内容包括JS常见设计模式以及具体应用场景,打造一站式知识长龙服务,适合有JS基础的同学学习。
- 立即学习 542次学习
-
- GO语言核心编程课程
- 本课程采用真实案例,全面具体可落地,从理论到实践,一步一步将GO核心编程技术、编程思想、底层实现融会贯通,使学习者贴近时代脉搏,做IT互联网时代的弄潮儿。
- 立即学习 508次学习
-
- 简单聊聊mysql8与网络通信
- 如有问题加微信:Le-studyg;在课程中,我们将首先介绍MySQL8的新特性,包括性能优化、安全增强、新数据类型等,帮助学生快速熟悉MySQL8的最新功能。接着,我们将深入解析MySQL的网络通信机制,包括协议、连接管理、数据传输等,让
- 立即学习 497次学习
-
- JavaScript正则表达式基础与实战
- 在任何一门编程语言中,正则表达式,都是一项重要的知识,它提供了高效的字符串匹配与捕获机制,可以极大的简化程序设计。
- 立即学习 487次学习
-
- 从零制作响应式网站—Grid布局
- 本系列教程将展示从零制作一个假想的网络科技公司官网,分为导航,轮播,关于我们,成功案例,服务流程,团队介绍,数据部分,公司动态,底部信息等内容区块。网站整体采用CSSGrid布局,支持响应式,有流畅过渡和展现动画。
- 立即学习 484次学习