Reiner, My suggestion then is to come up with your classes first and then make a design. A very common pitfall is to design for something that "may" happen and then later face over engineered code.. In the late nineties, we called this the YAGNI principle which stood for "You Aint Going to Need It!"
If you propose your new more complete class model, I can help with your polymorphic associations (If you still need them).. Lastly, remember that PAs are not free, they add extra conditions to the select clauses which can be quite costly with improper or imcomplete indexing. Reiner Pittinger wrote: > > But how to do this with "the magic" of Rails? -- 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 -~----------~----~----~----~------~----~------~--~---
