http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5860
--- Comment #13 from M. de Rooy <m.de.r...@rijksmuseum.nl> 2011-05-13 12:56:13 UTC --- (In reply to comment #12) > I talked to Chris about it in the morning and we debated if checking for the > uniqueness of the index might be away to make it easier not relying on version > numbers. > We also need a patch for 3.2.x and 3.4, because the bug is currently in all > maintained versions. People are at different stages when updating, some might > be in between and have run into a mysql error message and are already past the > update with index still being unique. > I think what we need to do is add another database update at the end. Making > sure that in every case the index will be fixed. As I said a check for > uniqueness using the information_schema tablae and the NOT_UNIQUE field might > be easier here. I would not use information_schema if you do not include name of database (Table schema). Do you send another revision? -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug. _______________________________________________ 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/
