#30638: Allow the per-database TIME_ZONE option on databases that support
timezones.
-------------------------------------+-------------------------------------
Reporter: Aymeric Augustin | Owner: Aymeric
| Augustin
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* stage: Unreviewed => Accepted
Comment:
I think it can be more tricky then it looks like to support connection
with a native timezone support and in the same time returns datetimes in
other timezone. We should avoid unnecessary conversions. It can also be
confusing for users.
Tentatively accepted, we can evaluate a patch. I understand that you're
going to submit it.
--
Ticket URL: <https://code.djangoproject.com/ticket/30638#comment:7>
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.0fd7ae241bc3648048b79d27c8d6f375%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
