App
Updates and trust
Bobby Tables checks for a new version once a day, tells you in a banner, and installs it in place when you choose. It sends no analytics, and an error report leaves your computer only when you press Send.
Where to find it
| Action | How |
|---|---|
| See a new version | The banner at the top of the window |
| Check now | Bobby Tables → Check for Updates… on macOS, Help → Check for Updates… on Linux |
| Turn off automatic checks | Preferences…, ⌘, (Ctrl+,), then General and Check for updates automatically |
| See the installed version | About Bobby Tables, in the same menu as Check for Updates… |
| Report a problem | Help → Report a Bug / Send Feedback…, or Report… on an error |
Checking for updates
While the app is open it checks at most once a day, without showing a dialog. Check for Updates… checks straight away and shows Checking for Updates while it contacts the update server. When nothing newer exists, You're up to date names the version you are running. When the server cannot be reached, Couldn't check for updates offers Try Again and OK.
The update banner
A newer version appears as a banner across the top of the window with the first line of its release notes, and a manual check that finds one opens the same banner. Dismissing it keeps automatic checks quiet about that version, while Check for Updates… still offers it. Update downloads the package with a progress bar, checks its signature, installs it and opens the app again on the new version. Where the app cannot replace itself, such as a Debian package install, the button reads Download and opens the installer instead.
What the app sends
There are no analytics, no usage tracking and no remote feature flags. The update check sends this computer's platform and the running version, and nothing about your license. With a license, the app also checks it in the background by sending its signed receipt, described on License. Error reports are sent only when you press Send, and remote image previews in results stay off until you turn them on.
When something fails
A failed query shows the database's message under the editor, with its SQLSTATE code, line, column and hint where the database gives them, and your statement stays in the editor. A view that cannot be displayed is replaced by a card with Copy, Report…, Close tab and Try again, while the rest of the app keeps working. If the whole interface stops, a recovery screen titled Something went wrong offers Copy, Report… and Reload.
Reporting a problem
Report… opens a short form on the error, with optional What were you doing? and Email fields. Before it is sent, paths in your home folder are shortened and connection names, hosts, database names, bucket names and file names are replaced with <redacted>. The report carries the error message, where in the interface it happened, the app version and the operating system, and never your logs, saved connections, query history or license receipt. If sending fails, the details are left on your clipboard.
Good to know
- A package whose signature does not verify is never installed.
- Every release ships SHA-256 checksums, and the macOS package is signed and notarized.
- A license is not needed to update.
- Automatic updates are published for Apple Silicon Macs and for Linux x86_64. Other builds are told to download the update.
- The app replaces itself only from a location it can write to. Otherwise it says so and offers the download.
Help → Open Logs Foldershows the local diagnostic log, which is never uploaded.