It's easy enough to read the output before you migrate. It's pretty darn hard to accidentally delete an entire Model. It'd have to be a new or obscure Model with no references in your Views, no ForeignKeys to it, etc etc. Deleting a Field accidentally on the other hand is pretty easy to do. I do feel that migrations are a major sore point in Django. I don't believe that *"*Make sure to read the output to see what makemigrations* thinks you have changed - it’s not perfect, and for complex changes it might not be detecting what you expect." * is good enough for us. A flag/option for this wouldn't hurt.
-- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/6262515b-ca57-4708-8240-fb618115cc54o%40googlegroups.com.
