Documentation Source Text

we can document the problem.

<h1>SQLite Is Embedded, Not Client-Server</h1>

<p>
When ever comparing SQLite to other SQL database engines like
SQL Server, PostgreSQL, MySQL, or Oracle, it is important first of all
to realize the SQLite is not intended as a replacement or competitor to
any of those systems.  SQLite is [serverless].  There is no separate
server process that manages the database.  An application interact
with the database engine using function calls, not be sending messages
to a separate process or thread.

<p>
The fact that SQLite is embedded and [serverless] instead of being
................................................................................
But to retain backwards compatibility, if there are columns named TRUE or
FALSE, then the keywords are treated as identifiers referencing those
columns, rather than BOOLEAN literals.

<h2>No Separate DATETIME Datatype</h2>

<p>
SQLite as no DATETIME datatype.
Instead, dates and times can be stored in any of these ways:

<ul>
<li> As a TEXT string in the ISO-8610 format.  Example: '2018-04-02 12:13:46'.
<li> As an INTEGER number of seconds since 1970 (also known as "unix time").
<li> As a REAL value that is the fractional 
     [https://en.wikipedia.org/wiki/Julian_day|Julian day number].
................................................................................
That Are Not In The GROUP BY Clause</h1>

<p>
In most SQL implementations, output columns of an aggregate query
may only reference aggregate functions or columns named in the
GROUP BY clause.  It does not make good sense to reference an ordinary
column in an aggregate query because each output row might be composed
from two more more rows in the input table(s).

<p>
SQLite does not impose this restriction.
The output columns from an aggregate query can be arbitrary expressions
that include columns not found in GROUP BY clause.
This feature has two uses:

................................................................................

<li><p>
If a query contains no aggregate functions at all, then a GROUP BY
clause can be added as a substitute of DISTINCT ON clause.  In other words,
output rows are filtered so that only one row is shows for each distinct
set of values in the GROUP BY clause.  If two or more output rows would
have otherwise had the same set of values for the GROUP BY columns, then
the one of the rows is chosen arbitrarily.
</ol>

<h1>Does Not Do Full Unicode Case Folding By Default</h1>

<p>
SQLite does not know about the upper-case/lower-case distinction
for all unicode characters.  SQL functions like
................................................................................
when SQLite was first being designed) SQLite will also interpret
a double-quotes string as
string literal if it does not match any valid identifier.
<p>
This misfeature means that a misspelled double-quoted
identifier will be interpreted as a string literal, rather than generating
an error.
It also lures developers who are new to the SQL language into
bad habit of using double-quoted string literals when they
really need to learn to use the correct single-quoted string literal form.
<p>
In hindsight, we should not have tried to make SQLite accept MySQL 3.x
syntax, and should have never allowed double-quoted string literals.
However, there are countless applications that make use of
double-quoted string literals and so we continue to support

we can document the problem.

<h1>SQLite Is Embedded, Not Client-Server</h1>

<p>
When ever comparing SQLite to other SQL database engines like
SQL Server, PostgreSQL, MySQL, or Oracle, it is important first of all
to realize that SQLite is not intended as a replacement or competitor to
any of those systems.  SQLite is [serverless].  There is no separate
server process that manages the database.  An application interact
with the database engine using function calls, not be sending messages
to a separate process or thread.

<p>
The fact that SQLite is embedded and [serverless] instead of being
................................................................................
But to retain backwards compatibility, if there are columns named TRUE or
FALSE, then the keywords are treated as identifiers referencing those
columns, rather than BOOLEAN literals.

<h2>No Separate DATETIME Datatype</h2>

<p>
SQLite has no DATETIME datatype.
Instead, dates and times can be stored in any of these ways:

<ul>
<li> As a TEXT string in the ISO-8610 format.  Example: '2018-04-02 12:13:46'.
<li> As an INTEGER number of seconds since 1970 (also known as "unix time").
<li> As a REAL value that is the fractional 
     [https://en.wikipedia.org/wiki/Julian_day|Julian day number].
................................................................................
That Are Not In The GROUP BY Clause</h1>

<p>
In most SQL implementations, output columns of an aggregate query
may only reference aggregate functions or columns named in the
GROUP BY clause.  It does not make good sense to reference an ordinary
column in an aggregate query because each output row might be composed
from two or more rows in the input table(s).

<p>
SQLite does not impose this restriction.
The output columns from an aggregate query can be arbitrary expressions
that include columns not found in GROUP BY clause.
This feature has two uses:

................................................................................

<li><p>
If a query contains no aggregate functions at all, then a GROUP BY
clause can be added as a substitute of DISTINCT ON clause.  In other words,
output rows are filtered so that only one row is shows for each distinct
set of values in the GROUP BY clause.  If two or more output rows would
have otherwise had the same set of values for the GROUP BY columns, then
one of the rows is chosen arbitrarily.
</ol>

<h1>Does Not Do Full Unicode Case Folding By Default</h1>

<p>
SQLite does not know about the upper-case/lower-case distinction
for all unicode characters.  SQL functions like
................................................................................
when SQLite was first being designed) SQLite will also interpret
a double-quotes string as
string literal if it does not match any valid identifier.
<p>
This misfeature means that a misspelled double-quoted
identifier will be interpreted as a string literal, rather than generating
an error.
It also lures developers who are new to the SQL language into the
bad habit of using double-quoted string literals when they
really need to learn to use the correct single-quoted string literal form.
<p>
In hindsight, we should not have tried to make SQLite accept MySQL 3.x
syntax, and should have never allowed double-quoted string literals.
However, there are countless applications that make use of
double-quoted string literals and so we continue to support