[Koha] [Important] Update your MySQL|MariaDB configuration to avoid data loss

[Bortel, Gary]

For a multi-tenant installation with multiple MySQL databases...

"The Solution" (https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix) recommends adding "init-file=/var/lib/mysql/init-file_kohadev.sql" in the my.cnf MySQL configuration file, then creating the appropriately configured "init-file_kohadev.sql" file. Where there are multiple Koha databases, should one add multiple "init-file=..." statements to my.cnf as well as multiple init-file_kohadev.sql files? Or will MySQL only accept one init-file directive in which case the .sql file would include multiple blocks of code...one for each database?


gcb


               


-----Original Message-----
From: Koha [mailto:koha-bounces at lists.katipo.co.nz] On Behalf Of Jonathan Druart
Sent: Tuesday, August 01, 2017 6:23 AM
To: koha at lists.katipo.co.nz; koha-devel at lists.koha-community.org
Subject: [Koha] [Important] Update your MySQL|MariaDB configuration to avoid data loss

Hello everybody,

This is an important email and you should not ignore it.
If you are a librarian and have no technical skills you should forward this email to the administrator of your Koha installation.

We have been dealing with circulation history loss in the last versions of Koha, and we ended up with a solution.
You should read the following wiki page attentively and set up the proposed
solution: https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix

Cheers,
Jonathan
_______________________________________________
Koha mailing list  http://koha-community.org Koha at lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha