There is a fresh source-code snapshot of the unreleased 3.18.0 version
of SQLite up on the download page:
https://www.sqlite.org/download.html
https://www.sqlite.org/draft/releaselog/3_18_0.html <--- Change log
Have you ever wondered when you should run ANALYZE on an SQLite
database? It is tricky to figure out when that is appropriate. The
new "PRAGMA optimize" command tries to automate the decision for you.
Simply run "PRAGMA optimize" just prior to closing your database
connection, and SQLite willl automatically run ANALYZE if it thinks
doing so will improve query performance. Usually, the "PRAGMA
optimize" will be a no-op. But every now and then it will reanalyze
important indexes and thereby help you queries to run optimally. See
https://www.sqlite.org/draft/pragma.html#pragma_optimize for
additional information. Feedback on this new feature is encouraged.
NOTE TO FOSSIL USERS:
If you access the SQLite sources directly using the Fossil version
control system (https://www.fossil-scm.org/fossil/doc/trunk/www/index.wiki)
then you should upgrade to the latest version of Fossil - probably the
latest unreleased trunk version. Newer versions of Fossil understand
SHA3-256 hash names on artifacts in addition to the older SHA1 names.
Older versions of Fossil only understand SHA1 names. We expect to
start using SHA3-256 hash names in the SQLite repository soon. If you
fail to upgrade, your older "fossil" application will give an error
the first time you try to "fossil update" after SHA3 content is added.
See https://www.fossil-scm.org/fossil/doc/trunk/www/hashpolicy.wiki
fpr additional information.
--
D. Richard Hipp
d...@sqlite.org
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
