#24686: Support for Moving a model between two Django apps -------------------------------+------------------------------------ Reporter: Alex Rothberg | 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 Petr DlouhĂ˝): Maybe this could be separated into two separate tasks. We could first create database operation like `django.db.models.MoveToApp`. This alone could save a lot of manual work and confusion for developers. Second stage would be creating the autodetection mechanism, which would make migrations with this operation automatically. -- Ticket URL: <https://code.djangoproject.com/ticket/24686#comment:9> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/067.5615b05f84c1372064303236ac143ef9%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.