Documentation Source Text

  <p>If this option is defined, then it must also be 
  defined when using the 'lemon' tool to generate a parse.c
  file. Because of this, this option may only be used when the library is built
  from source, not from the [amalgamation] or from the collection of
  pre-packaged C files provided for non-Unix like platforms on the website.
  </p>
}








COMPILE_OPTION {YYTRACKMAXSTACKDEPTH} {
  This option causes the LALR(1) parser stack depth to be tracked
  and reported using the [sqlite3_status]([SQLITE_STATUS_PARSER_STACK],...)
  interface.  SQLite's LALR(1) parser has a fixed stack depth
  (determined at compile-time using the [YYSTACKDEPTH] options).
  This option can be used to help determine if an application is

  <p>If this option is defined, then it must also be 
  defined when using the 'lemon' tool to generate a parse.c
  file. Because of this, this option may only be used when the library is built
  from source, not from the [amalgamation] or from the collection of
  pre-packaged C files provided for non-Unix like platforms on the website.
  </p>
}

COMPILE_OPTION {SQLITE_ENABLE_UNLOCK_NOTIFY} {
  This option enables the [sqlite3_unlock_notify()] interface and
  its associated functionality.  See the documentation titled
  [Using the SQLite Unlock Notification Feature] for additional
  information.
}

COMPILE_OPTION {YYTRACKMAXSTACKDEPTH} {
  This option causes the LALR(1) parser stack depth to be tracked
  and reported using the [sqlite3_status]([SQLITE_STATUS_PARSER_STACK],...)
  interface.  SQLite's LALR(1) parser has a fixed stack depth
  (determined at compile-time using the [YYSTACKDEPTH] options).
  This option can be used to help determine if an application is

</td>
<td width="20"></td><td bgcolor="#80a796" width="1"></td><td width="20"></td>
<td valign="top">
<h3>Current Status</h3>

<p><ul>
<li><a href="releaselog/3_6_11.html">Version 3.6.11</a>
of SQLite is recommended for all new development.  Upgrading from
version 3.6.10 is optional.  Upgrading from versions prior to 3.6.10
is recommended.</li>
</ul></p>

<h3>Common Links</h3>

</td>
<td width="20"></td><td bgcolor="#80a796" width="1"></td><td width="20"></td>
<td valign="top">
<h3>Current Status</h3>

<p><ul>
<li><a href="releaselog/3_6_12.html">Version 3.6.12</a>
of SQLite is recommended for all new development.  Upgrading from
version 3.6.10 is optional.  Upgrading from versions prior to 3.6.10
is recommended.</li>
</ul></p>

<h3>Common Links</h3>

interface.  The TCL and TH3 test harnesses are both capable of
inserting a modified version of malloc() that can be rigged fail 
after a certain number of allocations.  These instrumented mallocs
can be set to fail only once and then start working again, or to
continue failing after the first failure.  OOM tests are done in a
loop.  On the first iteration of the loop, the instrumented malloc
is rigged to fail on the first allocation.  Then some SQLite operation
is carried out and checks or done to make sure SQLite handled the
OOM error correctly.  Then the time-to-failure counter
on the instrumented malloc is increased by one and the test is
repeated.  The loop continues until the entire operation runs to
completion without ever encountering a simulated OOM failure.
Tests like this are run twice, once with the instrumented malloc
set to fail only once, and again with the instrumented malloc set
to fail continuously after the first failure.</p>

interface.  The TCL and TH3 test harnesses are both capable of
inserting a modified version of malloc() that can be rigged fail 
after a certain number of allocations.  These instrumented mallocs
can be set to fail only once and then start working again, or to
continue failing after the first failure.  OOM tests are done in a
loop.  On the first iteration of the loop, the instrumented malloc
is rigged to fail on the first allocation.  Then some SQLite operation
is carried out and checks are done to make sure SQLite handled the
OOM error correctly.  Then the time-to-failure counter
on the instrumented malloc is increased by one and the test is
repeated.  The loop continues until the entire operation runs to
completion without ever encountering a simulated OOM failure.
Tests like this are run twice, once with the instrumented malloc
set to fail only once, and again with the instrumented malloc set
to fail continuously after the first failure.</p>

  lock is available instead of returning SQLITE_LOCKED immediately, for
  use in multi-threaded applications. If the sqlite3_blocking_step() function
  presented to the left returns SQLITE_LOCKED, this indicates that to block 
  would deadlock the system.

<p>
  The [sqlite3_unlock_notify()] API, which is only available if the library is
  compiled with the pre-processor symbol SQLITE_ENABLE_UNLOCK_NOTIFY defined,
  is [sqlite3_unlock_notify | documented here]. This page is no substitute for
  reading the full API documentation!

<p><b>The sqlite3_unlock_notify() API</b>

<p>
  After a call to [sqlite3_step()] returns SQLITE_LOCKED, the
................................................................................
    SQLITE_LOCKED_SHAREDCACHE. Otherwise, in the "DROP TABLE|INDEX" case,
    it is just plain SQLITE_LOCKED. Another solution might be to limit
    the number of times that any single query could be reattempted (to say 
    100). Although this might be less efficient than one might wish, the 
    situation in question is not likely to occur often.

<div style="clear:both"></div>

  lock is available instead of returning SQLITE_LOCKED immediately, for
  use in multi-threaded applications. If the sqlite3_blocking_step() function
  presented to the left returns SQLITE_LOCKED, this indicates that to block 
  would deadlock the system.

<p>
  The [sqlite3_unlock_notify()] API, which is only available if the library is
  compiled with the pre-processor symbol [SQLITE_ENABLE_UNLOCK_NOTIFY] defined,
  is [sqlite3_unlock_notify | documented here]. This page is no substitute for
  reading the full API documentation!

<p><b>The sqlite3_unlock_notify() API</b>

<p>
  After a call to [sqlite3_step()] returns SQLITE_LOCKED, the
................................................................................
    SQLITE_LOCKED_SHAREDCACHE. Otherwise, in the "DROP TABLE|INDEX" case,
    it is just plain SQLITE_LOCKED. Another solution might be to limit
    the number of times that any single query could be reattempted (to say 
    100). Although this might be less efficient than one might wish, the 
    situation in question is not likely to occur often.

<div style="clear:both"></div>

HLR H40310 
SQLite shall recognize as a VARIABLE token the a question-mark (u003f)
followed by zero or more NUMERIC characters.

HLR H40320 
SQLite shall recognize as a VARIABLE token one of the characters
at-sign (u0040), dollar-sign (u0024), or colon (u003a) followed
by a parameter name.

HLR H40330 
SQLite shall recognize as a VARIABLE token the shape-sign (u0023)
followed by a parameter name that does not begin with a
NUMERIC character.

HLR H41010 
SQLite shall divide input SQL text into tokens working from left to
right.

HLR H41020 
At each step in the SQL tokenization process, SQLite shall extract
the longest possible token from the remaining input text.
................................................................................

HLR H41845 
SQLite shall recognize the 4-character sequenence "WHEN" in any combination of upper and lower case letters as the keyword token WHEN.

HLR H41848 
SQLite shall recognize the 5-character sequenence "WHERE" in any combination of upper and lower case letters as the keyword token WHERE.

HLR H42000 
The SQLite parser shall accept SQL statements conforming to the following
syntax:
<center>[syntax/sql-stmt.gif]</center>

HLR H42002 
The preparation of an SQL statement that is not accepted by
the SQLite parser shall fail with an error.

HLR H42004 
SQLite shall use the built-in NOCASE collating sequence when comparing
identifiers and datatype names within SQL statements during
statement preparation.

HLR H42008 
A token received by the parser shall be converted into an ID token
if the original token value would have resulted in a syntax error,
a token value of ID will allow the parse to continue,
and if the original token value was one of:
ABORT
AFTER
ANALYZE
................................................................................
TEMP
TRIGGER
UNION
VACUUM
VIEW
VIRTUAL

HLR H42010 
The SQLite parser shall accept BEGIN statements
that conform to the following syntax:
<blockquote><pre>
cmd ::= BEGIN transaction_type transaction_name.
transaction_type ::= .
transaction_type ::= DEFERRED.
transaction_type ::= IMMEDIATE.
transaction_type ::= EXCLUSIVE.
transaction_name ::= .
transaction_name ::= TRANSACTION.
transaction_name ::= TRANSACTION name.
</pre></blockquote>

HLR H42012 
A token received by the parser shall be converted into an ANY token
if the original token value would have resulted in a syntax error
and if a token value of ANY will allow the parse to continue.

HLR H42013 
The successful evaluation of a BEGIN statement shall
cause the [database connection] to exit autocommit mode.

HLR H42016 
The evaluation of a BEGIN TRANSACTION statement shall fail with an error
if the [database connection] is not in autocommit mode at the
start of evaluation.

HLR H42019 
If the <i>transaction_type</i> keyword is omitted from a
BEGIN TRANSACTION statement then the behavior shall be the same
as if the DEFERRED keyword were used.

HLR H42022 
When the DEFERRED keyword appears in a BEGIN statement
the locking state of the underlying database files shall be
the same before and after the statement is evaluated.

HLR H42025 
When the IMMEDIATE keyword appears in a BEGIN statement
then successful evaluation of the statement shall cause a RESERVED
lock to be obtained for all underlying database files.

HLR H42028 
When the EXCLUSIVE keyword appears in a BEGIN statement
then successful evaluation of the statement shall cause a EXCLUSIVE
lock to be obtained for all underlying database files.

HLR H42110 
SQLite shall accept the following COMMIT statement syntax:
<blockquote><pre>
cmd ::= COMMIT transaction_name.
cmd ::= END transaction_name.
</pre></blockquote>

HLR H42113 
The successful evaluation of COMMIT statement places the
[database connection] in autocommit mode.

HLR H42116 
If a [database connection] is already in autocommit mode when
a COMMIT statement is evaluated, then the statement shall fail
with an error.

HLR H42210 
The SQLite parser shall accept ROLLBACK statements
that conform to the following syntax:
<blockquote><pre>
cmd ::= ROLLBACK transaction_name.
</pre></blockquote>

HLR H42213 
The successful evaluation of ROLLBACK statement places the
[database connection] in autocommit mode.

HLR H42216 
If a [database connection] is already in autocommit mode when
a ROLLBACK statement is invoked, then the statement invocation
shall fail with an error.

HLR H42222 
Other pending statements on the same [database connection]
as a successfully evaluated ROLLBACK statement shall be aborted.

HLR H42225 
The successful evaluation of a ROLLBACK statement causes the
current transaction on the [database connection] to roll back.

HLR H42310 
The SQLite parser shall accept CREATE TABLE statements
that conform to the following syntax:
<blockquote><pre>
cmd ::= CREATE temp TABLE ifnotexists fullname table_definition.
temp ::= .
temp ::= TEMP.
ifnotexists ::= .
ifnotexists ::= IF NOT EXISTS.
</pre></blockquote>

HLR H42313 
When the TEMP keyword appears in a CREATE TABLE statement and the
<i>databasename</i> exists and is something other than "temp", then
the preparation of the CREATE TABLE statement shall fail with an error.

HLR H42316 
When the TEMP keyword appears in a CREATE TABLE statement the behavior
shall be as if the <i>databasename</i> where "temp".

HLR H42319 
The successful evaluation of a CREATE TABLE statement shall cause
a new SQL table whose name is given by the <i>objectname</i> to be
created in the schema of the database whose name is given by the
<i>databasename</i>.

HLR H42322 
If a CREATE TABLE statement specifies no <i>databasename</i> and omits
the TEMP keyword then the behavior shall be as if a <i>databasename</i>
of "main" where used.

HLR H42325 
The preparation of a CREATE TABLE statement shall fail with an
error if the IF NOT EXISTS clause is omitted and the <i>objectname</i>
is the same as the name of a table or view
in the same database.

HLR H42328 
The evaluation of a CREATE TABLE statement shall be a silent no-op if the
IF NOT EXISTS clause is present and the <i>objectname</i>
is the same as the name of a table or view
in the same database.

HLR H42331 
The preparation of a CREATE TABLE statement shall fail with an error if the
the <i>objectname</i> is the same as the name of an index
in any database attached to the same [database connection].

HLR H42334 
The preparation of a CREATE TABLE statement shall fail with an error if the
the <i>databasename</i> references a database that is not
attached to the same [database connection].

HLR H42410 
The SQLite parser shall accept the following syntax for the
<i>table_definition</i> section of a CREATE TABLE statement:
<blockquote><pre>
table_definition ::= LP columnlist constraint_opt RP.
columnlist ::= column.
columnlist ::= columnlist COMMON column.
constraint_opt ::= .
constraint_opt ::= COMMA constraint_list.
</pre></blockquote>

HLR H42413 
The SQLite parser shall accept the following syntax
for the <i>column</i> component of a <i>table_definition</i>.
<blockquote><pre>
column ::= name column_type column_constraint_list.
column_type ::= .
column_type ::= typename.
column_type ::= typename LP signed_int RP.
column_type ::= typename LP signed_int COMMA signed_int RP.
typename ::= identifier.
typename ::= typename identifier.
signed_int ::= INTEGER.
signed_int ::= MINUS INTEGER.
signed_int ::= PLUS INTEGER.
</pre></blockquote>

HLR H42416 
The preparation of an ordinary [CREATE TABLE] statement shall fail
with an error if it specifies two or more columns with the same name.

HLR H42419 
The datatype affinity of each column in a table generate by an
ordinary [CREATE TABLE] statement
shall be determined from the <i>column_type</i>
text using the following 5-step algorithm:
<ol>
<li><p> If the <i>column_type</i> contains the string "INT"
then the affinity is INTEGER.</p></li>
<li><p> Else if the <i>column_type</i> contains one of the strings
"CHAR", "CLOB", or "TEXT" then the affinity is TEXT. </p></li>
<li><p> Else if the <i>column_type</i> contains the string "BLOB"
or is omitted then the affinity is NONE. </p></li>
<li><p> Else if the <i>column_type</i> constains one of the strings
"REAL", "FLOA", or "DOUB" then the affinity
is REAL. </p></li>
<li><p> Otherwise the affinity is NUMERIC. </p></li>
</ol>

HLR H42450 
The SQLite parser shall accept the following syntax for the list of column
constraints and modifiers that follows a column definition in
an ordinary [CREATE TABLE] statement.
<blockquote><pre>
column_constraint_list ::= .
column_constraint_list ::= column_constraint_list named_column_constraint.
named_column_constraint ::= CONSTRAINT name column_constraint.
named_column_constraint ::= column_constraint.
column_constraint ::= DEFAULT term.
column_constraint ::= DEFAULT identifier.
column_constraint ::= DEFAULT PLUS term.
column_constraint ::= DEFAULT MINUS term.
column_constraint ::= DEFAULT LP expr RP.
column_constraint ::= NULL conflict.
column_constraint ::= NOT NULL conflict.
column_constraint ::= PRIMARY KEY sortorder conflict autoincr.
column_constraint ::= UNIQUE conflict.
column_constraint ::= CHECK LP expr RP.
column_constraint ::= COLLATE identifier.
column_constraint ::= foreign_key_constraint.
column_constraint ::= deferrable_constraint.
autoincr ::= .
autoincr ::= AUTOINCR.
indexlist_opt ::= .
indexlist_opt ::= LP indexlist RP.
conflict ::= .
conflict ::= ON CONFLICT IGNORE.
conflict ::= ON CONFLICT REPLACE.
conflict ::= ON CONFLICT ABORT.
conflict ::= ON CONFLICT FAIL.
conflict ::= ON CONFLICT ROLLBACK.
</pre></blockquote>

HLR H42453 
When a column as a DEFAULT constraint, the default value for the
column shall be the value specified by that constraint.

HLR H42456 
If a column has no DEFAULT constraint then the default value for
that column shall be NULL.

HLR H42459 
If a column has no NOT NULL constraint then the NULL conflict
resolution behavior for the column shall be NONE.

HLR H42462 
If a column has a NOT NULL constraint and that constrait lacks
an ON CONFLICT clause
then the null-conflict resolution behavior for the column shall
be ABORT.

HLR H42465 
If a column has a NOT NULL constraint and that constraint
has an ON CONFLICT clause
then the null-conflict resolution behavior for the column shall
be the behavior specified by the ON CONFLICT clause.

HLR H42467 
A column without a COLLATE constraint shall have a default
collating sequence of BINARY.

HLR H42468 
A column with a COLLATE constraint shall have a default
collating sequence as specified by the COLLATE constraint.

HLR H42470 
If the datatype of a single-column PRIMARY KEY is
exactly "INTEGER" then the name of that column shall be
an alias for the table rowid.

HLR H42472 
If a table contains no column named "ROWID" then "ROWID" shall be
an alias for the table rowid.

HLR H42474 
If a table contains no column named "OID" then "OID" shall be
an alias for the table rowid.

HLR H42476 
If a table contains no column named "_ROWID_" then "_ROWID_" shall be
an alias for the table rowid.

HLR H42478 
A table shall have an autoincrementing rowid if and only if
the PRIMARY KEY for the table is an alias for the rowid and
the PRIMARY KEY declaration uses the AUTOINCR keyword.

HLR H42480 
Successful evaluation of a CREATE TABLE statement shall create
an index for every UNIQUE constraint where the created index has
a conflict resolution algorithm as specified by the ON CONFLICT
clause of the UNIQUE constraint or a conflict resolution algorithm
of ABORT if there is no ON CONFLICT clause on the constraint.

HLR H42510 
The SQLite parser shall accept the following syntax for the list of table
contraints that occurs at the end of an ordinary [CREATE TABLE] statement.
<blockquote><pre>
constraint_list ::= constraint.
constraint_list ::= constraint_list constraint.
constraint_list ::= constraint_list COMMA constraint.
constraint ::= CHECK LP expr RP conflict.
constraint ::= CONSTRAINT name.
constraint ::= FOREIGN KEY LP columnlist RP foreign_key_constraint defer_opt.
constraint ::= PRIMARY KEY LP indexlist autoinc RP conflict.
constraint ::= UNIQUE LP indexlist RP conflict.
</pre></blockquote>

HLR H42513 
The preparation of a CREATE TABLE statement that contains more
than one PRIMARY KEY constraint shall fail with an error.

HLR H42516 
The preparation of a CREATE TABLE statement that contains a
CHECK constraint that uses a subquery shall fail with an error.

HLR H42517 
The preparation of a CREATE TABLE statement that contains a
CHECK constraint that uses a parameter shall fail with an error.

HLR H42518 
Name resolution of the <i>expr</i> with each CHECK constraint of
a CREATE TABLE statement shall be carried out using a name context
with an empty result set and a source set holding
single source element that is the
table being created.

HLR H42521 
The preparation of a CREATE TABLE statement that contains a
DEFAULT constraint with an non-constant expression
shall fail with an error.

HLR H42536 
A PRIMARY KEY constraint that does not result in a rowid alias
shall have the same effect as a UNIQUE constraint.

HLR H42539 
Preparation of a CREATE TABLE statement shall fail with an
error if the <i>indexlist</i> of either a table PRIMARY KEY
or a table UNIQUE constraint references a column that is not
a column in the table.

HLR H42570 
The SQLite parser shall accept the following syntax for a foreign
key constraint as either a separate constraint or as part of a
column constraint in an ordinary [CREATE TABLE] statement.
<blockquote><pre>
foreign_key_constraint ::= REFERENCES name indexlist_opt fkarglist.
defer_opt ::= .
defer_opt ::= deferrable_constraint.
deferrable_constraint ::= NOT DEFERRABLE initially_deferred_clause.
deferrable_constraint ::= DEFERRABLE initially_deferred_clause.
fkarglist ::= .
fkarglist ::= fkarglist fkarg.
fkarg ::= MATCH name.
fkarg ::= ON DELETE fkaction.
fkarg ::= ON UPDATE fkaction.
fkarg ::= ON INSERT fkaction.
fkaction ::= SET NULL.
fkaction ::= SET DEFAULT.
fkaction ::= CASCADE.
fkaction ::= RESTRICT.
initially_deferred_clause ::= .
initially_deferred_clause ::= INITIALLY DEFERRED.
initially_deferred_clause ::= INITIALLY IMMEDIATE.
</pre></blockquote>

HLR H42610 
The SQLite parser shall accept the following syntax for creating new
database tables from the result set of SELECT statements.
<blockquote><pre>
table_definition ::= AS select.
</pre></blockquote>

HLR H42613 
The table generated by a CREATE TABLE AS statement shall have the
same number of columns as the result set of the SELECT.

HLR H42616 
The names of the columns in a table generated by a CREATE TABLE AS
statement shall have base names which are the names of the columns
in the result set of the SELECT statement

HLR H42617 
Each column name in a table generated by a CREATE TABLE AS
statement shall have an arbitrary suffix appended to its basename
if and only if such a suffix is necessary to make the name
distinct from all preceding column names in the table.

HLR H42619 
All columns in a table generated by a CREATE TABLE AS statement
shall have a default value of NULL.

HLR H42622 
All columns in a table generated by a CREATE TABLE AS statement
shall have a NULL conflict resolution behavior of NONE.

HLR H42625 
All columns in a table generated by a CREATE TABLE AS statement
shall have an affinity of NONE.

HLR H42628 
All columns in a table generated by a CREATE TABLE AS statement
shall have a default collating sequence of BINARY.

HLR H42700 
The SQLite parser shall accept DROP TABLE statements
that conform to the following syntax.
<blockquote><pre>
cmd ::= DROP TABLE ifexists fullname.
ifexists ::= .
ifexists ::= IF EXISTS.
</pre></blockquote>

HLR H42710 
The preparation of a DROP TABLE statement shall fail with an
error if the statement lacks an IF EXISTS clause and the
<i>fullname</i> does not reference a existing table.

HLR H42713 
The evaluation of a DROP TABLE statement shall be a silent no-op
if the the statement has an IF EXISTS clause and the
<i>fullname</i> does not reference a existing table.

HLR H42716 
The successful evaluation of a DROP TABLE statement shall cause
the table identified by <i>fullname</i> to be removed from its
database and discarded.

HLR H42719 
The successful evaluation of a DROP TABLE statement shall cause
all indices attached to the table identified by <i>fullname</i>
to be removed from their database and discarded.

HLR H42721 
The successful evaluation of a DROP TABLE statement shall cause
all triggers attached to the table identified by <i>fullname</i>
to be removed from their database and discarded.

HLR H42724 
The preparation of a DROP TABLE statement shall fail with an
error if <i>fullname</i> is a system table.

HLR H42800 
The SQLite parser shall accept CREATE INDEX statements that
conform to the following syntax:
<blockquote><pre>
cmd ::= CREATE unique INDEX ifnotexists fullname ON tablename LP indexlist RP.
tablename ::= name.
indexlist ::= indexlist COMMA columnname collate sortorder.
indexlist ::= columnname collate sortorder.
columnname ::= name.
collate ::= .
collate ::= COLLATE identifier.
sortorder ::= .
sortorder ::= ASC.
sortorder ::= DESC.
</pre></blockquote>

HLR H42803 
The target database of a CREATE INDEX statement shall be the
<i>databasename</i> specified in the <i>fullname</i> term of the
statement if the <i>databasename</i> exists.

HLR H42806 
If the <i>fullname</i> term of a CREATE INDEX statement does not
specify a <i>databasename</i> and the <i>tablename</i> references a table
that is in the "temp" database, then the target database for the statement
shall be "temp".

HLR H42809 
If the <i>fullname</i> term of a CREATE INDEX statement does not
specify a <i>databasename</i> and the <i>tablename</i> references a table
that is not in the "temp" database, then the target database for the
statement shall be "main".

HLR H42812 
The preparation of a CREATE INDEX statement shall fail with an error if the
<i>databasename</i> of the <i>fullname</i> exists and references a database
that is not attached to the same [database connection].

HLR H42815 
The preparation of a CREATE INDEX statement shall fail with an error if the
<i>tablename</i> does not reference an ordinary table in the
database of the statement.

HLR H42818 
A successful evaluation of a CREATE INDEX statement shall create a
new index called <i>objectname</i>
in the database of the statement and attached to the
table identified by <i>tablename</i> in that same database.

HLR H42821 
An index generated by a CREATE INDEX statement that omits the
UNIQUE keyword shall have a conflict resolution behavior
of NONE.

HLR H42824 
An index generated by a CREATE INDEX statement that includes the
UNIQUE keyword shall have a conflict resolution behavior
of ABORT.

HLR H42830 
The preparation of a CREATE INDEX statement shall fail with an error if any
<i>columnname</i> value within the <i>indexlist</i> is not the
name of one of the columns of the <i>tablename</i> table.

HLR H42833 
The collating sequence for each column of an index shall be the
collating sequence specified in the <i>indexlist</i>.

HLR H42836 
If an index column does not specify a collating sequence then
the collating sequence shall be
the default collating sequence of the corresponding table column.

HLR H42839 
The sort order for an index column shall be descending if and only
if the DESC keyword is used in the <i>indexlist</i> entry for that
term.

HLR H42842 
The preparation of a CREATE INDEX statement shall fail with an error
if the <i>tablename</i> refers to a system table.

HLR H42900 
The SQLite parser shall accept DROP INDEX statements
that conform to the following syntax:
<blockquote><pre>
cmd ::= DROP INDEX ifexists fullname.
</pre></blockquote>

HLR H42910 
The preparation of a DROP INDEX statement shall fail with an
error if the statement lacks an IF EXISTS clause and the
<i>fullname</i> does not reference a existing index.

HLR H42913 
The evaluation of a DROP INDEX statement shall be a silent no-op
if the the statement has an IF EXISTS clause and the
<i>fullname</i> does not reference a existing index.

HLR H42916 
The successful evaluation of a DROP INDEX statement shall cause
the index identified by <i>fullname</i> to be removed from its
database and discarded.

HLR H43100 
The SQLite parser shall accept CREATE VIEW statements
that conform to the following syntax:
<blockquote><pre>
cmd ::= CREATE temp VIEW ifnotexists fullname AS select.
</pre></blockquote>

HLR H43113 
When the TEMP keyword appears in a CREATE VIEW statement and the
<i>databasename</i> exists and is something other than "temp", then
the preparation of the CREATE VIEW statement shall fail with an error.

HLR H43116 
When the TEMP keyword appears in a CREATE VIEW statement the behavior
shall be as if the <i>databasename</i> where "temp".

HLR H43119 
The successful evaluation of a CREATE VIEW statement shall cause
a new view whose name is given by the <i>objectname</i> and is located
in the schema of the database whose name is given by the
<i>databasename</i>.

HLR H43122 
If a CREATE VIEW statement specifies no <i>databasename</i> and omits
the TEMP keyword then the behavior shall be as if a <i>databasename</i>
of "main" where used.

HLR H43125 
The preparation of a CREATE VIEW statement shall fail with an
error if the IF NOT EXISTS clause is omitted and the <i>objectname</i>
is the same as the name of a table or view
in the same database.

HLR H43128 
The evaluation of a CREATE VIEW statement shall be a silent no-op if the
IF NOT EXISTS clause is present and the <i>objectname</i>
is the same as the name of a table or view
in the same database.

HLR H43131 
The preparation of a CREATE VIEW statement shall fail with an error if the
the <i>objectname</i> is the same as the name of an index
in any database attached to the same [database connection].

HLR H43200 
The SQLite parser shall accept DROP VIEW statements
that conform to the following syntax:
<blockquote><pre>
cmd ::= DROP VIEW ifexists fullname.
</pre></blockquote>

HLR H43204 
The preparation of a DROP VIEW statement shall fail with an
error if the statement lacks an IF EXISTS clause and the
<i>fullname</i> does not reference a existing view.

HLR H43207 
The evaluation of a DROP VIEW statement shall be a silent no-op
if the the statement has an IF EXISTS clause and the
<i>fullname</i> does not reference a existing view.

HLR H43211 
The successful evaluation of a DROP VIEW statement shall cause
the view identified by <i>fullname</i> to be removed from its
database and discarded.

HLR H43214 
The successful evaluation of a DROP VIEW statement shall cause
all triggers attached to the view identified by <i>fullname</i>
to be removed from their database and discarded.

HLR H43234 
The preparation of a CREATE VIEW statement shall fail with an error if the
the <i>databasename</i> references a database that is not
attached to the same [database connection].

HLR H43237 
The view generated by a CREATE VIEW statement shall have the
same number of columns as the result set of the SELECT.

HLR H43241 
The names of the columns in a view generated by a CREATE VIEW
statement shall have base names which are the names of the columns
in the result set of the SELECT statement

HLR H43244 
Each column name in a table generated by a CREATE VIEW
statement shall have an arbitrary suffix appended to its basename
if and only if such a suffix is necessary to make the name
distinct from all preceding column names in the view.

HLR H43300 
The SQLite parser shall accept CREATE TRIGGER statements
that conform to the following syntax:
<blockquote><pre>
cmd ::= CREATE temp TRIGGER ifnotexists fullname trigger trigger_body.
trigger ::= trigger_time trigger_event foreach_clause when_clause.
trigger_body ::= BEGIN trigger_cmd_list END.
trigger_cmd_list ::= trigger_cmd_list trigger_cmd SEMI.
trigger_cmd_list ::= trigger_cmd_list.
trigger_cmd ::= DELETE FROM tablename where.
trigger_cmd ::= update_cmd tablename SET setlist where.
trigger_cmd ::= insert_cmd INTO tablename columnlist_opt VALUES LP exprlist RP.
trigger_cmd ::= insert_cmd INTO tablename columnlist_opt select.
trigger_cmd ::= select.
trigger_event ::= DELETE ON trigger_target.
trigger_event ::= INSERT ON trigger_target.
trigger_event ::= UPDATE OF columnlist ON trigger_target.
trigger_event ::= UPDATE ON trigger_target.
trigger_target ::= fullname.
trigger_time ::= AFTER.
trigger_time ::= BEFORE.
trigger_time ::= INSTEAD OF.
trigger_time ::=.
foreach_clause ::= FOR EACH ROW.
foreach_clause ::=.
when_clause ::= WHEN expr.
when_clause ::=.
</pre></blockquote>

HLR H43303 
When the TEMP keyword appears in a CREATE TRIGGER statement and the
<i>databasename</i> of the <i>fullname</i> exists
then the preparation of the statement
shall fail with an error.

HLR H43306 
When the TEMP keyword appears in a CREATE TRIGGER statement
the target database of the trigger shall be "temp".

HLR H43309 
When the TEMP keyword is omitted in a CREATE TRIGGER statement and the
<i>databasename</i> of the <i>fullname</i> is
omitted then the target database of the trigger shall be "main".

HLR H43312 
When the <i>databasename</i> of <i>fullname</i> in a CREATE TRIGGER
statement exists, then the target database shall be the database
named by <i>databasename</i>.

HLR H43315 
If a CREATE TRIGGER does not specify a <i>trigger_time</i> then
the <i>trigger_time</i> shall be BEFORE.

HLR H43318 
The preparation of a CREATE TRIGGER statement shall fail with an error
the <i>trigger_time</i> is INSTEAD OF and <i>trigger_target</i> is not
the name of view in the target database.

HLR H43321 
The preparation of a CREATE TRIGGER statement shall fail with an error
the <i>trigger_time</i> is not INSTEAD OF and <i>trigger_target</i> is not
the name of an ordinary table in the target database.

HLR H43324 
The preparation of a CREATE TRIGGER statement shall fail with an error
if the <i>trigger_target</i> is a system table.

HLR H43500 
The SQLite parser shall accept DROP TRIGGER statements
that conform to the following syntax:
<blockquote><pre>
cmd ::= DROP TRIGGER ifexists fullname.
</pre></blockquote>

HLR H43504 
The preparation of a DROP TRIGGER statement shall fail with an
error if the statement lacks an IF EXISTS clause and the
<i>fullname</i> does not reference a existing trigger.

HLR H43507 
The evaluation of a DROP TRIGGER statement shall be a silent no-op
if the the statement has an IF EXISTS clause and the
<i>fullname</i> does not reference a existing trigger.

HLR H43511 
The successful evaluation of a DROP TRIGGER statement shall cause
the trigger identified by <i>fullname</i> to be removed from its
database and discarded.

HLR H43514 
The successful evaluation of a DROP TRIGGER statement shall cause
all triggers attached to the trigger identified by <i>fullname</i>
to be removed from their database and discarded.

HLR H43600 
The SQLite parser shall accept CREATE VIRTUAL TABLE statements
that conform to the following syntax.
<blockquote><pre>
cmd ::= CREATE VIRTUAL TABLE fullname USING name vtab_arg_list.
vtab_arg_list ::= .
vtab_arg_list ::= LP vtab_arg_token RP.
vtab_arg_token ::= ANY.
vtab_arg_token ::= LP anylist RP.
anylist ::= .
anylist ::= anylist ANY.
</pre></blockquote>

HLR H43700 
The SQLite parser shall accept ALTER TABLE RENAME statements
that conform to the following syntax:
<blockquote><pre>
cmd ::= ALTER TABLE fullname RENAME TO name.
</pre></blockquote>

HLR H43750 
The SQLite parser shall accept ALTER TABLE ADD COLUMN statements
that conform to the following syntax:
<blockquote><pre>
cmd ::= ALTER TABLE fullname ADD column_keyword column.
column_keyword ::= .
column_keyword ::= COLUMNKW.
</pre></blockquote>

HLR H43810 
The SQLite parser shall accept INSERT statements that
conform to the following syntax:
<blockquote><pre>
cmd ::= insert_cmd INTO fullname columnlist_opt insert_content.
insert_cmd ::= INSERT.
insert_cmd ::= REPLACE.
insert_cmd ::= INSERT OR REPLACE.
insert_cmd ::= INSERT OR IGNORE.
insert_cmd ::= INSERT OR ABORT.
insert_cmd ::= INSERT OR FAIL.
insert_cmd ::= INSERT OR ROLLBACK.
columnlist_opt ::= .
columnlist_opt ::= LP columnlist RP.
columnlist ::= columnname.
columnlist ::= columnlist COMMA columnname.
</pre></blockquote>

HLR H43813 
The preparation of an INSERT statement shall fail with an error
if the <i>instcolist</i> contains a reference to a column which
is not a column in the table identified by <i>fullname</i> and is
not one of the special column named "ROWID", "OID", or "_ROWID_".

HLR H43816 
The preparation of an INSERT statement shall fail with an error
if <i>fullname</i> does not identify either a view with an
INSTEAD OF INSERT trigger or a table.

HLR H43819 
The preparation of an INSERT statement shall fail with an error
if the <i>objectname</i> of the <i>fullname</i> is "sqlite_master"
or "sqlite_temp_master" and the database connection is not in
writeable schema mode.

HLR H43821 
When the form of an INSERT statement is simply "INSERT" then the
default null- and uniqueness-conflict resolution algorithms shall
be used.

HLR H43824 
When the form of an INSERT statement is simply "REPLACE" then the
null- and uniqueness-conflict resolution algorithms shall all
change to REPLACE.

HLR H43827 
When the form of an INSERT statement is "INSERT OR <i>algorithm</i>"
then the null- and uniqueness-conflict resolution algorithms shall all
change to <i>algorithm</i>.

HLR H43831 
Name resolution in the <i>insert_content</i> term of an INSERT statement
shall be carried out using a name context
with an empty result set and a source set holding
single source element that is the <i>fullname</i> table.

HLR H43840 
The SQLite parser shall accept INSERT VALUE statements that
conform to the following syntax:
<blockquote><pre>
insert_content ::= VALUES LP exprlist RP.
</pre></blockquote>

HLR H43843 
The preparation of an INSERT VALUE statement shall fail with an
error if the <i>columnlist</i> element exists and the number of
entries in the <i>instcollist</i> is different
from the number of entries in the <i>exprlist</i>.

HLR H43846 
The preparation of an INSERT VALUE statement shall fail with an
error if the <i>columnlist</i> element does not exists and the number of
entries in the <i>exprlist</i> is different
from the number of columns in the table or view identified by
<i>fullname</i>.

HLR H43890 
The SQLite parser shall accept INSERT DEFAULT statements that
conform to the following syntax:
<blockquote><pre>
insert_contents ::= DEFAULT VALUES.
</pre></blockquote>

HLR H43900 
The SQLite parser shall accept DELETE statements that
conform to the following syntax:
<blockquote><pre>
cmd ::= DELETE FROM fullname where.
where ::= .
where ::= WHERE expr.
</pre></blockquote>

HLR H43904 
The preparation of a DELETE statement shall fail with an error if
the <i>fullname</i> element does not identify a view with an
INSTEAD OF DELETE trigger or a table.

HLR H43907 
The preparation of a DELETE statement shall fail with an error if
the <i>objectname</i> of the <i>fullname</i> element is "sqlite_master"
or "sqlite_temp_master" and the database connection is not in
writeable_schema mode.

HLR H43911 
Name resolution in the <i>where</i> term of a DELETE statement
shall be carried out using a name context
with an empty result set and a source set holding
single source element that is the <i>fullname</i> table.

HLR H44100 
The SQLite parser shall accept UPDATE statements that
conform to the following syntax:
<blockquote><pre>
cmd ::= update_cmd fullname SET setlist where.
update_cmd ::= UPDATE.
update_cmd ::= UPDATE OR IGNORE.
update_cmd ::= UPDATE OR REPLACE.
update_cmd ::= UPDATE OR ABORT.
update_cmd ::= UPDATE OR FAIL.
update_cmd ::= UPDATE OR ROLLBACK.
setlist ::= setting.
setlist ::= setlist COMMA setting.
setting ::= columnname EQ expr.
</pre></blockquote>

HLR H44113 
The preparation of an UPDATE statement shall fail with an error
if any <i>columnname</i>
is not a column in the table identified by <i>fullname</i> and is
not one of the special columns named "ROWID", "OID", or "_ROWID_".

HLR H44116 
The preparation of an UPDATE statement shall fail with an error
if <i>fullname</i> does not identify either a view with an
INSTEAD OF UPDATE trigger that covers all <i>columnname</i>s or a table.

HLR H44119 
The preparation of an UPDATE statement shall fail with an error
if the <i>objectname</i> of the <i>fullname</i> is "sqlite_master"
or "sqlite_temp_master" and the database connection is not in
writeable schema mode.

HLR H44121 
When the form of an UPDATE statement is simply "UPDATE" then the
default null- and uniqueness-conflict resolution algorithms shall
be used.

HLR H44127 
When the form of an UPDATE statement is "UPDATE OR <i>algorithm</i>"
then the null- and uniqueness-conflict resolution algorithms shall all
change to <i>algorithm</i>.

HLR H44131 
Name resolution in the <i>where</i> term of a DELETE statement
shall be carried out using a name context
with an empty result set and a source set holding
single source element that is the <i>fullname</i> table.

HLR H44200 
The SQLite parser shall accept VACUUM statements that
conform to the following syntax:
<blockquote><pre>
cmd ::= VACUUM.
cmd ::= VACUUM name.
</pre></blockquote>

HLR H44300 
The SQLite parser shall accept ANALYZE statements
that conform to the following syntax:
<blockquote><pre>
cmd ::= ANALYZE.
cmd ::= ANALYZE fullname.
</pre></blockquote>

HLR H44303 
The preparation of an ANALYZE statement
shall fail with an error if
the <i>fullname</i> is included and does not evaluate to
either an individual table name or the name of a database.

HLR H44400 
The SQLite parser shall accept REINDEX statements
that conform to the following syntax:
<blockquote><pre>
cmd ::= REINDEX.
cmd ::= REINDEX fullname.
</pre></blockquote>

HLR H44403 
The preparation of an ANALYZE statement
shall fail with an error if
the <i>fullname</i> is included and does not evaluate to
either an individual table name or the name of a database
or the name of a collating sequence.

HLR H44500 
cmd ::= ATTACH database_kw expr AS expr.
database_kw ::= .
database_kw ::= DATABASE.

HLR H44503 
The <i>expr</i> terms of an ATTACH statement that are
identifiers shall be interpreted as string literals.

HLR H44506 
The preparation of an ATTACH statement shall fail with an error
if either <i>expr</i> is not a constant expression.

HLR H44509 
The preparation of an ATTACH statement shall fail with an error
if the second <i>expr</i> evaluates to the name of a database
that is already attached to the database connection.

HLR H44600 
The SQLite parser shall accept DETACH statements
that conform to the following syntax:
<blockquote><pre>
cmd ::= DETACH database_kw expr.
</pre></blockquote>

HLR H44603 
The <i>expr</i> term of an DETACH statement that is an
identifier shall be interpreted as string literals.

HLR H44606 
The preparation of an DETACH statement shall fail with an error
if the <i>expr</i> is not a constant expression.

HLR H44609 
The preparation of an DETACH statement shall fail with an error
if the <i>expr</i> does not evaluate to the
name of an attached database other than "temp" or "main".

HLR H44700 
The SQLite parser shall accept the EXPLAIN keyword as a prefix
to other valid SQL statements, as shown by the following syntax:
<blockquote><pre>
sql_statement ::= EXPLAIN cmd SEMI.
</pre></blockquote>

HLR H44800 
The SQLite parser shall accept EXPLAIN QUERY PLAY as a prefix
to other valid SQL statements, as shown by the following syntax:
<blockquote><pre>
sql_statement ::= EXPLAIN QUERY PLAN cmd SEMI.
</pre></blockquote>

HLR H45000 
The SQLite parser shall accept SELECT statements that
conform to the following syntax:
<blockquote><pre>
cmd ::= select.
select ::= query.
select ::= select UNION query.
select ::= select UNION ALL query.
select ::= select EXCEPT query.
select ::= select INTERSECT query.
query ::= SELECT distinct resultset from where groupby having orderby limit.
distinct ::= .
distinct ::= DISTINCT.
groupby ::= .
groupby ::= GROUP BY exprlist.
having ::= .
having ::= HAVING expr.
orderby ::= .
orderby ::= ORDER BY exprlist.
limit ::=.
limit ::= LIMIT expr.
limit ::= LIMIT expr COMMA expr.
limit ::= LIMIT expr OFFSET expr.
resultset ::= result.
resultset ::= resultset COMMA result.
result ::= STAR.
result ::= tablename DOT STAR.
result ::= expr as.
from ::= .
from ::= FROM sourceset.
sourceset ::= source.
sourceset ::= sourceset joinop source.
source ::= fullname as on using.
source ::= LP select RP as on using.
as ::= .
as ::= AS name.
as ::= identifier.
on ::= .
on ::= ON expr.
using ::= .
using ::= USING LP columnlist RP.
joinop ::= COMMA.
joinop ::= JOIN.
joinop ::= JOIN_KW JOIN.
joinop ::= JOIN_KW JOIN_KW JOIN.
joinop ::= JOIN_KW JOIN_KW JOIN_KW JOIN.
</pre></blockquote>

HLR H45003 
The preparation of a statement containing a <i>select</i>
shall fail with an error if the <i>select</i> contains
two terms of the same compound query having a different number of columns
in their result sets.

HLR H45006 
The preparation of a statement containing a <i>select</i>
shall fail with an error if the <i>select</i> contains a compound query that
has an ORDER BY, GROUP BY, HAVING, or LIMIT clause on any term of than
the right-most.

HLR H45009 
The preparation of a statement containing a <i>select</i>
shall fail with an error if the <i>select</i> contains a compound query with
an ORDER BY or GROUP BY clause with a term that is not either
a token-by-token duplicate of the result columns of one of the
compound query terms, or the "AS" name of one of the compound
query terms, or a compile-time integer between 1 and N where N is
the number of columns in each compound query term.

HLR H45012 
The preparation of a statement containing a <i>select</i>
shall fail with an error if the <i>select</i> contains a join with two
or more of the following properties:
<ol>
<li> The NATURAL keyword in the <i>joinop</i> </li>
<li> An ON clause </li>
<li> A USING clause</li>
</ol>

HLR H45015 
The preparation of a statement containing a <i>select</i>
shall fail with an error if the <i>select</i> contains a <i>joinop</i>
that uses the keywords RIGHT or FULL.

HLR H45018 
The preparation of a statement containing a <i>select</i>
shall fail with an error if the <i>select</i> contains a <i>joinop</i>
that uses either of the keywords OUTER or LEFT
together with either INNER or CROSS.

HLR H45021 
The preparation of a statement containing a <i>select</i>
shall fail with an error if the <i>select</i> contains a <i>using</i>
that names columns that are not found in both the table to the
immediate right of the join and in the result set of all tables
to the left of the join.

HLR H45024 
The preparation of a statement containing a <i>select</i>
shall fail with an error if the <i>fullname</i> of a <i>source</i>
does not refer to an existing table or view.

HLR H45027 
The preparation of a statement containing a <i>limit</i>
shall fail with an error if any <i>expr</i> within the <i>limit</i>
does not evaluate to a compile-time integer.

HLR H45103 
Name resolution of a top-level SELECT statement shall use an
empty name context.

HLR H45106 
Name context of a <i>query</i> term shall be
constructed by adding a new inner name context layer
to the name context of the construct containing the <i>query</i>
term.

HLR H45109 
Name resolution of the <i>resultset</i> of a <i>query</i> shall
use the name context of the <i>query</i> with an empty result
set and the source set
configured to the <i>from</i> clause of the query.

HLR H45112 
Name resolution of all child terms of a <i>query</i> other than
<i>resultset</i> child shall use the name context of the <i>query</i>
with the result set configured to be the <i>resultset</i> clause of the
<i>query</i> and with the source set configured to be the
<i>from</i> clause of the query.

HLR H46000 
The SQLite parser shall accept PRAGMA statements
that conform to the following syntax:
<blockquote><pre>
cmd ::= PRAGMA fullname EQ DELETE.
cmd ::= PRAGMA fullname EQ ON.
cmd ::= PRAGMA fullname EQ name.
cmd ::= PRAGMA fullname EQ expr.
cmd ::= PRAGMA fullname LP name RP.
cmd ::= PRAGMA fullname LP expr RP.
cmd ::= PRAGMA fullname.
</pre></blockquote>

HLR H46003 
The evaluation of a PRAGMA statement with an unknown verb shall
be a silent no-op.

HLR H47000 
The SQLite parser shall accept expressions that
conform to the following syntax:
<blockquote><pre>
expr ::= BITNOT expr.
expr ::= CASE case_operand case_exprlist case_else END.
expr ::= CAST LP expr AS typetoken RP.
expr ::= EXISTS LP select RP.
expr ::= function_name LP STAR RP.
expr ::= function_name LP distinct exprlist RP.
expr ::= LP expr RP.
expr ::= LP select RP.
expr ::= MINUS expr.
expr ::= NOT expr.
expr ::= PLUS expr.
expr ::= RAISE LP IGNORE RP.
expr ::= RAISE LP ABORT COMMA name RP.
expr ::= RAISE LP FAIL COMMA name RP.
expr ::= RAISE LP ROLLBACK COMMA name RP.
expr ::= VARIABLE.
expr ::= expr AND expr.
expr ::= expr BITAND expr.
expr ::= expr BITOR expr.
expr ::= expr LSHIFT expr.
expr ::= expr RSHIFT expr.
expr ::= expr COLLATE ids.
expr ::= expr CONCAT expr.
expr ::= expr EQ expr.
expr ::= expr NE expr.
expr ::= expr IS NOT NULL.
expr ::= expr IS NULL.
expr ::= expr ISNULL
expr ::= expr NOTNULL.
expr ::= expr LT expr.
expr ::= expr GT expr.
expr ::= expr GE expr.
expr ::= expr LE expr.
expr ::= expr NOT NULL.
expr ::= expr OR expr.
expr ::= expr PLUS expr.
expr ::= expr MINUS expr.
expr ::= expr STAR expr.
expr ::= expr SLASH expr.
expr ::= expr REM expr.
expr ::= expr BETWEEN expr AND expr.
expr ::= expr NOT BETWEEN expr AND expr.
expr ::= expr IN LP exprlist RP.
expr ::= expr IN LP select RP.
expr ::= expr IN fullname.
expr ::= expr NOT IN LP exprlist RP.
expr ::= expr NOT IN LP select RP.
expr ::= expr NOT IN fullname.
expr ::= expr LIKE_KW expr escape.
expr ::= expr MATCH expr escape.
expr ::= expr NOT LIKE_KW expr escape.
expr ::= expr NOT MATCH expr escape.
expr ::= rtvalue.
expr ::= term.
term ::= CTIME_KW.
term ::= INTEGER.
term ::= FLOAT
term ::= BLOB.
term ::= NULL.
term ::= STRING.
exprlist ::= expr.
exprlist ::= exprlist COMMA expr.
case_else ::= ELSE expr.
case_else ::= .
case_exprlist ::= WHEN expr THEN expr.
case_exprlist ::= case_exprlist WHEN expr THEN expr.
case_operand ::= expr.
case_operand ::= .
function_name ::= ID.
escape ::= .
escape ::= ESCAPE expr.
</pre></blockquote>

HLR H47003 
The unary PLUS, unary MINUS, and BITNOT operators shall have
precedence over the COLLATE operator.

HLR H47006 
The COLLATE operator shall have precedence over the CONCAT
operator.

HLR H47009 
The CONCAT operator shall have precedence over the STAR, SLASH,
and REM operators.

HLR H47012 
The STAR, SLASH, and REM operator shall have equal precedence.

HLR H47015 
The STAR, SLASH, and REM operators shall have precedence over the
binary PLUS and binary MINUS operators.

HLR H47018 
The binary PLUS and binary MINUS operators shall have equal precedence.

HLR H47021 
The binary PLUS and binary MINUS operators shall have precedence
over the BITAND, BITOR, LSHIFT, and RSHIFT operators.

HLR H47024 
The BITAND, BITOR, LSHIFT, and RSHIFT operators shall have equal
precendence.

HLR H47027 
The BITAND, BITOR, LSHIFT, and RSHIFT operators shall have precedence
over the ESCAPE operator.

HLR H47029 
The ESCAPE operator shall have precedence over
the GT, LE, LT, and GE operators.

HLR H47033 
The GT, LE, LT, and GE operators shall have equal precedence.

HLR H47036 
The GT, LE, LT, and GE operators shall have precedence over
the IS, MATCH, LIKE_KW, BETWEEN, IN, ISNULL, NOTNULL, NE, and EQ
operators shall have equal precedence.

HLR H47039 
The IS, MATCH, LIKE_KW, BETWEEN, IN, ISNULL, NOTNULL, NE, and EQ
operators shall have equal precedence.

HLR H47042 
The IS, MATCH, LIKE_KW, BETWEEN, IN, ISNULL, NOTNULL, NE, and EQ
operators shall have precedence over the unary NOT operator.

HLR H47045 
The unary NOT operator shall have precedence over the AND operator.

HLR H47048 
The AND operator shall have precedence over the OR operator.

HLR H47051 
Operators of equal precedence shall group from right to left.

HLR H49100 
The SQLite parser shall accept names, fullnames, and identifiers
that conform to the following syntax:
<blockquote><pre>
name ::= ID.
name ::= JOIN_KW.
name ::= STRING.
fullname ::= objectname.
fullname ::= databasename DOT objectname.
objectname ::= name.
databasename ::= name.
columnname ::= name.
identifier ::= ID.
identifier ::= STRING.
</pre></blockquote>

HLR H49103 
The SQLite parser shall accept <i>rtvalue</i> elements of an
<i>expr</i> that conform to the following syntax:
<blockquote><pre>
rtvalue ::= databasename DOT tablename DOT columnname.
rtvalue ::= tablename DOT columnname.
rtvalue ::= ID.
rtvalue ::= JOIN_KW.
</pre></blockquote>

HLR H41010 
SQLite shall divide input SQL text into tokens working from left to
right.

HLR H41020 
At each step in the SQL tokenization process, SQLite shall extract
the longest possible token from the remaining input text.
................................................................................

HLR H41845 
SQLite shall recognize the 4-character sequenence "WHEN" in any combination of upper and lower case letters as the keyword token WHEN.

HLR H41848 
SQLite shall recognize the 5-character sequenence "WHERE" in any combination of upper and lower case letters as the keyword token WHERE.

HLR H41900





The preparation of an SQL statement that is not accepted by
the SQLite parser shall fail with an error.

HLR H41910
SQLite shall use the built-in NOCASE collating sequence when comparing
identifiers and datatype names within SQL statements during
statement preparation.

HLR H41920
A token received by the parser shall be converted into an ID token
if the original token value would have resulted in a syntax error,
a token value of ID will allow the parse to continue,
and if the original token value was one of:
ABORT
AFTER
ANALYZE
................................................................................
TEMP
TRIGGER
UNION
VACUUM
VIEW
VIRTUAL

HLR H41930
A token received by the parser shall be converted into an ANY token
if the original token value would have resulted in a syntax error
and if a token value of ANY will allow the parse to continue.

HLR H42000
In the absence of semantic or other errors, the SQLite parser shall
accept a "sql-stmt-list" that conforms to the following syntax:
<center>[syntax/sql-stmt-list.gif]</center>

HLR H42100
In the absence of semantic or other errors, the SQLite parser shall
accept a "sql-stmt" that conforms to the following syntax:
<center>[syntax/sql-stmt.gif]</center>

HLR H42200
In the absence of semantic or other errors, the SQLite parser shall
accept a "alter-table-stmt" that conforms to the following syntax:
<center>[syntax/alter-table-stmt.gif]</center>

HLR H42300
In the absence of semantic or other errors, the SQLite parser shall
accept a "analyze-stmt" that conforms to the following syntax:
<center>[syntax/analyze-stmt.gif]</center>

HLR H42400
In the absence of semantic or other errors, the SQLite parser shall
accept a "attach-stmt" that conforms to the following syntax:
<center>[syntax/attach-stmt.gif]</center>

HLR H42500
In the absence of semantic or other errors, the SQLite parser shall
accept a "begin-stmt" that conforms to the following syntax:
<center>[syntax/begin-stmt.gif]</center>

HLR H42600
In the absence of semantic or other errors, the SQLite parser shall
accept a "commit-stmt" that conforms to the following syntax:
<center>[syntax/commit-stmt.gif]</center>

HLR H42700
In the absence of semantic or other errors, the SQLite parser shall
accept a "rollback-stmt" that conforms to the following syntax:
<center>[syntax/rollback-stmt.gif]</center>

HLR H42800
In the absence of semantic or other errors, the SQLite parser shall
accept a "savepoint-stmt" that conforms to the following syntax:
<center>[syntax/savepoint-stmt.gif]</center>

HLR H42900
In the absence of semantic or other errors, the SQLite parser shall
accept a "release-stmt" that conforms to the following syntax:
<center>[syntax/release-stmt.gif]</center>

HLR H43000
In the absence of semantic or other errors, the SQLite parser shall
accept a "create-index-stmt" that conforms to the following syntax:
<center>[syntax/create-index-stmt.gif]</center>

HLR H43100
In the absence of semantic or other errors, the SQLite parser shall
accept a "indexed-column" that conforms to the following syntax:
<center>[syntax/indexed-column.gif]</center>

HLR H43200
In the absence of semantic or other errors, the SQLite parser shall
accept a "create-table-stmt" that conforms to the following syntax:
<center>[syntax/create-table-stmt.gif]</center>

HLR H43300
In the absence of semantic or other errors, the SQLite parser shall
accept a "column-def" that conforms to the following syntax:
<center>[syntax/column-def.gif]</center>

HLR H43400
In the absence of semantic or other errors, the SQLite parser shall
accept a "type-name" that conforms to the following syntax:
<center>[syntax/type-name.gif]</center>

HLR H43500
In the absence of semantic or other errors, the SQLite parser shall
accept a "column-constraint" that conforms to the following syntax:
<center>[syntax/column-constraint.gif]</center>

HLR H43600
In the absence of semantic or other errors, the SQLite parser shall
accept a "signed-number" that conforms to the following syntax:
<center>[syntax/signed-number.gif]</center>

HLR H43700
In the absence of semantic or other errors, the SQLite parser shall
accept a "table-constraint" that conforms to the following syntax:
<center>[syntax/table-constraint.gif]</center>

HLR H43800
In the absence of semantic or other errors, the SQLite parser shall
accept a "foreign-key-clause" that conforms to the following syntax:
<center>[syntax/foreign-key-clause.gif]</center>

HLR H43900
In the absence of semantic or other errors, the SQLite parser shall
accept a "conflict-clause" that conforms to the following syntax:
<center>[syntax/conflict-clause.gif]</center>

HLR H44000
In the absence of semantic or other errors, the SQLite parser shall
accept a "create-trigger-stmt" that conforms to the following syntax:
<center>[syntax/create-trigger-stmt.gif]</center>

HLR H44100
In the absence of semantic or other errors, the SQLite parser shall
accept a "create-view-stmt" that conforms to the following syntax:
<center>[syntax/create-view-stmt.gif]</center>

HLR H44200
In the absence of semantic or other errors, the SQLite parser shall
accept a "create-virtual-table-stmt" that conforms to the following syntax:
<center>[syntax/create-virtual-table-stmt.gif]</center>

HLR H44300
In the absence of semantic or other errors, the SQLite parser shall
accept a "delete-stmt" that conforms to the following syntax:
<center>[syntax/delete-stmt.gif]</center>

HLR H44400
In the absence of semantic or other errors, the SQLite parser shall
accept a "delete-stmt-limited" that conforms to the following syntax:
<center>[syntax/delete-stmt-limited.gif]</center>

HLR H44500
In the absence of semantic or other errors, the SQLite parser shall
accept a "detach-stmt" that conforms to the following syntax:
<center>[syntax/detach-stmt.gif]</center>

HLR H44600
In the absence of semantic or other errors, the SQLite parser shall
accept a "drop-index-stmt" that conforms to the following syntax:
<center>[syntax/drop-index-stmt.gif]</center>

HLR H44700
In the absence of semantic or other errors, the SQLite parser shall
accept a "drop-table-stmt" that conforms to the following syntax:
<center>[syntax/drop-table-stmt.gif]</center>

HLR H44800
In the absence of semantic or other errors, the SQLite parser shall
accept a "drop-trigger-stmt" that conforms to the following syntax:
<center>[syntax/drop-trigger-stmt.gif]</center>

HLR H44900
In the absence of semantic or other errors, the SQLite parser shall
accept a "drop-view-stmt" that conforms to the following syntax:
<center>[syntax/drop-view-stmt.gif]</center>

HLR H45000
In the absence of semantic or other errors, the SQLite parser shall
accept a "expr" that conforms to the following syntax:
<center>[syntax/expr.gif]</center>

HLR H45100
In the absence of semantic or other errors, the SQLite parser shall
accept a "raise-function" that conforms to the following syntax:
<center>[syntax/raise-function.gif]</center>

HLR H45200
In the absence of semantic or other errors, the SQLite parser shall
accept a "literal-value" that conforms to the following syntax:
<center>[syntax/literal-value.gif]</center>

HLR H45300
In the absence of semantic or other errors, the SQLite parser shall
accept a "insert-stmt" that conforms to the following syntax:
<center>[syntax/insert-stmt.gif]</center>

HLR H45400
In the absence of semantic or other errors, the SQLite parser shall
accept a "pragma-stmt" that conforms to the following syntax:
<center>[syntax/pragma-stmt.gif]</center>

HLR H45500
In the absence of semantic or other errors, the SQLite parser shall
accept a "pragma-value" that conforms to the following syntax:
<center>[syntax/pragma-value.gif]</center>

HLR H45600
In the absence of semantic or other errors, the SQLite parser shall
accept a "reindex-stmt" that conforms to the following syntax:
<center>[syntax/reindex-stmt.gif]</center>

HLR H45700
In the absence of semantic or other errors, the SQLite parser shall
accept a "select-stmt" that conforms to the following syntax:
<center>[syntax/select-stmt.gif]</center>

HLR H45800
In the absence of semantic or other errors, the SQLite parser shall
accept a "select-core" that conforms to the following syntax:
<center>[syntax/select-core.gif]</center>

HLR H45900
In the absence of semantic or other errors, the SQLite parser shall
accept a "result-column" that conforms to the following syntax:
<center>[syntax/result-column.gif]</center>

HLR H46000
In the absence of semantic or other errors, the SQLite parser shall
accept a "join-source" that conforms to the following syntax:
<center>[syntax/join-source.gif]</center>

HLR H46100
In the absence of semantic or other errors, the SQLite parser shall
accept a "single-source" that conforms to the following syntax:
<center>[syntax/single-source.gif]</center>

HLR H46200
In the absence of semantic or other errors, the SQLite parser shall
accept a "join-op" that conforms to the following syntax:
<center>[syntax/join-op.gif]</center>

HLR H46300
In the absence of semantic or other errors, the SQLite parser shall
accept a "join-constraint" that conforms to the following syntax:
<center>[syntax/join-constraint.gif]</center>

HLR H46400
In the absence of semantic or other errors, the SQLite parser shall
accept a "ordering-term" that conforms to the following syntax:
<center>[syntax/ordering-term.gif]</center>

HLR H46500
In the absence of semantic or other errors, the SQLite parser shall
accept a "compound-operator" that conforms to the following syntax:
<center>[syntax/compound-operator.gif]</center>

HLR H46600
In the absence of semantic or other errors, the SQLite parser shall
accept a "update-stmt" that conforms to the following syntax:
<center>[syntax/update-stmt.gif]</center>

HLR H46700
In the absence of semantic or other errors, the SQLite parser shall
accept a "update-stmt-limited" that conforms to the following syntax:
<center>[syntax/update-stmt-limited.gif]</center>

HLR H46800
In the absence of semantic or other errors, the SQLite parser shall
accept a "qualified-table-name" that conforms to the following syntax:
<center>[syntax/qualified-table-name.gif]</center>

HLR H46900
In the absence of semantic or other errors, the SQLite parser shall
accept a "vacuum-stmt" that conforms to the following syntax:
<center>[syntax/vacuum-stmt.gif]</center>