#26296: values() after extra() gives incorrect error message
-------------------------------------+-------------------------------------
Reporter: vvkuznetsov | Owner:
Type: | vvkuznetsov
Cleanup/optimization | Status: assigned
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: db | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timgraham):
Note [https://docs.djangoproject.com/en/dev/ref/models/querysets/#extra
the documentation], "This is an old API that we aim to deprecate at some
point in the future. Use it only if you cannot express your query using
other queryset methods. If you do need to use it, please file a ticket
using the QuerySet.extra keyword with your use case (please check the list
of existing tickets first) so that we can enhance the QuerySet API to
allow removing extra(). We are no longer improving or fixing bugs for this
method."
In light of that, is it worth fixing this?
--
Ticket URL: <https://code.djangoproject.com/ticket/26296#comment:2>
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/069.d54ff979217d6f93aebdcaf6d719e0ee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
