#25569: Add a friendly error report when using select_related() on a reverse
relation
-------------------------------------+-------------------------------------
Reporter: Shai Berger | Owner: Vincent
| Perez
Type: New feature | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Shai Berger):
* status: assigned => closed
* resolution: => wontfix
Comment:
Hi Vincent,
Thanks for your efforts, and sorry for your time, but I agree with Tim:
This ticket would have been nice to add early in the 1.8 lifecycle, but
it's become much less valuable now. Most of the people who wanted to
upgrade from pre-1.8 have already done so. Your latest suggestion is
indeed simple, but IMO doesn't really add much value, and without the
"help upgrade to 1.8" motive, indeed sets a bad precedent for adding
unnecessary details to an error message.
--
Ticket URL: <https://code.djangoproject.com/ticket/25569#comment:19>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.845e59a9731f8e2e4cd52c04c6db4713%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
