Julian Leviston wrote: > Yes, you should store simply an array of ID's, not the entire objects. > An ID (integer) is about 4 bytes or so from memory, so it won't be > terribly much information...
This seems a terrible flaw* to me then: how am I supposed to store this kind of data? I cannot use a normal global, instance, or class variable as these could become confused if multiple users are accessing the service at once. Am I supposed to create a new, temporary per user database -- and how would I do that? I guess I could keep track of the search terms that produced the list instead of the list itself, then when a sort is selected, reapply the search and then sort. *but maybe not surprising considering the nature of the html/http beast. -- 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 -~----------~----~----~----~------~----~------~--~---
