Here's what I want C to look like using your example:
create property V.id binary
create property V.createAt datetime
create property V.updatedAt datetime
create class A extends V
create class B extends V
create property A.someOtherField string
create property B.andYetAnother integer
create class C extends A, B
This is what I expected:
class C
{
property id binary;
property createAt datetime;
property updatedAt datetime;
property someOtherField string;
property andYetAnother integer;
};
Below is how OrientDB produces class C:
class C
{
property id binary;
property id binary;
property createAt datetime;
property createAt datetime;
property updatedAt datetime;
property updatedAt datetime;
property someOtherField string;
property andYetAnother integer;
};
OrientDB doesn't appear to recognize that V is common to both A & B. As I
stated I can live with this once I know that when C.id is accessed it will
be consistent and not throw and error.
There should be some mechanism to resolve ambiguities otherwise OrientDB
may be creating extra space for duplicate properties.
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.
