Error starting local database
I'm trying to start developing locally instead of hitting my project database directly. I've done
supabase init in my folder, supabase link and tried to supabase db pull to get an initial schema. Once I have that schema, it asks me if I want to apply it to the remote migrations and I do that. Then, when I try to supabase db pull again, I get the included very long set of warnings about privileges and then a failure due to ERROR: function public.armor(bytea) does not exist (SQLSTATE 42883)
I could include the initial migrations file, but it does include CREATE EXTENSION IF NOT EXISTS "pgcrypto" WITH SCHEMA "public"; and other extensions. Why might I be seeing this error? I'm very happy to introduce additional info as needed2 Replies
Bumping as I truly am at a loss as to how to solve this, I assume it's an issue with the way the docker containers are being set up but I really am having trouble googling a solution and AI is useless here.
after you did supabase link, did you stop/start the local supabase? that will ensure the versions are the same.