Re: Problems using primary key as attribute
Re: Problems using primary key as attribute
- Subject: Re: Problems using primary key as attribute
- From: Ray Ackland <email@hidden>
- Date: Sun, 17 Aug 2003 18:56:52 +1200
Pam,
In this case, the client # is intended to be a unique identifier for a
specific person. The only purpose of this number is (apart from playing
a part in the relationships) is to help the staff find the file in the
cabinet.
Names can change. Client information can change. I can't think of any
instances when that number should change (kind of like a primary key
really).
Ray.
On Sunday, Aug 17, 2003, at 17:01 Pacific/Auckland,
email@hidden wrote:
OK, then what happens when the client # is changed, which is definitely
possible for any number of reasons? If you have a separate key, you can
make the changes without blinking.
Pam
Ray Ackland wrote:
I don't know if I would go along with such a strong critique. All they
are doing is using the primary key in a relationship with a real life
filing cabinet. This just means that the key need to be human readable
(or get the computer to go to the filing cabinet for them :).
The only knowledge contained in the client # is what record to look up
(in the cabinet) which is what is the norm.
r.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.