This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/datafusion.git
The following commit(s) were added to refs/heads/asf-site by this push:
new c998e1de14 Publish built docs triggered by
ada0923a3927d16dc5d810637cfbea4146c54f54
c998e1de14 is described below
commit c998e1de140cb3dca701bf41fb533dd16107ac76
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Mon Jan 5 21:04:39 2026 +0000
Publish built docs triggered by ada0923a3927d16dc5d810637cfbea4146c54f54
---
_sources/user-guide/sql/scalar_functions.md.txt | 79 +++++++++++++++++++++----
searchindex.js | 2 +-
user-guide/sql/scalar_functions.html | 74 +++++++++++++++++++----
3 files changed, 132 insertions(+), 23 deletions(-)
diff --git a/_sources/user-guide/sql/scalar_functions.md.txt
b/_sources/user-guide/sql/scalar_functions.md.txt
index 360311552f..fe1ed1cab6 100644
--- a/_sources/user-guide/sql/scalar_functions.md.txt
+++ b/_sources/user-guide/sql/scalar_functions.md.txt
@@ -2867,9 +2867,19 @@ Additional examples can be found
[here](https://github.com/apache/datafusion/blo
### `to_timestamp`
-Converts a value to a timestamp (`YYYY-MM-DDT00:00:00Z`). Supports strings,
integer, unsigned integer, and double types as input. Strings are parsed as
RFC3339 (e.g. '2023-07-20T05:44:00') if no [Chrono formats] are provided.
Integers, unsigned integers, and doubles are interpreted as seconds since the
unix epoch (`1970-01-01T00:00:00Z`). Returns the corresponding timestamp.
+Converts a value to a timestamp (`YYYY-MM-DDT00:00:00.000000<TZ>`) in the
session time zone. Supports strings,
+integer, unsigned integer, and double types as input. Strings are parsed as
RFC3339 (e.g. '2023-07-20T05:44:00')
+if no [Chrono formats] are provided. Strings that parse without a time zone
are treated as if they are in the
+session time zone, or UTC if no session time zone is set.
+Integers, unsigned integers, and doubles are interpreted as seconds since the
unix epoch (`1970-01-01T00:00:00Z`).
-Note: `to_timestamp` returns `Timestamp(ns)`. The supported range for integer
input is between `-9223372037` and `9223372036`. Supported range for string
input is between `1677-09-21T00:12:44.0` and `2262-04-11T23:47:16.0`. Please
use `to_timestamp_seconds` for the input outside of supported bounds.
+Note: `to_timestamp` returns `Timestamp(ns, TimeZone)` where the time zone is
the session time zone. The supported range
+for integer input is between`-9223372037` and `9223372036`. Supported range
for string input is between
+`1677-09-21T00:12:44.0` and `2262-04-11T23:47:16.0`. Please use
`to_timestamp_seconds`
+for the input outside of supported bounds.
+
+The session time zone can be set using the statement `SET TIMEZONE = 'desired
time zone'`.
+The time zone can be a value like +00:00, 'Europe/London' etc.
```sql
to_timestamp(expression[, ..., format_n])
@@ -2878,7 +2888,11 @@ to_timestamp(expression[, ..., format_n])
#### Arguments
- **expression**: Expression to operate on. Can be a constant, column, or
function, and any combination of arithmetic operators.
-- **format_n**: Optional [Chrono
format](https://docs.rs/chrono/latest/chrono/format/strftime/index.html)
strings to use to parse the expression. Formats will be tried in the order they
appear with the first successful one being returned. If none of the formats
successfully parse the expression an error will be returned.
+- **format_n**:
+ Optional [Chrono
format](https://docs.rs/chrono/latest/chrono/format/strftime/index.html)
strings to use to parse the expression.
+ Formats will be tried in the order they appear with the first successful one
being returned. If none of the formats successfully
+ parse the expression an error will be returned. Note: parsing of named
timezones (e.g. 'America/New_York') using %Z is
+ only supported at the end of the string preceded by a space.
#### Example
@@ -2901,7 +2915,14 @@ Additional examples can be found
[here](https://github.com/apache/datafusion/blo
### `to_timestamp_micros`
-Converts a value to a timestamp (`YYYY-MM-DDT00:00:00.000000Z`). Supports
strings, integer, and unsigned integer types as input. Strings are parsed as
RFC3339 (e.g. '2023-07-20T05:44:00') if no [Chrono
format](https://docs.rs/chrono/latest/chrono/format/strftime/index.html)s are
provided. Integers and unsigned integers are interpreted as microseconds since
the unix epoch (`1970-01-01T00:00:00Z`) Returns the corresponding timestamp.
+Converts a value to a timestamp (`YYYY-MM-DDT00:00:00.000000<TZ>`) in the
session time zone. Supports strings,
+integer, unsigned integer, and double types as input. Strings are parsed as
RFC3339 (e.g. '2023-07-20T05:44:00')
+if no [Chrono formats] are provided. Strings that parse without a time zone
are treated as if they are in the
+session time zone, or UTC if no session time zone is set.
+Integers, unsigned integers, and doubles are interpreted as microseconds since
the unix epoch (`1970-01-01T00:00:00Z`).
+
+The session time zone can be set using the statement `SET TIMEZONE = 'desired
time zone'`.
+The time zone can be a value like +00:00, 'Europe/London' etc.
```sql
to_timestamp_micros(expression[, ..., format_n])
@@ -2910,7 +2931,11 @@ to_timestamp_micros(expression[, ..., format_n])
#### Arguments
- **expression**: Expression to operate on. Can be a constant, column, or
function, and any combination of arithmetic operators.
-- **format_n**: Optional [Chrono
format](https://docs.rs/chrono/latest/chrono/format/strftime/index.html)
strings to use to parse the expression. Formats will be tried in the order they
appear with the first successful one being returned. If none of the formats
successfully parse the expression an error will be returned.
+- **format_n**:
+ Optional [Chrono
format](https://docs.rs/chrono/latest/chrono/format/strftime/index.html)
strings to use to parse the expression.
+ Formats will be tried in the order they appear with the first successful one
being returned. If none of the formats successfully
+ parse the expression an error will be returned. Note: parsing of named
timezones (e.g. 'America/New_York') using %Z is
+ only supported at the end of the string preceded by a space.
#### Example
@@ -2933,7 +2958,14 @@ Additional examples can be found
[here](https://github.com/apache/datafusion/blo
### `to_timestamp_millis`
-Converts a value to a timestamp (`YYYY-MM-DDT00:00:00.000Z`). Supports
strings, integer, and unsigned integer types as input. Strings are parsed as
RFC3339 (e.g. '2023-07-20T05:44:00') if no [Chrono
formats](https://docs.rs/chrono/latest/chrono/format/strftime/index.html) are
provided. Integers and unsigned integers are interpreted as milliseconds since
the unix epoch (`1970-01-01T00:00:00Z`). Returns the corresponding timestamp.
+Converts a value to a timestamp (`YYYY-MM-DDT00:00:00.000<TZ>`) in the session
time zone. Supports strings,
+integer, unsigned integer, and double types as input. Strings are parsed as
RFC3339 (e.g. '2023-07-20T05:44:00')
+if no [Chrono formats] are provided. Strings that parse without a time zone
are treated as if they are in the
+session time zone, or UTC if no session time zone is set.
+Integers, unsigned integers, and doubles are interpreted as milliseconds since
the unix epoch (`1970-01-01T00:00:00Z`).
+
+The session time zone can be set using the statement `SET TIMEZONE = 'desired
time zone'`.
+The time zone can be a value like +00:00, 'Europe/London' etc.
```sql
to_timestamp_millis(expression[, ..., format_n])
@@ -2942,7 +2974,11 @@ to_timestamp_millis(expression[, ..., format_n])
#### Arguments
- **expression**: Expression to operate on. Can be a constant, column, or
function, and any combination of arithmetic operators.
-- **format_n**: Optional [Chrono
format](https://docs.rs/chrono/latest/chrono/format/strftime/index.html)
strings to use to parse the expression. Formats will be tried in the order they
appear with the first successful one being returned. If none of the formats
successfully parse the expression an error will be returned.
+- **format_n**:
+ Optional [Chrono
format](https://docs.rs/chrono/latest/chrono/format/strftime/index.html)
strings to use to parse the expression.
+ Formats will be tried in the order they appear with the first successful one
being returned. If none of the formats successfully
+ parse the expression an error will be returned. Note: parsing of named
timezones (e.g. 'America/New_York') using %Z is
+ only supported at the end of the string preceded by a space.
#### Example
@@ -2965,7 +3001,13 @@ Additional examples can be found
[here](https://github.com/apache/datafusion/blo
### `to_timestamp_nanos`
-Converts a value to a timestamp (`YYYY-MM-DDT00:00:00.000000000Z`). Supports
strings, integer, and unsigned integer types as input. Strings are parsed as
RFC3339 (e.g. '2023-07-20T05:44:00') if no [Chrono
format](https://docs.rs/chrono/latest/chrono/format/strftime/index.html)s are
provided. Integers and unsigned integers are interpreted as nanoseconds since
the unix epoch (`1970-01-01T00:00:00Z`). Returns the corresponding timestamp.
+Converts a value to a timestamp (`YYYY-MM-DDT00:00:00.000000000<TZ>`) in the
session time zone. Supports strings,
+integer, unsigned integer, and double types as input. Strings are parsed as
RFC3339 (e.g. '2023-07-20T05:44:00')
+if no [Chrono formats] are provided. Strings that parse without a time zone
are treated as if they are in the
+session time zone. Integers, unsigned integers, and doubles are interpreted as
nanoseconds since the unix epoch (`1970-01-01T00:00:00Z`).
+
+The session time zone can be set using the statement `SET TIMEZONE = 'desired
time zone'`.
+The time zone can be a value like +00:00, 'Europe/London' etc.
```sql
to_timestamp_nanos(expression[, ..., format_n])
@@ -2974,7 +3016,11 @@ to_timestamp_nanos(expression[, ..., format_n])
#### Arguments
- **expression**: Expression to operate on. Can be a constant, column, or
function, and any combination of arithmetic operators.
-- **format_n**: Optional [Chrono
format](https://docs.rs/chrono/latest/chrono/format/strftime/index.html)
strings to use to parse the expression. Formats will be tried in the order they
appear with the first successful one being returned. If none of the formats
successfully parse the expression an error will be returned.
+- **format_n**:
+ Optional [Chrono
format](https://docs.rs/chrono/latest/chrono/format/strftime/index.html)
strings to use to parse the expression.
+ Formats will be tried in the order they appear with the first successful one
being returned. If none of the formats successfully
+ parse the expression an error will be returned. Note: parsing of named
timezones (e.g. 'America/New_York') using %Z is
+ only supported at the end of the string preceded by a space.
#### Example
@@ -2997,7 +3043,14 @@ Additional examples can be found
[here](https://github.com/apache/datafusion/blo
### `to_timestamp_seconds`
-Converts a value to a timestamp (`YYYY-MM-DDT00:00:00.000Z`). Supports
strings, integer, and unsigned integer types as input. Strings are parsed as
RFC3339 (e.g. '2023-07-20T05:44:00') if no [Chrono
format](https://docs.rs/chrono/latest/chrono/format/strftime/index.html)s are
provided. Integers and unsigned integers are interpreted as seconds since the
unix epoch (`1970-01-01T00:00:00Z`). Returns the corresponding timestamp.
+Converts a value to a timestamp (`YYYY-MM-DDT00:00:00<TZ>`) in the session
time zone. Supports strings,
+integer, unsigned integer, and double types as input. Strings are parsed as
RFC3339 (e.g. '2023-07-20T05:44:00')
+if no [Chrono formats] are provided. Strings that parse without a time zone
are treated as if they are in the
+session time zone, or UTC if no session time zone is set.
+Integers, unsigned integers, and doubles are interpreted as seconds since the
unix epoch (`1970-01-01T00:00:00Z`).
+
+The session time zone can be set using the statement `SET TIMEZONE = 'desired
time zone'`.
+The time zone can be a value like +00:00, 'Europe/London' etc.
```sql
to_timestamp_seconds(expression[, ..., format_n])
@@ -3006,7 +3059,11 @@ to_timestamp_seconds(expression[, ..., format_n])
#### Arguments
- **expression**: Expression to operate on. Can be a constant, column, or
function, and any combination of arithmetic operators.
-- **format_n**: Optional [Chrono
format](https://docs.rs/chrono/latest/chrono/format/strftime/index.html)
strings to use to parse the expression. Formats will be tried in the order they
appear with the first successful one being returned. If none of the formats
successfully parse the expression an error will be returned.
+- **format_n**:
+ Optional [Chrono
format](https://docs.rs/chrono/latest/chrono/format/strftime/index.html)
strings to use to parse the expression.
+ Formats will be tried in the order they appear with the first successful one
being returned. If none of the formats successfully
+ parse the expression an error will be returned. Note: parsing of named
timezones (e.g. 'America/New_York') using %Z is
+ only supported at the end of the string preceded by a space.
#### Example
diff --git a/searchindex.js b/searchindex.js
index fef3106645..beca48554c 100644
--- a/searchindex.js
+++ b/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"alltitles":{"!=":[[61,"op-neq"]],"!~":[[61,"op-re-not-match"]],"!~*":[[61,"op-re-not-match-i"]],"!~~":[[61,"id19"]],"!~~*":[[61,"id20"]],"#":[[61,"op-bit-xor"]],"%":[[61,"op-modulo"]],"&":[[61,"op-bit-and"]],"(relation,
name) tuples in logical fields and logical columns are
unique":[[13,"relation-name-tuples-in-logical-fields-and-logical-columns-are-unique"]],"*":[[61,"op-multiply"]],"+":[[61,"op-plus"]],"-":[[61,"op-minus"]],"/":[[61,"op-divide"]],"<":[[61,"op-lt"]],"<
[...]
\ No newline at end of file
+Search.setIndex({"alltitles":{"!=":[[61,"op-neq"]],"!~":[[61,"op-re-not-match"]],"!~*":[[61,"op-re-not-match-i"]],"!~~":[[61,"id19"]],"!~~*":[[61,"id20"]],"#":[[61,"op-bit-xor"]],"%":[[61,"op-modulo"]],"&":[[61,"op-bit-and"]],"(relation,
name) tuples in logical fields and logical columns are
unique":[[13,"relation-name-tuples-in-logical-fields-and-logical-columns-are-unique"]],"*":[[61,"op-multiply"]],"+":[[61,"op-plus"]],"-":[[61,"op-minus"]],"/":[[61,"op-divide"]],"<":[[61,"op-lt"]],"<
[...]
\ No newline at end of file
diff --git a/user-guide/sql/scalar_functions.html
b/user-guide/sql/scalar_functions.html
index 57a4e0cce6..ff71ccca50 100644
--- a/user-guide/sql/scalar_functions.html
+++ b/user-guide/sql/scalar_functions.html
@@ -3373,8 +3373,17 @@ an error will be returned.</p></li>
</section>
<section id="to-timestamp">
<h3><code class="docutils literal notranslate"><span
class="pre">to_timestamp</span></code><a class="headerlink"
href="#to-timestamp" title="Link to this heading">#</a></h3>
-<p>Converts a value to a timestamp (<code class="docutils literal
notranslate"><span class="pre">YYYY-MM-DDT00:00:00Z</span></code>). Supports
strings, integer, unsigned integer, and double types as input. Strings are
parsed as RFC3339 (e.g. ‘2023-07-20T05:44:00’) if no [Chrono formats] are
provided. Integers, unsigned integers, and doubles are interpreted as seconds
since the unix epoch (<code class="docutils literal notranslate"><span
class="pre">1970-01-01T00:00:00Z</span></code>). Re [...]
-<p>Note: <code class="docutils literal notranslate"><span
class="pre">to_timestamp</span></code> returns <code class="docutils literal
notranslate"><span class="pre">Timestamp(ns)</span></code>. The supported range
for integer input is between <code class="docutils literal notranslate"><span
class="pre">-9223372037</span></code> and <code class="docutils literal
notranslate"><span class="pre">9223372036</span></code>. Supported range for
string input is between <code class="docutils lite [...]
+<p>Converts a value to a timestamp (<code class="docutils literal
notranslate"><span
class="pre">YYYY-MM-DDT00:00:00.000000<TZ></span></code>) in the session
time zone. Supports strings,
+integer, unsigned integer, and double types as input. Strings are parsed as
RFC3339 (e.g. ‘2023-07-20T05:44:00’)
+if no [Chrono formats] are provided. Strings that parse without a time zone
are treated as if they are in the
+session time zone, or UTC if no session time zone is set.
+Integers, unsigned integers, and doubles are interpreted as seconds since the
unix epoch (<code class="docutils literal notranslate"><span
class="pre">1970-01-01T00:00:00Z</span></code>).</p>
+<p>Note: <code class="docutils literal notranslate"><span
class="pre">to_timestamp</span></code> returns <code class="docutils literal
notranslate"><span class="pre">Timestamp(ns,</span> <span
class="pre">TimeZone)</span></code> where the time zone is the session time
zone. The supported range
+for integer input is between<code class="docutils literal notranslate"><span
class="pre">-9223372037</span></code> and <code class="docutils literal
notranslate"><span class="pre">9223372036</span></code>. Supported range for
string input is between
+<code class="docutils literal notranslate"><span
class="pre">1677-09-21T00:12:44.0</span></code> and <code class="docutils
literal notranslate"><span class="pre">2262-04-11T23:47:16.0</span></code>.
Please use <code class="docutils literal notranslate"><span
class="pre">to_timestamp_seconds</span></code>
+for the input outside of supported bounds.</p>
+<p>The session time zone can be set using the statement <code class="docutils
literal notranslate"><span class="pre">SET</span> <span
class="pre">TIMEZONE</span> <span class="pre">=</span> <span
class="pre">'desired</span> <span class="pre">time</span> <span
class="pre">zone'</span></code>.
+The time zone can be a value like +00:00, ‘Europe/London’ etc.</p>
<div class="highlight-sql notranslate"><div
class="highlight"><pre><span></span><span class="n">to_timestamp</span><span
class="p">(</span><span class="n">expression</span><span
class="p">[,</span><span class="w"> </span><span class="p">...,</span><span
class="w"> </span><span class="n">format_n</span><span class="p">])</span>
</pre></div>
</div>
@@ -3382,7 +3391,11 @@ an error will be returned.</p></li>
<h4>Arguments<a class="headerlink" href="#id194" title="Link to this
heading">#</a></h4>
<ul class="simple">
<li><p><strong>expression</strong>: Expression to operate on. Can be a
constant, column, or function, and any combination of arithmetic
operators.</p></li>
-<li><p><strong>format_n</strong>: Optional <a class="reference external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html";>Chrono
format</a> strings to use to parse the expression. Formats will be tried in the
order they appear with the first successful one being returned. If none of the
formats successfully parse the expression an error will be returned.</p></li>
+<li><p><strong>format_n</strong>:
+Optional <a class="reference external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html";>Chrono
format</a> strings to use to parse the expression.
+Formats will be tried in the order they appear with the first successful one
being returned. If none of the formats successfully
+parse the expression an error will be returned. Note: parsing of named
timezones (e.g. ‘America/New_York’) using %Z is
+only supported at the end of the string preceded by a space.</p></li>
</ul>
</section>
<section id="id195">
@@ -3406,7 +3419,13 @@ an error will be returned.</p></li>
</section>
<section id="to-timestamp-micros">
<h3><code class="docutils literal notranslate"><span
class="pre">to_timestamp_micros</span></code><a class="headerlink"
href="#to-timestamp-micros" title="Link to this heading">#</a></h3>
-<p>Converts a value to a timestamp (<code class="docutils literal
notranslate"><span class="pre">YYYY-MM-DDT00:00:00.000000Z</span></code>).
Supports strings, integer, and unsigned integer types as input. Strings are
parsed as RFC3339 (e.g. ‘2023-07-20T05:44:00’) if no <a class="reference
external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html";>Chrono
format</a>s are provided. Integers and unsigned integers are interpreted as
microseconds since the unix epoch (<co [...]
+<p>Converts a value to a timestamp (<code class="docutils literal
notranslate"><span
class="pre">YYYY-MM-DDT00:00:00.000000<TZ></span></code>) in the session
time zone. Supports strings,
+integer, unsigned integer, and double types as input. Strings are parsed as
RFC3339 (e.g. ‘2023-07-20T05:44:00’)
+if no [Chrono formats] are provided. Strings that parse without a time zone
are treated as if they are in the
+session time zone, or UTC if no session time zone is set.
+Integers, unsigned integers, and doubles are interpreted as microseconds since
the unix epoch (<code class="docutils literal notranslate"><span
class="pre">1970-01-01T00:00:00Z</span></code>).</p>
+<p>The session time zone can be set using the statement <code class="docutils
literal notranslate"><span class="pre">SET</span> <span
class="pre">TIMEZONE</span> <span class="pre">=</span> <span
class="pre">'desired</span> <span class="pre">time</span> <span
class="pre">zone'</span></code>.
+The time zone can be a value like +00:00, ‘Europe/London’ etc.</p>
<div class="highlight-sql notranslate"><div
class="highlight"><pre><span></span><span
class="n">to_timestamp_micros</span><span class="p">(</span><span
class="n">expression</span><span class="p">[,</span><span class="w">
</span><span class="p">...,</span><span class="w"> </span><span
class="n">format_n</span><span class="p">])</span>
</pre></div>
</div>
@@ -3414,7 +3433,11 @@ an error will be returned.</p></li>
<h4>Arguments<a class="headerlink" href="#id196" title="Link to this
heading">#</a></h4>
<ul class="simple">
<li><p><strong>expression</strong>: Expression to operate on. Can be a
constant, column, or function, and any combination of arithmetic
operators.</p></li>
-<li><p><strong>format_n</strong>: Optional <a class="reference external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html";>Chrono
format</a> strings to use to parse the expression. Formats will be tried in the
order they appear with the first successful one being returned. If none of the
formats successfully parse the expression an error will be returned.</p></li>
+<li><p><strong>format_n</strong>:
+Optional <a class="reference external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html";>Chrono
format</a> strings to use to parse the expression.
+Formats will be tried in the order they appear with the first successful one
being returned. If none of the formats successfully
+parse the expression an error will be returned. Note: parsing of named
timezones (e.g. ‘America/New_York’) using %Z is
+only supported at the end of the string preceded by a space.</p></li>
</ul>
</section>
<section id="id197">
@@ -3438,7 +3461,13 @@ an error will be returned.</p></li>
</section>
<section id="to-timestamp-millis">
<h3><code class="docutils literal notranslate"><span
class="pre">to_timestamp_millis</span></code><a class="headerlink"
href="#to-timestamp-millis" title="Link to this heading">#</a></h3>
-<p>Converts a value to a timestamp (<code class="docutils literal
notranslate"><span class="pre">YYYY-MM-DDT00:00:00.000Z</span></code>).
Supports strings, integer, and unsigned integer types as input. Strings are
parsed as RFC3339 (e.g. ‘2023-07-20T05:44:00’) if no <a class="reference
external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html";>Chrono
formats</a> are provided. Integers and unsigned integers are interpreted as
milliseconds since the unix epoch (<code [...]
+<p>Converts a value to a timestamp (<code class="docutils literal
notranslate"><span class="pre">YYYY-MM-DDT00:00:00.000<TZ></span></code>)
in the session time zone. Supports strings,
+integer, unsigned integer, and double types as input. Strings are parsed as
RFC3339 (e.g. ‘2023-07-20T05:44:00’)
+if no [Chrono formats] are provided. Strings that parse without a time zone
are treated as if they are in the
+session time zone, or UTC if no session time zone is set.
+Integers, unsigned integers, and doubles are interpreted as milliseconds since
the unix epoch (<code class="docutils literal notranslate"><span
class="pre">1970-01-01T00:00:00Z</span></code>).</p>
+<p>The session time zone can be set using the statement <code class="docutils
literal notranslate"><span class="pre">SET</span> <span
class="pre">TIMEZONE</span> <span class="pre">=</span> <span
class="pre">'desired</span> <span class="pre">time</span> <span
class="pre">zone'</span></code>.
+The time zone can be a value like +00:00, ‘Europe/London’ etc.</p>
<div class="highlight-sql notranslate"><div
class="highlight"><pre><span></span><span
class="n">to_timestamp_millis</span><span class="p">(</span><span
class="n">expression</span><span class="p">[,</span><span class="w">
</span><span class="p">...,</span><span class="w"> </span><span
class="n">format_n</span><span class="p">])</span>
</pre></div>
</div>
@@ -3446,7 +3475,11 @@ an error will be returned.</p></li>
<h4>Arguments<a class="headerlink" href="#id198" title="Link to this
heading">#</a></h4>
<ul class="simple">
<li><p><strong>expression</strong>: Expression to operate on. Can be a
constant, column, or function, and any combination of arithmetic
operators.</p></li>
-<li><p><strong>format_n</strong>: Optional <a class="reference external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html";>Chrono
format</a> strings to use to parse the expression. Formats will be tried in the
order they appear with the first successful one being returned. If none of the
formats successfully parse the expression an error will be returned.</p></li>
+<li><p><strong>format_n</strong>:
+Optional <a class="reference external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html";>Chrono
format</a> strings to use to parse the expression.
+Formats will be tried in the order they appear with the first successful one
being returned. If none of the formats successfully
+parse the expression an error will be returned. Note: parsing of named
timezones (e.g. ‘America/New_York’) using %Z is
+only supported at the end of the string preceded by a space.</p></li>
</ul>
</section>
<section id="id199">
@@ -3470,7 +3503,12 @@ an error will be returned.</p></li>
</section>
<section id="to-timestamp-nanos">
<h3><code class="docutils literal notranslate"><span
class="pre">to_timestamp_nanos</span></code><a class="headerlink"
href="#to-timestamp-nanos" title="Link to this heading">#</a></h3>
-<p>Converts a value to a timestamp (<code class="docutils literal
notranslate"><span class="pre">YYYY-MM-DDT00:00:00.000000000Z</span></code>).
Supports strings, integer, and unsigned integer types as input. Strings are
parsed as RFC3339 (e.g. ‘2023-07-20T05:44:00’) if no <a class="reference
external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html";>Chrono
format</a>s are provided. Integers and unsigned integers are interpreted as
nanoseconds since the unix epoch (< [...]
+<p>Converts a value to a timestamp (<code class="docutils literal
notranslate"><span
class="pre">YYYY-MM-DDT00:00:00.000000000<TZ></span></code>) in the
session time zone. Supports strings,
+integer, unsigned integer, and double types as input. Strings are parsed as
RFC3339 (e.g. ‘2023-07-20T05:44:00’)
+if no [Chrono formats] are provided. Strings that parse without a time zone
are treated as if they are in the
+session time zone. Integers, unsigned integers, and doubles are interpreted as
nanoseconds since the unix epoch (<code class="docutils literal
notranslate"><span class="pre">1970-01-01T00:00:00Z</span></code>).</p>
+<p>The session time zone can be set using the statement <code class="docutils
literal notranslate"><span class="pre">SET</span> <span
class="pre">TIMEZONE</span> <span class="pre">=</span> <span
class="pre">'desired</span> <span class="pre">time</span> <span
class="pre">zone'</span></code>.
+The time zone can be a value like +00:00, ‘Europe/London’ etc.</p>
<div class="highlight-sql notranslate"><div
class="highlight"><pre><span></span><span
class="n">to_timestamp_nanos</span><span class="p">(</span><span
class="n">expression</span><span class="p">[,</span><span class="w">
</span><span class="p">...,</span><span class="w"> </span><span
class="n">format_n</span><span class="p">])</span>
</pre></div>
</div>
@@ -3478,7 +3516,11 @@ an error will be returned.</p></li>
<h4>Arguments<a class="headerlink" href="#id200" title="Link to this
heading">#</a></h4>
<ul class="simple">
<li><p><strong>expression</strong>: Expression to operate on. Can be a
constant, column, or function, and any combination of arithmetic
operators.</p></li>
-<li><p><strong>format_n</strong>: Optional <a class="reference external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html";>Chrono
format</a> strings to use to parse the expression. Formats will be tried in the
order they appear with the first successful one being returned. If none of the
formats successfully parse the expression an error will be returned.</p></li>
+<li><p><strong>format_n</strong>:
+Optional <a class="reference external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html";>Chrono
format</a> strings to use to parse the expression.
+Formats will be tried in the order they appear with the first successful one
being returned. If none of the formats successfully
+parse the expression an error will be returned. Note: parsing of named
timezones (e.g. ‘America/New_York’) using %Z is
+only supported at the end of the string preceded by a space.</p></li>
</ul>
</section>
<section id="id201">
@@ -3502,7 +3544,13 @@ an error will be returned.</p></li>
</section>
<section id="to-timestamp-seconds">
<h3><code class="docutils literal notranslate"><span
class="pre">to_timestamp_seconds</span></code><a class="headerlink"
href="#to-timestamp-seconds" title="Link to this heading">#</a></h3>
-<p>Converts a value to a timestamp (<code class="docutils literal
notranslate"><span class="pre">YYYY-MM-DDT00:00:00.000Z</span></code>).
Supports strings, integer, and unsigned integer types as input. Strings are
parsed as RFC3339 (e.g. ‘2023-07-20T05:44:00’) if no <a class="reference
external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html";>Chrono
format</a>s are provided. Integers and unsigned integers are interpreted as
seconds since the unix epoch (<code class [...]
+<p>Converts a value to a timestamp (<code class="docutils literal
notranslate"><span class="pre">YYYY-MM-DDT00:00:00<TZ></span></code>) in
the session time zone. Supports strings,
+integer, unsigned integer, and double types as input. Strings are parsed as
RFC3339 (e.g. ‘2023-07-20T05:44:00’)
+if no [Chrono formats] are provided. Strings that parse without a time zone
are treated as if they are in the
+session time zone, or UTC if no session time zone is set.
+Integers, unsigned integers, and doubles are interpreted as seconds since the
unix epoch (<code class="docutils literal notranslate"><span
class="pre">1970-01-01T00:00:00Z</span></code>).</p>
+<p>The session time zone can be set using the statement <code class="docutils
literal notranslate"><span class="pre">SET</span> <span
class="pre">TIMEZONE</span> <span class="pre">=</span> <span
class="pre">'desired</span> <span class="pre">time</span> <span
class="pre">zone'</span></code>.
+The time zone can be a value like +00:00, ‘Europe/London’ etc.</p>
<div class="highlight-sql notranslate"><div
class="highlight"><pre><span></span><span
class="n">to_timestamp_seconds</span><span class="p">(</span><span
class="n">expression</span><span class="p">[,</span><span class="w">
</span><span class="p">...,</span><span class="w"> </span><span
class="n">format_n</span><span class="p">])</span>
</pre></div>
</div>
@@ -3510,7 +3558,11 @@ an error will be returned.</p></li>
<h4>Arguments<a class="headerlink" href="#id202" title="Link to this
heading">#</a></h4>
<ul class="simple">
<li><p><strong>expression</strong>: Expression to operate on. Can be a
constant, column, or function, and any combination of arithmetic
operators.</p></li>
-<li><p><strong>format_n</strong>: Optional <a class="reference external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html";>Chrono
format</a> strings to use to parse the expression. Formats will be tried in the
order they appear with the first successful one being returned. If none of the
formats successfully parse the expression an error will be returned.</p></li>
+<li><p><strong>format_n</strong>:
+Optional <a class="reference external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html";>Chrono
format</a> strings to use to parse the expression.
+Formats will be tried in the order they appear with the first successful one
being returned. If none of the formats successfully
+parse the expression an error will be returned. Note: parsing of named
timezones (e.g. ‘America/New_York’) using %Z is
+only supported at the end of the string preceded by a space.</p></li>
</ul>
</section>
<section id="id203">
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
