cake
CCConvex Community
•Created by cake on 5/13/2025 in #support-community
Workflow for migrations?
Does that incur costs when turning the schema on and off? I assume when it’s turned back on it’s going to check the schema again?
15 replies
CCConvex Community
•Created by cake on 5/13/2025 in #support-community
Workflow for migrations?
I might leverage turning on and off schema validation
15 replies
CCConvex Community
•Created by cake on 5/13/2025 in #support-community
Workflow for migrations?
Until I'm at the scale where I need to worry that going down for 5 minutes at 3 AM is a problem, I'd rather not worry about it with my migrations.
15 replies
CCConvex Community
•Created by cake on 5/13/2025 in #support-community
Workflow for migrations?
When you only have a few thousand customers, migrations can still be done in seconds, even on convex I'd imagine
15 replies
CCConvex Community
•Created by cake on 5/13/2025 in #support-community
Workflow for migrations?
migrations typically only impact a small portion of the data that a user could access typically, and convex's ability to "continue" migrations or re-run migrations without migrating the same data twice seems particularly valuable here
15 replies
CCConvex Community
•Created by cake on 5/13/2025 in #support-community
Workflow for migrations?
Maybe migrations take a bit longer in convex, or maybe it's best practice to always do them with zero-downtime taken into account, but there is an overhead cost to that decision that I now have to take on
15 replies
CCConvex Community
•Created by cake on 5/13/2025 in #support-community
Workflow for migrations?
Thanks for your write-up
15 replies
CCConvex Community
•Created by cake on 5/13/2025 in #support-community
Workflow for migrations?
It seems like my schema is defined in code, and my migrations don't effect schema, just migrate data. This seems particularly annoying.
If I have a list of all my migrations that need to run, it also seems like I need to remove all run migrations from that list after every release (meaning I have to keep track of what's been run and not run in production), and then after it runs, I can update my schema to it's final, tightened value.
This dance between run migrations, and the current schema, because migrations don't change schema, seems particularly cumbersome. Are there any solutions?
15 replies