http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14067 --- Comment #5 from Barton Chittenden <barton@bywatersolutions.com> --- (In reply to David Cook from comment #4)
(In reply to Barton Chittenden from comment #2)
Here's the error as found in intranet-error.log
[Mon May 04 08:52:27 2015] [error] [client xx.xx.xx.xx] [Mon May 4 08:52:27 2015] deletemem.pl: DBD::mysql::st execute failed: Column 'cardnumber' cannot be null at /usr/local/share/perl/5.10.1/DBIx/Class/Storage/DBI.pm line 1834. [Mon May 04 08:52:27 2015] [error] [client xx.xx.xx.xx] Premature end of script headers: deletemem.pl
That's an interesting error. When I look at my databases, 'cardnumber' is a nullable column. I'd suggest looking at Koha::Schema::Result::Borrower.pm and seeing if "cardnumber" has "is_nullable" set to 1. I'd also check the actual database to see if it's a nullable column...
Yes, borrowers.cardnumber is nullable in the database in question: mysql> describe borrowers; +---------------------+--------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +---------------------+--------------+------+-----+---------+----------------+ | borrowernumber | int(11) | NO | PRI | NULL | auto_increment | | cardnumber | varchar(16) | YES | UNI | NULL | | and in /usr/share/koha/lib/Koha/Schema/Result/Borrower.pm =head2 cardnumber data_type: 'varchar' is_nullable: 1 size: 16 So... I don't know. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.