See the post on BlueSky: https://bsky.app/profile/provisionalidea.bsky.social/post/3lhujtm2qkc2i
According to many comments, the US government DOES use SQL, and Musk is not understanding much what’s going on.
See the post on BlueSky: https://bsky.app/profile/provisionalidea.bsky.social/post/3lhujtm2qkc2i
According to many comments, the US government DOES use SQL, and Musk is not understanding much what’s going on.
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!!!
That, or he doesn’t understand composite keys.
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.
Nah, they are supposed to be unique. If it was that it’d at least be a design choice potentially worth 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… 🙄