#32731: makemigrations reports "No changes detected" if a property exists with
the
same field name
-------------------------------+--------------------------------------
Reporter: Jej | Owner: nobody
Type: Uncategorized | Status: closed
Component: Migrations | Version: 3.2
Severity: Normal | Resolution: invalid
Keywords: annoying | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:2 Jej]:
> Django warn about a lot of issues in user code. Why not this one and
just silently does nothing? Why a field in the model would be ignored
without notice?
Because you override it in your own code, so it's not a model field
anymore. I'm happy to review a patch if you know how to check easily that
a property overrides a model field in the same class.
--
Ticket URL: <https://code.djangoproject.com/ticket/32731#comment:4>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/061.f714e57dfe8365b6af6427f63eadb00d%40djangoproject.com.
