Code

Changes between Initial Version and Version 1 of Ticket #17831


Ignore:
Timestamp:
03/04/12 21:01:13 (2 years ago)
Author:
julien
Comment:

I haven't been able to review this fully but this seems like a potential release blocker.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #17831

    • Property Patch needs improvement unset
    • Property Severity changed from Normal to Release blocker
    • Property Needs tests unset
    • Property Needs documentation unset
  • Ticket #17831 – Description

    initial v1  
    11This may be applicable to other backends, but I'm not sure. 
    22 
    3 When using USE_TZ the backend connection is set to use UTC.  So __year/__month/__day lookup filters will filter where the UTC timestamp has a year/month/day of the lookup value.  However, what's really desired is to use the timestamp at the current timezone.  For example, the current code when filtering for "today" datetimes which are not in UTC can potentially return a list of matching records where the set of days being displayed is more than one. 
     3When using USE_TZ the backend connection is set to use UTC.  So `__year`/`__month`/`__day` lookup filters will filter where the UTC timestamp has a year/month/day of the lookup value.  However, what's really desired is to use the timestamp at the current timezone.  For example, the current code when filtering for "today" datetimes which are not in UTC can potentially return a list of matching records where the set of days being displayed is more than one.