diff --git a/databases/bigtable.mdx b/databases/bigtable.mdx index 7c60db1..a25c0df 100644 --- a/databases/bigtable.mdx +++ b/databases/bigtable.mdx @@ -104,7 +104,7 @@ The table goes before the first slash, and the key is everything after it up to A request does not get the row cap in [Settings > Data](/customization/data-settings): a `READ` without `rowsLimit` returns up to 5,000,000 rows, so give it one. -For [Safe Mode](/features/safe-mode), `GET`, `SCAN` and `READ` are reads and every other request is a write. A `DELETE`, or a `PUT` that sets a cell to `null`, also raises the dangerous query warning on **Silent**. +For [Safe Mode](/features/safe-mode), `GET`, `SCAN` and `READ` are reads and every other request is a write. Each request names one row, so a `DELETE` or a `PUT` that sets a cell to `null` is a write like any other. ## SSL/TLS diff --git a/databases/etcd.mdx b/databases/etcd.mdx index 18dca6b..57dfc9f 100644 --- a/databases/etcd.mdx +++ b/databases/etcd.mdx @@ -77,7 +77,7 @@ The whole vocabulary is `get`, `put`, `del` (or `delete`), `watch`, `lease grant |---------|-------| | `get` | `--prefix`, `--limit=N`, `--keys-only`, `--order=ASCEND` or `DESCEND`, `--sort-by=KEY`, `VERSION`, `CREATE`, `MOD` or `VALUE`. Leave the last two out and the server's own ordering applies | | `put` | `--lease=ID` | -| `del` | `--prefix` | +| `del` | `--prefix`. Without it, `del` removes one key and counts as a write; with it, every key under the prefix, which counts as destructive. A range end or `--from-key` is refused | | `watch` | `--prefix`, `--timeout=SECONDS`, 30 by default. Events collect for that long, then arrive as a grid | | `lease timetolive` | `--keys` | diff --git a/databases/firebase.mdx b/databases/firebase.mdx index 72ccd86..d2b5787 100644 --- a/databases/firebase.mdx +++ b/databases/firebase.mdx @@ -116,7 +116,7 @@ Saving reads the document again and stops if it changed after you opened it, so | `PATCH users/alice?updateMask=age {"age": 31}` | Changes the named fields. Without `updateMask` the body replaces the document. Never creates one | | `DELETE users/alice` | Deletes a document | -`POST` and `PATCH` bodies use the **Edit Document** JSON, on the same line or the lines under it. There is no `PUT`. Write a space or any of `% ? # & = /` inside an ID as its percent escape, such as `GET users/John%20Doe`. `DELETE` raises the dangerous query warning even on **Silent**. Other writes follow the connection's [Safe Mode](/features/safe-mode) level. +`POST` and `PATCH` bodies use the **Edit Document** JSON, on the same line or the lines under it. There is no `PUT`. Write a space or any of `% ? # & = /` inside an ID as its percent escape, such as `GET users/John%20Doe`. A `DELETE` of anything but one document raises the dangerous query warning even on **Silent**. Other writes, a `DELETE` of one document included, follow the connection's [Safe Mode](/features/safe-mode) level. ## Realtime Database @@ -167,7 +167,7 @@ GET /chats?orderBy="$key"&limitToFirst=20 `GET`, `PUT`, `PATCH`, `POST` and `DELETE` take a path and, for writes, a JSON body on the same line or the lines under it. Query parameters apply to `GET` only, and a `PATCH` body is an object of the children to change. `PUT /` and `DELETE /` are refused: write or delete the root's children one at a time. -A `DELETE`, a `PUT` that leaves the node empty and a `PATCH` that sets a child to `null` raise the dangerous query warning even on **Silent**. Other writes follow the connection's [Safe Mode](/features/safe-mode) level. +A `DELETE`, `PUT` or `PATCH` that removes or replaces the root or a top-level node, which the sidebar lists as a table, raises the dangerous query warning even on **Silent**: a `PUT` there drops every record the new value does not hold. One that removes or replaces a node further down, one record or part of it, follows the connection's [Safe Mode](/features/safe-mode) level like any other write. ## Emulators diff --git a/databases/memcached.mdx b/databases/memcached.mdx index fea78e4..1a337dc 100644 --- a/databases/memcached.mdx +++ b/databases/memcached.mdx @@ -79,7 +79,7 @@ lru_crawler metadump all The whole vocabulary is `get`, `gets`, `gat`, `gats`, `set`, `add`, `replace`, `append`, `prepend`, `cas`, `touch`, `delete`, `incr`, `decr`, `flush_all`, `stats`, `version` and `lru_crawler metadump`. Anything else comes back as "Unsupported Memcached command" without reaching the server. Storage commands take ` `, the order of the text protocol. -Safe Mode reads `get`, `gets`, `version`, `stats` and `lru_crawler metadump` as reads, `delete` and `flush_all` as destructive, and everything else, `stats reset` included, as a write. +Safe Mode reads `get`, `gets`, `version`, `stats` and `lru_crawler metadump` as reads, `flush_all` as destructive, and everything else, `delete` and `stats reset` included, as a write. ## Server Dashboard diff --git a/databases/qdrant.mdx b/databases/qdrant.mdx index a13bc8d..8738b16 100644 --- a/databases/qdrant.mdx +++ b/databases/qdrant.mdx @@ -87,7 +87,7 @@ POST /collections/docs/points/query A response that lists points, from `query`, `scroll`, `search` or a retrieve by id, renders as a grid with `id`, then `score` when there is one, the payload fields, and any vectors returned. Anything else is shown as formatted JSON. -Read-only mode allows `GET`, `POST /collections/{name}/facet`, and the read endpoints under `/points`: `query`, `scroll`, `search`, `count`, `recommend`, `discover`, their batch and group forms, and a retrieve by id. A `DELETE`, a path ending in `delete` or `clear`, and `points/batch` count as destructive. A snapshot request is flagged as reaching the server's disk. +Read-only mode allows `GET`, `POST /collections/{name}/facet`, and the read endpoints under `/points`: `query`, `scroll`, `search`, `count`, `recommend`, `discover`, their batch and group forms, and a retrieve by id. Deleting one point by its ID, `POST /collections/{name}/points/delete` with `{"points": [7]}`, is a write. Any other `DELETE`, path ending in `delete` or `clear`, and `points/batch` count as destructive. A snapshot request is flagged as reaching the server's disk. ## SSL/TLS diff --git a/features/ai-assistant.mdx b/features/ai-assistant.mdx index 23d6eef..2f0cfd8 100644 --- a/features/ai-assistant.mdx +++ b/features/ai-assistant.mdx @@ -87,7 +87,7 @@ The mode picker in the composer footer controls which tools the AI can call. It | Mode | Tools available | When to use | |------|----------------|-------------| | **Ask** | Read-only schema lookups: `list_connections` (this conversation's connection only), `get_connection_status`, `list_databases`, `list_schemas`, `list_tables`, `describe_table`, `get_table_ddl`. | Questions, exploration, drafting queries you run yourself. | -| **Edit** | All Ask tools, plus `execute_query` for queries and data changes, such as `SELECT`, `INSERT`, `UPDATE`, `DELETE` and `MERGE`. It refuses schema, privilege, session and transaction commands, and changes to the database's own tables; run those in Agent mode or a query tab. [What Edit runs](#what-edit-runs) lists each engine. A function a query calls is not read, so it runs whatever it does. Destructive statements stay blocked. See [external query rules](/developers#what-read-only-allows). | Letting the AI run the queries it proposes. | +| **Edit** | All Ask tools, plus `execute_query` for queries and data changes, such as `SELECT`, `INSERT`, `UPDATE`, `DELETE` and `MERGE`. It refuses schema, privilege, session and transaction commands, and changes to the database's own tables; run those in Agent mode or a query tab. [What Edit runs](#what-edit-runs) lists each engine. A function a query calls is not read, so it runs whatever it does. Destructive statements stay blocked; deleting one document, row, key or record by its ID is a data change and runs. See [external query rules](/developers#what-read-only-allows). | Letting the AI run the queries it proposes. | | **Agent** | All tools, plus `confirm_destructive_operation` for destructive statements. Runs tools in a loop. | Multi-step migrations and schema changes. | Mode and [Safe Mode](/features/safe-mode) are independent gates. Agent mode does not bypass Safe Mode. @@ -99,7 +99,7 @@ Every engine follows one rule: reads, plus the commands that change data. Anythi | Database | Runs besides reads | Refused, for example | |------|------|------| | SQL databases, DynamoDB | `INSERT`, `UPDATE`, `DELETE`, `MERGE`, `UPSERT`, `REPLACE INTO`, DynamoDB item requests | `CREATE`, `ALTER`, `GRANT`, `SET`, `BEGIN`, `CALL`, rows of `pg_settings`, `mysql.user` or `msdb` | -| Cassandra, ScyllaDB | `INSERT`, `UPDATE`, `DELETE` and a `BATCH` of them | `CREATE ROLE`, `GRANT`, `USE`, rows of `system_auth`, `system_views` or ScyllaDB's `system` | +| Cassandra, ScyllaDB | `INSERT`, `UPDATE`, `DELETE` and a `BATCH` of them | `CREATE ROLE`, `GRANT`, `USE`, rows of `system_auth`, `system_views`, or ScyllaDB's `system` and `audit` | | SurrealDB | `CREATE`, `INSERT`, `UPDATE`, `UPSERT`, `DELETE`, `RELATE` | `DEFINE`, `ALTER`, `REMOVE`, `USE`, `LET`, `BEGIN`, a `fn::` or `api::` call | | MongoDB | `insertOne`, `insertMany`, `updateOne`, `updateMany`, `replaceOne`, `findOneAndUpdate`, `bulkWrite`, and the `insert`, `update` and `findAndModify` commands | `createIndex`, `createCollection`, `use`, `killOp`, writes into `admin`, `config`, `local` or a `system.` collection | | Redis | Writes to strings, hashes, lists, sets, sorted sets, streams, bitmaps, geo, HyperLogLog, JSON, time series, probabilistic types and vector sets | `ACL`, `CLIENT`, `SELECT`, `MULTI`, `PUBLISH`, `FT.CREATE`, `TS.CREATERULE`, `SLOWLOG RESET` | @@ -108,7 +108,7 @@ Every engine follows one rule: reads, plus the commands that change data. Anythi | Typesense, Qdrant, Weaviate | Document, point and object writes | Collection and schema changes, API keys, users, aliases, snapshots | | etcd | `put`, `create`, `lease grant`, `lease keep-alive` | `user add`, `role add`, `user grant-role`, `auth enable` | | Memcached | Storage commands, `touch`, `incr`, `decr`, `gat` | `stats reset`, `stats detail on` | -| Kafka | `PRODUCE` | `DROP TOPIC`, which counts as destructive | +| Kafka | `PRODUCE` | `DROP TOPIC`, which counts as destructive, and `PRODUCE` into a topic another service keeps its state in: a name starting with `_` or `.`, such as `_schemas`, Kafka Connect's `connect-configs`, `connect-offsets` and `connect-status`, MirrorMaker 2's `.internal` topics, and Kafka Streams topics ending in `-changelog` or `-repartition` | | Firestore, Realtime Database, Bigtable | Document, path and row writes | A Realtime Database path through a key that starts with `.`, such as `.settings` | ### Tool calling diff --git a/features/safe-mode.mdx b/features/safe-mode.mdx index 1121663..364fb3f 100644 --- a/features/safe-mode.mdx +++ b/features/safe-mode.mdx @@ -24,7 +24,7 @@ Four things the table cannot carry. The confirmation dialog shows the whole stat Confirmation dialog over a query tab, showing a fourteen line UPDATE with Cancel and Execute Confirmation dialog over a query tab, showing a fourteen line UPDATE with Cancel and Execute - **Silent** is not a free pass: `DROP`, `TRUNCATE`, `CREATE OR REPLACE` of a table, schema or database, `INSERT OVERWRITE`, and a `DELETE` with no `WHERE` still raise the built-in dangerous query warning even there. So does a [Structure](/features/table-structure#saving-changes) save that drops a column, changes a column's type or character set, adds NOT NULL, changes the primary key, adds or rewrites a check constraint, converts a table's existing columns to another character set, or removes a MongoDB field. And **Read-Only** goes past queries to the interface itself, disabling inline cell editing, adding, deleting and duplicating rows, table truncate and drop, and import. + **Silent** is not a free pass: `DROP`, `TRUNCATE`, `CREATE OR REPLACE` of a table, schema or database, `INSERT OVERWRITE`, and a `DELETE` with no `WHERE` still raise the built-in dangerous query warning even there. On an engine without SQL, so do deleting an index, a collection, a table, many items at once or the items a query or prefix matches; deleting one item by its ID is an ordinary write. So does a [Structure](/features/table-structure#saving-changes) save that drops a column, changes a column's type or character set, adds NOT NULL, changes the primary key, adds or rewrites a check constraint, converts a table's existing columns to another character set, or removes a MongoDB field. And **Read-Only** goes past queries to the interface itself, disabling inline cell editing, adding, deleting and duplicating rows, table truncate and drop, and import. ## Connections that are always read-only @@ -54,7 +54,7 @@ A statement runs as a read only when TablePro can tell for certain that it reads A read can still call a function that writes, such as `SELECT purge_orders()`. At **Read-Only** on PostgreSQL, PGlite, CockroachDB, KingbaseES, MySQL, MariaDB, SQLite, DuckDB and ClickHouse, the server refuses that write. Every read TablePro runs for you there runs in the engine's own read-only mode: Run, Run Selection, Run All, Explain, opening a table or view with its row counts and page turns, Fetch All, exports, Transfer, Data Compare, Copy Objects and dashboard tiles. Run All then opens no transaction of its own, and a SQL export reads table by table with no snapshot across tables. DuckDB and KingbaseES do this once their plugin in **Settings > Extensions** is updated for this release. -Oracle, Dameng and OceanBase have no such mode, and their functions can write. At **Read-Only** there, a query that calls a function outside TablePro's list of built-ins is blocked, and so is a raw filter or the filter of an export, a Transfer, a Data Compare or a Copy Objects, before any row is read. The message names the level to switch to: **Alert**, or the lowest level a [configuration profile](#managed-by-an-organization) or Agent mode still offers, and it says the level is held when nothing below Read-Only is offered. Below Read-Only the query counts as a read, so only the two Full levels ask before it runs. The automatic row count of such a browse shows no total. +Oracle, Dameng and OceanBase have no such mode, and their functions can write. At **Read-Only** there, a query that calls a function outside TablePro's list of built-ins is blocked, and so is a raw filter or the filter of an export, a Transfer, a Data Compare or a Copy Objects, before any row is read. The message names the level to switch to: **Alert**, or the lowest level a [configuration profile](#managed-by-an-organization) or Agent mode still offers, and it says the level is held when nothing below Read-Only is offered. Below Read-Only the query counts as a read, so only the two Full levels ask before it runs. The automatic row count of such a browse shows no total. On Oracle, `MATCH_RECOGNIZE` runs: inside it `PREV`, `NEXT`, `FIRST`, `LAST`, `CLASSIFIER` and `MATCH_NUMBER` are the clause's own, and outside it they are your functions. Oracle and Dameng also run a function named without parentheses, as in `SELECT purge_orders FROM dual`, when no table the query reads has a column of that name. At **Read-Only** that name is blocked like a call: the database's own catalog says which names the session can call, read again at most once a minute per schema. A name that is a column of a table in the query, or a select-list alias in `ORDER BY`, runs. A dotted name that no table in the query starts, such as `pkg.purge_orders`, is blocked without asking the catalog. When the catalog cannot be read, the query is blocked. diff --git a/features/server-dashboard.mdx b/features/server-dashboard.mdx index 664df4d..8f9d510 100644 --- a/features/server-dashboard.mdx +++ b/features/server-dashboard.mdx @@ -74,7 +74,7 @@ What the tile draws depends on what comes back: A tile fetches at most 2,000 rows, the most a chart draws, so a query that returns a whole table costs one page of it per refresh. -A tile runs one statement, and only a read. A saved query that writes, holds more than one statement, or reads files on the server is refused on the tile with the reason and never runs. So is every tile on a connection whose [Safe Mode level](/features/safe-mode#levels) asks before reads, **Alert (Full)** and **Safe Mode (Full)**, since nobody is there to confirm a refresh. +A tile runs one statement, and only a read, on the connection's own session: it waits for a statement a query tab is running there, and runs in the database and schema the session was on when the tile was checked. A saved query that writes, holds more than one statement, or reads files on the server is refused on the tile with the reason and never runs. So is every tile on a connection whose [Safe Mode level](/features/safe-mode#levels) asks before reads, **Alert (Full)** and **Safe Mode (Full)**, since nobody is there to confirm a refresh. Each tile refreshes with the dashboard unless you slow it down: open its **Tile Options** menu, the circled ellipsis, and pick **Every Minute**, **Every 5 Minutes**, **Every 15 Minutes**, or **Every Hour** under **Refresh**. An expensive count then runs once a minute instead of every second. A failed run keeps the last result on the tile and shows the error beneath it.