#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 purpose of Django's makemigrations command is to identify changes in
managed models, or models in which Django has authority over the database
table structure.
I think you're mistaken here, the migration framework has always been
tracking changes to unmanaged models for two reasons
1. Support managed models referencing un-managed ones
2. Support data migrations involving un-managed models
The report here relates to 2. which I think it reasonable to assume that
if the framework tracks additions and removal it should also alterations.
--
Ticket URL: <https://code.djangoproject.com/ticket/35813#comment:6>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701926c5745c3-ef9fd959-82a9-4334-8b15-eedb87163ce5-000000%40eu-central-1.amazonses.com.
