Re: Avoiding duplicate records
Re: Avoiding duplicate records
- Subject: Re: Avoiding duplicate records
- From: David Avendasora <email@hidden>
- Date: Tue, 15 Jan 2008 11:50:20 -0500
Oh sure, bring scalability into it... ;)
But that's why I was also suggesting it be flagged as a potential
duplicate in _this_ situation. I don't think that you can really
depend upon email addresses as being unique between two people. Now,
he did always say "contacts" in the original email, so are contacts
different from people?
Dave
On Jan 15, 2008, at 11:08 AM, Mike Schrag wrote:
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.
Initiate religious argument .............. NOW.
Regardless of the business logic debate, one HUGE caveat here is
that you cannot properly resolve several race conditions in EOF
implementing logic purely in Java. In particular, enforcing
uniqueness is a really nasty one. If you have multiple instances
or multiple EOF stacks, you will always be open to a race trying to
keep values unique without also having a unique constraint on your
database (where the database can enforce that atomically).
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40avendasora.com
This email sent to email@hidden
_______________________________________________
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