#32513: SQLite3 Backend Falsly claims SQLite does not support Timezone aware
DateTimes
-------------------------------------+-------------------------------------
Reporter: Arthur Moore | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: datetime, timezone | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Arthur Moore):
> This is how Django is intended to be used and I think that's what you
should be doing.
How? Current that does not appear to be possible. The code referenced
either explicitly strips the timestamp if "USE_TZ=True" or it raises a
ValueError, which is this Bug. I could go with a custom field that
bypasses `adapt_datetimefield_value`, but that seems overkill for simply
trying to store a timezone.
Regardless, this bug exists because the ValueError does not reflect the
reality of how this database connection works in practice.
--
Ticket URL: <https://code.djangoproject.com/ticket/32513#comment:5>
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/071.22076e9639e9515ad09e8ee467365fc2%40djangoproject.com.
