We’d prefer not to use pagination so the new unsetPagination() was welcomed. But we found that the limit (whatever default_per_page is) is still applied to the number of records when setCustomQuery() isn’t used. I’m not sure if this is a misunderstanding from our side? The documentation says “This is useful when you want to display all records without pagination, or when working with custom queries that return a limited dataset.” – the first part of that sentence, “when you want to display all records”, applies to us and the second part is an “or” not an “and”, so shouldn’t it work without setCustomQuery() too?
We’re using Grocery Crud Enterprise 3.2.6.