slindsey3000 wrote: > I have had the worst time getting my forms to accept input for more > than one model. I tried using accepts_nested, and other techniques > and finally got it all working. But it was not fun. I never did get > accepts_nested working!
accepts_nested works very easily. If you can tell us what problems you're having, I'm sure we can help. > > I do need more experience. > > I did hit upon one idea that I just wanted to run by the community. > Let me know what you think. > > If you have one form that will need to send values to several > models.... how about creating a "Form" model with generic attributes. > This "Form" model could for example have fields integer1:integer, > integer2:integer ... etc.. and have fields string1:string, > string2:string..... etc.. > > You would build a "Form" model that could handle any form in your > site. > > Then you just collect the values into this "Form" model.. after they > are in you just assign them to all your other models. No need to go > crazy with all those parameters[][:this][:that]. Bad idea. Beside the conceptual wrongness, the resulting params hash will be *harder* to work with (because the names won't be descriptive), not easier. If you want to do soething like this properly, check out the Presenter pattern. > > It for sure may not be the MOST efficient way to deal with the > database, but it can't be that bad. It is that bad. Don't even bother. > > Thoughts? > Learn the framework, don't fight it and kludge your way around it. > Shawn Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. -- 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.
