Relationship where filters {relatedList}_some: whereInput not working after update without errors
See original GitHub issueBug report
query {
allItems(where:
{ role_some: { id: "5fa13d83f96f29ecb6bed061" } }
) {
id
}
}
}
no results without error ! but this is working
query {
allItems(where:
{ role_some: { name_starts_with_i : "some string" } }
) {
id
}
}
}
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Nested filter on related model not working · Issue #331 - GitHub
(Prisma2/nexus) I am using the following (simplified) model: model Staff { id String @default(cuid()) @id @unique user User? active Boolean? }
Read more >Solved: Relationship and Cross Filtering not working quite...
I have created a relationship in PowerBI using the [StartTime]-[SequenceID] in both tables to link them together and set filtering to work in...
Read more >Filter Inputs - ent
Configure GQL. After running the code generation, we're ready to complete the integration and expose the filtering capabilities in GraphQL: 1.
Read more >Filtering and sorting (Concepts) - Prisma
Use the Prisma Client API to filter records by any combination of fields or related record fields, and sort the results.
Read more >Bi-directional relationship guidance - Power BI - Microsoft Learn
Let's now consider that the relationship between the Product and Sales table no longer filters in both directions. And, the following measure ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the bug reports, I’ve been able to recreate this and will hopefully be able to ship a fix quickly 👍
@timleslie a quick fix is to add “&& relationshipInfo.rel.cardinality !== ‘N:N’” in the commented code at row 53 here https://github.com/keystonejs/keystone/pull/4591/commits/91b3d96918858c5b7d5600e77964fb5f76010dfe
In this way it will skip N:N relationships, but still remains the huge performances issue.