Unknown date Unknown author
CREATE INDEX
1. Syntax
create-index-stmt: hide
CREATE INDEX IF NOT EXISTS
UNIQUE
schema-name . index-name ON table-name ( indexed-column )
,
WHERE expr
expr: show
literal-value
bind-parameter
schema-name . table-name . column-name
unary-operator expr
expr binary-operator expr
function-name ( function-arguments )
, filter-clause over-clause
( expr )
CAST ( expr AS type-name )
expr COLLATE collation-name
expr NOT LIKE expr
GLOB ESCAPE expr
REGEXP expr
MATCH
expr ISNULL
NOTNULL
NOT NULL
expr IS NOT DISTINCT FROM expr
expr NOT BETWEEN expr AND expr
expr NOT IN ( select-stmt )
expr
, table-name
,
schema-name . table-function ( expr )
NOT EXISTS ( select-stmt )
CASE expr WHEN expr THEN expr ELSE expr END
raise-function
FILTER ( WHERE expr )
DISTINCT
,
expr
ORDER BY ordering-term
,
*
expr
COLLATE collation-name ASC NULLS FIRST
DESC NULLS LAST
numeric-literal
string-literal
blob-literal
NULL
TRUE
FALSE
CURRENT_TIME
CURRENT_DATE
CURRENT_TIMESTAMP
OVER window-name
(
base-window-name
PARTITION BY expr
ORDER BY ordering-term
frame-spec )
RANGE BETWEEN UNBOUNDED PRECEDING AND expr PRECEDING
ROWS expr PRECEDING CURRENT ROW
GROUPS CURRENT ROW expr FOLLOWING
expr FOLLOWING UNBOUNDED FOLLOWING
UNBOUNDED PRECEDING
expr PRECEDING
CURRENT ROW
EXCLUDE NO OTHERS
EXCLUDE CURRENT ROW
EXCLUDE GROUP
EXCLUDE TIES
expr
COLLATE collation-name ASC NULLS FIRST
DESC NULLS LAST
RAISE ( IGNORE )
ROLLBACK , expr
ABORT
FAIL
WITH common-table-expression
RECURSIVE ,
SELECT result-column
DISTINCT ,
ALL
select-core
FROM table-or-subquery
,
join-clause
WHERE expr
GROUP BY expr HAVING expr
WINDOW window-name AS window-defn
,
VALUES ( expr )
,
compound-operator
ORDER BY ordering-term
LIMIT expr
OFFSET expr
, expr
table-name ( column-name )
,
NOT MATERIALIZED
AS ( select-stmt )
UNION
UNION ALL
INTERSECT
EXCEPT
table-or-subquery
join-operator table-or-subquery join-constraint
ON expr
USING ( column-name )
,
,
JOIN
NATURAL LEFT OUTER
RIGHT
FULL
INNER
CROSS
expr
COLLATE collation-name ASC NULLS FIRST
DESC NULLS LAST
expr
AS column-alias
*
table-name . *
table-name AS table-alias
schema-name .
INDEXED BY index-name
NOT INDEXED
,
table-function-name ( expr )
AS table-alias
( select-stmt )
( table-or-subquery )
,
( join-clause
base-window-name
PARTITION BY expr
ORDER BY ordering-term
frame-spec )
RANGE BETWEEN UNBOUNDED PRECEDING AND expr PRECEDING
ROWS expr PRECEDING CURRENT ROW
GROUPS CURRENT ROW expr FOLLOWING
expr FOLLOWING UNBOUNDED FOLLOWING
UNBOUNDED PRECEDING
expr PRECEDING
CURRENT ROW
EXCLUDE NO OTHERS
EXCLUDE CURRENT ROW
EXCLUDE GROUP
EXCLUDE TIES
name
( signed-number )
( signed-number , signed-number )
numeric-literal
+
-
indexed-column: show
column-name
expr COLLATE collation-name ASC
DESC
The CREATE INDEX command consists of the keywords "CREATE
INDEX" followed by the name of the new index, the keyword "ON", the
name of a previously created table that is to be indexed, and a
parenthesized list of table column names and/or expressions that are
used for the index key. If the optional WHERE clause is included, then the
index is a "partial index".
If the optional IF NOT EXISTS clause is present and another index with
the same name already exists, then this command becomes a no-op.
There are no arbitrary limits on the number of indices that can be
attached to a single table. The number of columns in an index is limited
to the value set by sqlite3_limit(SQLITE_LIMIT_COLUMN,...).
Indexes are removed with the DROP INDEX command.
[Link] 1/3
9/20/25, 6:37 PM CREATE INDEX
1.1. Unique Indexes
If the UNIQUE keyword appears between CREATE and INDEX then
duplicate index entries are not allowed. Any attempt to insert a duplicate
entry will result in an error.
For the purposes of unique indices, all NULL values are considered
different from all other NULL values and are thus unique. This is one of
the two possible interpretations of the SQL-92 standard (the language in
the standard is ambiguous). The interpretation used by SQLite is the same
and is the interpretation followed by PostgreSQL, MySQL, Firebird, and
Oracle. Informix and Microsoft SQL Server follow the other interpretation
of the standard, which is that all NULL values are equal to one another.
1.2. Indexes on Expressions
Expressions in an index may not reference other tables and may not use
subqueries nor functions whose result might change (ex: random() or
sqlite_version()). Expressions in an index may only refer to columns in the
table that is being indexed. Indexes on expression will not work with
versions of SQLite prior to version 3.9.0 (2015-10-14). See the Indexes On
Expressions document for additional information about using general
expressions in CREATE INDEX statements.
1.3. Descending Indexes
Each column name or expression can be followed by one of the "ASC" or
"DESC" keywords to indicate sort order. The sort order may or may not be
ignored depending on the database file format, and in particular the
schema format number. The "legacy" schema format (1) ignores index
sort order. The descending index schema format (4) takes index sort
order into account. Only versions of SQLite 3.3.0 (2006-01-11) and later are
able to understand the descending index format. For compatibility,
version of SQLite between 3.3.0 and 3.7.9 use the legacy schema format by
default. The newer schema format is used by default in version 3.7.10
(2012-01-16) and later. The legacy_file_format pragma can be used to
change set the specific behavior for any version of SQLite.
[Link] 2/3
9/20/25, 6:37 PM CREATE INDEX
1.4. NULLS FIRST and NULLS LAST
The NULLS FIRST and NULLS LAST predicates are not supported for
indexes. For sorting purposes, SQLite considers NULL values to be
smaller than all other values. Hence NULL values always appear at the
beginning of an ASC index and at the end of a DESC index.
1.5. Collations
The COLLATE clause optionally following each column name or
expression defines a collating sequence used for text entries in that
column. The default collating sequence is the collating sequence defined
for that column in the CREATE TABLE statement. Or if no collating
sequence is otherwise defined, the built-in BINARY collating sequence is
used.
This page last modified on 2022-04-18 [Link] UTC
Viewed using Just Read
[Link] 3/3
