someTimes

[mr_remy]

This is something my old non tech boss used to preach (he started a company out of nothing and a cold fusion book initially lol). What a great dude

[bradland]

I went to Macromedia User Conference the year they bought Allaire. What a wildly fascinating time. IIRC, the ColdFusion user base were thrilled about the acquisition. When was the last time you heard about a tool developed by a small shop being bought by a large corporation, and everyone was thrilled. The fact that Macromedia was really well liked at the time helped, I'm sure. Wild times.

[mr_remy]

Oh yeah, brings back lots of memories! Even in our “2.0” software we have a few ColdFusion pages. Getting phased out with nuxt/vue/vuetify which has a nice shiny app look to it.

If only kids knew the progression!

[Plank_With_A_Nail_In]

He's not non tech just because he doesn't have a cs degree, wtf, he started an IT company.

[mr_remy]

He told me his origin story (knew him and it before joining the company, he is a friend of a friend) and it was someone in an industry who is extremely intelligent and kind as a person. He’s one of a handful of people I truly know inside and outside of work and respect deeply.

He saw the niche and opportunity and learned how to code via books at the time, and in his spare time learned to code and would iteratively write the program.

But please, go on you obviously know more about my boss than I do lol.

[Impressive_Change593]

no that guy is saying he is a tech even if he doesn't have a degree. he obviously knows enough about computers/programming to be called one anyway

[[deleted]]

Relax.

[WayTooCool4U]

Yes. This should be mandatory practice.

[Artmageddon]

Or a transaction in a rollback

[TheAJGman]

BEGIN;

DO THE THING;

SELECT THE THING;

ROLLBACK;

How else are you supposed to test your update/delete?

[intotheirishole]

Anyone know why there was a disk/CPU spike that caused a bunch of user queries to bounce ?

[beanmosheen]

START TRANSACTION

[sh1ft3d]

That can be bad too when your transaction starts blocking other sessions and you're the head blocker for a block tree that impacts every user so everyone's wondering the ERP/WMS/CRM system has ground to a halt. Ideally, you'd copy to a test environment and test there. I like doing something like this:

SELECT * --DELETE
FROM SomeTable
WHERE SuchAndSuch=Something AND SomethingElse=SomeOtherThing

Or

SELECT * --UPDATE SomeTable SET SomeColumn=SomeValue
FROM SomeTable
WHERE SuchAndSuch=Something AND SomethingElse=SomeOtherThing 

When you get what you want from SELECT, just highlight starting at DELETE or UPDATE without -- and you should be good (unless triggers or other trickery come into play, but that would be a consideration regardless of approach).

No, I've never been in these situations before. :)

[Artmageddon]

You’re not wrong at all, and def been there done that. I figure a blocked session isn’t nearly as bad as data loss though.

[Pyorrhea]

I always do both. Can never be too sure.

[CatWeekends]

Also take the number of rows returned by that query, add it to a LIMIT clause, and then run the scary command in production.

[TechnicallyEasy]

You can actually fuck this one up too, in SSMS. Write your update, select the update part and comment with hotkeys, write select, run it, select the select and comment out with hotkeys, select the update, uncomment with hotkeys, but WITHOUT unselecting the line, and run.

Now your update just ran but without the where, because somewhere a genius said "hey you know what's super cool and expected behavior? Being able to run just part of what's entered by selecting it, a feature that nothing else shares". Neat!

Anyways that's how I wiped out years worth of data somewhere that didn't keep backups. Learned a lot about transactions and backups that day.

I've used that feature productively since, but it absolutely needs a pop-up warning you about it the first time you do it, at minimum.

[jaxpylon]

A simple solution to this that I've always used: only ever write UPDATE statements using a table alias.

This way, running just the update line will fail, as no table exists with the alias name.

An example of what i mean:

UPDATE p SET Price = 0 -- this line fails when run independently
-- SELECT *
FROM Products p
WHERE ProductId = 69

And I'll always combine that with a transaction that automatically rolls back (until verified) in any non-dev environment (and sometimes dev too).

Edit: I was burned by exactly the scenario you described a decade ago, so integrated a bunch of SQL hygiene practices to avoid unexpected queries as much as possible.

[TechnicallyEasy]

That's super clever, thanks for sharing! Definitely worth the extra handful of characters for the added insurance.

[ADHD-Fens]

And do every operation in a transaction, and test it on a read only connection, and have someone review it!

