DuckDBConnectionStringBuilder's property set is quite anemic

[masonwheeler]

An ADO.NET connection string builder class is meant to allow users to build a connection string programmatically in a safe, well-typed manner. Every configuration value should have a property, with the appropriate data type, so that they can be found via reflection and thus be available to Intellisense for developers to use. This is table stakes. A truly well-designed connection string builder class should also annotate the properties with the appropriate category and description attributes, so that a property inspector can categorize them in a useful way.

DuckDBConnectionStringBuilder has none of that. It exposes only a single property, DataSource, despite the documentation listing over 100 valid properties. Furthermore, it bizarrely treats every property name that is not a data source as invalid if accessed by name. This makes the connection string builder highly inaccessible to both users and tooling.

Would it be possible to bring this connection string builder up to snuff?

[Giorgi]

It doesn't treat property names as invalid:

if (DataSourceKeys.Contains(keyword) || ConfigurationOptions.Contains(keyword))
{
    base[keyword] = value;
}
else
{
    throw new InvalidOperationException($"Unrecognized connection string property '{keyword}'");
}

[masonwheeler]

You're right. My mistake; I misread that second clause.

Even so, the lack of proper properties severely limits its usefulness, leaving the list of configuration options opaque to both users and tooling.

[Giorgi]

What do you suggest?

[masonwheeler]

If you have the NativeMethods.Configuration.DuckDBGetConfigFlag method available, which will give you a name and description of every property, it shouldn't be too difficult to write a simple code generator to create the code for these properties. Most of the properties are strings, so iterate the config options, generate a string property for each one, and stick a [Description()] attribute on them with the description, and a blank [Category("")].

Then go back and double-check them, filling in the categories and making sure that properties that aren't strings get typed correctly.