Wow, this looks like it fixes a lot of the minor gripes I have with SQL, thanks for mentioning it. It feels way less cludgy and "modernized" compared to SQL.

That reminds me of the Ecto DSL.

Maybe as a baby step we could just get legal trailing commas

Or force the big RDBMS to use the same syntax like SQL was intended to be, so I don't have to reach for an ORM or maintain different flavors of the same query.

If someone knows a tool that reliably converts PostgreSQL queries to something like SQLite, please share!

Not sure how such a tool could possibly exist, given all the functionality of Postgres that SQLite simply lacks.

You could ask ChatGPT to do this sort of conversion

Still not going to have wave around things like not having transactions or proper trigger functions.

SQLite does have transactions. But I do agree with your general point that Sqlite is worlds apart from Postgre

haven't really tried for that transform but have a look at https://www.jooq.org/translate/

sqlglot might be what you are looking for.

https://github.com/tobymao/sqlglot

The syntax looks very similar to Microsoft's Kusto Query Language (KQL): https://learn.microsoft.com/en-us/azure/data-explorer/kusto/...

It's interesting to see that everyone's attempt at fixing SQL seems to converge on surprisingly similar solutions...

Microsoft did linq first which is probably the basis for the rest.

From first principles, it seems reasonable to expect transformations to go in a linear order. From there you look for ways to minimize special cases (eg why is `where` different from `having`?). Then you can just layer on some quality of life things which would appear to a designer after five minutes of real-world use (dear god, please let me have trailing commas).

I would expect there to be a lot of convergent evolution as how to go from a pile of data to narrowing on what you want.