https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18651
--- Comment #71 from Katrin Fischer <[email protected]> --- At this moment, I don't feel confident in this patch set to be the right fix. - We will keep the state of constant renumbering. Once a MySQL restart has caused the issue, you will never fully recover from it. - We introduce new issues with the lock/race condition as it keeps check ins from happening in my tests pretty constantly. At this point, I am wondering if we shouldn't go as far as reverting bug 18242 and push massively for the database based fix. If your DB has the doubled up id issue, it means that when returning those items, the entry will get lost, but the problem will end there. I have a feeling, that the current fix causes issues like https://lists.katipo.co.nz/pipermail/koha/2017-July/048437.html But I am not fully grasping how it happens yet. Also we have seen weird issues in circulation ourselves testing 16.11.x. with problematic issue_ids. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
