From 265c34bf0f4dcd8693e7fb74a0c3a95fc12f69e3 Mon Sep 17 00:00:00 2001 From: Ngo Quoc Dat Date: Fri, 13 Nov 2026 08:06:49 +0700 Subject: [PATCH 1/2] docs(ios): SQL Server three-part names and Read-Only transactions --- ios/index.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ios/index.mdx b/ios/index.mdx index 819bbe0..758a8e5 100644 --- a/ios/index.mdx +++ b/ios/index.mdx @@ -201,7 +201,7 @@ Suggestions fill the bar above the keyboard as you type, in front of the fixed k Touch and hold **Run** for **Run All Statements**, which sends every statement in the editor in order. It is in the **More** menu too. On a hardware keyboard, `Cmd+Enter` runs the statement or the selection, `Cmd+Shift+Enter` runs every statement, and `Cmd+.` stops. On iPad the menu bar's **Query** menu lists **Run Statement**, **Run All Statements**, **Stop** and **Clear Query**, and its **View** menu switches sections with `Cmd+1` through `Cmd+4`. -On MySQL, MariaDB, TiDB, OceanBase and SQL Server, a `USE` you run moves the table list and the database menu to that database, and a dropped connection reconnects there; while a window has unsaved changes on the connection, the `USE` is undone and a message says why. Until a run with a `USE` ends and the menu has followed it, **Run** waits in every window. On MySQL, MariaDB, TiDB and OceanBase, **Tables** names the database the menu shows in every statement it sends. On SQL Server it does not, so saving, inserting, deleting, truncating and dropping there stop with a message while such a run is going, or while the session sits in another database than the menu shows. On PostgreSQL, a `SET search_path` you run, or a **Roll Back** that undoes one, moves the schema menu to the schema the session uses. +On MySQL, MariaDB, TiDB, OceanBase and SQL Server, a `USE` you run moves the table list and the database menu to that database, and a dropped connection reconnects there; while a window has unsaved changes on the connection, the `USE` is undone and a message says why. Until a run with a `USE` ends and the menu has followed it, **Run** waits in every window. **Tables** names the database the menu shows in every statement it sends, as `[database].[schema].[table]` on SQL Server, so a save, insert, delete, truncate or drop reaches the table on screen wherever the session sits. On PostgreSQL, a `SET search_path` you run, or a **Roll Back** that undoes one, moves the schema menu to the schema the session uses. Tap a query in **History** or **Saved Queries**, or a table under **SELECT * FROM ...** in the **More** menu, to add it to the editor. It fills an empty editor; otherwise it goes after your text as a statement of its own, with the cursor in it, and **Undo** takes it back. A statement that creates, alters or drops a table refreshes the table list in every window open on the connection. **History** keeps the last 200 runs on the device, fewer once their text passes 2 MB, and drops the oldest first, so a script it shows is always whole. @@ -285,7 +285,7 @@ The **Status** row in **Info** uses the same words: **Connected**, **Not Connect Turn on Face ID, Touch ID, or Optic ID under **Settings > Security**. A cold launch always asks, and the connection from your last session waits behind that question: no connecting screen, no host key prompt, nothing dialed until you authenticate. After that **Auto-Lock** relocks immediately or after 1, 5, 15, or 60 minutes idle, starting at 5. The lock covers open sheets and connections, and the app switcher shows a locked card instead of your data; a connection open underneath stays connected. Turning the lock off asks you to authenticate first. -Each connection carries its own [safe mode](/features/safe-mode) level, synced from the Mac. Set it with **Safe Mode** under **Organization** in the connection's form. iOS has three: **Off**, **Confirm Writes**, and **Read-Only**, which refuses writes outright. On PostgreSQL, MySQL, MariaDB, OceanBase and Oracle, Read-Only also refuses a query that calls a function outside TablePro's list of built-ins, since such a function can write; switch to **Confirm Writes** to run it. **Default Safe Mode** under **Settings > New Connections** sets the level a new connection starts at. +Each connection carries its own [safe mode](/features/safe-mode) level, synced from the Mac. Set it with **Safe Mode** under **Organization** in the connection's form. iOS has three: **Off**, **Confirm Writes**, and **Read-Only**, which refuses writes outright. A read can still call a function that writes, such as `SELECT purge_orders()`. At Read-Only on PostgreSQL, MySQL 5.6.5 and later, and MariaDB 10.0 and later, **Query** runs each statement in the server's read-only transaction and then rolls it back. The server refuses a write the function makes in that transaction, and a setting it changes, as with `set_config`, is undone. What a function does outside the transaction still happens: `dblink_exec` writes over a connection of its own, and `pg_terminate_backend` and `GET_LOCK` act on the server. Some sessions cannot take the read-only transaction: OceanBase, Oracle, MySQL before 5.6.5, MariaDB before 10.0, and a session with a transaction or a `LOCK TABLES` open. A MySQL or MariaDB session with autocommit off has a transaction open after any statement. There, Read-Only refuses a query that calls a function outside TablePro's list of built-ins; switch to **Confirm Writes** to run it. **Default Safe Mode** under **Settings > New Connections** sets the level a new connection starts at. SSH tunnels authenticate with a password, a private key or **Keyboard Interactive**. A tunnel set to **SSH Agent** on the Mac signs in here with a private key on this device and stays **SSH Agent** on the Mac. When the server asks for more, after the password or key or through keyboard-interactive, a password prompt gets the SSH password and a code prompt gets the code from **Two-Factor Authentication**. Any other question, or a code in **Prompt at Connect** mode, appears on the connection's screen for you to answer. **Auto Generate** takes the Base32 secret from your authenticator setup with its algorithm, digits and period, and shares them with the Mac; a tunnel that follows a Mac SSH profile uses the profile's. A private key on a security key does not work here, and the **SSH Sign-In Unavailable** alert says so. An unknown host key, the SSH server's or a jump host's, prompts with its fingerprint first, on the connection's own screen. The question waits there until you answer it, and leaving the screen ends that attempt. A key pasted under **Paste Key**, or picked as a text file, is kept in the Keychain beside the connection's passwords, never in the saved connection list. A key file that is not text is copied into the app and read from there. Setting **Auth Method** to **Password**, choosing **Import File**, or turning **SSH Tunnel** off deletes the saved key when you tap **Save**. A tunnel the Mac forwards to a unix socket on the server forwards to the same socket here. Turning the tunnel off keeps its other settings, here and on the Mac, for when you turn it back on. A tunnel that drops while the connection is open reconnects it, as returning to the app does; see [When the connection drops](#when-the-connection-drops). From 200933fce7ef5904e0292e9f3aeec403b550b1ec Mon Sep 17 00:00:00 2001 From: Ngo Quoc Dat Date: Fri, 13 Nov 2026 08:11:05 +0700 Subject: [PATCH 2/2] docs(ios): say the read-only rollback undoes a setting on PostgreSQL only --- ios/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ios/index.mdx b/ios/index.mdx index 758a8e5..d29c890 100644 --- a/ios/index.mdx +++ b/ios/index.mdx @@ -285,7 +285,7 @@ The **Status** row in **Info** uses the same words: **Connected**, **Not Connect Turn on Face ID, Touch ID, or Optic ID under **Settings > Security**. A cold launch always asks, and the connection from your last session waits behind that question: no connecting screen, no host key prompt, nothing dialed until you authenticate. After that **Auto-Lock** relocks immediately or after 1, 5, 15, or 60 minutes idle, starting at 5. The lock covers open sheets and connections, and the app switcher shows a locked card instead of your data; a connection open underneath stays connected. Turning the lock off asks you to authenticate first. -Each connection carries its own [safe mode](/features/safe-mode) level, synced from the Mac. Set it with **Safe Mode** under **Organization** in the connection's form. iOS has three: **Off**, **Confirm Writes**, and **Read-Only**, which refuses writes outright. A read can still call a function that writes, such as `SELECT purge_orders()`. At Read-Only on PostgreSQL, MySQL 5.6.5 and later, and MariaDB 10.0 and later, **Query** runs each statement in the server's read-only transaction and then rolls it back. The server refuses a write the function makes in that transaction, and a setting it changes, as with `set_config`, is undone. What a function does outside the transaction still happens: `dblink_exec` writes over a connection of its own, and `pg_terminate_backend` and `GET_LOCK` act on the server. Some sessions cannot take the read-only transaction: OceanBase, Oracle, MySQL before 5.6.5, MariaDB before 10.0, and a session with a transaction or a `LOCK TABLES` open. A MySQL or MariaDB session with autocommit off has a transaction open after any statement. There, Read-Only refuses a query that calls a function outside TablePro's list of built-ins; switch to **Confirm Writes** to run it. **Default Safe Mode** under **Settings > New Connections** sets the level a new connection starts at. +Each connection carries its own [safe mode](/features/safe-mode) level, synced from the Mac. Set it with **Safe Mode** under **Organization** in the connection's form. iOS has three: **Off**, **Confirm Writes**, and **Read-Only**, which refuses writes outright. A read can still call a function that writes, such as `SELECT purge_orders()`. At Read-Only on PostgreSQL, MySQL 5.6.5 and later, and MariaDB 10.0 and later, **Query** runs each statement in the server's read-only transaction and then rolls it back. The server refuses a write the function makes in that transaction. On PostgreSQL, a setting it changes, as with `set_config`, is undone. What a function does outside the transaction still happens: `dblink_exec` writes over a connection of its own, and `pg_terminate_backend` and `GET_LOCK` act on the server. Some sessions cannot take the read-only transaction: OceanBase, Oracle, MySQL before 5.6.5, MariaDB before 10.0, and a session with a transaction or a `LOCK TABLES` open. A MySQL or MariaDB session with autocommit off has a transaction open after any statement. There, Read-Only refuses a query that calls a function outside TablePro's list of built-ins; switch to **Confirm Writes** to run it. **Default Safe Mode** under **Settings > New Connections** sets the level a new connection starts at. SSH tunnels authenticate with a password, a private key or **Keyboard Interactive**. A tunnel set to **SSH Agent** on the Mac signs in here with a private key on this device and stays **SSH Agent** on the Mac. When the server asks for more, after the password or key or through keyboard-interactive, a password prompt gets the SSH password and a code prompt gets the code from **Two-Factor Authentication**. Any other question, or a code in **Prompt at Connect** mode, appears on the connection's screen for you to answer. **Auto Generate** takes the Base32 secret from your authenticator setup with its algorithm, digits and period, and shares them with the Mac; a tunnel that follows a Mac SSH profile uses the profile's. A private key on a security key does not work here, and the **SSH Sign-In Unavailable** alert says so. An unknown host key, the SSH server's or a jump host's, prompts with its fingerprint first, on the connection's own screen. The question waits there until you answer it, and leaving the screen ends that attempt. A key pasted under **Paste Key**, or picked as a text file, is kept in the Keychain beside the connection's passwords, never in the saved connection list. A key file that is not text is copied into the app and read from there. Setting **Auth Method** to **Password**, choosing **Import File**, or turning **SSH Tunnel** off deletes the saved key when you tap **Save**. A tunnel the Mac forwards to a unix socket on the server forwards to the same socket here. Turning the tunnel off keeps its other settings, here and on the Mac, for when you turn it back on. A tunnel that drops while the connection is open reconnects it, as returning to the app does; see [When the connection drops](#when-the-connection-drops).