#24037: Migrating a legacy table results in data loss
-------------------------------------+-------------------------------------
Reporter: iambibhas | Owner: timgraham
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"51ea30a43bafad40b4a24ad0be346796a9c7ab6a"]:
{{{
#!CommitTicketReference repository=""
revision="51ea30a43bafad40b4a24ad0be346796a9c7ab6a"
[1.7.x] Fixed #24037 -- Prevented data loss possibility when changing
Meta.managed.
The migrations autodetector now issues AlterModelOptions operations for
Meta.managed changes instead of DeleteModel + CreateModel.
Thanks iambibhas for the report and Simon and Markus for review.
Backport of 061caa5b386681dc7bdef16918873043224a299c from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24037#comment:7>
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.00423352bd80f6f61c4396449cdbc144%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
