On 10/24/07, SmileyChris <[EMAIL PROTECTED]> wrote:
>
> > Is there a way to get the
> > auto_now/auto_now_add feature of DateTimeField to use UTC?
>
> Those methods suck and hopefully will be removed. Use a callable
> default instead of auto_now_add (or overridden save instead of
> auto_now, like
> Is there a way to get the
> auto_now/auto_now_add feature of DateTimeField to use UTC?
Those methods suck and hopefully will be removed. Use a callable
default instead of auto_now_add (or overridden save instead of
auto_now, like Jarek gave):
from datetime import datetime
class YourModel(model
Joe Holloway napisaĆ(a):
> I'm looking to store UTC date/times so I don't have to worry about
> time zones until I localize the display. From looking at the code in
> DateTimeField I think I've answered my own question, but I just want
> to ask here for the sake of conversation. Is there a way to
http://www.cnd-industry.com/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EM
I'm looking to store UTC date/times so I don't have to worry about
time zones until I localize the display. From looking at the code in
DateTimeField I think I've answered my own question, but I just want
to ask here for the sake of conversation. Is there a way to get the
auto_now/auto_now_add fe
5 matches
Mail list logo