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.

Sign up for GitHub

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

Jump to bottom

Should we add IgnoreMigration()into the second step migration? #32

Open
tarasinf opened this issue Jul 23, 2024 · 0 comments
Open

Should we add IgnoreMigration()into the second step migration? #32

tarasinf opened this issue Jul 23, 2024 · 0 comments

Comments

@tarasinf
Copy link

The question is about the second step:

Lastly, after the changes above have been deployed, field1 can then safely be removed in the model (plus another makemigrations run)

When we remove a field that was deprecated in the previous release by adding deprecate_field(), should we add IgnoreMigration() into migration where we remove the field in the second step?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tarasinf