#31596: ForeignKey.validate() should validate using the base manager.
-------------------------------------+-------------------------------------
Reporter: Jon Dufresne | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: model form | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:8 Damian Nardelli]:
> Hello. The documentation for v2.2
(https://docs.djangoproject.com/en/2.2/topics/db/managers/#using-managers-
for-related-object-access) is stating that the base manager will be used
in that version too instead of the default manager. We just saw that this
fix has been released 12 days ago for v3.2.5, we were wondering when it'll
be released for v2.2? Thanks!
It is not a regression, per our backporting policy this means it doesn't
qualify for a backport to 2.2.x (see
[https://docs.djangoproject.com/en/stable/internals/release-process/
Django’s release process] for more details). Moreover Django 2.2 is in
extended support so it doesn't get bugfixes (except security issues)
anymore.
--
Ticket URL: <https://code.djangoproject.com/ticket/31596#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.26396cb819db8f816810dc8c32c277c3%40djangoproject.com.
