-
Notifications
You must be signed in to change notification settings - Fork 871
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
Inheritance of Edges is not respected #7201
Comments
As I understand inheritance of edges, what is shared are the properties of the edge, not the connectivity. Naturally, this only works, if you are using standard edges and not lightweight edges. If you connect two vertices with "is_underlying", that is the only connection being made and the only connection you'll see. So, what you are seeing is correct behavior. Now, to make clear what is happening with inheritance, let's say you add a property "createdAt" on the "ist_komponente" edge class. If you create an edge with "is_underlying", the "createdAt" property is also available to use in the schema of the "is_underlying" edge class. If you also searched for edges created on a certain day from the "ist_komponente" class, you'll also get results from the "is_underlying" class. That is what inheritance offers. Scott |
The problem is: The database is inconsistent. If I ask the Component-Edge: How many Items belong to Stilhalter, I get "3" as answer. |
hi @topofocus
You should use graph function and not use the fields directly
|
I notice, Edge-properties just reflect the morphology not the structure. Thanks for clarification. I will adapt this in ActiveOrient. |
OrientDB Version: 2.2.15
Expected behavior
Edges should respect object inheritance
Actual behavior
Edges are displayed separately in every case
Steps to reproduce
Because
E < ist_komponente < is_underlying
"ist_komponente" must include #85:0
is the expected result.
In my view, this is a major bug
The text was updated successfully, but these errors were encountered: