MySQL 字符串转double转换栈帧(可能丢失精度)

本文涉及的产品
云数据库 RDS MySQL Serverless,0.5-2RCU 50GB
云数据库 RDS MySQL Serverless,价值2615元额度,1个月
简介: 简单记录栈帧以备后用欢迎关注我的《深入理解MySQL主从原理 32讲 》,如下:一、转换案例最近有朋友讨论字符串转换double丢失精度的问题案例如下:本案例来自朋友徐晨亮root@mysqldb 22:12: [xucl]> show create table t1\G*************************** 1.

简单记录栈帧以备后用


欢迎关注我的《深入理解MySQL主从原理 32讲 》,如下:

image.png

一、转换案例

最近有朋友讨论字符串转换double丢失精度的问题案例如下:

本案例来自朋友徐晨亮


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也出来了

转换在官方文档写的很清楚,这里两边都转换为了double类型进行比较。

二、简单测试

实际上我们可以用一个double类型的字段插入字符串就可以测试这种情况:

mysql> use testmts
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> insert into test11 values('1111111111111111111111111111111111');
Query OK, 1 row affected (37 min 53.07 sec)

mysql> show create table test11;
+--------+----------------------------------------------------------------------------------------+
| Table  | Create Table                                                                           |
+--------+----------------------------------------------------------------------------------------+
| test11 | CREATE TABLE `test11` (
  `n` double DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 |
+--------+----------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

mysql> select * from test11;
+-----------------------+
| n                     |
+-----------------------+
|  9.007199254740991e15 |
|  9.007199254740992e15 |
|  9.007199254740991e17 |
| 1.1111111111111112e31 |
| 1.1111111111111112e31 |
| 1.1111111111111111e33 |
| 1.1111111111111111e33 |
| 1.1111111111111111e33 |
| 1.1111111111111111e33 |
| 1.1111111111111111e33 |
| 1.1111111111111111e33 |
+-----------------------+
11 rows in set (0.00 sec)

可以看到实际上精度已经丢失了。大概16字符到17字符之间,多的可能被忽略掉,字符串丢失精度。

三、转换函数

这个转换函数几百上千行,没仔细看,太费劲。记录一下栈帧:

#0  my_strtod_int (s00=0x7ffedc0065f0 '1' <repeats 34 times>, se=0x7fffec5eb678, error=0x7fffec5eb680, buf=0x7fffec5ea770 "\320\001", buf_size=3680)
    at /mysqldata/percona-server-locks-detail-5.7.22/strings/dtoa.c:1356
#1  0x0000000001ee07c1 in my_strtod (str=0x7ffedc0065f0 '1' <repeats 34 times>, end=0x7fffec5eb678, error=0x7fffec5eb680)
    at /mysqldata/percona-server-locks-detail-5.7.22/strings/dtoa.c:472
#2  0x0000000001ec4eda in my_strntod_8bit (cs=0x2e379e0, str=0x7ffedc0065f0 '1' <repeats 34 times>, length=34, end=0x7fffec5eb678, err=0x7fffec5eb680)
    at /mysqldata/percona-server-locks-detail-5.7.22/strings/ctype-simple.c:741
#3  0x0000000000f4dbae in Field_double::store (this=0x7ffedc9a1390, from=0x7ffedc0065f0 '1' <repeats 34 times>, len=34, cs=0x2e379e0)
    at /mysqldata/percona-server-locks-detail-5.7.22/sql/field.cc:4825
#4  0x0000000000f9bbc7 in Item::save_str_value_in_field (this=0x7ffedc006618, field=0x7ffedc9a1390, result=0x7ffedc006628)
    at /mysqldata/percona-server-locks-detail-5.7.22/sql/item.cc:561
#5  0x0000000000fae204 in Item_string::save_in_field_inner (this=0x7ffedc006618, field=0x7ffedc9a1390, no_conversions=false)
    at /mysqldata/percona-server-locks-detail-5.7.22/sql/item.cc:6895
#6  0x0000000000fad7de in Item::save_in_field (this=0x7ffedc006618, field=0x7ffedc9a1390, no_conversions=false)
    at /mysqldata/percona-server-locks-detail-5.7.22/sql/item.cc:6752
#7  0x0000000001549101 in fill_record (thd=0x7ffedc000b90, table=0x7ffedc9a8650, ptr=0x7ffedc9a1388, values=..., bitmap=0x0, insert_into_fields_bitmap=0x0)
    at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_base.cc:9702
#8  0x00000000015493e9 in fill_record_n_invoke_before_triggers (thd=0x7ffedc000b90, ptr=0x7ffedc9a1380, values=..., table=0x7ffedc9a8650, event=TRG_EVENT_INSERT, 
    num_fields=1) at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_base.cc:9784
#9  0x00000000017fd477 in Sql_cmd_insert::mysql_insert (this=0x7ffedc006d80, thd=0x7ffedc000b90, table_list=0x7ffedc0067c8)
    at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_insert.cc:751
#10 0x00000000018040ed in Sql_cmd_insert::execute (this=0x7ffedc006d80, thd=0x7ffedc000b90) at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_insert.cc:3121
#11 0x00000000015cc753 in mysql_execute_command (thd=0x7ffedc000b90, first_level=true) at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_parse.cc:3746
#12 0x00000000015d2fde in mysql_parse (thd=0x7ffedc000b90, parser_state=0x7fffec5ed600) at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_parse.cc:5901
#13 0x00000000015c6b72 in dispatch_command (thd=0x7ffedc000b90, com_data=0x7fffec5edd70, command=COM_QUERY)
    at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_parse.cc:1490
#14 0x00000000015c58ff in do_command (thd=0x7ffedc000b90) at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_parse.cc:1021
#15 0x000000000170e578 in handle_connection (arg=0x6ab5a00) at /mysqldata/percona-server-locks-detail-5.7.22/sql/conn_handler/connection_handler_per_thread.cc:312
#16 0x0000000001945538 in pfs_spawn_thread (arg=0x697a460) at /mysqldata/percona-server-locks-detail-5.7.22/storage/perfschema/pfs.cc:2190
#17 0x00007ffff7bcfaa1 in start_thread () from /lib64/libpthread.so.0
#18 0x00007ffff6b37c4d in clone () from /lib64/libc.so.6

开头案例转换栈帧

#0  my_strtod (str=0x7ffee097a803 "204027026112927605", end=0x7fff009ef778, error=0x7fff009ef784) at /mysqldata/percona-server-locks-detail-5.7.22/strings/dtoa.c:468
#1  0x0000000001ec4eda in my_strntod_8bit (cs=0x2e377a0, str=0x7ffee097a803 "204027026112927605", length=18, end=0x7fff009ef778, err=0x7fff009ef784)
    at /mysqldata/percona-server-locks-detail-5.7.22/strings/ctype-simple.c:741
#2  0x0000000000f5639f in Field_varstring::val_real (this=0x7ffee097ae60) at /mysqldata/percona-server-locks-detail-5.7.22/sql/field.cc:7663
#3  0x0000000000fa2b9d in Item_field::val_real (this=0x7ffee0007180) at /mysqldata/percona-server-locks-detail-5.7.22/sql/item.cc:2960
#4  0x0000000000fc8d3d in Arg_comparator::compare_real (this=0x7ffee0007378) at /mysqldata/percona-server-locks-detail-5.7.22/sql/item_cmpfunc.cc:1745
#5  0x0000000000fde0fc in Arg_comparator::compare (this=0x7ffee0007378) at /mysqldata/percona-server-locks-detail-5.7.22/sql/item_cmpfunc.h:92
#6  0x0000000000fcafb9 in Item_func_eq::val_int (this=0x7ffee00072a0) at /mysqldata/percona-server-locks-detail-5.7.22/sql/item_cmpfunc.cc:2507
#7  0x0000000001581a11 in evaluate_join_record (join=0x7ffee00077b8, qep_tab=0x7ffee0a77520) at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_executor.cc:1492
#8  0x0000000001581372 in sub_select (join=0x7ffee00077b8, qep_tab=0x7ffee0a77520, end_of_records=false)
    at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_executor.cc:1297
#9  0x0000000001580be6 in do_select (join=0x7ffee00077b8) at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_executor.cc:950
#10 0x000000000157eaa2 in JOIN::exec (this=0x7ffee00077b8) at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_executor.cc:199
#11 0x0000000001620327 in handle_query (thd=0x7ffee0000c00, lex=0x7ffee0003230, result=0x7ffee00074e8, added_options=0, removed_options=0)
    at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_select.cc:185
#12 0x00000000015d1f77 in execute_sqlcom_select (thd=0x7ffee0000c00, all_tables=0x7ffee0006be0) at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_parse.cc:5445
#13 0x00000000015ca380 in mysql_execute_command (thd=0x7ffee0000c00, first_level=true) at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_parse.cc:2939
#14 0x00000000015d2fde in mysql_parse (thd=0x7ffee0000c00, parser_state=0x7fff009f1600) at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_parse.cc:5901
#15 0x00000000015c6b72 in dispatch_command (thd=0x7ffee0000c00, com_data=0x7fff009f1d70, command=COM_QUERY)
    at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_parse.cc:1490
#16 0x00000000015c58ff in do_command (thd=0x7ffee0000c00) at /mysqldata/percona-server-locks-detail-5.7.22/sql/sql_parse.cc:1021
#17 0x000000000170e578 in handle_connection (arg=0x3605a30) at /mysqldata/percona-server-locks-detail-5.7.22/sql/conn_handler/connection_handler_per_thread.cc:312
#18 0x0000000001945538 in pfs_spawn_thread (arg=0x36e71c0) at /mysqldata/percona-server-locks-detail-5.7.22/storage/perfschema/pfs.cc:2190
#19 0x00007ffff7bcfaa1 in start_thread () from /lib64/libpthread.so.0
#20 0x00007ffff6b37c4d in clone () from /lib64/libc.so.6

四、官方文档关于转换的说明

The following rules describe how conversion occurs for comparison operations:
• 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.
• If both arguments in a comparison operation are strings, they are compared as strings.
• If both arguments are integers, they are compared as integers.
• Hexadecimal values are treated as binary strings if not compared to a number.
• 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.
• 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.
• In all other cases, the arguments are compared as floating-point (real) numbers.

五、为什么会丢失精度

一般来讲double占用8直接也就是64位其中:

  • 1位 符号位
  • 11位 指数位
  • 52位 尾数位

我们可以看到尾数位才是精度的保证,它的精度实际上没有long int类型高。因此当查过保存的上限将会丢失精度。

作者微信:gp_22389860

相关实践学习
基于CentOS快速搭建LAMP环境
本教程介绍如何搭建LAMP环境,其中LAMP分别代表Linux、Apache、MySQL和PHP。
全面了解阿里云能为你做什么
阿里云在全球各地部署高效节能的绿色数据中心,利用清洁计算为万物互联的新世界提供源源不断的能源动力,目前开服的区域包括中国(华北、华东、华南、香港)、新加坡、美国(美东、美西)、欧洲、中东、澳大利亚、日本。目前阿里云的产品涵盖弹性计算、数据库、存储与CDN、分析与搜索、云通信、网络、管理与监控、应用服务、互联网中间件、移动服务、视频服务等。通过本课程,来了解阿里云能够为你的业务带来哪些帮助 &nbsp; &nbsp; 相关的阿里云产品:云服务器ECS 云服务器 ECS(Elastic Compute Service)是一种弹性可伸缩的计算服务,助您降低 IT 成本,提升运维效率,使您更专注于核心业务创新。产品详情: https://www.aliyun.com/product/ecs
相关文章
|
16天前
|
SQL 存储 关系型数据库
|
4月前
|
关系型数据库 MySQL 数据库
MySQL数据库-截取字符串
MySQL数据库-截取字符串
27 0
|
4月前
|
关系型数据库 MySQL 数据库
MySQL数据库-字符串位数不够前面补0
MySQL数据库-字符串位数不够前面补0
26 0
|
5月前
|
SQL Oracle 关系型数据库
MySQL之如何将字符串分隔为列表结果集
MySQL之如何将字符串分隔为列表结果集
102 1
|
6月前
|
关系型数据库 MySQL
MySQL清除字符串首尾空格函数
MySQL清除字符串首尾空格函数
|
8月前
|
存储 NoSQL 关系型数据库
7.4.4 【MySQL】索引字符串值的前缀
7.4.4 【MySQL】索引字符串值的前缀
45 0
|
9天前
|
关系型数据库 MySQL Linux
【MySQL-10】数据库函数-案例演示【字符串/数值/日期/流程控制函数】(代码演示&可cv代码)
【MySQL-10】数据库函数-案例演示【字符串/数值/日期/流程控制函数】(代码演示&可cv代码)
【MySQL-10】数据库函数-案例演示【字符串/数值/日期/流程控制函数】(代码演示&可cv代码)
|
5月前
|
存储 关系型数据库 MySQL
MySQL中的列类型之字符串类型总结
MySQL中的列类型之字符串类型总结
79 1
|
2月前
|
C#
C# 字节数组与INT16,float,double之间相互转换,字符数组与字符串相互转换,
C# 字节数组与INT16,float,double之间相互转换,字符数组与字符串相互转换,
39 1
|
5月前
|
SQL JSON 关系型数据库
【SQL编程】MySQL 5.7.28 版本使用 SQL 直接解析 JSON 字符串(判断是否是合法JSON类型+文本深度+文本长度+值类型+keys获取+值获取+不同深度数据获取)
【SQL编程】MySQL 5.7.28 版本使用 SQL 直接解析 JSON 字符串(判断是否是合法JSON类型+文本深度+文本长度+值类型+keys获取+值获取+不同深度数据获取)
62 0