Is this really true? I can think of lots of situations where you
might have multiple contacts with the same email address. For
example, [EMAIL PROTECTED] could be a shared mailbox for several
sales reps who don't yet have their own accounts (yes, it still
happens in this day and age...) or the person who checks a generic
email address changes over time or [EMAIL PROTECTED] that is used
by many people in a family.
In the situation of the person checking a generic email address
changing, how will you handle that if it is a constraint in the
database? Delete the old contact? Not allow the new contact? I think
you'd be far better off checking to see if it exists already,
flagging it as a _potential_ duplicate and allow a human to make the
determination. Often times customers don't understand the cascading
impacts of decisions like this.
I think this is a case of something seeming unique, but really isn't.
You can have a business rule that says they don't want duplicates,
but hard-coding business rules into the DB can lead to problems in
the future. Use Java to enforce the business logic, not the DB.
Dave
On Jan 15, 2008, at 9:55 AM, Miguel Arroz wrote:
A contact list may have tens of thousands of contacts (this is not
a theoretical limit, it's a requirement), and cannot have duplicate
records (ie, two contacts with the same email).
_______________________________________________
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]
