https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28267
--- Comment #18 from David Cook <dc...@prosentient.com.au> --- (In reply to Mason James from comment #15) > (In reply to skaman.tx from comment #14) > > > > Any further thoughts? > > hi skaman > > running this SQL before the upgrade might fix the error... > ALTER TABLE `items` ROW_FORMAT=DYNAMIC; > > more info... > https://mariadb.com/kb/en/troubleshooting-row-size-too-large-errors-with- > innodb/ Cheers, Mason! When I ran some SQL from that troubleshooting page, I noticed that all the Koha tables were using "Compact" row format. The database I was using was set up a long time ago, and it did in-place upgrades that retained the legacy settings it seems. From 10.2.x, the default has been Dynamic. I think this bug report could probably be closed, although perhaps we could have an audit script for double-checking some MySQL settings before upgrading I guess... that's a bit fraught though. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
