You're viewing a single thread.
Should be
age > (my_age / 2) +7
46 4 ReplyWhy would there be an age and my_age column on the table GIRLS?
20 0 ReplyGood 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.14 1 ReplyThank you. I assumed the reader would be educated enough to guess I meant a variable. But yeah, should used @my_age
1 1 ReplyPretty 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
2 0 ReplyA fair point :D
1 0 Reply
Because for each girl you meet, you might tell her a different age.
7 0 ReplyAh, 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.
2 0 Reply
Found the programmer thread that criticises the data model instead of the t-shirt
12 0 ReplyOr (my_age - 7) * 2 < age < (my_age / 2) +7`
8 3 ReplyUh, no no. The rule is "half my age plus seven". I've no idea what your other term is supposed to represent.
2 0 ReplyHe’s saying it goes both ways. The upper limit is a women who you would be half her age plus 7.
6 0 ReplyThis "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.
1 1 Reply