#25944: Allow to tunnel migration to specific app
-----------------------------+--------------------
Reporter: RamezIssac | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------
Use case:
A third party app allow for "dynamic model loading" (where you can specify
one of its base model via something like `THIRD_PARTY_BASE_MODEL =
'myapp.CustomBase' ` in settings.py)
Then, when running `makemigrations` the migration file goes to the 3rd
party migrations folder (probably in the virtualenv) and unless manual
care taken to copy the migration file to the main app, renaming etc. , it
will lead to a complicated situation.
--
Ticket URL: <https://code.djangoproject.com/ticket/25944>
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/053.bb0f0fd9c24d88a1af2d49339a133f6e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
