https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17721
Katrin Fischer changed:
What|Removed |Added
Resolution|--- |REMIND
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17721
Nicolas Legrand changed:
What|Removed |Added
See Also|
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17721
--- Comment #6 from Nicolas Legrand ---
I didn't find explicitly such a limitation in ISO 2709.
--
You are receiving this mail because:
You are watching all bug changes.
___
Koha-bugs
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17721
--- Comment #5 from Nicolas Legrand ---
I don't see any such limitation in UNIMARC standard. Unfortunately, I don't
have a ISO 2709 version right now so I can't check there too.
--
You are receiving this
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17721
--- Comment #4 from Marcel de Rooy ---
(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
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17721
--- Comment #3 from Katrin Fischer ---
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
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17721
Séverine Queune changed:
What|Removed |Added
CC|
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17721
--- Comment #2 from Nicolas Legrand ---
ha and also no, you can't insert a 995a with a 995A when it's
collate=utf8_general_ci and the field is a key because it consider that 995a is
the same key as 995A.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17721
Nicolas Legrand changed:
What|Removed |Added
CC|
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17721
Marcel de Rooy changed:
What|Removed |Added
See Also|
10 matches
Mail list logo