Hi, assume following scenario
<<Entity>>User <<Entity>>Right - User - Right assocation: 1 +user --- 0..* +rights <<Entity>>AdministrationRight (subclass of Right) <<Entity>>Foo <<Entity>>RightToFoo (subclass of Right) - RightToFoo - Foo assocation: 0..* -rightToFoo --- 1 +foo Since RightToFoo's association to Foo is required (1 on foo association end), FK_FOO column in generated RIGHT db table will be created as NOT NULL. And therefore you will not be able to create any AdministrationRight, since db create statement for this will of course not contain FK_FOO. Well.. hope you get the point ;) Of course this example is a bit stupid but if there'd be plenty of RightToXXX subclasses, this subclassing scheme may make more sense (since I'd for sure like to model just one association between User and Right instead of drawing a new association to every RightToXXX). My question is.. what can I/we do with this? Is it right if the corresponding FK_FOO is created as NOT NULL? Doesn't seem so.. So would it make more sense if it was NULL capable or would it break something? AndroMDA 3.0 R.O.C.K.S !!! -- Sincerely Tomas Brejla ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
