confirmed to be an issue with validates_date_time http://www.semergence.com/2006/12/20/validates_date_time-not-ready-for-prime-time/
On Mon, Nov 3, 2008 at 7:07 PM, AD <[EMAIL PROTECTED]> wrote: > I used 19:00 b/c of Time zones (EST is GMT-5). I have a before_filter that > sets the time zone to either the users time zone, or EST by default. > Database is storing it as 00:00:00 b/c we store as UTC > before_filter: Time.zone = current_user.timezone ? > current_user.timezone : $DEFAULT_TIME_ZONE where DEFAULT is EST > > mysql> select id,publish_date from clips where id=53385 ; > +-------+---------------------+ > | id | publish_date | > +-------+---------------------+ > | 53385 | 2008-11-04 00:00:00 | > +-------+---------------------+ > > Its a datetime field in DB > | publish_date | datetime > > Adam > > On Mon, Nov 3, 2008 at 5:03 PM, AD <[EMAIL PROTECTED]> wrote: > >> Hello, >> There appears to be a strange bug in Rails 2.1.1 where if I set a >> datetime field to YYYY-MM-DD 00:00:00 (using TimeZone support) Rails returns >> nil, instead of YYYY-MM-DD 00:00:00 >> >> Here is confirmed output: >> >> >> c = Clip.find(53385) >> => #<Clip id: 53385, title: "test 2", description: "test2", keywords: >> "test2", publish_date: "2008-11-03 11:13:00"> >> >> c.publish_date = "2008-11-03 19:00:00" >> => "2008-11-03 19:00:00" >> >> c.save >> => true >> >> c = Clip.find(53385) >> => #<Clip id: 53385, title: "test 2", description: "test2", keywords: >> "test2", publish_date: nil> >> >> c.publish_date >> => nil >> >> Any reason for this behavior ? >> >> Adam >> > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
