For discussion on SQLite 3.39.0, see <a href="https://news.ycombinator.com/item?id=31876604" rel="nofollow">https://news.ycombinator.com/item?id=31876604</a><p>I'm not sure why a minor SQLite bugfix release needs to be posted here.
Changes in version 3.39.0 (2022-06-25):<p>Add (long overdue) support for RIGHT and FULL OUTER JOIN.<p>Add new binary comparison operators IS NOT DISTINCT FROM and IS DISTINCT FROM that are equivalent to IS and IS NOT, respective, for compatibility with PostgreSQL and SQL standards.<p>Add a new return code (value "3") from the sqlite3_vtab_distinct() interface that indicates a query that has both DISTINCT and ORDER BY clauses.<p>Added the sqlite3_db_name() interface.<p>The unix os interface resolves all symbolic links in database filenames to create a canonical name for the database before the file is opened.<p>If the SQLITE_OPEN_NOFOLLOW flag is used with sqlite3_open_v2() or similar, the open will fail if any element of the path is a symbolic link.<p>Defer materializing views until the materialization is actually needed, thus avoiding unnecessary work if the materialization turns out to never be used.<p>The HAVING clause of a SELECT statement is now allowed on any aggregate query, even queries that do not have a GROUP BY clause.<p>Many microoptimizations collectively reduce CPU cycles by about 2.3%.<p>From the changelog.
I wanted to find something more interesting than news of a minor patch release about what is probably the worlds most installed database.<p>Turns out the developers sell licenses and a few proprietary extensions - I never knew about CEROD or SEE before. <a href="https://www.sqlite.org/purchase/license" rel="nofollow">https://www.sqlite.org/purchase/license</a>?<p>I wonder if proceeds from this commercialisation alone are sufficient to keep the OSS effort going or whether the devs also have other paid endeavours.