No protection exist for other tables than issues/old_issues. Note that bug 19059 (SO) will handle reserves/old_reserves. On Thu, 31 Aug 2017 at 21:04 David Cook <dcook@prosentient.com.au> wrote:
Hi Doug,
Note though that there are other tables than just ‘issues’ where you might still get duplicates. I usually find it happens to us with the ‘reserves’ table. I don’t know that there are any protections for this table in Koha if you don’t change your my.cnf file.
I’m planning to look at adding insert triggers to prevent duplicate IDs, but I just haven’t had the time to work on this yet…
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St
Ultimo, NSW 2007
Australia
Office: 02 9212 0899 <02%2092%2012%2008%2099>
Direct: 02 8005 0595 <02%2080%2005%2005%2095>
*From:* koha-devel-bounces@lists.koha-community.org [mailto: koha-devel-bounces@lists.koha-community.org] *On Behalf Of *Jonathan Druart *Sent:* Friday, 1 September 2017 2:52 AM *To:* koha@lists.katipo.co.nz; koha-devel@lists.koha-community.org *Subject:* Re: [Koha-devel] [Important] Update your MySQL|MariaDB configuration to avoid data loss
Yes, the fix is for all Koha versions.
On Thu, 31 Aug 2017 at 13:24 Doug Dearden <dearden@sarsf.org> wrote:
Hello list,
I have upgraded to 17.05.02 and taken care of two duplicate IDs on one of my instances. Do I still need to make the changes to the /etc/myscl/my.cnf file? Or did the fix in 17.05.02 make that unnecessary?
Thanks,
Doug
*From:* koha-devel-bounces@lists.koha-community.org [mailto: koha-devel-bounces@lists.koha-community.org] *On Behalf Of *Jonathan Druart *Sent:* Tuesday, August 1, 2017 7:23 AM *To:* koha@lists.katipo.co.nz; koha-devel@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