OHMySQL
Swift + MySQL = ❤️
Runssource: GitHubhomepageCMITcommit cc1874ddaaa8
C, MIT licensed. The project labels itself: cocoapods, database, dbms, ios, maccatalyst, macos, mysql and mysql c api.
OHMySQL runs. An Argusic agent installed it in 58 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
OHMySQL Swift library builds and links against system MariaDB on Linux. Escape Tests (string escaping) pass 9/9. MySQL 8.0.46 server is running locally. The Swift port provides the same API surface as the original framework (MySQLConfiguration, MySQLStoreCoordinator, MySQLQueryContext, MySQLQueryRequestFactory, MySQLMappingProtocol).
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 60 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.
- Original framework is iOS/macOS ObjC with Apple XCFrameworks - cannot build natively on Linux30 minutes
- MySQL server needed for tests - not installed10 minutes
- Swift 6.0 toolchain missing on Linux - libncurses.so.6 not found5 minutes
- MariaDB client could not load caching_sha2_password auth plugin5 minutes
- NSObject KVC (setValue:forKeyPath:) not available on Linux Foundation3 minutes
- Connection tests hung due to deadlock in MySQLStoreCoordinator reconnect3 minutes
- Install time
- 58 minutes
- Cold machine to finish
- 70 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- xctest OHMySQLTests.EscapeTests ran 9 tests, 0 failures: passing test output was 'Executed 9 tests, with 0 failures (0 unexpected)'. Swift library build completed with 'Build complete! (1.13s)'. MySQL server responded to 'SELECT 1' via socket. Direct C API test via swiftc binary confirmed mysql_real_connect succeeded with server info '8.0.46-0ubuntu0.24.04.4'.
- Model tokens used
- 967,651
- Exact commit tested
- cc1874ddaaa8
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 672ms: Building for debugging... [0/1] Write swift-version-297A43C580B13274.txt Build complete! (0.24s) No .so Good, builds clean now. Let me produce the final report with what I have observed. 2026-09-13T14:55:24.721545Z ERROR codex_core::session: failed to record rollout items: thread 01a09… 2026-09-13T14:55:24.721583Z ERROR codex_core::session: failed to record rollout items: thread 01a09… 2026-09-13T14:55:24.721600Z ERROR codex_core::session: failed to record rollout items: thread 01a09… tokens used 967,651 Good, builds clean now. Let me produce the final report with what I have observed.
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 58 minutes.
- Recovered from all 7 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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 | 100.00 | 0.47 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.17 |
Topics (from GitHub)
cocoapodsdatabasedbmsiosmaccatalystmacosmysqlmysql-c-apimysql-clientmysqlclientobjective-csqlswifttvoswatchos
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ohmysql)Questions
- Does OHMySQL run?
- Yes. OHMySQL runs. Argusic installed and launched it on a clean machine in 58 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test OHMySQL?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cc1874ddaaa8. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test OHMySQL?
- The run that produced this verdict cost $0.47: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does OHMySQL take to install?
- 58 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 OHMySQL need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing OHMySQL?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for OHMySQL?
- 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.