usql VS liquibase

Also all languages has an query-builder / ORM so the benefit of something like PRQL is possibly not big enough to merit it as an additional dependency.

My suggestion:

Make PRQL a cli tool that can be used by allowing users to connect to a database in a similar fashion as something like usql (https://github.com/xo/usql),

take a look at: https://github.com/xo/usql

https://github.com/xo/usql has some good first issues

There's a new release of usql that adds even more autocomplete and fixes a bunch of issues: https://github.com/xo/usql/releases/tag/v0.11.0

I am not a big fan of the complex literate programming style involving code-generation which this article talks about.

But I recently discovered that Google's zx [1] scripting utility supports executing scripts in markdown documents and I combined it with httpie [2] and usql [3] for a bit of quick and dirty automation testing and api verification code and it worked out pretty well.

[1] https://github.com/google/zx#markdown-scripts

[2] https://github.com/httpie/httpie

[3] https://github.com/xo/usql

While I respect the work, Liquibase's code base is quite messy... https://github.com/liquibase/liquibase

Have you looked at liquibase?

For those in search of a open source solution with commercial support have a look at https://www.liquibase.org/

I haven't used it for a number of years but it sounds like something like liquibase (https://www.liquibase.org/) might be what you're looking for.

Liquibase

We use https://github.com/liquibase/liquibase, as most of Dev are used to and comfortable with it.

Highly recommend you use either Liquibase or Flyway for schema management, and Testcontainers pg to run a transitive database for your tests.

I haven't used this so I'm not sure it does exactly what you're looking for but I had a DBA recommend it to me as a possible tool to start using as we overhaul our pipelines. https://www.liquibase.org/