#22288: F() expression not compatible with __range field look up
-------------------------------------+-------------------------------------
Reporter: liushaohua86@… | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by MatthewWilkes):
* needs_docs: => 0
* needs_tests: => 0
Comment:
I have had the same problem, albeit with date objects. I've begun working
on a patch, WIP is at
https://github.com/django/django/compare/master...MatthewWilkes:22288
-iterables-and-F-objects
Current state is 1 failing test on sqlite (not tested on other backend) so
certainly not ready for review at the moment. Posting here for visibility,
as I've spoken to many of the people involved on IRC.
While working on this I've started to think that checking for expected
parameter types in lookups being done by comparing their names is a bad
idea, given the work done on custom lookups. Perhaps it would make sense
for some of the value preparation to be offloaded onto the lookup, or at
least the parsing of value data structures, to allow for richer lookups to
use expressions too.
--
Ticket URL: <https://code.djangoproject.com/ticket/22288#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/080.144693b257b26b30dba4a8e935e18b47%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
