Thanks Robert & Colin, in the current case , server and users are in the same Time zone ( UTC+1) so server local time is user local time ( my UNIX box is UTC+1)
by today , I always mean user's today which is local time so as per your answer when I make a local time query, it's normal to have it 'converted' into utc for comparisons so => all events are created at user's local time , then stored in UTC if I need to query last week user's events, then my query should use local time ( system will convert the query times to UTC and compare with stored db UTC times) thanks again On Feb 7, 7:18 pm, Robert Walker <li...@ruby-forum.com> wrote: > Colin Law wrote in post #1044565: > > > On 7 February 2012 17:12, Erwin <yves_duf...@mac.com> wrote: > > It depends which you want. Times in the db should always be in UTC, > > so in the first case it is testing against the start of the day in > > local time, which is 23:00 UTC. In the second case it is testing > > against the start of the day UTC. So the decision is yours, if you > > want your scope to return events from today local time then use the > > former, if you want today UTC then use the later. It all depends on > > what you mean by 'today'. > > And, by "local time" he means "server's local time" not necessarily the > "local time" for the actual user. If you want to support the "user's > local time" then you'll need to know the time zone where the user > actually resides. Typically that's just something you'll have to ask > them when they create their account so you can store their local time > zone along with their account information. > > Ughhh! +1 for Stardates. > > -- > Posted viahttp://www.ruby-forum.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 rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
