Re: Compound Primary Keys and WO
Re: Compound Primary Keys and WO
- Subject: Re: Compound Primary Keys and WO
- From: Florijan Stamenkovic <email@hidden>
- Date: Tue, 12 Jul 2005 08:54:28 +0200
On Jul 11, 2005, at 16:29, Sam loy wrote:
My question is this: How do you guys - WO Novices to Experts (Me being
a total Newbie) deal with Compound PKs? Do you avoid them like the
plague? Is it considered just part of bargain and no big deal (i.e.
Setting a delegate to create PKs)? Is it something I will inevitably
*have* to deal with and might as well get started?
It is inevitable (or better to say it is standard procedure) in
creating many-to-many relationships (see Apple's documentation, book
called Using EOModeler), but in that scenario you will use propagate
primary key option on some involved relationships, so key generation is
still done automatically for you. As I understood it is normally bad
practice using any exposed, functional, attribute (car license number
for ex.) for your primary key. Thereby I always have a _single_ non
exposed int or long attribute used as the primary key. In which case
the generation of it for new records is automatic. No hustle involved
:)
Cheers
F
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden