Hey Benjamin, Take a look at this website I found about cached and in-memory databases. I think the gist of the article is that caching is good if you are doing SELECTs on data that is frequently used whereas in-memory speeds up writes, (inserts and updates) to the db as well as querying. Maybe I am missing something?
http://www.mcobject.com/in_memory_database Denis <http://www.mcobject.com/in_memory_database> On Mon, Aug 30, 2010 at 3:00 PM, Benjamin Peterson <benja...@python.org>wrote: > Denis Gomes <denisg640 <at> gmail.com> writes: > > > > > Eventually my goal is to dynamically load and unload sections of a file > based > database (could be tables or rows) in and out of memory for effeciency > purposes. > > Have you actually found this to be an useful optimization? SQLite already > internally caches database information in memory. > > > > > -- > http://mail.python.org/mailman/listinfo/python-list >
-- http://mail.python.org/mailman/listinfo/python-list