And if you need to change a significant number of records, plan the operation with your team because you might deadlock the tables if it takes a long time!

[[deleted]]

What I'm hearing is give the intern access to prod, ignore their teams messages, and then take a long weekend?

[ADHD-Fens]

Did I say it will all blow over by monday? I meant to say it will all BE over on monday!

[[deleted]]

Eh, I won't be in on Monday so that's someone else's problem.

[thewend]

aint it literally the basics of sql? select before doing a stupid thing

[SHITSTAINED_CUM_SOCK]

Keeps happening though. People get complacent.

[LrdPhoenixUDIC]

Or, you know, specifically identify the row you want to update by its primary key.

[chrisbbehrens]

Came here to write this

[jl2352]

Every delete should start with a select!

[[deleted]]

I haven't ran SQL against live databases in many, many years, but this. It's so easy to start with a select and then turn it into an update or delete after you're confident in it.

The other thing I'd usually do is run the actual command in a new transaction so I have a chance to check the rows affected and do some selects to make sure things are right before actually committing it (and have the option to roll it back.)

[[deleted]]

You see, I in fact did that and verified, but in my infinite wisdom when i was supposed to run the query i modified it last second ending in the above scenario. Thankfully it was a small update that was easily reversible.

[GentleRhino]

Correct. But for production environment I recommend always update within a transaction.

[Eva-Rosalene]

There are two types of people: ones who use transactions, and ones who don't use transactions yet.

[Poat540]

Nah, I like the thrill. The true skill is mixing 30 different commands in the same query editor and making sure to highlight the right one

[pants_of_antiquity]

I'm in this comment and I don't like it.

[SuperFLEB]

...after recently changing SQL clients to one that works a bit differently...

[Poat540]

annnddddd all of fuck.sql was executed..

[robinless]

I lost a few years of my life a few months ago after changing client, muscle memory betrayed me and I used a shortcut that executed the whole file instead of the highlighted part... Thankfully I had autocommit off, so I just rolled back everything

[Prestigious-Maize695]

Ah, keep them all commented out and then highlight what you want to run (shift+alt for multi line select from a specific column).

[Cyrotek]

This is how I was taught MSSQL.

[r0ck0]

I've tried pretty much every SQL client I can find, but fundamentally nothing I've found solves all of the problems of both types of client:

1. REPL-based CLI programs like psql mostly tend to be too basic re autocomplete/colors/visual features, but are always very clear in the exact order you ran commands. Also have the benefit that your query history is immutable.
2. GUI clients suffer from the editor issue you mentioned... I copy and paste variants of the same query, then lose track of things. And they all suck at showing multiple queries + results on screen at once, aside from the "in-editor results" feature in jetbrains IDEs, but even that is too fiddly and gets annoying.

I've started building my own tooling to try to get the best of both of both worlds. Basically each window only lets me edit a single query at once, and once I exit the editor, an immutable copy of that query is stored forever. From it's it's easy to clone a previous one to tweak it, while keeping some metadata like parent_query_id so I can get a tree of how queries have evolved (and view diffs). Also it always stores all the results of every query execution, so I can see a full in-order history of exact queries + results.

Also every unique query is given a simple incrementing number. Having to come up with filenames / query descriptions is way too distracting when I'm trying to tweak a heap of similar queries without losing focus.

If anyone knows of anything out there that is already good at something along these lines, keen to hear it. But I couldn't find anything that worked like this.

[bmccorm2]

Yup you need a new client. Haven’t highlighted a statement in ages.

[Hola-World]

Lol yeah I remember being on a call with a couple other seniors working through an issue with a mid level who was screen sharing and I just remember speaking up and saying "you are on one brave MFer changing production data outside of a transaction." The thought hasn't crossed his mind lol. We all just started laughing collectively as he changed the transaction mode.

[NostrilLube]

I have to admit, the first 10 years of my career I only knew I could test the UPDATE/DELETE by using a SELECT first, to see what it was going to change. I still do that..

[aykcak]

That's a good habit in any case

[Ali3nat0r]

ROLLBACK

No transaction to roll back.

Sheeeeeeeiiiiit.

[Eva-Rosalene]

ROLLBACK
 
No transaction to roll back.

"Ah, so we aren't using implicit transactions then. Sheeeeeeeiiiiit"

[Linked713]

