hi pablo, > I'm trying to set up a many-to-many relation with cmp and XDoclet, and > what do I find in the XDoclet web-site best practices ? "Try to avoid > compound primary keys". > > > I've been working in banking software for more than 16 years, and 90% (or > maybe more) of the keys I've used have lots of fields. I thought we were > developing professional applications. How can I avoid using compound keys? > it's easy...don't use them internally :) why not using UUID or any other computed key ? I must signal that ther's a huge distinction between object model & relational one.... > Even the simplest entity, the customer, has a compound key: document type > and document number (and sometimes more fields). What should I say to my > users? We would rather use a single field customer_id because of technical > reasons? > > > I don't know if this is a Xdoclet, EJB, J2EE, containers or whatever > issue, I think people defining standards have to get closer to real > business solutions. > yes but always you must do some trade-offs ,ins't it ?
cheers jerome > > > --------------------------------- > Do you Yahoo!? > Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
