Thats interesting. I didn't know anything about normal forms, but a quick glance at G4G has some interesting information. I don't have the time to go through their full article at the moment, but its been added to my to do list.
Link for the lazy: https://www.geeksforgeeks.org/types-of-normal-forms-in-dbms/
This sounds like a reasonable argument.
Can you pass any resources with examples on when having duplicate values would be useful/best practices?
Right, but if there were multiple entries with the same SSN, wouldnt that be a concern?
Just so I'm clear, you're implying that a given SSN could appear associated to multiple "keys" because the key-value pair in a NoSQL database could have complex data.
An example I can imagine is a widow collecting her dead husband's Social Security. Her SSN could appear in her own entry and also in her dead husband's as a payee of that benefit, thus appearing as a "duplicate" SSN.
Is that in line with what you're saying?
But they are implying SSN to SSN+Birthdate is a one-to-many relationship. Since SSN to SSN should be one-to-one, you can conclude the SSN to Birthdate is one-to-many, right?
A weak example would be my grandma. She was born before social security and was told as a kid she was born in 1938. Because I guess in the olden days, you just didn't need to pass your birth certificate around for anything, it wasn't until she went to get married at ~age 25 that she needed her birth certificate and when she got it, it actually said she was born in 1940 (I forget the actual years, but I remember it was a two year and two day gap between dates).
Its a weak example that should apply to only a microscopic portion of the population, but I could see her having some weird records in the databases as a result.
Edit: brain dropped out and I forgot part of a sentence.
A given SSN appearing in multiple tables actually makes sense. To someone not familiar with SQL (i.e. at about my level of understanding), I could see that being misinterpreted as having multiple SSN repeated "in the database".
Of all the comments ao far, I find yours the most compelling.
Beat me to asking this follow up, though you linking additional resources is probably more effort that I would have done. Thanks for that!
Look, I'm just glad I have the technical skills to reconfigure my system.
Talking to my parents/grandparents/other family that aren't tech savvy, they all complain about how one drive and Microsoft's ads, and Edge keep butting into their lives, but then they have no idea how to mitigate the constant pings about those things.
I'm glad someone is enjoying Microsoft's barrage of services tho.
I'd stop whining about it if they'd stop reinstalling it.
Ah the old "malware detectors have the selectors for malware and so they show up as malware to other malware detection systems" problem.
Yeah, that seems like a reasonable case to have duplicate SSNs.