Greg Donald wrote: > On Tue, Aug 31, 2010 at 1:46 PM, Robert Walker <[email protected]> > wrote: >> I personally don't know why MySQL even bothers providing a TIME field >> type. >> >> Of course, as always, I could be missing some specific use case for it. > > Repeating events, "Tuesdays at 4:00pm" for example. > > PostgreSQL also provides a time field type where no date is stored.
As I said meaningless without applying the date part to it. If today is Saturday, and the event is scheduled at 4:00 p.m. Tuesday, what happens if the time changes to, or from, daylight savings time at 2:00 a.m. Sunday. The value "4:00 p.m." must be translated based on the specific date the Tuesday lands on. Might as well just store the time as a string at that point. The time has no value as a Time (object) (i.e it must be parsed based on the date anyway). -- Posted via http://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 [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.
