I’m a tech interested guy. I’ve touched SQL once or twice, but wasn’t able to really make sense of it. That combined with not having a practical use leaves SQL as largely a black box in my mind (though I am somewhat familiar with technical concepts in databasing).

With that, I keep seeing [pic related] as proof that Elon Musk doesn’t understand SQL.

Can someone give me a technical explanation for how one would come to that conclusion? I’d love if you could pass technical documentation for that.

  • DahGangalang@infosec.pubOP
    link
    fedilink
    arrow-up
    12
    ·
    edit-2
    6 days ago

    Yeah, obviously ol’ boy is tripping if he thinks SQL isn’t used in the government.

    Big thing I’m prying at is whether there would be a legitimate purpose to have duplicated SSNs in the database (thus showing the Vice Bro doesn’t understand how SQL works).

    I’m not aware of any instance where two people share an SSN though. The Social Security Administration even goes as far as to say they don’t recycle the SSNs of dead people (its linked a couple times in other comments and Voyager doesn’t let me save drafts of comments, I’ll make an edit to this comment with that link for you).

    Can you point me to somewhere showing multiple people can share an SSN?

    Edit: as promised: The Social Security FAQ page

    • ryegye24@midwest.social
      link
      fedilink
      English
      arrow-up
      12
      ·
      6 days ago

      Assuming the whole “duplicate SSN” thing isn’t just a complete fabrication, we have no idea what table he was even looking at! A table of transactions e.g. would have a huge number of duplicate SSNs.

      • homicidalrobot@lemm.ee
        link
        fedilink
        arrow-up
        9
        ·
        6 days ago

        The fact that SSN aren’t singular identifiers has been public knowledge for quite a while. ID analytics has shown in over a decade of studies that some people have multiple SSN attached to their name, while some (over five million) SSN are used by three or more living individuals. If you search “ID analytics SSN” you’ll find loads of articles reporting on this dating back to 2010 and a bit before.

    • WarlordSdocy@lemmy.world
      link
      fedilink
      arrow-up
      9
      ·
      6 days ago

      I mean I don’t know a ton about SQL but one thing to keep in mind about SSNs is they were not originally meant to be used for identification but because we have no form of national id and places still needed a way to verify who you are people just started using SSNs for that since it’s something everyone has and there wasn’t really a better option. So now the government has been having to try and make them work for that and make them more secure. The better solution would be to make some form of national id that is designed to be secure but Republicans and people like Musk would probably call that government overreach or a way to spy and track people.

      • DahGangalang@infosec.pubOP
        link
        fedilink
        arrow-up
        2
        ·
        6 days ago

        Ugh, YES, I am so frustrated at the counter arguments for this that I constantly hear spouted by my (ultra-conservative) family.

        I hope that notion re-enters the public consciousness as a part of this (not holding my breath tho)

    • socsa@piefed.social
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      6 days ago

      My wife has a tax payment history under two different legal names which share a single SSN

      • DahGangalang@infosec.pubOP
        link
        fedilink
        arrow-up
        2
        ·
        6 days ago

        Hmmm, well I can’t speak to how the actual databases are put together, so maybe they would have that as two separate unique primary keys with a duplicated SSN.

        But it really seems like bad design if they out it together that way…

        • JoeyJoeJoeJr@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          6 days ago

          Worth noting is that “good” database design evolved over time (https://en.wikipedia.org/wiki/Database_normalization). If anything was setup pre-1970s, they wouldn’t have even had the conception of the normal forms used to cut down on data duplication. And even after they were defined, it would have been quite a while before the concepts trickled down from acedmemia to the engineers actually setting up the databases in production.

          On top of that, name to SSN is a many-to-many relationship - a single person can legally change their name, and may have to apply for a new SSN (e.g. in the case of identity theft). So even in a well normalized database, when you query the data in a “useful” form (e.g. results include name and SSN), it’s probably going to appear as if there are multiple people using the same SSN, as well as multiple SSNs assigned to the same person.

    • kboy101222
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      6 days ago

      I’d imagine the numbers of dead people eventually get cycled around to. 9 digits only gives you 999,999,999 people to go through, and we have over a third of that in existence right now.