Skip to content

DownloadDownload DMG

The rest of the app, one claim per picture. Every one of these is a screenshot of it running, not a rendering.

The Objects tab for a schema, one row per table and view with its kind, estimated rows, size and owner. — An estimate is labelled as an estimate.Objects overview of a schema: kind, size, engine, collation, owner. Every figure comes from the introspector, and nothing here runs COUNT(*) behind your back.

The visual query builder with two tables on the canvas joined on a foreign key, and the generated SQL beside them. — Drop two tables on the canvas and the foreign key becomes the join.The builder writes fully quoted, schema-qualified SQL, so it runs unchanged wherever you paste it.

The grid filter bar over the orders table with two conditions on it — each one a column, an operator and a value — joined by OR. — A filter is conditions, not a string you concatenate.Conditions join with AND or OR. Values are sent as parameters, never interpolated, and the filter runs on the server.

The cell inspector open beside the grid, showing the focused cell’s column name, native type, constraints and raw value. — Precision survives the round trip.The cell inspector shows the raw value: JSON pretty-printed, binary as a hex dump. decimal and timestamp keep the server’s own text, never routed through Double or Date.

The Map tab of a table with a geometry column, its points drawn on Apple Maps. — Geometry columns get a real map.Points, lines and polygons drawn on Apple Maps, straight from the table tab. Click one to select its row.

The export sheet over a table tab, offering the format, the scope and the options that format needs. — A large table never has to fit in memory.Export streams rows to disk as they arrive: CSV, JSON, NDJSON, SQL INSERT and Excel. Dump, import and transfer work the same way — including a transfer between two different engines.

Six pictures, six claims. Two things are worth doing with them.

Read what is under the screenshotsA Swift Package Manager workspace with a strictly downward dependency graph, all database I/O in actors, and a CI that fails on a warning.

Check the claim in the second cardThe status bar names the row range and the elapsed time on every tab. Open a big table and read it — that is the one to check first.