On Dec 18, 4:56 pm, byrnejb <[email protected]> wrote: > Now, in my case both R and U must exist before they may be associated > and neither may be created in the same process that creates the > association row in C. Further, the association in C contains data > unique to that association.
Hi, I was about to post a very similar problem although I think it is a bit simpler so an answer would be great if someone can give us a hand. What I found in those tutorials about complex forms is that they create relations on the fly to new objects (also created in the same process) and this case is slightly different you need to establish a relation between the object you are instantiating and an existing one. In my case I have a model say House and I need to assign it a Category instance, but I don't want to instantiate a new Category for that object, I just need to associate that object with an existing category object via its ID, how can I do that? I've been looking at fields_for and nested models but I don't think this is the case to apply that approach, let me know if I'm wrong. Thanks! m. -- 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.
