Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add configuration to disable query batching #23730

Open
janpio opened this issue Apr 4, 2024 · 2 comments
Open

Add configuration to disable query batching #23730

janpio opened this issue Apr 4, 2024 · 2 comments
Labels
domain/client Issue in the "Client" domain: Prisma Client, Prisma Studio etc. kind/feature A request for a new feature. topic: batching topic: client api topic: performance

Comments

@janpio
Copy link
Contributor

janpio commented Apr 4, 2024

Sometimes our batching functionality (see https://www.prisma.io/docs/orm/prisma-client/queries/query-optimization-performance#solving-n1-in-graphql-with-findunique-and-prisma-clients-dataloader) does not work as intended (see for example bugs with label topic: batching).

Right now, there is no way for our users to opt out of that functionality.
We should add one, disableQueryBatching: true or findUniqueBatching: false could work in some form.

@macrozone

This comment was marked as off-topic.

@ericallam
Copy link

Would definitely be nice to be able to do this, as it recently caused outage on trigger.dev by doing a full table scan. ref: https://twitter.com/maverickdotdev/status/1800178147897561317

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain/client Issue in the "Client" domain: Prisma Client, Prisma Studio etc. kind/feature A request for a new feature. topic: batching topic: client api topic: performance
Projects
None yet
Development

No branches or pull requests

3 participants