#23867: Remove hacks required by .dates() queries
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Database | Keywords:
layer (models, ORM) | Has patch: 0
Severity: Normal | Needs tests: 0
Triage Stage: Ready for | Easy pickings: 0
checkin |
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
The dates() queries implementation uses custom QuerySet, Query and
Compiler classes. Before expressions and database value converters were
added there were no other way to convert the database values than addition
of these subclasses to hack around the limitations in Django. But now with
expressions and converters support it is possible to implement the dates
queries by using public APIs only.
This is implemented in https://github.com/django/django/pull/3570.
As I don't think anybody wants to keep the old way around, and also I
think the patch is ready for merge, so I'll mark this directly as ready
for checkin.
--
Ticket URL: <https://code.djangoproject.com/ticket/23867>
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/051.327a9607168851883929dc86d575d08c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
