You are only browsing one thread in the discussion! All comments are available on the post page.

Return

fibojoly ,

Should be age > (my_age / 2) +7

JackbyDev ,

Why would there be an age and my_age column on the table GIRLS?

lennivelkant ,

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.

fibojoly ,

Thank you. I assumed the reader would be educated enough to guess I meant a variable.
But yeah, should used @my_age

lennivelkant ,

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

fibojoly ,

A fair point :D

jol ,

Because for each girl you meet, you might tell her a different age.

JackbyDev ,

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.

Gladaed ,

Or (my_age - 7) * 2 < age < (my_age / 2) +7`

fibojoly ,

Uh, no no. The rule is "half my age plus seven". I've no idea what your other term is supposed to represent.

ji17br ,

He’s saying it goes both ways. The upper limit is a women who you would be half her age plus 7.

absGeekNZ ,
@absGeekNZ@lemmy.nz avatar

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.

olafurp ,

Found the programmer thread that criticises the data model instead of the t-shirt

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • [email protected]
  • All magazines
    •