diff options
| author | Julien Hartmann <julien@etherdream.org> | 2016-06-23 17:10:52 +0700 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-07-11 13:30:44 -0400 |
| commit | f4afb85d7e900123fa8f88110adc011ab184e153 (patch) | |
| tree | c917ef85c486c4f399ea1076178b7034eb7fcbb5 /docs | |
| parent | 418658f453bed7fe7949dda26651aab370003e6a (diff) | |
Fixed #26749 -- Preserved behavior of use_for_related_field during deprecation.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/releases/1.10.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/releases/1.10.txt b/docs/releases/1.10.txt index c56ac6efc6..b7b2813b31 100644 --- a/docs/releases/1.10.txt +++ b/docs/releases/1.10.txt @@ -1091,6 +1091,12 @@ class to override the manager from the concrete model, or you'll set the model's ``Meta.manager_inheritance_from_future=True`` option to opt-in to the new inheritance behavior. +During the deprecation period, ``use_for_related_fields`` will be honored and +raise a warning, even if a ``base_manager_name`` is set. This allows +third-party code to preserve legacy behavior while transitioning to the new +API. The warning can be silenced by setting +``silence_use_for_related_fields_deprecation=True`` on the manager. + Miscellaneous ------------- |