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
The following SQL will have different behavior for TiDB and MySQL:
select cast(cast(b'1011' as JSON) as UNSIGNED);
TiDB:
ERROR 1105 (HY000): Unknown type code in JSON
MySQL:
mysql> select cast(cast(X'01AF' as JSON) as SIGNED); +---------------------------------------+ | cast(cast(X'01AF' as JSON) as SIGNED) | +---------------------------------------+ | 0 | +---------------------------------------+ 1 row in set, 1 warning (0.00 sec) mysql> show warnings; +---------+------+--------------------------------------------------------------------------+ | Level | Code | Message | +---------+------+--------------------------------------------------------------------------+ | Warning | 3156 | Invalid JSON value for CAST to INTEGER from column cast_as_json at row 1 | +---------+------+--------------------------------------------------------------------------+ 1 row in set (0.00 sec)
The text was updated successfully, but these errors were encountered:
Fixed, as we added opaque value support.
Sorry, something went wrong.
No branches or pull requests
Enhancement
The following SQL will have different behavior for TiDB and MySQL:
TiDB:
MySQL:
The text was updated successfully, but these errors were encountered: