SELECT * FROM "GIRLS" WHERE good = yes
LinkedinLunatics
A place to post ridiculous posts from linkedIn.com
(Full transparency.. a mod for this sub happens to work there.. but that doesn't influence his moderation or laughter at a lot of posts.)
That is really a shirt for SQL enthusiast. Now, I want to rebuild the database and write some convention for writing request.
This is the most Indian shit I have seen this week.
most infurating part of this is the mixing of cases
Big pp energy over here
This is not funny and any man wearing this would probably not pass a similar test using any woman's criteria. If I saw someone wearing this my first thought would certainly not be "hey this is a guy with a great sense of humor and I would like to hang with him!".
~~and smallwaist = true~~
and itty_bitty_waist = true
and round_thing_in_your_face = true
is_sprung = true
It should be waist_size=1
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.
ERROR: permission denied for "GIRLS"
Should be age > (my_age / 2) +7
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 - 66
At 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.
Why 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) +7
FTFOP - 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_age
from 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