[Django] #20012: test_year_lookup_edge_case fails under Oracle

5 views
Skip to first unread message

Django

unread,
Mar 10, 2013, 4:48:35 AM3/10/13
to django-...@googlegroups.com
#20012: test_year_lookup_edge_case fails under Oracle
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: Database | Version: master
layer (models, ORM) | Keywords:
Severity: Release | Has patch: 0
blocker | Needs tests: 0
Triage Stage: Accepted | Easy pickings: 0
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
http://ci.djangoproject.com/job/Django%20Oracle/lastCompletedBuild/database=oracle,python=python2.7/testReport/basic.tests/ModelTest/test_year_lookup_edge_case/

--
Ticket URL: <https://code.djangoproject.com/ticket/20012>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Mar 10, 2013, 6:22:30 AM3/10/13
to django-...@googlegroups.com
#20012: test_year_lookup_edge_case fails under Oracle
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
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 apollo13):

* cc: apollo13 (added)


--
Ticket URL: <https://code.djangoproject.com/ticket/20012#comment:1>

Django

unread,
Mar 10, 2013, 6:24:07 AM3/10/13
to django-...@googlegroups.com
#20012: test_year_lookup_edge_case fails under Oracle
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
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 |
-------------------------------------+-------------------------------------

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>

Django

unread,
May 4, 2013, 5:16:35 PM5/4/13
to django-...@googlegroups.com
#20012: test_year_lookup_edge_case fails under Oracle
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
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):

* cc: shai@… (added)


--
Ticket URL: <https://code.djangoproject.com/ticket/20012#comment:3>

Django

unread,
May 19, 2013, 11:54:36 AM5/19/13
to django-...@googlegroups.com
#20012: test_year_lookup_edge_case fails under Oracle
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: shai
Type: Bug | Status: assigned

Component: Database layer | Version: master
(models, ORM) | Resolution:
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):

* 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>

Django

unread,
May 21, 2013, 7:12:38 PM5/21/13
to django-...@googlegroups.com
#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>

Reply all
Reply to author
Forward
0 new messages