#35813: Makemigrations not properly tracking changes to unmanaged models
-------------------------------------+-------------------------------------
Reporter: Hanny G | Owner: Hanny G
Type: Bug | Status: assigned
Component: Migrations | Version: 5.1
Severity: Normal | Resolution:
Keywords: makemigrations, | Triage Stage: Accepted
unmanaged |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
The patch is in
[https://code.djangoproject.com/query?status=!closed&needs_better_patch=0&needs_tests=0&needs_docs=0&has_patch=1&stage=Accepted&desc=1&order=changetime
the review queue] so it will eventually be looked at. The upcoming release
of 5.2 has kept everyone busy which explains why no one had a chance to
look at your patch yet.
One thing that might be worth doing in the mean time is to add a release
note mentioning that `makemigrations` will now appropriately track any
change to managed models which might cause new changes to be detected on
upgrade.
--
Ticket URL: <https://code.djangoproject.com/ticket/35813#comment:8>
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 visit
https://groups.google.com/d/msgid/django-updates/01070193e46afe75-1650aa78-cba4-4712-a499-e4f866116162-000000%40eu-central-1.amazonses.com.
