!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rule 1- All posts must be legitimate questions. All post titles must include a question.
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Rule 2- Your question subject cannot be illegal or NSFW material.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding META posts and joke questions.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
Rule 7- You can't intentionally annoy, mock, or harass other members.
If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here.
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
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.
How come republicans keep saying that doggy is going to expose all the fraud in the government but yet the biggest fraud with 37 felonies is president? What the actual fuck to these people think?
He is saying the US government doesn't use structured databases.
At least 90% of all databases have a structure.
I think a lot of comments here miss the mark, it's not really just about stating the gov does not use SQL or speculation regarding keys.
Deduplication is generally part of a compression strategy and has nothing to do with SQL. If we're being generous he may have been talking about normalization, but no one I have ever met has confused the two terms (they are distinctly different from an engineering perspective).
There are degrees of normalization too, so it may make total sense to normalize 3NF (third normal form) rather than say 6NF depending on the data.
Everything they don't understand (which is nearly everything) is either God or fraud. Do with that information what you will.
If he doesn't think the government uses sql after having his goons break into multiple government servers he is an idiot.
If he is lying to cover his ass for fucking up so many things (the more likely explanation) then saying "he never used sql" is basically a dig at how technically inept he really is despite bragging about being a tech bro.
If SSNs are used as a primary key (a unique identifier for a row of data) then they'd have to be duplicated to be able to merge data together.
However, even if they aren't using ssn as an identifier as it's sensitive information. It's not uncommon to repeat data either for speed/performance sake, simplicity in table design, it's in a lookup table, or you have disconnected tables.
Having a value repeated doesn't tell you anything about fraud risk, efficency, or really anything. Using it as the primary piece of evidence for a claim isn't a strong arguement.
Dedup is about saving storage and has literally nothing to do with primary keys.
I'm still learning SQL, so if I'm out of line someone please correct me, but, the gist of it, is that SQL (Structured Query Language) is a language used in pretty much all relational databases, which with something like the Social Security database is almost guaranteed. Having duplicates of information in a relational database is not a sign of fraud, or anything shady going on.
When you're born, your name, along with your SSN and any other relevant info is put into the database, later in life, say you change your name, the original name, along with your SSN will stay there, and a new line in the database would be added with your new name, along with your SSN again (a duplicate) that way the database has a reference point between old and new name, and keeps all your information lined up between the two.
If you were to get rid of all of that duplicate information, anyone who's ever had a name change, been married, etc. It will cause chaos in the database, with hundreds of millions of entries that now have no relation to anything, and are now just basically dead ends.
Rows in a SQL table have a primary key which works as the unique identifier for that row. The primary key can be as simple as an incrementing number.
Might seem like a stupid question, but I'm in nostupidquestions sooo... Did Elon really do this tweet with the word "retard" in it? Obviously am on Lemmy so don't use Twitter.
Frankly the whole exchange sounds like Hollywood tech jargon.vaguely relevant words used in a not quite sensible way....
I saw a comment about this in the last couple of days that was really interesting and educational. Unfortunately I can't seem to find it again to link it, but the gist of it was that there would be two things wrong with using SSNs as primary keys in a SQL database:
Using SSNs as keys would violate both.
I went looking for best practices regarding SQL primary keys and found this really interesting post and discussion on Stack Overflow:
https://stackoverflow.com/questions/337503/whats-the-best-practice-for-primary-keys-in-tables
My first thought was that people's SSNs can and do change, and sometimes (rarely?) people may have more than one SSN. Like someone mentions in that link, human error would be another reason why you would not want to use external data and particularly SSNs as primary keys.
Musk is the walking Dunning-Krueger, he is too stupid to realize how terrible he sounds.
That dipshit does not even know how his dear friend at Oracle made tons of money in the past decades.