-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"supabase db push" fails, generated migration contains schema "_analytics" #26245
Comments
Hey hey, thanks for opening! By default, the migrations commands exclude system schemas but it can include them if it is run with I cannot reproduce but this does not mean it is not a bug! Just want to sanity check first that |
I only used Happy to share a debug log if there is a way to exclude private/organization data. |
Hello, I have the same issue, I created a new project online, then linked it to a local projet, pulled the db. I then enabled "analytics" in config.toml then ran "db diff" to create a migration file which should not contain anything because it's a brand new project with nothing added but it does contain the definitions for the table _analytics. |
Just upgraded my local environment to v1.167.4 (CLI); issue still exists.
When I add Update: It now worked as expected using |
I have the exact same issue today. |
I've fixed this regression |
Bug report
Describe the bug
I am not able to push a local migration to my linked cloud instance. The migration file contains internal tables from the
_analytics
schema.To Reproduce
supabase db diff -f change_purchase_id_type --use-migra
(or without--use-migra
)supabase db push
Expected behavior
public
schema (?)supabase db push
succeedsdata
Commands and error
Generated migration
migration.zip
_analytics
schemapublic
schemaSystem information
The text was updated successfully, but these errors were encountered: