PHP：“注意：未定义的变量”，“注意：未定义的索引”和“注意：未定义的偏移量”(“Notice: Undefined variable”, “Notice: Undefined index”, and “Notice: Undefined offset” using PHP)

 k ...所以OP没有回应。 这很酷。 这是关于该错误的mysql文档... http://dev.mysql.com/doc/innodb-plugin/1.0/en/innodb-compression-syntax-warnings.html 
 
 
 
 运行ALTER TABLE xyz ENGINE=InnoDB; 再次刺激。 
 
 
 然后show errors; 。 
 
 
 做一个show create table xyz; 
 
 
 看看你是否处于innodb严格模式......（我会在prod和non-prod都这样做，看看有什么区别） SELECT @@GLOBAL.sql_mode; SELECT @@SESSION.sql_mode; SELECT @@GLOBAL.sql_mode; SELECT @@SESSION.sql_mode; 
 
 
 来自docs： 如果您在InnoDB严格模式下运行， KEY_BLOCK_SIZE与除COMPRESSED KEY_BLOCK_SIZE的任何ROW_FORMAT的组合会生成错误，而不是警告，并且不会创建表。 
 
 
 使用您获得的信息和链接中的信息来确定如何设置key_block_size和row_format以使其获取它。 
 
 
 非prod数据库的工作原理是： 
 
 
 
 使用任何其他ROW_FORMAT指定ROW_FORMAT生成警告，您可以使用SHOW WARNINGS查看。 但是，该表是非压缩的; 指定的KEY_BLOCK_SIZE被忽略）。 （在非innodb严格模式下） 
 
 
 如果你想要更多的帮助，发布你得到的信息，我绝对可以建议...这可能是alter table xyz engine=innodb ROW_FORMAT=COMPRESSED; 和/或使innodb模式设置等于非prod数据库设置的设置。 
 
 key_block_size 
 
 比你想知道的行格式更多 
 
 对于真实的，虽然......听起来像prod是在innodb严格模式而非prod不是。 
 
 
 发现了这个： 
 
innodb_strict_mode:

The innodb_strict_mode option controls whether InnoDB operates in strict mode, 
where conditions that are normally treated as warnings, cause errors instead 
(and the underlying statements fail).

This mode is the default setting in MySQL 5.5.5 and higher. 
 
 你的一个版本高于5.5.5，另一个低于。 那个默认可能是差异...... 

k... so OP isn't responding. that's cool. this is the mysql documentation on that error... http://dev.mysql.com/doc/innodb-plugin/1.0/en/innodb-compression-syntax-warnings.html
 
 
 
run ALTER TABLE xyz ENGINE=InnoDB; in prod again. 
 
 
then do show errors;. 
 
 
do a show create table xyz;
 
 
see if you're in innodb strict mode... (i would do this in both prod and non-prod to see any difference) SELECT @@GLOBAL.sql_mode; SELECT @@SESSION.sql_mode;
 
 
from docs: If you are running in InnoDB strict mode, the combination of a KEY_BLOCK_SIZE with any ROW_FORMAT other than COMPRESSED generates an error, not a warning, and the table is not created. 
 
 
use that info you got and the info at the link to determine how you should set your key_block_size and row_format to get it to take it. 
 
 
the non-prod db works because: 
 
 
 
Specifying a KEY_BLOCK_SIZE with any other ROW_FORMAT generates a warning that you can view with SHOW WARNINGS. However, the table is non-compressed; the specified KEY_BLOCK_SIZE is ignored). (in non-innodb-strict mode) 
 
 
if you want more help, post the info you get and i can definitely suggest things... which would probably be alter table xyz engine=innodb ROW_FORMAT=COMPRESSED; and/or making the innodb mode setting equal to what your non-prod db is set with.
 
key_block_size
 
more than you ever wanted to know on row formats
 
for real, though... it sounds like prod is in innodb strict mode and non-prod isn't. 
 
 
found this:
 
innodb_strict_mode:

The innodb_strict_mode option controls whether InnoDB operates in strict mode, 
where conditions that are normally treated as warnings, cause errors instead 
(and the underlying statements fail).

This mode is the default setting in MySQL 5.5.5 and higher. 
 
One of your versions is above 5.5.5 and the other is below. That default might be the discrepancy....