Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dynamic Entities with Dynamic Navigation Properties that fit with NoSQL Graph db providers #1513

Closed
jersiovic opened this issue Feb 1, 2015 · 4 comments

Comments

@jersiovic
Copy link

Do you have evaluated the idea of supporting dynamic types for entities with navigation properties to other entities that fit with Graph dbs or hibrid dbs(Document+Graph). Nodes of those dbs are schema free and each node can be connected to other different nodes.
So it would be great EF will allow us to use dynamic navigation properties instead of use the current ones we define in the class. Those navigation properties will be set per object instead of per type, in that way we could harness the real power of NoSql dbs

This request is related with this other issue in Orchard CMS Github where we discuss about how can fit EF7 with the dynamic schema Orchard uses: OrchardCMS/OrchardCore#12

@jersiovic
Copy link
Author

Hibernate OGM (http://hibernate.org/ogm) does support from time ago schema free data.
https://hibernate.atlassian.net/browse/OGM-470
Will also EF7 support it?

@divega
Copy link
Contributor

divega commented May 23, 2015

Looking at items that have been sitting on my plate for some time I found this one that I think at this stage either belongs in the backlog or possibly closed if we believed it is something we are never going to do, so clearing up milestone.

The main point is obviously to have truly schema-less models, where each instance can have its own shape, or at least some more limited but still useful version of that, such as enabling "complex type" properties that are schema-less which has been supported by other O/RMs for a long time.

OrchardCMS/OrchardCore#12 is an interesting read too, although it is clear Orchard does not need EF7 to support this feature.

@divega divega removed this from the Discussions milestone May 23, 2015
@divega divega removed their assignment May 23, 2015
@rowanmiller rowanmiller added this to the Investigation milestone May 27, 2015
@rowanmiller
Copy link
Contributor

@divega to open a new issue capturing the expand object feature and put on backlog

@divega
Copy link
Contributor

divega commented May 28, 2015

We won't be supporting anything like this for now but I have captured some information on dynamic models for our backlog in #2282. I am going to close this item in favor of that one.

@divega divega closed this as completed May 28, 2015
@divega divega removed this from the Investigation milestone May 28, 2015
@divega divega removed their assignment May 28, 2015
@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants