Low Search and EE5
Hi Support,
When I apply Low search at EE5 for a channel with approx 32 fields, result is broken. I receive an exception "MySQL can only use 61 tables in a join"
I tried debugging and found that channel entry model is doing this. But when I fetch all fields of channel entry out of Low search, all fields are returned.
Can you share any thoughts over the cause of this exception? Is it relevant with LowSearch or it could be anything else.
- Abhi
Replies
Low 2 May 2019 07:19
Well, this sounds like a limitation to MySQL and EE4's new field setup, where each field gets its own table. So not necessarily LS related -- in fact, LS tries to keep its queries lean and mean before calling the native Channel Entries module to display the search results.
I'd confer with EllisLab about this.
W3care Developer 3 May 2019 05:00
Thanks for getting back to me Low. I also had the same thought that it must be an issue related with EE4 but when I try to list all the entries of that channel by using simple channel entry tag, I don't see any such exception. I assume that the tag is also joining the fields' tables, isn't it?
Kindly let me know if you receive any response from EllisLab which can help us in sorting this problem.
Thanks indeed :)
Low 3 May 2019 07:51
Actually, I suggested you should ask EllisLab.
The query that is throwing the error is generated by the native Channel Entries module (see your other now closed thread). Low Search merely calls the native Channel module to display the search results.
W3care Developer 7 May 2019 05:42
Ok Low, thanks for the replies. I have been trying to find a fix either with EllisLab or by reducing some fields for that channel.
Have a good day :)