#24037: Migrating a legacy table results in data loss
----------------------------+------------------------------------
Reporter: iambibhas | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Changes (by charettes):
* cc: charettes (added)
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
* type: Uncategorized => Bug
* stage: Unreviewed => Accepted
Comment:
Shouldn't the autodetector simply issue a `AlterModelOptions` to change
the model state from `managed=False` to `True` in this case? This would be
no-op at the database level.
--
Ticket URL: <https://code.djangoproject.com/ticket/24037#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.2bd75c57c7eeca7281103063ad132c96%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
