#24837: Unable to query DateField using DateRange
----------------------------------+------------------------------------
Reporter: schinckel | Owner:
Type: New feature | Status: new
Component: contrib.postgres | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by mjtamlyn):
I've made some progress, see
https://github.com/django/django/compare/master...mjtamlyn:query-with-
ranges
There is no operator for `not_contained_by` in postgres so I removed that
pseudocode from schinckel's branch.
The code passes the tests but needs some serious tidying up to cover non-
simple use cases (F objects, complex expressions with output types etc).
Sadly a lot of explicit typecasting is required to make postgres not freak
out. As a result, I think we likely should just support "matching"
operations. For example this means big integer in a big integer range,
datetime in a datetime range not a date range.
--
Ticket URL: <https://code.djangoproject.com/ticket/24837#comment:4>
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/067.85c24b2dc1c07acf10fde95b863155e2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
