Bug description
I was having this error with a Next.js build while deploying to Zeit. It uses getStaticProps, but I doubt that is relevant here.
I'm using a brand new Digital Ocean Postgres instance with their connection pool.
17:53:37.265 PrismaClientUnknownRequestError:
17:53:37.265 Invalid `prisma.product.findOne()` invocation:
17:53:37.265 Error occurred during query execution:
17:53:37.265 ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(Error { kind: Db, cause: Some(DbError { severity: "ERROR", parsed_severity: Some(Error), code: SqlState("42P05"), message: "prepared statement \"s0\" already exists", detail: None, hint: None, position: None, where_: None, schema: None, table: None, column: None, datatype: None, constraint: None, file: Some("prepare.c"), line: Some(473), routine: Some("StorePreparedStatement") }) }) })
How to reproduce
Try to use Prisma client with with Digital Ocean Postgres and pgbouncer in transaction mode. It was failing every time for me.
Prisma migrate worked correctly.
Expected behavior
It should work
Prisma information
"@prisma/cli": "2.0.0-beta.2",
"@prisma/client": "2.0.0-beta.2",
Bug description
I was having this error with a Next.js build while deploying to Zeit. It uses getStaticProps, but I doubt that is relevant here.
I'm using a brand new Digital Ocean Postgres instance with their connection pool.
How to reproduce
Try to use Prisma client with with Digital Ocean Postgres and pgbouncer in transaction mode. It was failing every time for me.
Prisma migrate worked correctly.
Expected behavior
It should work
Prisma information