Skip to content
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

Add how-to guide on "incremental migrations" #117

Open
cloutiertyler opened this issue Dec 16, 2024 · 0 comments
Open

Add how-to guide on "incremental migrations" #117

cloutiertyler opened this issue Dec 16, 2024 · 0 comments

Comments

@cloutiertyler
Copy link
Contributor

Instead of migrating an old table, just add a new table alongside it, like player_v_2. When you want to do an operation, first check if the v_2 table has a row. If it does, you've already "migrated" that row, so use it. If it doesn't, look for a row in the old table, migrate it, insert it into the v_2 table, and then do the op. Wow! It's almost like we had migrations, except we don't!

Write a doc that describes how to do this in more detail, with examples.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant