News for hackers. Stuff that matters.

A comment on ZetaSQL – A SQL Analyzer Framework from Google. Parent comment

Re:ZetaSQL – A SQL Analyzer Framework from Google by setr on Tuesday May 21, 2019 @08:36PM (#19976618)
I’m pretty sure it wouldn’t follow any; I can’t imagine any significant benefit (if you’re not chasing strict compatibility, general SQL should take you more than far enough on the beginner-friendly front) and significant benefit from doing a custom SQL
[ Parent | on HN ]
Re:ZetaSQL – A SQL Analyzer Framework from Google by paxys on Wednesday May 22, 2019 @12:00AM (#19977647)
A benefit of following an established standard is that one can use this not just to write a new engine but also to build internal tooling (static analysis, linters, IDE tools etc.) for an existing one (e.g. MySQL).
[ Parent | on HN ]
Re:ZetaSQL – A SQL Analyzer Framework from Google by djhaskin987 on Tuesday May 21, 2019 @08:43PM (#19976670)
What significant benefit
[ Parent | on HN ]
Re:ZetaSQL – A SQL Analyzer Framework from Google by davidjnelson on Tuesday May 21, 2019 @08:57PM (#19976755)
Things like late row lookups in mysql that are not an issue in postgres https://explainextended.com/2011/02/11/late-row-lookups-inno...
[ Parent | on HN ]
Re:ZetaSQL – A SQL Analyzer Framework from Google by riffraff on Wednesday May 22, 2019 @04:02AM (#19978952)
aren't both executions (mysqls' and postgresqls') acceptable from an SQL point of view?

I don't think the SQL standard mandates how the DBMS executes the query. In fact, I seem to remember that was on of the purposes of having an high level language.

[ Parent | on HN ]