> I'd have to say though at this point I'm still having trouble deciding > if I would need my own join tables. For most of my tables I'm thinking > not. The more I think about I can't think of any situation I would > need a join table anymore but then I wonder if it's just ignorance > lol. Support tickets for example. A Ticket will have many updates. > I'll always find the ticket_updates via :through & :has_many. And if I > have a ticket_update I can always find the ticket because ticket_id > would be stored in the ticket_update.
Imagine that your Support tickets system has ability to attach some tags to ticket. How would you implement that? Generally join tables are used when there is has_and_belongs_to_many association. One can look at has_many :through as a join table fat enough to become a model itself. Regards, Rimantas -- http://rimantas.com/ -- 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.
