Changes between Version 2 and Version 3 of Ticket #29900, comment 1
- Timestamp:
- Oct 28, 2018, 9:14:08 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #29900, comment 1
v2 v3 1 1 I 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. 2 2 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 ambiguity is amplified when the referenced model is declared in an other app.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 ambiguity is amplified when the referenced model is declared in an other app. 4 4 5 5 {{{#!python