Opened 12 years ago
Closed 12 years ago
#20501 closed Bug (fixed)
A test for datetime queries with timezones fails under Oracle
| Reported by: | Shai Berger | Owned by: | Shai Berger |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Release blocker | Keywords: | oracle, timezone |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I think this is caused by the fix introduced in [dfe6ea3b1f6c7119a552ba6a] -- that fix was in the right direction, but didn't account for timezones.
Change History (2)
comment:1 by , 12 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Yes, you need to do like in django/db/backends/init.py.