Wojciech Ciesielski wrote:
||conceptually you are correct, but technically it's hard to maintain
||these relationships, for example, which of all offices is the 'primary'
||one ?
[Ciesielski]
I would add isPrimary:boolean to User2OfficeAssignment with constraint to
enforce only one primary per user. Or - completely 'object' solution: add
User.primaryOfficeAssigment pointing to exactly one User2OfficeAssignment
object. And there is no ambiguity :-)
Wojtek
except for the fact that the latter office /must/ be present in the
other relationships as well
(the primary office must be an office where the user has a role)
that's indeed what I'm doing now .. I guess it's the nicest way to
currently do it
-- Wouter
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Andromda-user mailing list
Andromda-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/andromda-user
