Django datetimefield可识别时区的CET(Django datetimefield timezone aware CET)

 我看到这个帖子是Django在将它保存到数据库时会破坏时区感知的DateTimeField？ 但它特别使用pytz和mysql，以及不使用pytz和使用SQLite的地方（因为它可能会产生影响）。 
 
 我有以下模型 
 
class ScheduleItem(models.Model):
    work_date = models.DateTimeField('Work date')
 
 我插入数据如下： 
 
from isoweek import Week
from dateutil import parser
from django.utils import timezone

def foo()
    year = 2016 #hardcoded for example purpose
    wknr = 2 #hardcoded for example purpose
    dateObj = parser.parse(Week(year, wknr).day(0).isoformat() + " 00:00:00")
    print(dateObj) # 2016-01-11 00:00:00 as expected
    final = timezone.make_aware(dateObj)
    print(final) # 2016-01-11 00:00:00+01:00 as expected
    return final


workdate = foo()
si = ScheduleItem(work_date=workdate)
si.save()
 
 打印语句给我正确的输出，但是一旦我查看数据库（SQLite），我看到2016-01-10 23:00:00 
 
 我的Django设置说 
 
TIME_ZONE = 'CET'
USE_TZ = True
 
 检索我得到的数据： 
 
datetime.datetime(2016, 1, 10, 23, 0, tzinfo=<UTC>)
 
 为什么它以另一种格式存储数据，然后我指定，为什么如果Django设置为时区感知，我是否会收到UTC时区？ 我的意思是在插入日期时间对象前说： datetime.datetime(2016, 1, 11, 0, 0, tzinfo=<DstTzInfo 'CET' CET+1:00:00 STD>) 
 
 更新 - 
 
 同时，我通过在数据库中设置TIME_ZONE找到了一个解决方法，如此处的Django文档中所述。 这给了我数据库中正确的时区/日期，但根据该文档，我不需要它，因为我的数据库由Django管理 
 
 
 
 这允许与存储日期时间的第三方数据库在本地时间而不是UTC进行交互。 为避免出现DST更改的问题，您不应为由Django管理的数据库设置此选项。 
 
 
 我仍然不清楚为什么Django在将数据存储在数据库中时将具有CET时区的日期时间对象转换为UTC，但在检索时还不够智能以将其转换回CET。 

I saw this post Is Django corrupting timezone-aware DateTimeField when saving it to the Database? but it specifically uses pytz and mysql and what not where I don't use pytz and use SQLite (incase it might have an impact). 
 
I have the following model
 
class ScheduleItem(models.Model):
    work_date = models.DateTimeField('Work date')
 
And I insert data as follows:
 
from isoweek import Week
from dateutil import parser
from django.utils import timezone

def foo()
    year = 2016 #hardcoded for example purpose
    wknr = 2 #hardcoded for example purpose
    dateObj = parser.parse(Week(year, wknr).day(0).isoformat() + " 00:00:00")
    print(dateObj) # 2016-01-11 00:00:00 as expected
    final = timezone.make_aware(dateObj)
    print(final) # 2016-01-11 00:00:00+01:00 as expected
    return final


workdate = foo()
si = ScheduleItem(work_date=workdate)
si.save()
 
The print statements give me the right output, however once I look in the database (SQLite) I see 2016-01-10 23:00:00
 
My django settings say
 
TIME_ZONE = 'CET'
USE_TZ = True
 
Retrieving the data I get: 
 
datetime.datetime(2016, 1, 10, 23, 0, tzinfo=<UTC>)
 
Why is it storing the data in another format then I specify and why if Django is set to be timezone aware do I get a UTC timezone back? I mean before insertion the datetime object says: datetime.datetime(2016, 1, 11, 0, 0, tzinfo=<DstTzInfo 'CET' CET+1:00:00 STD>)
 
update - 
 
I found a work around in the meantime by setting TIME_ZONE on the database as described in the Django documentation here. This gives me the right timezone/date in the database, but according to that documentation I shouldn't need it because my DB is managed by Django
 
 
 
This allows interacting with third-party databases that store datetimes in local time rather than UTC. To avoid issues around DST changes, you shouldn’t set this option for databases managed by Django.
 
 
It is still unclear to me why Django does convert a datetime object with a CET timezone to UTC when storing it in the database, but isn't smart enough to convert it back to CET when retrieving. 

原文：https://stackoverflow.com/questions/35084164