Skip to content

[DDSQL] data type and type literal doc updates #31404

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bradbesserman merged 2 commits into from
Sep 2, 2025
Merged

[DDSQL] data type and type literal doc updates #31404

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b7ac677
[DDSQL] data type and type literal doc updates
bradbesserman Sep 2, 2025
c04f1bd
explicit type prefix sentence phrasing
bradbesserman Sep 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/en/ddsql_reference/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,7 @@ DDSQL supports the following data types:

### Array types

All data types except `JSON` support array types. Arrays can contain multiple values of the same data type.
All data types support array types. Arrays can contain multiple values of the same data type.

## Type literals

Expand All @@ -123,7 +123,7 @@ DDSQL supports explicit type literals using the syntax `[TYPE] [value]`.
| `TIMESTAMP` | `TIMESTAMP 'value'` | `TIMESTAMP '2023-12-25 10:30:00'` |
| `VARCHAR` | `VARCHAR 'value'` | `VARCHAR 'hello world'` |

The type prefix can be omitted and the type is automatically inferred from the value. For example, `'hello world'` is inferred as `VARCHAR`, `123` as `BIGINT`, and `true` as `BOOLEAN`.
The type prefix can be omitted and the type is automatically inferred from the value. For example, `'hello world'` is inferred as `VARCHAR`, `123` as `BIGINT`, and `true` as `BOOLEAN`. Use explicit type prefixes when values could be ambiguous; for example,`TIMESTAMP '2025-01-01'` would be inferred as `VARCHAR` without the prefix.

### Array literals

Expand All @@ -145,7 +145,7 @@ SELECT
price * DOUBLE 1.08 AS price_with_tax,
created_at + INTERVAL '7 days' AS expiry_date
FROM products
WHERE active = BOOLEAN true;
WHERE created_at > TIMESTAMP '2025-01-01';
{{< /code-block >}}

## Functions
Expand Down
Loading