#22660: Dependencies between non-migrated and migrated apps break migration
-------------------------------+--------------------------------------
Reporter: yakky | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.7-beta-2
Severity: Normal | Keywords: migrations, dependencies
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
If models for `app_sec` depends on models from `app_main` (because of
foreign keys or parentship) and models in `app_main` have non trivial
dependencies between them, migrate cannot resolve bases or cannot load
models.
I've setup an example project https://github.com/yakky/migrations_poc to
clarify class relationships.
Transform `app_sec` in a migrated app or using `run_before` attribute on
`app_main` migrations may not be a viable solution: `app_sec` may not be
under developer control or can be unknown at the time of creating
migrations (e.g.: if `app_main` is a general available application and
`app_sec` is a random application reusing models from `app_main`).
Real world case here is django CMS
--
Ticket URL: <https://code.djangoproject.com/ticket/22660>
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/048.65195f83a3eec1a42fe9dd6a631ebf8c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
