I searched my irc logs and found the chat where I mentioned the specific commit: http://github.com/rails/rails/commit/aa5cdb0d47fb5484bfdde8244df7efeb2175bf3a
I don't remember how well I tested that though. But do find out :) Eloy On 17 mrt 2009, at 23:49, Eloy Duran wrote: > I once looked into this as well, but worked around it > :) > > Anyways, the problem was introduced in Hash.from_xml iirc, > it has nothing to do with the recent changes to xml mini. > > Eloy > > On 17 mrt 2009, at 22:35, stewbawka wrote: > >> >> Hey all, >> >> Just updated rails and i have a bunch of activeresource models that >> connect to a bunch of tables that don't follow the rails naming >> convention.. they actually have CamelCase field names, which wasn't >> my >> idea, but i have to deal with it.. it was working fine pre-upgrade, >> but now when i get an object or hash from activeresource the >> fieldnames/keys are uncamelized (ie: CustomerID becomes >> customer_id).. >> >> This change is causing me much grief and i don't want to keep >> referencing the fields by their actual fieldnames. >> >> I know that the new rails allows for you to swap the xml parser out >> for another one though i haven't actually figured out how to do this. >> I used to have the faster_from_xml plugin installed on my app along >> with the libxml-ruby gem, but the upgrade broke the plugin so i >> deleted the plugin. Is it the parser that is doing that to the field >> names or is it something inside activesupport? >> >> thanks a bunch! >> >> Stuart >> >> >> > --~--~---------~--~----~------------~-------~--~----~ 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 [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-core?hl=en -~----------~----~----~----~------~----~------~--~---
