Re:SQL is 43 years old – Here’s why we still use it today
by yawaramin on Sunday May 07, 2017 @02:13PM
(#14286671)
A composite key made up of foreign keys in a junction table.
Re:SQL is 43 years old – Here’s why we still use it today
by irishsultan on Wednesday May 03, 2017 @07:58AM
(#14254931)
How often does the birthday of people change? (Then again, how likely is it to be unique?)
Re:SQL is 43 years old – Here’s why we still use it today
by sobani on Wednesday May 03, 2017 @08:45AM
(#14255163)
The closest example I can give is that I work on a system where the birthday can be partially unknown. This mostly affect refugees. So the person either has to guess his own age, or only knows the year, or only the year and month.
Then again, someone might make a mistake. "What do you mean 09-11 is not November 9th, you silly American."
Now that I think of it, I guess the best argument against natural keys is "typos".
Note I will disqualify anything that has a reasonable chance of changing, like the primary email address of an account, a persons name, a persons day of birth or the 'public id' of a bank account