#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 -------------------------------------+------------------------------------- Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: new => closed * resolution: => fixed Comment: In [changeset:"cef3f2d3c64055c9fc1757fd61dba24b557a2add" cef3f2d3]: {{{ #!CommitTicketReference repository="" revision="cef3f2d3c64055c9fc1757fd61dba24b557a2add" Fixed #28373 -- Used connection timezone instead of UTC when making dates timezone-aware on MySQL, SQLite, and Oracle. Thanks vtalpaert for the initial patch. Co-Authored-By: Mariusz Felisiak <felisiak.mari...@gmail.com> }}} -- Ticket URL: <https://code.djangoproject.com/ticket/28373#comment:10> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/067.09fc6009a37c226d89d61acdbaa0b9e2%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.