in reply to A database caching scheme

This is not a Perl solution, however it may be a better solution for your situation. Have you thought about caching the recordset not in memory but in the DB itself using a temp table? This would allow you to share the recordset, reduce network traffic, as well as offload some of the logic to the DB.

Replies are listed 'Best First'.
Re^2: A database caching scheme
by bprew (Monk) on Nov 14, 2004 at 23:06 UTC
    I would agree with terra. In fact, if you're using oracle, you can create session-level temporary tables that will expire when the session disconnects:
    CREATE GLOBAL TEMPORARY TABLE foo ( bar VARCHAR2(16), baz DATE ) ON COMMIT PRESERVE ROWS
    Unfortunatly, I don't know about other RDBMS's such as Postgres or MySQL. Hope that helps

    --
    Ben