this post was submitted on 01 Jul 2024
331 points (92.3% liked)

LinkedinLunatics

3580 readers
17 users here now

A place to post ridiculous posts from linkedIn.com

(Full transparency.. a mod for this sub happens to work there.. but that doesn't influence his moderation or laughter at a lot of posts.)

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] JackbyDev@programming.dev 21 points 4 months ago (2 children)

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

[–] lennivelkant@discuss.tchncs.de 15 points 4 months ago (1 children)

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 points 4 months ago* (last edited 4 months ago) (1 children)

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 3 points 4 months ago (1 children)

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@sh.itjust.works 1 points 4 months ago

A fair point :D

[–] jol@discuss.tchncs.de 8 points 4 months ago (1 children)

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

[–] JackbyDev@programming.dev 2 points 4 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.