#28373: TIME_ZONE value in DATABASES settings is not used for date lookup
-------------------------------------+-------------------------------------
Reporter: Victor Talpaert | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution:
Keywords: settings ORM lookup | Triage Stage: Accepted
mysql timezone |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Can Sarıgöl):
* cc: Can Sarıgöl (added)
* needs_tests: 1 => 0
Comment:
hi, I have a PR to fix this part about another problem. added a commit to
include into it.
[https://github.com/django/django/pull/10910/commits/088cf0d6dec564db37d1d7754c469d1784e1740b
Commit]
--
Ticket URL: <https://code.djangoproject.com/ticket/28373#comment:6>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.f5bccd479c9baec0b15f5512216ed4c6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
