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 相关文章推荐
Windows10下安装MySQL8
Apr 06 MySQL
IDEA 链接Mysql数据库并执行查询操作的完整代码
May 20 MySQL
详解MySQL中的pid与socket
Jun 15 MySQL
MySQL如何解决幻读问题
Aug 07 MySQL
MySQL数据库必备之条件查询语句
Oct 15 MySQL
基于MySql验证的vsftpd虚拟用户
Nov 07 MySQL
关于mysql中时间日期类型和字符串类型的选择
Nov 27 MySQL
彻底解决MySQL使用中文乱码的方法
Jan 22 MySQL
MySQL磁盘碎片整理实例演示
Apr 03 MySQL
深入理解mysql事务隔离级别和存储引擎
Apr 12 MySQL
Mysql排查分析慢sql之explain实战案例
Apr 19 MySQL
MySQL约束(创建表时的各种条件说明)
Jun 21 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
使用dump函数,给php加断点测试
2013/06/25 PHP
用PHP生成excel文件到指定目录
2015/06/22 PHP
功能强大的PHP图片处理类(水印、透明度、旋转)
2015/10/21 PHP
PHP实现时间日期友好显示实现代码
2019/09/08 PHP
JavaScript中通过闭包解决只能取得包含函数中任何变量最后一个值的问题
2010/08/12 Javascript
理解Javascript_02_理解undefined和null
2010/10/11 Javascript
js借助ActiveXObject实现创建文件
2013/09/29 Javascript
基于jquery插件实现常见的幻灯片效果
2013/11/01 Javascript
跟我学习javascript的定时器
2015/11/19 Javascript
微信小程序  action-sheet详解及实例代码
2016/11/09 Javascript
javascript显示系统当前时间代码
2016/12/29 Javascript
Vue 父子组件的数据传递、修改和更新方法
2018/03/01 Javascript
基于Vue渲染与插件的加载顺序的问题详解
2018/03/05 Javascript
jQuery pagination分页示例详解
2018/10/23 jQuery
小程序使用wxs解决wxml保留2位小数问题
2019/12/13 Javascript
JavaScript实现公告栏上下滚动效果
2020/03/13 Javascript
JS常用跨域方法实现原理解析
2020/12/09 Javascript
Python中用Ctrl+C终止多线程程序的问题解决
2013/03/30 Python
Python中关键字is与==的区别简述
2014/07/31 Python
Python制作简易注册登录系统
2016/12/15 Python
基于 Django 的手机管理系统实现过程详解
2019/08/16 Python
python2.7的flask框架之引用js&amp;css等静态文件的实现方法
2019/08/22 Python
tensorflow使用range_input_producer多线程读取数据实例
2020/01/20 Python
tensorflow 利用expand_dims和squeeze扩展和压缩tensor维度方式
2020/02/07 Python
基于python实现简单网页服务器代码实例
2020/09/14 Python
pandas将list数据拆分成行或列的实现
2020/12/13 Python
HTML5实现视频直播功能思路详解
2017/11/16 HTML / CSS
小蚁科技官方商店:YI Technology
2019/08/23 全球购物
创立科技Java面试题
2015/11/29 面试题
英文求职信写作小建议
2014/02/16 职场文书
党员公开承诺书和承诺事项
2014/03/25 职场文书
公安交警个人对照检查材料思想汇报
2014/10/01 职场文书
培训简讯范文
2015/07/20 职场文书
简单介绍Python的第三方库yaml
2021/06/18 Python
redis cluster支持pipeline的实现思路
2021/06/23 Redis
Rhit高效可视化Nginx日志查看工具
2021/11/01 Servers