#2626: Datetime handling is broken when dealing with more than one time zone
------------------------------------------------------+---------------------
Reporter: Tom Tobin <[EMAIL PROTECTED]> | Owner: nobody
Status: new | Milestone: post-1.0
Component: Core framework | Version:
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------------------------+---------------------
Comment (by korpios):
We've solved this at The Onion — and thanks to signals, we didn't even
have to hack up Django core (in this case, anyway).
The code is available in Bulbs, our catch-all open source library (which
is being actively used by us in production):
https://launchpad.net/bulbs
Django should still stop having the PostgreSQL backends use `TIMESTAMP
WITH TIME ZONE` and `SET TIME ZONE`; there should also be a note that
using more than one time zone in a single site will blow things up unless
you use a solution like `DateTimeZoneField` in Bulbs.
(I'm no longer following this ticket; if something's wrong with Bulbs,
please let us know by filing a !LaunchPad ticket.)
--
Ticket URL: <http://code.djangoproject.com/ticket/2626#comment:13>
Django <http://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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
