8126)",Dear Sona, This is not an issue with TeamKaeru's server settings. I have the same problem, and all the people running MySQL 5.7 will experience the sa"/> 8126)""> 8126)",Dear Sona, This is not an issue with TeamKaeru's server settings. I have the same problem, and all the people running MySQL 5.7 will experience the sa"/> 8126)""/> 8126)",Dear Sona, This is not an issue with TeamKaeru's server settings. I have the same problem, and all the people running MySQL 5.7 will experience the sa "/>

Gennady Kovshenin on "[Plugin: Gallery] Err 1118 - Row size too large (> 8126)"

ساخت وبلاگ

Dear Sona,

This is not an issue with TeamKaeru's server settings. I have the same problem, and all the people running MySQL 5.7 will experience the same problem. Be prepared to receive more and more similar reports.

Your wp_bwg_theme table has WAY too many fields: 438 fields, which is a textbook case of bad design.

See this question for more information:
http://dba.stackexchange.com/questions/45837/mysql-row-size-too-large-8126

To quote the answer:

SUMMARY : Bill Karwin said it before and I agree: REDESIGN THE TABLE. That will circvumvent the row length issue for sure.

Please don't blindly challenge the facts, and lea from the experts in the aforementioned thread: this table is poorly designed, and its contents should be split across several tables.

You might get away with switching the table engine to MyISAM (a pretty bad idea), or switching InnoDB to the Barracuda file format + switching to innodb_file_per_table + switching to ROW_FORMAT=DYNAMIC to get the options field data out of the row, which might save just enough space to fit in the 8126 bytes.

But that doesn't change the facts. You cannot impose a specific database configuration to accommodate a bad design.

I would appreciate if you could fix this issue ASAP!

Kind regards,
Ben

WordPress ...
ما را در سایت WordPress دنبال می کنید

برچسب : نویسنده : استخدام کار wpss بازدید : 279 تاريخ : دوشنبه 28 تير 1395 ساعت: 5:42