#24686: Support for Moving a model between two Django apps
-------------------------------+--------------------
Reporter: cancan101 | Owner: nobody
Type: New feature | Status: new
Component: Uncategorized | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
An issue that I run into is that at some point one of my apps becomes so
large that I decide to split the application into a number of separate
logical units. Right now the Django migration system leaves me on my own
to write a correct migration to support updating the db to reflect the new
multi-app layout.
There is an [http://stackoverflow.com/questions/25648393/how-to-move-a
-model-between-two-django-apps-django-1-7 SO post] that attempts to
outline a solution but I would suggest trying to detect these model moves
and then auto-generating these migrations.
--
Ticket URL: <https://code.djangoproject.com/ticket/24686>
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/052.7e85adb16fbf7de6bcfe4babe374edcf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
