Yes, the fix is for all Koha versions. On Thu, 31 Aug 2017 at 13:24 Doug Dearden <[email protected]> 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:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jonathan > Druart > *Sent:* Tuesday, August 1, 2017 7:23 AM > *To:* [email protected]; [email protected] > *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 > _______________________________________________ Koha mailing list http://koha-community.org [email protected] https://lists.katipo.co.nz/mailman/listinfo/koha
