If I were you, then I would think this way. I am assuming that your users are just unregistered site visitors.
1. Make a search controller and a searches model to store user queries 2. Make a searchresult model to store results 3. make searchresult belongs to search. personally, i would not store search results to a table unless there is a specific need to do so. After all, same query @ different times would produce different result sets. I would consider the entities such as user, 3rd party feed as models and the search as an interaction between those entities. I will watch this topic to learn other's expert opinions. -- 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 -~----------~----~----~----~------~----~------~--~---
