https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16719 --- Comment #5 from Oliver Bock <oliver.bock@aei.mpg.de> --- Steps to reproduce: 1) Map the attribute "cardnumber" for replication and update in your LDAP config 2) Create at least two users that don't yet have a value for that attribute in LDAP 3) Log in with both users one after the other 4) The second log in should result in a UNIQUE CONSTRAINT violation While "cardnumber" is NULLable, inserting/updating two borrowers with an empty string for it result in a UNIQUE CONSTRAINT violation. This proves that a semantically correct action fails with the current implementation. This wouldn't happen if NULL would be used instead of an empty string. HTH, Oliver -- You are receiving this mail because: You are watching all bug changes.