I could be way off since I know nothing about the actual application, but here's what I think:

To keep results consistent for the end user in the face of potential updates to the database between the initial and follow-up requests, I would probably keep a separate table containing the active "sessions" and the query results associated with that session. (Or store them by other means)

To illustrate:

1. User searches for "XXXX" which yields 3 hits(1, 4 and 5)
2. Database record 5 is updated and no longer matches "XXXX"
3. User requests match no.3, should receive record 5 which would no longer match if the initial query was executed again. He would probably be very confused if that record suddenly wasn't available. ("You just told me there were 3 matches!") Even if this will potentially send outdated info.