3 ms·
Reading the "Key Changes" section, it looks like the sqlite4_env environment will address the global mutex problem that was discussed in a recent HN thread. Th
by jasode 12y ago
Reading the "Key Changes" section, it looks like the sqlite4_env environment will address the global mutex problem that was discussed in a recent HN thread.
The pluggable db engine looks interesting but if I remember right, in MySQL the pluggable db engine initially attracted some niche providers but the marketplace of ideas eventually settled on ISAM/Innodb.
What's still not clear from the Executive Summary is if there would be any compelling use case for the older SQLite3 for reasons other than backward compatibility. It would be great if the SQLite designers could answer: "You'd want to use v3 instead of v4 for greenfield projects if...?"
- SoftwareMaven 12y agoI don't think there is an answer to your question beyond "it's been battle tested extremely well", but there are strong reasons to move to sqlite4 (in particular, multiple linked instances in eg mobile apps and mobile OSes). It's not like Python where the weight of the existing community has drawn you towards python 2 (something that has changed a lot recently).
- jasode 12y agoThat's fair but I guess I was looking for a stronger statement from them because even for new minor point releases, the sqlite.org home page says clearly: "Version 3.8.4.3 of SQLite is recommended for all new development." Every time they change the "z" in v.x.y.z, they'll still state "is recommended for all new development." So, it seems like they could just clearly say, "SQLite4 is recommended for all new development." ...unless there's some architecture tradeoff (unrelated to backward compatibility) that still makes SQLite3 desirable over SQLite4.
- keeperofdakeys 12y agoSqlite3 is used in so many places, they would be fools to deprecate it. Maybe in five years, they'll revisit the issue, but for now they want to improve the fundamentals of sqlite. One good thing is I expect most of their testing code can be ported over to sqlite4 http://www.sqlite.org/testing.html http://www.sqlite.org/testing.html