From c2344860d7061cd1babd81b2871478a23c37f1f7 Mon Sep 17 00:00:00 2001 From: Ngo Quoc Dat Date: Wed, 11 Nov 2026 20:20:18 +0700 Subject: [PATCH] docs(databases): parameter types, Oracle region zones, Teradata Stop, streamed exports --- databases/memcached.mdx | 2 +- databases/oracle.mdx | 6 ++++-- databases/sap-hana.mdx | 2 +- databases/teradata.mdx | 4 ++++ features/query-parameters.mdx | 12 ++++++++++++ 5 files changed, 22 insertions(+), 4 deletions(-) diff --git a/databases/memcached.mdx b/databases/memcached.mdx index 06312456..fea78e4f 100644 --- a/databases/memcached.mdx +++ b/databases/memcached.mdx @@ -46,7 +46,7 @@ The text protocol has no command that lists keys, so the list comes from one of | 1.4.31 and later, with the LRU crawler on (the default) | `lru_crawler metadump all`. Every key | | Older, or started with `-o no_lru_crawler` | `stats cachedump` per slab class. A sample: the server caps each slab's reply, so keys can be missing | -The table's comment says which one the connection uses. Neither is a snapshot: the server walks its LRU lists while it keeps moving items between them, so a key changed during the walk can be missing until the next refresh. A listing stops at 1,000,000 keys. Sorting is by key, and filters apply to **Key** only: `=`, `!=`, contains, starts with, ends with, `IN`, `NOT IN` and regex. Values are read with `get` for the rows on the current page. +The table's comment says which one the connection uses. Neither is a snapshot: the server walks its LRU lists while it keeps moving items between them, so a key changed during the walk can be missing until the next refresh. A listing stops at 1,000,000 keys, and an export that reaches it says it was cut there, unless keys expire or are evicted while it runs. Sorting is by key, and filters apply to **Key** only: `=`, `!=`, contains, starts with, ends with, `IN`, `NOT IN` and regex. Values are read with `get` for the rows on the current page. ## Editing diff --git a/databases/oracle.mdx b/databases/oracle.mdx index 368df804..a9794fd4 100644 --- a/databases/oracle.mdx +++ b/databases/oracle.mdx @@ -134,7 +134,7 @@ NCHAR, NVARCHAR2 and NCLOB read the same under either national character set Ora | BINARY_FLOAT, BINARY_DOUBLE | Native Swift Float/Double | | DATE | `YYYY-MM-DD HH:MM:SS` | | TIMESTAMP(p) | `YYYY-MM-DD HH:MM:SS` plus exactly p fractional digits | -| TIMESTAMP WITH TIME ZONE | As TIMESTAMP, followed by the value's own offset, such as `+02:00` | +| TIMESTAMP WITH TIME ZONE | As TIMESTAMP, followed by the value's own offset, such as `+02:00`, or by its region name, such as `Europe/Paris` | | TIMESTAMP WITH LOCAL TIME ZONE | As TIMESTAMP, in the session time zone, followed by that zone's offset | | INTERVAL DAY TO SECOND | `D HH:MM:SS` plus fractional seconds when non-zero (up to 9 digits, trailing zeros trimmed) | | INTERVAL YEAR TO MONTH | `Y-MM` | @@ -145,7 +145,9 @@ NCHAR, NVARCHAR2 and NCLOB read the same under either national character set Ora | REF | `` placeholder | | Object types, such as XMLTYPE and SDO_GEOMETRY | `` placeholder; a NULL object shows as NULL | -To read a geometry as text, select `SDO_UTIL.TO_WKTGEOMETRY(column)` instead of the column. A `TIMESTAMP WITH TIME ZONE` stored with a region name such as `Europe/Paris` shows ``; select `TO_CHAR(column, 'YYYY-MM-DD HH24:MI:SS.FF TZR')` to read it. +To read a geometry as text, select `SDO_UTIL.TO_WKTGEOMETRY(column)` instead of the column. + +A `TIMESTAMP WITH TIME ZONE` stored with a region name shows the wall clock in that region, then the name: `2026-01-01 00:00:00.000000 Europe/Paris`. The names come from the server's `V$TIMEZONE_NAMES`, read once per connection. When the account cannot read that view, or macOS does not know the region's name, the value shows in UTC with `+00:00`, the same instant without its region. Grant `SELECT` on `V_$TIMEZONE_NAMES` to see the names. Grid edits, deletes and filters spell dates and timestamps in a form that does not depend on the session's `NLS_DATE_FORMAT`, so they work whatever it is set to. A table without a primary key matches the row by every column, and an edit is refused when that match would need a LOB, LONG, BFILE, XMLTYPE, JSON, VECTOR or object value, since Oracle cannot compare those. diff --git a/databases/sap-hana.mdx b/databases/sap-hana.mdx index dc9162fc..b6c3cf37 100644 --- a/databases/sap-hana.mdx +++ b/databases/sap-hana.mdx @@ -115,7 +115,7 @@ Keep **Verify Identity** for HANA Cloud, whose certificates chain to DigiCert ro - Procedures, functions and triggers are not in the sidebar. Read one with `SELECT DEFINITION FROM SYS.PROCEDURES WHERE SCHEMA_NAME = 'APP' AND PROCEDURE_NAME = 'P'`, or from `SYS.FUNCTIONS` and `SYS.TRIGGERS` by their own name columns. - Every statement commits as it runs. A batch or a grid save that fails partway keeps the statements before the failure, so check what landed before running it again. A statement that binds a `BLOB`, `CLOB` or `NCLOB` value runs in a transaction of its own, which resets the session's `SET TRANSACTION` isolation level and access mode. - **matches regex** in the filter bar runs as a plain contains match. For a pattern, write `WHERE col LIKE_REGEXPR 'pattern'` in the SQL editor. -- A single result larger than 2 GiB fails with "The SAP HANA driver failed unexpectedly." Export and [Copy and duplicate](/features/copy-objects) read a whole table or result into memory before writing, and stop at 5,000,000 rows. Export a larger table in slices, with a `WHERE` on a key range or `LIMIT` and `OFFSET`. +- Export and [Copy and duplicate](/features/copy-objects) fetch rows from the server 1,000 at a time rather than the whole result first, with no row cap. A query that runs in the editor with no row limit reads its whole result first, stops at 5,000,000 rows, and fails with "The SAP HANA driver failed unexpectedly." past 2 GiB; export such a result instead. - [Compare & Sync](/features/compare-sync) is not available. - A `CALL` with query parameters runs, but its result sets are not shown, and a procedure with `OUT` parameters is refused. Write the arguments into the statement to see the result sets. diff --git a/databases/teradata.mdx b/databases/teradata.mdx index a58e18c0..81958dd0 100644 --- a/databases/teradata.mdx +++ b/databases/teradata.mdx @@ -46,6 +46,10 @@ A database and a user are both namespaces in Teradata, and both appear as top-le Identifiers are quoted with double quotes. Teradata has no `LIMIT`, so a table's first page comes back with `TOP` and later pages with `QUALIFY ROW_NUMBER()`. +## Stopping a query + +**Stop** keeps the session. A statement still running is aborted, and Teradata rolls back the transaction it ran in. With **Transaction Mode** set to `ANSI`, that is every change since the last `COMMIT`, and the tab says so. In `TERA` mode it is the statement alone, or every change since `BT` when one is open. On `DEFAULT` and `TERA` the tab shows no notice, even on a system that runs ANSI by default. A result already coming back is cut where it is, and nothing is rolled back. + ## SSL/TLS | Mode | What happens | diff --git a/features/query-parameters.mdx b/features/query-parameters.mdx index 2e868fd4..21e39523 100644 --- a/features/query-parameters.mdx +++ b/features/query-parameters.mdx @@ -32,6 +32,18 @@ Every parameter needs a value or NULL. Running with one empty stops with "Missin Where the driver has a parameter API the value is bound, never pasted into the text; everywhere else it is escaped. Either way you never quote a value yourself, and a `'` in a value is not an injection. +On Trino, Cloudflare R2 SQL and InfluxDB the value is written into the statement, and the type popup decides how: + +| Type | Written as | +|------|-----------| +| String | A plain number such as `42` or `-3.5` as a number, so `LIMIT :n` works. Anything else as quoted text, `00123` and `1E5` included | +| Integer | A whole number, `00123` included | +| Decimal | A number, `1E5` and `-3.5` included | +| Boolean | `TRUE` or `FALSE`, from `true`, `false`, `1`, `0`, `yes`, `no`, `on` or `off`. Flux reads only lower case, so write `true` in a Flux script instead | +| Date | Quoted text | + +A value that does not read as its type is sent as quoted text, and the server reports the mismatch. Teradata writes every value as quoted text, whatever its type. + ## What counts as a parameter `:name` is detected when `name` starts with a letter or underscore. These are not: