Documentation Source Text

          → requires [sqlite3_bind_pointer()] to set the PTR parameter.
     </ul>
<li> Added the [SQLITE_STMT virtual table] extension.
<li> Added the [COMPLETION extension] - designed to suggest
<li> Added the [UNION virtual table] extension.
     tab-completions for interactive user interfaces.  This is a work in progress.
     Expect further enhancements in future releases.




<li> Added the [sqlite3_prepare_v3()] and [sqlite3_prepare16_v3()] interfaces
     with the extra "prepFlags" parameters.
<li> Provide the [SQLITE_PREPARE_PERSISTENT] flag [sqlite3_prepare_v3()] and
     use it to limit [lookaside memory] misuse by [FTS3], [FTS5], and the
     [R-Tree extension].
<li> Added the [PRAGMA secure_delete=FAST] command.  When secure_delete is
     set to FAST, old content is overwritten with zeros as long as that does

          → requires [sqlite3_bind_pointer()] to set the PTR parameter.
     </ul>
<li> Added the [SQLITE_STMT virtual table] extension.
<li> Added the [COMPLETION extension] - designed to suggest
<li> Added the [UNION virtual table] extension.
     tab-completions for interactive user interfaces.  This is a work in progress.
     Expect further enhancements in future releases.
<li> The built-in [date and time functions] have been enhanced so that they can be
     used within [CHECK constraints], [indexes on expressions], and in the WHERE clause
     of a [partial index], provided that they do not use the 'now', 'localtime', or
     'utc' keywords.  [date/time special case|Futher information].
<li> Added the [sqlite3_prepare_v3()] and [sqlite3_prepare16_v3()] interfaces
     with the extra "prepFlags" parameters.
<li> Provide the [SQLITE_PREPARE_PERSISTENT] flag [sqlite3_prepare_v3()] and
     use it to limit [lookaside memory] misuse by [FTS3], [FTS5], and the
     [R-Tree extension].
<li> Added the [PRAGMA secure_delete=FAST] command.  When secure_delete is
     set to FAST, old content is overwritten with zeros as long as that does

<title>Deterministic SQL Functions</title>
<tcl>hd_keywords {deterministic function} {deterministic functions}\
     {deterministic SQL functions} {non-deterministic functions}</tcl>

<fancy_format>



<p>
SQL functions in SQLite can be either "deterministic" or "non-deterministic".

<p>
A deterministic function always gives the same answer whenever it has
the same inputs.  Most built-in SQL functions in SQLite are
deterministic.  For example, the [abs|abs(X)] function always returns
................................................................................
are examples of non-deterministic functions:

<ul>
<li> [random()]
<li> [changes()]
<li> [last_insert_rowid()]
<li> [sqlite3_version()]
<li> [date and time functions|datetime()]
</ul>

<p>
The [random()] function is obviously non-deterministic because it gives
a different answer every time it is invoked.  The answers from [changes()]
and [last_insert_rowid()] depend on prior SQL statements, and so they
are also non-deterministic.  The [date and time functions] are all
considered non-deterministic since, depending on their arguments, they
might return the current time, which is forever changing.  The
[sqlite3_version()] function is mostly constant, but it can change when
SQLite is upgraded, and so even though it always returns the same answer
for any particular session, because it can change answers across sessions
it is still considered non-deterministic.


<h1>Restrictions on the use of non-deterministic functions</h1>

<p>
There are some contexts in SQLite that do not allow the use of
non-deterministic functions:

<ul>

<li>In the WHERE clause of a [partial index].
<li>In an expression used as part of an [expression index].
</ul>

<p>
In the cases above, the values returned by the function is recorded
in the index b-tree.  If the function later starts returning a different
value, then the index will be seen as corrupt.  Hence, to avoid corrupt
indexes, only deterministic functions can be used.




















<h1>Application-defined deterministic functions</h1>

<p>
By default, [application-defined SQL functions] are considered to
be non-deterministic.  However, if the 4th parameter to
[sqlite3_create_function_v2()] is OR-ed with 
[SQLITE_DETERMINISTIC], then SQLite will treat that function as if it
................................................................................
[SQLITE_DETERMINISTIC] and if that function ends up being used in
the WHERE clause of a [partial index] or in an
[expression index], then when the function begins to return different
answers, the associated index may become corrupt.  If an SQL function
is nearly deterministic (which is to say, if it only rarely changes,
like [sqlite_version()]) and it is used in an index that becomes
corrupt, the corruption can be fixed by running [REINDEX].

<title>Deterministic SQL Functions</title>
<tcl>hd_keywords {deterministic function} {deterministic functions}\
     {deterministic SQL functions} {non-deterministic functions}</tcl>

<fancy_format>

<h1>Overview</h1>

<p>
SQL functions in SQLite can be either "deterministic" or "non-deterministic".

<p>
A deterministic function always gives the same answer whenever it has
the same inputs.  Most built-in SQL functions in SQLite are
deterministic.  For example, the [abs|abs(X)] function always returns
................................................................................
are examples of non-deterministic functions:

<ul>
<li> [random()]
<li> [changes()]
<li> [last_insert_rowid()]
<li> [sqlite3_version()]

</ul>

<p>
The [random()] function is obviously non-deterministic because it gives
a different answer every time it is invoked.  The answers from [changes()]
and [last_insert_rowid()] depend on prior SQL statements, and so they
are also non-deterministic. The


[sqlite3_version()] function is mostly constant, but it can change when
SQLite is upgraded, and so even though it always returns the same answer
for any particular session, because it can change answers across sessions
it is still considered non-deterministic.


<h1>Restrictions on the use of non-deterministic functions</h1>

<p>
There are some contexts in SQLite that do not allow the use of
non-deterministic functions:

<ul>
<li>In the expression of a [CHECK constraint].
<li>In the WHERE clause of a [partial index].
<li>In an expression used as part of an [expression index].
</ul>

<p>
In the cases above, the values returned by the function is recorded
in the index b-tree.  If the function later starts returning a different
value, then the index will be seen as corrupt.  Hence, to avoid corrupt
indexes, only deterministic functions can be used.

<tcl>hd_fragment dtexception {date/time special case}</tcl>
<h1>Special-case Processing For Date/Time Functions</h1>

<p>
The built-in [date and time functions] of SQLite are a special case.
These functions are usually considered deterministic.  However, if
these functions use the string "now" as the date, or if they use
the [localtime modifier] or the [utc modifier], then they are
considered non-deterministic.  Because the inputs to functions are
not necessarily known until run-time, the date/time functions will
throw an exception if they encounter any of the non-deterministic
features in a context where only deterministic functions are allows.

<p>
Prior to SQLite 3.20.0 ([dateof:3.20.0]) all date/time functions were
always considered non-deterministic.  The ability for date/time functions
to be deterministic sometimes and non-deterministic at other times,
depending on their arguments, was added for the 3.20.0 release.

<h1>Application-defined deterministic functions</h1>

<p>
By default, [application-defined SQL functions] are considered to
be non-deterministic.  However, if the 4th parameter to
[sqlite3_create_function_v2()] is OR-ed with 
[SQLITE_DETERMINISTIC], then SQLite will treat that function as if it
................................................................................
[SQLITE_DETERMINISTIC] and if that function ends up being used in
the WHERE clause of a [partial index] or in an
[expression index], then when the function begins to return different
answers, the associated index may become corrupt.  If an SQL function
is nearly deterministic (which is to say, if it only rarely changes,
like [sqlite_version()]) and it is used in an index that becomes
corrupt, the corruption can be fixed by running [REINDEX].

<p>
The interfaces necessary to construct a function that is sometimes
deterministic and sometimes non-deterministic depending on their
inputs, such as the built-in date/time functions, are not published.
Generic [application-defined SQL functions] must
be always deterministic or always non-deterministic.