Justas

@microsoft-github-policy-service agree

After some investigation I found that root cause of such behavior is that `DuckDBCommand` always execute queries using method `PreparedStatement.PrepareMultiple`. Which uses these C API methods: * `duckdb_extract_statements` * `duckdb_prepare_extracted_statement`...

In given case even if `duckdb_execute_prepared` would log failed queries I don't think DuckDB.NET would work "out of the box", because code fails fast earlier: ```cs var status = NativeMethods.ExtractStatements.DuckDBPrepareExtractedStatement(connection,...

IMHO from the perspective of the C API, the behavior appears to be correct. When using a Prepared Statement, if the preparation phase fails, the query itself is not executed...

True. The given solution won’t cover all cases, but it will handle the scenario where `CommandText` is a single SQL statement without any parameters. I think this is quite a...