supabse db remote throws error starting shadow database
I have multiple migrations scripts in my supabase folder. Any time I run or I get hit with this error
During the setup, I can see that it applies my initial remote commit (first migration file) and then throws the error on the second migration file. The first line of the second file is
The weird thing is that if I run it goes through the migration files just fine. One thing to note is that I delete "my_table" entirely in a later migration, but the table is definitely initiated in the initial migration file.
I haven't wanted to make any changes on the
(actual) database because of this error, and have had to go through the steps of starting the container, creating new migration, and then pushing. Any help would be appreciated
During the setup, I can see that it applies my initial remote commit (first migration file) and then throws the error on the second migration file. The first line of the second file is
The weird thing is that if I run it goes through the migration files just fine. One thing to note is that I delete "my_table" entirely in a later migration, but the table is definitely initiated in the initial migration file.
I haven't wanted to make any changes on the
(actual) database because of this error, and have had to go through the steps of starting the container, creating new migration, and then pushing. Any help would be appreciated
