https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40176
David Cook <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #14 from David Cook <[email protected]> --- (In reply to Andrii Nugged from comment #10) > usability note: > > on Kohas with MANY wrong barcodes this change (very strict) prevented it > from loading a number of bibilios and that stopped whole Koha department > from work for a while: required everyone to fix the barcodes in one day > otherwise it blocks the usage. (In reply to Andrii Nugged from comment #11) > Some of our customers used non-printable barcode for some special > codification, and it was something like "MovedBRANCHIDinum12312123" and > other customizations, which helped them to sort the books and expand usage > of barcode field to something wider. This now requires to re-think how to > use barcodes and change business logic, and even more – will require to asap > fix of database, and what's worse - manual or some complex batch, because > wrong barcodes records won't be shown after 25.05.02 update (and seems > 24.11.recent people also getting this issue). > > This really blocked number of libraries. (In reply to Katrin Fischer from comment #12) > As the barcode is varchar(20) in the database, it woudl mean that those > libraries in question have updated the field to a different datatype > previously, is that correct? > Maybe if this causes a lot of issues the barcode field could be extended in > the database and in the API by default? As Katrin says, it sounds like you customized Koha database schemas for your customers, and then experienced problems when you applied this patch, because there was a discrepancy between upstream Koha and your downstream Koha. But that's not an upstream issue. This change is logical for upstream Koha. If you're going to customize Koha downstream, the onus is on you to test your customizations to make sure they work before putting them into a production environment. It's why I typically advise people not to change the database schema downstream. It's too risky. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://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/
