3 ms·
I have a feeling that does not work at all in non-trivial scenarios, e.g. if both composite keys and date range matching are required to resolve a reference.
by eurasiantiger 6y ago
I have a feeling that does not work at all in non-trivial scenarios, e.g. if both composite keys and date range matching are required to resolve a reference.
- sbarre 6y agoCould you test this and get back to us with the results?
- sorenbs 6y agoThere are pretty extensive docs on how Prisma optimises n+1 queries: https://www.prisma.io/docs/guides/performance-and-optimization/query-optimization-performance#n1-in-other-contexts https://www.prisma.io/docs/guides/performance-and-optimizati...
- eurasiantiger 6y agoThe examples are still for a trivial case of joining one thing to many things. What about joining one thing to many things that join to many things that join to one thing that joins to many things that join to many things that join to many things?
- Sujan 6y agoNo need to test really - indeed more complicated cases are not covered by this yet. But happy to look at any Github issues with reproduction of cases that are not working, but could or should work to make your life better.