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

[David Cook]

Hi Jonathan,

 

This still feels like a workaround to me and not a real long-term solution. If someone uses koha-create or koha-remove, they still need to remember to update that MySQL init-file, as that won’t happen automatically. I think it would require a lot of on-going maintenance that not all Koha users are able to achieve.

 

Plus, if they have a lot of Koha instances, that init file is going to be huge and difficult to manage. 

 

I was thinking another option might be to add a trigger for borrowers, biblio, biblioitems, items, issues, and reserves, which makes sure that the number selected is higher than any existing number from the table or deletedtable. Of course, that might slow down inserts a bit. I haven’t tried it. If we use triggers, we could add/remove them along with koha-create and koha-remove dynamically. (See the comments of https://dev.mysql.com/doc/refman/5.5/en/innodb-auto-increment-handling.html#innodb-auto-increment-initialization). I think that would be a more elegant solution. I think it’s one that could also be handled via updatedatabase.pl for people upgrading without any administrator intervention.

 

I might actually look at implementing that locally. I’m happy to do that and report back. I use BEFORE INSERT triggers in PostgreSQL on non-Koha databases with a much higher volume of transactions, and they work well.  But I’m happy to try and then report back.

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St

Ultimo, NSW 2007

Australia

 

Office: 02 9212 0899

Direct: 02 8005 0595

 

From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Jonathan Druart
Sent: Tuesday, 1 August 2017 11:23 PM
To: koha at lists.katipo.co.nz; koha-devel at lists.koha-community.org
Subject: [Koha-devel] [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