https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26356 --- Comment #2 from Owen Leonard <oleonard@myacpl.org> --- Based on this and the other report you posted today, Bug 26353, it sounds like you have a server issue which is outside the scope of the help we can provide via Bugzilla. I suggest you seek help on the Koha mailing list (http://koha-community.org/support/koha-mailing-lists/), in the #koha IRC channel (http://koha-community.org/get-involved/irc/) or seek paid support here: https://koha-community.org/support/ -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26356 --- Comment #4 from Jonathan Cuéllar <jcautomatizacion@gmail.com> --- (In reply to Owen Leonard from comment #2)

Based on this and the other report you posted today, Bug 26353, it sounds like you have a server issue which is outside the scope of the help we can provide via Bugzilla.

I suggest you seek help on the Koha mailing list (http://koha-community.org/support/koha-mailing-lists/), in the #koha IRC channel (http://koha-community.org/get-involved/irc/) or seek paid support here: https://koha-community.org/support/

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. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26356 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au --- Comment #6 from David Cook <dcook@prosentient.com.au> --- (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.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26356 --- Comment #8 from Jonathan Cuéllar <jcautomatizacion@gmail.com> --- (In reply to David Cook from comment #7)

(In reply to Jonathan Cuéllar from comment #0)

...

Currently when performing a search by user in Koha using first and last name, the system takes more than 22 minutes to execute the search

I find it doubtful that it took 22 minutes. Did you mean 22 seconds?

The web server would typically time out after 5 minutes, so I don't know how it possibly could have taken 22 minutes for an out-of-the-box installation.

The timeout was extended, so it is 22 minutes -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26356 --- Comment #10 from David Cook <dcook@prosentient.com.au> --- I can't replicate your issue using the attachment provided. First, the attachment is invalid SQL. It looks like this is only a fragment of the actual SQL being run (plus it contains a number of syntax errors). Second, when I run the corrected SQL fragment directly against the database, I get a response in about .0131 seconds. So I don't think it's the SQL. I think there's probably more going on with your data and your server than is made clear in this issue report. You may have a genuine issue, but it's not reproducible or even clear what it is at this point. As Owen suggested earlier, I think your issue qualifies as a support issue rather than a bug report. I'd say you probably need to look at getting a paid support provider or dig into the code yourself. Alternatively, you may try to reproduce your own issue, and break down the steps to make it clearer to us what might be happening. For instance, with a freshly installed Koha, does this happen after importing 50,000 borrowers (and making no other changes)? How are those borrowers imported? Can you share the dataset so that someone else more technical can try to reproduce the problem in a technical environment? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26356 Alexander Borkowski <alexander.borkowski@kau.se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernard.scaife@ptfs-europe. | |com --- Comment #12 from Alexander Borkowski <alexander.borkowski@kau.se> --- *** Bug 28645 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.