On Wed, Aug 25, 2010 at 5:13 PM, Johan Ekblad <jka@ekblad.org> wrote:
2010-08-25 16:57, Tom Van Braeckel skrev:
> Dear list,
> I'm going to Turkey in a few days, which is in a different timezone, and
> I noticed that we currently don't keep track of timezone information in
> the database, since MySQL does not allow this.
> Has there been some thought on how we should handle this ?
> The best way (I think) is to always store DATETIME's in the GMT
> timezone, and then convert them to the user's timezone when outputting
> the DATETIME for viewing.
> Any thoughts on this ?

logMany.php receives the time in ISO 8601 format, for example:

The easiest way is if you can retrieve your current timezone and adjust
the "+01:00" in the example above to the right thing. (For example if
your timezone is "GMT+05" adjust to "+05:00" before sending to server.

Another way is to look up the timezone (a rest api) from your current
location (lat,lng). Normally you only need to do this when you start
logging (once). You can use for example this api:


(as I'm using in trunk/server/keyInfo.php)

Thanks, but that's not what I meant.
Knowing the timezone in Java is not problem (I use Calendar.getInstance().get(Calendar.TIMEZONE_OFFSET).

The problem is that our database does not keep track of the time zone (in the "time" column of PositionLog) so I proposed always converting the time to GMT+00:00 time before storing it. Maybe this convention has been followed before, but I wasn't sure so if you approve, I will always convert the (local) time to GMT+00:00 before storing in in the database...


  //regards: Johan

Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
Opengeotracker-devel mailing list