I'm doing a DBA class right now, and something that comes up is that the only stable reference to some tables should be a unique identifier, either a numerical private key, or some sort of...
I'm doing a DBA class right now, and something that comes up is that the only stable reference to some tables should be a unique identifier, either a numerical private key, or some sort of surrogate (system-defined, typically numeric) key. This allows you to exist with your ID number, and any identity, such as department or name can change. It just makes sense from a technical perspective.
My table designs, and justifications for projects, are that any field that can change should be free to, and they'll still have that unique identifier, but I think that's also hinted at in my textbook where I likely picked it up.
One of those things GDPR actually really handled well: it treats "the ability to correct your personal information" as a fundamental right.
I'm doing a DBA class right now, and something that comes up is that the only stable reference to some tables should be a unique identifier, either a numerical private key, or some sort of surrogate (system-defined, typically numeric) key. This allows you to exist with your ID number, and any identity, such as department or name can change. It just makes sense from a technical perspective.
My table designs, and justifications for projects, are that any field that can change should be free to, and they'll still have that unique identifier, but I think that's also hinted at in my textbook where I likely picked it up.