@willya@lemmyf.uk to Programmer Humor@lemmy.mlEnglish • 2 years agoWhoopsthumbsnap.comimagemessage-square79fedilinkarrow-up11.33Karrow-down117
arrow-up11.31Karrow-down1imageWhoopsthumbsnap.com@willya@lemmyf.uk to Programmer Humor@lemmy.mlEnglish • 2 years agomessage-square79fedilink
minus-square@mrbaby@lemmy.worldlinkfedilink15•2 years agoAnd you can save a bunch of time by inlining all this into one query
minus-square@342345@feddit.delinkfedilink5•edit-22 years agoWhy update before select? Shouldn’t it be the other way around? (I’m clueless. )
minus-squareJujalinkfedilink9•2 years agoThe select after the update is to check if the update went through properly. You can have more selects before the update if you wanted to.
deleted by creator
And you can save a bunch of time by inlining all this into one query
Why update before select? Shouldn’t it be the other way around? (I’m clueless. )
The select after the update is to check if the update went through properly. You can have more selects before the update if you wanted to.
Ah. It makes sense now. Thanks.
The four horsemen of the datapocalypse
deleted by creator