-
Notifications
You must be signed in to change notification settings - Fork 29
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
Propel / Filtering w. many to many #234
Comments
👍 so good to read some Propel users :) I think issue is here. It should be $this->joins[$joinAlias] = call_user_func_array(array($parentQuery, 'use'.$field.'Query'), array($joinAlias, \Criteria::INNER_JOIN)); (note the $joinAlias at the end instead of $field). According to this documentation Let me know if it works, Thank you @Lionel09 |
Thanks for your feedback! I revert my change in Example with an object If I try this config in the yml of Document:
I've got an error:
|
Hi @Lionel09 My mistake, I didn't carefully read your post... I came back on you "corrected" version of
But the thing is: I actually don't know what really is the initial issue. Do you have any additional informations to provide us? Do you have any error? In the console or in a page? With all of this, we should find the right way to handle the collection filter. Thanks for your help |
I've just done some tests to filter list results with objects related in many to many relations.
I've tried to fix this issue for Propel, but that's not finished so I'm just putting here some works to remind me later and to have feedbacks.
Fix config type:
Fix PropelQueryFilter:
Finally, I've got an error in "counting result"
Stack trace:
This SQL request throws the error:
every derivated table must have its own alias
The text was updated successfully, but these errors were encountered: