Opened 10 years ago
Last modified 9 years ago
#23790 new Bug
Possible bad interaction between migration dependencies and relabeling apps — at Initial Version
| Reported by: | Aymeric Augustin | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.7 |
| Severity: | Normal | Keywords: | |
| Cc: | info+coding@… | Triage Stage: | Accepted |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
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.)
Note:
See TracTickets
for help on using tickets.