Agree. some_model/1/other_model/2 is a lame way to refer to join_model/1. Evan
On 7/7/07, Josh Peek <[EMAIL PROTECTED]> wrote: > > On Jul 7, 11:12 am, Geoff B <[EMAIL PROTECTED]> wrote: > > I think a case can be made for using an [EMAIL PROTECTED], @track] nested > > route > > -- say a user browsed to album 45, and then clicked track 219 -- if > > your UI requires a "back to album 45" navigational link on the track > > page, you couldn't infer the referring album id from the resource id > > alone if there's a many-to-many relationship between albums and tracks > > -- instead, you'd need to grab the album id from the URI > > If your referring to a HABTM relationship, look into creating a real > join model between them using has many though. That why you have a > real resource you can point your url to. > > > > > -- Evan Weaver Cloudburst, LLC --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
