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

"Reset" migrations #28

Open
ninest opened this issue Mar 14, 2022 · 1 comment
Open

"Reset" migrations #28

ninest opened this issue Mar 14, 2022 · 1 comment

Comments

@ninest
Copy link
Collaborator

ninest commented Mar 14, 2022

We currently have 5 database migrations and might end up making more before launch. Perhaps we should delete them and make a single one? We won't be losing any data and it's not important to back to the previous migrations because they were never in production.

Also, I'd recommend reading through these (if you haven't already). Migrations can get a little confusing and we sometimes do have to manually edit SQL files when we, for example, want to rename a column.

@adidoesnt
Copy link
Owner

Yeah, makes sense to delete the old migrations. Had a read of the resources attached!

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

2 participants