consider the following example (that what I would like to model):
Entity: Department
Attributes: ...whatever...
Relationships:
headOfDepartment --> Employee
viceHeadOfDepartment --> Employee
pointyHairedBoss -->
dilbert -->
other Employees -->>
Entity: Employee
Attributes: ...whatever...
Relationships:
department --> Department
Every Employee is only in one Department. The Department has (and
needs) four special Employees (head, vice head, pointy haired boss,
dilbert). Turns out that it is impossible to model this with
bidirectional relationships if you don't want to model it like that:
Entity: Employee
Attributes: ...whatever...
Relationships:
departmentImHeadOf --> Department
departmentImViceHeadOf --> Department
departmentImPointyHairedBossOf --> Department
departmentImDilbertOf --> Department
departmentOtherEmployeeOf --> Department
What about:
Entity: Department
Attributes: ...whatever...
Relationships:
headOfDepartment --> Role
viceHeadOfDepartment --> Role
pointyHairedBoss --> Role
dilbert --> Role
other Employees -->> Employee
Entity: Role
Attributes: ...whatever...
Relationships:
department --> Department
employee --> Employee
(add role-type attribute or subclass Role if needed)
Entity: Employee
Attributes: ...whatever...
Relationships:
department --> Department
roles -->> Role
That's basically the same as your "ugly" version, just less ugly.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
