

The General tab
Language
System (the default), English, Tiếng Việt, 简体中文, 繁體中文, 한국어, Türkçe, Français. Pick a different one and the tab offers Relaunch to finish the switch.Startup
When TablePro starts takes Reopen Last Session (the default) or Show Welcome Screen. What a reopened session brings back, and what it does when a server is down, is on Tabs. A relaunch from Relaunch to Update, or from a Relaunch button in Settings, reopens the last session once, whichever you pick.Tabs and sidebar
Icons, comments, system databases and schemas, partitions, and row size are also under View Options, the button beside the sidebar’s filter field. Right-clicking the empty space below the object list reaches the same options.
Connections
Show recent connections is on out of the box and puts a Recent section in the welcome window and Switch Connection. Turning it off hides the section and keeps the history. Clear Recent, on the Recent connection history row, forgets it, which also starts sorting by Last Connected over. The switch and the history both stay on this Mac. Check connections sets how often each open connection is checked for a dropped session. The choices, and what a failed check starts, are under Connection health.Query timeout
How many seconds a query runs before it is cancelled. The default is 60; the picker offers 10 to 600 seconds and No limit. The value is read when a connection opens, so a change reaches an open connection only after you reconnect. A connection can override this value under Options > Query timeout. Leave that field empty to inherit this setting, or enter0 for no limit. The same section has a separate connect timeout for tunnels, proxies and database sign-in; it does not change how long a query can run.
Where the engine can enforce it, the timeout becomes a server-side setting: statement_timeout on PostgreSQL, max_execution_time on MySQL and ClickHouse, max_statement_time on MariaDB, ob_query_timeout on OceanBase, query_timeout on StarRocks. On SQLite it bounds how long a statement waits for a locked database instead. Drivers that talk HTTP (BigQuery, Bigtable, Spanner, Cloudflare D1, LibSQL, Etcd, DynamoDB, Elasticsearch, Typesense, and ClickHouse) bound the request at the timeout plus 30 seconds, and Oracle enforces it in the client: the connection is closed to unblock the call, and the next query reconnects and restores your current schema. SAP HANA ends the statement with the same ALTER SYSTEM CANCEL SESSION that Stop sends.
Older servers have neither: MySQL before 5.7.8, MariaDB before 10.1.1. A statement that passes the timeout there is stopped with KILL QUERY from a second connection, which reaches a SELECT on MySQL and any statement at all on MariaDB. A server behind a proxy that reports a version it does not have still gets the right one of the two.
No limit still caps an HTTP request at one hour, because the transport needs a ceiling.
An export, Copy To, a table transfer and a data comparison read with the timeout off and put it back when they finish. Their reads wait for the side that writes, so a long copy would otherwise be cancelled part way. MySQL and MariaDB give up on a read left waiting for 10 minutes, and TablePro raises the session’s net_write_timeout to that when a read starts.
On InfluxDB and Typesense such a read is one HTTP response that lasts as long as the copy, so the one-hour cap does not apply to it.
Command line tool
Command Line shows whether the shell command links to this copy of the app. Copy its Terminal line to install or remove the link. See Terminal for installation and commands.Trusted links
Use Forget to remove one saved link approval, or Forget All to remove them all. See Trusting a link for which links qualify and when they still ask.Software update
The top row says where updates stand, and its button takes the next step:
Check Now and TablePro > Check for Updates… check at once. A check you start ignores the schedule and any staged rollout, so it always offers the newest build.
Update channel is Stable out of the box. Pick Beta to be offered each new version as a beta before its stable release. Beta updates covers going back to stable.
The two switches are on out of the box. The first one stops the daily check, the second stops the install.
Automatically check for updates runs the check in the background once a day. Turn it off and nothing reaches the network until you start a check yourself.
Download and install updates automatically fetches the new version in the background and swaps it in the next time TablePro quits, with no dialog. Turn it off to be asked first. With the check switched off the switch is dimmed and installs never run.
Updates arrive through Sparkle and are signature-checked before they install.
What’s New opens the highlights of the version you are running, with a button to the full changelog. It is also Help > What’s New.
An administrator can pin the channel, both switches and the interval across a fleet. See Managed updates.
When an update is waiting
A waiting update shows in four places: a button at the trailing end of each connection window’s title bar, a link under the version on the welcome window, the TablePro > Check for Updates… menu item, and the top row of this section. There is no notification and no Dock badge. With nothing waiting, the button and the link are gone. The button and the link take one of two names:- Update Available: a background check found a new version that has not downloaded, which is what happens with Download and install updates automatically off. Click it to open the update window.
- Relaunch to Update: a new version downloaded in the background, or plugin updates are staged. In a connection window it opens a popover with the version, Release Notes, the plugins that update too, Later and Relaunch Now. On the welcome window it relaunches straight away.

