#26903: support date and timestamp containment within postgres range field
----------------------------------+------------------------------------
Reporter: Aron Podrigal | Owner: felixxm
Type: Bug | Status: closed
Component: contrib.postgres | Version: master
Severity: Normal | Resolution: fixed
Keywords: rangefield | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"6b048b364ca1e0e56a0d3815bf2be33ac9998355" 6b048b36]:
{{{
#!CommitTicketReference repository=""
revision="6b048b364ca1e0e56a0d3815bf2be33ac9998355"
Fixed #26903 -- Fixed __contains lookup for Date/DateTimeRangeField.
Thanks Mariusz Felisiak and Tim Graham for polishing the patch.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26903#comment:7>
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/062.e1f34ecd037e326a5b3c3dc8b85e8c93%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
