Sam Carleton <scarle...@miltonstreet.com> wrote:
> I am using SQLite inside of Apache.  I am using the Apache connection pool
> system, so as long as the server is running there is always one connection
> to the database.  I have one very high traffic table with lots of reads and
> writes, it turns out that this info does *NOT* need to be resident beyond
> the life of the Apache server.  Is there any way to create a table that is
> in memory only and can be accessed by multiple connections?

Put it into a separate database living on a RAM drive, perhaps?
-- 
Igor Tandetnik


_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to