#24612: Confusing error message when using only/defer through deleted related
field
-------------------------------------+-------------------------------------
Reporter: Richard Eames | Owner: Eduardo
Type: | Status: assigned
Cleanup/optimization |
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
It's difficult to say if a deleted reverse relation is the only way to hit
an error there. Something along the lines of `"Cannot resolve keyword %r
into field. Choices are: %s"` might be more generic. Is there any other
validation for only/deferred fields? Might be interesting to see if this
case could be covered there.
--
Ticket URL: <https://code.djangoproject.com/ticket/24612#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 [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/066.0b5ddec1a95e811a9b1be37c508c1461%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
