11–20 of 125 posts
I have never understood why RDBs have such general concepts of primary keys, where you can for example let date of birth be a primary key, when in every schema I have ever designed or seen, all rows get unique integer IDs anyway.
What about people with the same birthdays?
At a quick glance on my databases, I see nothing of the sort.
I have never understood why RDBs have such general concepts of primary keys, where you can for example let date of birth be a primary key, when in every schema I have ever designed or seen, all rows get unique integer IDs anyway.
The textbook case would be student IDs in a university database where each row corresponds to a single student. However some universities view the student id as sensitive information (kind of like a ssn in the US) and so in that scenario it should be aliased to some other key to prevent the student id from being present in multiple tables as a foreign key.
Earlier quoted context omitted.
What about people with the same birthdays?
What about them? Do they really exist, practically speaking? At a quick glance on my databases, I see nothing of the sort.
I have never understood why RDBs have such general concepts of primary keys, where you can for example let date of birth be a primary key, when in every schema I have ever designed or seen, all rows get unique integer IDs anyway.
It's rare in practice but occasionally rows have natural unique identifiers that are useable. The textbook case would be student IDs in a university database where each row corresponds to a single student. However some universities view the student id as sensitive information (kind of like a ssn in the US) and so in that scenario it should be aliased to some other key to prevent the student id from being present in m…
It is ironic, given that the whole reason to have a student ID is for it to be a primary key in some database somewhere.
I have never understood why RDBs have such general concepts of primary keys, where you can for example let date of birth be a primary key, when in every schema I have ever designed or seen, all rows get unique integer IDs anyway.
What about people with the same birthdays?
I have never understood why RDBs have such general concepts of primary keys, where you can for example let date of birth be a primary key, when in every schema I have ever designed or seen, all rows get unique integer IDs anyway.
Earlier quoted context omitted.
What about them? Do they really exist, practically speaking? At a quick glance on my databases, I see nothing of the sort.
https://en.wikipedia.org/wiki/Birthday_problem
I would guess that you would need a big group of random people such that there is a high chance of having two people born the very same day.
Earlier quoted context omitted.
What about them? Do they really exist, practically speaking? At a quick glance on my databases, I see nothing of the sort.
https://en.wikipedia.org/wiki/Birthday_problem
I have never understood why RDBs have such general concepts of primary keys, where you can for example let date of birth be a primary key, when in every schema I have ever designed or seen, all rows get unique integer IDs anyway.
Earlier quoted context omitted.
https://en.wikipedia.org/wiki/Birthday_problem
Is there anything comparable to the birthday paradox, which includes years, by the way? I would guess that you would need a big group of random people such that there is a high chance of having two people born the very same day.