今天接到一個(gè)朋友電話說是覺的數(shù)據(jù)庫被別人更改了,出現(xiàn)數(shù)據(jù)不對(duì)的問題 。經(jīng)過很久的排查是數(shù)據(jù)類型溢出了(發(fā)生問題的版本是MySQL 5.1)。后來通過給朋友那邊把MySQL 5.1升級(jí)到MySQL 5.5去解決這個(gè)問題。 這也讓我有興趣去了解一下MySQL不同版本數(shù)據(jù)類型溢出的處理機(jī)制。
先看一下MySQL支持的整型數(shù)及大小,存儲(chǔ)空間:
pe | Storage | Minimum Value | Maximum Value | 存儲(chǔ)大小 |
---|---|---|---|---|
(Bytes) | (Signed/Unsigned) | (Signed/Unsigned) | byte | |
TINYINT | 1 | -128 | 127 | 1 byte |
0 | 255 | |||
SMALLINT | 2 | -32768 | 32767 | 2 bytes |
0 | 65535 | |||
MEDIUMINT | 3 | -8388608 | 8388607 | 3 bytes |
0 | 16777215 | |||
INT | 4 | -2147483648 | 2147483647 | 4 bytes |
0 | 4294967295 | |||
BIGINT | 8 | -9223372036854775808 | 9223372036854775807 | 8 bytes |
0 | 18446744073709551615 |
另外請(qǐng)記著mysql的數(shù)據(jù)處理會(huì)轉(zhuǎn)成bigint處理,所以這里就用bigint幾個(gè)測(cè)試:
代碼如下:
SELECT CAST(0 AS UNSIGNED) - 1;
SELECT 9223372036854775807 + 1;
MySQL 5.1 下:
代碼如下:
mysql> SELECT CAST(0 AS UNSIGNED) - 1;
+-------------------------+
| CAST(0 AS UNSIGNED) - 1 |
+-------------------------+
| 18446744073709551615 |
+-------------------------+
1 row in set (0.01 sec)
mysql> SELECT 9223372036854775807 + 1;
+-------------------------+
| 9223372036854775807 + 1 |
+-------------------------+
| -9223372036854775808 |
+-------------------------+
1 row in set (0.01 sec)
MySQL 5.5, 5.6, 5.7下:
代碼如下:
mysql> SELECT CAST(0 AS UNSIGNED) - 1;
ERROR 1690 (22003): BIGINT UNSIGNED value is out of range in '(cast(0 as unsigned) - 1)'
mysql>
mysql>
mysql>
mysql> SELECT 9223372036854775807 + 1;
ERROR 1690 (22003): BIGINT value is out of range in '(9223372036854775807 + 1)'
所在處理這類數(shù)據(jù)是一定要小心溢出(如早期有做弊沖Q幣就是利用這個(gè)方法處理)
這個(gè)問題有可能會(huì)出現(xiàn)積分消息,積分相加, 或是一些錢相關(guān)的業(yè)務(wù)中出現(xiàn), 主庫5.1 ,從庫MySQL 5.5情況也會(huì)出現(xiàn)不同步的問題。
建議:這類業(yè)務(wù)系統(tǒng)盡可能的升級(jí)到MySQL 5.5后版本
更多詳情參考: http://dev.mysql.com/doc/refman/5.7/en/out-of-range-and-overflow.html
聲明:本網(wǎng)頁內(nèi)容旨在傳播知識(shí),若有侵權(quán)等問題請(qǐng)及時(shí)與本網(wǎng)聯(lián)系,我們將在第一時(shí)間刪除處理。TEL:177 7030 7066 E-MAIL:11247931@qq.com