#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
-----------------------------+------------------------------------
Comment (by knbk):
An actual implementation would supersede #24016.
I don't think the operation to move a model to another app has to be
significantly more complex that the current `RenameModel`. The
autodetection, on first sight, is just a matter of removing this check:
https://github.com/django/django/blob/master/django/db/migrations/autodetector.py#L421
I do have some concerns about dependencies. If the migration lives in the
old app, the autodetector won't be able to detect that the next migration
in the new app depends on the `RenameModel` migration in the old app.
Likewise, if the migration lives in the new app, the next migration in the
old app won't have a dependency on the migration that moves the model. The
last case ''might'' not be a problem, but I can't say that off the top of
my head.
--
Ticket URL: <https://code.djangoproject.com/ticket/24686#comment:3>
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.1863688fbb2bb6b7ec84c3584120968f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
