https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17721 --- Comment #4 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- (In reply to Katrin Fischer from comment #3)
We need the table or the column to be case sensitive in order to be able to configure, store and retrieve uppercase and lowercase subfields separately.
I am no MySQL expert, so can't tell what is the perfect type to use for that use case.
Documenting the behaviour is of course always a good idea. A comment in kohastructure.sql maybe?
I am all for a comment at least. As mentioned before, using uppercase subfields is not MARC conform. https://www.loc.gov/marc/96principl.html tells me: === Subfield codes in the MARC 21 formats consist of two characters--a delimiter [1F(16), 8-bit], followed by a data element identifier. A data element identifier may be any lowercase alphabetic or numeric character. === Dont be confused about the delimiter. The last sentence about data element is important. Since many libraries seem to use the concept, we could permit it (somewhat reluctantly). A comment that we use this collation for that reason should be added in kohastructure. -- You are receiving this mail because: You are watching all bug changes.