First off, I am reasonably sure that giving a form field a numerical name is going to fail, although I am not 100% sure that Rails doesn't do something clever about that. I know that in HTML, the ID attribute may never start with a number, not sure about the name attribute, though.
Second, if you want all of these choices to arrive at the server in a meaningful chunk, your best bet is to name them so that the browser will treat the value assignments like a nested hash, rather than a bunch of dissociated individual values. Take a look at this form submission in your console while it's running in development. What do you see in the params hash that prints out as the form is submitted?
Do your teams have a corresponding ID? Why not use that as your key, rather than the manually-incremented num?
Walter
> please suggest.
>
> thanks
> Jai
>
> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
rubyonrails-ta...@googlegroups.com.
> To post to this group, send email to
rubyonra...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-talk/5e2f92db-9c77-4151-825a-fb3d062e8a62%40googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.