The user search in reserve/request.pl got broken by bug 13894. The search using the "recordset" doesn not care for "lastname, firstname" as before, instead finding nothing. Scenario: EASY SETUP: database with two borrowers with same last name, and one record minimu. 1) go to KOHA_SITE/cgi-bin/koha/reserve/request.pl?biblionumber=1 2) enter the last name. You should get two results in the table 3) same site, enter "lastname, firstname" (comma optional). You get no result. This used to work before 13894. Vile RecordSet broke it...
Actually, problem seems with C4/Utils/DataTables/Members.pm 's search method.
Created attachment 49877 [details] [review] Bug 16197 - Specifying both last and firstname in reserve's patrong search yields nothing. The user search in reserve/request.pl got broken by bug 13894. The search using the "recordset" doesn not care for "lastname, firstname" as before, instead finding nothing. Test scenario: EASY SETUP: database with two borrowers with same last name, and one record minimu. 1) go to KOHA_SITE/cgi-bin/koha/reserve/request.pl?biblionumber=1 2) enter the last name. You should get two results in the table 3) same site, enter "lastname, firstname" (comma optional). You get no result. 4) Apply the patch, same test now return the one matching result.
Created attachment 49887 [details] [review] Bug 16197 - Specifying both last and firstname in reserve's patrong search yields nothing. The user search in reserve/request.pl got broken by bug 13894. The search using the "recordset" doesn not care for "lastname, firstname" as before, instead finding nothing. Test scenario: EASY SETUP: database with two borrowers with same last name, and one record minimu. 1) go to KOHA_SITE/cgi-bin/koha/reserve/request.pl?biblionumber=1 2) enter the last name. You should get two results in the table 3) same site, enter "lastname, firstname" (comma optional). You get no result. 4) Apply the patch, same test now return the one matching result. Signed-off-by: Nick Clemens <nick@bywatersolutions.com>
I signed off, but am marking to in discussion as I think this is the same issue as 15930. I like this approach, but it causes issues for the patch of 15252. I think the best solution proposed is to use "quotes" to force phrase searching for two part names
Blou, please jump into the discussion on bug 15930. I'd like to provide a global fix for this issue.
*** This bug has been marked as a duplicate of bug 15930 ***