Drew@sopuli.xyz to LinkedinLunatics@sh.itjust.works · 3 days agoBelchingsopuli.xyzimagemessage-square74fedilinkarrow-up1324arrow-down130
arrow-up1294arrow-down1imageBelchingsopuli.xyzDrew@sopuli.xyz to LinkedinLunatics@sh.itjust.works · 3 days agomessage-square74fedilink
minus-squarefibojoly@sh.itjust.workslinkfedilinkarrow-up41arrow-down4·edit-22 days agoShould be age > (my_age / 2) +7
minus-squareolafurp@lemmy.worldlinkfedilinkarrow-up11·2 days agoFound the programmer thread that criticises the data model instead of the t-shirt
minus-squareJackbyDev@programming.devlinkfedilinkEnglisharrow-up19·2 days agoWhy would there be an age and my_age column on the table GIRLS?
minus-squarelennivelkant@discuss.tchncs.delinkfedilinkarrow-up12arrow-down1·2 days agoGood 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.
minus-squarefibojoly@sh.itjust.workslinkfedilinkarrow-up1arrow-down1·edit-22 days agoThank you. I assumed the reader would be educated enough to guess I meant a variable. But yeah, should used @my_age
minus-squarejol@discuss.tchncs.delinkfedilinkarrow-up6·2 days agoBecause for each girl you meet, you might tell her a different age.
minus-squareJackbyDev@programming.devlinkfedilinkEnglisharrow-up1·2 days agoAh, 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.
minus-squareGladaed@feddit.orglinkfedilinkarrow-up7arrow-down3·2 days agoOr (my_age - 7) * 2 < age < (my_age / 2) +7`
minus-squarefibojoly@sh.itjust.workslinkfedilinkarrow-up2·2 days agoUh, no no. The rule is “half my age plus seven”. I’ve no idea what your other term is supposed to represent.
minus-squareji17br@lemmy.mllinkfedilinkarrow-up6·2 days agoHe’s saying it goes both ways. The upper limit is a women who you would be half her age plus 7.
minus-squareabsGeekNZ@lemmy.nzlinkfedilinkEnglisharrow-up1arrow-down1·2 days agoThis “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.
Should be
age > (my_age / 2) +7Found the programmer thread that criticises the data model instead of the t-shirt
Why would there be an age and my_age column on the table GIRLS?
Good point.
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_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
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.
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.
deleted by creator