#24686: Support for Moving a model between two Django apps
-----------------------------+------------------------------------
Reporter: cancan101 | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* component: Uncategorized => Migrations
* needs_tests: => 0
* version: 1.8 => master
* needs_docs: => 1
* stage: Unreviewed => Accepted
Comment:
Not sure about feasibility of detecting/auto-generating, but if not, we
could certainly document the [http://stackoverflow.com/a/26472482/5112
SeparateDatabaseAndState solution] in docs/howto/writing-migrations.txt.
--
Ticket URL: <https://code.djangoproject.com/ticket/24686#comment:1>
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.25e0034daa878e11339a0f697660eb48%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
