Summary: | Search patrons with non-Latin languages is broken if DefaultPatronSearchFields includes date or datetime field | ||
---|---|---|---|
Product: | Koha | Reporter: | Ulrich Kleiber <ulrich.kleiber> |
Component: | Patrons | Assignee: | Bugs List <koha-bugs> |
Status: | CLOSED WORKSFORME | QA Contact: | Testopia <testopia> |
Severity: | major | ||
Priority: | P5 - low | CC: | gmcharlt, jonathan.druart, kyle |
Version: | 16.11 | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Attachments: | Bug 19967: Search patrons with non-Latin languages is brocken. |
Description
Ulrich Kleiber
2018-01-12 16:21:41 UTC
I think we need to do the fix for all date fields, I just tried adding datexpiry and it breaks the search as well. (dateexpiry, dateenrolled, lastseen, updated_on..?) To test: - Configure DefaultPatronSearchFields including dateofbirth and surname - Add a patron to your database with a cyrillig surname - Try to search for the patron - > keeps loading forever Created attachment 70490 [details] [review] Bug 19967: Search patrons with non-Latin languages is brocken. If DefaultPatronSearchFields includes a column with type date, datetime or timestamp, search patrons with non-Latin languages hangis on 'Processing...'. Converting columns with type date, datetime or timestamp to type string eliminates this bug. Ulrich, you are using a MySQLism, you should use Koha::Objects->columns instead. Hi Jonathan, is it possible to get the data type of a column with Koha::Objects->columns? Katrin mentioned, that you could not reproduce the error under MariaDB. Our MySQL Version is '14.14 Distrib 5.5.58, for debian-linux-gnu (x86_64)'. Perhaps the implicit type conversion has changed in MariaDB. Sorry Ulrich, I forgot to answer you. I've just retested and it works for me (I tried with lastseen). Can you confirm this is fixed? We have retested this in our test installationf or 20.05 and can no longer replicate the problem. Closing WORKSFORME! We have completely switched to MariaDB |