-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Disabling STRICT_TRANS_TABLES should allow NULL insert into NOT NULL column with default value #11648
Comments
@wjhuang2016 Thanks for your feedback! |
Confirming I can reproduce this against master. The specific issue is that TiDB does not impliment drop table if exists t1;
create table t1 (id int NOT NULL DEFAULT 8);
SET sql_mode = 'STRICT_TRANS_TABLES';
insert into t1 values (1), (NULL), (2);
SET sql_mode = '';
insert into t1 values (1), (NULL), (2);
..
mysql> SET sql_mode = 'STRICT_TRANS_TABLES';
Query OK, 0 rows affected (0.00 sec)
mysql> insert into t1 values (1), (NULL), (2); -- should fail (correct)
ERROR 1048 (23000): Column 'id' cannot be null
mysql> SET sql_mode = '';
Query OK, 0 rows affected (0.00 sec)
mysql> insert into t1 values (1), (NULL), (2); -- should succeed (fails incorrectly)
ERROR 1048 (23000): Column 'id' cannot be null
mysql> select tidb_version()\G
*************************** 1. row ***************************
tidb_version(): Release Version: v4.0.0-beta.2-771-gca41972fb
Edition: Community
Git Commit Hash: ca41972fbac068c8a5de107d9075f09ac68842ac
Git Branch: master
UTC Build Time: 2020-07-14 02:41:21
GoVersion: go1.13
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false
1 row in set (0.00 sec)
|
insert into t1 values (1), (NULL), (2);
failed in sql_mode ''
@zimulala this issue is not picked up? |
@watchpoints I had a PR for it, and I will reopen it soon. |
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 |
Bug Report
tidb-server -V
or runselect tidb_version();
on TiDB)?master
The text was updated successfully, but these errors were encountered: