mugle-dev team mailing list archive

[David Coles <coles.david@xxxxxxxxx>]

Yes. I think that's the right thing to do. We can work out Team
membership by just looking at the UserTeamRelation. We want to try and
avoid any duplication of values if at all possible.

David

On Fri, 2011-02-11 at 14:24 +1100, Scott Ritchie wrote:
> Awesome, ill hopefully get all these mapped out to Classes this
> afternoon. 
> Just a quick question;
> 
> For one to many relationships (for example UserTeamRelation -> User) i
> have currently just made it so the class at the "1" end owns the class
> at the many end:
> ie:
> UserTeamRelation {
>    private DevTeam team;
>    private User developer;
> }
> 
> Should i also show this relationship on the otherside? 
> ie:
> User {
>     private ID;
>     ....
>     private List<UserTeamRelation> teams;
> }
> 
> Currently im only doing the former, and leaving out the latter.

Attachment: signature.asc
Description: This is a digitally signed message part