Replies: 2 comments 2 replies
-
I think I partly know what you mean, but, you have a many to many but are using the ManyToOne? |
Beta Was this translation helpful? Give feedback.
2 replies
-
Would like to point out that it would be awesome if we can figure out a way to make this work smoother, like that for the filtering it stays as is (so you can still use your custom fields) but have a option to directly (in your case) the user. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Let's say you have a Project and a User entity with a many to many relation Project_User:
The naive approach would be that you add a
@Relation
on top of each class and then you'll end up querying your project and users like this:Is there an easy way to do it like that instead?
I manage to make it work by making the ProjectService extend the RelationQueryService but it doesn't use the dataloader (so it's making on user database request for each project).
Have you ever faced this situation?
Beta Was this translation helpful? Give feedback.
All reactions