When innodb_strict_mode is on, table creation and every alter table that would result in a too-large row size fails, issuing an error 1118:
and logs a different but technically correct message to the error log:
However, when innodb_strict_mode=0 the error message becomes a warning message:
but the same message written to the error log as an error when innodb_strict_mode was set to 1 gets written to the error log as a warning:
The same problem happens with TRUNCATE TABLE and OPTIMIZE TABLE operations. However, these operations succeed and write the incorrect message to the log regardless of the value of innodb_strict_mode.
which is incorrect. The table gets successfully created with all fields including c181 and c182-c200.