> No memory safe language will protect you from getting your SQL queries wrong.

That's kind of the point.

> Races in a database are not “data races” in the programming language sense

Only in the sense that in a sufficiently large bureaucracy you get to power up the Somebody Else's Problem Field and blame the DBA for it. But that doesn't get you the missing money back.

This whole conversation is about memory safety of programming languages, not security vulns that no language can prevent

Which is, again, the point. People have a new hammer but not everything is a nail.

And lots of programming languages provide tools to address data races. SQL has transactions, several languages have compare-and-swap primitives, etc.