#23790: Possible bad interaction between migration dependencies and relabeling 
apps
----------------------------+------------------------------------
     Reporter:  aaugustin   |                    Owner:  nobody
         Type:  Bug         |                   Status:  new
    Component:  Migrations  |                  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):

 A third-party app with models changing its label has always meant changing
 the name of all its database tables, too (unless it uses `Meta.db_table`
 to preserve them). So it's always been the case that changing the label of
 an app with models is a Fairly Backwards Incompatible Thing To Do. I guess
 what's new in 1.7 is that a) changing app-label is easier than it used to
 be (no longer implies changing import path), and b) migrations introduce a
 new layer of label-dependence that isn't fixed by using a backwards-
 compatible `Meta.db_table`.

 I'm having trouble seeing a way to make this smoother, other than possibly
 improving the error message (though the current one isn't terrible) and
 probably adding a note to the docs in the `AppConfig` section clarifying
 that changing `app_label` midstream is a breaking change for any existing
 installs of that app. Fundamentally, migrations need some way to reliably
 and persistently reference an app, and that's always been the purpose of
 app-label.

--
Ticket URL: <https://code.djangoproject.com/ticket/23790#comment:7>
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.ac546b73718cbe72822ef7d76f19dcdd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to