DuckDB 2.0.1 LTS restores per-match updates in SQL
A target row with two source matches counts twice and appears twice in RETURNING output. The DuckDB patch also lets users register custom extension repositories by hostname under the default settings.
The DuckDB team released DuckDB 2.0.1 on November 20, the first patch in its 2.0 long-term support series. The patch restores DuckDB 1.x behavior for UPDATE ... FROM and the MERGE update action when several source rows match the same target row.
DuckDB says the statements now apply one update per match. A target row that matches twice contributes two to the affected-row count and appears twice in the output if the statement uses RETURNING. If the matches supply different values for the same column, the final value can vary.
In 2.0.0, MERGE raised an error when several source rows matched a target row for an update, while UPDATE ... FROM used one match. The DuckDB team said it reversed the change after it slowed large updates. DuckDB says the final value is predictable if each target row has at most one source match or if all matches supply the same values for the updated columns.
The patch also lets users register custom extension repositories by hostname. With a publisher’s hostname in CREATE EXTENSION REPOSITORY, DuckDB reads a metadata file on that host over verified HTTPS. It follows the repository URL in the file and pins the public signing keys from the repository’s own metadata for later signature checks.
The default for allow_extension_repositories is now hosts, which permits hostname-based registration and keeps previously registered repositories trusted. Adding a repository with an explicit WITH PREFIX requires setting it to allowed. The previous default, undecided, blocked new registrations, and 2.0.1 rejects that setting value. DuckDB describes custom extension repositories as a work in progress and says the metadata format may change.
DuckDB also fixed a filtering bug that could omit rows with NULL values from tables in database files written by DuckDB 1.x.
The DuckDB 2.0.1 Python package requires Python 3.11 or later and is available as prebuilt wheels and a source distribution.
More news

Databricks details interactive architectures for 70 industries

MotherDuck launches experimental Excel add-in preview

ClickHouse previews Arrow Flight connector for Power BI
