MySQL令人咋舌的隐式转换


Posted in MySQL onApril 05, 2021

一、问题描述

root@mysqldb 22:12:  [xucl]> 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)

root@mysqldb 22:19:  [xucl]> select * from t1;
+--------------------+
| id                 |
+--------------------+
| 204027026112927605 |
| 204027026112927603 |
| 2040270261129276   |
| 2040270261129275   |
| 100                |
| 101                |
+--------------------+
6 rows in set (0.00 sec)

奇怪的现象:

root@mysqldb 22:19:  [xucl]> select * from t1 where id=204027026112927603;
+--------------------+
| id                 |
+--------------------+
| 204027026112927605 |
| 204027026112927603 |
+--------------------+
2 rows in set (0.00 sec)

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

 

二、源码解释

其中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。

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

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

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).
*/

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

root@mysqldb 23:30:  [xucl]> select * from t1 where id=2040270261129276;
+------------------+
| id               |
+------------------+
| 2040270261129276 |
+------------------+
1 row in set (0.00 sec)

root@mysqldb 23:30:  [xucl]> select * from t1 where id=101;
+------+
| id   |
+------+
| 101  |
+------+
1 row in set (0.00 sec)

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

root@mysqldb 22:19:  [xucl]> select * from t1 where id='204027026112927603';
+--------------------+
| id                 |
+--------------------+
| 204027026112927603 |
+--------------------+
1 row in set (0.01 sec)

三、结论

  1. 避免发生隐式类型转换,隐式转换的类型主要有字段类型不一致、in参数包含多个类型、字符集类型或校对规则不一致等

  2. 隐式类型转换可能导致无法使用索引、查询结果不准确等,因此在使用时必须仔细甄别

  3. 数字类型的建议在字段定义时就定义为int或者bigint,表关联时关联字段必须保持类型、字符集、校对规则都一致

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

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学习总结-基础架构概述
Apr 05 MySQL
详解mysql三值逻辑与NULL
May 19 MySQL
MySQL系列之十一 日志记录
Jul 02 MySQL
MySQL 四种连接和多表查询详解
Jul 16 MySQL
MySQL数据库超时设置配置的方法实例
Oct 15 MySQL
mysql函数全面总结
Nov 11 MySQL
教你如何让spark sql写mysql的时候支持update操作
Feb 15 MySQL
MySQL如何快速创建800w条测试数据表
Mar 17 MySQL
Linux系统下MySQL配置主从分离的步骤
Mar 21 MySQL
Golang连接并操作MySQL
Apr 14 MySQL
MySQL批量更新不同表中的数据
May 11 MySQL
MySQL 原理优化之Group By的优化技巧
Aug 14 MySQL
MySQL基础(一)
Apr 05 #MySQL
MySQL基础(二)
MySQL学习总结-基础架构概述
MySQL锁机制
mysql知识点整理
Apr 05 #MySQL
浅析InnoDB索引结构
Apr 05 #MySQL
MySQL入门命令之函数-单行函数-流程控制函数
Apr 05 #MySQL
You might like
自己动手,丰衣足食 - 短波框形天线制作
2021/03/01 无线电
php把数据表导出为Excel表的最简单、最快的方法(不用插件)
2014/05/10 PHP
PHP使用Mysql事务实例解析
2014/09/08 PHP
php去掉文件前几行的方法
2015/07/29 PHP
php创建无限级树型菜单
2015/11/05 PHP
学习php设计模式 php实现工厂模式(factory)
2015/12/07 PHP
YII框架中使用memcache的方法详解
2017/08/02 PHP
JS动态创建元素的两种方法
2016/04/20 Javascript
JS之获取样式的简单实现方法(推荐)
2016/09/13 Javascript
基于Vue.js实现简单搜索框
2020/03/26 Javascript
Angular-Touch库用法示例
2016/12/22 Javascript
Html5+jQuery+CSS制作相册小记录
2016/12/30 Javascript
浅谈Angular 观察者模式理解
2018/11/01 Javascript
手把手教你使用TypeScript开发Node.js应用
2019/05/06 Javascript
Vue 幸运大转盘实现思路详解
2019/05/06 Javascript
微信小程序如何刷新当前界面的实现方法
2019/06/07 Javascript
微信小程序select下拉框实现源码
2019/11/08 Javascript
jQuery实现弹出层效果
2019/12/10 jQuery
Python实现求最大公约数及判断素数的方法
2015/05/26 Python
构建Python包的五个简单准则简介
2015/06/15 Python
老生常谈进程线程协程那些事儿
2017/07/24 Python
python实现图书馆研习室自动预约功能
2018/04/27 Python
pandas数据集的端到端处理
2019/02/18 Python
pytorch 预训练层的使用方法
2019/08/20 Python
python lambda表达式(匿名函数)写法解析
2019/09/16 Python
Django1.11自带分页器paginator的使用方法
2019/10/31 Python
Python编程快速上手——strip()函数的正则表达式实现方法分析
2020/02/29 Python
CSS3实现超酷的黑猫警长首页
2016/04/26 HTML / CSS
工厂保安员岗位职责
2014/01/31 职场文书
优秀教导主任事迹材料
2014/05/09 职场文书
五心教育心得体会
2014/09/04 职场文书
基层工作经历证明
2015/06/19 职场文书
小学运动会加油稿
2015/07/22 职场文书
干货:我将这样书写我的演讲稿!
2019/05/09 职场文书
2019通用版劳动合同范本!
2019/07/11 职场文书
Golang中channel的原理解读(推荐)
2021/10/16 Golang