On 7/7/07, DHH <[EMAIL PROTECTED]> wrote: > > > > You shouldn't need to be scoping person #1 if its the unique id. > > I think this is going too far. I too prefer to limit the scope to one > level, but there are legitimate reasons to have deeper nesting. / > albums/45/tracks/1 (where the track number is scoped on the album).
I think Josh's grudge is against: /tracks/219 == /albums/45/tracks/219 ... where the track id is the unique ID of the track. This is perfectly fine with me, on the other hand: albums/45/tracks/1 ... but then we're talking about composite primary keys, which aren't popular amongst Rails devs. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
