#23790: Possible bad interaction between migration dependencies and relabeling
apps
-------------------------------+------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by carljm):
In theory, it would be possible for migrations to stop using app-label for
dependencies and start using full dotted paths instead? Maybe?
And then since db table names aren't hardcoded in migrations, maybe
migrations could adapt to the app being re-labeled? (If you did the re-
labeling before running any of its migrations; re-labeling midstream would
still require manual table renames.)
This would be a big change, but if we wanted to revive the idea of using
`AppConfig.label` for third-party apps, I think that would be the
necessary path.
Using full paths of course means that if the import path for an app
changes, you have to edit all its migrations. But maybe that's better,
since import path is definitely under the control of the app author,
always, unlike app label (since the advent of `AppConfig.label`).
If we don't make this change to migrations, it seems possible that there
are no really compelling use-cases remaining for `AppConfig.label`, just
bugs-in-waiting, and we should consider deprecating and removing it.
--
Ticket URL: <https://code.djangoproject.com/ticket/23790#comment:10>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.be47ee4cb81daeb04edac68005098740%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
