[
https://issues.apache.org/jira/browse/IGNITE-20475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17841849#comment-17841849
]
Pavel Tupitsyn commented on IGNITE-20475:
-----------------------------------------
Investigation complete, working PoC created:
https://github.com/apache/ignite-3/pull/3675
*Conclusion*
Implementing an EF Core provider is feasible and we should do that.
*Proposed Work Plan*
See IGNITE-22132:
1. Implement ADO.NET classes (connection, command, etc): IGNITE-22131
2. Polish the PoC implementation to create a basic provider: IGNITE-22133
3. Add specification tests, create tickets for missing/failing things:
IGNITE-22134
4. Add NuGet package once we have most of the tests working
> .NET: Thin 3.0: EF Core provider (investigate)
> ----------------------------------------------
>
> Key: IGNITE-20475
> URL: https://issues.apache.org/jira/browse/IGNITE-20475
> Project: Ignite
> Issue Type: New Feature
> Components: platforms, thin client
> Affects Versions: 3.0.0-beta1
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: .NET, ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> EF Core provider will allow using Ignite as any other DB supported by EF.
> This makes adoption incredibly easy for the users - a matter of a few changed
> lines to switch from Postgres/MsSQL/MySQL, keeping all existing code.
> This is also a big undertaking and needs more investigation/PoC.
> * https://learn.microsoft.com/en-us/ef/core/providers/writing-a-provider
> *
> https://blog.oneunicorn.com/2016/11/11/so-you-want-to-write-an-ef-core-provider/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
