rr7@lemmy.world to Programmer Humor@lemmy.mlEnglish · 1 year agoI think I leave early todaylemmy.worldimagemessage-square17fedilinkarrow-up1302arrow-down12
arrow-up1300arrow-down1imageI think I leave early todaylemmy.worldrr7@lemmy.world to Programmer Humor@lemmy.mlEnglish · 1 year agomessage-square17fedilink
minus-squarecashews_win@lemmy.worldlinkfedilinkEnglisharrow-up12·1 year ago“I didn’t put a WHERE clause in that DELETE statement”
minus-squareEmasXP@lemmy.worldlinkfedilinkEnglisharrow-up5·1 year agoAs a side note, DBeaver actually asks for confirmation if it thinks you are about to do something wonky. I think it’s quite telling just how common this mistake is. We’ve all been there
minus-squaremarcos@lemmy.worldlinkfedilinkEnglisharrow-up4·1 year agoUpdate and delete should require a where clause. You can always use true or 1 = 1, the gain from omitting it is minimal. The fact that no DBMS ever decided to implement this, not even as an option is quite distressing.
“I didn’t put a WHERE clause in that DELETE statement”
As a side note, DBeaver actually asks for confirmation if it thinks you are about to do something wonky. I think it’s quite telling just how common this mistake is. We’ve all been there
Update and delete should require a where clause. You can always use true or 1 = 1, the gain from omitting it is minimal.
The fact that no DBMS ever decided to implement this, not even as an option is quite distressing.