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 ability to set Prisma connection_limit for each deployment separately #1208

Open
mipyykko opened this issue Jun 8, 2023 · 0 comments
Open

Comments

@mipyykko
Copy link
Collaborator

mipyykko commented Jun 8, 2023

Some deployments using the same backend don't really need the same amount of connections in the pool. Don't know how this is actually affecting anything, but anyway.

Possibly need to pass the full connection string, as Prisma schema needs to be able to access the env value directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant