A Database Constraint Can Close the Gap Between Checking and Writing
Checking whether a record exists before inserting another one does not guarantee uniqueness.
wade womersley – york based software engineer
Engineering notes from the sharp end
wade womersley – york based software engineer I write the way I work: direct, useful, and more interested in what holds up in production than what sounds clever on a slide.
306 published posts
Latest update
Latest post
Checking whether a record exists before inserting another one does not guarantee uniqueness.
Archive
A proper game manual could get the adventure going before the game had even started.
A webhook can contain perfectly sensible JSON and still fail signature verification.
A request ID in one log line is useful.
One of my favourite things about furry conventions is how quickly the wonderfully ridiculous starts to look normal.
A temporary feature flag is very good at becoming a permanent piece of the application.
A test that repeats the implementation can pass while proving very little.
My favourite sort of Halloween decoration is the one that has wandered slightly away from being scary.
“Run it at six” is incomplete information for a scheduled job.
Replacing app.js and hoping every cache forgets the old version is a fairly unpleasant deployment strategy.