>Your goals make a lot of sense. However I think you can do my second >suggestion. Compile with STAT2 code included by default, but make the >analyze command only build stat1 by default. > >This will result in no change in default behaviour, but means that anyone >wanting to use stat2 can easily do so. (The vast majority of SQLite >non-embedded device deployments do not compile SQLite themselves and are >arguably in the "business applications" demographic.) > >If I build a database right now and mail it off to another random SQLite >user and even if I compile with stat2 and run analyze, then it is unlikely >they will be able to make use of the stat2 information. > >You can make ANALYZE take a numerical argument or a word such as FULL or >QUICK to explicitly choose which flavour is used.
Roger, you're right once again! That setup would be a must for many, even possibly most, users with no (apparent) downside. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
