Giorgi
commented
1 year ago Implementing an EF Core provider for a database is a huge task. I don't have any (short-term) plans to implement it. You could probably modify EF Core SQLite provider and modify it to work with DuckDB instead but I haven't looked into it.
If you need the provider to use in a commercial product, you can contribute it back to the project or you could fund the development.
Did you look already into creating a IQueryable/LINQ provider? There are many use cases in .NET where such a provider would be really nice.
We are currently looking into enabling easy access to parquet files over an GraphQL API. IQueryable would allow us to filter and project client requests to duckdb directly.