Supabase is an open source Firebase alternative. Start your project with a Postgres database, Authentication, instant APIs, Edge Functions, Realtime subscriptions, and Storage.

Supabase

I've followed the docs on how to connect to prisma but I am having this issue where it says 

`prepared statement "s0" already exists`

 I understand this has something to do with connection pooling and pgBouncer, since I am working on a remix project that's being hosted on netlify but as far as I understand my connection string doesn't have the pgbouncer query param in it, also I've tried to change the connection pooling settings but it hasn't helped.

Hello <@690660491982274650>!
This thread has been automatically created from your message in <#843999948717555735> a few seconds ago.

We have already mentioned the <@&951828363943759883> so that they can see your message and help you as soon as possible!

**Want to unsubscribe from this thread?**
Right-click the thread in Discord (or use the ``...`` menu) and select "Leave Thread" to unsubscribe from future updates.

**Want to change the title?**
Use the ``/title`` command!

**We have solved your problem?**
Click the button below to archive it.

Check the last paragraph
https://supabase.com/docs/guides/integrations/prisma

https://github.com/prisma/prisma/issues/6485

I saw the last paragraph on the supabase docs, that's why I mentioned it on the question, the docs say to use the connection string as in step 4 which doesn't exist or isn't actually numbered

But also the docs only mention this happening during migrations, and I'm making a query

I don't know if there's a way to suggest a change in the docs, but for sure the last two paragraphs here https://supabase.com/docs/guides/integrations/prisma can be more descriptive of the issue, this was fixed by adding the pgbouncer=true param to the connection string, it does say it'll be needed when deploying, but it is also needed to work locally, and not only for a migrations issue