From ee9fcb1672ddf5910ed8c45c37a00f32ebbe2bb1 Mon Sep 17 00:00:00 2001 From: Christopher Medrela Date: Fri, 7 Feb 2014 22:34:56 +0100 Subject: Fixed #17673 -- Forbid field shadowing. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Thanks Anssi Kääriäinen for the suggestion. --- docs/releases/1.7.txt | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs') diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt index b22890c301..bda84e847f 100644 --- a/docs/releases/1.7.txt +++ b/docs/releases/1.7.txt @@ -1068,6 +1068,12 @@ Miscellaneous which does allow primary keys with value 0. It only forbids *autoincrement* primary keys with value 0. +* Shadowing model fields defined in a parent model has been forbidden as this + creates amiguity in the expected model behavior. In addition, any clashing + fields in the model inheritance hierarchy results in a system check error. + For example, if you use multi-inheritance, you need to define custom primary + key fields on parent models, otherwise the default ``id`` fields will clash. + .. _deprecated-features-1.7: Features deprecated in 1.7 -- cgit v1.3