I'm trying to model, for the purposes of XSD schema generation, the following pseudo XSD code,complexType name="Account" ...complexType name="Ledger" sequence element name="accnt" type="Account"so that Ledger contains a whole instance/copy of Account. ER Studio works well and is suggestive on how to model Ledger having a reference to Account (or vice-versa) once PKs are defined. But that's not what I am looking for.
Surely, there has to be more to this "nearest." I mean c'mon!: contains, has-a, encapsulation is a long running bonafide issue at least in physical models even if the logical ER model does not directly support it.
Another way to represent this in a logical model is by using a SubType relationship, but I don't think it gets you any closer to what you want
Powered by IDERA