We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please answer these questions before submitting your issue. Thanks!
select -9223372036854775809;
9223372036854775809 is overflow math.MaxInt64, but mysql convert it to Decimal type.
9223372036854775809
mysql> select -9223372036854775809; Field 1: `-9223372036854775809` Catalog: `def` Database: `` Table: `` Org_table: `` Type: NEWDECIMAL Collation: binary (63) Length: 20 Max_length: 20 Decimals: 0 Flags: NOT_NULL BINARY NUM +----------------------+ | -9223372036854775809 | +----------------------+ | -9223372036854775809 | +----------------------+ 1 row in set (0.00 sec)
but TiDB return 9223372036854775807 caused by int overflow, and still use LONGLONG type;
mysql> select -9223372036854775809; Field 1: `-9223372036854775809` Catalog: `def` Database: `` Table: `` Org_table: `` Type: LONGLONG Collation: binary (63) Length: 0 Max_length: 19 Decimals: 31 Flags: BINARY NUM +----------------------+ | -9223372036854775809 | +----------------------+ | 9223372036854775807 | +----------------------+ 1 row in set (0.00 sec)
tidb-server -V
The text was updated successfully, but these errors were encountered:
#3691
Sorry, something went wrong.
expression: fix #3762, signed integer overflow handle in minus unary …
f87e0af
…scalar function
expression: fix #3762, add builtin_op_test.go, some builtin test cases
465dd1b
e008c6c
winkyao
No branches or pull requests
Please answer these questions before submitting your issue. Thanks!
select -9223372036854775809;
9223372036854775809
is overflow math.MaxInt64, but mysql convert it to Decimal type.but TiDB return 9223372036854775807 caused by int overflow, and still use LONGLONG type;
tidb-server -V
)?The text was updated successfully, but these errors were encountered: