Opened 8 years ago
Closed 8 years ago
#26903 closed Bug (fixed)
support date and timestamp containment within postgres range field
Reported by: | Aron Podrigal | Owned by: | Mariusz Felisiak |
---|---|---|---|
Component: | contrib.postgres | Version: | dev |
Severity: | Normal | Keywords: | rangefield |
Cc: | felisiak.mariusz@… | Triage Stage: | Accepted |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
currently trying to do a lookup
MyModel.objects.filter(datetime_range__contains=timezone.now())
results in incorrect SQL.
Pull request at https://github.com/django/django/pull/6885
Change History (7)
comment:1 by , 8 years ago
Triage Stage: | Unreviewed → Accepted |
---|---|
Version: | 1.9 → master |
comment:2 by , 8 years ago
Patch needs improvement: | set |
---|
comment:3 by , 8 years ago
Patch needs improvement: | unset |
---|
comment:4 by , 8 years ago
Patch needs improvement: | set |
---|
comment:6 by , 8 years ago
Patch needs improvement: | unset |
---|
Note:
See TracTickets
for help on using tickets.
Simon suggests adding tests with timezone aware values.