Small. Fast. Reliable.
Choose any three.

1. Overview


WITH RECURSIVE common-table-expression , DELETE FROM qualified-table-name returning-clause expr WHERE





The DELETE command removes records from the table identified by the qualified-table-name.

R-20205-17349:[If the WHERE clause is not present, all records in the table are deleted. ] R-26300-50198:[If a WHERE clause is supplied, then only those rows for which the WHERE clause boolean expression is true are deleted. ] R-23360-48280:[Rows for which the expression is false or NULL are retained. ]


2. ] Restrictions on DELETE Statements Within CREATE TRIGGER

The following restrictions apply to DELETE statements that occur within the body of a CREATE TRIGGER statement:

3. Optional LIMIT and ORDER BY clauses

R-40026-10531:[If SQLite is compiled with the SQLITE_ENABLE_UPDATE_DELETE_LIMIT compile-time option, then the syntax of the DELETE statement is extended by the addition of optional ORDER BY and LIMIT clauses: ]


WITH RECURSIVE common-table-expression , DELETE FROM qualified-table-name WHERE expr returning-clause ORDER BY ordering-term , LIMIT expr OFFSET expr , expr

R-44062-08550:[If a DELETE statement has a LIMIT clause, the maximum number of rows that will be deleted is found by evaluating the accompanying expression and casting it to an integer value. ] R-02661-56399:[If the result of the evaluating the LIMIT clause cannot be losslessly converted to an integer value, it is an error. ] R-00598-03741:[A negative LIMIT value is interpreted as "no limit". ] R-26377-49195:[If the DELETE statement also has an OFFSET clause, then it is similarly evaluated and cast to an integer value. Again, it is an error if the value cannot be losslessly converted to an integer. ] R-64004-53814:[If there is no OFFSET clause, or the calculated integer value is negative, the effective OFFSET value is zero. ]

R-48141-52334:[If the DELETE statement has an ORDER BY clause, then all rows that would be deleted in the absence of the LIMIT clause are sorted according to the ORDER BY. The first M rows, where M is the value found by evaluating the OFFSET clause expression, are skipped, and the following N, where N is the value of the LIMIT expression, are deleted. ] R-64535-08414:[If there are less than N rows remaining after taking the OFFSET clause into account, or if the LIMIT clause evaluated to a negative value, then all remaining rows are deleted. ]

R-37284-06965:[If the DELETE statement has no ORDER BY clause, then all rows that would be deleted in the absence of the LIMIT clause are assembled in an arbitrary order before applying the LIMIT and OFFSET clauses to determine the subset that are actually deleted. ]

R-07548-13422:[The ORDER BY clause on a DELETE statement is used only to determine which rows fall within the LIMIT. The order in which rows are deleted is arbitrary and is not influenced by the ORDER BY clause. ] R-16484-18454:[This means that if there is a RETURNING clause, the rows returned by the statement probably will not be in the order specified by the ORDER BY clause. ]

4. The Truncate Optimization

R-32811-57727:[When the WHERE clause and RETURNING clause are both omitted from a DELETE statement and the table being deleted has no triggers, SQLite uses an optimization to erase the entire table content without having to visit each row of the table individually. ] This "truncate" optimization makes the delete run much faster. Prior to SQLite version 3.6.5 (2008-11-12), the truncate optimization also meant that the sqlite3_changes() and sqlite3_total_changes() interfaces and the count_changes pragma will not actually return the number of deleted rows. That problem has been fixed as of version 3.6.5 (2008-11-12).

R-64895-14776:[The truncate optimization can be permanently disabled for all queries by recompiling SQLite with the SQLITE_OMIT_TRUNCATE_OPTIMIZATION compile-time switch. ]

The truncate optimization can also be disabled at runtime using the sqlite3_set_authorizer() interface. R-34561-00264:[If an authorizer callback returns SQLITE_IGNORE for an SQLITE_DELETE action code, then the DELETE operation will proceed but the truncate optimization will be bypassed and rows will be deleted one by one. ]

This page last modified on 2022-01-08 05:02:57 UTC