-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
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
The common type of bigint and bigint unsigned is not stable in TiDB #15771
Comments
Both SQL will return the same result (18446744073709551614) on the master, related PR #21062 . |
Please edit this comment or add a new comment to complete the following informationNot a bug
Duplicate bug
BugNote: Make Sure that 'component', and 'severity' labels are added 1. Root Cause Analysis (RCA) (optional)2. Symptom (optional)3. All Trigger Conditions (optional)4. Workaround (optional)5. Affected versions6. Fixed versions |
Please edit this comment to complete the following information BugNote: Make Sure that 'component', and 'severity' labels are added 1. Root Cause Analysis (RCA)Not process UnsignedFlag in AggFieldType 2. SymptomWrong result when using unsigned in AggField 3. All Trigger Conditions
4. Workaround (optional)5. Affected versions[v4.0.1:v4.0.8] 6. Fixed versionsv4.0.9 |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. What did you do?
2. What did you expect to see?
the above two sql should return the same result(The same query in Mysql-5.7 return -2)
3. What did you see instead?
the first one's return type is bigint unsigned, and the second one's return type is bigint
4. What version of TiDB are you using? (
tidb-server -V
or runselect tidb_version();
on TiDB)TiDB master
The text was updated successfully, but these errors were encountered: