John Siracusa wrote: > "The time zone of the DateTime object that results from a successful parse > is set to the value of the time_zone option, if defined. Otherwise, it is > set to the server_time_zone value of the object's db attribute using > DateTime's set_time_zone method."
Nice feature. > In the absence of any explicit action (e.g., a setting a server_time_zone() > on your db objects) DateTime objects will "pass through" RDBO as-is. That > simplifies things significantly. IME, it's best to store all dates in the > db in a single time zone and then convert to the user's time zone when > displaying the dates. Agreed, but that usually means you should specify a time zone for DateTime objects. Otherwise, you can get into a lot of trouble using the floating time zone if you try to do any comparisons with epoch times or MySQL TIMESTAMP columns. - Perrin ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
