ERROR: permission denied for “GIRLS”
That is really a shirt for SQL enthusiast. Now, I want to rebuild the database and write some convention for writing request.
most infurating part of this is the mixing of cases
This is the most Indian shit I have seen this week.
and smallwaist = trueand itty_bitty_waist = true
and round_thing_in_your_face = true
is_sprung = true
It should be waist_size=1
SELECT * FROM “GIRLS” WHERE good = yes
🙄🤦♂️
Gonna sound racist but deal with it.
I constantly meet asian developers (Singapore , India, China, etc) with this edgelord personality. They come to American conferences and meetups, say some wild sexist shit, and someone has to politely let them know not to.
Some backtrack. Some apologize. Some literally freeze up and pretend like it didn’t happen.
We do still live in a bubble in the west. We’re fighting for equity across genders and race, while some parts of the world are still questioning if sexual harassment against women at work is really that big of a deal.
Many of my guy coworkers have been (and are) sort of misogynistic, and homophobic (I’m in India). It makes me really uncomfortable. Might start reporting people to HR one day.
Just get to know HR first. They might be mysogynists themselves (even if they are female).
That last part is a face saving culture reaction. If you’re feeling culturally sensitive the thing to do is just move on and see if they do it again.
Should be
age > (my_age / 2) +7Why would there be an age and my_age column on the table GIRLS?
Because for each girl you meet, you might tell her a different age.
Ah, but if we care at all about normalization and that’s calculatable from the other columns (it should be) then it shouldn’t be a column. Unless it’s expensive and this is a view, of course.
Good point.
Should be
age > (@my_age / 2) +7FTFOP - now my age is some value defined outside the immediate query.
More likely, the GIRLS would be a view of some table persons and you could query
my_agefrom that table too.Thank you. I assumed the reader would be educated enough to guess I meant a variable. But yeah, should used @my_age
Pretty sure “People who know enough about SQL to know about variables” is a subset of “People who know enough about SQL to be pedantic about it” :p
A fair point :D
Found the programmer thread that criticises the data model instead of the t-shirt
Or (my_age - 7) * 2 < age < (my_age / 2) +7`
Uh, no no. The rule is “half my age plus seven”. I’ve no idea what your other term is supposed to represent.
He’s saying it goes both ways. The upper limit is a women who you would be half her age plus 7.
This “rule” only works for a small set of ages from 14 ~ 30ish
If you are 14 then the range for “age” is 14 - 14
If you are 30 then the range for “age” is 22 - 46
If you are 40 then the range for “age” is 27 - 66At 30 the upper level is 16 years different; while it could work it is a big gap to bridge. It only gets worse the older you get.
deleted by creator
I would reject this pull request. Why is the indenting all over the place? Why is your keyword capitalisation all over the place? WHY YELLOW?!
Edit: the more I look at this the more it pisses me off. Wtf is going on with your kerning? Just random number and placement of spaces. Also, why is the table name in caps? Who does that? Select * is lazy. Do you really need every field about a girl? Really? Worst of all, not a limited request. I sware this is just the kind of thing that would return 30 million rows and brick the database for twenty seconds.
Yesssss, bro 😀
I would like to subscribe to your newsletter.
You are now a Certified Rejector. Stay sharp, keep the wheel rolling.
Shouldn’t boyfriend be a reference to another table?
BF has no referential integrity
That’s (part of) why it should be a separate table to map the relation “Relationship”. People can have more than one (polyamory, infidelity), and you could track fields like the start, end, status (e.g. flirting, dating, committed, engaged, married, ended) in there.
You forgot some: Why is there no space after SELECT?
Why are boyfriend and smallwaist not questions like is_cute and is_crazy? Either all boils are with a verb or none.
Also why is smallwaist not in snake case? It should be small_waist (or better yet has_small_waist or even better waist = “small”)
Also also boyfriend should be null not false, this would solve multiple issues.
And finally the only positive thing is the * itself, because selecting only body would be even worse. 🤣
Most SQL Dbs use bits, so it would be
WHERE field = 1The entire shirt caused me 4d6 psychological damage.
What is 4d as a numeric format prefix? I only know 0b and 0x. Is it some 4-24 system?
Here 4d6 is Dungeons and Dragons (etc.) shorthand for “roll four six-sided dice and add up the numbers”.
And what range can that sum cover?
It’s a random number based system with iterations at 4, 8, 10, 12, and because they want people to go insane, 20.
So everything can randomly be 1-20 at any point in time, and then sometimes you add them together and there’s maniacal laughter.
Aren’t there some d6 stuff too?
Oh how could I forget!
shitty taste <> “humor”
Who says programmers don’t have a sense of humor?
No one. It’s just what you pretend people say to make yourself feel like some kind of special exception.
me. I said it.
Well then you’re a mean old doody head.
The pallette for the syntax highlighter is horrid. Hardly readable.
But it is highlighter colour!
