Hello, Does anyone out there use compound primary keys in their EO model? I know there are several ways to model persistence, but I am sort of stuck with a database structure that cannot be changed (at the moment). I have read/been told some WebObjects advice that we seem to give dire warnings about not using the automated primary key generation features of WebObjects on every table. There seems to be a mantra that all tables need a single primary key, which is automatically created and and that compound primary keys are evil... well at least that was the gist :-)
While I do use automated primary key generation, I inherited a few tables that are "join tables" where the primary keys are compounded. It seems like from reading the Apple docs and even seeing the propagate primary key option in EOModeler, that is there is support for this concept. I am just interested if there are those out there that have used "propagate primary key"/compound keys or even custom-generated primary keys in real-world WebObjects applications? I know I could try to convince the DBA to redesign the data model, but at this point trying to see if WebObjects can handle this legacy application or if I proceed, with trying a WebObjects solution, that I will be heading for pitfalls without using the "WebObjects way". Pete _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
