https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30328
Laura Escamilla <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Laura.escamilla@bywatersolu | |tions.com Status|Signed Off |Failed QA --- Comment #42 from Laura Escamilla <[email protected]> --- While reviewing Bug 30328, I noticed a potential issue with barcode uniqueness. The barcode generation logic resets the increment to 0 when the maximum existing increment reaches 9, then increments it back to 1. I reproduced this behavior using the same increment logic and SQL calculation with a temporary table. When barcodes ending in 1 through 9 already exist for the same prefix and timestamp, the next calculated increment is 1, which would reuse an existing barcode. Additionally, the query only examines the final digit of the barcode, so increments greater than 9 are not currently supported. Both automated tests pass, but neither appears to cover this scenario. Could the increment logic be reviewed to prevent duplicate barcodes when multiple items are generated within the same second? Thank you! -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
