From: "Fischer Krisztián" <fischer@...>
Date: 2007-07-18T08:30:12+09:00
Subject: Re: Time range min/max inconsistency

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Brett Simmers wrote:
>> => Tue Jul 17 14:00:00 +0200 2007
> I don't know if this is related to your problem, but whenever I use
> Marshal.load to load a marshaled Time object, it's always created in the
> local timezone, regardless of what zone the saved object was in.  This
> is similar behavior, although I'm pretty sure Ranges don't use Marshal,
> and it's weird that it's just the max.

Thanks for the answer.

Seems to me like timezone is the black sheep in ruby. Today I ran into
the problem described above, and shortly after this into an other one.

If you store a UTC time in mysql via rails' ActiveRecord and read it
back, the local timezone is added to the time, which is pretty strange.

I could fix the problem with a small hack, however as a ruby newbie it
took me a day to figure this out. :)

Thanks,
Chris

- --
Fischer Kriszti�n
Borganization Kft.
Tel: (+36) 70/384-383-5
Tel: (+36) 1/3360547
email: fischer@borganization.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGnVEA6VUohGTtAQYRAjR8AJ0UbIKu37o/ikmuqzsSWKmgAk11+gCeKl8H
08K2vUyDVr1giGzH+Tb88sc=
=RX1m
-----END PGP SIGNATURE-----