From 46ca2ccb26ef197a549642e69ed92bb24d6f23ac Mon Sep 17 00:00:00 2001 From: Ngo Quoc Dat Date: Tue, 3 Nov 2026 21:03:28 +0700 Subject: [PATCH 1/2] docs(features): restore availability, import Stop rollback and MCP disconnect refusal --- developers/mcp-tools.mdx | 2 +- features/change-tracking.mdx | 2 +- features/import-export.mdx | 2 ++ 3 files changed, 4 insertions(+), 2 deletions(-) diff --git a/developers/mcp-tools.mdx b/developers/mcp-tools.mdx index 8c21928..260185e 100644 --- a/developers/mcp-tools.mdx +++ b/developers/mcp-tools.mdx @@ -53,7 +53,7 @@ A call that has to open a connection with a pre-connect script also waits for th |------|-----------|---------| | `list_connections` | `purpose` (optional) | `connections[]` with `id`, `name`, `type`, `host`, `port`, `database`, `is_connected`, `ai_policy`, `external_access`, `safe_mode`, `tags`, plus `color` and `group` when set. `is_connected` is false once a connection stops answering, before it is disconnected | | `connect` | `connection_id` | `status` (`connected`), `connection_id`, `current_database`, plus `current_schema` and `server_version` when known. Returns once the driver is up | -| `disconnect` | `connection_id` | `status` (`disconnected`), `connection_id` | +| `disconnect` | `connection_id` | `status` (`disconnected`), `connection_id`. Refused with `denied` while the connection has running work, an open transaction or unsaved changes in TablePro, or when TablePro cannot tell whether a transaction is open | | `get_connection_status` | `connection_id` | `status` (`connected`, `connecting`, `disconnected`, `error`), `connection_id`, `current_database`, plus `current_schema`, `server_version`, `connected_at`, `last_active_at` and `error` when they apply | | `switch_database` | `connection_id`, `database` | `status` (`switched`), `connection_id`, `current_database` | | `switch_schema` | `connection_id`, `schema` | `status` (`switched`), `connection_id`, `current_schema` | diff --git a/features/change-tracking.mdx b/features/change-tracking.mdx index 63ffdc4..5b6fcc4 100644 --- a/features/change-tracking.mdx +++ b/features/change-tracking.mdx @@ -136,7 +136,7 @@ To drop the whole queue, choose **File > Discard Changes…** and confirm; a sta ## Restoring a save -**Edit > Restore Previous Values…**, or the same item under **Actions** in the toolbar, puts back what the rows held before the last save on the current table. It ships with no shortcut; bind one in **Settings > Keyboard**, under **Data Grid**. Pro license. +**Edit > Restore Previous Values…**, or the same item under **Actions** in the toolbar, puts back what the rows held before the last save on the current table. It ships with no shortcut; bind one in **Settings > Keyboard**, under **Data Grid**. Pro license. The item is dimmed while no values are kept for the current table. Values are kept on this Mac for 7 days, encrypted, and never synced. Turn the capture off, or delete what is stored, in **Settings > Data > Data Rewind**. diff --git a/features/import-export.mdx b/features/import-export.mdx index 4df6799..c57798b 100644 --- a/features/import-export.mdx +++ b/features/import-export.mdx @@ -316,6 +316,8 @@ The import runs on the connection's own session, and afterwards puts back the se On SQL Server a file that holds a `GO` line runs a batch at a time, cut at its `GO` lines the way `sqlcmd` cuts it, so every count and failure here is a batch rather than a statement. A file with no `GO` line runs a statement at a time. See [Scripts and batches](/databases/mssql#scripts-and-batches). +**Stop** in the progress sheet asks first. It says the import rolls back when the import runs in its own transaction, every target table rolls back, and nothing has committed yet. Otherwise it says what was already imported may stay. That covers MyISAM tables, a transaction you opened yourself, an engine without transactions, and a SQL file on MySQL, MariaDB or SQL Server, where `CREATE`, `ALTER`, `DROP` or a `GO` batch can commit on its own. + Skip and Continue collects up to 1,000 failures with their line numbers and messages, and the summary counts successes against failures behind a **Copy Details** button. **Save Report…** writes them all to a CSV with a line, a statement and the database's own error per row, so a large import's failures can be sorted and searched rather than scrolled. A stop shows the line, the database's own message, and the failing statement, with the dialog still open behind it, ready for a changed setting and another run. The alert shows the first 10,000 characters of a longer statement and the first five errors of a batch that raised more, and **Copy Details** copies all of them. ### Disabling foreign key checks From 3ac3a740b50ee45fa75f1c886e4e08df6db42de8 Mon Sep 17 00:00:00 2001 From: Ngo Quoc Dat Date: Tue, 3 Nov 2026 21:24:01 +0700 Subject: [PATCH 2/2] docs(features): drop the import Stop paragraph --- features/import-export.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/features/import-export.mdx b/features/import-export.mdx index c57798b..4df6799 100644 --- a/features/import-export.mdx +++ b/features/import-export.mdx @@ -316,8 +316,6 @@ The import runs on the connection's own session, and afterwards puts back the se On SQL Server a file that holds a `GO` line runs a batch at a time, cut at its `GO` lines the way `sqlcmd` cuts it, so every count and failure here is a batch rather than a statement. A file with no `GO` line runs a statement at a time. See [Scripts and batches](/databases/mssql#scripts-and-batches). -**Stop** in the progress sheet asks first. It says the import rolls back when the import runs in its own transaction, every target table rolls back, and nothing has committed yet. Otherwise it says what was already imported may stay. That covers MyISAM tables, a transaction you opened yourself, an engine without transactions, and a SQL file on MySQL, MariaDB or SQL Server, where `CREATE`, `ALTER`, `DROP` or a `GO` batch can commit on its own. - Skip and Continue collects up to 1,000 failures with their line numbers and messages, and the summary counts successes against failures behind a **Copy Details** button. **Save Report…** writes them all to a CSV with a line, a statement and the database's own error per row, so a large import's failures can be sorted and searched rather than scrolled. A stop shows the line, the database's own message, and the failing statement, with the dialog still open behind it, ready for a changed setting and another run. The alert shows the first 10,000 characters of a longer statement and the first five errors of a batch that raised more, and **Copy Details** copies all of them. ### Disabling foreign key checks