#17263: When time zone support is active, raise a warning when a naive datetime
reaches the database adapter
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: aaugustin
Type: | Status: new
Cleanup/optimization | Version:
Component: Database | Keywords:
layer (models, ORM) | Has patch: 0
Severity: Normal | Needs tests: 0
Triage Stage: Design | Easy pickings: 0
decision needed |
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
I haven't done it because I thought it would be too obnoxious -- for
instance, if you're using a third-party app that uses datetimes in a non-
trivial way and hasn't been upgraded yet.
But a good argument in favor of such a warning was made
[http://groups.google.com/group/django-developers/msg/682a41fd2c8da431 on
the mailing list], and it's easy to filter the warning out with one line
in your settings file if you don't care.
--
Ticket URL: <https://code.djangoproject.com/ticket/17263>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