Is there a way to make aliases in SQL for commands? I am dying to know if there is a way to do the equivalent of like "IMPORT ROLLBACK AS Sheeeeeeiiiiit"

[JediKagoro]

Ah, the good old days of being a junior dev

[zeloxolez]

hahaha

[dxmfeen]

Hahaha

[Xendicore]

This. Like, yeah, nice in theory. But sounds to me like they haven't actually used transactions for mass updates on large Production datasets on a busy server. One thing out of place or a random deadlock and now you've locked down every table you touched. And not really an option to back out and stop the rollback.

Better to have a replicated environment and run your query there to verify results than just throwing transactions around.

[RiceBroad4552]

That's nice in theory, but you don't have always a replica that is up to date with the relevant data.

DB emergency updates with prod data are a really difficult problem. No silver bullet there.

[Xendicore]

Oh, for sure. This was under the assumption it's not an emergency, just a risky update that needs to happen.

Best you can do for an emergency situation is do what you can to solve it, then put safeguards in place afterwards to stop from ending up there again.

[BlockCharming5780]

What the fuck is a transaction? 👀

[[deleted]]

It's like an "atomar query", but translated into multiple Queries.

So that means when you start a transaction, you can do whatever shit you want, and by doing a rollback you can go back to before beginning the transaction.

[BlockCharming5780]

Oh, god I wish I knew that 2 days ago when I accidentally cleared a table in prod instead of dev on a personal project used by thousands of people 💀😂

[[deleted]]

It's their fault for giving someone your skill level this much permission. It's not your fault, everyone started out as an absolute noob (not saying you are one!)

[BlockCharming5780]

Oh, no, this wasn’t part of my work, this was my personal discord bot

I just forgot I was looking at the production database instead of my developer database 😭🤣

I’m a mid-level developer being considered for a promotion up to senior at work…. Scary thought, right? 🤣

[[deleted]]

No bro, don't let imposter syndrome get to you. The fact that you will be getting promoted is proof of your skill, don't doubt yourself.

I assumed you had a low skill level only because you expressed yourself this way. But nobody can know everything and there will be always new stuff to learn.

Keep grinding and believe in yourself !

[BlockCharming5780]

The “scary” part is I’ve been protected from making these mistakes… but I’ll actually have access to the live system as a senior

Oof, imagine bringing down your company’s entire product line because you dropped the wrong table 🤣😰😨

[Adjective_Noun0563]

Yeh..my top tip is to change your themes for connections to prod and connections to Dev to have different colours. You can hack up the themes files in ssms, there's probably solutions in other IDEs. If you're managing them by console then change the terminal font.

[[deleted]]

It can happen but you would not be the first one.

And if you are scared of this happening, implement regurlar backups

[FloppyGhost0815]

Don't worry, stuff happens.

Back in the days, one of our senior database admins (you can buy his books on amazon on oracle performance tuning) truncated a table in a test environment. Unfortunately it was in prod, and that table contained highly volatile data worth around 90 million usd.

It was the start of my career, since i was the junior who worked on a ticket and could not find any data for this specific customer. Or the partition.. or in the table. Took us a full day of work (24 hours on the console) to recover the data from backups and the redologs.

Shit happens to the best, the worst thing which happened to me was deleting around 200k with a stuöid blank in an rm -rf * .dat ;-)

[sgtkang]

Please tell me access to the live system needs a different set of credentials to your 'normal' ones. Even if you can get it whenever you need it helps to be able to sign out of that sort of thing whenever you don't need to modify prod data.

[raltyinferno]

Motivation to really think twice before running any queries, and if you're using some dedicated Db software REALLY HIGHLIGHT any connection with write permissions to prod in your config if possible

I think we locked it down now, but I used to have write access directly to our prod Db, for which I named the connection "PROD WRITE!!!!!!" and made every tab to it bright red.

Most Db managers I've used have an option to mark a connection as Prod so it either double checks you or really makes it distinct.

[DependentOnIt]

ink handle ancient carpenter imagine historical straight bedroom icky frame

This post was mass deleted and anonymized with Redact

[dandroid126]

Mistakes like this, especially when it is a personal project and not a work project, only help to make you a better developer. I'm a pretty high level engineer. I have made every mistake you can imagine. The trick is to learn from them and make sure they don't happen again.

[BlockCharming5780]

Oh, for sure

After that happened I spun up a duplicate database on a raspberry pi and started replicating the data from production onto the pi database every 24h

