Skip to content
This repository was archived by the owner on Apr 14, 2022. It is now read-only.

Filter over boundaries of 1:N connections #94

Closed
Totktonada opened this issue Mar 22, 2018 · 1 comment
Closed

Filter over boundaries of 1:N connections #94

Totktonada opened this issue Mar 22, 2018 · 1 comment
Assignees
Labels
customer enhancement New feature or request prio3
Milestone

Comments

@Totktonada
Copy link
Member

Consider empty list for a subrequest as a non-match situation.

@Totktonada Totktonada added the enhancement New feature or request label Mar 22, 2018
@Totktonada Totktonada added this to the 0.0.1 milestone Apr 17, 2018
@Totktonada Totktonada modified the milestones: 0.0.1, 0.0.2 Jul 10, 2018
@opomuc
Copy link

opomuc commented Jul 13, 2018

Basically customer wants such thing:

Let's assume we have a filter individuals(individual_customer_relation: {uid: $num}, last_name: $last_name) where individual_customer_relation is a 1:N connection to another space. Three situations are possible:

  • last_name is specified
  • num is specified
  • both last_name and num are specified

We need to be able to filter resulting data in all of those 3 situations. When num is present -- only those individuals that have >= 1 of connected objects with uid == num must be returned. And so on

Totktonada added a commit that referenced this issue Aug 7, 2018
It is primarily for filters over 1:N connection borders (#94).
Totktonada added a commit that referenced this issue Aug 16, 2018
It is primarily for filters over 1:N connection borders (#94).
@Totktonada Totktonada self-assigned this Sep 4, 2018
Totktonada added a commit that referenced this issue Sep 4, 2018
Totktonada added a commit that referenced this issue Sep 4, 2018
Totktonada added a commit to Hollow111/graphql that referenced this issue Sep 14, 2018
…-over-1-n-conn

Support filters over 1:N connections
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
customer enhancement New feature or request prio3
Projects
None yet
Development

No branches or pull requests

2 participants