Changes between Version 1 and Version 2 of Ticket #29900, comment 1


Ignore:
Timestamp:
Oct 28, 2018, 9:13:50 AM (6 years ago)
Author:
Simon Charette

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #29900, comment 1

    v1 v2  
    11I agree that it could be more intuitive to use `f'{field.name}_{field.target_field.name}'` as attribute name. However changing it at this point would break backward compatibility for a large number of projects and require a deprecation period.
    22
    3 Also in the cases where it's the referenced primary key that declares a different name the reference attribute name would be less obvious because of the implicit `to_field`. The problematic is even worse when the referenced model is declared in another app.
     3Also in the cases where it's the referenced primary key that declares a different name the reference attribute name would be less obvious because of the implicit `to_field`. The ambiguity is amplified when the referenced model is declared in another app.
    44
    55{{{#!python
Back to Top