Is it a good idea to store and access an active query resultset in Coldfusion vs re-quering the database?
===

I have a product search engine using Coldfusion8 and MySQL 5.0.88

The product search has two display modes: **Multiple View** and **Single View**. 

**Multiple** displays basic record info, **Single** requires additional data to be polled from the database. 

Right now a user does a search and I'm polling the database for   

  **(a)** total records and   
  **(b)** records FROM to TO. 

The user always goes to **Single view** from his current resultset, so my idea was to store the current resultset for each user and not have to query the database again to get (waste a) overall number of records and  (waste b) a the single record I already queried before AND then getting the detail information I still need for the Single view. 

However, I'm getting nowhere with this. 

I cannot cache the current resultset-query, because it's unique to each user(session). 

The queries are running inside a CFINVOKED method inside a CFC I'm calling through AJAX, so the whole query runs and afterwards the CFC and CFINVOKE method are discarded, so I can't use query of query or variables.cfc_storage. 

So my idea was to store the current resultset in the Session scope, which will be updated with every new search, the user runs (either pagination or completely new search). The maximum results stored will be the number of results displayed.

I can store the query allright, using:

     <cfset Session.resultset = query_name>

This stores the whole query with results, like so: 

    query
    CACHED: false 
    EXECUTIONTIME: 2031 
    SQL: SELECT a.*, p.ek, p.vk, p.x, p.y
        FROM arts a
            LEFT JOIN p ON 
            ...
            LEFT JOIN f ON 
            ... 
            WHERE a.aktiv = "ja"
            AND 
            ... 20 conditions ...

    SQLPARAMETERS: [array]
    1) ... 20+ parameters

    RESULTSET: 
     [Record # 1] 
        a: true
        style: 402
        price: 2.3
        currency: CHF
        ...
     [Record # 2] 
        a: true
        style: 402abc
        ...

This would be overwritten every time a user does a new search. However, if a user wants to see the details of one of these items, I don't need to query (total number of records & get one record) if I can access the record I need from my temp storage. This way I would save two database trips worth **2031** execution time each to get data which I already pulled before.

The tradeoff would be every user having a resultset of up to 48 results (max number of items per page) in Session.scope.

**My questions**:  
1. Is this feasable or should I requery the database?  
2. If I have a struture/array/object like a the above, how do I pick the record I need out of it by style number = how do I access the resultset? I can't just loop over the stored query (tried this for a while now...).



Thanks for help! 
