We're not talking about whether or not a SSN uniquely identifies a person.
We are talking about the process for changing up an
incorrectly-entered natural primary key, for whatever reason that
might be.
On Wed, Apr 4, 2012 at 9:36 AM, Durchholz, Joachim
wrote:
> Seems like everybody is looking a
Seems like everybody is looking at the institutions that can't keep their
numbers constant.
Give it a break.
Ordinal numbers of chemical elements cannot change, by definition.
I may be too optimistic about ISBNs and EANs. Haven't dealt with them and don't
know how reliable their issuers are. I g
Maybe your government doesn't goof up social security numbers, but
ours does. :-)
http://www2.nbc4i.com/news/2010/dec/06/2/study-finds-millions-duplicate-social-security-num-ar-316988/
Also, don't forget that if a social security number (let's assume the
government never messes up and assigns th
On 4/04/12 7:06 PM, Durchholz, Joachim wrote:
However any time you have a primary key with meaning is probably
a mistake in database design. You are best trying to avoid this
at all costs unless you are constrained by a legacy system in
some way.
This is common advice, but the topic is controve
