Error seeding DB via Prisma command, possible invocation error #24207
Replies: 2 comments
-
Hi @AllThingsSmitty 👋 Thank you for raising this question. The error message you're seeing is related to Prisma's connection pool timing out. This typically happens when the number of concurrent database connections exceeds the limit set by your database provider. Also, according to this section of the documentation
One way to mitigate this is to try reducing the number of concurrent request. If your seed script is trying to create a large number of records at once, consider breaking it down into smaller batches. Also, the reproduction repository you shared is returning a 404. You may want to reshare it. |
Beta Was this translation helpful? Give feedback.
-
Thanks, I think the repo set to private was throwing that 404 so I've made https://github.com/AllThingsSmitty/evento public. Thank you for the suggestion about smaller amounts of records. I trimmed down my list of records (originally 19) to just one record to see if this would work and it doesn't. I'm still getting the following error:
|
Beta Was this translation helpful? Give feedback.
-
Bug description
While running
npx prisma db seed
on my Next.js app (to seed a Postgre db hosted on Vercel) I receive the following error message:How to reproduce
npm init
to get all dependenciesnpx prisma db seed
Note
My
.env
variables that connect to Vercel's postgres db with secret password aren't included in the project. Not sure how to best get that to you.Expected behavior
Expecting to see a response that the seeding of the db has completed successfully.
Prisma information
Environment & setup
Prisma Version
Beta Was this translation helpful? Give feedback.
All reactions