sqlite-adonet

Document implementation details for the Microsoft.Data.Sqlite ADO.NET provider.

14.8k|3.4k|Updated Jan 23, 2014
One-click install
npx skills add https://github.com/dotnet/efcore --skill sqlite-adonet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sqlite-adonet
Source: https://github.com/dotnet/efcore/tree/main/.agents/skills/sqlite-adonet
Command: npx skills add https://github.com/dotnet/efcore --skill sqlite-adonet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation and guidance for implementing and maintaining the Microsoft.Data.Sqlite ADO.NET provider, specifically for changes under src/Microsoft.Data.Sqlite.Core/.

Core Features & Use Cases

  • Standalone ADO.NET provider in src/Microsoft.Data.Sqlite.Core/, independent of EF Core.
  • Implements System.Data.Common abstractions to enable consistent data access across providers.
  • Serves as a reference for maintenance tasks, bug fixes, and new feature work on the provider.

Quick Start

Identify the relevant source files under src/Microsoft.Data.Sqlite.Core/ and follow the existing coding standards to implement the required changes.

Frequently Asked Questions about sqlite-adonet

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement changes to the Microsoft.Data.Sqlite ADO.NET provider?

To implement changes to the Microsoft.Data.Sqlite ADO.NET provider, identify the relevant source files under src/Microsoft.Data.Sqlite.Core/ and follow existing coding standards to apply edits safely.

What is the Microsoft.Data.Sqlite provider's relationship to EF Core?

The Microsoft.Data.Sqlite provider is a standalone ADO.NET implementation in src/Microsoft.Data.Sqlite.Core/ that operates independently of EF Core while enforcing consistency with System.Data.Common abstractions.

Does the Sqlite ADO.NET provider depend on EF Core abstractions?

No, the Sqlite ADO.NET provider does not depend on EF Core. It implements System.Data.Common abstractions directly to enable consistent data access and guide provider edits independently.

When do I need to use System.Data.Common abstractions in the Sqlite provider?

You need to use System.Data.Common abstractions when modifying the ADO.NET surface in src/Microsoft.Data.Sqlite.Core/ to ensure consistency across data access providers during maintenance or bug fixes.

What are the limitations of editing the Sqlite ADO.NET provider surface?

Provider edits are specifically limited to changes within the src/Microsoft.Data.Sqlite.Core/ directory, focusing on the ADO.NET surface and related abstractions rather than EF Core provider modifications.