voidstar wrote in post #950126: > Hey, > Thanks for the reply, I could easily write some code to discard the > time field, which is what I'll probably do now
You don't have to discard anything. Just ignore it. Check Rails' field types; I think if you define the field in the migration as date instead of datetime, you will get a Date object from the DB, not the DateTime you currently have. > but I'd just like to > know how rails is doing this, I guess is should go about downloading > the rails source and grok it myself. You've already got the Rails source. > > I'm in GMT but using daylight savings. > > I guess if I just reset the time members of the DateTime object its > returning to me I'm relatively insulated from errors if this > translation changes in a future release. There's no need to reset. There's no translation, really; Rails is creating a DateTime object, so it needs a time value. Again, you're overthinking it and persuading yourself into more complex code than is actually necessary. > > Thanks > Barry Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- 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.
