> Suggestion: After you run ANALYZE, go back and modify values in > sqlite_stat1 (and sqlite_stat2 if you are using SQLITE_ENABLE_STAT2) with > "typical" values that you would expect to see in most databases. Yes, you > can read and write the sqlite_stat1 and sqlite_stat2 tables. Maybe you can > come up with some prepackaged default values for sqlite_stat1 and > sqlite_stat2 based on experiments in your development lab, and then just > put > your prepackaged defaults into the real sqlite_stat1 and sqlite_stat2 after > running ANALYZE. > > Thank you for the helpful suggestion-- I do recall reading previously that you could modify the _stat tables, but haven't ever pursued that approach. (Mostly, I was avoiding the extra work of having to maintain these "magic" stat values in our code; partially lazy, partially in case my test data wasn't as "typical" as I thought it would be.) Either way, it seems a straightforward enough solution that I can try.
One question: After I modify this stat data, do I need to close/reopen the connection for the changes to take effect? Or will the results be used automatically the next time I create the prepared statement? Thank you again. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
