A stray commit buried multiple levels deep cost me months
droppedasbaby.com
A stray commit buried multiple levels deep cost me months
1–10 of 38 posts
Re: A stray commit buried multiple levels deep cost me months
#2Why not? Why should I be allowed to db.commit() midway through a transaction?
Re: A stray commit buried multiple levels deep cost me months
#3> DO NOT blame the framework Why not? Why should I be allowed to db.commit() midway through a transaction?
Re: A stray commit buried multiple levels deep cost me months
#4Re: A stray commit buried multiple levels deep cost me months
#5> DO NOT blame the framework Why not? Why should I be allowed to db.commit() midway through a transaction?
With great power comes great responsibility.
Re: A stray commit buried multiple levels deep cost me months
#6> DO NOT blame the framework Why not? Why should I be allowed to db.commit() midway through a transaction?
I think the option should be there, but it needs to be used responsibly.
Re: A stray commit buried multiple levels deep cost me months
#7Re: A stray commit buried multiple levels deep cost me months
#8> DO NOT blame the framework Why not? Why should I be allowed to db.commit() midway through a transaction?
Giving "I cut my finger with a knife, why is the knife so sharp?" energy. JKJK. I think the option should be there, but it needs to be used responsibly.
Re: A stray commit buried multiple levels deep cost me months
#9Re: A stray commit buried multiple levels deep cost me months
#10Show, don't tell. The article should've included an example of these helpers.
All in all, this feels poorly written, but also poorly thought out. The DB layer can and should throw an exception if you manually begin/commit inside a context manager. Please do blame it if it doesn't.