• lennivelkant@discuss.tchncs.de
        0·
        5 months ago

        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@sh.itjust.works
          0·
          5 months ago

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

          • lennivelkant@discuss.tchncs.de
            0·
            5 months ago

            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

        • JackbyDev@programming.devEnglish
          0·
          5 months ago

          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.

      • fibojoly@sh.itjust.works
        0·
        5 months ago

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

        • ji17br@lemmy.ml
          0·
          5 months ago

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

          • absGeekNZ@lemmy.nzEnglish
            0·
            5 months ago

            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.