Hi,
When I try to save the safe path
/data/web/virtuals/XXXXX/virtual/www/subdom/czech-offroad/logs/vmfiles/ XXXXX is number
I get this error:
1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs SQL=ALTER TABLE `kleu_virtuemart_products_cs_cz` CHANGE COLUMN `product_desc` `product_desc` VARCHAR(18400) NOT NULL DEFAULT '' AFTER `product_s_desc`
http://imtp.me/9dkc02lj3.p
please advise how to fix it
http://forum.virtuemart.net/index.php?topic=128956.0
and dblayoutstrict=0
Hi Max,
Thanks, it worked perfectly. I added dblayoutstrict=0 to virtuemart.cfg file and then saved the configuration again and all tables were created and fixed and no errors appear now.
Ok, How about updates? When i update vm from 3.0.9 to 3.0.12 - seems like "product_desc" field type changed back to varchar (18400)
Ok, How about updates? When i update vm from 3.0.9 to 3.0.12 - seems like "product_desc" field type changed back to varchar (18400)
life is never perfect... change it back...
uhhm, this is a serious error, because it leads to lost data. But I changed only the reading of sql file and the handling updating of the engine. So the file was almost untouched since May 2015. The code is
else if(strpos($name,'desc')!==false) {
if(VmConfig::get('dblayoutstrict',true)){
$fields[$name] = 'varchar('.VmConfig::get('dbdescsize',19000).') '.$linedefault;
} else {
$fields[$name] = 'text '.$linedefaulttext;
}
Please test http://forum.virtuemart.net/index.php?topic=133113.0
- enhanced tableupdater, also correcting missing Primary Keys
- virtumart.cfg parser understands // inline comments