Narrow the feature gap between EF Core and EF6

dotnet / efcore

EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.

https://docs.microsoft.com/ef/

MIT License

13.64k stars 3.15k forks source link

Narrow the feature gap between EF Core and EF6 #24106

Open roji opened 3 years ago

roji commented 3 years ago

This is a grouping of related issues. Feel free to vote (👍) for this issue to indicate that this is an area that you think we should spend time on, but consider also voting for individual issues for things you consider especially important.

There are still some scenarios supported on EF6 which aren't on EF Core. In order to make it as easy as possible to transition from EF6 to EF Core, we plan to close this gap as much as possible, although some scenarios will remain unsupported by design.

Done in 6.0

[x] #22609
[x] #22475
[x] #13805
[x] #12088
[x] #10059

Done in 7.0

[x] #214
[x] #3864
[x] #11003
[x] #3170
[x] #19811
[x] #620
[x] #245
[x] #15911
[x] #11624
[x] #17653
[x] #19929
[x] #19930
[x] #4038

Done in 8.0

[x] #10753
[x] #10042
[x] #30426

Backlog

[ ] #10140
[ ] #831
[ ] #16491
[ ] #23206
[ ] #5536
[ ] #14544
[ ] #16298
[ ] #8127
[ ] #12895
[ ] #29143
[ ] #31236
[ ] #29013

ankitmatrix08 commented 2 years ago

@AndriySvyryd May I know why this has been removed from 7.0.0 milestone as before it was on scheduled and confirmed here ?

roji commented 2 years ago

@ankitmatrix08 this has been changed to the "epics" milestone, which is where we track over-arching epics which track specific issues. It's just a "book-keeping" change - the concrete issues tracked here are still in the 7.0 milestone and are still planned (though that doesn't mean all will necessary make it in).

ajcvickers commented 2 years ago

@dotnet/efteam We need to discuss Epics again. When do we close them? If someone votes for an Epic, what are they voting for?

roji commented 2 years ago

I personally like to have epics in the milestone, allowing both ourselves and users to track work in the milestone for a high-level item. Here's how Npgsql does it - it's been very useful for me (and hopefully for users) to be able to drill down like this.

For work that's ongoing across multiple versions (e.g. EF6 parity), each milestone epic can simply reference the one before etc., and we can have one in the backlog for unplanned work.

But we should probably discuss in a design meeting...

ankitmatrix08 commented 2 years ago

@ankitmatrix08 this has been changed to the "epics" milestone, which is where we track over-arching epics which track specific issues. It's just a "book-keeping" change - the concrete issues tracked here are still in the 7.0 milestone and are still planned (though that doesn't mean all will necessary make it in).

@roji That's the thing, since it's not clear as to what all items will make it to the 7.0.0 (among ef6-parity) release hence the confusion and trouble for us decide our migration.

roji commented 2 years ago

@ankitmatrix08 the milestone on each individual issue determines whether it's in the plan or not. This issue is just a list referencing those issues for easier tracking; we generally update it to keep it in sync, but that may not happen right away. Just check individual issues directly.

mairaw commented 1 year ago

I'm cleaning up the .NET 6 project. This shows as completed on the project dashboard but still open here. Not sure if this needs any updates.

roji commented 1 year ago

@mairaw thanks, we're using this to track overall EF6 parity issues across versions (6.0, 7.0, backlog...). Short of creating a separate issue for things we did in 6.0 and tracking that in the project, I think it makes sense to simply remove this.

mairaw commented 1 year ago

Sounds good @roji. Thanks for making the update.