Replies: 3 comments 3 replies
-
At the top of this discussion (search drizzle) https://github.com/orgs/supabase/discussions/17817 is an example of a connection string for drizzle. Also some generic docs. https://supabase.com/docs/guides/database/connecting-to-postgres#connecting-with-drizzle Not sure if this was working for you and the Supavisor change broke it, or you are just starting out. |
Beta Was this translation helpful? Give feedback.
-
I fixed it by removing the square brackets around the password in the database URI env var 🤦🏻♀️ |
Beta Was this translation helpful? Give feedback.
-
In case this helps anyone. Had an @ sign in the middle of my sufficiently long password, didn't notice it, drizzle kit didn't care, but the postgres npm package did care. Perhaps a different regex used for parsing the connection string (?) If you try to connect to the pooler with a wrong password, you will get the rather misleading SASL_SIGNATURE_MISMATCH Also, you need to pass the supabase cert (which can be downloaded from supabase dashboard > settings > database, below the enforce ssl setting) to postgres so you don't get an error about SELF_SIGNED_CERT_IN_CHAIN
|
Beta Was this translation helpful? Give feedback.
-
Hi Everyone,
I'm working on a project using Supabase for the DB, Drizzle for an ORM, and AuthJs for authentication. I'm able to run
supabase link
without a problem, I can push local db migrations to Supabase, but when I try logging in with Google, I get the following error:If it helps, here's my
Auth.tsx
file:And here's my
Db.tsx
:I've seen elsewhere that the solution to
SASL_SIGNATURE_MISMATCH:
is to change passwords, but that hasn't helped in my situation.Many thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions