Added bug 18970 for the test each new issue id - approach.
Not sure if 18966 is the way to go, "halting the system" until we fixed the autoincrement.
I suppose we’d have to make sure the deleted flag is indexed, and it would mean changing many SQL reports not to include deleted records… so that might be easier said than done.
Alternatively, maybe we need more robust logical (ie code) ways of managing the relationships between active and inactive (ie deleted) data? I mean… what’s the point of keeping a history of data if we can’t use it?
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@lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org]
On Behalf Of Jonathan Druart
Sent: Friday, 21 July 2017 3:23 AM
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] AUTO_INCREMENT fix - prevent data lost
And see bug 18966 for a third (last!?) round. I tried to resume in the description of the bug what has been done and what I propose to move forward.
BE INVOLVED!
On Wed, 12 Jul 2017 at 15:11 Jonathan Druart <jonathan.druart@bugs.koha-community.org> wrote:
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