> Can you think of any good use case for a non-arbitrary primary key? Login names; Vehicle registration numbers; flight numbers; domain names; file names; ip addresses. Keys are used in those cases where the enforcement…
The article mentions auto-incrementing keys, not surrogates. Not the same thing at all. Not all incrementing keys are surrogates and not all surrogates are incrementing keys. Also, your problem number 1 is a problem…
I'm a Protonmail user. E2E isn't snake oil but it does assume you have an alternative secure channel for password exchange. I like the fact that my mail archive is encrypted even though I don't send encrypted mail to…
> the correct solution is to use a constraint to enforce the uniqueness That would of course be correct for a natural key. It seems that you too recommend using natural keys and I agree with you on that point. Natural…
> Can you think of any good use case for a non-arbitrary primary key? Login names; Vehicle registration numbers; flight numbers; domain names; file names; ip addresses. Keys are used in those cases where the enforcement…
The article mentions auto-incrementing keys, not surrogates. Not the same thing at all. Not all incrementing keys are surrogates and not all surrogates are incrementing keys. Also, your problem number 1 is a problem…
I'm a Protonmail user. E2E isn't snake oil but it does assume you have an alternative secure channel for password exchange. I like the fact that my mail archive is encrypted even though I don't send encrypted mail to…
> the correct solution is to use a constraint to enforce the uniqueness That would of course be correct for a natural key. It seems that you too recommend using natural keys and I agree with you on that point. Natural…