« Ruby on Rails Calendar Helper doesn’t quite work for me
Rails: Parsing iCal calendar on a password-protected WebDAV server »

Nested resources in Ruby on Rails: why bother?

Nested resources in Ruby on Rails are sort of neat, but they are a pain to implement. What’s more, I have to ask myself, why bother?

If a resource has a unique identifier id, then why would you need to call its parent resource to call it? The unique identifier is enough. And what resource doesn’t have a unique id these days?

This entry was posted on Sunday, September 23rd, 2007 at 7:11 pm and is filed under Ruby on Rails. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.

One Response to “Nested resources in Ruby on Rails: why bother?”

  1. Anko Painting Says:
    June 18th, 2009 at 8:46 pm

    umm, you might want one form (say user details) which multiple addresses, and want that all the be handled by the same form. ie have an add address link and a remove address link.

    or allow adding teams to a user inline. I’ve used nested resources heaps.

Leave a Reply