sweatybridge
No user record in our sample, but sweatybridge has activity below (stories or comments). Likely we have partial data — the full bulk-load will fill profiles in.
No user record in our sample, but sweatybridge has activity below (stories or comments). Likely we have partial data — the full bulk-load will fill profiles in.
> it doesn’t tell you the consequences of changing an attribute (database restart or other downtime-inducing stuff) Modern diff tools are designed to provide better guardrails in these situations. For eg, pg-schema-diff…
> When they started integrating this tool on some trial candidates they found SO many inconsistencies between environments: server settings differences, extraneous or missing indexes, vestigial "temp" tables created…
Thank you for the helpful feedback. > Using supabase migration up would mean moving the latest migration out of the migrations folder, running supabase db reset, moving the file back in and then calling supabase…
> if your latest migration is destructive - you want to seed data and then run the next migration. We have added supabase migration up [0] command that runs only pending migrations (ie. those that don't exist in local…
Hello, I work on CLI full time. Things have certainly improved over the last few months on using this tool for migrating self-hosted databases. Currently all supabase db and migration commands support --db-url flag [1]…