Vladimir Prieto wrote: > On 25 mayo, 11:29, Robert Walker <[email protected]> wrote: >> I can't imagine why you would need to do something like this > > imagine this: > > - too much records to search for. > - after a few searches, user finally get a group of records (not only > one) to work on. > - user edits one > > ...save it and he has to search again to get the same group? no way! > users are lazy. instead, why don't show him the same group of records > that he search before? that way, user can edit the next over and over > again without searching everytime. > > so, how can i get the same group of searched records? searching > again. am i right?
If I were to implement this I would create a new model, something like Search or SavedSearch, and use the database to store recent searches. Someone also mentioned that you could store the search criteria in the session, which would work fine, as long as you only need to store one set of search criteria per user. Storing the search criteria in it's own table adds more flexibility to the system. This way you could allow the users to essentially "bookmark" their searches. Since you would have this separate Search model you could provide views for users to organize and manage their searches. -- 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.
