diff --git a/databases/cassandra.mdx b/databases/cassandra.mdx index af8e1e8..85d37cd 100644 --- a/databases/cassandra.mdx +++ b/databases/cassandra.mdx @@ -101,6 +101,8 @@ The filter bar offers **Match all** only, because CQL has no `OR`, and **Search An edited value is sent as its column's type, so it has to read as one: a number for `int` or `decimal`, a UUID for `uuid`, `0x…` for `blob`. A `timestamp` takes the form the grid shows, the form cqlsh prints, a date alone, or milliseconds since 1970, and one with no zone is read as UTC. A value that does not parse is refused and nothing in the save is written. `list`, `set`, `map`, `tuple`, user-defined types and `duration` cannot be edited in the grid: write an `UPDATE` in the CQL editor. +An edited cell keeps the time to live it had left. Browsing reads each cell's `TTL`, and the save writes `USING TTL` with what remains, or `USING TTL 0` for a cell that never expires in a table with a default TTL. Cells with different TTLs in one row are written in one conditional `BATCH`, and undoing a delete puts each cell back with the TTL it had left. + Each row in a save is written by its own statement, named by its whole primary key, so deleting several rows sends one `DELETE` each. **Add Row** writes `INSERT … IF NOT EXISTS`: a new row whose key is already taken is refused rather than written over the row that holds it. A primary key column cannot be edited in place. Delete the row and add it again with the new key. Results in the CQL editor are read-only. Open the table from the sidebar to edit its rows. diff --git a/databases/elasticsearch.mdx b/databases/elasticsearch.mdx index fce244b..0e15731 100644 --- a/databases/elasticsearch.mdx +++ b/databases/elasticsearch.mdx @@ -55,7 +55,7 @@ Columns come from the index mapping. `object` fields flatten to dotted paths suc Column filters translate to `term`, `range`, `wildcard`, `terms` and `exists`. Two filter rows on leaves of the same array match two different objects unless you set both rows to the same element. The **Raw SQL** filter column is the exception: its text goes over as a `query_string`, so write Lucene there, `name:Widget` or `price:>10`, matched across all fields. Sorting a `text` field targets its `.keyword` subfield when the mapping has one. A nested leaf sorts and filters; its JSON parent column does neither. -Grid edits become REST calls keyed by `_id`: `POST /index/_update/{id}`, `PUT /index/_doc/{id}` and `DELETE /index/_doc/{id}`. Edit a nested array through its JSON parent column. A value typed into one of its leaf columns, in an existing document or a new one, cannot be written, so Save stops, names that column, and sends nothing until you undo the edit. +Grid edits become REST calls keyed by `_id`: `POST /index/_update/{id}`, `PUT /index/_doc/{id}` and `DELETE /index/_doc/{id}`. An update or delete goes to the index the document was read from and carries its `routing`, so a child document of a `join` field, or one indexed with custom routing, is changed on its own shard. In a `text` or `keyword` field, a value that reads as a JSON array is saved as an array only when the field already holds one; otherwise it stays a string. A new row saves it as an array unless the rows read held such a string in that field. Edit a nested array through its JSON parent column. A value typed into one of its leaf columns, in an existing document or a new one, cannot be written, so Save stops, names that column, and sends nothing until you undo the edit. Deleting an index from the sidebar sends `DELETE /`, the request the confirmation shows. @@ -89,7 +89,7 @@ New connections start on **Disabled**, plain HTTP with no fallback to anything e - The sidebar lists concrete indices only, and hides every name beginning with `.`. Aliases and data streams do not appear; address them by name in the console. - Sorting on `_id`, or on a `text` field with no `.keyword` subfield, does nothing: the column is dropped from the sort and the rows keep the order they had. Add the subfield, or sort a keyword field. - Paging past 10,000 documents switches to `search_after` over a point-in-time. That threshold is fixed, so an index with a lowered `max_result_window` errors before the switch; raise the index setting back to 10,000. -- An array or object cell is cut at 10,000 characters and ends in `...`. Saving an edit to a cut cell stores the fragment; change long values in the console. +- An array or object cell is cut at 10,000 characters and ends in `...`. Saving an edit to a cut cell is refused; change long values in the console. - Truncate is not offered. The nearest thing Elasticsearch has is `_delete_by_query`, which runs asynchronously and reports conflicts per document. Run it in the console. - No mapping or schema editing, no transactions, no import. - OpenSearch is not supported. diff --git a/databases/mongodb.mdx b/databases/mongodb.mdx index c6f0ec7..69ae7f3 100644 --- a/databases/mongodb.mdx +++ b/databases/mongodb.mdx @@ -80,9 +80,9 @@ Over an SSH tunnel only the first host is used and the rest of the list is dropp ## Browsing collections -Click a collection to page through its documents. The columns are the fields in the documents on screen, then any field the collection's `$jsonSchema` validator declares that none of them hold, so an empty collection still shows the fields it was created with. A top-level ObjectId renders as its hex string. A nested object or array shows as Extended JSON in the order it is stored: `{"$oid": "…"}`, `{"$date": "2024-05-01T10:00:00.123Z"}`, `{"$numberLong": "5"}`, and `3.0` for a double that holds a whole number. +Click a collection to page through its documents. The columns are the fields in the documents on screen, then any field the collection's `$jsonSchema` validator declares that none of them hold, so an empty collection still shows the fields it was created with. A top-level ObjectId renders as its hex string. A nested object or array shows as Extended JSON in the order it is stored: `{"$oid": "…"}`, `{"$date": "2024-05-01T10:00:00.123Z"}`, `{"$numberLong": "5"}`, and `3.0` for a double that holds a whole number. Sorting by a column also sorts by `_id` last, so documents that share a value keep one order from page to page. -An edited cell keeps its field's type. A date stays a date, whether typed as `2024-01-02T03:04:05Z`, as `2024-01-02`, or picked in the date picker, which writes your local time. An ObjectId stays an ObjectId, an integer past 2^53 is sent as a 64-bit integer, and a field the validator declares as `string` is written as text even when it reads `123` or `true`. Where the grid has no type to go on, `123` is a number and `{"a": 1}` a document; text that only looks like JSON is written as a string. +An edited cell keeps its field's type. A number keeps the type the cell was read as, so editing a double in a field that mostly holds int32 values saves a double. A date stays a date, whether typed as `2024-01-02T03:04:05Z`, as `2024-01-02`, or picked in the date picker, which writes your local time. An ObjectId stays an ObjectId, an integer past 2^53 is sent as a 64-bit integer, and a field the validator declares as `string` is written as text even when it reads `123` or `true`. Where the grid has no type to go on, `123` is a number and `{"a": 1}` a document; text that only looks like JSON is written as a string. Editing a nested object or array writes only the paths that changed, such as `address.city` or `tags.1`, so every other value in it keeps its type and its place. Adding two keys at once, reordering keys, or changing an array's length writes the whole value instead. A binary cell keeps its BSON subtype when its bytes are edited, and a duplicated or pasted row keeps its binary fields. diff --git a/databases/redis.mdx b/databases/redis.mdx index 01ea5a3..c72d7be 100644 --- a/databases/redis.mdx +++ b/databases/redis.mdx @@ -97,22 +97,22 @@ The grid columns are **Key**, **Type**, **TTL**, **Length**, and **Value**. Valu | Type | Value column | Length column | |---|---|---| -| String | The entire value, however long | `STRLEN`, in bytes | +| String | The first 64 KB; a longer value ends in `...` | `STRLEN`, in bytes | | Hash | First 100 fields, as a JSON object | `HLEN` | | List | First 100 elements, as a JSON array | `LLEN` | | Set | First 100 members, as a JSON array | `SCARD` | | Sorted set | First 100 `[member, score]` pairs | `ZCARD` | | Stream | Newest 5 entries, as `[id, fields]` | `XLEN` | -A value that is not valid UTF-8, such as a gzip or MessagePack payload, opens in the hex editor instead of as text. +A value that is not valid UTF-8, such as a gzip or MessagePack payload, opens in the hex editor instead of as text. Exporting the keys writes every string whole. A **Type**, **TTL**, **Length** or **Value** cell is NULL when the server will not say for your user. ACL key patterns do not filter `SCAN`, so a user limited to `~app:*` still sees every key name, and a **Value** edit on a key whose **Type** is NULL stops the save. ### Editing -Editing a **Key** cell runs `RENAME`. Editing a **TTL** cell runs `EXPIRE`, or `PERSIST` when you clear it or set it to `-1` or NULL; in that column `-1` means no expiry and `-2` means the key is gone. Editing a **Value** cell runs `SET`, and only on a string, since a preview of a hash or list is not the whole structure. +Editing a **Key** cell runs `RENAME`. Editing a **TTL** cell runs `EXPIRE`, or `PERSIST` when you clear it or set it to `-1` or NULL; in that column `-1` means no expiry and `-2` means the key is gone. Editing a **Value** cell runs `SET`, and only on a string the grid shows whole, since a preview of a hash or list, or the start of a long string, is not the whole value. -Save sends nothing, names the reason and keeps your edits when a row holds an edit these commands cannot make: a **Value** edit on any type but a string, a NULL **Value**, a **Type** edit, or a **TTL** that is not a whole number of seconds above 0. +Save sends nothing, names the reason and keeps your edits when a row holds an edit these commands cannot make: a **Value** edit on any type but a string or on a string longer than 64 KB, a NULL **Value**, a **Type** edit, a **TTL** that is not a whole number of seconds above 0, or a new row copied from a key the grid shows only in part. Change the other types with a command: `HSET myhash field1 "value1"` rewrites one field and leaves the rest alone. Adding a row does follow the type you pick, generating `HSET`, `RPUSH`, `SADD`, `ZADD`, or `SET`; any other type stops the save. diff --git a/databases/surrealdb.mdx b/databases/surrealdb.mdx index 61c3522..20d7980 100644 --- a/databases/surrealdb.mdx +++ b/databases/surrealdb.mdx @@ -62,6 +62,7 @@ Right-click a namespace for **Drop Namespace…** (`REMOVE NAMESPACE`) or a data Changing a cell runs an `UPDATE` that sets only the fields you touched, leaving computed `FUTURE` fields and another writer's changes alone. Values go out as typed parameters, so an `int` stays an `int` and a filter value is never parsed as SurrealQL. - `id` is the primary key and read-only. Leave it empty on a new row for a generated one, or type `table:id` to choose it. +- A record whose id is a UUID, an array or an object is saved by that id. In a query result, such a record cannot be edited or deleted, since its id reads the same as a string id; open the table to change it. - A record link shows as `table:id`. Objects and arrays show as compact JSON and are edited as JSON. - On a `RELATION` table, `in` and `out` sit next to `id`. - A `SCHEMALESS` table has no declared fields, so its columns come from the rows fetched: a field only some records carry still gets a column, and the rest show an empty cell.