From 50f00c1bf3e4b7fd7619dce5dce504b00a54ada1 Mon Sep 17 00:00:00 2001 From: Colin Barry Date: Thu, 16 Oct 2025 16:54:52 +0100 Subject: [PATCH 1/2] fix: Clarify `datetime` behaviour when fields are missing --- pages/fundamentals/data-types.mdx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/pages/fundamentals/data-types.mdx b/pages/fundamentals/data-types.mdx index 4b24addb7..344583ca9 100644 --- a/pages/fundamentals/data-types.mdx +++ b/pages/fundamentals/data-types.mdx @@ -622,7 +622,12 @@ CREATE (:Flight {AIR123: datetime("2021-04-21T14:15:00Z")}); Maps for constructing `ZonedDateTime` values may have the following fields: `year`, `month`, `day`, `hour`, `minute`, `second`, `millisecond`, -`microsecond` and `timezone`. +`microsecond` and `timezone`. If some numeric fields are omitted, they will +assume the lowest value for that field, which is `0` for `year`, `hour`, +`minute`, `second`, `millisecond`, and `microsecond`; and `1` for `month` and +`day`. If the `timezone` is omitted, UTC will be assumed. If all numeric +fields are omitted and only the `timezone` is specified, then a `datetime` +representing the current clock time in the given timezone is created. There are two options for the `timezone` field: * string: timezone name from the From e7b66ff7f002e280362e407f6ca85afdfd395282 Mon Sep 17 00:00:00 2001 From: Matea Pesic <80577904+matea16@users.noreply.github.com> Date: Fri, 17 Oct 2025 09:20:05 +0200 Subject: [PATCH 2/2] Update pages/fundamentals/data-types.mdx --- pages/fundamentals/data-types.mdx | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/pages/fundamentals/data-types.mdx b/pages/fundamentals/data-types.mdx index 344583ca9..86f9d268f 100644 --- a/pages/fundamentals/data-types.mdx +++ b/pages/fundamentals/data-types.mdx @@ -622,12 +622,13 @@ CREATE (:Flight {AIR123: datetime("2021-04-21T14:15:00Z")}); Maps for constructing `ZonedDateTime` values may have the following fields: `year`, `month`, `day`, `hour`, `minute`, `second`, `millisecond`, -`microsecond` and `timezone`. If some numeric fields are omitted, they will -assume the lowest value for that field, which is `0` for `year`, `hour`, -`minute`, `second`, `millisecond`, and `microsecond`; and `1` for `month` and -`day`. If the `timezone` is omitted, UTC will be assumed. If all numeric -fields are omitted and only the `timezone` is specified, then a `datetime` -representing the current clock time in the given timezone is created. +`microsecond` and `timezone`. +- If some numeric fields are omitted, they default to the lowest value for that field: + - `0` for `year`, `hour`, `minute`, `second`, `millisecond`, and `microsecond`. + - `1` for `month` and `day`. +- If the `timezone` is omitted, it defaults to UTC. +- If all numeric fields are omitted and only the `timezone` is specified, then a `datetime` +represents the **current time** in the that timezone. There are two options for the `timezone` field: * string: timezone name from the