makemigrations reports "No changes detected" if a property exists with the same field name

[Jej]

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.

[Mariusz Felisiak]

I don't think there is much Django can do in such cases. It's an issue in your code.

[Jej]

Of course it's an issue in my code. But 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?

[Mariusz Felisiak]

Replying to 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.

[Jej]

Ok. Thanks for the explanation of the underlaying.