stackql-middleware VS squid

Hi HN, we have an open-source project called StackQL which can be used for CSPM, cross-provider UAM/entitlements reporting, inventory analysis, and finops across different public cloud and SaaS providers; see https://github.com/stackql/stackql-provider-registry. In addition, StackQL can be used for IaC (across different cloud providers), including multi-cloud transaction and rollback capability, which we are building out. Can be used standalone (in exec or server mode running a postgres wire protocol server) or using Docker, Python, Jupyter, within GitHub Actions (incl https://github.com/marketplace/actions/stackql-studios-stack... and https://github.com/marketplace/actions/stackql-studios-stack...) and more.

The project can also be used with a private registry (API provider) as an application query interface - like GraphQL - except using SQL statements and transformations (including scalar and aggregate functions, joins, unions, and table-valued functions - see https://github.com/stackql/stackql-middleware and https://github.com/stackql/stackql-playground.

We are looking for contributors!! The core project is written in Golang with tests implemented using the Robot framework and Python. We have about 40 related repos in our org, spanning Python, Jupyter, JavaScript/TypeScript (Deno and NodeJS). Let us know what you think!

I guess I failed to set the context correctly given that you presented solutions for Clojure and Python, where it isn't as much of a problem since from the start the language fails to provide compiler guarantees you usually come to expect out of a SQL driver wrapper in typed languages (even though Clojure macros are probably powerful enough to allow this).

As a comparison, DX-wise this is no safer and is indeed very similar to the usual idiom in Go for example, where you just concatenate (pre-interpolated) SQL strings. But when you actually want the compiler to prove the correctness of your queries even in a rudimentary way, these .sql file solutions usually (if not, everytime) fail to provide the necessary external checker that processes templates and uses an accurate model of your database and SQL to verify that all used combinations make sense.

The closest thing to a proper take on this I've seen is https://github.com/andywer/squid with https://github.com/andywer/postguard which, although the SQL is inlined in the code, it uses the right approach for verifying correctness as far as I could tell in the little time I experimented with it.

For typescript and javascript, there's also squid + its companion project, postguard: https://github.com/andywer/squid