[Koha-devel] AUTO_INCREMENT fix - prevent data lost
David Cook
dcook at prosentient.com.au
Thu Jul 13 05:07:48 CEST 2017
I’ve looked at the wiki page, but I haven’t looked at Bugzilla or the source code. Why on Earth would we get lost data? Shouldn’t we be copying the code to the “deleted*” tables and THEN deleting it from the main table?
In pre-5.7 versions, you could produce this same behaviour by running OPTIMIZE on a table; it would reset the auto increment counter for the table, and it would cause errors because you couldn’t delete records because there was already a record with that key in the deleted* table.
Anyway, I don’t have time to dwell at the moment, but just adding that to the mix.
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: Thursday, 13 July 2017 4:12 AM
To: koha-devel at lists.koha-community.org
Subject: [Koha-devel] AUTO_INCREMENT fix - prevent data lost
Hi devs,
Please review and test https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix
I have added a ref from the Koha on Debian wiki page https://wiki.koha-community.org/wiki/Koha_on_Debian#Further_Configuration
It sounds like I should add it somewhere more visible, but do not find where, any ideas?
See also bug 18931 where I would like to add a warning on the about page if data are corrupted.
Please review quickly, that way we can share the tips on the general mailing list.
Cheers,
Jonathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20170713/add0c2a1/attachment.html>
More information about the Koha-devel
mailing list