Support collections of owned entities

[AndriySvyryd]

[SneezeWeeze]

Any chance this will be included in the 2.1.0 release in Q4?

[AndriySvyryd]

@SneezeWeeze It's currently in the Backlog, meaning it is not planned for the next release.
You can vote for features by using the +1 reaction on the original comment (👍)

[crhairr]

I don't think #246 should be considered closed without this since enumerables are a very common use case for complex types in the NoSQL world.

But I'd also like to add to this that key-value/dictionary types should be supported, as this is another very common "enumerable" complex type in the NoSQL world.

[divega]

I don't think #246 should be considered closed...

@crhairr it seems our team just tracks work very differently from what you expect. In case it helps you understand:

• We often close issues when significant portions of the scenarios they originally represented are covered. Then we create new issue for remaining scenarios. As I already explained to you, Complex types and/or value objects #246 was closed because owned types can already do a superset of what complex types could do in EF6, and that was a very significant milestone for us.
• Although dictionaries are somewhat related to this issue, they are tracked separately in Rich collection support: Dictionary, Lookup, HashSet, etc. #2919.

[crhairr]

Yeah, I saw the dictionary issue earlier and already upvoted it. I meant to come back here and reference it directly to link the two.

As for how you track your work: at every company I've ever been at that uses Agile, the dev team would have gotten yelled at for closing issues when "significant portions" were done, instead of when the issue was "completely done" according to original acceptance criteria. I guess prior management has beaten that into me, so I'll stop paying it forward.

What I'm really interested in is better support for third-party, NoSQL DB providers for EFCore. Complex Type support is a huge part of that and seems like relatively low-hanging fruit given how rich EFCore's metadata system already is. Properly supporting complex types would go a very long way to getting more third party DB providers in play and having a more expanded EFCore community. It would also REALLY help me out with my MongoDB provider.

[divega]

@crhairr regarding the important of these features for supporting document oriented databases, I think we are in complete agreement.

@smitpatel is currently working on a provider for the Document DB API in Cosmos DB and we hope to learn a lot about what is missing and how to approach document databases in general. I would recommend that you track his steps in this process and that you keep engaging in conversations with us about this. Ideally, your expertise on the MongoDB requirements will help us produce a better design that can accommodate more document database providers easily.

[ahmedtolba1984]

@AndriySvyryd @divega
When will you support this feature 'Collection of Owned Types' ?

[divega]

@ahmedtolba1984 the plan is to work on this soon after we finish 2.1.

[ahmedtolba1984]

@divega
Thanks :)