mysql中null转double,如何避免MySQL的隐式转换(截断了错误的DOUBLE值)

本文介绍如何在MySQL中将关于字符串与整数比较导致的警告升级为错误,避免因隐式类型转换造成的意外结果。通过使用CAST或CONVERT函数强制类型转换,并讨论了配置SQL_MODE设置和正确处理数据类型比较的重要性。
摘要由CSDN通过智能技术生成

When I execute this query

mysql> SELECT * FROM test WHERE sample_col = 'foo';

with this table.

mysql> SHOW CREATE TABLE test\G

*************************** 1. row ***************************

Table: test

Create Table: CREATE TABLE `test` (

`id` int(10) unsigned NOT NULL AUTO_INCREMENT,

`sample_col` int(11) DEFAULT NULL,

PRIMARY KEY (`id`)

) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=utf8

1 row in set (0.00 sec)

mysql> SELECT * FROM test;

+----+------------+

| id | sample_col |

+----+------------+

| 1 | 0 |

| 2 | 1 |

| 3 | 2 |

+----+------------+

3 rows in set (0.00 sec)

MySQL automatically convert 'foo' of WHERE clause to zero and I received this warning message.

mysql> SELECT * FROM test WHERE sample_col = 'foo';

+----+------------+

| id | sample_col |

+----+------------+

| 1 | 0 |

+----+------------+

1 row in set, 1 warning (0.00 sec)

mysql> SHOW WARNINGS;

+---------+------+-----------------------------------------+

| Level | Code | Message |

+---------+------+-----------------------------------------+

| Warning | 1292 | Truncated incorrect DOUBLE value: 'foo' |

+---------+------+-----------------------------------------+

1 row in set (0.00 sec)

How can I configure MySQL to report this warning as error? (Or how can I stop implicit conversion?)

I've set SQL_MODE as strict but it seems not affect SELECT statement.

mysql> SELECT @@SQL_MODE;

+------------------------------------------+

| @@SQL_MODE |

+------------------------------------------+

| STRICT_ALL_TABLES,NO_ENGINE_SUBSTITUTION |

+------------------------------------------+

Version of MySQL is 5.6.16.

mysql> SELECT @@VERSION;

+------------+

| @@VERSION |

+------------+

| 5.6.16-log |

+------------+

[UPDATE]

The query SELECT * FROM test WHERE sample_col = 'foo'; was a bug of my code. And I cannot notice the bug because of implicit conversion.

My purpose is "how to avoid such query" or "how to detect this bug soon". So I want to know the way to stop implicit conversion or way to change error level of this from warning to error.

解决方案

You should rather try casting it explicitly using CAST or CONVERT function like below and don't count on implicit casting.

SELECT * FROM test WHERE sample_col = cast('foo' as int);

(OR)

SELECT * FROM test WHERE cast(sample_col as varchar) = 'foo';

Moreover, there is no point is comparing a INT type column with string value and AFAIK, there is no such setting present to stop implicit casting. if you really want to result in error rather than converting it to 0 then cast it explicitly; in which case it will error out.

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值