Hi Scott,
Thanks for your response. I have properties and A and properties on B
therefore C has to extend both A & B. This is the same kind of problems
encountered with multiple inheritance when you program in C++. The problem
is how OrientDB resolves ambiguities.
What I want is to have all my vertices to posses and id, createAt and
updateAt fields by adding those properties to V. This way all classes that
inherit from V will have those base properties.
Doing it the way you suggested would leave me without an id field for B
and without createAt, updateAt for A. I want A, B, and C to have id,
createAt and updateAt and for C to inherit the properties of A, B, and V.
>>>In other words, you added properties to V, making it the superclass and
extended A and B from it, which means they both have the same properties as
V. Then you extend C from A and B, both having the same inherited fields. I
guess OrientDB doesn't realize the same fields are coming from V and just
adds them together, which, from an inheritance perspective, isn't wrong
either.
That is technically true that "it isn't wrong" but the then the question is
which id field is OrientDB going to use when you access C.id? Should it be
C.A.id? or C.B.id? Will it use the first one and will it be consistent?
This is what I need to know. My guess is that the dups will create wasted
space in the database but I can live with that. What really matters is
consistent access to the information.
Cheers,
Chris.
>
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
