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
Now if the filters on detail(s) returns nothing we want to skip that record entirely, this is like an inner join applied after both data loaders are run in a stacked manner: we first get orders and try to fetch relevant details with those keys afterwards.
As mentioned in the link above, the join must be done on the app layer. My question is how that could be done in an efficient manner?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Consider some query type as follows:
The scenario is similar to https://elixirforum.com/t/multiple-filters-for-related-object-types-with-a-graphql-absinthe-dataloader/29896. We want to define filters for both order and detail(s) which are fetched from different data sources.
Now if the filters on detail(s) returns nothing we want to skip that record entirely, this is like an
inner join
applied after both data loaders are run in a stacked manner: we first get orders and try to fetch relevant details with those keys afterwards.As mentioned in the link above, the join must be done on the app layer. My question is how that could be done in an efficient manner?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions