--
Ticket URL: <https://code.djangoproject.com/ticket/20012>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* cc: apollo13 (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/20012#comment:1>
Comment (by apollo13):
#20011 seems to be similar, namely it appears as if the "BETWEEN
'1.1.2009' and '31.12.2009 23:59:59.99999'" seems to produce wrong results
for the right interval boundary.
--
Ticket URL: <https://code.djangoproject.com/ticket/20012#comment:2>
* cc: shai@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/20012#comment:3>
* status: new => assigned
* owner: nobody => shai
Comment:
The problem is that with Oracle, `datetime(2009,12,31,23,59,59,999999)` is
received without the second-fraction part, whereas `'2009-12-31
23:59:59.999999'` is received with the fraction. The backend uses the
latter for saving (as it should), but the former for the edge of the year
range. I will commit the fix later tonight.
--
Ticket URL: <https://code.djangoproject.com/ticket/20012#comment:4>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"dfe6ea3b1f6c7119a552ba6a018f89745e767132"]:
{{{
#!CommitTicketReference repository=""
revision="dfe6ea3b1f6c7119a552ba6a018f89745e767132"
Fixed #20012 -- test_year_lookup_edge_case fails under Oracle
Used formatted date instead of datetime object for the end of the
year range, as the datetime object loses fractions-of-seconds when
inserted into the db.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/20012#comment:5>