Sorry for the delay in response - was on vacation for a few days.
After reading up more on naive and aware timezones in python, this all
makes more sense now. Thanks for your pointers, they were helpful.
Margie
On Sep 4, 9:03 am, Brian Neal wrote:
> On Sep 4, 10:47 am,
Tracy,
Sorry for the delay, just got back from a short vacation. Thanks very
much for your clarification. I think I now understand how to proceed!
On Sep 7, 8:06 pm, Tracy Reed wrote:
> On Thu, Sep 03, 2009 at 03:48:14PM -0700, Margie spake thusly:
>
> > What is the
On Thu, Sep 03, 2009 at 03:48:14PM -0700, Margie spake thusly:
> What is the default when using a django DateTimeField? Does it not
> save it in UTC? If it is not saving it in UTC, what is it saving it
> in?
Python has two kinds of DateTime objects: naive and
non-naive. Non-naive has timezone
On Sep 4, 10:47 am, Margie wrote:
>
> Can someone clarify what format dates and times are stored in when
> using just a standard DateTimeField? Is my timezone encoded in the
> database or is some generic, non-timezone-specific date/time stored?
There is no timezone
I am using mysql.
Can someone clarify what format dates and times are stored in when
using just a standard DateTimeField? Is my timezone encoded in the
database or is some generic, non-timezone-specific date/time stored?
I don't understand why I would want to save my timezone along with my
On Thu, Sep 3, 2009 at 11:36 PM, Margie
Roginski wrote:
>
> I've created a django app and I soon am going to have users that are
> in multiple timezones. My app is a task management system and it is
> important for users to see dates and times with respect to their own
Thanks for the input. I have a couple questions. Both of you talk
about saving the date/time in UTC format. What is the default when
using a django DateTimeField? Does it not save it in UTC? If it is not
saving it in UTC, what is it saving it in? I thought that one of the
things the
> I've created a django app and I soon am going to have users that are
> in multiple timezones. My app is a task management system and it is
> important for users to see dates and times with respect to their own
> time zone. IE, if here in California I create a task at 3PM on Sept
> 3, I want
On Thu, Sep 03, 2009 at 02:36:21PM -0700, Margie Roginski spake thusly:
> the task creation date, they should see 3PM on Sept 3. Is there a
> "best" way to handle this? Things that come to mind are:
I am going to have to be dealing with this soon also. My plan is to
store datetime objects in
I've created a django app and I soon am going to have users that are
in multiple timezones. My app is a task management system and it is
important for users to see dates and times with respect to their own
time zone. IE, if here in California I create a task at 3PM on Sept
3, I want someone in
10 matches
Mail list logo