Re: timestamp weirdness with WO and FrontBase
Re: timestamp weirdness with WO and FrontBase
- Subject: Re: timestamp weirdness with WO and FrontBase
- From: Ray Kiddy <email@hidden>
- Date: Thu, 31 Jan 2008 17:47:36 -0800
On Jan 31, 2008, at 3:36 PM, Kevin Windham wrote:
I have an app that stores a start date for an event. When entering
a date in the web app it appears fine. In the DB it shows up as a
day earlier because it looks like the timestamp in the db is offset
backwards by several hours.
Is this related to timezone, or frontbase, or something else? I
don't really want to have the data modified since the date and time
are specific to a locale already. It just confuses things to have
any kind of timezone or offset applied.
The reason I even bring this up is that it seems for some reason
across restarts the dates in the web app get the actual db date and
not what was originally entered into on the html form.
TIA,
Kevin
This question has come up before, many times, and is usually
accompanied by much gnashing of teeth. There is a long answer.
Perhaps we will not have to hear it again.
The short answer is that you should probably store your time data in
GMT form. The question of how the time looks to the UI is really a UI-
level issue and if each session has a default time zone, and the user
can set the default time zone, and the time zone is only used to come
up with the display form of the data, things will work better.
I do not think the issue is FrontBase. It sounds as though you are
saving the time data as GMT and reading it in and interpreting it as
being in your local time zone, or vice versa.
There are past threads you can read on this issue. Good luck.
- ray
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden