How do I setup my Supabase DB connection string to work with Prisma Accelerate
Supabase currently provide 2 connection modes; Session and Transaction (Pooler). From all indications, using the transaction mode (with pgbouncer=true) as the connection string in my Prisma Accelerate dashboard seems to be the intended approach. However, I get
Error occurred during query execution:
ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(PostgresError { code: "26000", message: "prepared statement \"s2\" does not exist", severity: "ERROR", detail: None, column: None, hint: None }), transient: false })
On the other hand, if I set the session mode connection url on my Accelerate dashboard, I get Client Max Connections Reached
Really need some pointers here for anyone who has been able to get this to work. Thanks.4 Replies
Hey @Edward
Can you please try using the non-pooled connection string, the one with port 5432 and check if you get the same error?
Hi @Nurul (Prisma)
I was having the same problem, but when I used the direct_url, I did not get the error until now,
Thank you
@Nurul
it started giving this error again??

Did this happen while developing locally or on your deployed app?