andioop@programming.dev to Programmer Humor@programming.devEnglish · 8 months agoLittle Timmy Tablesprogramming.devimagemessage-square6linkfedilinkarrow-up13arrow-down10
arrow-up13arrow-down1imageLittle Timmy Tablesprogramming.devandioop@programming.dev to Programmer Humor@programming.devEnglish · 8 months agomessage-square6linkfedilink
minus-squareNullPointerException@lemmy.calinkfedilinkarrow-up0·8 months agoWhy would Santa need two separate tables for this?
minus-squarespiffpitt@lemmy.worldlinkfedilinkEnglisharrow-up2·8 months agodon’t underestimate database design in production environments
minus-squarephorq@lemmy.mllinkfedilinkarrow-up1·8 months agoExactly, Santa’s always watching and audit logs get complicated
minus-squareunalivejoy@lemmy.ziplinkfedilinkarrow-up1·8 months agoI would make two separate views. CREATE VIEW NiceList AS SELECT * FROM Children WHERE behavior = 'nice' AND parent.income > 40000; CREATE VIEW NaughtyList AS SELECT * FROM Children WHERE behavior = 'naughty';
Why would Santa need two separate tables for this?
don’t underestimate database design in production environments
Exactly, Santa’s always watching and audit logs get complicated
I would make two separate views.
CREATE VIEW NiceList AS SELECT * FROM Children WHERE behavior = 'nice' AND parent.income > 40000; CREATE VIEW NaughtyList AS SELECT * FROM Children WHERE behavior = 'naughty';