I have an application with the following behavior: - Data is large -- gigabytes or 10s of gigabytes (will never fit into memory) - the indexes for the data is small -- will definitely fit into memory - it will be relatively rare that any particular data is accessed more often than others
for these reasons, it would never be advantageous for sqlite to ever cache the data into memory. ideally it would always keep the entire index in memory and never cache the data. i've read other posts on this list that say that we can't guess what sqlite will do with cache. however, could i be relatively confident that most of the time, it will prioritize keeping the index in memory before it starts keeping the data? if i can't more or less depend on this, then sqlite probably won't work for my application. Thanks, John _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
