There is a dependency line at the beginning of every migration which requires an earlier migration to have been executed.If you name your migration files alphanumerically in the sequence you want them to run AND the dependencies all line up AND the django_migrations table does not indicate your migrations have already been run AND the database migrations actually have not happened OR are idempotent, everything should run smoothly.Mike--(Unsigned mail from my phone) -------- Original message --------From: Douglas Silva <dogusky.t...@gmail.com> Date: 17/3/21 07:20 (GMT+10:00) To: Django users <django-users@googlegroups.com> Subject: How django's migration system works? I have two apps in my project: transitions and maintenance. One to deal with data insertions and another to deal with models. This is the current structure and cannot be changed.I would like to know how do I run all transitions migrations first and then maintenance ones.
-- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-users/4ccf7c36-5c98-429d-b954-34295c886023n%40googlegroups.com. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-users/605124ab.1c69fb81.3778c.720fSMTPIN_ADDED_MISSING%40gmr-mx.google.com.
