Verity search next/previous buttons 2

[MikeCF]

Hi,

I'm currently writing the results page for a Verity search. I will need to use next/previous for users to be able to page through results. The only problem is that any time i've done this kind of thing before, the query has to be processed each time the page is refreshed.

This is a big overhead each time the user goes forward or back through the search results. Is there a way to do previous/next without the need to re-query upon refreshing the page?

thanks,

Mike

 

[NorthStarDA]

i dont think there is a reliable way to do that, i've often wondered the same thing (not for verity, never used that but for general list pages with next/prev buttons). i dont know if you can do it with verity, but i often cache my query for a few minutes, then when they go forward it pulls from cache which is much faster.

 

[webmigit]

I don't use verity so I doubt this is applicable for verity but NorthStar.. here's something I found that helped..

I ran my query the first time with all my various criteria.. and saved the returned record IDs to a file named a random number.. this same random number was passed along the prev/next fields as a url variable.. And I read that file..

Using that method, I was able to cut 33% off my load time (1.8 seconds down to 1.2).

ALFII.com

http://www.alfii.com

---------------------
If this post answered or helped to answer your question, please reply with such so that forum members with a similar question will know to use this advice.

 

[NorthStarDA]

good idea webmigit,

so you save that as a text file? do you think saving to a temporary table would speed it up any more or no?

i had come up with another solution to this some time ago which involved doing something very similar where i would put the ID's of the returned list into a session variable- but because of the amount of data i was dealing with it was not a 'memory friendly' option.

 

[webmigit]

Saving to a tempory table might work better, I hadn't thought of that..

Hopefully my results with my idea might inspire you to try yours..

ALFII.com

http://www.alfii.com

---------------------
If this post answered or helped to answer your question, please reply with such so that forum members with a similar question will know to use this advice.

 

[MikeCF]

Thanks guys, great food for thought there! I had wondered about using a temp table. Maybe saving the search results to that and populating a 'keyword' column with the keyword the user had entred in the search. Then I could query the table on each page refresh (with the prev/next buttons) and pull out the result set using keyword. This might have the added advantage of being able to save common search items with their results in the table thus saving more time on frequent searches on the site. Of course, as it happens this site has to be singing and dancing by this Friday (quelle surprise!) so I'm gonna program the 'old fashioned' version and then update it afterwords (honest ;-)),

cheers and thanks for the help,

Mike