• barsquid@lemmy.world
    link
    fedilink
    arrow-up
    30
    ·
    3 months ago

    One of the reasons women will find this repugnant is because they didn’t normalize their tables. Should be boyfriend_id is null.

    • JackbyDev@programming.dev
      link
      fedilink
      English
      arrow-up
      10
      ·
      3 months ago

      Why is there a separate table for men and women in the first place? Shouldn’t there be a person table with a many to many relationship with itself (because polyamory exists)?

      • GBU_28@lemm.ee
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 months ago

        They allowed business logic to pollute the DB table, and “small waist” is a defined range in some confluence doc somewhere.

  • simple@lemm.ee
    link
    fedilink
    arrow-up
    5
    ·
    3 months ago

    I can already imagine a 40-something year old manager coming into work wearing this

  • MercuryGenisus@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    3 months ago

    I would reject this pull request. Why is the indenting all over the place? Why is your keyword capitalisation all over the place? WHY YELLOW?!

    Edit: the more I look at this the more it pisses me off. Wtf is going on with your kerning? Just random number and placement of spaces. Also, why is the table name in caps? Who does that? Select * is lazy. Do you really need every field about a girl? Really? Worst of all, not a limited request. I sware this is just the kind of thing that would return 30 million rows and brick the database for twenty seconds.