Bug #82717 | ALTER TABLE allows adding NOT NULL BLOB columns | ||
---|---|---|---|
Submitted: | 24 Aug 2016 23:48 | Modified: | 25 Aug 2016 17:38 |
Reporter: | Chris Giard | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: DDL | Severity: | S3 (Non-critical) |
Version: | 5.6.27 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[24 Aug 2016 23:48]
Chris Giard
[25 Aug 2016 15:13]
MySQL Verification Team
Hi, Thank you for your bug report. However, I can not find any justification for your report. Our manual does not have a single sentence about non-assumption of the default values in the case of the combo of the --innodb-strict-mode and sql_mode=TRADITIONAL. There are references to syntax errors and some non-permissible options, but nowhere does our manual state that default values must be specified with the above combo !!!!
[25 Aug 2016 15:23]
Chris Giard
Hello Sinisa, TRADITIONAL includes STRICT_ALL_TABLES, which has in the description "Enable strict SQL mode for all storage engines. Invalid data values are rejected. For details, see Strict SQL Mode." http://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sqlmode_strict_all_tables. The "Strict SQL Mode" section additionally says "A value can be invalid for several reasons. For example, it might have the wrong data type for the column, or it might be out of range. A value is missing when a new row to be inserted does not contain a value for a non-NULL column that has no explicit DEFAULT clause in its definition," and "Strict mode also affects DDL statements such as CREATE TABLE."
[25 Aug 2016 17:38]
MySQL Verification Team
Yes, You are right. When you connect all those dots together, this DDL should return the error, while it does not. Verified as reported. However, a low priority bug.