Forgive me for reopening an old thread, but > posts/1/comments/34 > > Which then lets me do > > @post = user.posts.find(params[:post_id]) > @comment = @post.comments.find(params[:id])
Forgive me, but I actually do think that's silly. If I really needed to do that I'd do @comment = Comment.find(params[:id], :include=>[:post] @post = @comment.post and save a hit to the database. I'm having a really hard time wrapping my mind around the nesting, except that the URL looks pretty. Do you really mean to say that we should be accessing both objects that way? It seems really hackish. When I did this without nested routes on my first project, I built URLs this way but never used the post_id in the URL at all. Is that wrong? I'm just looking for some enlightenment here, not trying to be difficult! :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
