#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 timo):
I have to agree with @akaariai -- I don't understand what the use case for
using `values()` along with `only()` and `defer()` would be? The
[https://github.com/django/django/pull/2303 proposal] of having `only()`
override the fields in `values()` seems confusing. I would expect any
fields not already selected by `values()` not to be available later in the
`QuerySet`.
--
Ticket URL: <https://code.djangoproject.com/ticket/22023#comment:8>
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.f596df32e6490d79d763c6f15736de97%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
