trdsql VS usql

Apparently, there were many who thought the same thing; Tools to execute SQL against CSV were trdsql, q, csvq, TextQL. They were highly functional, hoewver, had many options and no input completion. I found it just a little difficult to use.

Nice! Kinds of reminds me of trdsql

trdsql(https://github.com/noborus/trdsql) is a tool that executes SQL for files such as CSV, but it can also be used by connecting to MySQL. Therefore, SQL such as CREATE TABLE table AS SELECT * FROM csvfile.csv can also be executed.

trdsql can execute SQL against CSV, LTSV, JSON and TBLN, and the database can also use SQLite,PostgreSQL and MySQL.

trdsql can execute SQL against CSV, LTSV, JSON and TBLN, and the database can also use SQLite,PostgreSQL and MySQL.

Check out https://github.com/noborus/trdsql

The trdsql I made is feature-rich and fast (as a similar SQL tool).

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