that's right .. I personally also recommend simply using a single primary key which is entirely decoupled from any business attributes/objects
Hibernate also recommend this strategy, and AndroMDA works optimaly when working this way for example, the CRUD feature which generates an entire application to manage your tables: can't handed these primary keys it's just that if you start down that road things become unneccesarily complex -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1384#1384 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
