> You're probably better off ignoring all this stuff and just getting a > working solution. Only then is it worth running some sort of > profiling system on your application to find out which bits are most > worth optimising. Since the sqlite3 library is pretty fast already > you might find that fiddling with shared cache defaults could make > only 5% the improvement that improving the rest of your code will.
I agree - if I ever did those timings, now would not be the best time :) The solution that I have now works well (without shared cache), so I'll move on to other areas for the time being - it's fast enough, as most time is spent elsewhere (processing the actual files). Dennis _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
