https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24986 Bug ID: 24986 Summary: Maximum row size reached soon for borrowers and deletedborrowers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs@lists.koha-community.org Reporter: julian.maurice@biblibre.com QA Contact: testopia@bugs.koha-community.org Running updatedatabase.pl I got the following error messages: DBD::mysql::db do failed: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs [for Statement "ALTER TABLE borrowers ADD COLUMN autorenew_checkouts TINYINT(1) NOT NULL DEFAULT 1 AFTER anonymized"] at installer/data/mysql/updatedatabase.pl li ne 21259 DBD::mysql::db do failed: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs [for Statement "ALTER TABLE deletedborrowers ADD COLUMN autorenew_checkouts TINYINT(1) NOT NULL DEFAULT 1 AFTER anonymized"] at installer/data/mysql/updatedatabas e.pl line 21262. After re-injecting an old clean dump and replaying the updatedatabase.pl errors are gone, so it was probably because of other columns coming from patches not yet in master. Maybe we should start moving some columns to other tables. An obvious candidate is all the address fields that can be moved in a patron_addresses table. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.