content_image/840539.jpg content_image/840541.jpg
on the CREATE TABLE  or ALTER TABLE  statements, and how the options appear in the output of SHOW TABLE STATUS . 

When innodb_strict_mode  is OFF , MySQL creates or alters the table, but ignores certain settings as shown below. You can see the warning messages in the MySQL error log. When innodb_strict_mode is ON , these specified combinations of options generate errors, and the table is not created or altered. To see the full description of the error condition, issue the SHOW ERRORS  statement: example: 

mysql> CREATE TABLE x (id INT PRIMARY KEY, c INT) -> ENGINE=INNODB KEY_BLOCK_SIZE=33333; ERROR 1005 (HY000): Can’t create table ’test.x’ (errno: 1478) mysql> SHOW ERRORS; 

<img src='content_image/840539.jpg'>

<img src='content_image/840541.jpg'>

When innodb_strict_mode  is ON , MySQL rejects invalid ROW_FORMAT  or KEY_BLOCK_SIZE parameters and issues errors. Strict mode is ON  by default. When innodb_strict_mode  is OFF , MySQL issues warnings instead of errors for ignored invalid parameters. 

It is not possible to see the chosen KEY_BLOCK_SIZE  using SHOW TABLE STATUS . The statement SHOW CREATE TABLE  displays the KEY_BLOCK_SIZE  (even if it was ignored when creating the table). The real compressed page size of the table cannot be displayed by MySQL. 

