Repository navigation
dbui v0.2.4
Pre-releaseThis build is unsigned. It is not notarized by Apple, so macOS will
refuse to open it until you clear the quarantine flag. See
Installing below. The in-app updater will not offer this
release — install it by hand.
Two reports from the same corner of the app: creating a table looked like
nothing had happened, and an error the engine took the trouble to explain was
gone by the time it was read.
CREATE TABLE says what it did
Every engine reports DDL as zero rows affected, and the status bar rendered
that as "0 rows affected" — true, and a verdict on nothing. dbui now reads the
leading keywords of a statement and says CREATE TABLE notes · OK in 3 ms
instead.
A count the engine actually put a number on is never thrown away. A DELETE
that matched nothing still reports zero rows, because there that is the
answer.
The schema tree catches up on its own, too. Nothing re-read the catalog after a
DDL statement, so a table you had just made was not in the sidebar until you
pressed ⌘R. It appears now, through a refresh that stays quiet — the DDL's own
verdict is what you are reading, and "Catalog refreshed" landing on top of it a
moment later is how that feedback went missing in the first place.
SQL errors stay where you can read them
The status bar is one line, and the next message owns it. The reason a query
failed survived until the next thing happened — sorting a column, clicking a
cell, a background tab finishing its load — and then it was simply gone.
An error now belongs to the tab that earned it, drawn in a panel between the
editor and the grid: the engine's own message, its SQLSTATE, the statement it
is about, and buttons to copy or dismiss it. It goes when the next run replaces
it, and not before.
A batch that fails halfway keeps what ran
Running five statements and failing on the third used to discard the results of
the first two along with the error, leaving an empty grid and a one-line
footer. The failure now travels inside the batch: the statements that ran stay
in the strip above the grid, their rows are still there, and the panel says how
far it got — "2 statements ran before this one · 1 was not attempted".
Errors on background tabs are no longer swallowed
Both the query and the table-load paths only reported a failure if its tab was
still in front. Switching tabs while something was in flight made its error
disappear entirely. It lands on the tab it belongs to now, whether or not you
are looking at it.
Installing
This release is not signed or notarized, so Gatekeeper blocks it on first
open. After dragging dbui to Applications:
xattr -dr com.apple.quarantine /Applications/dbui.appThen open it normally. Alternatively, try to open it once, then go to System
Settings → Privacy & Security and click Open Anyway.
Signed and notarized builds will return in a later release. Until then the
in-app updater will not offer this version — it requires a notarized build
carrying the same Team Identifier as the copy you are running, and it refuses
anything that fails that check.
Verify your download against SHA256SUMS:
shasum -a 256 -c SHA256SUMS