#24686: Support for Moving a model between two Django apps
-------------------------------+------------------------------------
Reporter: Alex Rothberg | Owner: Bhuvnesh
Type: New feature | Status: assigned
Component: Migrations | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by Maarten Nieber):
I've been struggling with this issue for a while, and came upon an
extremely simple (though not perfect) solution. Things seem to keep
working fine if I move the model code to a new django app, and set the
"app_label" field in the Meta class to point to the old django app.
I have two questions:
- is this totally fine to do, and expected to work?
- should we explain in the Docs that this is a simple and effective way to
move a model?
--
Ticket URL: <https://code.djangoproject.com/ticket/24686#comment:33>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018c77382296-82247ae5-e260-4cb3-96ca-e30da5c5eeb7-000000%40eu-central-1.amazonses.com.
