We do stuff like this all the time. caching data locally.

The deal is we store last datetime changed for each row in each table in our database. Every time the row gets changed the datetime gets updated.

The various systems that use the data search the local data cache, not the external database.

Before doing the search we do an update to the cache and to do that we keep track of the lastdatetime when the database was looked at and we look for any rows that have changed since then. If the result set is zero, then the cached data gets used as is and the lastdatetime gets incremented in the cache.

If the resultset is not zero, we grab the changes, and incorporate them into the data set and then update the cache date.

Then once the cache is updated, we do the search.

If the cache is empty, or the last cache check date is empty, we do a complete pull from the database.

Kee


On Jan 14, 2008, at 11:28 AM, Richard Miller wrote:

I'm looking for suggestions on how to accomplish the following.

1. User starts a search of my text-based database (via browser and Rev cgi). 2. My app finds the results (which are a series of line numbers... possibly as many as 1000) 3. I now want to store those results so that when the user brings up a data page resulting from the search, they can go back to the results (presumably to go to another data page from the results) without having to re-do the search or use the back-button on their browser. I know how to store the results within a link (i.e. http:// www.results.com?results=1,2,3..."), and I'm using this in various places already. But this won't work for me in all cases.

I'm guessing one solution might be to issue a temporary id number and connect that to a given users search process. The results could then be stored in a file on the server under this ID, with this page liquidated after some period of time (30 minutes? 60 minutes?). Would this work or is there a better way to handle this.

Thanks.
Richard Miller
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution




-------------------------------------------------
I check email roughly 2 to 3 times per business day.
Kagi main office: +1 (510) 550-1336


_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to