#30467: `makemigrations app_label` sometimes tries to create migrations for
unrequested app_label
-------------------------------------+-------------------------------------
Reporter: Vsevolod Novikov | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: 2.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => invalid
Comment:
Given the `ForeignKey`, this is expected behaviour, as explained in the
[https://docs.djangoproject.com/en/2.2/topics/migrations/#dependencies
Dependencies section of the Migrations documentation], and linked to from
the `makemigrations` docs.
> While migrations are per-app, the tables and relationships implied by
your models are too complex to be created for just one app at a time. When
you make a migration that requires something else to run - for example,
you add a ForeignKey in your books app to your authors app - the resulting
migration will contain a dependency on a migration in authors.
--
Ticket URL: <https://code.djangoproject.com/ticket/30467#comment:1>
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/064.673ee9316da4cdf079a7e13269ff1270%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
