https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18428
Barton Chittenden <bar...@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |major --- Comment #1 from Barton Chittenden <bar...@bywatersolutions.com> --- The underlying problem is that innodb doesn't keep auto_increment across SQL server restarts -- it simply sets auto_increment to max(reserves.reserve_id)+1 on startup. Because the action of moving rows from reserves to old_reserves makes old_reserves.reserve_id higher than reserves.reserve_id, rebooting the server when it's in that state will create duplicate reserve_ids between reserves and old_reserves. since we treat deleted* tables the same way, we should also fix select distinct table_name from information_schema.columns where table_name like 'deleted%'; +--------------------+ | table_name | +--------------------+ | deletedbiblio | | deletedbiblioitems | | deletedborrowers | | deleteditems | +--------------------+ -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org 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/