#28373: TIME_ZONE value in DATABASES settings is not used when making dates
timezone-aware on MySQL, SQLite, and Oracle.
-------------------------------------+-------------------------------------
Reporter: Victor Talpaert | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: settings ORM lookup | Triage Stage: Ready for
mysql timezone | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"88637064b3118f90ae5a402e1b47a243ef88d656" 88637064]:
{{{
#!CommitTicketReference repository=""
revision="88637064b3118f90ae5a402e1b47a243ef88d656"
Refs #28373 -- Stopped setting tzinfo in typecast_timestamp().
Unnecessary since cef3f2d3c64055c9fc1757fd61dba24b557a2add. When
USE_TZ=True, conn_tznames is always passed to methods that use
typecast_timestamp(). Therefore, it can return naive datetimes.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28373#comment:11>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.bd354270f7fb137e48f9315e30d086dd%40djangoproject.com.
