DB calls vs Session solution

Hi there, Quick question on performance: I have got some expensive sql queries (doing lots of LEFT JOINS) that result in anything between 10 to 10000 results. I need to do paging on those. So far I have used a LIMIT solution which will not do anymore because you don't get the whole total. Now, the idea is to store the results (or the sql query string?) in the session to avoid too many db calls (on paging). The question now is: is the serializing/unserializing more expensive than another db call? Thanks, T SPIRAL EYE STUDIOS P.O. Box 37907, Faerie Glen, 0043 Tel: +27 12 362 3486 Fax: +27 12 362 3493 Mobile: +27 82 442 9228 Email: thomas.hochstetter@gmx.net Web: www.spiraleye.co.za