willya@lemmyf.uk to Programmer Humor@lemmy.mlEnglish · 10 months agoWhoopsthumbsnap.comimagemessage-square79fedilinkarrow-up11.19Karrow-down116
arrow-up11.18Karrow-down1imageWhoopsthumbsnap.comwillya@lemmyf.uk to Programmer Humor@lemmy.mlEnglish · 10 months agomessage-square79fedilink
minus-squaremrbaby@lemmy.worldlinkfedilinkarrow-up15·10 months agoAnd you can save a bunch of time by inlining all this into one query
minus-square342345@feddit.delinkfedilinkarrow-up5·edit-210 months agoWhy update before select? Shouldn’t it be the other way around? (I’m clueless. )
minus-squareJuja@lemmy.worldlinkfedilinkarrow-up9·10 months 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.
BEGIN
UPDATE
SELECT
COMMIT
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.
Be Safe! Be a BUSCer!