I'm not sure if you meant UTC instead of UAT. While UTC is at offset 0 it is still a TZ. So I can simply reproduce this issue by running my server on one machine with TZ set to anything you want. Then run the app from another machine and pull up the page shows the date. Now, change the client TZ to (GMT-12:00) International Date Line West and refresh the page. Then change the client TZ to (GMT+13:00) Nuku'alofa and what the date change.
So is there a Flex Date object that only stores the date like java.sql.Date does? I've seen solutions like http://flexblog.faratasystems.com/?p=289 which is not really what we want as we are just fooling the app and having to code each date field to store what comes from the db and manually convert each time you access the date. I really don't want to have to go to sending Strings back/forth and converting manually but our system is bound by law on dates and this is a serious problem for us. Thanks, Dale From: Dale Bronk [mailto:[email protected]] Sent: Friday, August 07, 2009 12:56 PM To: [email protected] Subject: RE: [AFFUG Discuss] Dates We have made sure that the date is in the db correctly. We use java.sql.Date which "does not hold time". It really does hold time and makes all entries set to midnight (00:00:00). Problem is that when the client TZ is different than the server. The Date in flex holds time. So when the date is coming from the server in Pacific TZ of 2/5/1985 00:00:00 and comes down the line and Granite DS goes through all the serialization when it comes out it is converting to the clients TZ and making the date 2/4/1985. But from the responses I'm hearing no one else is having issues using AMF getting dates from the server from one TZ into a client with another TZ. What makes it more complex when we save a java.sql.Timestamp we want this to happen. When the user in CA schedules a meeting for tomorrow at noon, we want the user in GA to see tomorrow at 9am. It is when we are storing java.sql.Date which does not use time we want the date to be the date. Dale From: [email protected] [mailto:[email protected]] On Behalf Of Tom McNeer Sent: Friday, August 07, 2009 12:34 PM To: [email protected] Subject: Re: [AFFUG Discuss] Dates Dale, If the date/time was recorded correctly in the database, it's coming back out the same way (unless something terminally weird is going on). Whatever is showing a different date to the GA customer is something affected by his local machine, of course. So I guess the question is, what are you doing inside Flex with the date? Have you confirmed that it is going across the wire to Flex with the correct date? Unless you are somehow manipulating the date once it's in the Flex app, there's no reason it would change. Maybe a little code would help? (BTW, David's suggestion about using Universal time in databases is good practice in many cases. But a DOB is a DOB. It's not really a timestamp - except in the strict, datatype sense - so time zones shouldn't be applied to it - anywhere.) -- Thanks, Tom Tom McNeer MediumCool http://www.mediumcool.com 1735 Johnson Road NE Atlanta, GA 30306 404.589.0560 ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
