Context Navigation

Changes between Version 1 and Version 2 of Ticket #34699, comment 17

v1	v2
1	1	Without a proper notion of typing / distinct types for Django naive vs aware datetime fields it is quite hard to make the experience better here. The way things are currently designed `DateTimeField` is expected to be naive if `USE_TZ = False` and aware otherwise, there's no way to represent naive `DateTimeField` at the ORM level when `USE_TZ = True`.
2	2
3		Even on Postgres which has distinct types for naive and aware timestamps (`timestamp` and `timestamptz`) there's no warning emitted when mixing both; [https://dbfiddle.uk/xyLSKpNO it simply defaults to the globally configured timezone] ~~like it's the case~~ on Python
	3	Even on Postgres which has distinct types for naive and aware timestamps (`timestamp` and `timestamptz`) there's no warning emitted when mixing both; [https://dbfiddle.uk/xyLSKpNO it simply defaults to the globally configured timezone] as opposed to how it's implemented on Python
4	4
5	5	{{{#!python