Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] can't list and count on a foreign key #2019

Closed
nikophil opened this issue Jan 23, 2018 · 4 comments
Closed

[BUG] can't list and count on a foreign key #2019

nikophil opened this issue Jan 23, 2018 · 4 comments
Labels
bug help wanted Issues and PRs which are looking for volunteers to complete them.

Comments

@nikophil
Copy link

nikophil commented Jan 23, 2018

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

@javiereguiluz
Copy link
Collaborator

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.

@javiereguiluz javiereguiluz added the help wanted Issues and PRs which are looking for volunteers to complete them. label Jan 25, 2018
@nikophil
Copy link
Author

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...

@javiereguiluz
Copy link
Collaborator

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.

@Pierstoval
Copy link
Contributor

I would definitely need this kind of feature, so is it possible to reopen? 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug help wanted Issues and PRs which are looking for volunteers to complete them.
Projects
None yet
Development

No branches or pull requests

3 participants