https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17216
Jacek Ablewicz <a...@biblos.pk.edu.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |a...@biblos.pk.edu.pl --- Comment #98 from Jacek Ablewicz <a...@biblos.pk.edu.pl> --- (In reply to Katrin Fischer from comment #97) > >Got the same error in my test setup. For undetermined reason, > >authorised_value >field in marc_subfield_structure table did not have > >utf8_unicode_ci collation. > > That's intentional. ci = case insensitive breaks uppercase subfield codes > which are often used to create additional fields in 952. marc_subfield_structure.tagsubfield indeed has utf8_bin collation, but should the same rule apply for authorised_value? By default (in fresh installs), marc_subfield_structure.authorised_value has utf8_unicode_ci collation, for some reasons (I still have no idea why, maybe update from Bug 11944 partially failed) in my old test DB, this field has no collation defined, and that's why adding FK failed for me with error 150. But it can be failing for different reason[s] for other people - and probably is, this collation issue seems to be some kind of problem which was specific to this particular DB. There is one other table (overduerules) in that DB which does not have utf8_unicode_ci collation set by default for all text fields, but it looks more like an omission in updatedatabase (Bug 13624, DB version: 3.23.00.007). -- 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/