#20012: test_year_lookup_edge_case fails under Oracle
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: shai
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution: fixed
Severity: Release blocker | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by Shai Berger <shai@…>):
* 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>
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.7b1e4d23d168dbc201ca74a85b277886%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
