willya@lemmyf.uk to Programmer Humor@lemmy.mlEnglish · 1 year agoWhoopsthumbsnap.comimagemessage-square110fedilinkarrow-up11.32Karrow-down117
arrow-up11.3Karrow-down1imageWhoopsthumbsnap.comwillya@lemmyf.uk to Programmer Humor@lemmy.mlEnglish · 1 year agomessage-square110fedilink
minus-squaremrbaby@lemmy.worldlinkfedilinkarrow-up15·1 year agoAnd you can save a bunch of time by inlining all this into one query
minus-squareAgent641@lemmy.worldlinkfedilinkarrow-up5·1 year agoThe four horsemen of the datapocalypse
minus-square342345@feddit.delinkfedilinkarrow-up5·edit-21 year agoWhy update before select? Shouldn’t it be the other way around? (I’m clueless. )
minus-squareJuja@lemmy.worldlinkfedilinkarrow-up9·1 year 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
The four horsemen of the datapocalypse
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!