Giorgi / DuckDB.NET / 36412182719

88%

push

github

Add a regression test that CommandBehavior.CloseConnection closes the connection last

f94d52b moved command.CloseConnection() after the reader's own cleanup in
DuckDBDataReader.Close. Besides exception safety, that order prevents database
corruption: with the old order, when the reader's connection is the file's last
one, the database is closed while the reader still holds native objects, and
concurrent reads and writes on a file database intermittently failed with WAL
replay errors, checksum mismatches, 'database has been invalidated' and native
crashes. This test fails with the old order and passes with the current one.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1601 of 1899 branches covered (84.31%)

Branch coverage included in aggregate %.

3229 of 3560 relevant lines covered (90.7%)

419442.97 hits per line