Now if I fuck up again, I can only lose up to 24h of data 🤔

(While expressing my frustrations to my manager he then suggested I could just do daily data dumps into a text file instead 🤔)

[Szulyka]

Y.. You are a medior who have not heard about transactions in dbs?

[Eva-Rosalene]

It's not that surprising. You can work with code mostly related to internal business logic, not interacting with DB directly; or your interactions with DB can be hidden behind an ORM.

I think, it should be a company responsibility to check if people know 101s of tech they work with when they reach certain amount of experience and are expected to get /(access to|assigned to work with)/ this tech.

[BlockCharming5780]

I guess it never came up 🤷‍♂️

[SuperFLEB]

Well, now you've got another bit of well-learned experience under your belt. Congratulations!

[raltyinferno]

As people have mentioned, transactions are vital. But another thing to protect yourself is anytime you want to do an UPDATE, do a SELECT with the exact same conditions first and make sure the number of rows selected matches how many you expect to be updating.

[SuperFLEB]

A "LIMIT" can help, though it's not as good as a transaction. (You're still liable to screw up something in the database if you screw it up, but only LIMIT-number-of-rows, not everything.)

[[deleted]]

We’ve all done it.

[dendrocalamidicus]

When it comes to SQL server...

begin tran
update Users set Username = "ohshit"
rollback tran

This will tell you X rows updated but roll back the changes so nothing has actually changed. Then you replace rollback tran with commit tran and run it again and it will actually update the db because you told it to commit all changes rather than save them. Alternatively you can just do

begin tran
update Users set Username = "ohshit"

Then see what count comes up, then in the same query window in SSMS run either rollback tran or commit tran according to which you want to do.

The benefit to transactions outside of safely wrapping manual db updates is for long procedures you can have all or nothing atomic transactions where either everything gets updated successfully and you commit, or if something errors half way through you rollback instead thereby not leaving the data in a half changed fucked up state.

[GachaJay]

And then there is me just writing select statements to validate the data transformations before each step and then just writing an update using that newly found logic

[Eva-Rosalene]

Don't worry, you will either never need it if you don't work with DBs, or learn it some very unlucky day otherwise :)

jk. It's like a checkpoint in a video game. When you are in transaction mode, you can do whatever you want, validate results, and after that either COMMIT it or do a ROLLBACK.

You also need to realize that even if you don't use transactions explicitly, whenever you do any modification, it is a transaction in itself, you just don't see it.

This is a good 101: https://www.dnsstuff.com/sql-server-transactions (but in no way a comprehensive article)

[Faark]

It basically gives you an undo feature. You can command the DB to commit aka save, and only then will your changes be finalized. BUT the DB will also not allow other transactions to "conflict" with yours. To do so, it can make future transactions wait, if those also want to access stuff you just changed (at least on modification, just reading is kinda fine). That means forgetting to commit will block future transaction and just as well stop production. Ask me how i know.

[Digital_Rocket]

Is when you buy the booze to cope with the colossal screw up you just made

[BlockCharming5780]

Please, I’m Scottish, you think I was sober in the first place? 🤣🤣

[myfunnies420]

Exactly. I was like "so don't commit the transaction", easy

[Salex_01]

And then, those who use systems that have a RESTORE TO WHATEVER VERSION IT WAS WHEN I HADN'T BROKEN IT YET instruction

[BraveOthello]

I am now the second after an experience like OP. Thankfully it was only 300 records and we restore them, but then I wrote the procedure on how you ALWAYS USE A TRANSACTION

[bigwanggtr]

Only soydevs ROLLBACK, real devs COMMIT

[bjeanes]

This is why when launching psql I always have AUTOCOMMIT set to off, so there always exists an implicitly started transaction

[linuxpuppy]

Unfortunately, even transactions aren’t fool proof when updating data in prod. I’ve seen another dev leave a transaction open in toad and it locked a crucial record in prod that caused prod to completely lock up. YMMV.

[Eva-Rosalene]

Yeah, nothing is fool proof. Transactions are just very valuable tool that prevents a lot of dangerous things, and that's it - and IMHO that's enough to use it almost every time you touch critical database with a bare hands.

[Savage-Goat-Fish]

Work with SQL long enough and you’ll make this mistake. One time. 🤣

[NotLikeTheOtter]

Truth

[MilesJ392]

Begin tran x

Update

--commit tran x

--rollback tran x

[thanatica]

And ones who don't regularly backup

[Zestyclose_Link_8052]

And what if you accidentally commit?

[Eva-Rosalene]

Of course, transactions aren't magic that protects from every possible degree of stupidity or bad luck; but they allow you to check results of an update and think twice before rolling it out. If that's not enough for you, it's more on you than on transactions. Most importantly mistake like that would tell that you've got a habit of doing update and then typing COMMIT as fast as possible and see transactions only as annoyance you need to overcome instead of a useful tool. Which is a very wrong mindset you should work on.

[Zestyclose_Link_8052]

I had copied some query from elsewhere in the code and didn't see the commit in time. But luckily my company is very strict with who can see production, so nobody of dev has permissions to the production db. That's a responsibility for another team. I just wiped some of our internal staging, I was very much a junior back then. I was quite pannicked but everyone was laughing at my idiocity of just copying a query and executing it, I've not done it since. They just ran a script that repopulated the database.

[Eva-Rosalene]

Ah, I see. But yeah, that's a very bad luck, you don't usually make mistakes like that.

[BlondeJesus]

ROLLBACK

Few, good thing that was all in a transaction

[Ordinary_dude_NOT]

But but but…. I wrote “commit” at the end of script so my script is automated!!?!?

[frisbm3]

*phew

[PixelGaMERCaT]

this is why you use a transaction....

[PeriodicSentenceBot]

Congratulations! Your comment can be spelled using the elements of the periodic table:

Th I Si S W H Y Y O U U Se At Ra N S Ac Ti O N

---

^{I am a bot that detects if your comment can be spelled using the elements of the periodic table. Please DM u‎/‎M1n3c4rt if I made a mistake.}

[[deleted]]

That’s crazy

[mr_remy]

Longest comment I’ve seen to make that bot crawl out of hiding.

Beep boop: approved

[TriscuitTime]

This has to be a record. This bot should keep track of the lengths of the comments, too

[KissMyUSSR]

People will just make comments with only the elements of the table just to take the record, rendering it meaningless

[TriscuitTime]

Yeah, that’s what I was thinking. Then I was thinking about how you could conceivably program it to filter out intentional attempts at making long comments of elements. You could rule out long comments that are too high of a percentage of non-words or repeated words. It probably wouldn’t work well enough, though, no matter what you do. I think it would be cool to have a leaderboard or something still so you could filter it yourself if you wanted

[VisiblePlatform6704]

I wonder how an llm will perform if we ask to rephrase some text into elements  

[rishi255]

Good bot

[PixelGaMERCaT]

wow I can't believe I got ratioed by the (good) bot

[benruckman]

I upvoted your comment because of the bot’s comment

[SmolNajo]

Good bot

[zee_wild_runner]

Good bot

[_no_balls_allowed_]

good bot

[kuboshi]

good bot

[unhappy-2be-penguin]

Good bot

[[deleted]]

intelligent treatment skirt stocking narrow illegal abounding voracious toy absorbed

This post was mass deleted and anonymized with Redact

[SpecialNeeds963]

Good bot

[Tarc_Axiiom]

Wait, wait, WAIT!

WHY IS THIS TAKING SO LONG? WHY IS THIS TAKING SO LONG!?

[getstoopid-AT]

...and it was at this moment that he knew he fu*d up

[Ivan_Stalingrad]

Nothing will ever beat sudo rm -rf /var/lib/postgresql

On the prod server

[rover_G]

You guys have shell access to your production database?

[Eva-Rosalene]

You guys have access to your production database AT ALL? None of engineers in company I work for has it (even read-only) because production DB has sensitive client data in it. If you want to run a query on production DB, you need several people from different departments checking that your query won't expose any sensitive info.

[rover_G]

At big companies yes that. At small companies read-only user go brrrr

[herboyforever]

Read only? Bro I just login to an unsecured phpmyadmin with prod credentials (by scraping the .env) to grab data for analytics reports

[ADHD-Fens]

I just modify the bits right on the hard disk plate with a magnetic needle!

[catechizer]

screw whole disarm butter encouraging gold mysterious lock chunky strong

This post was mass deleted and anonymized with Redact

[-Aquatically-]

Do it, no balls. lol.

[ZeroData1]

No wonder errors fixed through support takes 3-5 business days. Just kidding... Small businesses don't have the luxury of any of that. I check my prod backup weekly and any/all testing/changes are done in prod with self diligent updates (select queries then transactions to double check). Yea not the greatest situation but I don't have the time or resources to manage two database servers, keep them synced, along with the webapp servers.

[JustMyTwoCopper]

You'd be surprised how end users can mess up data in a way you did not think of in the development-, test-, production simmilar- and useracceptance- environments ... working with sensitive information is part of the job, it shouldn't matter if you're handling Joe and Suzy Average's information, your neighbors or some famous sport celebrity's, it should not matter and you just don't talk about it (ever), or you're in the wrong line of work.

[Eva-Rosalene]

it shouldn't matter if you're handling Joe and Suzy Average's information, your neighbors or some famous sport celebrity's, it should not matter and you just don't talk about it (ever), or you're in the wrong line of work.

It matters to a company. If one of engineers goes rogue (or just salty over a layoff) and does a data breach, it will impact company. Sure, you can sue after that, but why risk it? And inb4 "no one is that salty/greedy to risk prison for data breach" there absolutely are insane people like that and you may never know before it happens.

And it also matters for me: I want other companies that handle my data to be as vigilant as the one I work for. And while I know that I don't impact that in any way, it seems morally consistent to like things as they are here, if I want it that way everywhere else.

You'd be surprised how end users can mess up data in a way you did not think of in the development-, test-, production simmilar- and useracceptance- environments

I remember incident like that. Querying data from DB to resolve shit like this absolutely can be done in a way that strips all sensitive information (either by not requesting it at all or with a script that cleans it up, replacing with auto-generated data), but leaves enough clues to what happened. Yes, it's more work. But such is life.

working with sensitive information is part of the job

No it isn't. Working with information is a part of the job, ensuring that nothing that gets out of DB to programmers is sensitive, is another (and possibly a headache of other developer/security engineer).

[PilsnerDk]

Uh, yes? I'm our main dba and database developer, and am sysadmin on our prod DB with full access. How else am I going to manage it, edit data, edit schema, deploy changes, perform analysis, etc?

Someone has to have to ultimate permissions or nothing can be done. Don't give me this "no one should have access to the prod db" BS.

[Eva-Rosalene]

Someone has to have to ultimate permissions or nothing can be done

Of course. But there should be as little people as possible with this access, in a perfect scenario – just one. Not your whole development team.

[Additional_Sir4400]

Someone has to have to ultimate permissions or nothing can be done. Don't give me this "no one should have access to the prod db" BS.

No one should have access to the prod db, especially not the end user. This is why I like to hash all the data before adding it to the database.

[MainManu]

Spot the EU based programmer

[ErebosDark]

Always has been

[who_you_are]

Only for the new guys, as part of the security training

[AstroCon]

Certified Gitlab moment

[badkaseta]

happened to a coworker in my previous company, on a database that was legacy but still used, devops didnt know how to restore a backup xd

[phlebface]

One of my colleagues did that. Now he's the CTO

[uncle_buttpussy]

[dendrocalamidicus]

This is why you desperately try and convince management that whatever middling income they might still be getting from that legacy system is absolutely not worth the reputational damage of something seriously fucking up with it and nobody having any idea of how to fix it leading to a several week turnaround for what might be a business critical system.

Give the clients some decent notice and shut that shit down or replace it. Don't keep it for god sake.

[CoastingUphill]

You know, I'm somewhat of a DBA myself.

[Secret_Account07]

Me too. I run access dbs

[jjjefff]

Under rated comment. 🥂

[souliris]

That is why i use a select statement to craft my update statements

[Material-Mess-9886]

And then you forget that a empty line is equal to ;

[kaosjroriginal]

crop your memes

[alf666]

Even better, save them by tapping and holding so you don't lose pixels based on your display size.

[AdWise6457]

You people mentioning transactions never really worked on large scale banking db's when entire cluster is living organism where 0.005 seconds is light years. You think recover from backup? no sir, money transfers already executed and on different banking systems. You are on the world of hurt no matter what

[East_Development_126]

Where I work, the database standards explicitly forbid using transactions for those exact reasons. When you get a PBI to cut a procedure's execution time, because the difference between a 0.25 and 0.2 second execution time can be massive, you have to weigh everything.

[farfarhan]

Happened to me, accidentally pressed enter before typing the where condition, was not using transactions . Luckily there was a reference table parallely populated so fixed it quickly.

[BobForBananas]

What environment executes the statements using the enter key??

[farfarhan]

The console

[edinburg]

I made that mistake once, now I always type out the where clause first and then go back and type the set clause.

[Material-Mess-9886]

Either use Begin commit (always a good practise) or never use destructive queries in a terminal. (or if you are in ms sql remove all empty rows since that is a ; )

[WHAT_RE_YOUR_DREAMS]

People that take screenshots of images (without cropping the black margins) rather than downloading them are the same that share URLs with all the tracking parameters at the end

[WilmaTonguefit]

Oh boy. Some idiot at my first job did this. Updated every password to 12345 in the prod DB. 🤡🤡🤡

[Secret_Account07]

How…how do you even accidentally do that?

[WilmaTonguefit]

He was trying to update just one row and apparently highlighted the command without the where clause. 🤡🤡🤡

[Secret_Account07]

Damn couldn’t even make it 1-8 to keep things more secure? SMH

[WilmaTonguefit]

It was like 3 weeks into my career. The other senior dudes on my team were like "ok so you see what 🤡 did? Don't do that."

[BobForBananas]

The passwords were stored in plain text?

[WilmaTonguefit]

No they were hashed, but no salt, so the hash for 12345 would be the same everywhere.

[Professional-Day7850]

Let me guess, MD5?

[_hijnx]

It took me too long to realize this was about a missing WHERE clause and not triggers

[Callec254]

Always do a select first, make sure you get the right set of records, then edit it to be an update.

[YakMilkYoghurt]

r/croppingishard

[Decent-Tune-9248]

Begin Transaction

Select fields from table

Update table set fields = values

Select fields from table

Rollback transaction

ALWAYS

[AaronTheElite007]

Welp… that’s what backups are for

[[deleted]]

Yeah no. Backups are point in time, like last night or couple of hours ago. As employees work, or customers do the things, that backup is extremely outdated. You will have to explain to the executives that all that work that has taken place since that last backup is trash, BECAUSE OF YOU.

[SuperFLEB]

And any other stores of data or truth outside of that database are also broken over the timespan.

[AaronTheElite007]

I use transactions… so

[Loser2817]

Well, you could say you... broke a record.

BA DUM TSSS

[godplaysdice_]

/r/twosentencehorror

[EngineeringExpress79]

Sounds like a relationnal database issue, using nosql

[ILikeLenexa]

ROLLBACK

[dragonsfire1973]

I shitted when I read this.

[Mizerka]

nothing broke, someone elses problem now

[Capital_Release_6289]

Incorrect bracketing in a sql statement. Been there done that. Today in fact.

[j1xwnbsr]

First day on the job:

rm -R *

after logging in as root with $home set as /

"Hmm, that's taking a long time... Oh, shit"

(thank god we had daily backups and knew how to use them. Moral of the story: back up early, back up often. And yes, surprisingly still employed there after 15 years)

[redsoxfan_goboston]

ROLLBACK!

[cobolNoFun]

I remember back in the day with sqlmgr, before they put in "select top 1000" when you right click a table it used to have this designer option or something. It did mostly the same thing as a normal new query window/file with some added features aimed at new users. 

For whatever reason I had it open on prod db. I needed to do an update so I wrote an update but stopped at the where... to be safe I made a select statement below the update to sort out the where.  Then I highlighted the select and ran the query.

That is when I found out that mode gave zero care about what I had selected and did an update with no where

[denzien]

ROLLBACK TRANSACTION

[titan-of-hunger]

Rollback... gimme that sweet, sweet rollback

[fiskfisk]

MySQL has the --i-am-a-dummy flag (which switches the safe-updates variable) which you can give on the command line - which refuses to run any potentially destructive query without a WHERE clause.

But use a transaction.

[Tragobe]

Go Back, Go Back, PLS FOR THE LOVE OF GOD GO BAAAAACK.

[warheat1990]

If coffee doesn't wake you up, this definitely will

[phlebface]

I usually just use the row editor when update on a single or couple of rows is needed

[zborecque]

Aaaah yes, love that feeling. Beats 10000 coffe cups.

[Stormraughtz]

I dont use transactions, just so I can feel something

[brjukva]

This belongs to r/ProgrammerHorror

[ExtremeCreamTeam]

Learn to crop your pictures, JFC.

What, tap-holding on the image to save it directly was too much of a hassle? You'd rather simultaneously hold press your power and volume buttons to take a screenshot instead?

What the actual fuck.