db
Data Access Layer (DAL) for PostgreSQL, CockroachDB, MySQL, SQLite and MongoDB with ORM-like features.
Runs with mockssource: GitHubhomepageGoMITcommit dd97b4b4d5c6
Go, MIT licensed. The project labels itself: cockroachdb, dal, database, db, go, golang, mongodb and mysql.
db runs, with stand-ins for the services it depends on. An Argusic agent installed it in 4 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.
All packages compile and unit test suites pass (root pkg, 7 adapters, 5 internal pkgs); integration DB tests skipped due to missing Docker.
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 80.2 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 1.23.2 not installed in container2 minutes
- internal/testsuite package missing (needed by adapter/sqlite, adapter/ql tests)1 minute
- integration tests in tests/ require Docker + Ansible (ansible-playbook not found, no Docker)
- Install time
- 4 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 3 hit, 2 fixed with no human help
- How the result was proved
- go build ./... exited 0; go test -count=1 on all non-integration packages exited 0: 13 packages, all ok
- Model tokens used
- 101,283
- Exact commit tested
- dd97b4b4d5c6
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- Go 1.23.2 was not installed; downloaded and placed at `/tmp/go/bin/go` - `internal/testsuite/` package was missing — it's referenced by `adapter/sqlite` and `adapter/ql` … - Set `DB_NAME` environment variable to a temp file for sqlite adapter tests **Verification:** `go build ./...` exits 0. `go test -count=1 -timeout 120s` on all non-integration… tokens used 101,283 All 13 packages pass tests, all packages build. Here's the report: **Summary of what was done:** - Go 1.23.2 was not installed; downloaded and placed at `/tmp/go/bin/go` - `internal/testsuite/` package was missing — it's referenced by `adapter/sqlite` and `adapter/ql` … - Set `DB_NAME` environment variable to a temp file for sqlite adapter tests **Verification:** `go build ./...` exits 0. `go test -count=1 -timeout 120s` on all non-integration…
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
- Installed in 4 minutes.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Hit 3 errors during setup, 1 of which were not solved.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 85.33 | 0.07 | |
| Argusic Runner | 1/3 | Unverified | 75.00 | 0.05 |
Topics (from GitHub)
cockroachdbdaldatabasedbgogolangmongodbmysqlnosqlormpostgresqlsqlsqliteupper
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/db)Questions
- Does db run?
- db runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 4 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test db?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit dd97b4b4d5c6. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test db?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does db take to install?
- 4 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 db need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing db?
- 3 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 db?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.