mysql隐式转换造成索引失效的事故总结
2014-03-07 11:03
746 查看
隐式转换导致索引失效.这一点应当引起重视.也是开发中经常会犯的错误. 由于表的字段tu_mdn定义为varchar2(20),但在查询时把该字段作为number类型以where条件传给mysql,这样会导致索引失效. 错误的例子:select * from test where tu_mdn=13333333333; 正确的例子:select * from test where tu_mdn='13333333333';
看一下下面的案例,这个案例是开发过程中经常犯的一个错误,这种索引在大表的查询中是很致命的,直接能把数据库拖死:
mysql> show create table shipping\G;
*************************** 1. row ***************************
Table: shipping
Create Table: CREATE TABLE `shipping` (
`id` int(11) unsigned NOT NULL AUTO_INCREMENT,
`shipping_no` int(11) NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `shipping_no` (`shipping_no`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1
1 row in set (0.00 sec)
mysql> explain SELECT shipping_no FROM `shipping` WHERE `shipping_no` IN (62487941,62653594,62952180,63556576,63684186,99097538006,100433005006,100433006006);
+----+-------------+----------------------+-------+---------------+-------------+---------+------+------+-------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+----------------------+-------+---------------+-------------+---------+------+------+-------------+
| 1 | SIMPLE | shipping | range | shipping_no | shipping_no | 4 | NULL | 6 | Using where |
+----+-------------+----------------------+-------+---------------+-------------+---------+------+------+-------------+
1 row in set (0.00 sec)
mysql> explain SELECT shipping_no FROM `shipping` WHERE (`shipping_no` IN ('62487941','62653594','62952180','63556576','63684186','99097538006','100433005006','100433006006'));
+----+-------------+----------------------+------+---------------+------+---------+------+----------+-------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+----------------------+------+---------------+------+---------+------+----------+-------------+
| 1 | SIMPLE | shipping | ALL | shipping_no | NULL | NULL | NULL | 12803696 | Using where |
+----+-------------+----------------------+------+---------------+------+---------+------+----------+-------------+
1 row in set (0.00 sec)
很蛋疼的东西,希望开发者在开发的时候注意字段不要越界,最主要的是不要使用隐形转换,有些是转换不了的,DBA的同行们注意这种隐形转换带来的危害,一定要给开发者提供规范。
看一下下面的案例,这个案例是开发过程中经常犯的一个错误,这种索引在大表的查询中是很致命的,直接能把数据库拖死:
mysql> show create table shipping\G;
*************************** 1. row ***************************
Table: shipping
Create Table: CREATE TABLE `shipping` (
`id` int(11) unsigned NOT NULL AUTO_INCREMENT,
`shipping_no` int(11) NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `shipping_no` (`shipping_no`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1
1 row in set (0.00 sec)
mysql> explain SELECT shipping_no FROM `shipping` WHERE `shipping_no` IN (62487941,62653594,62952180,63556576,63684186,99097538006,100433005006,100433006006);
+----+-------------+----------------------+-------+---------------+-------------+---------+------+------+-------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+----------------------+-------+---------------+-------------+---------+------+------+-------------+
| 1 | SIMPLE | shipping | range | shipping_no | shipping_no | 4 | NULL | 6 | Using where |
+----+-------------+----------------------+-------+---------------+-------------+---------+------+------+-------------+
1 row in set (0.00 sec)
mysql> explain SELECT shipping_no FROM `shipping` WHERE (`shipping_no` IN ('62487941','62653594','62952180','63556576','63684186','99097538006','100433005006','100433006006'));
+----+-------------+----------------------+------+---------------+------+---------+------+----------+-------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+----------------------+------+---------------+------+---------+------+----------+-------------+
| 1 | SIMPLE | shipping | ALL | shipping_no | NULL | NULL | NULL | 12803696 | Using where |
+----+-------------+----------------------+------+---------------+------+---------+------+----------+-------------+
1 row in set (0.00 sec)
很蛋疼的东西,希望开发者在开发的时候注意字段不要越界,最主要的是不要使用隐形转换,有些是转换不了的,DBA的同行们注意这种隐形转换带来的危害,一定要给开发者提供规范。
相关文章推荐
- 关于oracle 与 mysql 的索引与隐式转换的总结
- 由于mysql隐式类型转换导致的索引失效的问题
- Mysql引起索引失效的原因总结
- Mysql 索引失效的情况总结
- 关于一次线上事故总结,以及对于mysql索引的总结(序言一)
- 隐式转换导致索引失效
- Mysql引起索引失效的原因总结
- mysql索引失效的几种情况(总结)
- MYSQL索引失效的各种情形总结
- MySQL SQL优化之字符串索引隐式转换
- MySQL的隐式类型转换整理总结
- 总结MySQL 下索引失效的情况
- 避免在sql的where中对字段进行转换(函数转换/操作符转换/隐式转换)------索引会失效从而导致慢查询
- mysql可能造成索引失效的场景
- MYSQL索引失效的各种情形总结
- SQL中一些不经意隐式类型转换或者函数使用导致索引失效问题
- 也议MySQL中隐式转换
- Mysql的float类型造成的困扰总结
- mysql索引总结----mysql 索引类型以及创建
- mysql索引总结----mysql 索引类型以及创建