Error occurred during query execution: ConnectorError(ConnectorError
See original GitHub issueIt seems to me like the pgbouncer=true
option is not being respected, any idea why this is the case?
Not sure if anybody else is facing the same.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Error occurred during query execution: cause: Some ... - GitHub
I get a pretty useless error message when I run into this. Error occurred during query execution: ConnectorError(ConnectorError { ...
Read more >prisma create with nested connect throws error - Stack Overflow
Invalid `prisma.movie.create()` invocation: Error occurred during query execution: ConnectorError(ConnectorError { user_facing_error: None, ...
Read more >PrismaClientUnknownRequestEr...
PrismaClientUnknownRequestError: Error occurred during query execution: ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(Error ...
Read more >V3: 'cached plan must not change result type' error by Enum ...
V3: 'cached plan must not change result type' error by Enum ... Error occurred during query execution: ConnectorError(ConnectorError ...
Read more >Error message reference - Prisma
Prisma Client, Migrate, Introspection error message reference. ... "Multiple errors occurred on the database during query execution: {errors}" ...
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
Alright, I am finishing some work on pmt and will make a release soon (this evening probably)
Ok my bad, I recall largely the reason why I wanted to update prisma from 2.2.0 to 2.4.1 was because of this issue on Prisma
https://github.com/prisma/prisma/issues/2921
I think
pmt
on 2.4.1 should fix this