Hi there For quite a while have not been able to...
# help
m
Hi there For quite a while have not been able to push migrations to remote databases. It gives following error:
Copy code
~/a/web ❯❯❯ supabase db push
Applying unapplied migrations...
Error: ERROR: permission denied for schema graphql_public (SQLSTATE 42501)
Migrations work locally, but not remove. Neither on our existing project or completely newly created projects
n
Hello @madsbuch! This thread has been automatically created from your message in #843999948717555735 a few seconds ago. We have already mentioned the @User 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.
m
It seems like the
remote_commit
migration that the supabase CLI created is faulty and has introduced a lot of breaking elements.
So, even creating an initial migrations and then trying to push that fails:
Copy code
~/a/web ❯❯❯ supabase db commit "initial commit"
Finished supabase db commit on branch main.
WARNING: The diff tool is not foolproof, so you may need to manually rearrange and modify the generated migration.
Run supabase db reset to verify that the new migration does not generate errors.
~/a/web ❯❯❯ supabase db push 
Applying unapplied migrations...
Error: ERROR: permission denied for schema graphql_public (SQLSTATE 42501)
Can also just add in what happens on reset:
Copy code
~/a/web ❯❯❯ supabase db reset
Error: Error resetting database: ERROR:  schema "graphql_public" does not exist
Nvm, it seems like the entire ecosystem is going to use Prisma for migrations. We will probably also just do that.
n
Thread was archived by @madsbuch. Anyone can send a message to unarchive it.
madsbuch (2022-05-24)