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 4c27da6544 Publish built docs triggered by
f8a22a51bfb6fea35c6fc96ea9a1af351a3ade5c
4c27da6544 is described below
commit 4c27da65449c85b3c2bca76d1b3c0c916f4df731
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Mon Jan 26 12:39:03 2026 +0000
Publish built docs triggered by f8a22a51bfb6fea35c6fc96ea9a1af351a3ade5c
---
_sources/contributor-guide/testing.md.txt | 1 +
_sources/library-user-guide/query-optimizer.md.txt | 2 ++
_sources/user-guide/arrow-introduction.md.txt | 1 +
_sources/user-guide/crate-configuration.md.txt | 1 +
_sources/user-guide/sql/scalar_functions.md.txt | 21 +++++++++++++++------
contributor-guide/testing.html | 2 +-
library-user-guide/query-optimizer.html | 6 +++---
user-guide/arrow-introduction.html | 2 +-
user-guide/crate-configuration.html | 4 ++--
user-guide/sql/scalar_functions.html | 21 +++++++++++++++------
10 files changed, 42 insertions(+), 19 deletions(-)
diff --git a/_sources/contributor-guide/testing.md.txt
b/_sources/contributor-guide/testing.md.txt
index 81ceabb646..5a6caed224 100644
--- a/_sources/contributor-guide/testing.md.txt
+++ b/_sources/contributor-guide/testing.md.txt
@@ -104,6 +104,7 @@ locally by following the [instructions in the
documentation].
[sqlite test suite]: https://www.sqlite.org/sqllogictest/dir?ci=tip
[instructions in the documentation]:
https://github.com/apache/datafusion/tree/main/datafusion/sqllogictest#running-tests-sqlite
+[extended.yml]:
https://github.com/apache/datafusion/blob/main/.github/workflows/extended.yml
## Rust Integration Tests
diff --git a/_sources/library-user-guide/query-optimizer.md.txt
b/_sources/library-user-guide/query-optimizer.md.txt
index d85ddff3c9..2254776bf6 100644
--- a/_sources/library-user-guide/query-optimizer.md.txt
+++ b/_sources/library-user-guide/query-optimizer.md.txt
@@ -514,3 +514,5 @@ fn analyze_filter_example() -> Result<()> {
Ok(())
}
```
+
+[treenode api]:
https://docs.rs/datafusion/latest/datafusion/common/tree_node/trait.TreeNode.html
diff --git a/_sources/user-guide/arrow-introduction.md.txt
b/_sources/user-guide/arrow-introduction.md.txt
index 5bb29a0c6a..5a225782ad 100644
--- a/_sources/user-guide/arrow-introduction.md.txt
+++ b/_sources/user-guide/arrow-introduction.md.txt
@@ -220,6 +220,7 @@ When working with Arrow and RecordBatches, watch out for
these common issues:
-
[Schema](https://docs.rs/arrow-schema/latest/arrow_schema/struct.Schema.html) -
Describes the structure of a RecordBatch (column names and types)
[apache arrow]: https://arrow.apache.org/docs/index.html
+[arrow-rs]: https://github.com/apache/arrow-rs
[`arc`]: https://doc.rust-lang.org/std/sync/struct.Arc.html
[`arrayref`]:
https://docs.rs/arrow-array/latest/arrow_array/array/type.ArrayRef.html
[`cast`]: https://docs.rs/arrow/latest/arrow/compute/fn.cast.html
diff --git a/_sources/user-guide/crate-configuration.md.txt
b/_sources/user-guide/crate-configuration.md.txt
index 83a46b50c0..87c8ecfebc 100644
--- a/_sources/user-guide/crate-configuration.md.txt
+++ b/_sources/user-guide/crate-configuration.md.txt
@@ -24,6 +24,7 @@ your Rust project. The [Configuration Settings] section lists
options that
control additional aspects DataFusion's runtime behavior.
[configuration settings]: configs.md
+[support for adding dependencies]:
https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-dependencies
## Using the nightly DataFusion builds
diff --git a/_sources/user-guide/sql/scalar_functions.md.txt
b/_sources/user-guide/sql/scalar_functions.md.txt
index 605c3285c3..7896adc0cf 100644
--- a/_sources/user-guide/sql/scalar_functions.md.txt
+++ b/_sources/user-guide/sql/scalar_functions.md.txt
@@ -2880,7 +2880,8 @@ Additional examples can be found
[here](https://github.com/apache/datafusion/blo
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
+if no [Chrono
formats](https://docs.rs/chrono/latest/chrono/format/strftime/index.html) 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`).
@@ -2928,7 +2929,8 @@ Additional examples can be found
[here](https://github.com/apache/datafusion/blo
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
+if no [Chrono
formats](https://docs.rs/chrono/latest/chrono/format/strftime/index.html) 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`).
@@ -2971,7 +2973,8 @@ Additional examples can be found
[here](https://github.com/apache/datafusion/blo
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
+if no [Chrono
formats](https://docs.rs/chrono/latest/chrono/format/strftime/index.html) 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`).
@@ -3014,7 +3017,8 @@ Additional examples can be found
[here](https://github.com/apache/datafusion/blo
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
+if no [Chrono
formats](https://docs.rs/chrono/latest/chrono/format/strftime/index.html) 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'`.
@@ -3056,7 +3060,8 @@ Additional examples can be found
[here](https://github.com/apache/datafusion/blo
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
+if no [Chrono
formats](https://docs.rs/chrono/latest/chrono/format/strftime/index.html) 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`).
@@ -3097,7 +3102,11 @@ Additional examples can be found
[here](https://github.com/apache/datafusion/blo
### `to_unixtime`
-Converts a value to seconds since the unix epoch (`1970-01-01T00:00:00`).
Supports strings, dates, timestamps, integer, unsigned integer, and float 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, unsigned integers, and floats are interpreted as seconds
since the unix epoch (`1970-01-01T00:00:00`).
+Converts a value to seconds since the unix epoch (`1970-01-01T00:00:00`).
+Supports strings, dates, timestamps, integer, unsigned integer, and float
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, unsigned integers, and floats are interpreted as seconds since the
unix epoch (`1970-01-01T00:00:00`).
```sql
to_unixtime(expression[, ..., format_n])
diff --git a/contributor-guide/testing.html b/contributor-guide/testing.html
index 88d1838f1a..83b8d97f86 100644
--- a/contributor-guide/testing.html
+++ b/contributor-guide/testing.html
@@ -457,7 +457,7 @@ cargo<span class="w"> </span>insta<span class="w">
</span>review
<section id="extended-tests">
<h2>Extended Tests<a class="headerlink" href="#extended-tests" title="Link to
this heading">#</a></h2>
<p>In addition to the standard CI test suite that is run on all PRs prior to
merge,
-DataFusion has “extended” tests (defined in [extended.yml]) that are run on
each
+DataFusion has “extended” tests (defined in <a class="reference external"
href="https://github.com/apache/datafusion/blob/main/.github/workflows/extended.yml">extended.yml</a>)
that are run on each
commit to <code class="docutils literal notranslate"><span
class="pre">main</span></code>. These tests rarely fail but take significantly
longer to run
than the standard test suite and add important test coverage such as ensuring
correctness when there are hash collisions and running the relevant portions of
diff --git a/library-user-guide/query-optimizer.html
b/library-user-guide/query-optimizer.html
index f1c6a36448..4f36096006 100644
--- a/library-user-guide/query-optimizer.html
+++ b/library-user-guide/query-optimizer.html
@@ -578,7 +578,7 @@ name to be used in a schema, <code class="docutils literal
notranslate"><span cl
</section>
<section id="recursively-walk-an-expression-tree">
<h3>Recursively walk an expression tree<a class="headerlink"
href="#recursively-walk-an-expression-tree" title="Link to this
heading">#</a></h3>
-<p>The [TreeNode API] provides a convenient way to recursively walk an
expression or plan tree.</p>
+<p>The <a class="reference external"
href="https://docs.rs/datafusion/latest/datafusion/common/tree_node/trait.TreeNode.html">TreeNode
API</a> provides a convenient way to recursively walk an expression or plan
tree.</p>
<p>For example, to find all subquery references in a logical plan, the
following code can be used:</p>
<div class="highlight-rust notranslate"><div
class="highlight"><pre><span></span><span class="c1">// Return all subquery
references in an expression</span>
<span class="k">fn</span><span class="w"> </span><span
class="nf">extract_subquery_filters</span><span class="p">(</span><span
class="n">expression</span><span class="p">:</span><span class="w">
</span><span class="kp">&</span><span class="nc">Expr</span><span
class="p">)</span><span class="w"> </span><span class="p">-></span><span
class="w"> </span><span class="nb">Result</span><span
class="o"><</span><span class="nb">Vec</span><span
class="o"><&</span><span class="n">E [...]
@@ -593,7 +593,7 @@ name to be used in a schema, <code class="docutils literal
notranslate"><span cl
<span class="p">}</span>
</pre></div>
</div>
-<p>Likewise you can use the [TreeNode API] to rewrite a <code class="docutils
literal notranslate"><span class="pre">LogicalPlan</span></code> or <code
class="docutils literal notranslate"><span
class="pre">ExecutionPlan</span></code></p>
+<p>Likewise you can use the <a class="reference external"
href="https://docs.rs/datafusion/latest/datafusion/common/tree_node/trait.TreeNode.html">TreeNode
API</a> to rewrite a <code class="docutils literal notranslate"><span
class="pre">LogicalPlan</span></code> or <code class="docutils literal
notranslate"><span class="pre">ExecutionPlan</span></code></p>
<div class="highlight-rust notranslate"><div
class="highlight"><pre><span></span><span class="c1">// Return all joins in a
logical plan</span>
<span class="k">fn</span><span class="w"> </span><span
class="nf">find_joins</span><span class="p">(</span><span
class="n">overall_plan</span><span class="p">:</span><span class="w">
</span><span class="kp">&</span><span class="nc">LogicalPlan</span><span
class="p">)</span><span class="w"> </span><span class="p">-></span><span
class="w"> </span><span class="nb">Result</span><span
class="o"><</span><span class="nb">Vec</span><span
class="o"><&</span><span class="n">Join</ [...]
<span class="w"> </span><span class="kd">let</span><span class="w">
</span><span class="k">mut</span><span class="w"> </span><span
class="n">extracted</span><span class="w"> </span><span class="o">=</span><span
class="w"> </span><span class="fm">vec!</span><span class="p">[];</span>
@@ -610,7 +610,7 @@ name to be used in a schema, <code class="docutils literal
notranslate"><span cl
</section>
<section id="rewriting-expressions">
<h3>Rewriting expressions<a class="headerlink" href="#rewriting-expressions"
title="Link to this heading">#</a></h3>
-<p>The [TreeNode API] also provides a convenient way to rewrite expressions and
+<p>The <a class="reference external"
href="https://docs.rs/datafusion/latest/datafusion/common/tree_node/trait.TreeNode.html">TreeNode
API</a> also provides a convenient way to rewrite expressions and
plans as well. For example to rewrite all expressions like</p>
<div class="highlight-sql notranslate"><div
class="highlight"><pre><span></span><span class="n">col</span><span class="w">
</span><span class="k">BETWEEN</span><span class="w"> </span><span
class="n">x</span><span class="w"> </span><span class="k">AND</span><span
class="w"> </span><span class="n">y</span>
</pre></div>
diff --git a/user-guide/arrow-introduction.html
b/user-guide/arrow-introduction.html
index ff33477548..0e3e466cfc 100644
--- a/user-guide/arrow-introduction.html
+++ b/user-guide/arrow-introduction.html
@@ -472,7 +472,7 @@
<section id="creating-arrayref-and-recordbatches">
<h2><a class="toc-backref" href="#id5" role="doc-backlink">Creating <code
class="docutils literal notranslate"><span class="pre">ArrayRef</span></code>
and <code class="docutils literal notranslate"><span
class="pre">RecordBatch</span></code>es</a><a class="headerlink"
href="#creating-arrayref-and-recordbatches" title="Link to this
heading">#</a></h2>
<p>Sometimes you need to create Arrow data programmatically rather than
reading from files.</p>
-<p>The first thing needed is creating an Arrow Array, for each column.
[arrow-rs] provides array builders and <code class="docutils literal
notranslate"><span class="pre">From</span></code> impls to create arrays from
Rust vectors.</p>
+<p>The first thing needed is creating an Arrow Array, for each column. <a
class="reference external"
href="https://github.com/apache/arrow-rs">arrow-rs</a> provides array builders
and <code class="docutils literal notranslate"><span
class="pre">From</span></code> impls to create arrays from Rust vectors.</p>
<div class="highlight-rust notranslate"><div
class="highlight"><pre><span></span><span class="k">use</span><span class="w">
</span><span class="n">arrow</span><span class="p">::</span><span
class="n">array</span><span class="p">::{</span><span
class="n">StringArray</span><span class="p">,</span><span class="w">
</span><span class="n">Int32Array</span><span class="p">};</span>
<span class="c1">// Create an Int32Array from a vector of i32 values</span>
<span class="kd">let</span><span class="w"> </span><span
class="n">ids</span><span class="w"> </span><span class="o">=</span><span
class="w"> </span><span class="n">Int32Array</span><span
class="p">::</span><span class="n">from</span><span class="p">(</span><span
class="fm">vec!</span><span class="p">[</span><span class="mi">1</span><span
class="p">,</span><span class="w"> </span><span class="mi">2</span><span
class="p">,</span><span class="w"> </span><span class="mi">3</span><span class
[...]
diff --git a/user-guide/crate-configuration.html
b/user-guide/crate-configuration.html
index 3a9aed02a7..ede120c628 100644
--- a/user-guide/crate-configuration.html
+++ b/user-guide/crate-configuration.html
@@ -414,8 +414,8 @@ control additional aspects DataFusion’s runtime
behavior.</p>
<h2>Using the nightly DataFusion builds<a class="headerlink"
href="#using-the-nightly-datafusion-builds" title="Link to this
heading">#</a></h2>
<p>DataFusion changes are published to <code class="docutils literal
notranslate"><span class="pre">crates.io</span></code> according to the <a
class="reference external"
href="https://github.com/apache/datafusion/blob/main/dev/release/README.md#release-process">release
schedule</a></p>
<p>If you would like to use or test versions of the DataFusion code which are
-merged but not yet published, you can use Cargo’s [support for adding
-dependencies] directly to a GitHub branch:</p>
+merged but not yet published, you can use Cargo’s <a class="reference
external"
href="https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-dependencies">support
for adding
+dependencies</a> directly to a GitHub branch:</p>
<div class="highlight-toml notranslate"><div
class="highlight"><pre><span></span><span class="n">datafusion</span><span
class="w"> </span><span class="o">=</span><span class="w"> </span><span
class="p">{</span><span class="w"> </span><span class="n">git</span><span
class="w"> </span><span class="p">=</span><span class="w"> </span><span
class="s2">"https://github.com/apache/datafusion"</span><span
class="p">,</span><span class="w"> </span><span class="n">branch</span><span
class [...]
</pre></div>
</div>
diff --git a/user-guide/sql/scalar_functions.html
b/user-guide/sql/scalar_functions.html
index efc81b444d..daa470f0f2 100644
--- a/user-guide/sql/scalar_functions.html
+++ b/user-guide/sql/scalar_functions.html
@@ -3388,7 +3388,8 @@ an error will be returned.</p></li>
<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: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
+if no <a class="reference external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html">Chrono
formats</a> 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
@@ -3434,7 +3435,8 @@ only supported at the end of the string preceded by a
space.</p></li>
<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.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
+if no <a class="reference external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html">Chrono
formats</a> 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>.
@@ -3476,7 +3478,8 @@ only supported at the end of the string preceded by a
space.</p></li>
<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.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
+if no <a class="reference external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html">Chrono
formats</a> 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>.
@@ -3518,7 +3521,8 @@ only supported at the end of the string preceded by a
space.</p></li>
<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.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
+if no <a class="reference external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html">Chrono
formats</a> 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>
@@ -3559,7 +3563,8 @@ only supported at the end of the string preceded by a
space.</p></li>
<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<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
+if no <a class="reference external"
href="https://docs.rs/chrono/latest/chrono/format/strftime/index.html">Chrono
formats</a> 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>.
@@ -3599,7 +3604,11 @@ only supported at the end of the string preceded by a
space.</p></li>
</section>
<section id="to-unixtime">
<h3><code class="docutils literal notranslate"><span
class="pre">to_unixtime</span></code><a class="headerlink" href="#to-unixtime"
title="Link to this heading">#</a></h3>
-<p>Converts a value to seconds since the unix epoch (<code class="docutils
literal notranslate"><span class="pre">1970-01-01T00:00:00</span></code>).
Supports strings, dates, timestamps, integer, unsigned integer, and float 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, unsigned integers, and floats are interpret
[...]
+<p>Converts a value to seconds since the unix epoch (<code class="docutils
literal notranslate"><span class="pre">1970-01-01T00:00:00</span></code>).
+Supports strings, dates, timestamps, integer, unsigned integer, and float
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, unsigned integers, and floats are interpreted as seconds since the
unix epoch (<code class="docutils literal notranslate"><span
class="pre">1970-01-01T00:00:00</span></code>).</p>
<div class="highlight-sql notranslate"><div
class="highlight"><pre><span></span><span class="n">to_unixtime</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>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]