https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26356
David Cook <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #6 from David Cook <[email protected]> --- (In reply to Jonathan Cuéllar from comment #0) > I don't think the problem is server-side, knowing that the reports were > working, additionally I am more focused on why the query generates so many > OR borrower ... OR borrower ... Or borrower, and if there is any way to > monitor the SQL generated by the platform. I appreciate the help you can > give me. Mmm very interesting. I don't have time to comprehensively look into this, but it appears that the SQL has so many "OR borrower" strings because Koha found patrons with attributes that matched your search terms... That server-side code is problematic. If you had too many matches (eg around 30,000-40,000), you'd probably actually crash Koha (as there limits on the length of SQL queries). I've actually seen this issue in other relational database-driven systems. But... if you're searching "jonathan cuellar" and you're getting that many matches off attributes, then it sounds like an issue with your data. -- You are receiving this mail because: You are the assignee for the bug. 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/
