Replies: 1 comment
-
Thanks! Ran into this exact same issue 2 years later, and removing those two statements above as well as the below statement solved it:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm writing this for others who might run into the same problem when enabling postgis locally.
TL;DR
While writing this bug report and creating a minimal proof I found out that migra creates the following statements:
After removing them the
supabase db reset
command works.When I start a new project for local development using some postgis features I'm getting the following error after creating a migration for my schema and running
supabase db reset
for testing if they work.The command I used for the migration is:
And this is the error.
I tried the following things to add postgis to my local database.
CREATE EXTENSION postgis;
in it. No luckCREATE EXTENSION postgis;
to the first migration. No luckCREATE EXTENSION postgis;
to the second migration. No luckdocker rmi --force $(docker images --format '{{.Repository}}:{{.Tag}}' | grep 'public.ecr.aws/t3w2s2c9')
. No luckSee the gist of the migration https://gist.github.com/ff6347/5c9155ff7978a5397b301eba94493797
Beta Was this translation helpful? Give feedback.
All reactions