Hi Jonathan, No, we only have 9 libraries so there should only be 11 entries in that table (we have two rotating collections we treat as "branches" as well). Cindy ----------------------------------------------------------- Cindy Murdock Ames IT Services Director Meadville Public Library | CCFLS https://meadvillelibrary.org | https://ccfls.org Please report tech support issues in Mantis: https://mantis.ccfls.org On Thu, Jul 30, 2020 at 3:29 AM Jonathan Druart < jonathan.druart@bugs.koha-community.org> wrote:
Hello Cindy, We faced this error for the table borrowers (bug 24986). I am quite surprised you got it for the branches table, especially for a "DROP COLUMN" statement. Do you have a ton of entries in this table? Regards, Jonathan
Le mer. 29 juil. 2020 à 19:05, Cindy Murdock Ames <cmurdock@ccfls.org> a écrit :
I've been running 19.11.05 for several months now with MariaDB 10.4.13
no issues AFAIK. I upgraded a test server to 20.05 and got some errors from updatedatabase.pl like this:
DBD::mysql::db do failed: Row size too large. The maximum row size for
with 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 branches DROP COLUMN branchprinter"] at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 21074.
After some investigating I found that our database (imported from 3.22 in April) had a row_format of "Compact" on all tables and newer versions of the database have a row_format of "Dynamic". I expect this is cruft from our database that has been imported into new versions of Koha several times, since we've been using Koha for 10+ years. Anyway, on my test server I changed ours to Dynamic and it was able to update without any errors after that, but I haven't yet upgraded our production server to it. Probably no one else will run into this, but I thought I'd just put it out into the ether in case anyone else runs into this issue.
Cindy
----------------------------------------------------------- Cindy Murdock Ames IT Services Director Meadville Public Library | CCFLS https://meadvillelibrary.org | https://ccfls.org
On Mon, Jul 27, 2020 at 11:24 AM Philippe Blouin < philippe.blouin@inlibro.com> wrote:
I only dared to write that affirmatively because I was just in the process of updating another machine (from 9.9 to 9.13), and it was installing MariaDB 10.4.13.
It was right in front of me, on my screen.
But after your answers I dug a bit and yeah, the source.list.d specifies 10.4 for mariadb.
So my initial answer is mostly wrong. The only correct part is that we do have multiple production systems running 10.4 without glitch, but that is not proof of anything.
My apologies for the misleading answer.
Philippe Blouin, Directeur de la technologie
Tél. : (833) 465-4276, poste 230 philippe.blouin@inLibro.com <mailto:philippe.blouin@inLibro.com>
inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com> On 2020-07-27 10:56 a.m., Michael Kuhn wrote:
Hi Philippe
Am 27.07.20 um 16:32 schrieb Philippe Blouin:
10.4 is the default mariadb version you get with an up-to-date Debian 9 or Ubuntu 18.
It works.
I just updated another Installation of Debian GNU/Linux 9.12 to 9.13. But it only updated to MariaDB 10.1.45, not 10.4.x
So my question is still open, if Koha 18.11 on Debian 9 will work with Koha 10.3
Best wishes: Michael
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha