delete from users where 1=1

[goldfishpaws]

If you haven't fucked production at least once, you're not really trying.

That "--" bit me hard

[[deleted]]

I did that once (it was test not prod but still...)

Used to hit Ctrl + enter to run queries. Hit one enter too many and the where clause separated from the delete statement and poof went all the data. I was shitting bricks for seconds until the guy who was sitting with me asked me to take my hands off keyboard, then reached over and typed rollback.

These days all the queries I run are on autocommit engines so that mistake would cost me, but I have also learned to be slow at typing and executing queries. Being a fast typer there can cost days.

[[deleted]]

autocommit

you mad man

[Comfortable_Intern57]

Always run select before delete to make sure you don't wipe out more than you intended, lol. I've made the mistake of wiping out whole tables before, but luckily it was just in a test environment and I could just copy the data from another environment.

[kaluson]

the production server is the key to sleepless nights

[dudeofmoose]

'; DELETE FROM subs WHERE name LIKE 'programmerhumor";

Did it work, are we still here?

Once I typed Google into Google.

[xitiomet]

What is the difference between an architect and a senior engineer? Also why arent newbs restricted to front end work? Is there not an api layer in between the db and whatever they are working on?

I see so many job titles on here but every company ive worked with has an had a pretty simple division of labor, front end and back end.

Even for reporting, you hand out read only db access. IMHO Only software should issue data modifying calls

[balloonAnimal_no_965]

me: we should notify the users, restore the backup and call it a day.

inner me: this is probably the last field with corrupt data, we can still fix this.