On Thu, Sep 17, 2009 at 2:36 PM, Marnen Laibow-Koser <[email protected]> wrote: > The issue here is not the presence or absence of a join model -- after > all, for a simple habtm, there's no reason at all to introduce the extra > class. Rather, this is a reflection of the fact that the OP is trying > to do something weird. With or without a join model, there should be no > reason to add b to a.bs 3 times.
Umm yeah, well.. I work in genetics research and I can tell you I have this exact scenario _all the time_. Genetic pathways repeat throughout any genome, human or other. Your assumption that everyone's data is like your own is illogical. And like I was saying, to avoid the problem I use a join model. Storing an extra integer column and having an extra class in play costs very little when compared to the headaches of having to look up join table records using multiple keys and include limit statements. It's so much easier to just say Foo.delete( 18176236 ). -- Greg Donald http://destiney.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 -~----------~----~----~----~------~----~------~--~---
