Drew to [email protected] • 3 days agoBelchingsopuli.xyzimagemessage-square55fedilinkarrow-up1280arrow-down123
arrow-up1257arrow-down1imageBelchingsopuli.xyzDrew to [email protected] • 3 days agomessage-square55fedilink
minus-squareJackbyDevlinkEnglish14•2 days agoWhy would there be an age and my_age column on the table GIRLS?
minus-square@[email protected]linkfedilink7•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-square@[email protected]linkfedilink0•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-square@[email protected]linkfedilink2•2 days agoBecause for each girl you meet, you might tell her a different age.
minus-squareJackbyDevlinkEnglish1•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.
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.