Django Timezone Configuration

Question

My django project is correctly enable the timezone in settings.

However, the datetime field of Django ORM object is a naive datetime object as shown in Block 3.

The expected result should be same as the output of Block 4 without any manually conversion.

In [1]: from django.conf import settings
   ...: settings.USE_TZ, settings.TIME_ZONE
Out[1]: (True, 'Asia/Hong_Kong')

In [2]: from qms.models import Quota

In [3]: q = Quota.objects.get(pk=1)
   ...: q.create_date, q.write_date
Out[3]:
(datetime.datetime(2021, 3, 10, 17, 37, 42, 489818),
 datetime.datetime(2021, 3, 10, 17, 37, 42, 489818))

In [4]: from django.utils import timezone
   ...: timezone.make_aware(q.create_date,timezone.utc), \
   ...: timezone.make_aware(q.write_date, timezone.utc)
Out[4]:
(datetime.datetime(2021, 3, 10, 17, 37, 42, 489818, tzinfo=<UTC>),
 datetime.datetime(2021, 3, 10, 17, 37, 42, 489818, tzinfo=<UTC>))

Record in SQL

Column	value
id	1
create_date	2021-03-10 17:37:42.489818+00
write_date	2021-03-10 17:37:42.489818+00
name	email

Django Model Definition

class Quota(models.models):
    name = models.CharField(max_length=255)
    create_date = models.DateTimeField(auto_now_add=True)
    write_date = models.DateTimeField(auto_now=True)

The PostgreSQL database schema and settings, Table "public.qms_quota"

Column	Type	Modifiers
id	integer	not null default nextval('qms_quota_id_seq'::regclass)
create_date	timestamp with time zone	not null
write_date	timestamp with time zone	not null
name	character varying(255)	not null

SHOW TIMEZONE;
 TimeZone
----------
 UTC

Questions

How can I get the timezone-aware datetime object directly without any conversion?
Or the manual conversion is expected ?

This is unusual behavior, so I'm assuming that your application or database has changed at some point? Can you replicate this with a fresh database? Also, please show the actual database values (not the Python objects) for your example (pk=1). — Kevin Christopher Henry
– Kevin Christopher Henry, Commented Mar 11, 2021 at 5:14

Ken Ho · Accepted Answer · 2021-03-11 12:58:37Z

2

The root-cause is a bug from a connection pool library django_postgrespool2==2.0.1.

When you use the your connection engine with "django_postgrespool2", it will NOT correctly handle the timezone settings. Releated Issue

TLDR: use engine `django.db.backends.postgresql`

edited Mar 11, 2021 at 12:58

answered Mar 11, 2021 at 12:52

Ken Ho

4802 gold badges5 silver badges18 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Iain Shelvington · Accepted Answer · 2021-03-11 04:47:05Z

0

You can use django.utils.timezone.localtime to convert the datetime received from the DB to localtime:

from django.utils.timezone import localtime
q = Quota.objects.get(pk=1)
print(localtime(q.create_date), localtime(q.write_date))

answered Mar 11, 2021 at 4:47

Iain Shelvington

32.5k3 gold badges36 silver badges55 bronze badges

1 Comment

Ken Ho Over a year ago

i want to get the aware datetime object without any conversion

Collectives™ on Stack Overflow

Django Timezone Configuration

2 Answers 2

TLDR: use engine `django.db.backends.postgresql`

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

TLDR: use engine django.db.backends.postgresql

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related

TLDR: use engine `django.db.backends.postgresql`