You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2022. It is now read-only.
Ideally every schema change would be accomplished via a generated migration script that is saved in a commit.
This is how it works in Rails (https://guides.rubyonrails.org/active_record_migrations.html) - you run a CLI command to generate a new migration, it creates a timestamped script, you edit the script and add commands for modifying the schema as well as any logic you might need for manipulating data. Then you run the migrate command and it will sequentially run the migrations up until the latest.
The benefit to this is that team members can easily be on the same schema regardless of what commit they are on.
We need a solution for renaming a field or a type, without having to rewrite the entire data.
P.S. Have a look at how EdgeDB does this: https://www.edgedb.com/showcase/migrations
The text was updated successfully, but these errors were encountered: