I'll give you what advice I do know. I'm not sure it will fully help you with your situation but it may help you to rethink your strategies.
First, make sure your tables are normalized before assigning associations to them. If you are going to work with HABTM then 3NF or greater.. The larger the query the better. Smaller queries are worse than one enormously large query because rails caches that query for use and doesn't have to go out and do another.. and another.. It will be less of a problem to process the data once you have it so I wouldn't worry about data processing at this point. It's better to just get the design and associations going. Without seeing your models, it's more difficult to guess what may be right or wrong from a design point. You might want to state exactly how many models you have, what tables and relationships you currently have associated which will help tie into your original topic. -- 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 -~----------~----~----~----~------~----~------~--~---
