4 ms·

The concept is applicable to relational databases in general, and it's a good idea. ETA: The point here is not the syntax, it's "don't leave race conditions sit

The concept is applicable to relational databases in general, and it's a good idea. ETA: The point here is not the syntax, it's "don't leave race conditions sitting around in your upserts." Whatever RDBMS you're using, you need to make sure you're at the very least inside a transaction, and at best avoiding an unnecessary transaction.

mulmen 6y ago
It’s not though because basically every RDBMS does this differently.
- dathinab 6y ago
  Yes the article isn't really applicable to e.g. postgres where you would simply use on conflict do update which is atomic so no need to bother with things like a serializable transaction.