#30638: Allow the per-database TIME_ZONE option on databases that support
timezones.
-------------------------------------+-------------------------------------
Reporter: Aymeric Augustin | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Aymeric Augustin):
* status: closed => new
* resolution: duplicate =>
Comment:
#23524 is about changing the timezone of the database connection i.e. at
the level of the PostgreSQL server for `timestamp with time zone` fields
generated by Django.
This ticket is about adding time zone information at the level of Django
for `timestamp` fields generated by third-party software — Django doesn't
generate such fields when USE_TZ = True.
--
Ticket URL: <https://code.djangoproject.com/ticket/30638#comment:2>
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.fa35f37ee3ece16c31a0b98b1a6c9027%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
