Muzaffer Dogru wrote: > > Why do you need a relationship *class*? > How else would I realize a many-many relationship? Each person needs a collection (list, array) of Roles.
> I need a third table to make the "connection" between > each person and his/her roles, don't I? Personally, I don't see why. Are you aware that object can have a property that is a collection? All I see is that a Person needs to have a collection of Roles. I can also see why you might want each Role to have a list of the Persons have have that Role, but to me that is really an index on Person.Role items (which I think I heard doesn't work with SQL yet). But there is no such object as a PersonRole - that is an RDBM artifact. You could make such a class merely to segregate these data from the Person object. But I don't believe that you *need* it. Regardless, your real problem seemed to be with ORefs and OIDs.
