> > I'm also thinking it might be much helpful to detect the rename as much as > possible and give warning message about developer has to modify the > migration to rename field properly >
sure, but how would you do this? And how would you cover all the possible cases to detect whether the dev intends to delete a field and replace it with another vs renaming the field entirely? For the django core devs, I can see this being a very large effort feature that, despite everything, is very brittle and introduces uncertanity in migrations. Having an option like that for makemigrations could be useful as an alternative. Perhaps you can write up a ticket for that at https://code.djangoproject.com/query for discussion? -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/3ae0aee2-adc9-4a4d-ada9-3177c9e3d66f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
