Hacker News Reader

That's not true though. SQL is not computationally complete. It does abstract over the complexity of access to relational data. And it is still used and useful. SQL is also not automatically brittle.

There is a problem of a language gap, a mismatch between SQL structures and internal types, and all in all maybe a gap in typed code and unit tests.

That does not mean you should implement your own database.

View on HN

Plain SQL is not turning complete, however SQL/PSM is and something along those lines is supported by (most?) database implementations like PostgreSQL, Oracle SQL, MySQL, etc. Seems to me like SQL is a perfect example of most people agreeing that the extra power/complexity is indeed a requirement.

Not sure the extensions were really needed though. Certainly the gaps could be filled externally and in a lot of shops it's what's mandated. I think an argument could be made that the extentions you're bringing up is more about a turf war between DBA's and Developers than about neccessity.

Most of the time, the SQL queries are only useful when they are part of a bigger application, which is often written using a Turing complete language.

Reply on news.ycombinator.com