3 ms·

Title possibly: "Stop writing upserts the wrong way (MS-SQL Server)" since it's less clear which flavor of SQL this is relevant?

• ksenzee 6y ago
  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.
• hobs 6y ago
  SQL Server is the name of the product, hence the inclusion in the title.
  • bragh 6y ago
    In a common forum that is not purely dedicated to Microsoft technology, MS product names really ought to be prefixed — context is important. For example, it applies to Entity Framework also: it has happened a few times to me that a non-MS developer assumed that ORMs in general were discussed, while it was related only to the MS implementation.
• deleted 6y ago
  [deleted]