this post was submitted on 11 Oct 2023
0 points (NaN% liked)

Programming

16977 readers
165 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
0
I accidentally removed the WHERE clause from my SQL query in a personal tool. Every row is now the same. I overwrote 206,000+ rows. I have no backup, I am stupid. (lemmy.world)
submitted 11 months ago* (last edited 11 months ago) by drekly@lemmy.world to c/programming@programming.dev
13 comments fedilink hide all child comments
 

"UPDATE table_name SET w = $1, x = $2, z = $4 WHERE y = $3 RETURNING *",

does not do the same as

"UPDATE table_name SET w = $1, x = $2, y = $3, z = $4 RETURNING *",

It's 2 am and my mind blanked out the WHERE, and just wanted the numbers neatly in order of 1234.

idiot.

FML.

top 13 comments
sorted by: hot top controversial new old
[–] gatelike@feddit.de 0 points 11 months ago

SQL scouts credo: I will never use indexes, I will always use column names.

[–] jjjalljs@ttrpg.network 0 points 11 months ago (1 children)

You all run queries against production from your local? Insanity.

[–] elvith@feddit.de 0 points 11 months ago

Everyone has a production system. Some may even have a separate testing environment!

[–] AlphaOmega@lemmy.world 0 points 11 months ago* (last edited 11 months ago) (1 children)

This is a hard lesson to learn. From now on, my guess is you will have dozens of backups.

[–] ReluctantMuskrat@lemmy.world 0 points 11 months ago (1 children)

And always use a transaction so you're required to commit to make it permanent. See an unexpected result? Rollback.

[–] sim642@lemm.ee 0 points 11 months ago (1 children)

Transactions aren't backups. You can just as easily commit before fully realizing it. Backups, backups, backups.

[–] elvith@feddit.de 0 points 11 months ago

Yes, but

  1. Begin transaction
  2. Update table set x='oopsie'
  3. Sees 42096 rows affected
  4. Rollback

Can prevent a restore, whereas doing the update with auto commit guarantees a restore on (mostly) every error you make

[–] MonkCanatella@sh.itjust.works 0 points 11 months ago* (last edited 11 months ago) (1 children)

this folks, is why you don't raw dog sql like some caveman

[–] olafurp@lemmy.world 0 points 11 months ago (1 children)

Raw dog is the fastest way to finish a task.

  • productivity
  • risk

It's a trade-off

[–] Sharpiemarker@feddit.de 0 points 11 months ago (1 children)

There's no way you're endorsing the way OP handled their data right?

[–] olafurp@lemmy.world 0 points 11 months ago* (last edited 11 months ago) (1 children)

No, but people are sometimes forced to do these things because of pressure from management and/or lack of infrastructure to do it in any other way.

Definitely don't endorse it but I have done it. Think of a "Everything is down" situation that can be fixed in 1 minute with SQL.

[–] Sharpiemarker@feddit.de 0 points 11 months ago

Got it. I'm with you.

[–] Bazz@feddit.de 0 points 11 months ago

I don't know if it makes you feel better but Tom Scott had a similar experience: https://youtu.be/X6NJkWbM1xk