usql
Universal command-line interface for SQL databases
Runssource: GitHubGoMITcommit 687d7b5deaa1
Go, MIT licensed. The project labels itself: command line, database, go, golang, mariadb, microsoft sql server, mysql and oracle.
usql runs. An Argusic agent installed it in 10 minutes and hit 4 errors on a clean machine with no GPU, and the whole session was recorded.
usql builds from source and runs on Go 1.27.1; the SQLite driver works end-to-end for creating tables, inserting, and querying; all 7 non-Docker test packages pass.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 90 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Go compiler not found in container2 minutes
- Test recording expects PAGER='less' but container has PAGER='more'1 minute
- Docker-dependent tests (informationschema, postgres, sqlserver) fail - no Docker socket available
- ODBC driver build fails - missing unixODBC development headers
- Install time
- 10 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 4 hit, 2 fixed with no human help
- How the result was proved
- echo 'CREATE TABLE users (id INTEGER PRIMARY KEY, name TEXT); INSERT INTO users VALUES (1, '"'"'alice'"'"'), (2, '"'"'bob'"'"'); SELECT * FROM users;' | ./usql sqlite:///home/runner/test_verify.db returned CREATE TABLE, INSERT 2, and 2 rows (alice, bob)
- Model tokens used
- 127,960
- Exact commit tested
- 687d7b5deaa1
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
2. **Built `usql`** — `go build` with the `most` tag set succeeded, producing a working `usql` bina… 3. **Ran the SQLite driver end-to-end** — created a table, inserted rows, and queried them, confirm… 4. **Ran the test suite** — fixed one test recording (the container's `PAGER` is `more` instead of … ## Errors encountered | Error | Fix | |---|---| | Go compiler not installed | Downloaded & extracted `go1.27.1.linux-amd64.tar.gz` | | Test expected `PAGER = 'less'`, container has `more` | Re-recorded testdata with `go test -update… | Docker-dependent tests (`informationschema`, `postgres`, `sqlserver`) fail | No Docker socket ava… | ODBC driver build fails | No unixODBC headers — unfixable without system packages | ## Test results All 7 test packages covering the core CLI, environment, handler, statement parsing, metadata, SQLit…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 10 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Hit 4 errors during setup, 2 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 10 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
command-linedatabasegogolangmariadbmicrosoft-sql-servermysqloracleoracle-databasepostgrespostgresqlsqlsqlitesqlite3
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/usql)Questions
- Does usql run?
- Yes. usql runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test usql?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 687d7b5deaa1. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test usql?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does usql take to install?
- 10 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does usql need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing usql?
- 4 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for usql?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.