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
In pingcap/tidb#2738 it mentions that TiDB should support more sql_modes, but it is not clear which existing modes are supported.
Because TiDB does not produce an error when setting an unsupported sql_mode, it is important that this be documented on sql/mysql-compatibility.md
sql/mysql-compatibility.md
The text was updated successfully, but these errors were encountered:
An example showing the sql_mode of NO_ENGINE_SUBSTITUTION having no impact:
NO_ENGINE_SUBSTITUTION
mysql> SELECT @@sql_mode; +--------------------------------------------+ | @@sql_mode | +--------------------------------------------+ | STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION | +--------------------------------------------+ 1 row in set (0.00 sec) mysql> CREATE TABLE t (a int) engine=idontexist; Query OK, 0 rows affected (0.18 sec)
Sorry, something went wrong.
Via the mysql docs. Here is my understanding so far:
Successfully merging a pull request may close this issue.
In pingcap/tidb#2738 it mentions that TiDB should support more sql_modes, but it is not clear which existing modes are supported.
Because TiDB does not produce an error when setting an unsupported sql_mode, it is important that this be documented on
sql/mysql-compatibility.md
The text was updated successfully, but these errors were encountered: