[Not entirely AndroMDA related, but...] On the other side of the PK(A,B) "debate" is the fact that I'm just now going through a (non-AndroMDA, dotNet) database and application making a lot of changes because the client has thrown another dimension into the many-to-many relationship. So the many-to-many PK and all the code that uses it has got to change, and the FK, PK and code for the tables that hang off this relationship (and then off those relationships, etc.).....
I find myself thinking: If only they'd used a surrogate key (and thrown a unique index on the two FK fields, presumably).... [And doesn't hibernate recommend not having more than one field in the PK? I've only read the docs a bit, though...] Mike. _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1383#1383 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- 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
