stuck while running prisma db push or pull

[BNK989]

Question

I have a new nuxt project in which I'm trying to connect to my db in supabase, I've installed prisma and initiated it.
in the file prisma/schema I've added my test schema, and I'm trying to push it using 'pnpx prisma db push' I receive no error or anything like that and it seems like the connection was made (if i change the login link it throws an error. here the link I have - removed the password postgres://postgres.baqeisvusnvwlldjnlie:********@aws-0-eu-central-1.pooler.supabase.com:6543/postgres

I also tried going in to supabase, creating a table and then tried pnpx prisma db pull and have a similar result, no error just a running Introspecting based on datasource defined in prisma\schema.prisma

How to reproduce (optional)

Expected behavior (optional)

No response

Information about Prisma Schema, Client Queries and Environment (optional)

// Add your schema.prisma

// Add any relevant Prisma Client queries here

• OS:

• Database:

• Node.js version:

• Run prisma -v to see your Prisma version and paste it

[ludralph]

Hi @BNK989 👋

Thank you for raising this question.

Can you try to use the direct connection string rather than the pooled one. Here is an example of a direct connection string:

DIRECT_URL="postgres://postgres:__PASSWORD__@db.__YOUR_SUPABASE_PROJECT__.supabase.co:5432/postgres"

The default port for the pooler is 6543, but if you are using the direct connection, it should be 5432. Ensure that you are using the correct port in your connection string.

[GoldeggCoder]

Also helped me! Thanks

[stpn48]

Bro thank you worked for me ❤️

[amineanime1]

Thank YOUU finally ❤️

[darren-finch]

Love when something is this simple, thanks man.

[Brien-Austin]

yeah the same worked for me after trying to figure out for a hour

[BNK989]

Amazing Thank you, Ben N. Klinovsky

…

On Tue, Jun 11, 2024 at 3:41 PM Jan Piotrowski ***@***.***> wrote: Note that this is now also documented at Supabase: https://supabase.com/partners/integrations/prisma — Reply to this email directly, view it on GitHub <#24412 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVN4BAIB7PKH5JZ5CG5LKUTZG3V6NAVCNFSM6AAAAABIYMEPH2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TOMZYHA2TA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[guiyumin]

Thanks. It worked!

[sreenivasanac]

thanks, it worked.
Can we also have it as a comment when someone is running the command, something like
"If this command is taking more time, try moving the port from 5432 instead of default port 6543"

[robcrock]

It's unfortunate that this was the solution... Prisma needs to update the backend to reflect what users on the frontend are presented with, because it was this port number.

[geforcesong]

stupid enough

[abdullah-azeemi]

Thanks