It seems like this conversion would be better handled in the controller or model.
Using anything other than integer primary keys also becomes riskier. So far Rails has done a pretty good job of permitting non-integer keys. I would hate to see that fall by the wayside. -1 On Feb 20, 7:39 pm, i am jbarket <jbar...@sleepunit.com> wrote: > Hey guys, > > I've got a very minor patch up. Tests for assocation_ids= still work > fine with these changes. > > Basically, some things send params for multiselects and such as > ["1,2,3,4"] and, while it might be possible to make sure that these > things handle what they send on their own, it seems like something > Rails should easily be able to deal with. > > The patch verifies the format and, if it finds something like this, it > converts it to the [1,2,3,4] Rails would prefer. > > Thanks for taking a look guys. > > http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/20... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
