Repository navigation
SQLPilot 1.0.1
Two fixes for problems 1.0.0 shipped with. Both were found within an hour of
release, on a real machine rather than in CI.
A connection store written by an older version would not open
This affects everyone upgrading from 0.4.0 or earlier — which is every
release before 1.0.0, because the migration framework shipped for the first
time in 1.0.0.
If you used SQLPilot before that framework existed, your
connections.db has the columns of version 5 and records itself as version 1 —
the old code added those columns at startup and never wrote down a version.
1.0.0 tried to add a column that was already there, refused the file, and fell
back to an empty in-memory store. Your connections were still on disk, intact
and invisible.
A migration whose change is already in place is now recorded rather than
refused. The tolerance is narrow — a missing table is still an error, because
that is a broken database and hiding it would be worse than stopping.
Nothing was lost. 1.0.0 left the file untouched by design; opening it with
1.0.1 brings your connections back.
A .deb or .rpm install could not update at all
The updater looks for {os}-{arch}-{installer} before {os}-{arch} — so a
.deb install asks for linux-x86_64-deb, an .rpm install for
linux-x86_64-rpm. Those keys were dropped from the update manifest in 0.4.0
on the belief that nothing read them. Something does: package installs found no
key of their own, fell back to one pointing at an AppImage they cannot apply,
and stopped.
All eleven keys are back, each pointing at something that format can actually
install.
The fix is in the manifest rather than in the app, so it reaches you where you
already are: a 1.0.0 or 0.4.0 install looking for linux-x86_64-deb now finds
one, and can update itself.
One case it does not fix: an install on an image-based system — rpm-ostree,
Silverblue, Bazzite, or anything with a read-only /usr — cannot self-update
whatever the manifest says, because applying an update there means writing to a
filesystem the running system cannot write to. Update those the way you
installed them.
Downloads
| Platform | File |
|---|---|
| Windows (portable) | SQLPilot.exe |
| Windows (installer) | SQLPilot_1.0.1_x64_en-US.msi or SQLPilot_1.0.1_x64-setup.exe |
| macOS (Apple Silicon) | SQLPilot_1.0.1_aarch64.dmg |
| macOS (Intel) | SQLPilot_1.0.1_x64.dmg |
| Linux | SQLPilot_1.0.1_amd64.deb, SQLPilot-1.0.1-1.x86_64.rpm, or SQLPilot_1.0.1_amd64.AppImage |
Everything in 1.0.0
applies unchanged.