https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633
--- Comment #72 from Andrew Fuerste-Henry <[email protected]> --- Sorting almost works correctly with these patches. The following three patrons show up in this order in a default patron search (ascending name sort): - surname: Acevedo, preferred_name: [blank], firstname: Hank - surname: Acevedo, preferred_name: [blank], firstname: Henry - surname: Acevedo, preferred_name: [blank], firstname: Hosea When I added a preferred_name I got: - surname: Acevedo, preferred_name: Angel, firstname: Henry - surname: Acevedo, preferred_name: [blank], firstname: Hank - surname: Acevedo, preferred_name: [blank], firstname: Hosea And then with a second preferred_name: - surname: Acevedo, preferred_name: Angel, firstname: Henry - surname: Acevedo, preferred_name: [blank], firstname: Hosea - surname: Acevedo, preferred_name: Zeus, firstname: Hank BUT things go weird if preferred_name is NULL -- in KTD the default data has preferred_name null but saves new/edited patrons with a blank instead. In the real world, I imagine patrons could be imported with a NULL value. With NULL preferred_names I get: - surname: Acevedo, preferred_name: NULL, firstname: Henry - surname: Acevedo, preferred_name: NULL, firstname: Hosea - surname: Acevedo, preferred_name: NULL, firstname: Hank -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
