#25047: "Conflicting migrations detected" error in makemigrations is rather
unhelpful
--------------------------------------------+--------------------
Reporter: nip3o | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Management commands) | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------------+--------------------
If you run makemigrations and have more than one migration which no other
migration depend upon (a leaf in the dependency graph), you will get the
following error
{{{
Conflicting migrations detected [0001_migration_a, 0002_migration_b]. To
fix them run python manage.py makemigrations --merge
}}}
I believe that it is hard to find the cause of this error without looking
at the implementation of the checker
(https://github.com/django/django/blob/bc77eb6d0858652e197c08c299efaeb06c51efee/django/db/migrations/loader.py#L325).
I suggest that we change "Conflicting migrations detected" to something
like "There can only be one migration which are not depended upon by
another migration". I would be happy to submit a PR.
--
Ticket URL: <https://code.djangoproject.com/ticket/25047>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/048.44b2cc97b2b6801aaeaca472ff52089b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
