Opened 4 years ago

Closed 4 years ago

#31948 closed New feature (fixed)

Add support for tzinfo parameter to TruncDate() and TruncTime().

Reported by: Joe Jackson Owned by: Joe Jackson
Component: Database layer (models, ORM) Version: dev
Severity: Normal Keywords:
Cc: Aymeric Augustin, Josh Smeaton Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Joe Jackson)


TruncDate inherits from TruncBase, which includes the TimeZone mixin. This should allow a developer to pass in a tzinfo object to be used when converting TruncDate, but it actually uses the return value from get_current_timezone_name() unconditionally and completely discards the passed in timezone info object. The result is that attempting to aggregate by date doesn't work for timezones other than the global django.utils.timezone. For example I can't have the django app be in UTC and pass the "America/New_York" timezone in.

Here's the offending line:
Note, that a similar issue is happening in TruncTime.

Here's the method I would expect it to use:


class TimeSlots(models.Model):
  start_at = models.DateTimeField()

tz = pytz.timezone("America/New_York")
report = (
  TimeSlots.objects.annotate(start_date=TruncDate("start_at", tzinfo=tz))
  .values("start_date", "timeslot_count")

I would expect this to work, but currently the results are wrong for any timezone other than the one returned by django.utils.timezone.


There was a workaround for me. I was able to use TruncDay and then convert the DateTimes returned outside of the database, but I found no way to convert from DateTime to Date in the database. Maybe a Cast would work, but I would expect TruncDate to work.



Change History (8)

comment:1 by Serhii Romanov, 4 years ago

Please check
Is it related to your issue?

in reply to:  1 comment:2 by Joe Jackson, 4 years ago

Replying to Serhii Romanov:

Please check
Is it related to your issue?

It is related, but not exactly my issue. That patch updates the TruncBase as_sql method, and world work. But the TruncDate and TruncTime classes override as_sql and don't call super. So the timezone passed in is ignored.

I can attempt to submit a patch for this issue. I'll just need to take a minute and read up on how to properly do that.

comment:3 by Joe Jackson, 4 years ago

Description: modified (diff)

comment:4 by Mariusz Felisiak, 4 years ago

Cc: Aymeric Augustin Josh Smeaton added
Keywords: TruncDate removed
Summary: TruncDate Unexpected BehaviorAdd support for tzinfo parameter to TruncDate() and TruncTime().
Triage Stage: UnreviewedAccepted
Type: BugNew feature
Version: 3.1master

tzinfo is not a documented (or tested) parameter of TruncDate() or TruncTime() so it's not a bug but request for a new feature.

It sounds reasonable to support tzinfo in TruncDate() and TruncTime(), and I cannot find any argument against it in the original PR (maybe Josh will remember sth).

comment:5 by Josh Smeaton, 4 years ago

There was no explicit reason to ignore any passed in tz parameter - it was just a reimplementation of the existing method:

Trunc documents the use of tzinfo: and it should reasonably apply to all subclasses of Trunc as well.

I think accept as a bug is the correct decision here.

comment:6 by Joe Jackson, 4 years ago

Owner: changed from nobody to Joe Jackson
Status: newassigned

comment:7 by Joe Jackson, 4 years ago

Description: modified (diff)
Has patch: set

comment:8 by Mariusz Felisiak <felisiak.mariusz@…>, 4 years ago

Resolution: fixed
Status: assignedclosed

In 9d5d865f:

Fixed #31948 -- Added tzinfo parameter to TruncDate() and TruncTime().

Note: See TracTickets for help on using tickets.
Back to Top