#23790: Possible bad interaction between migration dependencies and relabeling
apps
-------------------------------+--------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Description changed by MarkusH:
Old description:
> As far as I can tell, in migrations, `dependencies` is a list of
> `(app_label, migration_name)`.
>
> I'm wondering what happens if one relabels an application with
> `AppConfig.label`. How can migrations handle this case?
>
> (I haven't tried to create such a problem. I'm just making a note before
> I forget.)
>
> The only way I can think of is using the `appconfig.name` attribute
> instead of `appconfig.label`. But that's hard to find a smooth migration
> path.
New description:
As far as I can tell, in migrations, `dependencies` is a list of
`(app_label, migration_name)`.
I'm wondering what happens if one relabels an application with
`AppConfig.label`. How can migrations handle this case?
(I haven't tried to create such a problem. I'm just making a note before I
forget.)
--
--
Ticket URL: <https://code.djangoproject.com/ticket/23790#comment:2>
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/067.ef9f91f00b159729890d7ef651154818%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
