• @[email protected]English
    43•2 days ago

    Sounds like he got confused looking at a view of a join.

    SELECT holder_name, amount
FROM account JOIN transaction ON transaction.account_id=account.id;

-- WTF!! THERE'S DUPLICATES!!!
    • SchadrachEnglish
      4•2 days ago

      Not even that complicated - SSN are not unique, by design. The combination of SSN and name is supposed to be, but for most of the history of the program no one was actually checking for that so it really isn’t either. Until something like 2014 the first 5 digits of your SSN were basically a code for where you were born and the last 4 were just assigned in order.

      • @[email protected]English
        4•2 days ago

        Nah, they are supposed to be unique. If it was that it’d at least be a design choice potentially worthy of criticism. But consider, who’s more likely to have fucked up a database task: Musk? Or the designer, someone with a degree (a real degree) on this topic?

        Don’t worry: since he’s so big on transparency, I’m sure he’ll release the schema so we can check his work… 🙄

        • @frog_brawler
          3•1 day ago

          It seems inevitable that we’d have some duplicates by now… with 330 million people alive in the US today, and SSNs starting out in 1936, there’s no way everyone could have a unique number; especially with the consideration of the first 3 digits of the code correlating to place of residence at time of requesting a SSN.

        • LiveLMEnglish
          1•2 days ago

          With the way things are going, let’s say there will be lots of people checking out a lot more than just the database schema…