"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.

  • sim642@lemm.ee
    11·
    1 year ago

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

    • elvith@feddit.de
      20·
      1 year 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

      • ReluctantMuskrat@lemmy.world
        3·
        1 year ago

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

        Exactly. Restores often result in system downtime and may take hours and involve lots of people. The backup might not have the latest data either, and restoring to a single table you screwed up may not be feasible or come with risk of inconsistent data being loaded. Even if you just created the backup before your statement, what about the transaction coming in while you’re working and after you realize your error? Can you restore without impacting those?

        You want to avoid all of that if possible. If you’re mucking with data that you’ll have to restore if you mess up, production or not, you should be working with an open transaction. As you said… if you see an unexpected number of rows updated, easy to rollback. And you can run queries after you’ve modified the data to confirm your table contains data as you expect now. Something surprising… rollback and re-think what you’re doing. Better to never touch a backup and not shoot yourself in the foot and your data in the face all due to a stupid, easily preventable mistake.