Marnen Laibow-Koser wrote: > > Why not create a "wheels" view which combines the data from all the > "wheels_for_*" tables, then tie your Wheel model to that? > > Best, > -- > Marnen Laibow-Koser > http://www.marnen.org > [email protected]
I think that would have some performance issues. If there were 20 tables, but only 1 of them contained wheels for the car I was working on then all 20 tables would have to be checked during a join, no? -- Posted via http://www.ruby-forum.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 -~----------~----~----~----~------~----~------~--~---
