diff --git a/connections/connection-form.mdx b/connections/connection-form.mdx index 7d46986..7c61659 100644 --- a/connections/connection-form.mdx +++ b/connections/connection-form.mdx @@ -98,6 +98,8 @@ session picks it up. **Color** marks the connection in the connection list and its window. **Tags** and **Group** decide where it sits in the welcome window's tree. +Type a tag's name in **Tags** and press `Return` to add it: known tags complete as you type, and a new name becomes a new gray tag. Select a tag and press `Delete` to remove it. The tag menu beside the field shows each tag's color, and holds **Create New Tag…** for a tag with a color of your choice and **Manage Tags** to delete one. + ## Startup commands Statements split on semicolons and newlines outside quotes and comments, and run in order on the connection that just opened, after every connect including an automatic reconnect. They all run on one connection, so write one dialect. diff --git a/customization/general-settings.mdx b/customization/general-settings.mdx index 4a67466..bc15e11 100644 --- a/customization/general-settings.mdx +++ b/customization/general-settings.mdx @@ -3,7 +3,7 @@ title: General Settings description: Language, startup behavior, tabs, sidebar layout, connections, query timeout, the command line tool, updates, and reset --- -Most of this tab takes effect the moment you click. Language waits for a restart, and the query timeout reaches a connection only when that connection opens. +Most of this tab takes effect the moment you click. Language waits for a relaunch, and the query timeout reaches a connection only when that connection opens. General settings tab @@ -12,7 +12,7 @@ Most of this tab takes effect the moment you click. Language waits for a restart ## Language -System (the default), English, Tiếng Việt, 简体中文, 繁體中文, 한국어, Türkçe, Français. The tab tells you to restart once you pick a different one. +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 diff --git a/customization/notifications.mdx b/customization/notifications.mdx index 0dd0eb6..235a144 100644 --- a/customization/notifications.mdx +++ b/customization/notifications.mdx @@ -33,4 +33,4 @@ A tab whose work finished while you were looking elsewhere carries a dot beside ## Permission -macOS asks the first time there is actually something to tell you, not at launch. Refuse, or turn TablePro off in **System Settings > Notifications**, and this tab says so with a button that opens the right pane; TablePro bounces its Dock icon in place of the banner. Sound and alert style are per-app System Settings options, so this tab does not repeat them. +macOS asks the first time there is actually something to tell you, not at launch. Refuse, or turn TablePro off in **System Settings > Notifications**, and this tab says so with a button that opens the right pane, and catches up when you switch back to TablePro; TablePro bounces its Dock icon in place of the banner. Sound and alert style are per-app System Settings options, so this tab does not repeat them. diff --git a/databases/oracle.mdx b/databases/oracle.mdx index d481994..368df80 100644 --- a/databases/oracle.mdx +++ b/databases/oracle.mdx @@ -177,7 +177,7 @@ The SSL mode offers no certificate rows there, so **Verify Identity** checks the ### ORA-28002: the password will expire within … days -The login worked, and the password is in its grace period. Oracle AI Database 26ai sends `ORA-28098: Profile limits PASSWORD_LIFE_TIME and PASSWORD_GRACE_TIME are not unlimited, password will expire within … days.` instead. The message stays in a yellow banner above the editor until you dismiss it, and comes back on every connect. Change the password with `ALTER USER name IDENTIFIED BY "new password"`, or ask the DBA to, before the grace period ends: after that the login fails with ORA-28001. +The login worked, and the password is in its grace period. Oracle AI Database 26ai sends `ORA-28098: Profile limits PASSWORD_LIFE_TIME and PASSWORD_GRACE_TIME are not unlimited, password will expire within … days.` instead. The message stays in a bar above the editor until you dismiss it, and comes back on every connect. Change the password with `ALTER USER name IDENTIFIED BY "new password"`, or ask the DBA to, before the grace period ends: after that the login fails with ORA-28001. ### PROCEDURE … was created with compilation errors diff --git a/features/ai-assistant.mdx b/features/ai-assistant.mdx index db57636..913d6c4 100644 --- a/features/ai-assistant.mdx +++ b/features/ai-assistant.mdx @@ -29,7 +29,7 @@ Open **Settings > AI** (`Cmd+,`). **Enable AI Features** at the top gates the wh -The **Active Provider** picker decides which one handles requests. Setting it to **None** leaves any open conversation readable but read-only, with a **Settings…** button under it. Where a model supports reasoning effort, its detail sheet adds a picker for it and replies render their thinking in a collapsible **Reasoning** block. Gemini and Ollama have no picker, and on a router the picker follows the model: it is gone for a model the router lists as non-reasoning. +Each provider's row says whether it can answer: **API key set**, **Signed in as …**, **Local** or the server's host when it is ready, and **Needs an API key**, **Not signed in** or **Claude Code not installed**, with a warning symbol, when it needs you. A GitHub Copilot error shows there too. The **Active Provider** picker decides which one handles requests. Setting it to **None** leaves any open conversation readable but read-only, with **No AI Provider** and a **Settings…** button under it. Where a model supports reasoning effort, its detail sheet adds a picker for it and replies render their thinking in a collapsible **Reasoning** block. Gemini and Ollama have no picker, and on a router the picker follows the model: it is gone for a model the router lists as non-reasoning. With no preference, start with Claude or OpenAI on an API key: both take a key, tools, and images with no further setup. The others each come with something to know. diff --git a/features/mcp.mdx b/features/mcp.mdx index 09dfe5d..e4f8e83 100644 --- a/features/mcp.mdx +++ b/features/mcp.mdx @@ -14,13 +14,13 @@ This page covers the **Settings > MCP** pane. The protocol itself, the tool cata ## Starting and stopping -Open **Settings > MCP** and turn on **Enable MCP Server**. The **Status** row underneath is how you check it before touching a client config: it reads **Running on port 23508**, or **Stopped**, or the reason it failed. +Open **Settings > MCP** and turn on **Enable MCP Server**. The **Status** row underneath is how you check it before touching a client config: it reads **Running on port 23508**, or **Stopped**, or **Couldn't start** with the reason below it. **Try Again** beside a failure starts the server again. With the toggle off, nothing starts the server. A client that launches the bundled `tablepro-mcp` bridge gets "The TablePro MCP server is turned off" within a second instead of a timeout, and pairing an extension stops at the same message with **Open MCP Settings**. While it is only answering a client, TablePro stays out of the Dock and the app switcher. It appears in both, with its menu bar, once it has a window on screen, including one a client asked it to open. A TablePro the bridge launched while the toggle is off quits again. -The default port is **23508**. If it is taken, TablePro asks the kernel for a free one instead. Either way the real port goes to `~/Library/Application Support/TablePro/mcp-handshake.json`, which the bridge reads, so a client config never carries a port. +The default port is **23508**. If it is taken, TablePro asks the kernel for a free one instead, and the **Status** row says the port you set was in use. Either way the real port goes to `~/Library/Application Support/TablePro/mcp-handshake.json`, which the bridge reads, so a client config never carries a port. ## Server configuration diff --git a/features/plugins.mdx b/features/plugins.mdx index eec8ed0..354192d 100644 --- a/features/plugins.mdx +++ b/features/plugins.mdx @@ -77,13 +77,13 @@ Offline, the check waits and runs once the Mac is back online. If the registry h Bundled plugins update with the app. A plugin installed from a file, including one installed over a registry plugin, updates from the registry only when an app update leaves it rejected and the registry has a compatible build of it. -An app update can raise the plugin interface version. A plugin built for an older one is rejected at load instead of crashing, and stays in a banner in **Settings > Extensions** with the reason and an action until it is repaired: +An app update can raise the plugin interface version. A plugin built for an older one is rejected at load instead of crashing. It stays under **Couldn't Load** in the plugin list of **Settings > Extensions** until it is repaired. Select it to see the reason and the action: | Action | Meaning | |--------|---------| | **Update Now** | A compatible build is in the registry. One click installs it. | | **Check for Updates…** | The plugin requires a newer app version. Once one is found or downloaded, the button reads **Update Available…** or **Relaunch to Update**, as the app menu does. | -| No button | No compatible build is published yet. The update check keeps trying. | +| **Try Again** | No compatible build was found, or the registry could not be reached. The update check also keeps trying on its own. | | **Remove** | Deletes the rejected plugin from disk. | ## Managing plugins @@ -93,7 +93,7 @@ In **Settings > Extensions**: - **Uninstall** removes a user-installed plugin from disk. Bundled plugins cannot be uninstalled. - The detail pane shows version, bundle ID, capabilities, database type, and default port. Plugins with their own settings show them here. -macOS cannot fully unload a plugin's code, so removing one leaves a banner: "Relaunch TablePro to finish removing plugins." **Relaunch** quits, reopens your last session, and installs an app update that already downloaded. +macOS cannot fully unload a plugin's code, so removing one adds a row at the top of the list: "Relaunch to finish removing plugins." **Relaunch** quits, reopens your last session, and installs an app update that already downloaded. Saved connections survive a removal. A connection whose driver cannot load stays in the list, and opening it lands on "Could not connect" with the button for the cause: diff --git a/features/table-operations.mdx b/features/table-operations.mdx index 3781311..4e9bb11 100644 --- a/features/table-operations.mdx +++ b/features/table-operations.mdx @@ -90,6 +90,8 @@ Each operation lists the object kinds it applies to, so a view offers only the o PostgreSQL VACUUM carries FULL (rewrites the table and blocks access), ANALYZE, and VERBOSE toggles. MySQL CHECK TABLE offers QUICK, FAST, MEDIUM (the default), EXTENDED, and CHANGED. The options come from the driver, so an engine that adds one shows it without an app change. No other engine reports maintenance operations, so the submenu is hidden there, and in read-only safe mode. +A run that comes back clean shows nothing more. When the server answers with a note, such as MySQL's "Table does not support optimize, doing recreate + analyze instead" or a problem SQLite's integrity check found, a sheet lists it. + ## Generate test rows Right-click a table and choose **Generate Rows…** to fill it with made-up data. Set the number of rows, from 1 to 1,000,000, pick a generator for each column on the left, and check the first 10 rows in the preview before anything runs. diff --git a/images/connection-customization-dark.png b/images/connection-customization-dark.png index 4fde35d..9f640b6 100644 Binary files a/images/connection-customization-dark.png and b/images/connection-customization-dark.png differ diff --git a/images/connection-customization.png b/images/connection-customization.png index d6e5b6a..a85a98a 100644 Binary files a/images/connection-customization.png and b/images/connection-customization.png differ