#23524: Allow to set TIME_ZONE option on databases that support time zones.
-------------------------------------+-------------------------------------
Reporter: Mactory | Owner: Aymeric
| Augustin
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for
| 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:"ad88524e4db91dc2f148cf40184a81a454ee7aac" ad88524]:
{{{
#!CommitTicketReference repository=""
revision="ad88524e4db91dc2f148cf40184a81a454ee7aac"
Refs #23524 -- Unified BaseDatabaseWrapper.timezone.
There was a special case in this property to return None when the
database backend supports time zone. However, only the PostgreSQL
backend supports time zones and it never uses this property.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23524#comment:8>
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/065.4559afef7c2c38b82f6a86ec49fe7443%40djangoproject.com.
