Is Django corrupting timezone-aware DateTimeField when saving it to the Database?

Question

I have a Django model as described here

I create and save an instance of this model:

>>> from django.db.models import Max, F, Func
>>&         


        

Answer 1

Yes. Some of the data is discarded.

Django DateTime field stored data in a database DateTime storage that lacks timezone information thus the information is removed before storage.

This is whet the manual says:

Note that if you set this to point to a DateTimeField, only the date portion of the > field will be considered. Besides, when USE_TZ is True, the check will be performed > in the current time zone at the time the object gets saved.

The proper way to store full datetime date would be to use a DateTimeOffset field - that can be found in MS-Sql and others. But this is not supported (yet?)