SQLite version 3.7.0 is now available on the website
http://www.sqlite.org/
The most important change in version 3.7.0 is that SQLite now supports
write-ahead logs as an optional method for transaction control, for improved
performance and concurrency. Additional information can be found here:
http://www.sqlite.org/wal.html
We are actually already using the write-ahead logging feature on the SQLite
website itself, in the Fossil DVCS that tracks all changes to the SQLite source
tree. (Yes, the SQLite write-ahead log code is stored in an SQLite write-ahead
log database - how's that for recursion!)
http://www.sqlite.org/src
The added concurrency of the write-ahead log journaling mode allows multiple
users to be doing extended read operations, such as checking out historical
versions of the SQLite code or looking at extended timelines simultaneously
with developers making new checkins, adding or editing tickets, or actually
rebuilding the entire 10-year source code database. The write-ahead log code
has performed very well so far for us.
Version 3.7.0 also marks the official cut-over to our new SQLite logo and a new
color scheme for the website. We hope you like the new look.
The 114-day time span since the previous release (version 3.6.23.1) is the
longest span between consecutive releases in the 10-year history of SQLite.
Much of that time was spent testing and stressing the new write-ahead log
feature. This is probably the most thoroughly tested release of SQLite that we
have every produced. And so even though the write-ahead logging feature is
entirely new, we are very hopeful that the 3.7.0 release will prove to be
stable and robust and ready for production use.
Of course, if you do happen to run into problems, please let me know at once.
Thanks!
D. Richard Hipp
[email protected]
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
