You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Microsoft.Data.Sqlite currently does not implement the standard ADO.NET metadata collections exposed through DbConnection.GetSchema(...). For example:
usingvarconnection=newSqliteConnection("Data Source=:memory:");connection.GetSchema("DataSourceInformation");// ArgumentException: The requested collection 'DataSourceInformation' is not defined.
This makes SQLite an outlier for provider-agnostic code. SqlClient, Npgsql, and MySqlConnector expose DataSourceInformation and DataTypes, so consumers otherwise have to special-case Microsoft.Data.Sqlite. In particular, pengdows.crud discovers SQLite parameter-marker syntax through DataSourceInformation.
The initial conformance scope should cover the documented common collections: MetaDataCollections, DataSourceInformation, DataTypes, Restrictions, and ReservedWords. Tables, Columns, and Indexes are provider-specific extensions rather than common collections; they may be considered separately if useful for SQLite consumers.
The implementation should use SQLite's documented metadata interfaces and correctly handle attached databases, virtual tables, shadow tables, and user tables whose names begin with sqlite.
Closing this as a duplicate of #35917, which tracks the same Microsoft.Data.Sqlite GetSchema() support question and is now the upstream discussion for the comparative provider research. The implementation work remains on #39188.
Activity
MihuBot commentedon Oct 7, 2026
I'm a bot. Here is a possible related and/or duplicate issue (I may be wrong):
alaricd commentedon Oct 7, 2026
Closing this as a duplicate of #35917, which tracks the same Microsoft.Data.Sqlite
GetSchema()support question and is now the upstream discussion for the comparative provider research. The implementation work remains on #39188.