Greg Donald wrote: > On Tue, Aug 31, 2010 at 2:41 PM, Robert Walker <[email protected]> > wrote: >> You're still missing my point entirely. We're talking about representing >> a time with a Time object. It matters not whether you need to support >> multi-timezone or not. > > I agree, you brought it up. > >> AFAIK there is no Ruby object that represents >> time without date. > > It's called a Fixnum, works great.
Yep. I apologize for the misunderstanding. I knew we were arguing the same side of the issue. It just took me a few tries to get to the heart of the matter. Fixnum (INTEGER) is exactly what I typically use as well (i.e. an offset from midnight). reu wrote: > Rails automatically appends a dummy date when you use the TIME type on > your database. My point is: if you are using a time data type on your > database, you are doing that exactly because you don't want the date > included. My original intent was an effort to explain this question in original post. Rails is applying a "dummy date" because it must. However, that time representation is subject to interpretation. And that depends on what time zone Rails applies to that interpretation. -- 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.
