#32731: makemigrations reports "No changes detected" if a property exists with
the
same name
-----------------------------------------+--------------------------
Reporter: jej | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 3.2
Severity: Normal | Keywords: annoying
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+--------------------------
I turned around few time trying to add a new field in my model (FK).
makemigrations reported "No changes detected". I dropped the database and
after migrations files cleanup, the field was still not created. The
reason was I had a @property method with the same name in the model.
Logically I wanted to replace this calculated field by a db field, but
didn't think about to check it was here already as a property.
I would prefer that django report the problem when two properties are
conflicting or may conflict in case the field is created.
--
Ticket URL: <https://code.djangoproject.com/ticket/32731>
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/046.775bd1f3ecedaf67ef3a37d7c8031a57%40djangoproject.com.
