#26183: PostgreSQL backend: TimeField is created without time zone
-------------------------------------+-------------------------------------
Reporter: schtibe | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: postgres, timezone, | Triage Stage:
time field | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: new => closed
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
* resolution: => wontfix
Comment:
This is by design
[https://docs.djangoproject.com/en/dev/topics/i18n/timezones/#naive-and-
aware-datetime-objects as documented]:
Python’s `datetime.time` objects also feature a `tzinfo` attribute, and
PostgreSQL has a matching `time with time zone type`. However, as
PostgreSQL’s docs put it, this type “exhibits properties which lead to
questionable usefulness”.
[[BR]]
Django only supports naive time objects and will raise an exception if
you attempt to save an aware time object, as a timezone for a time with no
associated date does not make sense.
--
Ticket URL: <https://code.djangoproject.com/ticket/26183#comment:1>
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/065.6d0b4dd01bc109a081c22f74684eba52%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
