On bug 24379 there has been some conversation about login_attempts being set to null. While it doesn't seem to happen at creation it does during an import To recreate: 1 - Check your DB select distinct login_attempts from borrowers; 2 - All should be 0 (if you have some nulls already, thats ok) 3 - Run a report and download as CSV (you may need to set the delimiter syspref to comma) select surname, cardnumber, categorycode, branchcode FROM borrowers 4 - Tools -> Import borrowers 5 - Set to match on cardnumber and overwrite patrons 6 - Check the DB after import select distinct login_attempts from borrowers; 7 - All login_attempts are NULL
hm the column is 'default 0', so I guess the import must explicitly set it to NULL somewhere?
Tested and working in master.