MySQL令人大跌眼镜的隐式转换


Posted in MySQL onAugust 23, 2021

MySQL的隐式转换

一、问题描述

show create table t1\G
*************************** 1. row ***************************
       Table: t1
Create Table: CREATE TABLE `t1` (
  `id` varchar(255) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8
1 row in set (0.00 sec)
 
 select * from t1;
+--------------------+
| id                 |
+--------------------+
| 204027026112927605 |
| 204027026112927603 |
| 2040270261129276   |
| 2040270261129275   |
| 100                |
| 101                |
+--------------------+
6 rows in set (0.00 sec)

奇怪的现象:

select * from t1 where id=204027026112927603;
+--------------------+
| id                 |
+--------------------+
| 204027026112927605 |
| 204027026112927603 |
+--------------------+
2 rows in set (0.00 sec)

什么鬼,明明查的是204027026112927603,为什么204027026112927605也出来了

二、源码解释

堆栈调用关系如下所示:

MySQL令人大跌眼镜的隐式转换

其中JOIN::exec()是执行的入口,Arg_comparator::compare_real()是进行等值判断的函数,其定义如下

int Arg_comparator::compare_real()
{
  /*
    Fix yet another manifestation of Bug#2338. 'Volatile' will instruct
    gcc to flush double values out of 80-bit Intel FPU registers before
    performing the comparison.
  */
  volatile double val1, val2;
  val1= (*a)->val_real();
  if (!(*a)->null_value)
  {
    val2= (*b)->val_real();
    if (!(*b)->null_value)
    {
      if (set_null)
        owner->null_value= 0;
      if (val1 < val2)  return -1;
      if (val1 == val2) return 0;
      return 1;
    }
  }
  if (set_null)
    owner->null_value= 1;
  return -1;
}

比较步骤如下图所示,逐行读取t1表的id列放入val1,而常量204027026112927603存在于cache中,类型为double类型(2.0402702611292762E+17),所以到这里传值给val2后val2=2.0402702611292762E+17。

MySQL令人大跌眼镜的隐式转换

当扫描到第一行时,204027026112927605转成doule的值为2.0402702611292762e17,等式成立,判定为符合条件的行,继续往下扫描,同理204027026112927603也同样符合

MySQL令人大跌眼镜的隐式转换

如何检测string类型的数字转成doule类型是否溢出呢?这里经过测试,当数字超过16位以后,转成double类型就已经不准确了,例如20402702611292711会表示成20402702611292712(如图中val1)

MySQL令人大跌眼镜的隐式转换

MySQL令人大跌眼镜的隐式转换

MySQL string转成double的定义函数如下:

{
  char buf[DTOA_BUFF_SIZE];
  double res;
  DBUG_ASSERT(end != NULL && ((str != NULL && *end != NULL) ||
                              (str == NULL && *end == NULL)) &&
              error != NULL);
 
  res= my_strtod_int(str, end, error, buf, sizeof(buf));
  return (*error == 0) ? res : (res < 0 ? -DBL_MAX : DBL_MAX);
}

真正转换函数my_strtod_int位置在dtoa.c(太复杂了,简单贴个注释吧)

/*
  strtod for IEEE--arithmetic machines.
 
  This strtod returns a nearest machine number to the input decimal
  string (or sets errno to EOVERFLOW). Ties are broken by the IEEE round-even
  rule.
 
  Inspired loosely by William D. Clinger's paper "How to Read Floating
  Point Numbers Accurately" [Proc. ACM SIGPLAN '90, pp. 92-101].
 
  Modifications:
 
   1. We only require IEEE (not IEEE double-extended).
   2. We get by with floating-point arithmetic in a case that
     Clinger missed -- when we're computing d * 10^n
     for a small integer d and the integer n is not too
     much larger than 22 (the maximum integer k for which
     we can represent 10^k exactly), we may be able to
     compute (d*10^k) * 10^(e-k) with just one roundoff.
   3. Rather than a bit-at-a-time adjustment of the binary
     result in the hard case, we use floating-point
     arithmetic to determine the adjustment to within
     one bit; only in really hard cases do we need to
     compute a second residual.
   4. Because of 3., we don't need a large table of powers of 10
     for ten-to-e (just some small tables, e.g. of 10^k
     for 0 <= k <= 22).
*/

既然是这样,我们测试下没有溢出的案例

select * from t1 where id=2040270261129276;
+------------------+
| id               |
+------------------+
| 2040270261129276 |
+------------------+
1 row in set (0.00 sec)
 
 select * from t1 where id=101;
+------+
| id   |
+------+
| 101  |
+------+
1 row in set (0.00 sec)

结果符合预期,而在本例中,正确的写法应当是

select * from t1 where id='204027026112927603';
+--------------------+
| id                 |
+--------------------+
| 204027026112927603 |
+--------------------+
1 row in set (0.01 sec)

三、结论

避免发生隐式类型转换,隐式转换的类型主要有字段类型不一致、in参数包含多个类型、字符集类型或校对规则不一致等
隐式类型转换可能导致无法使用索引、查询结果不准确等,因此在使用时必须仔细甄别
数字类型的建议在字段定义时就定义为int或者bigint,表关联时关联字段必须保持类型、字符集、校对规则都一致

最后贴一下官网对于隐式类型转换的说明吧

1、If one or both arguments are NULL, the result of the comparison is NULL, except for the NULL-safe
<=> equality comparison operator. For NULL <=> NULL, the result is true. No conversion is needed.
2、If both arguments in a comparison operation are strings, they are compared as strings.
3、If both arguments are integers, they are compared as integers.
4、Hexadecimal values are treated as binary strings if not compared to a number.
5、If one of the arguments is a TIMESTAMP or DATETIME column and the other argument is a
constant, the constant is converted to a timestamp before the comparison is performed. This is
done to be more ODBC-friendly. This is not done for the arguments to IN(). To be safe, always
use complete datetime, date, or time strings when doing comparisons. For example, to achieve best
results when using BETWEEN with date or time values, use CAST() to explicitly convert the values to
the desired data type.
A single-row subquery from a table or tables is not considered a constant. For example, if a subquery
returns an integer to be compared to a DATETIME value, the comparison is done as two integers.
The integer is not converted to a temporal value. To compare the operands as DATETIME values,
use CAST() to explicitly convert the subquery value to DATETIME.
6、If one of the arguments is a decimal value, comparison depends on the other argument. The
arguments are compared as decimal values if the other argument is a decimal or integer value, or as
floating-point values if the other argument is a floating-point value.
7、In all other cases, the arguments are compared as floating-point (real) numbers.

以上就是MySQL令人大跌眼镜的隐式转换的详细内容,更多关于MySQL的隐式转换的资料请关注三水点靠木其它相关文章!,希望大家以后多多支持三水点靠木!

MySQL 相关文章推荐
详解mysql三值逻辑与NULL
May 19 MySQL
MySQL中distinct与group by之间的性能进行比较
May 26 MySQL
MYSQL数据库使用UTF-8中文编码乱码的解决办法
May 26 MySQL
你知道哪几种MYSQL的连接查询
Jun 03 MySQL
MySQL 数据恢复的多种方法汇总
Jun 21 MySQL
MySQL中datetime时间字段的四舍五入操作
Oct 05 MySQL
全面盘点MySQL中的那些重要日志文件
Nov 27 MySQL
MySQL中int (10) 和 int (11) 的区别
Jan 22 MySQL
MySQL实战记录之如何快速定位慢SQL
Mar 23 MySQL
Mysql分析设计表主键为何不用uuid
Mar 31 MySQL
Mysql数据库事务的脏读幻读及不可重复读详解
May 30 MySQL
SQL IDENTITY_INSERT作用案例详解
Aug 23 #MySQL
MySQL非空约束(not null)案例讲解
Aug 23 #MySQL
MySQL外键约束(FOREIGN KEY)案例讲解
Aug 23 #MySQL
MySQL 1130异常,无法远程登录解决方案详解
Aug 23 #MySQL
Node-Red实现MySQL数据库连接的方法
Aug 07 #MySQL
MySQL如何解决幻读问题
Aug 07 #MySQL
浅谈MySQL之select优化方案
Aug 07 #MySQL
You might like
PHP读MYSQL中文乱码的解决方法
2006/12/17 PHP
php zend 相对路径问题
2009/01/12 PHP
php教程之魔术方法的使用示例(php魔术函数)
2014/02/12 PHP
简单谈谈php中ob_flush和flush的区别
2014/11/27 PHP
Yii清理缓存的方法
2016/01/06 PHP
PHP基于GD库实现的生成图片缩略图函数示例
2017/07/05 PHP
laravel 实现上传图片到本地和前台访问示例
2019/10/21 PHP
javaScript 读取和设置文档元素的样式属性
2009/04/14 Javascript
js 分栏效果实现代码
2009/08/29 Javascript
jquery 元素控制(追加元素/追加内容)介绍及应用
2013/04/21 Javascript
JS判断是否360安全浏览器极速内核的方法
2015/01/29 Javascript
更高效的使用JQuery 这里总结了8个小技巧
2016/04/13 Javascript
微信小程序  http请求封装详解及实例代码
2017/02/15 Javascript
JavaScript重复元素处理方法分析【统计个数、计算、去重复等】
2017/12/14 Javascript
通过实例了解JS执行上下文运行原理
2020/06/17 Javascript
vue组件开发之tab切换组件使用详解
2020/08/21 Javascript
Python类属性的延迟计算
2016/10/22 Python
python一键升级所有pip package的方法
2017/01/16 Python
Python 读取图片文件为矩阵和保存矩阵为图片的方法
2018/04/27 Python
Pandas 同元素多列去重的实例
2018/07/03 Python
Python3实现腾讯云OCR识别
2018/11/27 Python
在Python中字符串、列表、元组、字典之间的相互转换
2019/11/15 Python
一文详述 Python 中的 property 语法
2020/09/01 Python
HTML5 贪吃蛇游戏实现思路及源代码
2013/09/03 HTML / CSS
eDreams意大利:南欧领先的在线旅行社
2018/11/23 全球购物
亚马逊新加坡官方网站:Amazon.sg
2020/03/25 全球购物
UDP协议功能
2013/01/06 面试题
大学生职业生涯规划书的基本内容
2014/01/06 职场文书
运动会广播稿60字
2014/01/15 职场文书
打架检讨书300字
2014/02/02 职场文书
高等教育学自荐书范文
2014/02/10 职场文书
财务工作犯错检讨书
2014/10/07 职场文书
2015年城乡环境综合治理工作总结
2015/07/24 职场文书
个人工作决心书
2015/09/22 职场文书
PHP 技巧 * SVG 保存为图片(分享图生成)
2021/04/02 PHP
Pytorch反向传播中的细节-计算梯度时的默认累加操作
2021/06/05 Python