https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17216
--- Comment #100 from Jacek Ablewicz <a...@biblos.pk.edu.pl> --- Huh, this is what happens (mysql 5.5.49): for a table with no default collation defined on table level (like marc_subfield_structure) MODIFY COLUMN authorised_value VARCHAR(32) DEFAULT NULL does not preserve existing collation for that field (which was, after all, utf8_unicode_ci in my test DB before attempting that upgrade: manually set up to utf8_unicode_ci for a bunch of marc_subfield_structure fields in DB update from Bug 11944), and it subsequently fails with error 150 on adding FK constraint because of collations inconsistency (I think.. not quite sure, but a solution from comment #96 fixes this problem). It's reproductible; note that I have different default collation defined mysql server-side on that box (utf8_general_ci) - if it was utf8_unicode_ci server-side, I guess there is a possibility this issue does not manifest itself (?). -- 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/