The Time object in Rails 2.3.2 is problematic because it acts like a datetime whenever possible, especially in hash conversions.
I am not using time zones, and I am not using and Datetimes. The mysql Time object simply holds a string, hh:mm:ss. All I want to do is render :xml with that time to show up that way, no UTC and no date, just hh:mm:ss I can override time.to_s in enviornment.rb but when I use the to_xml it still defaults to the datetime format. I tried to override the attribute reader and then I get this error. NoMethodError: undefined method `xmlschema' for "21:25:42":String from /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/ active_support/core_ext/hash/conversions.rb:38 After looking into conversions.rb. It appears that rails thinks of time as a datetime and this doesn't seem proper, especially when Date does not. Why should a random date be assigned to the time? I'll happily make a patch, but I thought to ask if there was some sort of reasoning behind this, or a special circumstance I will destroy when allowing to a Time hash conversion like Date has, which is independent of datetime? -Josh --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
