#22023: .values() followed by defer() or only() results invalid data or crash
-------------------------------------+-------------------------------------
Reporter: jtiai | Owner: wiget
Type: Bug | Status: assigned
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: orm | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by loic84):
IMO "deferring" only makes sense if you get actual objects from which you
can fetch deferred fields. While `only()` could conceptually modify the
list of fields used by `values()` (but shouldn't since we made it the
antonym of `defer()`), the "deferring" concept and therefore `defer()` are
completely at odd with `values()`/`values_list()`.
I recommend raising `NotImplementedError` for both
`ValuesQuerySet.defer()` and `ValuesQuerySet.only()`.
--
Ticket URL: <https://code.djangoproject.com/ticket/22023#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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.82d14d6502145b64e39f8fdc31022b04%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
