That’s (part of) why it should be a separate table to map the relation “Relationship”. People can have more than one (polyamory, infidelity), and you could track fields like the start, end, status (e.g. flirting, dating, committed, engaged, married, ended) in there.
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?!
Yesssss, bro 😀
You are now a Certified Rejector. Stay sharp, keep the wheel rolling.
I would like to subscribe to your newsletter.
Shouldn’t boyfriend be a reference to another table?
BF has no referential integrity
That’s (part of) why it should be a separate table to map the relation “Relationship”. People can have more than one (polyamory, infidelity), and you could track fields like the start, end, status (e.g. flirting, dating, committed, engaged, married, ended) in there.
You forgot some: Why is there no space after SELECT?
Why are boyfriend and smallwaist not questions like is_cute and is_crazy? Either all boils are with a verb or none.
Also why is smallwaist not in snake case? It should be small_waist (or better yet has_small_waist or even better waist = “small”)
Also also boyfriend should be null not false, this would solve multiple issues.
And finally the only positive thing is the * itself, because selecting only body would be even worse. 🤣