> What are the reasons that the column types are not the expected ones? > Would it be complicated to implement or would it lose performance or > just no one cared about this yet?
It's the same with this case: Foo.find(:select=> "*, SUM(something) as SomeFakeAttribute") We don't know the type of those values, and have no reliable way to figure them out. In the event that the database driver itself does typecasting (and some of them do) you'll get the right types automatically. So it's not a performance thing, we just don't have enough information to reliably do the typecasting. The place that does is the database driver, and that's the place where you'd need to send a patch. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
