mcpField
S
sqlite-adonet

sqlite-adonet

github.com/dotnetDevelopment14.8k48 installsUpdated today
Repository

About sqlite-adonet

A development skill for diagnosing and testing Microsoft.Data.Sqlite behavior at the ADO.NET provider layer. It focuses on command and transaction lifecycles rather than EF Core abstractions.

Key features

  1. 01ADO.NET command lifecycle guidance
  2. 02SQLite statement cleanup on connection close
  3. 03Retryable failed COMMIT behavior
  4. 04Transaction disposal and rollback tests

Use cases

  1. 01Investigating commands reused after a connection reopens
  2. 02Testing failed COMMIT separately from disposal errors
  3. 03Diagnosing connection close and reopen behavior

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dotnet/efcore --skill sqlite-adonet

After installing, type/sqlite-adonetin Claude Code to confirm it loaded.

Details

From the project README

Microsoft.Data.Sqlite

Standalone ADO.NET provider in src/Microsoft.Data.Sqlite.Core/, independent of EF Core. Implements System.Data.Common abstractions.

Notable Implementation Details

  • Static constructor calls SQLitePCL.Batteries_V2.Init() reflectively
  • CreateFunction()/CreateAggregate() overloads generated from T4 templates (.tt files)

Command Lifecycle

SqliteConnection tracks associated commands as weak references. Closing an open connection disposes every live tracked command before closing the native connection; command disposal releases prepared statements and unregisters the command. Diagnose close/reopen reports from this ownership path and the System.Data.Common contract, not from EF Core provider abstractions.

Closing does not erase the command's managed configuration or connection reference. If the same command object is used after reopening its connection, execution prepares fresh native statements against the new handle. Add a regression test only when the reported behavior remains reachable after following this lifecycle.

Transaction Completion

A failed COMMIT can leave the SQLite transaction active and retryable. Do not call Complete() or add transaction-level retries; SqliteCommand already retries busy/locked results through the connection's ExecuteNonQuery path.

Rollback during disposal must detach the managed transaction even when rollback throws, so keep Complete() in its finally. Test failed commit separately from failed Dispose()/DisposeAsync(): preserve the original exception and verify disposal permits a subsequent transaction.

Comments

Markdown supported