https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18428
--- Comment #3 from Barton Chittenden <[email protected]> --- (In reply to Jonathan Druart from comment #2) > To me the only clean and safe way to do that is to merge the tables. I plan > to work on that. I don't disagree that merging the tables is probably the right thing to do, but I think that we *can* safely fix the problem by adjusting the auto_increment at startup, as mentioned in IRC: 21:22 barton rangi: I think the right place to fix this is in the mysql init file. 21:22 ... we fix the problem on server startup, then we don't have to worry about it. 21:24 rangi thats not so hard for debian 21:24 there is a /etc/mysql/conf.d/ 21:24 barton by 'fix the problem' I mean set the auto_increment for issues and reserves. 21:25 rangi and my.cnf does includedir /etc/mysql/conf.d/ 21:25 so you can put a koha.cnf in there 21:25 and it will be used 21:25 and not overwritten by mysql upgrades 21:25 barton excellent. We should probably do the same thing for the deleted* tables. ... all told, I think that the tables that need to be merged or twiddled at startup is issues/old_issues, reserves/old_reserves, biblios/oldbiblios, biblioitems/oldbiblioitems, items/olditems, borrowers/deletedborrowers -- that's a lot fix at once. If we figure out how to fix one table in koha.cnf, we can do all six, then work on the plumbing. Just my two cents. -- 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/
