On Tue, Aug 31, 2010 at 2:30 PM, Robert Walker <[email protected]> wrote: > My point being again that any interpretation of whatever gets stored as > a time only, must be translated into a Time or DateTime object based on > a specific date, in a specific locale. That's really all I'm saying. > 4:00 p.m. from your locale may mean 7:30 p.m. in my locale. It's > dependent on geopolitical rules.
Lots of web apps, certainly dozens I've built, are just for a single company, with a single office, in a single time zone. That's great that you build apps where time zone does matter, and that you build apps for companies where time zone does matter, but it doesn't make the time (without date) field any less useful to me. -- Greg Donald destiney.com | gregdonald.com -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
