Giorgi / DuckDB.NET / 33151549788

88%

push

github

Expose DuckDB configuration options on DuckDBConnectionStringBuilder

The builder previously exposed only DataSource, so neither IntelliSense nor a
property grid could discover any of the ~300 configuration options DuckDB
accepts, and the only way to set one was an untyped string indexer.

Add 24 typed properties for the options that can be applied when the database
is opened, covering access mode, resources, storage, security, extensions,
query defaults and client metadata. Each carries Category, DisplayName and
Description attributes, with DisplayName matching the connection string keyword
the property writes so that tooling does not show the option twice. Value-typed
options are nullable, keeping "not specified" distinct from any value DuckDB
would accept: its defaults are computed at runtime, and threads rejects 0 as
well as negatives, so there is no usable sentinel.

Add DuckDBAccessMode, DuckDBSortOrder and DuckDBNullOrder so options with a
fixed set of values are typed rather than stringly. Getters accept every
spelling DuckDB itself accepts, including the sqlite, mysql and postgres null
orders; setters emit the canonical form.

Generate a PropertyDescriptor for every remaining option reported by
duckdb_get_config_flag, typed from duckdb_settings() and grouped by name, so
tooling sees the option set of the native library actually in use rather than a
list baked in at build time. List-valued options are omitted because
duckdb_set_config rejects every string form of a VARCHAR[] value.

Normalise every accepted data source spelling to a single stored keyword.
Keeping both "Data Source" and "DataSource" let a connection string hold two
conflicting values where the stale one silently won.

Fixes #346

1547 of 1841 branches covered (84.03%)

Branch coverage included in aggregate %.

197 of 251 new or added lines in 2 files covered. (78.49%)

3111 of 3440 relevant lines covered (90.44%)

378994.44 hits per line