You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
whenever i try to make a count and a group by on a foreign key (and use a "having" clause) in a list view, i got an error from the paginator.
I know this is a known issue, because of #1829 or #1557 but i couldn't find any opened issue.
I definitely need to filter some data from a count() on a foreign key... does anyone know a workaround please ?
Thank for your answer
The text was updated successfully, but these errors were encountered:
Sadly I don't know if there is a solution for this. We've tried all possibilities (true, false, etc.) and it always failed for some people. Honestly I don't know if this problem is because of Doctrine, the paginator or this bundle.
couldn't we at least provide a parameter for the "list" view, that gives us the possibility to chose wether or not using outputWalker ?
And probably disable sorting on foreign keys in that case.
I need to make different lists, based on a groupBy and a count() which could not be handled via dql_filters, and i had to override AdminController::createOrmPaginator to perform this...
I'm closing this issue because we're starting a new phase in the history of this bundle (see #2059). We've moved it into a new GitHub organization and we need to start from scratch: no past issues, no pending pull requests, etc.
I understand if you are angry or disappointed by this, but we really need to "reset" everything in order to reignite the development of this bundle.
Hello,
whenever i try to make a count and a group by on a foreign key (and use a "having" clause) in a list view, i got an error from the paginator.
I know this is a known issue, because of #1829 or #1557 but i couldn't find any opened issue.
I definitely need to filter some data from a count() on a foreign key... does anyone know a workaround please ?
Thank for your answer
The text was updated successfully, but these errors were encountered: