A nearby diagram shows the main components of SQLite and how they interoperate. The text below explains the roles of the various components.
# Overview
SQLite works by compiling SQL text into [bytecode](opcode.md), then running that bytecode using a virtual machine.
The [sqlite3_prepare_v2()](c3ref/prepare.md) and related interfaces act as a compiler for converting SQL text into bytecode. The [sqlite3_stmt](c3ref/stmt.md) object is a container for a single bytecode program that implements a single SQL statement. The [sqlite3_step()](c3ref/step.md) interface passes a bytecode program into the virtual machine, and runs the program until it either completes, or forms a row of result to be returned, or hits a fatal error, or is [interrupted](c3ref/interrupt.md).
# Interface
Much of the [C-language Interface](c3ref/intro.md) is found in source files [main.c](https://sqlite.org/src/file/src/main.c), [legacy.c](https://sqlite.org/src/file/src/legacy.c), and [vdbeapi.c](https://sqlite.org/src/file/src/vdbeapi.c) though some routines are scattered about in other files where they can have access to data structures with file scope. The [sqlite3_get_table()](c3ref/free_table.md) routine is implemented in [table.c](https://sqlite.org/src/file/src/table.c). The [sqlite3_mprintf()](c3ref/mprintf.md) routine is found in [printf.c](https://sqlite.org/src/file/src/printf.c). The [sqlite3_complete()](c3ref/complete.md) interface is in [complete.c](https://sqlite.org/src/file/src/complete.c). The [TCL Interface](tclsqlite.md) is implemented by [tclsqlite.c](https://sqlite.org/src/file/src/tclsqlite.c).
To avoid name collisions, all external symbols in the SQLite library begin with the prefix **sqlite3**. Those symbols that are intended for external use (in other words, those symbols which form the API for SQLite) add an underscore, and thus begin with **sqlite3\_**. Extension APIs sometimes add the extension name prior to the underscore; for example: **sqlite3rbu\_** or **sqlite3session\_**.
# Tokenizer
When a string containing SQL statements is to be evaluated it is first sent to the tokenizer. The tokenizer breaks the SQL text into tokens and hands those tokens one by one to the parser. The tokenizer is hand-coded in the file tokenize.c.
Note that in this design, the tokenizer calls the parser. People who are familiar with YACC and BISON may be accustomed to doing things the other way around — having the parser call the tokenizer. Having the tokenizer call the parser is better, though, because it can be made threadsafe and it runs faster.
# Parser
The parser assigns meaning to tokens based on their context. The parser for SQLite is generated using the [Lemon parser generator](lemon.md). Lemon does the same job as YACC/BISON, but it uses a different input syntax which is less error-prone. Lemon also generates a parser which is reentrant and thread-safe. And Lemon defines the concept of a non-terminal destructor so that it does not leak memory when syntax errors are encountered. The grammar file that drives Lemon and that defines the SQL language that SQLite understands is found in [parse.y](https://sqlite.org/src/file/src/parse.y).
Because Lemon is a program not normally found on development machines, the complete source code to Lemon (just one C file) is included in the SQLite distribution in the "tool" subdirectory.
# Code Generator
After the parser assembles tokens into a parse tree, the code generator runs to analyze the parse tree and generate [bytecode](opcode.md) that performs the work of the SQL statement. The [prepared statement](c3ref/stmt.md) object is a container for this bytecode. There are many files in the code generator, including: [attach.c](https://sqlite.org/src/file/src/attach.c), [auth.c](https://sqlite.org/src/file/src/auth.c), [build.c](https://sqlite.org/src/file/src/build.c), [delete.c](https://sqlite.org/src/file/src/delete.c), [expr.c](https://sqlite.org/src/file/src/expr.c), [insert.c](https://sqlite.org/src/file/src/insert.c), [pragma.c](https://sqlite.org/src/file/src/pragma.c), [select.c](https://sqlite.org/src/file/src/select.c), [trigger.c](https://sqlite.org/src/file/src/trigger.c), [update.c](https://sqlite.org/src/file/src/update.c), [vacuum.c](https://sqlite.org/src/file/src/vacuum.c), [where.c](https://sqlite.org/src/file/src/where.c), [wherecode.c](https://sqlite.org/src/file/src/wherecode.c), and [whereexpr.c](https://sqlite.org/src/file/src/whereexpr.c). In these files is where most of the serious magic happens. [expr.c](https://sqlite.org/src/file/src/expr.c) handles code generation for expressions. **where\*.c** handles code generation for WHERE clauses on SELECT, UPDATE and DELETE statements. The files [attach.c](https://sqlite.org/src/file/src/attach.c), [delete.c](https://sqlite.org/src/file/src/delete.c), [insert.c](https://sqlite.org/src/file/src/insert.c), [select.c](https://sqlite.org/src/file/src/select.c), [trigger.c](https://sqlite.org/src/file/src/trigger.c) [update.c](https://sqlite.org/src/file/src/update.c), and [vacuum.c](https://sqlite.org/src/file/src/vacuum.c) handle the code generation for SQL statements with the same names. (Each of these files calls routines in [expr.c](https://sqlite.org/src/file/src/expr.c) and [where.c](https://sqlite.org/src/file/src/where.c) as necessary.) All other SQL statements are coded out of [build.c](https://sqlite.org/src/file/src/build.c). The [auth.c](https://sqlite.org/src/file/src/auth.c) file implements the functionality of [sqlite3_set_authorizer()](c3ref/set_authorizer.md).
The code generator, and especially the logic in **where\*.c** and in [select.c](https://sqlite.org/src/file/src/select.c), is sometimes called the [query planner](optoverview.md). For any particular SQL statement, there might be hundreds, thousands, or millions of different algorithms to compute the answer. The query planner is an AI that strives to select the best algorithm from these millions of choices.
# Bytecode Engine
The [bytecode](opcode.md) program created by the code generator is run by a virtual machine.
The virtual machine itself is entirely contained in a single source file [vdbe.c](https://sqlite.org/src/file/src/vdbe.c). The [vdbe.h](https://sqlite.org/src/file/src/vdbe.h) header file defines an interface between the virtual machine and the rest of the SQLite library and [vdbeInt.h](https://sqlite.org/src/file/src/vdbeInt.h) which defines structures and interfaces that are private to the virtual machine itself. Various other **vdbe\*.c** files are helpers to the virtual machine. The [vdbeaux.c](https://sqlite.org/src/file/src/vdbeaux.c) file contains utilities used by the virtual machine and interface modules used by the rest of the library to construct VM programs. The [vdbeapi.c](https://sqlite.org/src/file/src/vdbeapi.c) file contains external interfaces to the virtual machine such as the [sqlite3_bind_int()](c3ref/bind_blob.md) and [sqlite3_step()](c3ref/step.md). Individual values (strings, integer, floating point numbers, and BLOBs) are stored in an internal object named "Mem" which is implemented by [vdbemem.c](https://sqlite.org/src/file/src/vdbemem.c).
SQLite implements SQL functions using callbacks to C-language routines. Even the built-in SQL functions are implemented this way. Most of the built-in SQL functions (ex: [abs()](lang_corefunc.md#abs), [count()](lang_aggfunc.md#count), [substr()](lang_corefunc.md#substr), and so forth) can be found in the [func.c](https://sqlite.org/src/file/src/func.c) source file. Date and time conversion functions are found in [date.c](https://sqlite.org/src/file/src/date.c). Some functions such as [coalesce()](lang_corefunc.md#coalesce) and [typeof()](lang_corefunc.md#typeof) are implemented as bytecode directly by the code generator.
# B-Tree
An SQLite database is maintained on disk using a B-tree implementation found in the [btree.c](https://sqlite.org/src/file/src/btree.c) source file. Separate B-trees are used for each table and each index in the database. All B-trees are stored in the same disk file. The [file format](fileformat2.md) details are stable and well-defined and are guaranteed to be compatible moving forward.
The interface to the B-tree subsystem and the rest of the SQLite library is defined by the header file [btree.h](https://sqlite.org/src/file/src/btree.h).
# Page Cache
The B-tree module requests information from the disk in fixed-size pages. The default [page_size](pragma.md#pragma_page_size) is 4096 bytes but can be any power of two between 512 and 65536 bytes. The page cache is responsible for reading, writing, and caching these pages. The page cache also provides the rollback and atomic commit abstraction and takes care of locking of the database file. The B-tree driver requests particular pages from the page cache and notifies the page cache when it wants to modify pages or commit or rollback changes. The page cache handles all the messy details of making sure the requests are handled quickly, safely, and efficiently.
The primary page cache implementation is in the [pager.c](https://sqlite.org/src/file/src/pager.c) file. [WAL mode](wal.md) logic is in the separate [wal.c](https://sqlite.org/src/file/src/wal.c) file. In-memory caching is implemented by the [pcache.c](https://sqlite.org/src/file/src/pcache.c) and [pcache1.c](https://sqlite.org/src/file/src/pcache1.c) files. The interface between the page cache subsystem and the rest of SQLite is defined by the header file [pager.h](https://sqlite.org/src/file/src/pager.h).
# OS Interface
In order to provide portability across operating systems, SQLite uses an abstract object called the [VFS](vfs.md). Each VFS provides methods for opening, reading, writing, and closing files on disk, and for other OS-specific tasks such as finding the current time, or obtaining randomness to initialize the built-in pseudo-random number generator. SQLite currently provides VFSes for unix (in the [os_unix.c](https://sqlite.org/src/file/src/os_unix.c) file) and Windows (in the [os_win.c](https://sqlite.org/src/file/src/os_win.c) file).
# Utilities
Memory allocation, caseless string comparison routines, portable text-to-number conversion routines, and other utilities are located in [util.c](https://sqlite.org/src/file/src/util.c). Symbol tables used by the parser are maintained by hash tables found in [hash.c](https://sqlite.org/src/file/src/hash.c). The [utf.c](https://sqlite.org/src/file/src/utf.c) source file contains Unicode conversion subroutines. SQLite has its own private implementation of [printf()](printf.md) (with some extensions) in [printf.c](https://sqlite.org/src/file/src/printf.c) and its own pseudo-random number generator (PRNG) in [random.c](https://sqlite.org/src/file/src/random.c).
# Test Code
Files in the "src/" folder of the source tree whose names begin with **test** are for testing only and are not included in a standard build of the library.
---
# Atomic Commit In SQLite
*Sección: Guides | Origen: https://www.sqlite.org/atomiccommit.html*
# 1. Introduction
An important feature of transactional databases like SQLite is "atomic commit". Atomic commit means that either all database changes within a single transaction occur or none of them occur. With atomic commit, it is as if many different writes to different sections of the database file occur instantaneously and simultaneously. Real hardware serializes writes to mass storage, and writing a single sector takes a finite amount of time. So it is impossible to truly write many different sectors of a database file simultaneously and/or instantaneously. But the atomic commit logic within SQLite makes it appear as if the changes for a transaction are all written instantaneously and simultaneously.
SQLite has the important property that transactions appear to be atomic even if the transaction is interrupted by an operating system crash or power failure.
This article describes the techniques used by SQLite to create the illusion of atomic commit.
The information in this article applies only when SQLite is operating in "rollback mode", or in other words when SQLite is not using a [write-ahead log](wal.md). SQLite still supports atomic commit when write-ahead logging is enabled, but it accomplishes atomic commit by a different mechanism from the one described in this article. See the [write-ahead log documentation](wal.md) for additional information on how SQLite supports atomic commit in that context.
# 2. Hardware Assumptions
Throughout this article, we will call the mass storage device "disk" even though the mass storage device might really be flash memory.
We assume that disk is written in chunks which we call a "sector". It is not possible to modify any part of the disk smaller than a sector. To change a part of the disk smaller than a sector, you have to read in the full sector that contains the part you want to change, make the change, then write back out the complete sector.
On a traditional spinning disk, a sector is the minimum unit of transfer in both directions, both reading and writing. On flash memory, however, the minimum size of a read is typically much smaller than a minimum write. SQLite is only concerned with the minimum write amount and so for the purposes of this article, when we say "sector" we mean the minimum amount of data that can be written to mass storage in a single go.
Prior to SQLite version 3.3.14, a sector size of 512 bytes was assumed in all cases. There was a compile-time option to change this but the code had never been tested with a larger value. The 512 byte sector assumption seemed reasonable since until very recently all disk drives used a 512 byte sector internally. However, there has recently been a push to increase the sector size of disks to 4096 bytes. Also the sector size for flash memory is usually larger than 512 bytes. For these reasons, versions of SQLite beginning with 3.3.14 have a method in the OS interface layer that interrogates the underlying filesystem to find the true sector size. As currently implemented (version 3.5.0) this method still returns a hard-coded value of 512 bytes, since there is no standard way of discovering the true sector size on either Unix or Windows. But the method is available for embedded device manufacturers to tweak according to their own needs. And we have left open the possibility of filling in a more meaningful implementation on Unix and Windows in the future.
SQLite has traditionally assumed that a sector write is not atomic. However, SQLite does always assume that a sector write is linear. By "linear" we mean that SQLite assumes that when writing a sector, the hardware begins at one end of the data and writes byte by byte until it gets to the other end. The write might go from beginning to end or from end to beginning. If a power failure occurs in the middle of a sector write it might be that part of the sector was modified and another part was left unchanged. The key assumption by SQLite is that if any part of the sector gets changed, then either the first or the last bytes will be changed. So the hardware will never start writing a sector in the middle and work towards the ends. We do not know if this assumption is always true but it seems reasonable.
The previous paragraph states that SQLite does not assume that sector writes are atomic. This is true by default. But as of SQLite version 3.5.0, there is a new interface called the Virtual File System ([VFS](vfs.md)) interface. The [VFS](vfs.md) is the only means by which SQLite communicates to the underlying filesystem. The code comes with default VFS implementations for Unix and Windows and there is a mechanism for creating new custom VFS implementations at runtime. In this new VFS interface there is a method called xDeviceCharacteristics. This method interrogates the underlying filesystem to discover various properties and behaviors that the filesystem may or may not exhibit. The xDeviceCharacteristics method might indicate that sector writes are atomic, and if it does so indicate, SQLite will try to take advantage of that fact. But the default xDeviceCharacteristics method for both Unix and Windows does not indicate atomic sector writes and so these optimizations are normally omitted.
SQLite assumes that the operating system will buffer writes and that a write request will return before data has actually been stored in the mass storage device. SQLite further assumes that write operations will be reordered by the operating system. For this reason, SQLite does a "flush" or "fsync" operation at key points. SQLite assumes that the flush or fsync will not return until all pending write operations for the file that is being flushed have completed. We are told that the flush and fsync primitives are broken on some versions of Windows and Linux. This is unfortunate. It opens SQLite up to the possibility of database corruption following a power loss in the middle of a commit. However, there is nothing that SQLite can do to test for or remedy the situation. SQLite assumes that the operating system that it is running on works as advertised. If that is not quite the case, well then hopefully you will not lose power too often.
SQLite assumes that when a file grows in length that the new file space originally contains garbage and then later is filled in with the data actually written. In other words, SQLite assumes that the file size is updated before the file content. This is a pessimistic assumption and SQLite has to do some extra work to make sure that it does not cause database corruption if power is lost between the time when the file size is increased and when the new content is written. The xDeviceCharacteristics method of the [VFS](vfs.md) might indicate that the filesystem will always write the data before updating the file size. (This is the SQLITE_IOCAP_SAFE_APPEND property for those readers who are looking at the code.) When the xDeviceCharacteristics method indicates that files content is written before the file size is increased, SQLite can forego some of its pedantic database protection steps and thereby decrease the amount of disk I/O needed to perform a commit. The current implementation, however, makes no such assumptions for the default VFSes for Windows and Unix.
SQLite assumes that a file deletion is atomic from the point of view of a user process. By this we mean that if SQLite requests that a file be deleted and the power is lost during the delete operation, once power is restored either the file will exist completely with all if its original content unaltered, or else the file will not be seen in the filesystem at all. If after power is restored the file is only partially deleted, if some of its data has been altered or erased, or the file has been truncated but not completely removed, then database corruption will likely result.
SQLite assumes that the detection and/or correction of bit errors caused by cosmic rays, thermal noise, quantum fluctuations, device driver bugs, or other mechanisms, is the responsibility of the underlying hardware and operating system. SQLite does not add any redundancy to the database file for the purpose of detecting corruption or I/O errors. SQLite assumes that the data it reads is exactly the same data that it previously wrote.
By default, SQLite assumes that an operating system call to write a range of bytes will not damage or alter any bytes outside of that range even if a power loss or OS crash occurs during that write. We call this the "[powersafe overwrite](psow.md)" property. Prior to [version 3.7.9](releaselog/3_7_9.md) (2011-11-01), SQLite did not assume powersafe overwrite. But with the standard sector size increasing from 512 to 4096 bytes on most disk drives, it has become necessary to assume powersafe overwrite in order to maintain historical performance levels and so powersafe overwrite is assumed by default in recent versions of SQLite. The assumption of powersafe overwrite property can be disabled at compile-time or at run-time if desired. See the [powersafe overwrite documentation](psow.md) for further details.
# 3. Single File Commit
We begin with an overview of the steps SQLite takes in order to perform an atomic commit of a transaction against a single database file. The details of file formats used to guard against damage from power failures and techniques for performing an atomic commit across multiple databases are discussed in later sections.
## 3.1. Initial State
The state of the computer when a database connection is first opened is shown conceptually by the diagram at the right. The area of the diagram on the extreme right (labeled "Disk") represents information stored on the mass storage device. Each rectangle is a sector. The blue color represents that the sectors contain original data. The middle area is the operating systems disk cache. At the onset of our example, the cache is cold and this is represented by leaving the rectangles of the disk cache empty. The left area of the diagram shows the content of memory for the process that is using SQLite. The database connection has just been opened and no information has been read yet, so the user space is empty.
\
## 3.2. Acquiring A Read Lock
Before SQLite can write to a database, it must first read the database to see what is there already. Even if it is just appending new data, SQLite still has to read in the database schema from the "[sqlite_schema](schematab.md)" table so that it can know how to parse the INSERT statements and discover where in the database file the new information should be stored.
The first step toward reading from the database file is obtaining a shared lock on the database file. A "shared" lock allows two or more database connections to read from the database file at the same time. But a shared lock prevents another database connection from writing to the database file while we are reading it. This is necessary because if another database connection were writing to the database file at the same time we are reading from the database file, we might read some data before the change and other data after the change. This would make it appear as if the change made by the other process is not atomic.
Notice that the shared lock is on the operating system disk cache, not on the disk itself. File locks really are just flags within the operating system kernel, usually. (The details depend on the specific OS layer interface.) Hence, the lock will instantly vanish if the operating system crashes or if there is a power loss. It is usually also the case that the lock will vanish if the process that created the lock exits.
\
## 3.3. Reading Information Out Of The Database
After the shared lock is acquired, we can begin reading information from the database file. In this scenario, we are assuming a cold cache, so information must first be read from mass storage into the operating system cache then transferred from operating system cache into user space. On subsequent reads, some or all of the information might already be found in the operating system cache and so only the transfer to user space would be required.
Usually only a subset of the pages in the database file are read. In this example we are showing three pages out of eight being read. In a typical application, a database will have thousands of pages and a query will normally only touch a small percentage of those pages.
\
## 3.4. Obtaining A Reserved Lock
Before making changes to the database, SQLite first obtains a "reserved" lock on the database file. A reserved lock is similar to a shared lock in that both a reserved lock and shared lock allow other processes to read from the database file. A single reserve lock can coexist with multiple shared locks from other processes. However, there can only be a single reserved lock on the database file. Hence only a single process can be attempting to write to the database at one time.
The idea behind a reserved lock is that it signals that a process intends to modify the database file in the near future but has not yet started to make the modifications. And because the modifications have not yet started, other processes can continue to read from the database. However, no other process should also begin trying to write to the database.
\
## 3.5. Creating A Rollback Journal File
Prior to making any changes to the database file, SQLite first creates a separate rollback journal file and writes into the rollback journal the original content of the database pages that are to be altered. The idea behind the rollback journal is that it contains all information needed to restore the database back to its original state.
The rollback journal contains a small header (shown in green in the diagram) that records the original size of the database file. So if a change causes the database file to grow, we will still know the original size of the database. The page number is stored together with each database page that is written into the rollback journal.
When a new file is created, most desktop operating systems (Windows, Linux, Mac OS X) will not actually write anything to disk. The new file is created in the operating systems disk cache only. The file is not created on mass storage until sometime later, when the operating system has a spare moment. This creates the impression to users that I/O is happening much faster than is possible when doing real disk I/O. We illustrate this idea in the diagram to the right by showing that the new rollback journal appears in the operating system disk cache only and not on the disk itself.
\
## 3.6. Changing Database Pages In User Space
After the original page content has been saved in the rollback journal, the pages can be modified in user memory. Each database connection has its own private copy of user space, so the changes that are made in user space are only visible to the database connection that is making the changes. Other database connections still see the information in operating system disk cache buffers which have not yet been changed. And so even though one process is busy modifying the database, other processes can continue to read their own copies of the original database content.
\
## 3.7. Flushing The Rollback Journal File To Mass Storage
The next step is to flush the content of the rollback journal file to nonvolatile storage. As we will see later, this is a critical step in insuring that the database can survive an unexpected power loss. This step also takes a lot of time, since writing to nonvolatile storage is normally a slow operation.
This step is usually more complicated than simply flushing the rollback journal to the disk. On most platforms two separate flush (or fsync()) operations are required. The first flush writes out the base rollback journal content. Then the header of the rollback journal is modified to show the number of pages in the rollback journal. Then the header is flushed to disk. The details on why we do this header modification and extra flush are provided in a later section of this paper.
\
## 3.8. Obtaining An Exclusive Lock
Prior to making changes to the database file itself, we must obtain an exclusive lock on the database file. Obtaining an exclusive lock is really a two-step process. First SQLite obtains a "pending" lock. Then it escalates the pending lock to an exclusive lock.
A pending lock allows other processes that already have a shared lock to continue reading the database file. But it prevents new shared locks from being established. The idea behind a pending lock is to prevent writer starvation caused by a large pool of readers. There might be dozens, even hundreds, of other processes trying to read the database file. Each process acquires a shared lock before it starts reading, reads what it needs, then releases the shared lock. If, however, there are many different processes all reading from the same database, it might happen that a new process always acquires its shared lock before the previous process releases its shared lock. And so there is never an instant when there are no shared locks on the database file and hence there is never an opportunity for the writer to seize the exclusive lock. A pending lock is designed to prevent that cycle by allowing existing shared locks to proceed but blocking new shared locks from being established. Eventually all shared locks will clear and the pending lock will then be able to escalate into an exclusive lock.
\
## 3.9. Writing Changes To The Database File
Once an exclusive lock is held, we know that no other processes are reading from the database file and it is safe to write changes into the database file. Usually those changes only go as far as the operating systems disk cache and do not make it all the way to mass storage.
\
## 3.10. Flushing Changes To Mass Storage
Another flush must occur to make sure that all the database changes are written into nonvolatile storage. This is a critical step to ensure that the database will survive a power loss without damage. However, because of the inherent slowness of writing to disk or flash memory, this step together with the rollback journal file flush in section 3.7 above takes up most of the time required to complete a transaction commit in SQLite.
\
## 3.11. Deleting The Rollback Journal
After the database changes are all safely on the mass storage device, the rollback journal file is deleted. This is the instant where the transaction commits. If a power failure or system crash occurs prior to this point, then recovery processes to be described later make it appear as if no changes were ever made to the database file. If a power failure or system crash occurs after the rollback journal is deleted, then it appears as if all changes have been written to disk. Thus, SQLite gives the appearance of having made no changes to the database file or having made the complete set of changes to the database file depending on whether or not the rollback journal file exists.
Deleting a file is not really an atomic operation, but it appears to be from the point of view of a user process. A process is always able to ask the operating system "does this file exist?" and the process will get back a yes or no answer. After a power failure that occurs during a transaction commit, SQLite will ask the operating system whether or not the rollback journal file exists. If the answer is "yes" then the transaction is incomplete and is rolled back. If the answer is "no" then it means the transaction did commit.
The existence of a transaction depends on whether or not the rollback journal file exists and the deletion of a file appears to be an atomic operation from the point of view of a user-space process. Therefore, a transaction appears to be an atomic operation.
The act of deleting a file is expensive on many systems. As an optimization, SQLite can be configured to truncate the journal file to zero bytes in length or overwrite the journal file header with zeros. In either case, the resulting journal file is no longer capable of rolling back and so the transaction still commits. Truncating a file to zero length, like deleting a file, is assumed to be an atomic operation from the point of view of a user process. Overwriting the header of the journal with zeros is not atomic, but if any part of the header is malformed the journal will not roll back. Hence, one can say that the commit occurs as soon as the header is sufficiently changed to make it invalid. Typically this happens as soon as the first byte of the header is zeroed.
\
## 3.12. Releasing The Lock
The last step in the commit process is to release the exclusive lock so that other processes can once again start accessing the database file.
In the diagram at the right, we show that the information that was held in user space is cleared when the lock is released. This used to be literally true for older versions of SQLite. But more recent versions of SQLite keep the user space information in memory in case it might be needed again at the start of the next transaction. It is cheaper to reuse information that is already in local memory than to transfer the information back from the operating system disk cache or to read it off of the disk drive again. Prior to reusing the information in user space, we must first reacquire the shared lock and then we have to check to make sure that no other process modified the database file while we were not holding a lock. There is a counter in the first page of the database that is incremented every time the database file is modified. We can find out if another process has modified the database by checking that counter. If the database was modified, then the user space cache must be cleared and reread. But it is commonly the case that no changes have been made and the user space cache can be reused for a significant performance savings.
\
# 4. Rollback
An atomic commit is supposed to happen instantaneously. But the processing described above clearly takes a finite amount of time. Suppose the power to the computer were cut part way through the commit operation described above. In order to maintain the illusion that the changes were instantaneous, we have to "rollback" any partial changes and restore the database to the state it was in prior to the beginning of the transaction.
## 4.1. When Something Goes Wrong...
Suppose the power loss occurred during [step 3.10](#section_3_10) above, while the database changes were being written to disk. After power is restored, the situation might be something like what is shown to the right. We were trying to change three pages of the database file but only one page was successfully written. Another page was partially written and a third page was not written at all.
The rollback journal is complete and intact on disk when the power is restored. This is a key point. The reason for the flush operation in [step 3.7](#section_3_7) is to make absolutely sure that all of the rollback journal is safely on nonvolatile storage prior to making any changes to the database file itself.
\
## 4.2. Hot Rollback Journals
The first time that any SQLite process attempts to access the database file, it obtains a shared lock as described in [section 3.2](#section_3_2) above. But then it notices that there is a rollback journal file present. SQLite then checks to see if the rollback journal is a "hot journal". A hot journal is a rollback journal that needs to be played back in order to restore the database to a sane state. A hot journal only exists when an earlier process was in the middle of committing a transaction when it crashed or lost power.
A rollback journal is a "hot" journal if all of the following are true:
- The rollback journal exists.
- The rollback journal is not an empty file.
- There is no reserved lock on the main database file.
- The header of the rollback journal is well-formed and in particular has not been zeroed out.
- The rollback journal does not contain the name of a super-journal file (see [section 5.5](#section_5_5) below) or if does contain the name of a super-journal, then that super-journal file exists.
The presence of a hot journal is our indication that a previous process was trying to commit a transaction but it aborted for some reason prior to the completion of the commit. A hot journal means that the database file is in an inconsistent state and needs to be repaired (by rollback) prior to being used.
\
## 4.3. Obtaining An Exclusive Lock On The Database
The first step toward dealing with a hot journal is to obtain an exclusive lock on the database file. This prevents two or more processes from trying to rollback the same hot journal at the same time.
\
## 4.4. Rolling Back Incomplete Changes
Once a process obtains an exclusive lock, it is permitted to write to the database file. It then proceeds to read the original content of pages out of the rollback journal and write that content back to where it came from in the database file. Recall that the header of the rollback journal records the original size of the database file prior to the start of the aborted transaction. SQLite uses this information to truncate the database file back to its original size in cases where the incomplete transaction caused the database to grow. At the end of this step, the database should be the same size and contain the same information as it did before the start of the aborted transaction.
\
## 4.5. Deleting The Hot Journal
After all information in the rollback journal has been played back into the database file (and flushed to disk in case we encounter yet another power failure), the hot rollback journal can be deleted.
As in [section 3.11](#section_3_11), the journal file might be truncated to zero length or its header might be overwritten with zeros as an optimization on systems where deleting a file is expensive. Either way, the journal is no longer hot after this step.
\
## 4.6. Continue As If The Uncompleted Writes Had Never Happened
The final recovery step is to reduce the exclusive lock back to a shared lock. Once this happens, the database is back in the state that it would have been if the aborted transaction had never started. Since all of this recovery activity happens completely automatically and transparently, it appears to the program using SQLite as if the aborted transaction had never begun.
\
# 5. Multi-file Commit
SQLite allows a single [database connection](c3ref/sqlite3.md) to talk to two or more database files simultaneously through the use of the [ATTACH DATABASE](lang_attach.md) command. When multiple database files are modified within a single transaction, all files are updated atomically. In other words, either all of the database files are updated or else none of them are. Achieving an atomic commit across multiple database files is more complex that doing so for a single file. This section describes how SQLite works that bit of magic.
## 5.1. Separate Rollback Journals For Each Database
When multiple database files are involved in a transaction, each database has its own rollback journal and each database is locked separately. The diagram at the right shows a scenario where three different database files have been modified within one transaction. The situation at this step is analogous to the single-file transaction scenario at [step 3.6](#section_3_6). Each database file has a reserved lock. For each database, the original content of pages that are being changed have been written into the rollback journal for that database, but the content of the journals have not yet been flushed to disk. No changes have been made to the database file itself yet, though presumably there are changes being held in user memory.
For brevity, the diagrams in this section are simplified from those that came before. Blue color still signifies original content and pink still signifies new content. But the individual pages in the rollback journal and the database file are not shown and we are not making the distinction between information in the operating system cache and information that is on disk. All of these factors still apply in a multi-file commit scenario. They just take up a lot of space in the diagrams and they do not add any new information, so they are omitted here.
\
## 5.2. The Super-Journal File
The next step in a multi-file commit is the creation of a "super-journal" file. The name of the super-journal file is the same name as the original database filename (the database that was opened using the [sqlite3_open()](c3ref/open.md) interface, not one of the [ATTACHed](lang_attach.md) auxiliary databases) with the text "**-mj***HHHHHHHH*" appended where *HHHHHHHH* is a random 32-bit hexadecimal number. The random *HHHHHHHH* suffix changes for every new super-journal.
*(Nota bene: The formula for computing the super-journal filename given in the previous paragraph corresponds to the implementation as of SQLite version 3.5.0. But this formula is not part of the SQLite specification and is subject to change in future releases.)*
Unlike the rollback journals, the super-journal does not contain any original database page content. Instead, the super-journal contains the full pathnames for rollback journals for every database that is participating in the transaction.
After the super-journal is constructed, its content is flushed to disk before any further actions are taken. On Unix, the directory that contains the super-journal is also synced in order to make sure the super-journal file will appear in the directory following a power failure.
The purpose of the super-journal is to ensure that multi-file transactions are atomic across a power-loss. But if the database files have other settings that compromise integrity across a power-loss event (such as [PRAGMA synchronous=OFF](pragma.md#pragma_synchronous) or [PRAGMA journal_mode=MEMORY](pragma.md#pragma_journal_mode)) then the creation of the super-journal is omitted, as an optimization.\
## 5.3. Updating Rollback Journal Headers
The next step is to record the full pathname of the super-journal file in the header of every rollback journal. Space to hold the super-journal filename was reserved at the beginning of each rollback journal as the rollback journals were created.
The content of each rollback journal is flushed to disk both before and after the super-journal filename is written into the rollback journal header. It is important to do both of these flushes. Fortunately, the second flush is usually inexpensive since typically only a single page of the journal file (the first page) has changed.
This step is analogous to [step 3.7](#section_3_7) in the single-file commit scenario described above.
\
## 5.4. Updating The Database Files
Once all rollback journal files have been flushed to disk, it is safe to begin updating database files. We have to obtain an exclusive lock on all database files before writing the changes. After all the changes are written, it is important to flush the changes to disk so that they will be preserved in the event of a power failure or operating system crash.
This step corresponds to steps [3.8](#section_3_8), [3.9](#section_3_9), and [3.10](#section_3_10) in the single-file commit scenario described previously.
\
## 5.5. Delete The Super-Journal File
The next step is to delete the super-journal file. This is the point where the multi-file transaction commits. This step corresponds to [step 3.11](#section_3_11) in the single-file commit scenario where the rollback journal is deleted.
If a power failure or operating system crash occurs at this point, the transaction will not rollback when the system reboots even though there are rollback journals present. The difference is the super-journal pathname in the header of the rollback journal. Upon restart, SQLite only considers a journal to be hot and will only playback the journal if there is no super-journal filename in the header (which is the case for a single-file commit) or if the super-journal file still exists on disk.
\
## 5.6. Clean Up The Rollback Journals
The final step in a multi-file commit is to delete the individual rollback journals and drop the exclusive locks on the database files so that other processes can see the changes. This corresponds to [step 3.12](#section_3_12) in the single-file commit sequence.
The transaction has already committed at this point so timing is not critical in the deletion of the rollback journals. The current implementation deletes a single rollback journal then unlocks the corresponding database file before proceeding to the next rollback journal. But in the future we might change this so that all rollback journals are deleted before any database files are unlocked. As long as the rollback journal is deleted before its corresponding database file is unlocked it does not matter in what order the rollback journals are deleted or the database files are unlocked.
# 6. Additional Details Of The Commit Process
[Section 3.0](#section_3_0) above provides an overview of how atomic commit works in SQLite. But it glosses over a number of important details. The following subsections will attempt to fill in the gaps.
## 6.1. Always Journal Complete Sectors
When the original content of a database page is written into the rollback journal (as shown in [section 3.5](#section_3_5)), SQLite always writes a complete sector of data, even if the page size of the database is smaller than the sector size. Historically, the sector size in SQLite has been hard coded to 512 bytes and since the minimum page size is also 512 bytes, this has never been an issue. But beginning with SQLite version 3.3.14, it is possible for SQLite to use mass storage devices with a sector size larger than 512 bytes. So, beginning with version 3.3.14, whenever any page within a sector is written into the journal file, all pages in that same sector are stored with it.
It is important to store all pages of a sector in the rollback journal in order to prevent database corruption following a power loss while writing the sector. Suppose that pages 1, 2, 3, and 4 are all stored in sector 1 and that page 2 is modified. In order to write the changes to page 2, the underlying hardware must also rewrite the content of pages 1, 3, and 4 since the hardware must write the complete sector. If this write operation is interrupted by a power outage, one or more of the pages 1, 3, or 4 might be left with incorrect data. Hence, to avoid lasting corruption to the database, the original content of all of those pages must be contained in the rollback journal.
## 6.2. Dealing With Garbage Written Into Journal Files
When data is appended to the end of the rollback journal, SQLite normally makes the pessimistic assumption that the file is first extended with invalid "garbage" data and that afterwards the correct data replaces the garbage. In other words, SQLite assumes that the file size is increased first and then afterwards the content is written into the file. If a power failure occurs after the file size has been increased but before the file content has been written, the rollback journal can be left containing garbage data. If after power is restored, another SQLite process sees the rollback journal containing the garbage data and tries to roll it back into the original database file, it might copy some of the garbage into the database file and thus corrupt the database file.
SQLite uses two defenses against this problem. In the first place, SQLite records the number of pages in the rollback journal in the header of the rollback journal. This number is initially zero. So during an attempt to rollback an incomplete (and possibly corrupt) rollback journal, the process doing the rollback will see that the journal contains zero pages and will thus make no changes to the database. Prior to a commit, the rollback journal is flushed to disk to ensure that all content has been synced to disk and there is no "garbage" left in the file, and only then is the page count in the header changed from zero to the number of pages in the rollback journal. The rollback journal header is always kept in a separate sector from any page data so that it can be overwritten and flushed without risking damage to a data page if a power outage occurs. Notice that the rollback journal is flushed to disk twice: once to write the page content and a second time to write the page count in the header.
The previous paragraph describes what happens when the synchronous pragma setting is "full".
> PRAGMA synchronous=FULL;
The default synchronous setting is full so the above is what usually happens. However, if the synchronous setting is lowered to "normal", SQLite only flushes the rollback journal once, after the page count has been written. This carries a risk of corruption because it might happen that the modified (non-zero) page count reaches the disk surface before all of the data does. The data will have been written first, but SQLite assumes that the underlying filesystem can reorder write requests and that the page count can be burned into oxide first even though its write request occurred last. So as a second line of defense, SQLite also uses a 32-bit checksum on every page of data in the rollback journal. This checksum is evaluated for each page during rollback while rolling back a journal as described in [section 4.4](#section_4_4). If an incorrect checksum is seen, the rollback is abandoned. Note that the checksum does not guarantee that the page data is correct since there is a small but finite probability that the checksum might be right even if the data is corrupt. But the checksum does at least make such an error unlikely.
Note that the checksums in the rollback journal are not necessary if the synchronous setting is FULL. We only depend on the checksums when synchronous is lowered to NORMAL. Nevertheless, the checksums never hurt and so they are included in the rollback journal regardless of the synchronous setting.
## 6.3. Cache Spill Prior To Commit
The commit process shown in [section 3.0](#section_3_0) assumes that all database changes fit in memory until it is time to commit. This is the common case. But sometimes a larger change will overflow the user-space cache prior to transaction commit. In those cases, the cache must spill to the database before the transaction is complete.
At the beginning of a cache spill, the status of the database connection is as shown in [step 3.6](#section_3_6). Original page content has been saved in the rollback journal and modifications of the pages exist in user memory. To spill the cache, SQLite executes steps [3.7](#section_3_7) through [3.9](#section_3_9). In other words, the rollback journal is flushed to disk, an exclusive lock is acquired, and changes are written into the database. But the remaining steps are deferred until the transaction really commits. A new journal header is appended to the end of the rollback journal (in its own sector) and the exclusive database lock is retained, but otherwise processing returns to [step 3.6](#section_3_6). When the transaction commits, or if another cache spill occurs, steps [3.7](#section_3_7) and [3.9](#section_3_9) are repeated. (Step [3.8](#section_3_8) is omitted on second and subsequent passes since an exclusive database lock is already held due to the first pass.)
A cache spill causes the lock on the database file to escalate from reserved to exclusive. This reduces concurrency. A cache spill also causes extra disk flush or fsync operations to occur and these operations are slow, hence a cache spill can seriously reduce performance. For these reasons a cache spill is avoided whenever possible.
# 7. Optimizations
Profiling indicates that for most systems and in most circumstances SQLite spends most of its time doing disk I/O. It follows then that anything we can do to reduce the amount of disk I/O will likely have a large positive impact on the performance of SQLite. This section describes some of the techniques used by SQLite to try to reduce the amount of disk I/O to a minimum while still preserving atomic commit.
## 7.1. Cache Retained Between Transactions
[Step 3.12](#section_3_12) of the commit process shows that once the shared lock has been released, all user-space cache images of database content must be discarded. This is done because without a shared lock, other processes are free to modify the database file content and so any user-space image of that content might become obsolete. Consequently, each new transaction would begin by rereading data which had previously been read. This is not as bad as it sounds at first since the data being read is still likely in the operating systems file cache. So the "read" is really just a copy of data from kernel space into user space. But even so, it still takes time.
Beginning with SQLite version 3.3.14 a mechanism has been added to try to reduce the needless rereading of data. In newer versions of SQLite, the data in the user-space pager cache is retained when the lock on the database file is released. Later, after the shared lock is acquired at the beginning of the next transaction, SQLite checks to see if any other process has modified the database file. If the database has been changed in any way since the lock was last released, the user-space cache is erased at that point. But commonly the database file is unchanged and the user-space cache can be retained, and some unnecessary read operations can be avoided.
In order to determine whether or not the database file has changed, SQLite uses a counter in the database header (in bytes 24 through 27) which is incremented during every change operation. SQLite saves a copy of this counter prior to releasing its database lock. Then after acquiring the next database lock it compares the saved counter value against the current counter value and erases the cache if the values are different, or reuses the cache if they are the same.
## 7.2. Exclusive Access Mode
SQLite version 3.3.14 adds the concept of "Exclusive Access Mode". In exclusive access mode, SQLite retains the exclusive database lock at the conclusion of each transaction. This prevents other processes from accessing the database, but in many deployments only a single process is using a database so this is not a serious problem. The advantage of exclusive access mode is that disk I/O can be reduced in three ways:
1. It is not necessary to increment the change counter in the database header for transactions after the first transaction. This will often save a write of page one to both the rollback journal and the main database file.
2. No other processes can change the database so there is never a need to check the change counter and clear the user-space cache at the beginning of a transaction.
3. Each transaction can be committed by overwriting the rollback journal header with zeros rather than deleting the journal file. This avoids having to modify the directory entry for the journal file and it avoids having to deallocate disk sectors associated with the journal. Furthermore, the next transaction will overwrite existing journal file content rather than append new content and on most systems overwriting is much faster than appending.
The third optimization, zeroing the journal file header rather than deleting the rollback journal file, does not depend on holding an exclusive lock at all times. This optimization can be set independently of exclusive lock mode using the [journal_mode pragma](pragma.md#pragma_journal_mode) as described in [section 7.6](#section_7_6) below.
## 7.3. Do Not Journal Freelist Pages
When information is deleted from an SQLite database, the pages used to hold the deleted information are added to a "[freelist](fileformat2.md#freelist)". Subsequent inserts will draw pages off of this freelist rather than expanding the database file.
Some freelist pages contain critical data; specifically the locations of other freelist pages. But most freelist pages contain nothing useful. These latter freelist pages are called "leaf" pages. We are free to modify the content of a leaf freelist page in the database without changing the meaning of the database in any way.
Because the content of leaf freelist pages is unimportant, SQLite avoids storing leaf freelist page content in the rollback journal in [step 3.5](#section_3_5) of the commit process. If a leaf freelist page is changed and that change does not get rolled back during a transaction recovery, the database is not harmed by the omission. Similarly, the content of a new freelist page is never written back into the database at [step 3.9](#section_3_9) nor read from the database at [step 3.3](#section_3_3). These optimizations can greatly reduce the amount of I/O that occurs when making changes to a database file that contains free space.
## 7.4. Single Page Updates And Atomic Sector Writes
Beginning in SQLite version 3.5.0, the new Virtual File System (VFS) interface contains a method named xDeviceCharacteristics which reports on special properties that the underlying mass storage device might have. Among the special properties that xDeviceCharacteristics might report is the ability to do an atomic sector write.
Recall that by default SQLite assumes that sector writes are linear but not atomic. A linear write starts at one end of the sector and changes information byte by byte until it gets to the other end of the sector. If a power loss occurs in the middle of a linear write then part of the sector might be modified while the other end is unchanged. In an atomic sector write, either the entire sector is overwritten or else nothing in the sector is changed.
We believe that most modern disk drives implement atomic sector writes. When power is lost, the drive uses energy stored in capacitors and/or the angular momentum of the disk platter to provide power to complete any operation in progress. Nevertheless, there are so many layers in between the write system call and the on-board disk drive electronics that we take the safe approach in both Unix and w32 VFS implementations and assume that sector writes are not atomic. On the other hand, device manufacturers with more control over their filesystems might want to consider enabling the atomic write property of xDeviceCharacteristics if their hardware really does do atomic writes.
When sector writes are atomic and the page size of a database is the same as a sector size, and when there is a database change that only touches a single database page, then SQLite skips the whole journaling and syncing process and simply writes the modified page directly into the database file. The change counter in the first page of the database file is modified separately since no harm is done if power is lost before the change counter can be updated.
## 7.5. Filesystems With Safe Append Semantics
Another optimization introduced in SQLite version 3.5.0 makes use of "safe append" behavior of the underlying disk. Recall that SQLite assumes that when data is appended to a file (specifically to the rollback journal) that the size of the file is increased first and that the content is written second. So if power is lost after the file size is increased but before the content is written, the file is left containing invalid "garbage" data. The xDeviceCharacteristics method of the VFS might, however, indicate that the filesystem implements "safe append" semantics. This means that the content is written before the file size is increased so that it is impossible for garbage to be introduced into the rollback journal by a power loss or system crash.
When safe append semantics are indicated for a filesystem, SQLite always stores the special value of -1 for the page count in the header of the rollback journal. The -1 page count value tells any process attempting to rollback the journal that the number of pages in the journal should be computed from the journal size. This -1 value is never changed. So that when a commit occurs, we save a single flush operation and a sector write of the first page of the journal file. Furthermore, when a cache spill occurs we no longer need to append a new journal header to the end of the journal; we can simply continue appending new pages to the end of the existing journal.
## 7.6. Persistent Rollback Journals
Deleting a file is an expensive operation on many systems. So as an optimization, SQLite can be configured to avoid the delete operation of [section 3.11](#section_3_11). Instead of deleting the journal file in order to commit a transaction, the file is either truncated to zero bytes in length or its header is overwritten with zeros. Truncating the file to zero length saves having to make modifications to the directory containing the file since the file is not removed from the directory. Overwriting the header has the additional savings of not having to update the length of the file (in the "inode" on many systems) and not having to deal with newly freed disk sectors. Furthermore, at the next transaction the journal will be created by overwriting existing content rather than appending new content onto the end of a file, and overwriting is often much faster than appending.
SQLite can be configured to commit transactions by overwriting the journal header with zeros instead of deleting the journal file by setting the "PERSIST" journaling mode using the [journal_mode](pragma.md#pragma_journal_mode) PRAGMA. For example:
> \
> PRAGMA journal_mode=PERSIST;\
The use of persistent journal mode provides a noticeable performance improvement on many systems. Of course, the drawback is that the journal files remain on the disk, using disk space and cluttering directories, long after the transaction commits. The only safe way to delete a persistent journal file is to commit a transaction with journaling mode set to DELETE:
> \
> PRAGMA journal_mode=DELETE;\
> BEGIN EXCLUSIVE;\
> COMMIT;\
Beware of deleting persistent journal files by any other means since the journal file might be hot, in which case deleting it will corrupt the corresponding database file.
Beginning in SQLite [version 3.6.4](releaselog/3_6_4.md) (2008-10-15), the TRUNCATE journal mode is also supported:
> \
> PRAGMA journal_mode=TRUNCATE;\
In truncate journal mode, the transaction is committed by truncating the journal file to zero length rather than deleting the journal file (as in DELETE mode) or by zeroing the header (as in PERSIST mode). TRUNCATE mode shares the advantage of PERSIST mode that the directory that contains the journal file and database does not need to be updated. Hence truncating a file is often faster than deleting it. TRUNCATE has the additional advantage that it is not followed by a system call (ex: fsync()) to synchronize the change to disk. It might be safer if it did. But on many modern filesystems, a truncate is an atomic and synchronous operation and so we think that TRUNCATE will usually be safe in the face of power failures. If you are uncertain about whether or not TRUNCATE will be synchronous and atomic on your filesystem and it is important to you that your database survive a power loss or operating system crash that occurs during the truncation operation, then you might consider using a different journaling mode.
On embedded systems with synchronous filesystems, TRUNCATE results in slower behavior than PERSIST. The commit operation is the same speed. But subsequent transactions are slower following a TRUNCATE because it is faster to overwrite existing content than to append to the end of a file. New journal file entries will always be appended following a TRUNCATE but will usually overwrite with PERSIST.
# 8. Testing Atomic Commit Behavior
The developers of SQLite are confident that it is robust in the face of power failures and system crashes because the automatic test procedures do extensive checks on the ability of SQLite to recover from simulated power loss. We call these the "crash tests".
Crash tests in SQLite use a modified VFS that can simulate the kinds of filesystem damage that occur during a power loss or operating system crash. The crash-test VFS can simulate incomplete sector writes, pages filled with garbage data because a write has not completed, and out of order writes, all occurring at varying points during a test scenario. Crash tests execute transactions over and over, varying the time at which a simulated power loss occurs and the properties of the damage inflicted. Each test then reopens the database after the simulated crash and verifies that the transaction either occurred completely or not at all and that the database is in a completely consistent state.
The crash tests in SQLite have discovered a number of very subtle bugs (now fixed) in the recovery mechanism. Some of these bugs were very obscure and unlikely to have been found using only code inspection and analysis techniques. From this experience, the developers of SQLite feel confident that any other database system that does not use a similar crash test system likely contains undetected bugs that will lead to database corruption following a system crash or power failure.
# 9. Things That Can Go Wrong
The atomic commit mechanism in SQLite has proven to be robust, but it can be circumvented by a sufficiently creative adversary or a sufficiently broken operating system implementation. This section describes a few of the ways in which an SQLite database might be corrupted by a power failure or system crash. (See also: [How To Corrupt Your Database Files](howtocorrupt.md).)
## 9.1. Broken Locking Implementations
SQLite uses filesystem locks to make sure that only one process and database connection is trying to modify the database at a time. The filesystem locking mechanism is implemented in the VFS layer and is different for every operating system. SQLite depends on this implementation being correct. If something goes wrong and two or more processes are able to write the same database file at the same time, severe damage can result.
We have received reports of implementations of both Windows network filesystems and NFS in which locking was subtly broken. We can not verify these reports, but as locking is difficult to get right on a network filesystem we have no reason to doubt them. You are advised to avoid using SQLite on a network filesystem in the first place, since performance will be slow. But if you must use a network filesystem to store SQLite database files, consider using a secondary locking mechanism to prevent simultaneous writes to the same database even if the native filesystem locking mechanism malfunctions.
The versions of SQLite that come preinstalled on Apple Mac OS X computers contain a version of SQLite that has been extended to use alternative locking strategies that work on all network filesystems that Apple supports. These extensions used by Apple work great as long as all processes are accessing the database file in the same way. Unfortunately, the locking mechanisms do not exclude one another, so if one process is accessing a file using (for example) AFP locking and another process (perhaps on a different machine) is using dot-file locks, the two processes might collide because AFP locks do not exclude dot-file locks or vice versa.
## 9.2. Incomplete Disk Flushes
SQLite uses the fsync() system call on Unix and the FlushFileBuffers() system call on w32 in order to sync the file system buffers onto disk oxide as shown in [step 3.7](#section_3_7) and [step 3.10](#section_3_10). Unfortunately, we have received reports that neither of these interfaces works as advertised on many systems. We hear that FlushFileBuffers() can be completely disabled using registry settings on some Windows versions. Some historical versions of Linux contain versions of fsync() which are no-ops on some filesystems, we are told. Even on systems where FlushFileBuffers() and fsync() are said to be working, often the IDE disk control lies and says that data has reached oxide while it is still held only in the volatile control cache.
On the Mac, you can set this pragma:
> PRAGMA fullfsync=ON;
Setting fullfsync on a Mac will guarantee that data really does get pushed out to the disk platter on a flush. But the implementation of fullfsync involves resetting the disk controller. And so not only is it profoundly slow, it also slows down other unrelated disk I/O. So its use is not recommended.
## 9.3. Partial File Deletions
SQLite assumes that file deletion is an atomic operation from the point of view of a user process. If power fails in the middle of a file deletion, then after power is restored SQLite expects to see either the entire file with all of its original data intact, or it expects not to find the file at all. Transactions may not be atomic on systems that do not work this way.
## 9.4. Garbage Written Into Files
SQLite database files are ordinary disk files that can be opened and written by ordinary user processes. A rogue process can open an SQLite database and fill it with corrupt data. Corrupt data might also be introduced into an SQLite database by bugs in the operating system or disk controller; especially bugs triggered by a power failure. There is nothing SQLite can do to defend against these kinds of problems.
## 9.5. Deleting Or Renaming A Hot Journal
If a crash or power loss does occur and a hot journal is left on the disk, it is essential that the original database file and the hot journal remain on disk with their original names until the database file is opened by another SQLite process and rolled back. During recovery at [step 4.2](#section_4_2) SQLite locates the hot journal by looking for a file in the same directory as the database being opened and whose name is derived from the name of the file being opened. If either the original database file or the hot journal have been moved or renamed, then the hot journal will not be seen and the database will not be rolled back.
We suspect that a common failure mode for SQLite recovery happens like this: A power failure occurs. After power is restored, a well-meaning user or system administrator begins looking around on the disk for damage. They see their database file named "important.data". This file is perhaps familiar to them. But after the crash, there is also a hot journal named "important.data-journal". The user then deletes the hot journal, thinking that they are helping to cleanup the system. We know of no way to prevent this other than user education.
If there are multiple (hard or symbolic) links to a database file, the journal will be created using the name of the link through which the file was opened. If a crash occurs and the database is opened again using a different link, the hot journal will not be located and no rollback will occur.
Sometimes a power failure will cause a filesystem to be corrupted such that recently changed filenames are forgotten and the file is moved into a "/lost+found" directory. When that happens, the hot journal will not be found and recovery will not occur. SQLite tries to prevent this by opening and syncing the directory containing the rollback journal at the same time it syncs the journal file itself. However, the movement of files into /lost+found can be caused by unrelated processes creating unrelated files in the same directory as the main database file. And since this is out from under the control of SQLite, there is nothing that SQLite can do to prevent it. If you are running on a system that is vulnerable to this kind of filesystem namespace corruption (most modern journalling filesystems are immune, we believe) then you might want to consider putting each SQLite database file in its own private subdirectory.
# 10. Future Directions And Conclusion
Every now and then someone discovers a new failure mode for the atomic commit mechanism in SQLite and the developers have to put in a patch. This is happening less and less and the failure modes are becoming more and more obscure. But it would still be foolish to suppose that the atomic commit logic of SQLite is entirely bug-free. The developers are committed to fixing these bugs as quickly as they might be found.
The developers are also on the lookout for new ways to optimize the commit mechanism. The current VFS implementations for Unix (Linux and Mac OS X) and Windows make pessimistic assumptions about the behavior of those systems. After consultation with experts on how these systems work, we might be able to relax some of the assumptions on these systems and allow them to run faster. In particular, we suspect that most modern filesystems exhibit the safe append property and that many of them might support atomic sector writes. But until this is known for certain, SQLite will take the conservative approach and assume the worst.
---
# Attach A Table To A Session Object
*Sección: Guides | Origen: https://www.sqlite.org/session/sqlite3session_attach.html*
[](../session/intro.md)
## Session Module C Interface
## Attach A Table To A Session Object
> int sqlite3session_attach(\
> sqlite3_session \*pSession, /\* Session object \*/\
> const char \*zTab /\* Table name \*/\
> );\
If argument zTab is not NULL, then it is the name of a table to attach to the session object passed as the first argument. All subsequent changes made to the table while the session object is enabled will be recorded. See documentation for [sqlite3session_changeset()](../session/sqlite3session_changeset.md) for further details.
Or, if argument zTab is NULL, then changes are recorded for all tables in the database. If additional tables are added to the database (by executing "CREATE TABLE" statements) after this call is made, changes for the new tables are also recorded.
Changes can only be recorded for tables that have a PRIMARY KEY explicitly defined as part of their CREATE TABLE statement. It does not matter if the PRIMARY KEY is an "INTEGER PRIMARY KEY" (rowid alias) or not. The PRIMARY KEY may consist of a single column, or may be a composite key.
It is not an error if the named table does not exist in the database. Nor is it an error if the named table does not have a PRIMARY KEY. However, no changes will be recorded in either of these scenarios.
Changes are not recorded for individual rows that have NULL values stored in one or more of their PRIMARY KEY columns.
SQLITE_OK is returned if the call completes without error. Or, if an error occurs, an SQLite error code (e.g. SQLITE_NOMEM) is returned.
### Special sqlite_stat1 Handling
As of SQLite version 3.22.0, the "sqlite_stat1" table is an exception to some of the rules above. In SQLite, the schema of sqlite_stat1 is:
\
CREATE TABLE sqlite_stat1(tbl,idx,stat) \
Even though sqlite_stat1 does not have a PRIMARY KEY, changes are recorded for it as if the PRIMARY KEY is (tbl,idx). Additionally, changes are recorded for rows for which (idx IS NULL) is true. However, for such rows a zero-length blob (SQL value X'') is stored in the changeset or patchset instead of a NULL value. This allows such changesets to be manipulated by legacy implementations of sqlite3changeset_invert(), concat() and similar.
The sqlite3changeset_apply() function automatically converts the zero-length blob back to a NULL value when updating the sqlite_stat1 table. However, if the application calls sqlite3changeset_new(), sqlite3changeset_old() or sqlite3changeset_conflict on a changeset iterator directly (including on a changeset iterator passed to a conflict-handler callback) then the X'' value is returned. The application must translate X'' to NULL itself if required.
Legacy (older than 3.22.0) versions of the sessions module cannot capture changes made to the sqlite_stat1 table. Legacy versions of the sqlite3changeset_apply() function silently ignore any modifications to the sqlite_stat1 table that are part of a changeset or patchset.
See also lists of [Objects](../session/objlist.md), [Constants](../session/constlist.md), and [Functions](../session/funclist.md).
---
# Automatic Undo/Redo With SQLite
*Sección: Guides | Origen: https://www.sqlite.org/undoredo.html*
# Automatic Undo/Redo Using SQLite
This page demonstrates how to use triggers to implement undo/redo logic for an application that uses SQLite as its [application file format](appfileformat.md).
## Object-Oriented Design
This design note considers the database to be a collection of objects. Each SQL table is a class. Each row is an instance of that class. There are, of course, other ways to interpret an SQL database schema, and the techniques described here work equally well under alternative interpretations, but an object-oriented view seems be more natural to most contemporary programmers.
## Capture Changes Using Triggers
The core idea is to create a special table (named "UNDOLOG" in the example) that holds information needed to undo/redo changes to the database. For each class (table) in the database that wants to participate in the undo/redo, triggers are created that cause entries to be made in the UNDOLOG table for each DELETE, INSERT, and UPDATE of the participating class. The UNDOLOG entries consist of ordinary SQL statements the can be played back to reverse the changes.
For example, suppose you wanted undo/redo on a class (table) that looks like this:
> \
> CREATE TABLE ex1(a,b,c);\
Triggers to record changes to table EX1 might look like this:
> \
> CREATE TEMP TRIGGER ex1_it AFTER INSERT ON ex1 BEGIN\
> INSERT INTO undolog VALUES(NULL,'DELETE FROM ex1 WHERE rowid='\|\|new.rowid);\
> END;\
> CREATE TEMP TRIGGER ex1_ut AFTER UPDATE ON ex1 BEGIN\
> INSERT INTO undolog VALUES(NULL,'UPDATE ex1\
> SET a='\|\|quote(old.a)\|\|',b='\|\|quote(old.b)\|\|',c='\|\|quote(old.c)\|\|'\
> WHERE rowid='\|\|old.rowid);\
> END;\
> CREATE TEMP TRIGGER ex1_dt BEFORE DELETE ON ex1 BEGIN\
> INSERT INTO undolog VALUES(NULL,'INSERT INTO ex1(rowid,a,b,c)\
> VALUES('\|\|old.rowid\|\|','\|\|quote(old.a)\|\|','\|\|quote(old.b)\|\|\
> ','\|\|quote(old.c)\|\|')');\
> END;\
After each INSERT on ex1, the ex1_it trigger constructs text of a DELETE statement that will undo the INSERT. The ex1_ut trigger constructs an UPDATE statement that will undo the effects of an UPDATE. And the ex1_dt trigger constructs a statement that will undo the effects of a DELETE.
Note the use of the [quote() SQL function](lang_corefunc.md#quote) in these triggers. The quote() function converts its argument into a form that is appropriate for inclusion in an SQL statement. Numeric values come through unchanged. Single quotes are added before and after strings and any internal single quotes are escaped. BLOB values are rendered using SQL-standard hexadecimal BLOB notation. The use of the quote() function ensures that the SQL statements used to undo and redo are always safe from SQL injection.
## Automatic Creation Of Triggers
Triggers such as the above could be entered manually, but that is tedious. An important feature of the technique demonstrated below is that the triggers are generated automatically.
The implementation language for the example code is [TCL](http://www.tcl-lang.org), though you can easily do the same thing in another programming language. Remember that the code here is a demonstration of the technique, not a drop-in module that will automatically do everything for you. The demonstration code shown below is derived from actual code in production use. But you will need to make changes to tailor it to your application.
To activate the undo/redo logic, invoke the undo::activate command with all classes (tables) that are to participate in the undo/redo as arguments. Use undo::deactivate, undo::freeze, and undo::unfreeze to control the state of the undo/redo mechanism.
The undo::activate command creates temporary triggers in the database that record all changes made to the tables named in the arguments.
## Application Interface
After a sequence of changes that define a single undo/redo step, invoke the undo::barrier command to define the limit of that step. In an interactive program, you can call undo::event after any change and undo::barrier will be called automatically as an idle callback.
When the user presses the Undo button, invoke undo::undo. Invoke undo::redo when the user presses the Redo button.
On each call to undo::undo or undo::redo, the undo/redo module automatically invokes methods status_refresh and reload_all in all toplevel namespaces. These methods should be defined to reconstruct the display or otherwise update the state of the program based on the undone/redone changes to the database.
The demonstration code below includes a status_refresh method that grays-out or activates the Undo and Redo buttons and menu entries depending on whether or not there is anything to be undone or redone. You will need to redefine this method to control the Undo and Redo buttons in your application.
The demonstration code assumes that the SQLite database is opened and used as a database object named "db".
## Example Code
> \
> \# Everything goes in a private namespace\
> namespace eval ::undo {\
> \
> \# proc: ::undo::activate TABLE ...\
> \# title: Start up the undo/redo system\
> \#\
> \# Arguments should be one or more database tables (in the database associated\
> \# with the handle "db") whose changes are to be recorded for undo/redo\
> \# purposes.\
> \#\
> proc activate {args} {\
> variable \_undo\
> if {\$\_undo(active)} return\
> eval \_create_triggers db \$args\
> set \_undo(undostack) {}\
> set \_undo(redostack) {}\
> set \_undo(active) 1\
> set \_undo(freeze) -1\
> \_start_interval\
> }\
> \
> \# proc: ::undo::deactivate\
> \# title: Halt the undo/redo system and delete the undo/redo stacks\
> \#\
> proc deactivate {} {\
> variable \_undo\
> if {!\$\_undo(active)} return\
> \_drop_triggers db\
> set \_undo(undostack) {}\
> set \_undo(redostack) {}\
> set \_undo(active) 0\
> set \_undo(freeze) -1\
> }\
> \
> \# proc: ::undo::freeze\
> \# title: Stop accepting database changes into the undo stack\
> \#\
> \# From the point when this routine is called up until the next unfreeze,\
> \# new database changes are rejected from the undo stack.\
> \#\
> proc freeze {} {\
> variable \_undo\
> if {\![info exists \_undo(freeze)\]} return\
> if {\$\_undo(freeze)\>=0} {error "recursive call to ::undo::freeze"}\
> set \_undo(freeze) \[db one {SELECT coalesce(max(seq),0) FROM undolog}\]\
> }\
> \
> \# proc: ::undo::unfreeze\
> \# title: Begin accepting undo actions again.\
> \#\
> proc unfreeze {} {\
> variable \_undo\
> if {\![info exists \_undo(freeze)\]} return\
> if {\$\_undo(freeze)\<0} {error "called ::undo::unfreeze while not frozen"}\
> db eval "DELETE FROM undolog WHERE seq\>\$\_undo(freeze)"\
> set \_undo(freeze) -1\
> }\
> \
> \# proc: ::undo::event\
> \# title: Something undoable has happened\
> \#\
> \# This routine is called whenever an undoable action occurs. Arrangements\
> \# are made to invoke ::undo::barrier no later than the next idle moment.\
> \#\
> proc event {} {\
> variable \_undo\
> if {\$\_undo(pending)==""} {\
> set \_undo(pending) \[after idle ::undo::barrier\]\
> }\
> }\
> \
> \# proc: ::undo::barrier\
> \# title: Create an undo barrier right now.\
> \#\
> proc barrier {} {\
> variable \_undo\
> catch {after cancel \$\_undo(pending)}\
> set \_undo(pending) {}\
> if {!\$\_undo(active)} {\
> refresh\
> return\
> }\
> set end \[db one {SELECT coalesce(max(seq),0) FROM undolog}\]\
> if {\$\_undo(freeze)\>=0 && \$end\>\$\_undo(freeze)} {set end \$\_undo(freeze)}\
> set begin \$\_undo(firstlog)\
> \_start_interval\
> if {\$begin==\$\_undo(firstlog)} {\
> refresh\
> return\
> }\
> lappend \_undo(undostack) \[list \$begin \$end\]\
> set \_undo(redostack) {}\
> refresh\
> }\
> \
> \# proc: ::undo::undo\
> \# title: Do a single step of undo\
> \#\
> proc undo {} {\
> \_step undostack redostack\
> }\
> \
> \# proc: ::undo::redo\
> \# title: Redo a single step\
> \#\
> proc redo {} {\
> \_step redostack undostack\
> }\
> \
> \# proc: ::undo::refresh\
> \# title: Update the status of controls after a database change\
> \#\
> \# The undo module calls this routine after any undo/redo in order to\
> \# cause controls gray out appropriately depending on the current state\
> \# of the database. This routine works by invoking the status_refresh\
> \# module in all top-level namespaces.\
> \#\
> proc refresh {} {\
> set body {}\
> foreach ns \[namespace children ::\] {\
> if {\[info proc \${ns}::status_refresh\]==""} continue\
> append body \${ns}::status_refresh\n\
> }\
> proc ::undo::refresh {} \$body\
> refresh\
> }\
> \
> \# proc: ::undo::reload_all\
> \# title: Redraw everything based on the current database\
> \#\
> \# The undo module calls this routine after any undo/redo in order to\
> \# cause the screen to be completely redrawn based on the current database\
> \# contents. This is accomplished by calling the "reload" module in\
> \# every top-level namespace other than ::undo.\
> \#\
> proc reload_all {} {\
> set body {}\
> foreach ns \[namespace children ::\] {\
> if {\[info proc \${ns}::reload\]==""} continue\
> append body \${ns}::reload\n\
> }\
> proc ::undo::reload_all {} \$body\
> reload_all\
> }\
> \
> \##############################################################################\
> \# The public interface to this module is above. Routines and variables that\
> \# follow (and whose names begin with "\_") are private to this module.\
> \##############################################################################\
> \
> \# state information\
> \#\
> set \_undo(active) 0\
> set \_undo(undostack) {}\
> set \_undo(redostack) {}\
> set \_undo(pending) {}\
> set \_undo(firstlog) 1\
> set \_undo(startstate) {}\
> \
> \
> \# proc: ::undo::status_refresh\
> \# title: Enable and/or disable menu options a buttons\
> \#\
> proc status_refresh {} {\
> variable \_undo\
> if {!\$\_undo(active) \|\| \[llength \$\_undo(undostack)\]==0} {\
> .mb.edit entryconfig Undo -state disabled\
> .bb.undo config -state disabled\
> } else {\
> .mb.edit entryconfig Undo -state normal\
> .bb.undo config -state normal\
> }\
> if {!\$\_undo(active) \|\| \[llength \$\_undo(redostack)\]==0} {\
> .mb.edit entryconfig Redo -state disabled\
> .bb.redo config -state disabled\
> } else {\
> .mb.edit entryconfig Redo -state normal\
> .bb.redo config -state normal\
> }\
> }\
> \
> \# xproc: ::undo::\_create_triggers DB TABLE1 TABLE2 ...\
> \# title: Create change recording triggers for all tables listed\
> \#\
> \# Create a temporary table in the database named "undolog". Create\
> \# triggers that fire on any insert, delete, or update of TABLE1, TABLE2, ....\
> \# When those triggers fire, insert records in undolog that contain\
> \# SQL text for statements that will undo the insert, delete, or update.\
> \#\
> proc \_create_triggers {db args} {\
> catch {\$db eval {DROP TABLE undolog}}\
> \$db eval {CREATE TEMP TABLE undolog(seq integer primary key, sql text)}\
> foreach tbl \$args {\
> set collist \[\$db eval "pragma table_info(\$tbl)"\]\
> set sql "CREATE TEMP TRIGGER \_\${tbl}\_it AFTER INSERT ON \$tbl BEGIN\n"\
> append sql " INSERT INTO undolog VALUES(NULL,"\
> append sql "'DELETE FROM \$tbl WHERE rowid='\|\|new.rowid);\nEND;\n"\
> \
> append sql "CREATE TEMP TRIGGER \_\${tbl}\_ut AFTER UPDATE ON \$tbl BEGIN\n"\
> append sql " INSERT INTO undolog VALUES(NULL,"\
> append sql "'UPDATE \$tbl "\
> set sep "SET "\
> foreach {x1 name x2 x3 x4 x5} \$collist {\
> append sql "\$sep\$name='\|\|quote(old.\$name)\|\|'"\
> set sep ","\
> }\
> append sql " WHERE rowid='\|\|old.rowid);\nEND;\n"\
> \
> append sql "CREATE TEMP TRIGGER \_\${tbl}\_dt BEFORE DELETE ON \$tbl BEGIN\n"\
> append sql " INSERT INTO undolog VALUES(NULL,"\
> append sql "'INSERT INTO \${tbl}(rowid"\
> foreach {x1 name x2 x3 x4 x5} \$collist {append sql ,\$name}\
> append sql ") VALUES('\|\|old.rowid\|\|'"\
> foreach {x1 name x2 x3 x4 x5} \$collist {append sql ,'\|\|quote(old.\$name)\|\|'}\
> append sql ")');\nEND;\n"\
> \
> \$db eval \$sql\
> }\
> }\
> \
> \# xproc: ::undo::\_drop_triggers DB\
> \# title: Drop all of the triggers that \_create_triggers created\
> \#\
> proc \_drop_triggers {db} {\
> set tlist \[\$db eval {SELECT name FROM sqlite_temp_schema\
> WHERE type='trigger'}\]\
> foreach trigger \$tlist {\
> if {\![regexp {\_.\*\_(i\|u\|d)t\$} \$trigger\]} continue\
> \$db eval "DROP TRIGGER \$trigger;"\
> }\
> catch {\$db eval {DROP TABLE undolog}}\
> }\
> \
> \# xproc: ::undo::\_start_interval\
> \# title: Record the starting conditions of an undo interval\
> \#\
> proc \_start_interval {} {\
> variable \_undo\
> set \_undo(firstlog) \[db one {SELECT coalesce(max(seq),0)+1 FROM undolog}\]\
> }\
> \
> \# xproc: ::undo::\_step V1 V2\
> \# title: Do a single step of undo or redo\
> \#\
> \# For an undo V1=="undostack" and V2=="redostack". For a redo,\
> \# V1=="redostack" and V2=="undostack".\
> \#\
> proc \_step {v1 v2} {\
> variable \_undo\
> set op \[lindex \$\_undo(\$v1) end\]\
> set \_undo(\$v1) \[lrange \$\_undo(\$v1) 0 end-1\]\
> foreach {begin end} \$op break\
> db eval BEGIN\
> set q1 "SELECT sql FROM undolog WHERE seq\>=\$begin AND seq\<=\$end\
> ORDER BY seq DESC"\
> set sqllist \[db eval \$q1\]\
> db eval "DELETE FROM undolog WHERE seq\>=\$begin AND seq\<=\$end"\
> set \_undo(firstlog) \[db one {SELECT coalesce(max(seq),0)+1 FROM undolog}\]\
> foreach sql \$sqllist {\
> db eval \$sql\
> }\
> db eval COMMIT\
> reload_all\
> \
> set end \[db one {SELECT coalesce(max(seq),0) FROM undolog}\]\
> set begin \$\_undo(firstlog)\
> lappend \_undo(\$v2) \[list \$begin \$end\]\
> \_start_interval\
> refresh\
> }\
> \
> \
> \# End of the ::undo namespace\
> }\
---
# Backlink Crossreference
*Sección: Guides | Origen: https://www.sqlite.org/doc_backlink_crossref.html*
- --blob-quote option → [climode.html#opt-textjsonb](climode.md#opt-textjsonb)
- --border setting → [climode.html#clmnr](climode.md#clmnr)
- --charlimit option → [climode.html#opt-linelimit](climode.md#opt-linelimit) [climode.html#opt-tlim](climode.md#opt-tlim)
- --colsep option → [cli.html#csv](cli.md#csv)
- --limits option → [climode.html](climode.md) [climode.html#opt-charlimit](climode.md#opt-charlimit) [climode.html#opt-linelimit](climode.md#opt-linelimit) [climode.html#opt-tlim](climode.md#opt-tlim)
- --linelimit option → [climode.html#opt-charlimit](climode.md#opt-charlimit) [climode.html#opt-tlim](climode.md#opt-tlim)
- --multiinsert setting → [climode.html#qbox](climode.md#qbox)
- --null option → [climode.html#opt-quote](climode.md#opt-quote)
- --once option → [climode.html](climode.md)
- --quote option → [climode.html](climode.md) [climode.html#opt-textjsonb](climode.md#opt-textjsonb)
- --quote setting → [climode.html#clmnr](climode.md#clmnr) [climode.html#opt-blob](climode.md#opt-blob)
- --reset option → [climode.html#crlf](climode.md#crlf)
- --rowsep option → [cli.html#csv](cli.md#csv)
- --safe command-line option → [changes.html#version_3_37_0](changes.md#version_3_37_0) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md)
- --screenwidth option → [climode.html](climode.md) [climode.html#split](climode.md#split)
- --tag option → [climode.html#opt-list](climode.md#opt-list) [climode.html#usermode](climode.md#usermode)
- --textjsonb option → [climode.html](climode.md)
- --titlelimit option → [climode.html#opt-charlimit](climode.md#opt-charlimit) [climode.html#opt-linelimit](climode.md#opt-linelimit)
- --unsafe-testing command-line option → [imposter.html#dotimposter](imposter.md#dotimposter)
- --update option → [changes.html#version_3_28_0](changes.md#version_3_28_0) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- --width option → [climode.html](climode.md)
- --wrap option → [climode.html#opt-wwrap](climode.md#opt-wwrap)
- -DSQLITE_DEBUG → [debugging.html](debugging.md)
- -DSQLITE_DEFAULT_FOREIGN_KEYS → [quirks.html](quirks.md)
- -DSQLITE_DEFAULT_LOOKASIDE → [c3ref/c_config_covering_index_scan.html#sqliteconfiglookaside](c3ref/c_config_covering_index_scan.md#sqliteconfiglookaside) [c3ref/c_dbconfig_defensive.html#sqlitedbconfiglookaside](c3ref/c_dbconfig_defensive.md#sqlitedbconfiglookaside) [capi3ref.html#sqliteconfiglookaside](capi3ref.md#sqliteconfiglookaside) [capi3ref.html#sqlitedbconfiglookaside](capi3ref.md#sqlitedbconfiglookaside)
- -DSQLITE_DEFAULT_MEMSTATUS → [changes.html#version_3_50_1](changes.md#version_3_50_1) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- -DSQLITE_DIRECT_OVERFLOW_READ → [fasterthanfs.html](fasterthanfs.md)
- -DSQLITE_DQS → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigdqsddl](c3ref/c_dbconfig_defensive.md#sqlitedbconfigdqsddl) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigdqsdml](c3ref/c_dbconfig_defensive.md#sqlitedbconfigdqsdml) [capi3ref.html#sqlitedbconfigdqsddl](capi3ref.md#sqlitedbconfigdqsddl) [capi3ref.html#sqlitedbconfigdqsdml](capi3ref.md#sqlitedbconfigdqsdml) [changes.html#version_3_29_0](changes.md#version_3_29_0) [news.html](news.md) [quirks.html#dblquote](quirks.md#dblquote) [releaselog/3_29_0.html](releaselog/3_29_0.md)
- -DSQLITE_ENABLE_BYTECODE_VTAB → [bytecodevtab.html](bytecodevtab.md)
- -DSQLITE_ENABLE_CARRAY → [carray.html](carray.md) [changes.html#version_3_51_0](changes.md#version_3_51_0) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- -DSQLITE_ENABLE_DBPAGE_VTAB → [changes.html#version_3_21_0](changes.md#version_3_21_0) [cli.html#compiling](cli.md#compiling) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- -DSQLITE_ENABLE_DBSTAT_VTAB → [amalgamation.html](amalgamation.md) [cli.html#compiling](cli.md#compiling) [howtocompile.html#cli](howtocompile.md#cli)
- -DSQLITE_ENABLE_EXPLAIN_COMMENTS → [changes.html#version_3_14_2](changes.md#version_3_14_2) [cli.html#compiling](cli.md#compiling) [debugging.html](debugging.md) [howtocompile.html#cli](howtocompile.md#cli) [opcode.html#subprog](opcode.md#subprog) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- -DSQLITE_ENABLE_FTS3 → [amalgamation.html](amalgamation.md)
- -DSQLITE_ENABLE_FTS4 → [cli.html#compiling](cli.md#compiling) [howtocompile.html#cli](howtocompile.md#cli)
- -DSQLITE_ENABLE_FTS5 → [amalgamation.html](amalgamation.md) [cli.html#compiling](cli.md#compiling) [howtocompile.html#cli](howtocompile.md#cli)
- -DSQLITE_ENABLE_GEOPOLY → [geopoly.html](geopoly.md)
- -DSQLITE_ENABLE_ICU → [quirks.html](quirks.md)
- -DSQLITE_ENABLE_JSON1 → [changes.html#version_3_38_0](changes.md#version_3_38_0) [cli.html#compiling](cli.md#compiling) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md)
- -DSQLITE_ENABLE_MATH_FUNCTIONS → [changes.html#version_3_35_0](changes.md#version_3_35_0) [howtocompile.html#cli](howtocompile.md#cli) [lang_mathfunc.html](lang_mathfunc.md) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- -DSQLITE_ENABLE_MEMSYS5 → [security.html](security.md)
- -DSQLITE_ENABLE_OFFSET_SQL_FUNC → [changes.html#version_3_22_0](changes.md#version_3_22_0) [cli.html#compiling](cli.md#compiling) [lang_corefunc.html#sqlite_offset](lang_corefunc.md#sqlite_offset) [releaselog/3_22_0.html](releaselog/3_22_0.md)
- -DSQLITE_ENABLE_ORDERED_SET_AGGREGATES → [percentile.html#\*percentilecontfunc](percentile.md#*percentilecontfunc)
- -DSQLITE_ENABLE_PERCENTILE → [changes.html#version_3_51_0](changes.md#version_3_51_0) [lang_aggfunc.html#median](lang_aggfunc.md#median) [lang_aggfunc.html#percentile](lang_aggfunc.md#percentile) [lang_aggfunc.html#percentile_cont](lang_aggfunc.md#percentile_cont) [lang_aggfunc.html#percentile_disc](lang_aggfunc.md#percentile_disc) [percentile.html](percentile.md) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- -DSQLITE_ENABLE_RBU → [amalgamation.html](amalgamation.md)
- -DSQLITE_ENABLE_RTREE → [amalgamation.html](amalgamation.md) [cli.html#compiling](cli.md#compiling) [howtocompile.html#cli](howtocompile.md#cli)
- -DSQLITE_ENABLE_SESSION → [amalgamation.html](amalgamation.md) [cves.html#cvetab](cves.md#cvetab)
- -DSQLITE_ENABLE_SNAPSHOT → [rescode.html#error_snapshot](rescode.md#error_snapshot)
- -DSQLITE_ENABLE_STMTVTAB → [cli.html#compiling](cli.md#compiling)
- -DSQLITE_ENABLE_UNKNOWN_SQL_FUNCTION → [cli.html#compiling](cli.md#compiling)
- -DSQLITE_HAVE_ZLIB → [cli.html#compiling](cli.md#compiling)
- -DSQLITE_INTROSPECTION_PRAGMAS → [cli.html#compiling](cli.md#compiling)
- -DSQLITE_OMIT_DESERIALIZE → [changes.html#version_3_36_0](changes.md#version_3_36_0) [releaselog/3_36_0.html](releaselog/3_36_0.md)
- -DSQLITE_OMIT_INTROSPECTION_PRAGMAS → [changes.html#version_3_30_0](changes.md#version_3_30_0) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md)
- -DSQLITE_OMIT_JSON → [changes.html#version_3_38_0](changes.md#version_3_38_0) [compile.html#enable_json1](compile.md#enable_json1) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md)
- -DSQLITE_OMIT_SHARED_CACHE → [c3ref/enable_shared_cache.html](c3ref/enable_shared_cache.md) [capi3ref.html#sqlite3_enable_shared_cache](capi3ref.md#sqlite3_enable_shared_cache) [sharedcache.html#dontuse](sharedcache.md#dontuse)
- -DSQLITE_OMIT_VACUUM → [c3ref/keyword_check.html](c3ref/keyword_check.md) [capi3ref.html#sqlite3_keyword_check](capi3ref.md#sqlite3_keyword_check)
- -DSQLITE_PRINTF_PRECISION_LIMIT → [security.html](security.md)
- -DSQLITE_STRICT_SUBTYPE → [changes.html#version_3_45_0](changes.md#version_3_45_0) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- -DSQLITE_TEMP_STORE → [howtocorrupt.html#svptbug](howtocorrupt.md#svptbug) [news.html](news.md)
- -DSQLITE_THREADSAFE → [cli.html#compiling](cli.md#compiling) [fasterthanfs.html](fasterthanfs.md)
- -DSQLITE_TRUSTED_SCHEMA → [appfunc.html#sec](appfunc.md#sec) [changes.html#version_3_31_0](changes.md#version_3_31_0) [pragma.html#pragma_trusted_schema](pragma.md#pragma_trusted_schema) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [security.html#baddb](security.md#baddb)
- -DSQLITE_USE_URI → [lang_vacuum.html#vacuuminto](lang_vacuum.md#vacuuminto)
- .archive command → [changes.html#version_3_22_0](changes.md#version_3_22_0) [changes.html#version_3_28_0](changes.md#version_3_28_0) [cli.html#compiling](cli.md#compiling) [cli.html#safemode](cli.md#safemode) [releaselog/3_22_0.html](releaselog/3_22_0.md) [releaselog/3_28_0.html](releaselog/3_28_0.md) [sqlar.html#cltools](sqlar.md#cltools) [vtablist.html](vtablist.md) [whentouse.html#container](whentouse.md#container)
- .connection → [changes.html#version_3_37_0](changes.md#version_3_37_0) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md)
- .databases → [changes.html#version_3_34_0](changes.md#version_3_34_0) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md)
- .dump → [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_32_0](changes.md#version_3_32_0) [changes.html#version_3_34_0](changes.md#version_3_34_0) [changes.html#version_3_35_1](changes.md#version_3_35_1) [nulinstr.html](nulinstr.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [stricttables.html](stricttables.md) [vtab.html#xshadowname](vtab.md#xshadowname)
- .dump command → [changes.html#version_3_50_0](changes.md#version_3_50_0) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- .excel → [changes.html#version_3_32_0](changes.md#version_3_32_0) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- .expert command → [changes.html#version_3_22_0](changes.md#version_3_22_0) [cves.html#cvetab](cves.md#cvetab) [releaselog/3_22_0.html](releaselog/3_22_0.md)
- .fullschema → [changes.html#version_3_8_6](changes.md#version_3_8_6) [releaselog/3_8_6.html](releaselog/3_8_6.md)
- .import → [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_32_0](changes.md#version_3_32_0) [changes.html#version_3_34_0](changes.md#version_3_34_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md)
- .import command → [changes.html#version_3_38_0](changes.md#version_3_38_0) [cli.html#safemode](cli.md#safemode) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md)
- .imposter dot-command → [changes.html#version_3_16_0](changes.md#version_3_16_0) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md)
- .load command → [cli.html#safemode](cli.md#safemode)
- .mode → [changes.html#version_3_33_0](changes.md#version_3_33_0) [changes.html#version_3_34_0](changes.md#version_3_34_0) [changes.html#version_3_35_3](changes.md#version_3_35_3) [cli.html#dotrules](cli.md#dotrules) [news.html](news.md) [releaselog/3_33_0.html](releaselog/3_33_0.md) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- .mode command → [changes.html#version_3_53_0](changes.md#version_3_53_0) [cli.html#csv](cli.md#csv) [cli.html#dotrules](cli.md#dotrules) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- .mode quote → [nulinstr.html](nulinstr.md)
- .once → [changes.html#version_3_32_0](changes.md#version_3_32_0) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- .open → [cli.html#dotconn](cli.md#dotconn)
- .open command → [changes.html#version_3_51_0](changes.md#version_3_51_0) [cli.html#safemode](cli.md#safemode) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- .output → [changes.html#version_3_32_0](changes.md#version_3_32_0) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- .parameter command → [changes.html#version_3_28_0](changes.md#version_3_28_0) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- .read → [changes.html#version_3_34_0](changes.md#version_3_34_0) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md)
- .recover dot-command → [changes.html#version_3_30_0](changes.md#version_3_30_0) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md)
- .schema → [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_34_0](changes.md#version_3_34_0) [changes.html#version_3_50_0](changes.md#version_3_50_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- .selftest dot-command → [changes.html#version_3_18_0](changes.md#version_3_18_0) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md)
- .sha3sum dot-command → [changes.html#version_3_18_0](changes.md#version_3_18_0) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md)
- .tables → [changes.html#version_3_20_0](changes.md#version_3_20_0) [climode.html#split](climode.md#split) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- .www dot-command → [changes.html#version_3_47_0](changes.md#version_3_47_0) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md)
- 34to35 → [35to36.html](35to36.md) [oldnews.html](oldnews.md)
- 35 Faster Than The Filesystem → [cpu.html#microopt](cpu.md#microopt) [whyc.html](whyc.md)
- 35to36 → [changes.html#version_3_6_1](changes.md#version_3_6_1) [oldnews.html](oldnews.md) [releaselog/3_6_0.html](releaselog/3_6_0.md)
- about 200 SQL statements per webpage → [whentouse.html#website](whentouse.md#website)
- abs → [arch.html](arch.md) [c3ref/c_deterministic.html#sqlitedeterministic](c3ref/c_deterministic.md#sqlitedeterministic) [c3ref/c_deterministic.html#sqliteinnocuous](c3ref/c_deterministic.md#sqliteinnocuous) [capi3ref.html#sqlitedeterministic](capi3ref.md#sqlitedeterministic) [capi3ref.html#sqliteinnocuous](capi3ref.md#sqliteinnocuous) [deterministic.html](deterministic.md) [lang_corefunc.html](lang_corefunc.md) [lang_corefunc.html#random](lang_corefunc.md#random)
- ACID → [useovernet.html](useovernet.md)
- acos → [lang_mathfunc.html](lang_mathfunc.md)
- acosh → [lang_mathfunc.html](lang_mathfunc.md)
- add column → [lang_altertable.html#otheralter](lang_altertable.md#otheralter)
- ADF → [staleexpridx.html#selfheal](staleexpridx.md#selfheal)
- advantages of WAL-mode → [wal.html#busy](wal.md#busy)
- affinities → [optoverview.html#constprop](optoverview.md#constprop)
- affinity → [faq.html#q3](faq.md#q3) [fileformat2.html##sqltab](fileformat2.md##sqltab) [foreignkeys.html#parentchild](foreignkeys.md#parentchild) [fts3.html#simple_fts_queries](fts3.md#simple_fts_queries) [gencol.html#vgc\*](gencol.md#vgc*) [lang_createtable.html#rowid](lang_createtable.md#rowid) [lang_createtable.html#tablecoldef](lang_createtable.md#tablecoldef) [lang_select.html#distinct](lang_select.md#distinct) [lang_select.html#fromclause](lang_select.md#fromclause) [oldnews.html](oldnews.md) [optoverview.html#flattening](optoverview.md#flattening) [optoverview.html#like_opt](optoverview.md#like_opt) [withoutrowid.html](withoutrowid.md)
- affshort → [appfileformat.html](appfileformat.md) [famous.html](famous.md)
- AFL → [testing.html#fuzzcheck](testing.md#fuzzcheck)
- aggfunc → [lang.html](lang.md) [lang_expr.html#\*funcinexpr](lang_expr.md#*funcinexpr) [lang_select.html#bareagg](lang_select.md#bareagg) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#aggwinfunc](windowfunctions.md#aggwinfunc)
- aggregate functions → [lang_corefunc.html](lang_corefunc.md) [lang_returning.html](lang_returning.md) [lang_with.html#recursivecte](lang_with.md#recursivecte) [windowfunctions.html](windowfunctions.md)
- Aggregate functions → [changes.html#version_3_44_0](changes.md#version_3_44_0) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md)
- Aggregate Functions → [fullsql.html](fullsql.md) [json1.html#jgroupobjectb](json1.md#jgroupobjectb) [windowfunctions.html#aggwinfunc](windowfunctions.md#aggwinfunc)
- aggregate JSON SQL functions → [json1.html#json5](json1.md#json5)
- aggregate SQL functions → [json1.html](json1.md)
- aggregate window functions → [c3ref/create_function.html](c3ref/create_function.md) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#biwinfunc](windowfunctions.md#biwinfunc)
- aggregate-function-invocation → [lang_aggfunc.html](lang_aggfunc.md) [lang_expr.html#\*funcinexpr](lang_expr.md#*funcinexpr)
- ALTER → [foreignkeys.html](foreignkeys.md)
- ALTER TABLE → [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_24_0](changes.md#version_3_24_0) [changes.html#version_3_25_0](changes.md#version_3_25_0) [changes.html#version_3_26_0](changes.md#version_3_26_0) [changes.html#version_3_38_0](changes.md#version_3_38_0) [changes.html#version_3_46_1](changes.md#version_3_46_1) [changes.html#version_3_53_0](changes.md#version_3_53_0) [changes.html#version_3_7_9](changes.md#version_3_7_9) [changes.html#version_3_8_7_1](changes.md#version_3_8_7_1) [compile.html#omit_altertable](compile.md#omit_altertable) [fileformat2.html#ffschema](fileformat2.md#ffschema) [fileformat2.html#schemaformat](fileformat2.md#schemaformat) [fileformat2.html#serialtype](fileformat2.md#serialtype) [foreignkeys.html#fk_actions](foreignkeys.md#fk_actions) [lang.html](lang.md) [lang_analyze.html#statanal](lang_analyze.md#statanal) [lang_createtable.html#notnullconst](lang_createtable.md#notnullconst) [lang_createtrigger.html](lang_createtrigger.md) [lang_naming.html](lang_naming.md) [news.html](news.md) [oldnews.html](oldnews.md) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_24_0.html](releaselog/3_24_0.md) [releaselog/3_25_0.html](releaselog/3_25_0.md) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md) [releaselog/3_26_0.html](releaselog/3_26_0.md) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md) [releaselog/3_46_1.html](releaselog/3_46_1.md) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [releaselog/3_7_9.html](releaselog/3_7_9.md) [releaselog/3_8_7_1.html](releaselog/3_8_7_1.md) [schematab.html](schematab.md) [vtab.html](vtab.md)
- ALTER TABLE ADD COLUMN → [changes.html#version_3_37_0](changes.md#version_3_37_0) [gencol.html#vgc\*](gencol.md#vgc*) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md)
- ALTER TABLE DROP COLUMN → [changes.html#version_3_35_0](changes.md#version_3_35_0) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- ALTER TABLE RENAME → [c3ref/c_dbconfig_defensive.html#sqlitedbconfiglegacyaltertable](c3ref/c_dbconfig_defensive.md#sqlitedbconfiglegacyaltertable) [capi3ref.html#sqlitedbconfiglegacyaltertable](capi3ref.md#sqlitedbconfiglegacyaltertable) [changes.html#version_3_39_1](changes.md#version_3_39_1) [pragma.html#pragma_legacy_alter_table](pragma.md#pragma_legacy_alter_table) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- ALTER TABLE RENAME COLUMN → [changes.html#version_3_27_0](changes.md#version_3_27_0) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- ALTER TABLE RENAME documentation → [c3ref/c_dbconfig_defensive.html#sqlitedbconfiglegacyaltertable](c3ref/c_dbconfig_defensive.md#sqlitedbconfiglegacyaltertable) [capi3ref.html#sqlitedbconfiglegacyaltertable](capi3ref.md#sqlitedbconfiglegacyaltertable)
- alter-table-stmt → [lang_altertable.html](lang_altertable.md)
- alternate-form-1 flag → [changes.html#version_3_50_0](changes.md#version_3_50_0) [printf.html#percentq](printf.md#percentq) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- amalgamation → [amalg-v-canon.html#canon](amalg-v-canon.md#canon) [appfileformat.html](appfileformat.md) [changes.html#version_3_17_0](changes.md#version_3_17_0) [changes.html#version_3_21_0](changes.md#version_3_21_0) [changes.html#version_3_41_0](changes.md#version_3_41_0) [changes.html#version_3_9_0](changes.md#version_3_9_0) [cksumvfs.html](cksumvfs.md) [cli.html#compiling](cli.md#compiling) [compile.html#enable_fts3](compile.md#enable_fts3) [compile.html#enable_fts4](compile.md#enable_fts4) [compile.html#enable_fts5](compile.md#enable_fts5) [compile.html#enable_geopoly](compile.md#enable_geopoly) [compile.html#enable_hidden_columns](compile.md#enable_hidden_columns) [compile.html#enable_ordered_set_aggregates](compile.md#enable_ordered_set_aggregates) [compile.html#enable_update_delete_limit](compile.md#enable_update_delete_limit) [compile.html#omitfeatures](compile.md#omitfeatures) [cpu.html](cpu.md) [cves.html#cvetab](cves.md#cvetab) [dbpage.html](dbpage.md) [download.html#srctree](download.md#srctree) [faq.html#q23](faq.md#q23) [fasterthanfs.html](fasterthanfs.md) [floatingpoint.html#decext](floatingpoint.md#decext) [floatingpoint.html#ieee754ext](floatingpoint.md#ieee754ext) [fts5.html#compiling_and_using_fts5](fts5.md#compiling_and_using_fts5) [geopoly.html](geopoly.md) [getthecode.html](getthecode.md) [howtocompile.html](howtocompile.md) [lemon.html](lemon.md) [malloc.html#memsysx](malloc.md#memsysx) [percentile.html#\*percentilecontfunc](percentile.md#*percentilecontfunc) [privatebranch.html](privatebranch.md) [prosupport.html](prosupport.md) [qmplan.html](qmplan.md) [rbu.html](rbu.md) [releaselog/3_17_0.html](releaselog/3_17_0.md) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md) [rtree.html](rtree.md) [selfcontained.html](selfcontained.md) [sessionintro.html](sessionintro.md) [spellfix1.html](spellfix1.md) [stmt.html](stmt.md) [tclsqlite.html](tclsqlite.md)
- amalgamation tarball → [changes.html#version_3_11_0](changes.md#version_3_11_0) [howtocompile.html#cli](howtocompile.md#cli) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md)
- ambiguous dates → [changes.html#version_3_46_0](changes.md#version_3_46_0) [releaselog/3_46_0.html](releaselog/3_46_0.md) [releaselog/3_46_1.html](releaselog/3_46_1.md)
- American Fuzzy Lop fuzzer → [changes.html#version_3_8_10](changes.md#version_3_8_10) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md)
- analysis_limit → [lang_analyze.html#approx](lang_analyze.md#approx)
- analysis_limit pragma → [changes.html#version_3_46_0](changes.md#version_3_46_0) [releaselog/3_46_0.html](releaselog/3_46_0.md) [releaselog/3_46_1.html](releaselog/3_46_1.md)
- ANALYZE → [appfileformat.html](appfileformat.md) [c3ref/stmt_scanstatus.html](c3ref/stmt_scanstatus.md) [capi3ref.html#sqlite3_stmt_scanstatus](capi3ref.md#sqlite3_stmt_scanstatus) [changes.html#version_3_23_0](changes.md#version_3_23_0) [changes.html#version_3_45_0](changes.md#version_3_45_0) [changes.html#version_3_6_18](changes.md#version_3_6_18) [changes.html#version_3_7_3](changes.md#version_3_7_3) [changes.html#version_3_7_6](changes.md#version_3_7_6) [changes.html#version_3_8_6](changes.md#version_3_8_6) [cli.html#expert](cli.md#expert) [compile.html#enable_stat2](compile.md#enable_stat2) [compile.html#enable_stat3](compile.md#enable_stat3) [compile.html#enable_stat4](compile.md#enable_stat4) [compile.html#omit_analyze](compile.md#omit_analyze) [dbhash.html](dbhash.md) [fileformat2.html#intschema](fileformat2.md#intschema) [fileformat2.html#stat1tab](fileformat2.md#stat1tab) [fileformat2.html#stat3tab](fileformat2.md#stat3tab) [fileformat2.html#stat4tab](fileformat2.md#stat4tab) [isolation.html](isolation.md) [lang.html](lang.md) [news.html](news.md) [oldnews.html](oldnews.md) [optoverview.html#autoindex](optoverview.md#autoindex) [optoverview.html#joins](optoverview.md#joins) [optoverview.html#manctrl](optoverview.md#manctrl) [optoverview.html#multi_index](optoverview.md#multi_index) [optoverview.html#option2](optoverview.md#option2) [optoverview.html#rangequery](optoverview.md#rangequery) [optoverview.html#skipscan](optoverview.md#skipscan) [pragma.html#pragma_analysis_limit](pragma.md#pragma_analysis_limit) [pragma.html#pragma_optimize](pragma.md#pragma_optimize) [queryplanner-ng.html#fossilcasestudy](queryplanner-ng.md#fossilcasestudy) [queryplanner-ng.html#hazards](queryplanner-ng.md#hazards) [queryplanner-ng.html#howtofix](queryplanner-ng.md#howtofix) [queryplanner-ng.html#qpstab](queryplanner-ng.md#qpstab) [queryplanner.html#searching](queryplanner.md#searching) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md) [releaselog/3_6_18.html](releaselog/3_6_18.md) [releaselog/3_7_3.html](releaselog/3_7_3.md) [releaselog/3_7_6.html](releaselog/3_7_6.md) [releaselog/3_8_6.html](releaselog/3_8_6.md)
- analyze-stmt → [lang_analyze.html](lang_analyze.md)
- application file format → [cintro.html](cintro.md) [features.html](features.md) [flextypegood.html](flextypegood.md) [sessionintro.html](sessionintro.md) [undoredo.html](undoredo.md)
- Application File Format → [about.html](about.md) [affcase1.html#smaller](affcase1.md#smaller) [onefile.html](onefile.md)
- application file-format → [aff_short.html](aff_short.md) [changes.html#version_3_7_17](changes.md#version_3_7_17) [features.html](features.md) [fileformat2.html#appid](fileformat2.md#appid) [pragma.html#pragma_application_id](pragma.md#pragma_application_id) [releaselog/3_7_17.html](releaselog/3_7_17.md) [wal.html#advantages](wal.md#advantages) [whentouse.html#appfileformat](whentouse.md#appfileformat)
- Application ID → [appfileformat.html](appfileformat.md) [changes.html#version_3_7_17](changes.md#version_3_7_17) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- application-defined SQL function → [c3ref/c_deterministic.html#sqlitedirectonly](c3ref/c_deterministic.md#sqlitedirectonly) [c3ref/result_blob.html](c3ref/result_blob.md) [c3ref/result_subtype.html](c3ref/result_subtype.md) [c3ref/value_subtype.html](c3ref/value_subtype.md) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [capi3ref.html#sqlite3_result_subtype](capi3ref.md#sqlite3_result_subtype) [capi3ref.html#sqlite3_value_subtype](capi3ref.md#sqlite3_value_subtype) [capi3ref.html#sqlitedirectonly](capi3ref.md#sqlitedirectonly) [fts5.html#custom_auxiliary_functions](fts5.md#custom_auxiliary_functions) [lang_expr.html#regexp](lang_expr.md#regexp) [staleexpridx.html](staleexpridx.md) [swarmvtab.html#the_missing_callback](swarmvtab.md#the_missing_callback) [swarmvtab.html#the_openclose_callback](swarmvtab.md#the_openclose_callback)
- application-defined SQL functions → [c3ref/c_any.html#sqliteany](c3ref/c_any.md#sqliteany) [c3ref/c_deterministic.html#sqlitedirectonly](c3ref/c_deterministic.md#sqlitedirectonly) [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/context.html](c3ref/context.md) [c3ref/stmt_readonly.html](c3ref/stmt_readonly.md) [c3ref/value.html](c3ref/value.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [capi3ref.html#sqlite3_stmt_readonly](capi3ref.md#sqlite3_stmt_readonly) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [capi3ref.html#sqliteany](capi3ref.md#sqliteany) [capi3ref.html#sqlitedirectonly](capi3ref.md#sqlitedirectonly) [changes.html#version_3_12_0](changes.md#version_3_12_0) [changes.html#version_3_30_0](changes.md#version_3_30_0) [changes.html#version_3_31_0](changes.md#version_3_31_0) [changes.html#version_3_42_0](changes.md#version_3_42_0) [changes.html#version_3_45_0](changes.md#version_3_45_0) [changes.html#version_3_8_0](changes.md#version_3_8_0) [cli.html#dotload](cli.md#dotload) [cli.html#fileio](cli.md#fileio) [compile.html#strict_subtype](compile.md#strict_subtype) [compile.html#trusted_schema](compile.md#trusted_schema) [deterministic.html#dtexception](deterministic.md#dtexception) [expridx.html](expridx.md) [fullsql.html](fullsql.md) [loadext.html](loadext.md) [loadext.html#write](loadext.md#write) [news.html](news.md) [optoverview.html#leftjoinreduction](optoverview.md#leftjoinreduction) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [releaselog/3_42_0.html](releaselog/3_42_0.md) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md) [rescode.html#internal](rescode.md#internal)
- application-defined window functions → [appfunc.html](appfunc.md)
- application_id pragma → [aff_short.html](aff_short.md) [pragma.html#pragma_schema_version](pragma.md#pragma_schema_version) [pragma.html#pragma_user_version](pragma.md#pragma_user_version)
- appreciate the freedom → [stricttables.html](stricttables.md)
- Appropriate Uses For SQLite → [quirks.html](quirks.md)
- approximate ANALYZE → [changes.html#version_3_32_0](changes.md#version_3_32_0) [news.html](news.md) [pragma.html#pragma_analysis_limit](pragma.md#pragma_analysis_limit) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- Approximate ANALYZE For Large Databases → [lang_analyze.html#pragopt](lang_analyze.md#pragopt)
- asin → [lang_mathfunc.html](lang_mathfunc.md)
- asinh → [lang_mathfunc.html](lang_mathfunc.md)
- atan → [lang_mathfunc.html](lang_mathfunc.md)
- atan2 → [lang_mathfunc.html](lang_mathfunc.md)
- atanh → [lang_mathfunc.html](lang_mathfunc.md)
- Atomic Commit → [howitworks.html](howitworks.md) [lockingv3.html#how_to_corrupt](lockingv3.md#how_to_corrupt)
- atomic commit → [affcase1.html#smaller](affcase1.md#smaller) [appfileformat.html](appfileformat.md) [wal.html](wal.md)
- ATTACH → [bytecodevtab.html#nexec](bytecodevtab.md#nexec) [c3ref/backup_finish.html#sqlite3backupinit](c3ref/backup_finish.md#sqlite3backupinit) [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/c_config_covering_index_scan.html#sqliteconfiguri](c3ref/c_config_covering_index_scan.md#sqliteconfiguri) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigenableattachwrite](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenableattachwrite) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigenabletrigger](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenabletrigger) [c3ref/c_dbstatus_options.html#sqlitedbstatusschemaused](c3ref/c_dbstatus_options.md#sqlitedbstatusschemaused) [c3ref/c_limit_attached.html#sqlitelimitattached](c3ref/c_limit_attached.md#sqlitelimitattached) [c3ref/db_name.html](c3ref/db_name.md) [c3ref/file_control.html](c3ref/file_control.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/stmt_readonly.html](c3ref/stmt_readonly.md) [c3ref/wal_hook.html](c3ref/wal_hook.md) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_db_name](capi3ref.md#sqlite3_db_name) [capi3ref.html#sqlite3_file_control](capi3ref.md#sqlite3_file_control) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite) [capi3ref.html#sqlite3_stmt_readonly](capi3ref.md#sqlite3_stmt_readonly) [capi3ref.html#sqlite3_wal_hook](capi3ref.md#sqlite3_wal_hook) [capi3ref.html#sqlite3backupinit](capi3ref.md#sqlite3backupinit) [capi3ref.html#sqliteconfiguri](capi3ref.md#sqliteconfiguri) [capi3ref.html#sqlitedbconfigenableattachwrite](capi3ref.md#sqlitedbconfigenableattachwrite) [capi3ref.html#sqlitedbconfigenabletrigger](capi3ref.md#sqlitedbconfigenabletrigger) [capi3ref.html#sqlitedbstatusschemaused](capi3ref.md#sqlitedbstatusschemaused) [capi3ref.html#sqlitelimitattached](capi3ref.md#sqlitelimitattached) [changes.html#version_3_15_0](changes.md#version_3_15_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_21_0](changes.md#version_3_21_0) [changes.html#version_3_5_6](changes.md#version_3_5_6) [changes.html#version_3_8_3](changes.md#version_3_8_3) [cintro.html](cintro.md) [cli.html#safemode](cli.md#safemode) [compile.html#omit_attach](compile.md#omit_attach) [dbpage.html](dbpage.md) [fts3.html#\_external_content_fts4_tables\_](fts3.md#_external_content_fts4_tables_) [inmemorydb.html](inmemorydb.md) [inmemorydb.html#temp_db](inmemorydb.md#temp_db) [lang_createtrigger.html](lang_createtrigger.md) [lang_detach.html](lang_detach.md) [lang_naming.html](lang_naming.md) [lang_vacuum.html](lang_vacuum.md) [lockingv3.html#rollback](lockingv3.md#rollback) [pragma.html#pragfunc](pragma.md#pragfunc) [pragma.html#pragma_encoding](pragma.md#pragma_encoding) [pragma.html#pragma_locking_mode](pragma.md#pragma_locking_mode) [pragma.html#pragma_mmap_size](pragma.md#pragma_mmap_size) [pragma.html#pragma_secure_delete](pragma.md#pragma_secure_delete) [pragma.html#syntax](pragma.md#syntax) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_5_6.html](releaselog/3_5_6.md) [releaselog/3_8_3.html](releaselog/3_8_3.md) [sharedcache.html#dontuse](sharedcache.md#dontuse) [shortnames.html](shortnames.md) [tclsqlite.html#backup](tclsqlite.md#backup) [tclsqlite.html#restore](tclsqlite.md#restore) [tempfiles.html#superjrnl](tempfiles.md#superjrnl) [tempfiles.html#tempdb](tempfiles.md#tempdb) [unionvtab.html](unionvtab.md) [uri.html](uri.md) [vfs.html](vfs.md) [vtab.html#xcreate](vtab.md#xcreate) [wal.html#advantages](wal.md#advantages)
- ATTACH DATABASE → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigenableattachcreate](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenableattachcreate) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigenableattachwrite](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenableattachwrite) [capi3ref.html#sqlitedbconfigenableattachcreate](capi3ref.md#sqlitedbconfigenableattachcreate) [capi3ref.html#sqlitedbconfigenableattachwrite](capi3ref.md#sqlitedbconfigenableattachwrite) [fullsql.html](fullsql.md) [lang.html](lang.md) [lang_createtable.html](lang_createtable.md)
- attach-stmt → [lang_attach.html](lang_attach.md)
- attached → [bytecodevtab.html#nexec](bytecodevtab.md#nexec) [c3ref/db_cacheflush.html](c3ref/db_cacheflush.md) [c3ref/wal_checkpoint_v2.html](c3ref/wal_checkpoint_v2.md) [capi3ref.html#sqlite3_db_cacheflush](capi3ref.md#sqlite3_db_cacheflush) [capi3ref.html#sqlite3_wal_checkpoint_v2](capi3ref.md#sqlite3_wal_checkpoint_v2) [cli.html#dschema](cli.md#dschema) [cli.html#dtables](cli.md#dtables)
- authorizer callback → [changes.html#version_3_19_0](changes.md#version_3_19_0) [lang_explain.html](lang_explain.md) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md)
- auto modifier → [changes.html#version_3_38_0](changes.md#version_3_38_0) [lang_datefunc.html](lang_datefunc.md) [lang_datefunc.html#tmval](lang_datefunc.md#tmval) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md)
- auto_vacuum → [changes.html#version_3_18_1](changes.md#version_3_18_1) [changes.html#version_3_19_3](changes.md#version_3_19_3) [compile.html#default_autovacuum](compile.md#default_autovacuum) [compile.html#omit_autovacuum](compile.md#omit_autovacuum) [fileformat2.html#ovflpgs](fileformat2.md#ovflpgs) [fileformat2.html#schemaformat](fileformat2.md#schemaformat) [lang_vacuum.html](lang_vacuum.md) [lang_vacuum.html#howvacuumworks](lang_vacuum.md#howvacuumworks) [mmap.html](mmap.md) [news.html](news.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md)
- autocommit mode → [c3ref/snapshot_get.html](c3ref/snapshot_get.md) [c3ref/snapshot_open.html](c3ref/snapshot_open.md) [capi3ref.html#sqlite3_snapshot_get](capi3ref.md#sqlite3_snapshot_get) [capi3ref.html#sqlite3_snapshot_open](capi3ref.md#sqlite3_snapshot_open) [foreignkeys.html#fk_enable](foreignkeys.md#fk_enable)
- AUTOINCREMENT → [c3ref/table_column_metadata.html](c3ref/table_column_metadata.md) [capi3ref.html#sqlite3_table_column_metadata](capi3ref.md#sqlite3_table_column_metadata) [changes.html#version_3_15_0](changes.md#version_3_15_0) [changes.html#version_3_23_0](changes.md#version_3_23_0) [changes.html#version_3_24_0](changes.md#version_3_24_0) [compile.html#omit_autoincrement](compile.md#omit_autoincrement) [faq.html#q1](faq.md#q1) [fileformat2.html#intschema](fileformat2.md#intschema) [fileformat2.html#seqtab](fileformat2.md#seqtab) [quirks.html#dblquote](quirks.md#dblquote) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_24_0.html](releaselog/3_24_0.md) [rescode.html#corrupt_sequence](rescode.md#corrupt_sequence) [stricttables.html](stricttables.md) [withoutrowid.html](withoutrowid.md)
- automated undo/redo stack → [aff_short.html](aff_short.md) [affcase1.html#smaller](affcase1.md#smaller) [appfileformat.html](appfileformat.md)
- automatic indexes → [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_24_0](changes.md#version_3_24_0) [changes.html#version_3_47_0](changes.md#version_3_47_0) [profile.html](profile.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_24_0.html](releaselog/3_24_0.md) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md) [stmt.html](stmt.md)
- Automatic indexing → [pragma.html#pragma_automatic_index](pragma.md#pragma_automatic_index)
- automatic indexing → [changes.html#version_3_8_11](changes.md#version_3_8_11) [changes.html#version_3_8_8](changes.md#version_3_8_8) [changes.html#version_3_9_2](changes.md#version_3_9_2) [compile.html#omit_automatic_index](compile.md#omit_automatic_index) [eqp.html](eqp.md) [pragma.html#pragma_automatic_index](pragma.md#pragma_automatic_index) [queryplanner-ng.html#qpstab](queryplanner-ng.md#qpstab) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md) [rescode.html#warning_autoindex](rescode.md#warning_autoindex)
- automatic_index pragma → [optoverview.html#autoindex](optoverview.md#autoindex)
- Automatically Running ANALYZE → [lang_analyze.html#pragopt](lang_analyze.md#pragopt)
- automerge command → [changes.html#version_3_8_5](changes.md#version_3_8_5) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- auxiliary columns → [rtree.html#xshadow](rtree.md#xshadow)
- auxiliary columns in r-tree tables → [changes.html#version_3_24_0](changes.md#version_3_24_0) [releaselog/3_24_0.html](releaselog/3_24_0.md)
- auxiliary function mapping → [fts5.html#the_rank_configuration_option](fts5.md#the_rank_configuration_option)
- avg → [changes.html#version_3_43_1](changes.md#version_3_43_1) [lang_aggfunc.html#aggfunclist](lang_aggfunc.md#aggfunclist) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md)
- B-tree → [imposter.html](imposter.md) [pragma.html#pragma_secure_delete](pragma.md#pragma_secure_delete) [rowidtable.html](rowidtable.md) [vtablist.html](vtablist.md)
- B-Trees → [withoutrowid.html#wtu](withoutrowid.md#wtu)
- backup API → [aff_short.html](aff_short.md) [changes.html#version_3_7_15](changes.md#version_3_7_15) [dbhash.html](dbhash.md) [howtocorrupt.html#stalefd](howtocorrupt.md#stalefd) [lang_vacuum.html#vacuuminto](lang_vacuum.md#vacuuminto) [releaselog/3_7_15.html](releaselog/3_7_15.md) [wal.html#advantages](wal.md#advantages) [whentouse.html#appfileformat](whentouse.md#appfileformat)
- base64 → [base85.html](base85.md) [cli.html#miscfeatures](cli.md#miscfeatures)
- base85 → [base64.html](base64.md) [cli.html#miscfeatures](cli.md#miscfeatures)
- bcvtab → [vtablist.html](vtablist.md)
- BEGIN → [c3ref/get_autocommit.html](c3ref/get_autocommit.md) [c3ref/stmt_readonly.html](c3ref/stmt_readonly.md) [capi3ref.html#sqlite3_get_autocommit](capi3ref.md#sqlite3_get_autocommit) [capi3ref.html#sqlite3_stmt_readonly](capi3ref.md#sqlite3_stmt_readonly) [faq.html#q19](faq.md#q19) [foreignkeys.html#fk_enable](foreignkeys.md#fk_enable) [fts3.html#\*fts4mergecmd](fts3.md#*fts4mergecmd) [fullsql.html](fullsql.md) [isolation.html](isolation.md) [lang_savepoint.html](lang_savepoint.md) [pragma.html#pragma_foreign_keys](pragma.md#pragma_foreign_keys) [rescode.html#busy](rescode.md#busy)
- BEGIN EXCLUSIVE → [changes.html#version_3_34_0](changes.md#version_3_34_0) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md)
- BEGIN IMMEDIATE → [changes.html#version_3_34_0](changes.md#version_3_34_0) [isolation.html](isolation.md) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md) [rescode.html#busy](rescode.md#busy)
- begin-stmt → [lang_transaction.html](lang_transaction.md)
- BETWEEN → [optoverview.html#like_opt](optoverview.md#like_opt)
- BINARY → [lang_corefunc.html#replace](lang_corefunc.md#replace) [lang_createtable.html#collateclause](lang_createtable.md#collateclause) [lang_select.html#nullslast](lang_select.md#nullslast) [rbu.html#fts4_tables](rbu.md#fts4_tables)
- bind_fallback method → [changes.html#version_3_28_0](changes.md#version_3_28_0) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- BLOB handle → [c3ref/blob_bytes.html](c3ref/blob_bytes.md) [c3ref/blob_close.html](c3ref/blob_close.md) [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/blob_read.html](c3ref/blob_read.md) [c3ref/blob_reopen.html](c3ref/blob_reopen.md) [c3ref/blob_write.html](c3ref/blob_write.md) [capi3ref.html#sqlite3_blob_bytes](capi3ref.md#sqlite3_blob_bytes) [capi3ref.html#sqlite3_blob_close](capi3ref.md#sqlite3_blob_close) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_blob_read](capi3ref.md#sqlite3_blob_read) [capi3ref.html#sqlite3_blob_reopen](capi3ref.md#sqlite3_blob_reopen) [capi3ref.html#sqlite3_blob_write](capi3ref.md#sqlite3_blob_write)
- BLOB handles → [c3ref/close.html](c3ref/close.md) [capi3ref.html#sqlite3_close](capi3ref.md#sqlite3_close)
- BLOB I/O performance → [affcase1.html#smaller](affcase1.md#smaller)
- block sorting → [changes.html#version_3_10_1](changes.md#version_3_10_1) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md)
- books about SQLite → [doclist.html](doclist.md) [keyword_index.html](keyword_index.md) [sitemap.html](sitemap.md)
- boolean expression → [lang_delete.html](lang_delete.md) [lang_select.html#fromclause](lang_select.md#fromclause) [lang_select.html#resultset](lang_select.md#resultset) [lang_select.html#whereclause](lang_select.md#whereclause) [lang_update.html](lang_update.md)
- bound parameter → [c3ref/profile.html](c3ref/profile.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html#sqlite3_profile](capi3ref.md#sqlite3_profile) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [changes.html#version_3_28_0](changes.md#version_3_28_0) [oldnews.html](oldnews.md) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- bound parameters → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigenableqpsg](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenableqpsg) [c3ref/c_stmtstatus_counter.html#sqlitestmtstatusreprepare](c3ref/c_stmtstatus_counter.md#sqlitestmtstatusreprepare) [c3ref/expanded_sql.html](c3ref/expanded_sql.md) [capi3ref.html#sqlite3_expanded_sql](capi3ref.md#sqlite3_expanded_sql) [capi3ref.html#sqlitedbconfigenableqpsg](capi3ref.md#sqlitedbconfigenableqpsg) [capi3ref.html#sqlitestmtstatusreprepare](capi3ref.md#sqlitestmtstatusreprepare) [changes.html#version_3_28_0](changes.md#version_3_28_0) [changes.html#version_3_6_21](changes.md#version_3_6_21) [cli.html#param](cli.md#param) [fts3.html#f3tknzr](fts3.md#f3tknzr) [lang_createtable.html#dfltval](lang_createtable.md#dfltval) [partialindex.html](partialindex.md) [releaselog/3_28_0.html](releaselog/3_28_0.md) [releaselog/3_6_21.html](releaselog/3_6_21.md)
- built-in memory allocators → [c3ref/mem_methods.html](c3ref/mem_methods.md) [capi3ref.html#sqlite3_mem_methods](capi3ref.md#sqlite3_mem_methods)
- built-in printf → [arch.html](arch.md) [c3ref/mprintf.html](c3ref/mprintf.md) [c3ref/str_append.html](c3ref/str_append.md) [capi3ref.html#sqlite3_mprintf](capi3ref.md#sqlite3_mprintf) [capi3ref.html#sqlite3_str_append](capi3ref.md#sqlite3_str_append) [changes.html#version_3_23_0](changes.md#version_3_23_0) [changes.html#version_3_42_0](changes.md#version_3_42_0) [changes.html#version_3_50_0](changes.md#version_3_50_0) [changes.html#version_3_51_0](changes.md#version_3_51_0) [compile.html#printf_precision_limit](compile.md#printf_precision_limit) [lang_corefunc.html#format](lang_corefunc.md#format) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_42_0.html](releaselog/3_42_0.md) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- built-in SQL math functions → [changes.html#version_3_35_0](changes.md#version_3_35_0) [compile.html#enable_math_functions](compile.md#enable_math_functions) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- built-in window functions → [windowfunctions.html](windowfunctions.md)
- busy-handler callback → [c3ref/wal_checkpoint_v2.html](c3ref/wal_checkpoint_v2.md) [capi3ref.html#sqlite3_wal_checkpoint_v2](capi3ref.md#sqlite3_wal_checkpoint_v2)
- busy_timeout pragma → [changes.html#version_3_7_15](changes.md#version_3_7_15) [releaselog/3_7_15.html](releaselog/3_7_15.md) [rescode.html#busy](rescode.md#busy)
- byte-order determination rules → [c3ref/result_blob.html](c3ref/result_blob.md) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob)
- bytecode → [arch.html](arch.md) [bytecodevtab.html](bytecodevtab.md) [c3ref/vtab_distinct.html](c3ref/vtab_distinct.md) [c3ref/vtab_in.html](c3ref/vtab_in.md) [capi3ref.html#sqlite3_vtab_distinct](capi3ref.md#sqlite3_vtab_distinct) [capi3ref.html#sqlite3_vtab_in](capi3ref.md#sqlite3_vtab_in) [changes.html#version_3_37_2](changes.md#version_3_37_2) [debugging.html](debugging.md) [lang_corefunc.html#iif](lang_corefunc.md#iif) [releaselog/3_37_2.html](releaselog/3_37_2.md) [rowvalue.html#rvinop](rowvalue.md#rvinop) [vtab.html#colUsed](vtab.md#colUsed) [whybytecode.html](whybytecode.md)
- bytecode and tables_used virtual tables → [compile.html#enable_bytecode_vtab](compile.md#enable_bytecode_vtab)
- bytecode engine → [changes.html#version_3_35_3](changes.md#version_3_35_3) [changes.html#version_3_45_1](changes.md#version_3_45_1) [compile.html#rcmd](compile.md#rcmd) [howitworks.html](howitworks.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md) [stmt.html](stmt.md)
- bytecode virtual table → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigstmtscanstatus](c3ref/c_dbconfig_defensive.md#sqlitedbconfigstmtscanstatus) [c3ref/stmt_scanstatus.html](c3ref/stmt_scanstatus.md) [capi3ref.html#sqlite3_stmt_scanstatus](capi3ref.md#sqlite3_stmt_scanstatus) [capi3ref.html#sqlitedbconfigstmtscanstatus](capi3ref.md#sqlitedbconfigstmtscanstatus) [changes.html#version_3_32_0](changes.md#version_3_32_0) [compile.html#enable_stmt_scanstatus](compile.md#enable_stmt_scanstatus) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- C-language Interface → [arch.html](arch.md) [rescode.html](rescode.md)
- cache_size → [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_7_6_3](changes.md#version_3_7_6_3) [compile.html#sorter_pmasz](compile.md#sorter_pmasz) [oldnews.html](oldnews.md) [pgszchng2016.html](pgszchng2016.md) [pragma.html#pragma_default_cache_size](pragma.md#pragma_default_cache_size) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_7_6_3.html](releaselog/3_7_6_3.md)
- cache_size pragma → [malloc.html#nofrag](malloc.md#nofrag) [pgszchng2016.html](pgszchng2016.md)
- cache_spill pragma → [changes.html#version_3_8_0](changes.md#version_3_8_0) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md)
- canonical source code → [changes.html#version_3_43_0](changes.md#version_3_43_0) [changes.html#version_3_49_0](changes.md#version_3_49_0) [news.html](news.md) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md)
- canonical sources → [changes.html#version_3_48_0](changes.md#version_3_48_0) [howtocompile.html](howtocompile.md) [howtocompile.html#cli](howtocompile.md#cli) [releaselog/3_48_0.html](releaselog/3_48_0.md) [tclsqlite.html](tclsqlite.md)
- capi3ref → [cintro.html](cintro.md) [quickstart.html](quickstart.md)
- capi3ref_funclist → [cintro.html](cintro.md)
- carray → [bindptr.html](bindptr.md) [bindptr.html#ptrtyp](bindptr.md#ptrtyp) [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_51_0](changes.md#version_3_51_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md) [vtablist.html](vtablist.md)
- carray extension → [compile.html#enable_carray](compile.md#enable_carray)
- carray table-valued function → [bindptr.html#ptrtyp](bindptr.md#ptrtyp) [c3ref/c_carray_blob.html](c3ref/c_carray_blob.md) [c3ref/carray_bind.html](c3ref/carray_bind.md) [capi3ref.html#SQLITE_CARRAY_BLOB](capi3ref.md#SQLITE_CARRAY_BLOB) [capi3ref.html#sqlite3_carray_bind](capi3ref.md#sqlite3_carray_bind) [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_34_0](changes.md#version_3_34_0) [changes.html#version_3_41_0](changes.md#version_3_41_0) [loadext.html#write](loadext.md#write) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- CASE expression → [lang_corefunc.html#iif](lang_corefunc.md#iif)
- case_sensitive_like → [optoverview.html#like_opt](optoverview.md#like_opt)
- case_sensitive_like pragma → [compile.html#case_sensitive_like](compile.md#case_sensitive_like) [lang_expr.html#like](lang_expr.md#like)
- CAST → [c3ref/column_blob.html](c3ref/column_blob.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [changes.html#version_3_8_7](changes.md#version_3_8_7) [datatype3.html#compaff](datatype3.md#compaff) [nulinstr.html](nulinstr.md) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- cast → [lang_expr.html#collateop](lang_expr.md#collateop) [oldnews.html](oldnews.md)
- CAST expression → [changes.html#version_3_7_16_1](changes.md#version_3_7_16_1) [changes.html#version_3_8_2](changes.md#version_3_8_2) [datatype3.html#affinity](datatype3.md#affinity) [lang_createtable.html#ckconst](lang_createtable.md#ckconst) [lang_expr.html#booleanexpr](lang_expr.md#booleanexpr) [lang_expr.html#hexint](lang_expr.md#hexint) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md) [releaselog/3_8_2.html](releaselog/3_8_2.md)
- CAST operator → [floatingpoint.html#\*rounding](floatingpoint.md#*rounding)
- categorical listing of SQLite documents → [doclist.html](doclist.md) [keyword_index.html](keyword_index.md) [sitemap.html](sitemap.md)
- ceil → [lang_mathfunc.html](lang_mathfunc.md)
- ceiling → [lang_mathfunc.html#trunc](lang_mathfunc.md#trunc)
- cfgerrors → [pragma.html#pragma_journal_mode](pragma.md#pragma_journal_mode) [pragma.html#pragma_schema_version](pragma.md#pragma_schema_version) [pragma.html#pragma_synchronous](pragma.md#pragma_synchronous) [pragma.html#pragma_writable_schema](pragma.md#pragma_writable_schema) [schematab.html](schematab.md)
- change counter → [fileformat2.html#filesize](fileformat2.md#filesize) [fileformat2.html#validfor](fileformat2.md#validfor) [rsync.html#intro](rsync.md#intro)
- changes → [deterministic.html](deterministic.md) [lang_corefunc.html](lang_corefunc.md)
- changes SQL function → [c3ref/changes.html](c3ref/changes.md) [c3ref/total_changes.html](c3ref/total_changes.md) [capi3ref.html#sqlite3_changes](capi3ref.md#sqlite3_changes) [capi3ref.html#sqlite3_total_changes](capi3ref.md#sqlite3_total_changes)
- changeset → [changes.html#version_3_23_0](changes.md#version_3_23_0) [cves.html#cvetab](cves.md#cvetab) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [session.html#sqlite3_changeset_iter](session.md#sqlite3_changeset_iter) [session/changeset_iter.html](session/changeset_iter.md)
- changesets → [session.html#sqlite3_changegroup](session.md#sqlite3_changegroup) [session/changegroup.html](session/changegroup.md)
- char → [changes.html#version_3_19_0](changes.md#version_3_19_0) [changes.html#version_3_7_16](changes.md#version_3_7_16) [changes.html#version_3_8_4](changes.md#version_3_8_4) [lang_corefunc.html](lang_corefunc.md) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md) [releaselog/3_7_16.html](releaselog/3_7_16.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md) [releaselog/3_8_4.html](releaselog/3_8_4.md) [releaselog/3_8_4_1.html](releaselog/3_8_4_1.md) [releaselog/3_8_4_2.html](releaselog/3_8_4_2.md) [releaselog/3_8_4_3.html](releaselog/3_8_4_3.md)
- CHECK → [changes.html#version_3_7_12](changes.md#version_3_7_12) [conflict.html](conflict.md) [fullsql.html](fullsql.md) [lang_conflict.html](lang_conflict.md) [releaselog/3_7_12.html](releaselog/3_7_12.md)
- CHECK constraint → [changes.html#version_3_34_0](changes.md#version_3_34_0) [changes.html#version_3_37_0](changes.md#version_3_37_0) [changes.html#version_3_7_15](changes.md#version_3_7_15) [deterministic.html](deterministic.md) [lang_altertable.html#altertabaddcol](lang_altertable.md#altertabaddcol) [lang_altertable.html#altertabdropcol](lang_altertable.md#altertabdropcol) [lang_conflict.html](lang_conflict.md) [oldnews.html](oldnews.md) [pragma.html#pragma_case_sensitive_like](pragma.md#pragma_case_sensitive_like) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md) [releaselog/3_7_15.html](releaselog/3_7_15.md) [rescode.html#constraint_check](rescode.md#constraint_check)
- CHECK constraints → [c3ref/c_deterministic.html#sqlitedirectonly](c3ref/c_deterministic.md#sqlitedirectonly) [c3ref/c_deterministic.html#sqliteinnocuous](c3ref/c_deterministic.md#sqliteinnocuous) [capi3ref.html#sqlitedirectonly](capi3ref.md#sqlitedirectonly) [capi3ref.html#sqliteinnocuous](capi3ref.md#sqliteinnocuous) [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_32_0](changes.md#version_3_32_0) [pragma.html#pragma_trusted_schema](pragma.md#pragma_trusted_schema) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md) [stricttables.html](stricttables.md)
- checklist → [qmplan.html](qmplan.md)
- checkpoint → [c3ref/c_dbconfig_defensive.html#sqlitedbconfignockptonclose](c3ref/c_dbconfig_defensive.md#sqlitedbconfignockptonclose) [c3ref/snapshot_open.html](c3ref/snapshot_open.md) [c3ref/wal_autocheckpoint.html](c3ref/wal_autocheckpoint.md) [c3ref/wal_hook.html](c3ref/wal_hook.md) [capi3ref.html#sqlite3_snapshot_open](capi3ref.md#sqlite3_snapshot_open) [capi3ref.html#sqlite3_wal_autocheckpoint](capi3ref.md#sqlite3_wal_autocheckpoint) [capi3ref.html#sqlite3_wal_hook](capi3ref.md#sqlite3_wal_hook) [capi3ref.html#sqlitedbconfignockptonclose](capi3ref.md#sqlitedbconfignockptonclose) [changes.html#version_3_16_0](changes.md#version_3_16_0) [fasterthanfs.html](fasterthanfs.md) [fileformat2.html#walcksm](fileformat2.md#walcksm) [howtocorrupt.html#fork](howtocorrupt.md#fork) [oldnews.html](oldnews.md) [pragma.html#pragma_checkpoint_fullfsync](pragma.md#pragma_checkpoint_fullfsync) [pragma.html#pragma_journal_size_limit](pragma.md#pragma_journal_size_limit) [pragma.html#pragma_query_only](pragma.md#pragma_query_only) [pragma.html#pragma_synchronous](pragma.md#pragma_synchronous) [pragma.html#pragma_wal_checkpoint](pragma.md#pragma_wal_checkpoint) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [tclsqlite.html#wal_hook](tclsqlite.md#wal_hook) [wal.html#walresetbug](wal.md#walresetbug) [walformat.html#locks](walformat.md#locks) [walformat.html#shm](walformat.md#shm)
- checkpoint mode → [c3ref/wal_checkpoint_v2.html](c3ref/wal_checkpoint_v2.md) [capi3ref.html#sqlite3_wal_checkpoint_v2](capi3ref.md#sqlite3_wal_checkpoint_v2)
- checkpoint_fullfsync → [pragma.html#pragma_fullfsync](pragma.md#pragma_fullfsync) [pragma.html#pragma_synchronous](pragma.md#pragma_synchronous)
- checkpointing → [c3ref/wal_checkpoint.html](c3ref/wal_checkpoint.md) [capi3ref.html#sqlite3_wal_checkpoint](capi3ref.md#sqlite3_wal_checkpoint) [compile.html#default_wal_autocheckpoint](compile.md#default_wal_autocheckpoint) [pragma.html#pragma_wal_autocheckpoint](pragma.md#pragma_wal_autocheckpoint) [wal.html#advantages](wal.md#advantages)
- checksum VFS shim → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlcksmfile](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlcksmfile) [capi3ref.html#sqlitefcntlcksmfile](capi3ref.md#sqlitefcntlcksmfile) [changes.html#version_3_32_0](changes.md#version_3_32_0) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md) [rescode.html#ioerr_data](rescode.md#ioerr_data)
- child key → [c3ref/blob_open.html](c3ref/blob_open.md) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open)
- chronology → [changes.html](changes.md) [getthecode.html](getthecode.md) [qmplan.html](qmplan.md) [releaselog/3_0_0.html](releaselog/3_0_0.md) [releaselog/3_0_1.html](releaselog/3_0_1.md) [releaselog/3_0_2.html](releaselog/3_0_2.md) [releaselog/3_0_3.html](releaselog/3_0_3.md) [releaselog/3_0_4.html](releaselog/3_0_4.md) [releaselog/3_0_5.html](releaselog/3_0_5.md) [releaselog/3_0_6.html](releaselog/3_0_6.md) [releaselog/3_0_7.html](releaselog/3_0_7.md) [releaselog/3_0_8.html](releaselog/3_0_8.md) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_17_0.html](releaselog/3_17_0.md) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md) [releaselog/3_1_0.html](releaselog/3_1_0.md) [releaselog/3_1_1.html](releaselog/3_1_1.md) [releaselog/3_1_2.html](releaselog/3_1_2.md) [releaselog/3_1_3.html](releaselog/3_1_3.md) [releaselog/3_1_4.html](releaselog/3_1_4.md) [releaselog/3_1_5.html](releaselog/3_1_5.md) [releaselog/3_1_6.html](releaselog/3_1_6.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_22_0.html](releaselog/3_22_0.md) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_24_0.html](releaselog/3_24_0.md) [releaselog/3_25_0.html](releaselog/3_25_0.md) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md) [releaselog/3_26_0.html](releaselog/3_26_0.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_28_0.html](releaselog/3_28_0.md) [releaselog/3_29_0.html](releaselog/3_29_0.md) [releaselog/3_2_0.html](releaselog/3_2_0.md) [releaselog/3_2_1.html](releaselog/3_2_1.md) [releaselog/3_2_2.html](releaselog/3_2_2.md) [releaselog/3_2_3.html](releaselog/3_2_3.md) [releaselog/3_2_4.html](releaselog/3_2_4.md) [releaselog/3_2_5.html](releaselog/3_2_5.md) [releaselog/3_2_6.html](releaselog/3_2_6.md) [releaselog/3_2_7.html](releaselog/3_2_7.md) [releaselog/3_2_8.html](releaselog/3_2_8.md) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md) [releaselog/3_33_0.html](releaselog/3_33_0.md) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [releaselog/3_36_0.html](releaselog/3_36_0.md) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md) [releaselog/3_39_0.html](releaselog/3_39_0.md) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md) [releaselog/3_3_0.html](releaselog/3_3_0.md) [releaselog/3_3_1.html](releaselog/3_3_1.md) [releaselog/3_3_10.html](releaselog/3_3_10.md) [releaselog/3_3_11.html](releaselog/3_3_11.md) [releaselog/3_3_12.html](releaselog/3_3_12.md) [releaselog/3_3_13.html](releaselog/3_3_13.md) [releaselog/3_3_14.html](releaselog/3_3_14.md) [releaselog/3_3_15.html](releaselog/3_3_15.md) [releaselog/3_3_16.html](releaselog/3_3_16.md) [releaselog/3_3_17.html](releaselog/3_3_17.md) [releaselog/3_3_2.html](releaselog/3_3_2.md) [releaselog/3_3_3.html](releaselog/3_3_3.md) [releaselog/3_3_4.html](releaselog/3_3_4.md) [releaselog/3_3_5.html](releaselog/3_3_5.md) [releaselog/3_3_6.html](releaselog/3_3_6.md) [releaselog/3_3_7.html](releaselog/3_3_7.md) [releaselog/3_3_8.html](releaselog/3_3_8.md) [releaselog/3_3_9.html](releaselog/3_3_9.md) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md) [releaselog/3_42_0.html](releaselog/3_42_0.md) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md) [releaselog/3_46_0.html](releaselog/3_46_0.md) [releaselog/3_46_1.html](releaselog/3_46_1.md) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md) [releaselog/3_48_0.html](releaselog/3_48_0.md) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md) [releaselog/3_4_0.html](releaselog/3_4_0.md) [releaselog/3_4_1.html](releaselog/3_4_1.md) [releaselog/3_4_2.html](releaselog/3_4_2.md) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md) [releaselog/3_52_0.html](releaselog/3_52_0.md) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [releaselog/3_5_0.html](releaselog/3_5_0.md) [releaselog/3_5_1.html](releaselog/3_5_1.md) [releaselog/3_5_2.html](releaselog/3_5_2.md) [releaselog/3_5_3.html](releaselog/3_5_3.md) [releaselog/3_5_4.html](releaselog/3_5_4.md) [releaselog/3_5_5.html](releaselog/3_5_5.md) [releaselog/3_5_6.html](releaselog/3_5_6.md) [releaselog/3_5_7.html](releaselog/3_5_7.md) [releaselog/3_5_8.html](releaselog/3_5_8.md) [releaselog/3_5_9.html](releaselog/3_5_9.md) [releaselog/3_6_0.html](releaselog/3_6_0.md) [releaselog/3_6_1.html](releaselog/3_6_1.md) [releaselog/3_6_10.html](releaselog/3_6_10.md) [releaselog/3_6_11.html](releaselog/3_6_11.md) [releaselog/3_6_12.html](releaselog/3_6_12.md) [releaselog/3_6_13.html](releaselog/3_6_13.md) [releaselog/3_6_14.html](releaselog/3_6_14.md) [releaselog/3_6_14_1.html](releaselog/3_6_14_1.md) [releaselog/3_6_14_2.html](releaselog/3_6_14_2.md) [releaselog/3_6_15.html](releaselog/3_6_15.md) [releaselog/3_6_16.html](releaselog/3_6_16.md) [releaselog/3_6_16_1.html](releaselog/3_6_16_1.md) [releaselog/3_6_17.html](releaselog/3_6_17.md) [releaselog/3_6_18.html](releaselog/3_6_18.md) [releaselog/3_6_19.html](releaselog/3_6_19.md) [releaselog/3_6_2.html](releaselog/3_6_2.md) [releaselog/3_6_20.html](releaselog/3_6_20.md) [releaselog/3_6_21.html](releaselog/3_6_21.md) [releaselog/3_6_22.html](releaselog/3_6_22.md) [releaselog/3_6_23.html](releaselog/3_6_23.md) [releaselog/3_6_23_1.html](releaselog/3_6_23_1.md) [releaselog/3_6_3.html](releaselog/3_6_3.md) [releaselog/3_6_4.html](releaselog/3_6_4.md) [releaselog/3_6_5.html](releaselog/3_6_5.md) [releaselog/3_6_6.html](releaselog/3_6_6.md) [releaselog/3_6_6_1.html](releaselog/3_6_6_1.md) [releaselog/3_6_6_2.html](releaselog/3_6_6_2.md) [releaselog/3_6_7.html](releaselog/3_6_7.md) [releaselog/3_6_8.html](releaselog/3_6_8.md) [releaselog/3_6_9.html](releaselog/3_6_9.md) [releaselog/3_7_0.html](releaselog/3_7_0.md) [releaselog/3_7_0_1.html](releaselog/3_7_0_1.md) [releaselog/3_7_1.html](releaselog/3_7_1.md) [releaselog/3_7_10.html](releaselog/3_7_10.md) [releaselog/3_7_11.html](releaselog/3_7_11.md) [releaselog/3_7_12.html](releaselog/3_7_12.md) [releaselog/3_7_12_1.html](releaselog/3_7_12_1.md) [releaselog/3_7_13.html](releaselog/3_7_13.md) [releaselog/3_7_14.html](releaselog/3_7_14.md) [releaselog/3_7_14_1.html](releaselog/3_7_14_1.md) [releaselog/3_7_15.html](releaselog/3_7_15.md) [releaselog/3_7_15_1.html](releaselog/3_7_15_1.md) [releaselog/3_7_15_2.html](releaselog/3_7_15_2.md) [releaselog/3_7_16.html](releaselog/3_7_16.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md) [releaselog/3_7_17.html](releaselog/3_7_17.md) [releaselog/3_7_2.html](releaselog/3_7_2.md) [releaselog/3_7_3.html](releaselog/3_7_3.md) [releaselog/3_7_4.html](releaselog/3_7_4.md) [releaselog/3_7_5.html](releaselog/3_7_5.md) [releaselog/3_7_6.html](releaselog/3_7_6.md) [releaselog/3_7_6_1.html](releaselog/3_7_6_1.md) [releaselog/3_7_6_2.html](releaselog/3_7_6_2.md) [releaselog/3_7_6_3.html](releaselog/3_7_6_3.md) [releaselog/3_7_7.html](releaselog/3_7_7.md) [releaselog/3_7_7_1.html](releaselog/3_7_7_1.md) [releaselog/3_7_8.html](releaselog/3_7_8.md) [releaselog/3_7_9.html](releaselog/3_7_9.md) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md) [releaselog/3_8_1.html](releaselog/3_8_1.md) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [releaselog/3_8_2.html](releaselog/3_8_2.md) [releaselog/3_8_3.html](releaselog/3_8_3.md) [releaselog/3_8_3_1.html](releaselog/3_8_3_1.md) [releaselog/3_8_4.html](releaselog/3_8_4.md) [releaselog/3_8_4_1.html](releaselog/3_8_4_1.md) [releaselog/3_8_4_2.html](releaselog/3_8_4_2.md) [releaselog/3_8_4_3.html](releaselog/3_8_4_3.md) [releaselog/3_8_5.html](releaselog/3_8_5.md) [releaselog/3_8_6.html](releaselog/3_8_6.md) [releaselog/3_8_7.html](releaselog/3_8_7.md) [releaselog/3_8_7_1.html](releaselog/3_8_7_1.md) [releaselog/3_8_7_2.html](releaselog/3_8_7_2.md) [releaselog/3_8_7_3.html](releaselog/3_8_7_3.md) [releaselog/3_8_7_4.html](releaselog/3_8_7_4.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md) [releaselog/3_8_9.html](releaselog/3_8_9.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md) [versionnumbers.html](versionnumbers.md)
- cintro → [c3ref/intro.html](c3ref/intro.md) [capi3ref.html](capi3ref.md) [lts.html](lts.md) [quickstart.html](quickstart.md)
- CLI → [amalgamation.html#amalgtarball](amalgamation.md#amalgtarball) [base64.html](base64.md) [base85.html](base85.md) [bytecodevtab.html](bytecodevtab.md) [c3ref/c_deterministic.html#sqlitedirectonly](c3ref/c_deterministic.md#sqlitedirectonly) [capi3ref.html#sqlitedirectonly](capi3ref.md#sqlitedirectonly) [changes.html#version_3_23_0](changes.md#version_3_23_0) [changes.html#version_3_23_1](changes.md#version_3_23_1) [changes.html#version_3_24_0](changes.md#version_3_24_0) [changes.html#version_3_25_0](changes.md#version_3_25_0) [changes.html#version_3_26_0](changes.md#version_3_26_0) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_28_0](changes.md#version_3_28_0) [changes.html#version_3_29_0](changes.md#version_3_29_0) [changes.html#version_3_30_0](changes.md#version_3_30_0) [changes.html#version_3_32_0](changes.md#version_3_32_0) [changes.html#version_3_33_0](changes.md#version_3_33_0) [changes.html#version_3_34_0](changes.md#version_3_34_0) [changes.html#version_3_35_0](changes.md#version_3_35_0) [changes.html#version_3_35_1](changes.md#version_3_35_1) [changes.html#version_3_35_3](changes.md#version_3_35_3) [changes.html#version_3_36_0](changes.md#version_3_36_0) [changes.html#version_3_37_0](changes.md#version_3_37_0) [changes.html#version_3_37_1](changes.md#version_3_37_1) [changes.html#version_3_38_0](changes.md#version_3_38_0) [changes.html#version_3_38_5](changes.md#version_3_38_5) [changes.html#version_3_40_1](changes.md#version_3_40_1) [changes.html#version_3_41_0](changes.md#version_3_41_0) [changes.html#version_3_41_2](changes.md#version_3_41_2) [changes.html#version_3_42_0](changes.md#version_3_42_0) [changes.html#version_3_43_2](changes.md#version_3_43_2) [changes.html#version_3_44_0](changes.md#version_3_44_0) [changes.html#version_3_44_1](changes.md#version_3_44_1) [changes.html#version_3_44_2](changes.md#version_3_44_2) [changes.html#version_3_45_0](changes.md#version_3_45_0) [changes.html#version_3_47_0](changes.md#version_3_47_0) [changes.html#version_3_48_0](changes.md#version_3_48_0) [changes.html#version_3_49_0](changes.md#version_3_49_0) [changes.html#version_3_51_0](changes.md#version_3_51_0) [changes.html#version_3_53_0](changes.md#version_3_53_0) [changes.html#version_3_6_11](changes.md#version_3_6_11) [changes.html#version_3_6_12](changes.md#version_3_6_12) [climode.html](climode.md) [cves.html#cvetab](cves.md#cvetab) [eqp.html](eqp.md) [floatingpoint.html#\*fpdigits](floatingpoint.md#*fpdigits) [floatingpoint.html#decext](floatingpoint.md#decext) [floatingpoint.html#ieee754ext](floatingpoint.md#ieee754ext) [howtocompile.html](howtocompile.md) [howtocompile.html#cli](howtocompile.md#cli) [json1.html#jblobbug](json1.md#jblobbug) [news.html](news.md) [nulinstr.html](nulinstr.md) [qmplan.html](qmplan.md) [quickstart.html](quickstart.md) [quirks.html#dblquote](quirks.md#dblquote) [recovery.html](recovery.md) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_24_0.html](releaselog/3_24_0.md) [releaselog/3_25_0.html](releaselog/3_25_0.md) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md) [releaselog/3_26_0.html](releaselog/3_26_0.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_28_0.html](releaselog/3_28_0.md) [releaselog/3_29_0.html](releaselog/3_29_0.md) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md) [releaselog/3_33_0.html](releaselog/3_33_0.md) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [releaselog/3_36_0.html](releaselog/3_36_0.md) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md) [releaselog/3_40_1.html](releaselog/3_40_1.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md) [releaselog/3_42_0.html](releaselog/3_42_0.md) [releaselog/3_43_2.html](releaselog/3_43_2.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md) [releaselog/3_48_0.html](releaselog/3_48_0.md) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [releaselog/3_6_11.html](releaselog/3_6_11.md) [releaselog/3_6_12.html](releaselog/3_6_12.md) [sqlar.html#cltools](sqlar.md#cltools) [staleexpridx.html#selfheal](staleexpridx.md#selfheal) [stricttables.html](stricttables.md) [uintcseq.html](uintcseq.md) [vtab.html#xshadowname](vtab.md#xshadowname) [vtablist.html](vtablist.md)
- clone the entire repository → [download.html#srctree](download.md#srctree)
- Clustered indexes → [fullsql.html](fullsql.md)
- co-routines → [changes.html#version_3_21_0](changes.md#version_3_21_0) [changes.html#version_3_41_0](changes.md#version_3_41_0) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- coalesce → [arch.html](arch.md) [changes.html#version_3_6_21](changes.md#version_3_6_21) [lang_corefunc.html](lang_corefunc.md) [lang_corefunc.html#ifnull](lang_corefunc.md#ifnull) [optoverview.html#leftjoinreduction](optoverview.md#leftjoinreduction) [releaselog/3_6_21.html](releaselog/3_6_21.md)
- Code of Ethics → [codeofconduct.html](codeofconduct.md)
- COLLATE → [fullsql.html](fullsql.md)
- COLLATE clause → [c3ref/vtab_collation.html](c3ref/vtab_collation.md) [capi3ref.html#sqlite3_vtab_collation](capi3ref.md#sqlite3_vtab_collation) [gencol.html#vgc\*](gencol.md#vgc*)
- COLLATE clauses → [stricttables.html](stricttables.md)
- COLLATE operator → [c3ref/vtab_collation.html](c3ref/vtab_collation.md) [capi3ref.html#sqlite3_vtab_collation](capi3ref.md#sqlite3_vtab_collation) [changes.html#version_3_7_15](changes.md#version_3_7_15) [changes.html#version_3_7_17](changes.md#version_3_7_17) [datatype3.html#colrules](datatype3.md#colrules) [lang_select.html#nullslast](lang_select.md#nullslast) [oldnews.html](oldnews.md) [releaselog/3_7_15.html](releaselog/3_7_15.md) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- collating function → [fileformat2.html#serialtype](fileformat2.md#serialtype)
- collating sequence → [changes.html#version_3_7_17](changes.md#version_3_7_17) [foreignkeys.html#parentchild](foreignkeys.md#parentchild) [gencol.html#vgc\*](gencol.md#vgc*) [lang_createtable.html#collateclause](lang_createtable.md#collateclause) [lang_expr.html#collateop](lang_expr.md#collateop) [optoverview.html#like_opt](optoverview.md#like_opt) [pragma.html#pragma_index_xinfo](pragma.md#pragma_index_xinfo) [releaselog/3_7_17.html](releaselog/3_7_17.md) [vtab.html#xbestindex](vtab.md#xbestindex)
- collating sequences → [changes.html#version_3_19_0](changes.md#version_3_19_0) [cintro.html](cintro.md) [cli.html#dotload](cli.md#dotload) [loadext.html](loadext.md) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md) [sqldiff.html](sqldiff.md)
- collation → [c3ref/create_collation.html](c3ref/create_collation.md) [capi3ref.html#sqlite3_create_collation](capi3ref.md#sqlite3_create_collation) [lang_select.html#fromclause](lang_select.md#fromclause) [lang_select.html#resultset](lang_select.md#resultset)
- column access functions → [c3ref/step.html](c3ref/step.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob)
- column affinity → [changes.html#version_3_32_0](changes.md#version_3_32_0) [changes.html#version_3_8_6](changes.md#version_3_8_6) [lang_expr.html#castexpr](lang_expr.md#castexpr) [lang_expr.html#hexint](lang_expr.md#hexint) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md) [releaselog/3_8_6.html](releaselog/3_8_6.md)
- column definition → [datatype3.html#collation](datatype3.md#collation) [fileformat2.html#serialtype](fileformat2.md#serialtype) [lang_expr.html#collateop](lang_expr.md#collateop)
- column definitions → [lang_createvtab.html](lang_createvtab.md) [vtab.html](vtab.md)
- column-constraint → [gencol.html](gencol.md) [lang_altertable.html](lang_altertable.md) [lang_createtable.html](lang_createtable.md) [lang_createtable.html#tablecoldef](lang_createtable.md#tablecoldef)
- column-def → [lang_altertable.html](lang_altertable.md) [lang_altertable.html#altertabaddcol](lang_altertable.md#altertabaddcol) [lang_createtable.html](lang_createtable.md) [lang_createtable.html#tablecoldef](lang_createtable.md#tablecoldef)
- column-name-list → [lang_createtrigger.html](lang_createtrigger.md) [lang_insert.html](lang_insert.md) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md)
- Columnar output modes → [changes.html#version_3_38_0](changes.md#version_3_38_0) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md)
- columnar output modes → [changes.html#version_3_38_0](changes.md#version_3_38_0) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md)
- colUsed field → [changes.html#version_3_10_0](changes.md#version_3_10_0) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md)
- comma option → [changes.html#version_3_42_0](changes.md#version_3_42_0) [releaselog/3_42_0.html](releaselog/3_42_0.md)
- Command Line Interface → [changes.html#version_3_6_21](changes.md#version_3_6_21) [changes.html#version_3_6_23](changes.md#version_3_6_23) [climode.html](climode.md) [compile.html#enable_iotrace](compile.md#enable_iotrace) [howtocompile.html](howtocompile.md) [oldnews.html](oldnews.md) [quickstart.html](quickstart.md) [recovery.html](recovery.md) [releaselog/3_6_21.html](releaselog/3_6_21.md) [releaselog/3_6_23.html](releaselog/3_6_23.md)
- command-line interface → [features.html](features.md) [lang_analyze.html#statanal](lang_analyze.md#statanal)
- command-line shell → [amalg-v-canon.html#canon](amalg-v-canon.md#canon) [changes.html#version_3_10_0](changes.md#version_3_10_0) [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_12_0](changes.md#version_3_12_0) [changes.html#version_3_13_0](changes.md#version_3_13_0) [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_14_2](changes.md#version_3_14_2) [changes.html#version_3_15_0](changes.md#version_3_15_0) [changes.html#version_3_16_0](changes.md#version_3_16_0) [changes.html#version_3_17_0](changes.md#version_3_17_0) [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_19_0](changes.md#version_3_19_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_21_0](changes.md#version_3_21_0) [changes.html#version_3_22_0](changes.md#version_3_22_0) [changes.html#version_3_25_0](changes.md#version_3_25_0) [changes.html#version_3_7_10](changes.md#version_3_7_10) [changes.html#version_3_7_11](changes.md#version_3_7_11) [changes.html#version_3_7_14](changes.md#version_3_7_14) [changes.html#version_3_7_16](changes.md#version_3_7_16) [changes.html#version_3_7_17](changes.md#version_3_7_17) [changes.html#version_3_7_5](changes.md#version_3_7_5) [changes.html#version_3_8_0](changes.md#version_3_8_0) [changes.html#version_3_8_10](changes.md#version_3_8_10) [changes.html#version_3_8_10_1](changes.md#version_3_8_10_1) [changes.html#version_3_8_2](changes.md#version_3_8_2) [changes.html#version_3_8_3](changes.md#version_3_8_3) [changes.html#version_3_8_5](changes.md#version_3_8_5) [changes.html#version_3_8_6](changes.md#version_3_8_6) [changes.html#version_3_8_7](changes.md#version_3_8_7) [changes.html#version_3_8_8_3](changes.md#version_3_8_8_3) [changes.html#version_3_8_9](changes.md#version_3_8_9) [compile.html#enable_explain_comments](compile.md#enable_explain_comments) [compile.html#enable_unknown_sql_function](compile.md#enable_unknown_sql_function) [compile.html#have_zlib](compile.md#have_zlib) [completion.html](completion.md) [csv.html](csv.md) [cves.html#cvetab](cves.md#cvetab) [dbpage.html](dbpage.md) [debugging.html](debugging.md) [eqp.html](eqp.md) [imposter.html#dotimposter](imposter.md#dotimposter) [lang_with.html#mandelbrot](lang_with.md#mandelbrot) [loadext.html](loadext.md) [news.html](news.md) [oldnews.html](oldnews.md) [opcode.html#subprog](opcode.md#subprog) [profile.html](profile.md) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_17_0.html](releaselog/3_17_0.md) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_22_0.html](releaselog/3_22_0.md) [releaselog/3_25_0.html](releaselog/3_25_0.md) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md) [releaselog/3_7_10.html](releaselog/3_7_10.md) [releaselog/3_7_11.html](releaselog/3_7_11.md) [releaselog/3_7_14.html](releaselog/3_7_14.md) [releaselog/3_7_16.html](releaselog/3_7_16.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md) [releaselog/3_7_17.html](releaselog/3_7_17.md) [releaselog/3_7_5.html](releaselog/3_7_5.md) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md) [releaselog/3_8_2.html](releaselog/3_8_2.md) [releaselog/3_8_3.html](releaselog/3_8_3.md) [releaselog/3_8_5.html](releaselog/3_8_5.md) [releaselog/3_8_6.html](releaselog/3_8_6.md) [releaselog/3_8_7.html](releaselog/3_8_7.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md) [releaselog/3_8_9.html](releaselog/3_8_9.md) [series.html](series.md) [sqlanalyze.html](sqlanalyze.md) [stmt.html](stmt.md) [vfs.html#shim](vfs.md#shim) [wal.html#fast](wal.md#fast) [whentouse.html#website](whentouse.md#website) [zipfile.html](zipfile.md)
- comment → [lang.html](lang.md)
- comment-syntax → [lang_comment.html](lang_comment.md)
- COMMIT → [c3ref/c_txn_none.html#sqlitetxnread](c3ref/c_txn_none.md#sqlitetxnread) [c3ref/c_txn_none.html#sqlitetxnwrite](c3ref/c_txn_none.md#sqlitetxnwrite) [c3ref/commit_hook.html](c3ref/commit_hook.md) [c3ref/get_autocommit.html](c3ref/get_autocommit.md) [c3ref/step.html](c3ref/step.md) [c3ref/stmt_readonly.html](c3ref/stmt_readonly.md) [capi3ref.html#sqlite3_commit_hook](capi3ref.md#sqlite3_commit_hook) [capi3ref.html#sqlite3_get_autocommit](capi3ref.md#sqlite3_get_autocommit) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [capi3ref.html#sqlite3_stmt_readonly](capi3ref.md#sqlite3_stmt_readonly) [capi3ref.html#sqlitetxnread](capi3ref.md#sqlitetxnread) [capi3ref.html#sqlitetxnwrite](capi3ref.md#sqlitetxnwrite) [changes.html#version_3_14_1](changes.md#version_3_14_1) [changes.html#version_3_32_2](changes.md#version_3_32_2) [changes.html#version_3_6_5](changes.md#version_3_6_5) [faq.html#q19](faq.md#q19) [foreignkeys.html#fk_enable](foreignkeys.md#fk_enable) [fts3.html#\*fts4mergecmd](fts3.md#*fts4mergecmd) [fullsql.html](fullsql.md) [isolation.html](isolation.md) [lang.html](lang.md) [lang_attach.html](lang_attach.md) [lang_savepoint.html](lang_savepoint.md) [oldnews.html](oldnews.md) [pragma.html#pragma_cache_spill](pragma.md#pragma_cache_spill) [pragma.html#pragma_query_only](pragma.md#pragma_query_only) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md) [releaselog/3_6_5.html](releaselog/3_6_5.md) [rescode.html#busy](rescode.md#busy) [tempfiles.html#superjrnl](tempfiles.md#superjrnl) [wal.html#advantages](wal.md#advantages) [wal.html#fast](wal.md#fast)
- commit-stmt → [lang_transaction.html](lang_transaction.md)
- common table expressions → [changes.html#version_3_10_0](changes.md#version_3_10_0) [changes.html#version_3_35_0](changes.md#version_3_35_0) [changes.html#version_3_35_3](changes.md#version_3_35_3) [changes.html#version_3_8_11](changes.md#version_3_8_11) [changes.html#version_3_8_3](changes.md#version_3_8_3) [compile.html#omit_cte](compile.md#omit_cte) [csv.html](csv.md) [features.html](features.md) [lang_returning.html](lang_returning.md) [lang_select.html#values](lang_select.md#values) [oldnews.html](oldnews.md) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [releaselog/3_8_3.html](releaselog/3_8_3.md) [versionnumbers.html](versionnumbers.md)
- common-table-expression → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- comparison expressions → [lang_select.html#nullslast](lang_select.md#nullslast)
- compile fts → [fts3.html#fts4aux](fts3.md#fts4aux) [fts3.html#near](fts3.md#near)
- compile loadable extensions → [memstat.html](memstat.md) [stmt.html](stmt.md)
- compile-time options → [amalg-v-canon.html#canon](amalg-v-canon.md#canon) [amalgamation.html](amalgamation.md) [debugging.html](debugging.md) [howtocompile.html#amal](howtocompile.md#amal) [howtocompile.html#cli](howtocompile.md#cli) [howtocompile.html#dll](howtocompile.md#dll) [lang_keywords.html](lang_keywords.md) [pragma.html#pragma_compile_options](pragma.md#pragma_compile_options) [privatebranch.html](privatebranch.md)
- compile_options pragma → [c3ref/compileoption_get.html](c3ref/compileoption_get.md) [capi3ref.html#sqlite3_compileoption_get](capi3ref.md#sqlite3_compileoption_get) [changes.html#version_3_6_23](changes.md#version_3_6_23) [compile.html#omit_compileoption_diags](compile.md#omit_compileoption_diags) [lang_corefunc.html#sqlite_compileoption_get](lang_corefunc.md#sqlite_compileoption_get) [oldnews.html](oldnews.md) [releaselog/3_6_23.html](releaselog/3_6_23.md)
- Compiling Loadable Extensions → [fts5.html#compiling_and_using_fts5](fts5.md#compiling_and_using_fts5)
- complete list of SQLite releases → [qmplan.html](qmplan.md) [releaselog/3_0_0.html](releaselog/3_0_0.md) [releaselog/3_0_1.html](releaselog/3_0_1.md) [releaselog/3_0_2.html](releaselog/3_0_2.md) [releaselog/3_0_3.html](releaselog/3_0_3.md) [releaselog/3_0_4.html](releaselog/3_0_4.md) [releaselog/3_0_5.html](releaselog/3_0_5.md) [releaselog/3_0_6.html](releaselog/3_0_6.md) [releaselog/3_0_7.html](releaselog/3_0_7.md) [releaselog/3_0_8.html](releaselog/3_0_8.md) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_17_0.html](releaselog/3_17_0.md) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md) [releaselog/3_1_0.html](releaselog/3_1_0.md) [releaselog/3_1_1.html](releaselog/3_1_1.md) [releaselog/3_1_2.html](releaselog/3_1_2.md) [releaselog/3_1_3.html](releaselog/3_1_3.md) [releaselog/3_1_4.html](releaselog/3_1_4.md) [releaselog/3_1_5.html](releaselog/3_1_5.md) [releaselog/3_1_6.html](releaselog/3_1_6.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_22_0.html](releaselog/3_22_0.md) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_24_0.html](releaselog/3_24_0.md) [releaselog/3_25_0.html](releaselog/3_25_0.md) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md) [releaselog/3_26_0.html](releaselog/3_26_0.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_28_0.html](releaselog/3_28_0.md) [releaselog/3_29_0.html](releaselog/3_29_0.md) [releaselog/3_2_0.html](releaselog/3_2_0.md) [releaselog/3_2_1.html](releaselog/3_2_1.md) [releaselog/3_2_2.html](releaselog/3_2_2.md) [releaselog/3_2_3.html](releaselog/3_2_3.md) [releaselog/3_2_4.html](releaselog/3_2_4.md) [releaselog/3_2_5.html](releaselog/3_2_5.md) [releaselog/3_2_6.html](releaselog/3_2_6.md) [releaselog/3_2_7.html](releaselog/3_2_7.md) [releaselog/3_2_8.html](releaselog/3_2_8.md) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md) [releaselog/3_33_0.html](releaselog/3_33_0.md) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [releaselog/3_36_0.html](releaselog/3_36_0.md) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md) [releaselog/3_39_0.html](releaselog/3_39_0.md) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md) [releaselog/3_3_0.html](releaselog/3_3_0.md) [releaselog/3_3_1.html](releaselog/3_3_1.md) [releaselog/3_3_10.html](releaselog/3_3_10.md) [releaselog/3_3_11.html](releaselog/3_3_11.md) [releaselog/3_3_12.html](releaselog/3_3_12.md) [releaselog/3_3_13.html](releaselog/3_3_13.md) [releaselog/3_3_14.html](releaselog/3_3_14.md) [releaselog/3_3_15.html](releaselog/3_3_15.md) [releaselog/3_3_16.html](releaselog/3_3_16.md) [releaselog/3_3_17.html](releaselog/3_3_17.md) [releaselog/3_3_2.html](releaselog/3_3_2.md) [releaselog/3_3_3.html](releaselog/3_3_3.md) [releaselog/3_3_4.html](releaselog/3_3_4.md) [releaselog/3_3_5.html](releaselog/3_3_5.md) [releaselog/3_3_6.html](releaselog/3_3_6.md) [releaselog/3_3_7.html](releaselog/3_3_7.md) [releaselog/3_3_8.html](releaselog/3_3_8.md) [releaselog/3_3_9.html](releaselog/3_3_9.md) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md) [releaselog/3_42_0.html](releaselog/3_42_0.md) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md) [releaselog/3_46_0.html](releaselog/3_46_0.md) [releaselog/3_46_1.html](releaselog/3_46_1.md) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md) [releaselog/3_48_0.html](releaselog/3_48_0.md) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md) [releaselog/3_4_0.html](releaselog/3_4_0.md) [releaselog/3_4_1.html](releaselog/3_4_1.md) [releaselog/3_4_2.html](releaselog/3_4_2.md) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md) [releaselog/3_52_0.html](releaselog/3_52_0.md) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [releaselog/3_5_0.html](releaselog/3_5_0.md) [releaselog/3_5_1.html](releaselog/3_5_1.md) [releaselog/3_5_2.html](releaselog/3_5_2.md) [releaselog/3_5_3.html](releaselog/3_5_3.md) [releaselog/3_5_4.html](releaselog/3_5_4.md) [releaselog/3_5_5.html](releaselog/3_5_5.md) [releaselog/3_5_6.html](releaselog/3_5_6.md) [releaselog/3_5_7.html](releaselog/3_5_7.md) [releaselog/3_5_8.html](releaselog/3_5_8.md) [releaselog/3_5_9.html](releaselog/3_5_9.md) [releaselog/3_6_0.html](releaselog/3_6_0.md) [releaselog/3_6_1.html](releaselog/3_6_1.md) [releaselog/3_6_10.html](releaselog/3_6_10.md) [releaselog/3_6_11.html](releaselog/3_6_11.md) [releaselog/3_6_12.html](releaselog/3_6_12.md) [releaselog/3_6_13.html](releaselog/3_6_13.md) [releaselog/3_6_14.html](releaselog/3_6_14.md) [releaselog/3_6_14_1.html](releaselog/3_6_14_1.md) [releaselog/3_6_14_2.html](releaselog/3_6_14_2.md) [releaselog/3_6_15.html](releaselog/3_6_15.md) [releaselog/3_6_16.html](releaselog/3_6_16.md) [releaselog/3_6_16_1.html](releaselog/3_6_16_1.md) [releaselog/3_6_17.html](releaselog/3_6_17.md) [releaselog/3_6_18.html](releaselog/3_6_18.md) [releaselog/3_6_19.html](releaselog/3_6_19.md) [releaselog/3_6_2.html](releaselog/3_6_2.md) [releaselog/3_6_20.html](releaselog/3_6_20.md) [releaselog/3_6_21.html](releaselog/3_6_21.md) [releaselog/3_6_22.html](releaselog/3_6_22.md) [releaselog/3_6_23.html](releaselog/3_6_23.md) [releaselog/3_6_23_1.html](releaselog/3_6_23_1.md) [releaselog/3_6_3.html](releaselog/3_6_3.md) [releaselog/3_6_4.html](releaselog/3_6_4.md) [releaselog/3_6_5.html](releaselog/3_6_5.md) [releaselog/3_6_6.html](releaselog/3_6_6.md) [releaselog/3_6_6_1.html](releaselog/3_6_6_1.md) [releaselog/3_6_6_2.html](releaselog/3_6_6_2.md) [releaselog/3_6_7.html](releaselog/3_6_7.md) [releaselog/3_6_8.html](releaselog/3_6_8.md) [releaselog/3_6_9.html](releaselog/3_6_9.md) [releaselog/3_7_0.html](releaselog/3_7_0.md) [releaselog/3_7_0_1.html](releaselog/3_7_0_1.md) [releaselog/3_7_1.html](releaselog/3_7_1.md) [releaselog/3_7_10.html](releaselog/3_7_10.md) [releaselog/3_7_11.html](releaselog/3_7_11.md) [releaselog/3_7_12.html](releaselog/3_7_12.md) [releaselog/3_7_12_1.html](releaselog/3_7_12_1.md) [releaselog/3_7_13.html](releaselog/3_7_13.md) [releaselog/3_7_14.html](releaselog/3_7_14.md) [releaselog/3_7_14_1.html](releaselog/3_7_14_1.md) [releaselog/3_7_15.html](releaselog/3_7_15.md) [releaselog/3_7_15_1.html](releaselog/3_7_15_1.md) [releaselog/3_7_15_2.html](releaselog/3_7_15_2.md) [releaselog/3_7_16.html](releaselog/3_7_16.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md) [releaselog/3_7_17.html](releaselog/3_7_17.md) [releaselog/3_7_2.html](releaselog/3_7_2.md) [releaselog/3_7_3.html](releaselog/3_7_3.md) [releaselog/3_7_4.html](releaselog/3_7_4.md) [releaselog/3_7_5.html](releaselog/3_7_5.md) [releaselog/3_7_6.html](releaselog/3_7_6.md) [releaselog/3_7_6_1.html](releaselog/3_7_6_1.md) [releaselog/3_7_6_2.html](releaselog/3_7_6_2.md) [releaselog/3_7_6_3.html](releaselog/3_7_6_3.md) [releaselog/3_7_7.html](releaselog/3_7_7.md) [releaselog/3_7_7_1.html](releaselog/3_7_7_1.md) [releaselog/3_7_8.html](releaselog/3_7_8.md) [releaselog/3_7_9.html](releaselog/3_7_9.md) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md) [releaselog/3_8_1.html](releaselog/3_8_1.md) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [releaselog/3_8_2.html](releaselog/3_8_2.md) [releaselog/3_8_3.html](releaselog/3_8_3.md) [releaselog/3_8_3_1.html](releaselog/3_8_3_1.md) [releaselog/3_8_4.html](releaselog/3_8_4.md) [releaselog/3_8_4_1.html](releaselog/3_8_4_1.md) [releaselog/3_8_4_2.html](releaselog/3_8_4_2.md) [releaselog/3_8_4_3.html](releaselog/3_8_4_3.md) [releaselog/3_8_5.html](releaselog/3_8_5.md) [releaselog/3_8_6.html](releaselog/3_8_6.md) [releaselog/3_8_7.html](releaselog/3_8_7.md) [releaselog/3_8_7_1.html](releaselog/3_8_7_1.md) [releaselog/3_8_7_2.html](releaselog/3_8_7_2.md) [releaselog/3_8_7_3.html](releaselog/3_8_7_3.md) [releaselog/3_8_7_4.html](releaselog/3_8_7_4.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md) [releaselog/3_8_9.html](releaselog/3_8_9.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- COMPLETION → [vtablist.html](vtablist.md)
- COMPLETION extension → [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- compound query → [changes.html#version_3_7_17](changes.md#version_3_7_17) [eqp.html#or-opt](eqp.md#or-opt) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- compound select → [lang_with.html#mathint](lang_with.md#mathint) [lang_with.html#recursivecte](lang_with.md#recursivecte)
- compound SELECT → [datatype3.html#affcompoundview](datatype3.md#affcompoundview) [lang_select.html](lang_select.md) [lang_select.html#limitoffset](lang_select.md#limitoffset) [lang_select.html#nullslast](lang_select.md#nullslast) [lang_select.html#orderby](lang_select.md#orderby)
- compound SELECTs → [lang_insert.html](lang_insert.md)
- compound-operator → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- compound-select-stmt → [lang_select.html#compound](lang_select.md#compound)
- compressed FTS4 content → [changes.html#version_3_7_6](changes.md#version_3_7_6) [releaselog/3_7_6.html](releaselog/3_7_6.md)
- compute the Mandelbrot set → [oldnews.html](oldnews.md)
- computed columns → [news.html](news.md)
- concat → [changes.html#version_3_44_0](changes.md#version_3_44_0) [lang_corefunc.html](lang_corefunc.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md)
- concat_ws → [changes.html#version_3_44_0](changes.md#version_3_44_0) [changes.html#version_3_49_1](changes.md#version_3_49_1) [changes.html#version_3_50_2](changes.md#version_3_50_2) [lang_corefunc.html](lang_corefunc.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- concat_ws SQL function → [cves.html#cvetab](cves.md#cvetab) [news.html](news.md)
- config method → [changes.html#version_3_30_0](changes.md#version_3_30_0) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md)
- configuration option → [c3ref/config.html](c3ref/config.md) [capi3ref.html#sqlite3_config](capi3ref.md#sqlite3_config)
- conflict clause → [lang_createtable.html#notnullconst](lang_createtable.md#notnullconst)
- conflict resolution algorithm → [lang_upsert.html#parseambig](lang_upsert.md#parseambig)
- conflict resolution mode → [c3ref/c_deny.html](c3ref/c_deny.md) [capi3ref.html#SQLITE_DENY](capi3ref.md#SQLITE_DENY) [rescode.html#abort](rescode.md#abort)
- conflict-clause → [lang_altertable.html](lang_altertable.md) [lang_conflict.html](lang_conflict.md) [lang_createtable.html](lang_createtable.md) [lang_createtable.html#notnullconst](lang_createtable.md#notnullconst)
- constant-propagation optimization → [changes.html#version_3_36_0](changes.md#version_3_36_0) [changes.html#version_3_41_0](changes.md#version_3_41_0) [releaselog/3_36_0.html](releaselog/3_36_0.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- contentless fts4 tables → [rbu.html#fts4_tables](rbu.md#fts4_tables)
- contentless-delete → [changes.html#version_3_43_0](changes.md#version_3_43_0) [news.html](news.md) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md)
- control characters → [changes.html#version_3_50_0](changes.md#version_3_50_0) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- copyright → [hirely.html](hirely.md)
- Core Functions → [fullsql.html](fullsql.md)
- corefunc → [fts5.html](fts5.md) [fts5.html#\_auxiliary_functions\_](fts5.md#_auxiliary_functions_) [lang.html](lang.md) [lang_datefunc.html](lang_datefunc.md) [lang_expr.html#\*funcinexpr](lang_expr.md#*funcinexpr)
- coreqp → [changes.html#version_3_7_13](changes.md#version_3_7_13) [inmemorydb.html#sharedmemdb](inmemorydb.md#sharedmemdb) [oldnews.html](oldnews.md) [releaselog/3_7_13.html](releaselog/3_7_13.md)
- correlated subqueries → [changes.html#version_3_27_0](changes.md#version_3_27_0) [fullsql.html](fullsql.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- cos → [lang_mathfunc.html](lang_mathfunc.md)
- cosh → [lang_mathfunc.html](lang_mathfunc.md)
- count → [arch.html](arch.md) [lang_aggfunc.html#aggfunclist](lang_aggfunc.md#aggfunclist) [lang_aggfunc.html#avg](lang_aggfunc.md#avg)
- count_changes pragma → [c3ref/changes.html](c3ref/changes.md) [c3ref/total_changes.html](c3ref/total_changes.md) [capi3ref.html#sqlite3_changes](capi3ref.md#sqlite3_changes) [capi3ref.html#sqlite3_total_changes](capi3ref.md#sqlite3_total_changes) [changes.html#version_3_6_5](changes.md#version_3_6_5) [changes.html#version_3_7_9](changes.md#version_3_7_9) [lang_createtrigger.html#instead_of_trigger](lang_createtrigger.md#instead_of_trigger) [lang_delete.html#truncateopt](lang_delete.md#truncateopt) [releaselog/3_6_5.html](releaselog/3_6_5.md) [releaselog/3_7_9.html](releaselog/3_7_9.md)
- covering index → [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_41_0](changes.md#version_3_41_0) [changes.html#version_3_46_1](changes.md#version_3_46_1) [changes.html#version_3_7_14](changes.md#version_3_7_14) [eqp.html](eqp.md) [fullsql.html](fullsql.md) [queryplanner.html#srchsortcovidx](queryplanner.md#srchsortcovidx) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md) [releaselog/3_46_1.html](releaselog/3_46_1.md) [releaselog/3_7_14.html](releaselog/3_7_14.md)
- covering indexes → [changes.html#version_3_40_0](changes.md#version_3_40_0) [changes.html#version_3_48_0](changes.md#version_3_48_0) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md) [releaselog/3_48_0.html](releaselog/3_48_0.md)
- CPU cycles used → [changes.html#version_3_17_0](changes.md#version_3_17_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_17_0.html](releaselog/3_17_0.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- CPU performance measurement → [changes.html#version_3_16_0](changes.md#version_3_16_0) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md)
- CREATE INDEX → [aff_short.html](aff_short.md) [appfileformat.html](appfileformat.md) [changes.html#version_3_7_8](changes.md#version_3_7_8) [changes.html#version_3_8_10](changes.md#version_3_8_10) [changes.html#version_3_8_6](changes.md#version_3_8_6) [expridx.html](expridx.md) [fileformat2.html##sqltab](fileformat2.md##sqltab) [fileformat2.html#ffschema](fileformat2.md#ffschema) [fileformat2.html#serialtype](fileformat2.md#serialtype) [foreignkeys.html#fk_actions](foreignkeys.md#fk_actions) [fullsql.html](fullsql.md) [lang.html](lang.md) [lang_altertable.html#otheralter](lang_altertable.md#otheralter) [lang_analyze.html#pragopt](lang_analyze.md#pragopt) [lang_dropindex.html](lang_dropindex.md) [limits.html#max_page_count](limits.md#max_page_count) [oldnews.html](oldnews.md) [optoverview.html#where_clause](optoverview.md#where_clause) [partialindex.html](partialindex.md) [pragma.html#pragma_index_info](pragma.md#pragma_index_info) [pragma.html#pragma_index_list](pragma.md#pragma_index_list) [pragma.html#pragma_index_xinfo](pragma.md#pragma_index_xinfo) [pragma.html#pragma_journal_mode](pragma.md#pragma_journal_mode) [pragma.html#pragma_legacy_alter_table](pragma.md#pragma_legacy_alter_table) [pragma.html#pragma_optimize](pragma.md#pragma_optimize) [releaselog/3_7_8.html](releaselog/3_7_8.md) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md) [releaselog/3_8_6.html](releaselog/3_8_6.md) [schematab.html](schematab.md) [staleexpridx.html](staleexpridx.md) [vtab.html](vtab.md)
- CREATE TABLE → [csv.html](csv.md) [eqp.html](eqp.md) [expridx.html](expridx.md) [fileformat2.html#ffschema](fileformat2.md#ffschema) [fileformat2.html#serialtype](fileformat2.md#serialtype) [foreignkeys.html](foreignkeys.md) [foreignkeys.html#fk_actions](foreignkeys.md#fk_actions) [foreignkeys.html#fk_enable](foreignkeys.md#fk_enable) [fullsql.html](fullsql.md) [imposter.html](imposter.md) [lang.html](lang.md) [lang_altertable.html#altertabaddcol](lang_altertable.md#altertabaddcol) [lang_altertable.html#otheralter](lang_altertable.md#otheralter) [lang_createindex.html#collidx](lang_createindex.md#collidx) [lang_createvtab.html](lang_createvtab.md) [lang_droptable.html](lang_droptable.md) [lang_expr.html#in_op](lang_expr.md#in_op) [lang_insert.html](lang_insert.md) [pragma.html#pragma_legacy_alter_table](pragma.md#pragma_legacy_alter_table) [schematab.html](schematab.md) [stricttables.html](stricttables.md) [vtab.html](vtab.md) [vtab.html#xcreate](vtab.md#xcreate) [withoutrowid.html](withoutrowid.md)
- CREATE TABLE AS → [changes.html#version_3_21_0](changes.md#version_3_21_0) [changes.html#version_3_8_11](changes.md#version_3_8_11) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- CREATE TRIGGER → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigenabletrigger](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenabletrigger) [c3ref/changes.html](c3ref/changes.md) [capi3ref.html#sqlite3_changes](capi3ref.md#sqlite3_changes) [capi3ref.html#sqlitedbconfigenabletrigger](capi3ref.md#sqlitedbconfigenabletrigger) [changes.html#version_3_16_1](changes.md#version_3_16_1) [changes.html#version_3_25_0](changes.md#version_3_25_0) [changes.html#version_3_39_4](changes.md#version_3_39_4) [compile.html#omit_trigger](compile.md#omit_trigger) [fileformat2.html#ffschema](fileformat2.md#ffschema) [foreignkeys.html#fk_actions](foreignkeys.md#fk_actions) [fullsql.html](fullsql.md) [lang.html](lang.md) [lang_altertable.html#otheralter](lang_altertable.md#otheralter) [lang_conflict.html](lang_conflict.md) [lang_createtable.html](lang_createtable.md) [lang_delete.html](lang_delete.md) [lang_droptrigger.html](lang_droptrigger.md) [lang_insert.html](lang_insert.md) [lang_update.html](lang_update.md) [lang_with.html#mathint](lang_with.md#mathint) [opcode.html#subprog](opcode.md#subprog) [pragma.html#pragma_legacy_alter_table](pragma.md#pragma_legacy_alter_table) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_25_0.html](releaselog/3_25_0.md) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md) [rescode.html#constraint_trigger](rescode.md#constraint_trigger) [schematab.html](schematab.md) [sqldiff.html](sqldiff.md)
- CREATE VIEW → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigenableview](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenableview) [capi3ref.html#sqlitedbconfigenableview](capi3ref.md#sqlitedbconfigenableview) [changes.html#version_3_8_7_1](changes.md#version_3_8_7_1) [changes.html#version_3_9_0](changes.md#version_3_9_0) [compile.html#omit_view](compile.md#omit_view) [fileformat2.html#ffschema](fileformat2.md#ffschema) [fullsql.html](fullsql.md) [lang.html](lang.md) [lang_altertable.html#otheralter](lang_altertable.md#otheralter) [lang_dropview.html](lang_dropview.md) [releaselog/3_8_7_1.html](releaselog/3_8_7_1.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md) [schematab.html](schematab.md) [sqldiff.html](sqldiff.md)
- CREATE VIRTUAL TABLE → [changes.html#version_3_7_11](changes.md#version_3_7_11) [cli.html#zipdb](cli.md#zipdb) [dbstat.html](dbstat.md) [fileformat2.html#ffschema](fileformat2.md#ffschema) [fts3.html#fts4](fts3.md#fts4) [lang.html](lang.md) [releaselog/3_7_11.html](releaselog/3_7_11.md) [schematab.html](schematab.md) [vtab.html](vtab.md) [vtab.html#customvtab](vtab.md#customvtab) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab) [vtab.html#epovtab](vtab.md#epovtab) [vtab.html#xcreate](vtab.md#xcreate) [vtab.html#xshadowname](vtab.md#xshadowname)
- create-index-stmt → [lang_createindex.html](lang_createindex.md) [partialindex.html](partialindex.md)
- create-table-stmt → [lang_createtable.html](lang_createtable.md)
- create-trigger-stmt → [lang_createtrigger.html](lang_createtrigger.md)
- create-view-stmt → [lang_createview.html](lang_createview.md)
- create-virtual-table-stmt → [lang_createvtab.html](lang_createvtab.md) [vtab.html](vtab.md)
- CROSS JOIN → [lang_select.html#crossjoin](lang_select.md#crossjoin) [profile.html](profile.md) [queryplanner-ng.html#howtofix](queryplanner-ng.md#howtofix)
- csv → [vtablist.html](vtablist.md)
- CSV output → [climode.html#crlf](climode.md#crlf)
- CSV virtual table → [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_21_0](changes.md#version_3_21_0) [changes.html#version_3_24_0](changes.md#version_3_24_0) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_24_0.html](releaselog/3_24_0.md)
- cte-table-name → [lang_with.html](lang_with.md) [lang_with.html#recursivecte](lang_with.md#recursivecte)
- custom auxiliary functions → [fts5.html#appendix_a](fts5.md#appendix_a)
- custom builds → [c3ref/initialize.html](c3ref/initialize.md) [capi3ref.html#sqlite3_initialize](capi3ref.md#sqlite3_initialize)
- custom r-tree queries → [changes.html#version_3_7_3](changes.md#version_3_7_3) [oldnews.html](oldnews.md) [releaselog/3_7_3.html](releaselog/3_7_3.md)
- custom SQL functions → [security.html#baddb](security.md#baddb)
- custom tokenizers → [fts5.html#tokenizers](fts5.md#tokenizers)
- custom virtual tables → [security.html#baddb](security.md#baddb)
- data_store_directory pragma → [c3ref/data_directory.html](c3ref/data_directory.md) [capi3ref.html#sqlite3_data_directory](capi3ref.md#sqlite3_data_directory)
- data_version pragma → [c3ref/changes.html](c3ref/changes.md) [c3ref/total_changes.html](c3ref/total_changes.md) [capi3ref.html#sqlite3_changes](capi3ref.md#sqlite3_changes) [capi3ref.html#sqlite3_total_changes](capi3ref.md#sqlite3_total_changes)
- database connection → [35to36.html](35to36.md) [appfunc.html](appfunc.md) [appfunc.html#sec](appfunc.md#sec) [backup.html](backup.md) [c3ref/auto_extension.html](c3ref/auto_extension.md) [c3ref/backup_finish.html#sqlite3backupinit](c3ref/backup_finish.md#sqlite3backupinit) [c3ref/backup_finish.html#sqlite3backuppagecount](c3ref/backup_finish.md#sqlite3backuppagecount) [c3ref/backup_finish.html#sqlite3backupstep](c3ref/backup_finish.md#sqlite3backupstep) [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/blob_write.html](c3ref/blob_write.md) [c3ref/busy_handler.html](c3ref/busy_handler.md) [c3ref/busy_timeout.html](c3ref/busy_timeout.md) [c3ref/c_config_covering_index_scan.html#sqliteconfiglookaside](c3ref/c_config_covering_index_scan.md#sqliteconfiglookaside) [c3ref/c_config_covering_index_scan.html#sqliteconfigmultithread](c3ref/c_config_covering_index_scan.md#sqliteconfigmultithread) [c3ref/c_config_covering_index_scan.html#sqliteconfigserialized](c3ref/c_config_covering_index_scan.md#sqliteconfigserialized) [c3ref/c_trace.html#sqlitetraceclose](c3ref/c_trace.md#sqlitetraceclose) [c3ref/c_txn_none.html](c3ref/c_txn_none.md) [c3ref/collation_needed.html](c3ref/collation_needed.md) [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/commit_hook.html](c3ref/commit_hook.md) [c3ref/context_db_handle.html](c3ref/context_db_handle.md) [c3ref/create_collation.html](c3ref/create_collation.md) [c3ref/create_function.html](c3ref/create_function.md) [c3ref/create_module.html](c3ref/create_module.md) [c3ref/data_directory.html](c3ref/data_directory.md) [c3ref/db_cacheflush.html](c3ref/db_cacheflush.md) [c3ref/db_config.html](c3ref/db_config.md) [c3ref/db_handle.html](c3ref/db_handle.md) [c3ref/db_mutex.html](c3ref/db_mutex.md) [c3ref/db_status.html](c3ref/db_status.md) [c3ref/deserialize.html](c3ref/deserialize.md) [c3ref/enable_shared_cache.html](c3ref/enable_shared_cache.md) [c3ref/errcode.html](c3ref/errcode.md) [c3ref/exec.html](c3ref/exec.md) [c3ref/get_clientdata.html](c3ref/get_clientdata.md) [c3ref/interrupt.html](c3ref/interrupt.md) [c3ref/limit.html](c3ref/limit.md) [c3ref/module.html](c3ref/module.md) [c3ref/next_stmt.html](c3ref/next_stmt.md) [c3ref/open.html](c3ref/open.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/progress_handler.html](c3ref/progress_handler.md) [c3ref/serialize.html](c3ref/serialize.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [c3ref/snapshot.html](c3ref/snapshot.md) [c3ref/snapshot_get.html](c3ref/snapshot_get.md) [c3ref/snapshot_open.html](c3ref/snapshot_open.md) [c3ref/table_column_metadata.html](c3ref/table_column_metadata.md) [c3ref/temp_directory.html](c3ref/temp_directory.md) [c3ref/trace_v2.html](c3ref/trace_v2.md) [c3ref/update_hook.html](c3ref/update_hook.md) [c3ref/value_blob.html](c3ref/value_blob.md) [c3ref/vtab_config.html](c3ref/vtab_config.md) [c3ref/wal_autocheckpoint.html](c3ref/wal_autocheckpoint.md) [c3ref/wal_checkpoint.html](c3ref/wal_checkpoint.md) [c3ref/wal_checkpoint_v2.html](c3ref/wal_checkpoint_v2.md) [capi3ref.html#SQLITE_TXN_NONE](capi3ref.md#SQLITE_TXN_NONE) [capi3ref.html#sqlite3_auto_extension](capi3ref.md#sqlite3_auto_extension) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_blob_write](capi3ref.md#sqlite3_blob_write) [capi3ref.html#sqlite3_busy_handler](capi3ref.md#sqlite3_busy_handler) [capi3ref.html#sqlite3_busy_timeout](capi3ref.md#sqlite3_busy_timeout) [capi3ref.html#sqlite3_collation_needed](capi3ref.md#sqlite3_collation_needed) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_commit_hook](capi3ref.md#sqlite3_commit_hook) [capi3ref.html#sqlite3_context_db_handle](capi3ref.md#sqlite3_context_db_handle) [capi3ref.html#sqlite3_create_collation](capi3ref.md#sqlite3_create_collation) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [capi3ref.html#sqlite3_create_module](capi3ref.md#sqlite3_create_module) [capi3ref.html#sqlite3_data_directory](capi3ref.md#sqlite3_data_directory) [capi3ref.html#sqlite3_db_cacheflush](capi3ref.md#sqlite3_db_cacheflush) [capi3ref.html#sqlite3_db_config](capi3ref.md#sqlite3_db_config) [capi3ref.html#sqlite3_db_handle](capi3ref.md#sqlite3_db_handle) [capi3ref.html#sqlite3_db_mutex](capi3ref.md#sqlite3_db_mutex) [capi3ref.html#sqlite3_db_status](capi3ref.md#sqlite3_db_status) [capi3ref.html#sqlite3_deserialize](capi3ref.md#sqlite3_deserialize) [capi3ref.html#sqlite3_enable_shared_cache](capi3ref.md#sqlite3_enable_shared_cache) [capi3ref.html#sqlite3_errcode](capi3ref.md#sqlite3_errcode) [capi3ref.html#sqlite3_exec](capi3ref.md#sqlite3_exec) [capi3ref.html#sqlite3_get_clientdata](capi3ref.md#sqlite3_get_clientdata) [capi3ref.html#sqlite3_interrupt](capi3ref.md#sqlite3_interrupt) [capi3ref.html#sqlite3_limit](capi3ref.md#sqlite3_limit) [capi3ref.html#sqlite3_module](capi3ref.md#sqlite3_module) [capi3ref.html#sqlite3_next_stmt](capi3ref.md#sqlite3_next_stmt) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite) [capi3ref.html#sqlite3_progress_handler](capi3ref.md#sqlite3_progress_handler) [capi3ref.html#sqlite3_serialize](capi3ref.md#sqlite3_serialize) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlite3_snapshot](capi3ref.md#sqlite3_snapshot) [capi3ref.html#sqlite3_snapshot_get](capi3ref.md#sqlite3_snapshot_get) [capi3ref.html#sqlite3_snapshot_open](capi3ref.md#sqlite3_snapshot_open) [capi3ref.html#sqlite3_table_column_metadata](capi3ref.md#sqlite3_table_column_metadata) [capi3ref.html#sqlite3_temp_directory](capi3ref.md#sqlite3_temp_directory) [capi3ref.html#sqlite3_trace_v2](capi3ref.md#sqlite3_trace_v2) [capi3ref.html#sqlite3_update_hook](capi3ref.md#sqlite3_update_hook) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [capi3ref.html#sqlite3_vtab_config](capi3ref.md#sqlite3_vtab_config) [capi3ref.html#sqlite3_wal_autocheckpoint](capi3ref.md#sqlite3_wal_autocheckpoint) [capi3ref.html#sqlite3_wal_checkpoint](capi3ref.md#sqlite3_wal_checkpoint) [capi3ref.html#sqlite3_wal_checkpoint_v2](capi3ref.md#sqlite3_wal_checkpoint_v2) [capi3ref.html#sqlite3backupinit](capi3ref.md#sqlite3backupinit) [capi3ref.html#sqlite3backuppagecount](capi3ref.md#sqlite3backuppagecount) [capi3ref.html#sqlite3backupstep](capi3ref.md#sqlite3backupstep) [capi3ref.html#sqliteconfiglookaside](capi3ref.md#sqliteconfiglookaside) [capi3ref.html#sqliteconfigmultithread](capi3ref.md#sqliteconfigmultithread) [capi3ref.html#sqliteconfigserialized](capi3ref.md#sqliteconfigserialized) [capi3ref.html#sqlitetraceclose](capi3ref.md#sqlitetraceclose) [changes.html#version_3_5_8](changes.md#version_3_5_8) [changes.html#version_3_6_1](changes.md#version_3_6_1) [changes.html#version_3_7_17](changes.md#version_3_7_17) [cintro.html](cintro.md) [compile.html#default_lookaside](compile.md#default_lookaside) [compile.html#enable_fts3_tokenizer](compile.md#enable_fts3_tokenizer) [compile.html#threadsafe](compile.md#threadsafe) [custombuild.html](custombuild.md) [fileformat2.html#ffschema](fileformat2.md#ffschema) [foreignkeys.html#fk_enable](foreignkeys.md#fk_enable) [fullsql.html](fullsql.md) [imposter.html](imposter.md) [lang_analyze.html#autoanalyze](lang_analyze.md#autoanalyze) [lang_attach.html](lang_attach.md) [lang_createview.html](lang_createview.md) [lang_expr.html#varparam](lang_expr.md#varparam) [lang_vacuum.html#vacuuminto](lang_vacuum.md#vacuuminto) [malloc.html](malloc.md) [malloc.html#lookaside](malloc.md#lookaside) [malloc.html#memstatus](malloc.md#memstatus) [malloc.html#nofrag](malloc.md#nofrag) [news.html](news.md) [oldnews.html](oldnews.md) [pragma.html#pragma_journal_mode](pragma.md#pragma_journal_mode) [pragma.html#pragma_legacy_alter_table](pragma.md#pragma_legacy_alter_table) [pragma.html#pragma_mmap_size](pragma.md#pragma_mmap_size) [releaselog/3_5_8.html](releaselog/3_5_8.md) [releaselog/3_6_1.html](releaselog/3_6_1.md) [releaselog/3_7_17.html](releaselog/3_7_17.md) [rescode.html#abort](rescode.md#abort) [rescode.html#busy](rescode.md#busy) [rescode.html#busy_snapshot](rescode.md#busy_snapshot) [rescode.html#locked](rescode.md#locked) [rescode.html#pve](rescode.md#pve) [schematab.html](schematab.md) [security.html#baddb](security.md#baddb) [stmt.html](stmt.md) [tempfiles.html#superjrnl](tempfiles.md#superjrnl) [tempfiles.html#tempdb](tempfiles.md#tempdb) [threadsafe.html](threadsafe.md) [unlock_notify.html](unlock_notify.md) [useovernet.html](useovernet.md) [vtab.html](vtab.md) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab) [vtab.html#xcreate](vtab.md#xcreate) [vtablist.html](vtablist.md) [wal.html#walfile](wal.md#walfile)
- database connections → [c3ref/backup_finish.html#sqlite3backupinit](c3ref/backup_finish.md#sqlite3backupinit) [c3ref/c_config_covering_index_scan.html#sqliteconfigmultithread](c3ref/c_config_covering_index_scan.md#sqliteconfigmultithread) [c3ref/c_config_covering_index_scan.html#sqliteconfigserialized](c3ref/c_config_covering_index_scan.md#sqliteconfigserialized) [c3ref/initialize.html](c3ref/initialize.md) [c3ref/snapshot.html](c3ref/snapshot.md) [capi3ref.html#sqlite3_initialize](capi3ref.md#sqlite3_initialize) [capi3ref.html#sqlite3_snapshot](capi3ref.md#sqlite3_snapshot) [capi3ref.html#sqlite3backupinit](capi3ref.md#sqlite3backupinit) [capi3ref.html#sqliteconfigmultithread](capi3ref.md#sqliteconfigmultithread) [capi3ref.html#sqliteconfigserialized](capi3ref.md#sqliteconfigserialized) [cintro.html](cintro.md) [cli.html#dotconn](cli.md#dotconn) [compile.html#default_automatic_index](compile.md#default_automatic_index) [compile.html#threadsafe](compile.md#threadsafe) [compile.html#yystackdepth](compile.md#yystackdepth) [custombuild.html](custombuild.md) [dbstat.html](dbstat.md) [isolation.html](isolation.md) [malloc.html](malloc.md) [malloc.html#lookaside](malloc.md#lookaside) [malloc.html#nofrag](malloc.md#nofrag) [rescode.html#protocol](rescode.md#protocol) [uri.html#urinolock](uri.md#urinolock) [vfs.html](vfs.md)
- database corruption caused by inconsistent use of 83 filenames → [howtocorrupt.html#delhotjrnl](howtocorrupt.md#delhotjrnl) [shortnames.html](shortnames.md)
- database filename aliasing → [changes.html#version_3_7_17](changes.md#version_3_7_17) [errlog.html](errlog.md) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- database header → [changes.html#version_3_7_17](changes.md#version_3_7_17) [pragma.html#pragma_application_id](pragma.md#pragma_application_id) [pragma.html#pragma_schema_version](pragma.md#pragma_schema_version) [pragma.html#pragma_user_version](pragma.md#pragma_user_version) [releaselog/3_7_17.html](releaselog/3_7_17.md) [rsync.html#intro](rsync.md#intro) [wal.html#bkwrds](wal.md#bkwrds)
- datatype → [faq.html#q3](faq.md#q3) [faq.html#q4](faq.md#q4) [flextypegood.html](flextypegood.md) [lang_corefunc.html#typeof](lang_corefunc.md#typeof) [lang_expr.html#collateop](lang_expr.md#collateop) [quirks.html](quirks.md) [stricttables.html](stricttables.md)
- Date And Time Functions → [changes.html#version_3_8_1](changes.md#version_3_8_1) [datatype3.html#datetime](datatype3.md#datetime) [releaselog/3_8_1.html](releaselog/3_8_1.md)
- date and time functions → [changes.html#version_3_10_0](changes.md#version_3_10_0) [changes.html#version_3_16_0](changes.md#version_3_16_0) [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_38_0](changes.md#version_3_38_0) [changes.html#version_3_38_1](changes.md#version_3_38_1) [changes.html#version_3_42_0](changes.md#version_3_42_0) [changes.html#version_3_43_0](changes.md#version_3_43_0) [changes.html#version_3_46_0](changes.md#version_3_46_0) [compile.html#gmtime_r](compile.md#gmtime_r) [compile.html#localtime_r](compile.md#localtime_r) [compile.html#localtime_s](compile.md#localtime_s) [datatype3.html#datetime](datatype3.md#datetime) [deterministic.html#dtexception](deterministic.md#dtexception) [news.html](news.md) [quirks.html](quirks.md) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md) [releaselog/3_42_0.html](releaselog/3_42_0.md) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md) [releaselog/3_46_0.html](releaselog/3_46_0.md) [releaselog/3_46_1.html](releaselog/3_46_1.md)
- date/time special case → [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- datefunc → [lang.html](lang.md) [lang_corefunc.html](lang_corefunc.md) [lang_expr.html#\*funcinexpr](lang_expr.md#*funcinexpr)
- datetime → [lang_datefunc.html#subsec](lang_datefunc.md#subsec)
- datetime SQL function → [optoverview.html#leftjoinreduction](optoverview.md#leftjoinreduction)
- DBCONFIG arguments → [c3ref/c_dbconfig_defensive.html#sqlitedbconfiglookaside](c3ref/c_dbconfig_defensive.md#sqlitedbconfiglookaside) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigmaindbname](c3ref/c_dbconfig_defensive.md#sqlitedbconfigmaindbname) [capi3ref.html#sqlitedbconfiglookaside](capi3ref.md#sqlitedbconfiglookaside) [capi3ref.html#sqlitedbconfigmaindbname](capi3ref.md#sqlitedbconfigmaindbname)
- dbhash.exe → [changes.html#version_3_14](changes.md#version_3_14) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- dbsqlfuzz → [testing.html#fuzzcheck](testing.md#fuzzcheck) [testing.html#tension](testing.md#tension)
- dbstat → [amalgamation.html](amalgamation.md) [vtablist.html](vtablist.md)
- DBSTAT aggregated mode → [changes.html#version_3_31_0](changes.md#version_3_31_0) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- DBSTAT virtual table → [changes.html#version_3_31_0](changes.md#version_3_31_0) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- dbstat virtual table → [changes.html#version_3_8_10](changes.md#version_3_8_10) [changes.html#version_3_8_10_1](changes.md#version_3_8_10_1) [changes.html#version_3_9_0](changes.md#version_3_9_0) [compile.html#enable_dbstat_vtab](compile.md#enable_dbstat_vtab) [howtocompile.html#cli](howtocompile.md#cli) [oldnews.html](oldnews.md) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md) [sqlanalyze.html](sqlanalyze.md) [vtab.html](vtab.md) [vtab.html#epovtab](vtab.md#epovtab)
- debugging memory allocator → [compile.html#memdebug](compile.md#memdebug) [compile.html#zero_malloc](compile.md#zero_malloc)
- decimal extension → [changes.html#version_3_33_0](changes.md#version_3_33_0) [changes.html#version_3_43_0](changes.md#version_3_43_0) [cli.html#miscfeatures](cli.md#miscfeatures) [lang_aggfunc.html#sumunc](lang_aggfunc.md#sumunc) [printf.html](printf.md) [releaselog/3_33_0.html](releaselog/3_33_0.md) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md)
- DEFAULT clauses → [c3ref/c_deterministic.html#sqlitedirectonly](c3ref/c_deterministic.md#sqlitedirectonly) [c3ref/c_deterministic.html#sqliteinnocuous](c3ref/c_deterministic.md#sqliteinnocuous) [capi3ref.html#sqlitedirectonly](capi3ref.md#sqlitedirectonly) [capi3ref.html#sqliteinnocuous](capi3ref.md#sqliteinnocuous) [pragma.html#pragma_trusted_schema](pragma.md#pragma_trusted_schema) [stricttables.html](stricttables.md)
- default column value → [lang_insert.html](lang_insert.md)
- default memory allocator → [compile.html#zero_malloc](compile.md#zero_malloc) [malloc.html#memsysx](malloc.md#memsysx)
- default value → [fileformat2.html#serialtype](fileformat2.md#serialtype) [gencol.html#vgc\*](gencol.md#vgc*) [lang_insert.html](lang_insert.md)
- default_cache_size pragma → [fileformat2.html#schemaformat](fileformat2.md#schemaformat)
- defense against dark arts → [appfileformat.html](appfileformat.md) [cves.html](cves.md) [news.html](news.md)
- defensive code → [testing.html#tension](testing.md#tension)
- defer_foreign_keys pragma → [changes.html#version_3_8_0](changes.md#version_3_8_0) [foreignkeys.html#fk_enable](foreignkeys.md#fk_enable) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md)
- degrees → [lang_mathfunc.html](lang_mathfunc.md)
- DELETE → [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [c3ref/total_changes.html](c3ref/total_changes.md) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlite3_total_changes](capi3ref.md#sqlite3_total_changes) [changes.html#version_3_12_2](changes.md#version_3_12_2) [changes.html#version_3_13_0](changes.md#version_3_13_0) [changes.html#version_3_14_2](changes.md#version_3_14_2) [changes.html#version_3_35_0](changes.md#version_3_35_0) [changes.html#version_3_6_4](changes.md#version_3_6_4) [cli.html#selftest](cli.md#selftest) [compile.html#enable_update_delete_limit](compile.md#enable_update_delete_limit) [foreignkeys.html#fk_actions](foreignkeys.md#fk_actions) [fts3.html#fts4](fts3.md#fts4) [fts5.html](fts5.md) [fullsql.html](fullsql.md) [isolation.html](isolation.md) [lang.html](lang.md) [lang_analyze.html#statanal](lang_analyze.md#statanal) [lang_createtable.html#notnullconst](lang_createtable.md#notnullconst) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_droptable.html](lang_droptable.md) [lang_indexedby.html](lang_indexedby.md) [lang_returning.html](lang_returning.md) [lang_with.html](lang_with.md) [pragma.html#pragma_count_changes](pragma.md#pragma_count_changes) [pragma.html#pragma_writable_schema](pragma.md#pragma_writable_schema) [rbu.html](rbu.md) [rbu.html#rbu_updates](rbu.md#rbu_updates) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [releaselog/3_6_4.html](releaselog/3_6_4.md) [rtree.html](rtree.md) [vtab.html](vtab.md)
- delete-stmt → [lang_createtrigger.html](lang_createtrigger.md) [lang_delete.html](lang_delete.md)
- delete-stmt-limited → [lang_delete.html](lang_delete.md)
- deleting a hot journal → [shortnames.html#db83corrupt](shortnames.md#db83corrupt)
- deprecated → [c3ref/aggregate_count.html](c3ref/aggregate_count.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_aggregate_count](capi3ref.md#sqlite3_aggregate_count)
- DESC → [fullsql.html](fullsql.md)
- descending indexes → [changes.html#version_3_14](changes.md#version_3_14) [fileformat2.html#schemaformat](fileformat2.md#schemaformat) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- descending indices → [changes.html#version_3_7_10](changes.md#version_3_7_10) [compile.html#default_file_format](compile.md#default_file_format) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- DETACH → [c3ref/db_filename.html](c3ref/db_filename.md) [c3ref/db_name.html](c3ref/db_name.md) [c3ref/stmt_readonly.html](c3ref/stmt_readonly.md) [capi3ref.html#sqlite3_db_filename](capi3ref.md#sqlite3_db_filename) [capi3ref.html#sqlite3_db_name](capi3ref.md#sqlite3_db_name) [capi3ref.html#sqlite3_stmt_readonly](capi3ref.md#sqlite3_stmt_readonly) [changes.html#version_3_21_0](changes.md#version_3_21_0) [compile.html#omit_attach](compile.md#omit_attach) [releaselog/3_21_0.html](releaselog/3_21_0.md) [tempfiles.html#tempdb](tempfiles.md#tempdb)
- DETACH DATABASE → [lang.html](lang.md) [lang_attach.html](lang_attach.md)
- detach-stmt → [lang_detach.html](lang_detach.md)
- deterministic functions → [expridx.html](expridx.md) [gencol.html#vgc\*](gencol.md#vgc*) [howtocorrupt.html#cfgerr](howtocorrupt.md#cfgerr) [staleexpridx.html](staleexpridx.md)
- deterministic SQL functions → [changes.html#version_3_15_0](changes.md#version_3_15_0) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md)
- DISTINCT → [changes.html#version_3_8_6](changes.md#version_3_8_6) [lang_select.html#simpleselect](lang_select.md#simpleselect) [releaselog/3_8_6.html](releaselog/3_8_6.md)
- doclist → [keyword_index.html](keyword_index.md) [sitemap.html](sitemap.md)
- dot-command → [cli.html#xtraargs](cli.md#xtraargs) [climode.html](climode.md)
- dot-commands → [changes.html#version_3_10_0](changes.md#version_3_10_0) [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_15_0](changes.md#version_3_15_0) [changes.html#version_3_37_0](changes.md#version_3_37_0) [changes.html#version_3_53_0](changes.md#version_3_53_0) [cli.html#dotconn](cli.md#dotconn) [cli.html#dotread](cli.md#dotread) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- double-quoted string literal → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigdqsddl](c3ref/c_dbconfig_defensive.md#sqlitedbconfigdqsddl) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigdqsdml](c3ref/c_dbconfig_defensive.md#sqlitedbconfigdqsdml) [capi3ref.html#sqlitedbconfigdqsddl](capi3ref.md#sqlitedbconfigdqsddl) [capi3ref.html#sqlitedbconfigdqsdml](capi3ref.md#sqlitedbconfigdqsdml) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_29_0](changes.md#version_3_29_0) [compile.html#dqs](compile.md#dqs) [compile.html#rcmd](compile.md#rcmd) [news.html](news.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_29_0.html](releaselog/3_29_0.md)
- double-quoted string literals → [changes.html#version_3_46_1](changes.md#version_3_46_1) [releaselog/3_46_1.html](releaselog/3_46_1.md)
- double-quoted string misfeature → [changes.html#version_3_41_0](changes.md#version_3_41_0) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- download page → [getthecode.html](getthecode.md) [howtocompile.html#amal](howtocompile.md#amal) [howtocompile.html#cli](howtocompile.md#cli)
- drop column → [lang_altertable.html#otheralter](lang_altertable.md#otheralter)
- DROP INDEX → [lang.html](lang.md) [lang_createindex.html](lang_createindex.md) [lang_naming.html](lang_naming.md) [partialindex.html](partialindex.md)
- DROP TABLE → [changes.html#version_3_7_9](changes.md#version_3_7_9) [foreignkeys.html](foreignkeys.md) [foreignkeys.html#fk_actions](foreignkeys.md#fk_actions) [fts3.html#fts4](fts3.md#fts4) [lang.html](lang.md) [lang_altertable.html#otheralter](lang_altertable.md#otheralter) [lang_analyze.html#statanal](lang_analyze.md#statanal) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createvtab.html](lang_createvtab.md) [lang_naming.html](lang_naming.md) [releaselog/3_7_9.html](releaselog/3_7_9.md) [rescode.html#locked](rescode.md#locked) [rtree.html](rtree.md) [unionvtab.html](unionvtab.md) [vtab.html](vtab.md) [vtab.html#sqlite3_module.xDestroy](vtab.md#sqlite3_module.xDestroy)
- DROP TRIGGER → [compile.html#omit_trigger](compile.md#omit_trigger) [lang.html](lang.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_naming.html](lang_naming.md)
- DROP VIEW → [compile.html#omit_view](compile.md#omit_view) [lang.html](lang.md) [lang_altertable.html#otheralter](lang_altertable.md#otheralter) [lang_createview.html](lang_createview.md) [lang_naming.html](lang_naming.md)
- drop-index-stmt → [lang_dropindex.html](lang_dropindex.md)
- drop-table-stmt → [lang_droptable.html](lang_droptable.md)
- drop-trigger-stmt → [lang_droptrigger.html](lang_droptrigger.md)
- drop-view-stmt → [lang_dropview.html](lang_dropview.md)
- dynamic typing → [faq.html#q2](faq.md#q2) [faq.html#q3](faq.md#q3) [lang_createtable.html#tablecoldef](lang_createtable.md#tablecoldef)
- edit SQL function → [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_22_0.html](releaselog/3_22_0.md)
- editdist3 → [spellfix1.html#configeditdist](spellfix1.md#configeditdist)
- encoding → [fts3.html#limitations](fts3.md#limitations) [lang_expr.html#castexpr](lang_expr.md#castexpr)
- enhanced query syntax → [fts3.html#compiling_and_enabling_fts3_and_fts4](fts3.md#compiling_and_enabling_fts3_and_fts4)
- eponymous virtual table → [changes.html#version_3_14](changes.md#version_3_14) [dbstat.html](dbstat.md) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [vtab.html#tabfunc2](vtab.md#tabfunc2) [vtab.html#xconnect](vtab.md#xconnect) [vtab.html#xcreate](vtab.md#xcreate)
- eponymous virtual tables → [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_9_0](changes.md#version_3_9_0) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md) [vtab.html#xshadowname](vtab.md#xshadowname)
- eponymous-only virtual table → [dbpage.html](dbpage.md) [memstat.html](memstat.md) [stmt.html](stmt.md) [vtab.html#xcreate](vtab.md#xcreate)
- eponymous-only virtual tables → [bytecodevtab.html](bytecodevtab.md)
- eqp-or-opt → [changes.html#version_3_24_0](changes.md#version_3_24_0) [releaselog/3_24_0.html](releaselog/3_24_0.md)
- error code → [35to36.html](35to36.md) [backup.html](backup.md) [c3ref/auto_extension.html](c3ref/auto_extension.md) [c3ref/backup_finish.html#sqlite3backupfinish](c3ref/backup_finish.md#sqlite3backupfinish) [c3ref/backup_finish.html#sqlite3backupstep](c3ref/backup_finish.md#sqlite3backupstep) [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/blob_read.html](c3ref/blob_read.md) [c3ref/blob_write.html](c3ref/blob_write.md) [c3ref/c_config_covering_index_scan.html](c3ref/c_config_covering_index_scan.md) [c3ref/c_dbconfig_defensive.html](c3ref/c_dbconfig_defensive.md) [c3ref/config.html](c3ref/config.md) [c3ref/db_cacheflush.html](c3ref/db_cacheflush.md) [c3ref/db_status.html](c3ref/db_status.md) [c3ref/enable_shared_cache.html](c3ref/enable_shared_cache.md) [c3ref/finalize.html](c3ref/finalize.md) [c3ref/initialize.html](c3ref/initialize.md) [c3ref/open.html](c3ref/open.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/reset.html](c3ref/reset.md) [c3ref/snapshot_open.html](c3ref/snapshot_open.md) [c3ref/status.html](c3ref/status.md) [c3ref/table_column_metadata.html](c3ref/table_column_metadata.md) [capi3ref.html#SQLITE_CONFIG_COVERING_INDEX_SCAN](capi3ref.md#SQLITE_CONFIG_COVERING_INDEX_SCAN) [capi3ref.html#SQLITE_DBCONFIG_DEFENSIVE](capi3ref.md#SQLITE_DBCONFIG_DEFENSIVE) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_auto_extension](capi3ref.md#sqlite3_auto_extension) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_blob_read](capi3ref.md#sqlite3_blob_read) [capi3ref.html#sqlite3_blob_write](capi3ref.md#sqlite3_blob_write) [capi3ref.html#sqlite3_config](capi3ref.md#sqlite3_config) [capi3ref.html#sqlite3_db_cacheflush](capi3ref.md#sqlite3_db_cacheflush) [capi3ref.html#sqlite3_db_status](capi3ref.md#sqlite3_db_status) [capi3ref.html#sqlite3_enable_shared_cache](capi3ref.md#sqlite3_enable_shared_cache) [capi3ref.html#sqlite3_finalize](capi3ref.md#sqlite3_finalize) [capi3ref.html#sqlite3_initialize](capi3ref.md#sqlite3_initialize) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_reset](capi3ref.md#sqlite3_reset) [capi3ref.html#sqlite3_snapshot_open](capi3ref.md#sqlite3_snapshot_open) [capi3ref.html#sqlite3_status](capi3ref.md#sqlite3_status) [capi3ref.html#sqlite3_table_column_metadata](capi3ref.md#sqlite3_table_column_metadata) [capi3ref.html#sqlite3backupfinish](capi3ref.md#sqlite3backupfinish) [capi3ref.html#sqlite3backupstep](capi3ref.md#sqlite3backupstep) [vtab.html#xcolumn](vtab.md#xcolumn) [vtab.html#xfilter](vtab.md#xfilter) [vtab.html#xnext](vtab.md#xnext) [vtab.html#xrename](vtab.md#xrename) [vtab.html#xrowid](vtab.md#xrowid) [vtab.html#xupdate](vtab.md#xupdate)
- error codes → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/step.html](c3ref/step.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step)
- error log → [c3ref/c_config_covering_index_scan.html#sqliteconfiglog](c3ref/c_config_covering_index_scan.md#sqliteconfiglog) [c3ref/log.html](c3ref/log.md) [capi3ref.html#sqlite3_log](capi3ref.md#sqlite3_log) [capi3ref.html#sqliteconfiglog](capi3ref.md#sqliteconfiglog) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_48_0](changes.md#version_3_48_0) [changes.html#version_3_7_17](changes.md#version_3_7_17) [cintro.html](cintro.md) [howtocorrupt.html#alias](howtocorrupt.md#alias) [howtocorrupt.html#unlink](howtocorrupt.md#unlink) [optoverview.html#autoindex](optoverview.md#autoindex) [quirks.html#dblquote](quirks.md#dblquote) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_48_0.html](releaselog/3_48_0.md) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- ESCAPE → [changes.html#version_3_21_0](changes.md#version_3_21_0) [changes.html#version_3_32_0](changes.md#version_3_32_0) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- eval method → [quickstart.html](quickstart.md)
- EXCLUDE clause → [changes.html#version_3_28_0](changes.md#version_3_28_0) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- EXCLUSIVE lock → [pragma.html#pragma_cache_spill](pragma.md#pragma_cache_spill)
- exclusive locking mode → [pragma.html#pragma_journal_size_limit](pragma.md#pragma_journal_size_limit) [walformat.html#shm](walformat.md#shm)
- exp → [lang_mathfunc.html](lang_mathfunc.md)
- experimental → [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [session.html#sqlite3_rebaser](session.md#sqlite3_rebaser) [session.html#sqlite3rebaser_configure](session.md#sqlite3rebaser_configure) [session.html#sqlite3rebaser_create](session.md#sqlite3rebaser_create) [session.html#sqlite3rebaser_delete](session.md#sqlite3rebaser_delete) [session.html#sqlite3rebaser_rebase](session.md#sqlite3rebaser_rebase) [session/rebaser.html](session/rebaser.md) [session/sqlite3rebaser_configure.html](session/sqlite3rebaser_configure.md) [session/sqlite3rebaser_create.html](session/sqlite3rebaser_create.md) [session/sqlite3rebaser_delete.html](session/sqlite3rebaser_delete.md) [session/sqlite3rebaser_rebase.html](session/sqlite3rebaser_rebase.md)
- experimental memory allocators → [changes.html#version_3_6_5](changes.md#version_3_6_5) [releaselog/3_6_5.html](releaselog/3_6_5.md)
- EXPLAIN → [c3ref/stmt_explain.html](c3ref/stmt_explain.md) [c3ref/stmt_readonly.html](c3ref/stmt_readonly.md) [capi3ref.html#sqlite3_stmt_explain](capi3ref.md#sqlite3_stmt_explain) [capi3ref.html#sqlite3_stmt_readonly](capi3ref.md#sqlite3_stmt_readonly) [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_13_0](changes.md#version_3_13_0) [changes.html#version_3_14_2](changes.md#version_3_14_2) [changes.html#version_3_28_0](changes.md#version_3_28_0) [changes.html#version_3_8_2](changes.md#version_3_8_2) [changes.html#version_3_8_3](changes.md#version_3_8_3) [compile.html#enable_explain_comments](compile.md#enable_explain_comments) [compile.html#enable_unknown_sql_function](compile.md#enable_unknown_sql_function) [compile.html#omit_explain](compile.md#omit_explain) [debugging.html](debugging.md) [eqp.html](eqp.md) [howitworks.html](howitworks.md) [howtocompile.html#cli](howtocompile.md#cli) [lang.html](lang.md) [opcode.html](opcode.md) [opcode.html#subprog](opcode.md#subprog) [optoverview.html#or_opt](optoverview.md#or_opt) [pragma.html](pragma.md) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_28_0.html](releaselog/3_28_0.md) [releaselog/3_8_2.html](releaselog/3_8_2.md) [releaselog/3_8_3.html](releaselog/3_8_3.md)
- EXPLAIN QUERY PLAN → [c3ref/c_scanstat_est.html#sqlitescanstatexplain](c3ref/c_scanstat_est.md#sqlitescanstatexplain) [c3ref/c_scanstat_est.html#sqlitescanstatparentid](c3ref/c_scanstat_est.md#sqlitescanstatparentid) [c3ref/c_scanstat_est.html#sqlitescanstatselectid](c3ref/c_scanstat_est.md#sqlitescanstatselectid) [c3ref/index_info.html](c3ref/index_info.md) [c3ref/stmt_explain.html](c3ref/stmt_explain.md) [c3ref/stmt_readonly.html](c3ref/stmt_readonly.md) [c3ref/stmt_scanstatus.html](c3ref/stmt_scanstatus.md) [capi3ref.html#sqlite3_index_info](capi3ref.md#sqlite3_index_info) [capi3ref.html#sqlite3_stmt_explain](capi3ref.md#sqlite3_stmt_explain) [capi3ref.html#sqlite3_stmt_readonly](capi3ref.md#sqlite3_stmt_readonly) [capi3ref.html#sqlite3_stmt_scanstatus](capi3ref.md#sqlite3_stmt_scanstatus) [capi3ref.html#sqlitescanstatexplain](capi3ref.md#sqlitescanstatexplain) [capi3ref.html#sqlitescanstatparentid](capi3ref.md#sqlitescanstatparentid) [capi3ref.html#sqlitescanstatselectid](capi3ref.md#sqlitescanstatselectid) [changes.html#version_3_13_0](changes.md#version_3_13_0) [changes.html#version_3_24_0](changes.md#version_3_24_0) [changes.html#version_3_36_0](changes.md#version_3_36_0) [changes.html#version_3_41_0](changes.md#version_3_41_0) [changes.html#version_3_48_0](changes.md#version_3_48_0) [changes.html#version_3_7_4](changes.md#version_3_7_4) [changes.html#version_3_8_0](changes.md#version_3_8_0) [cli.html#expert](cli.md#expert) [compile.html#enable_unknown_sql_function](compile.md#enable_unknown_sql_function) [debugging.html](debugging.md) [oldnews.html](oldnews.md) [pragma.html](pragma.md) [profile.html](profile.md) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_24_0.html](releaselog/3_24_0.md) [releaselog/3_36_0.html](releaselog/3_36_0.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md) [releaselog/3_48_0.html](releaselog/3_48_0.md) [releaselog/3_7_4.html](releaselog/3_7_4.md) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md)
- explain query plan → [lang_explain.html](lang_explain.md)
- export to excel → [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_22_0.html](releaselog/3_22_0.md)
- expr → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- expression → [lang.html](lang.md)
- expression affinity → [lang_createtable.html#createtabas](lang_createtable.md#createtabas)
- expression index → [c3ref/c_deterministic.html#sqliteresultsubtype](c3ref/c_deterministic.md#sqliteresultsubtype) [capi3ref.html#sqliteresultsubtype](capi3ref.md#sqliteresultsubtype) [changes.html#version_3_24_0](changes.md#version_3_24_0) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_27_1](changes.md#version_3_27_1) [deterministic.html](deterministic.md) [deterministic.html#dtexception](deterministic.md#dtexception) [gencol.html#vgc\*](gencol.md#vgc*) [pragma.html#pragma_case_sensitive_like](pragma.md#pragma_case_sensitive_like) [pragma.html#pragma_index_info](pragma.md#pragma_index_info) [pragma.html#pragma_index_xinfo](pragma.md#pragma_index_xinfo) [releaselog/3_24_0.html](releaselog/3_24_0.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [staleexpridx.html](staleexpridx.md)
- expression indexes → [c3ref/c_deterministic.html#sqlitedirectonly](c3ref/c_deterministic.md#sqlitedirectonly) [c3ref/c_deterministic.html#sqliteinnocuous](c3ref/c_deterministic.md#sqliteinnocuous) [capi3ref.html#sqlitedirectonly](capi3ref.md#sqlitedirectonly) [capi3ref.html#sqliteinnocuous](capi3ref.md#sqliteinnocuous) [changes.html#version_3_40_0](changes.md#version_3_40_0) [pragma.html#pragma_trusted_schema](pragma.md#pragma_trusted_schema) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md)
- ext-v-prim → [rescode.html#abort_rollback](rescode.md#abort_rollback) [rescode.html#auth_user](rescode.md#auth_user) [rescode.html#busy_recovery](rescode.md#busy_recovery) [rescode.html#busy_snapshot](rescode.md#busy_snapshot) [rescode.html#cantopen_convpath](rescode.md#cantopen_convpath) [rescode.html#cantopen_fullpath](rescode.md#cantopen_fullpath) [rescode.html#cantopen_isdir](rescode.md#cantopen_isdir) [rescode.html#constraint_check](rescode.md#constraint_check) [rescode.html#constraint_commithook](rescode.md#constraint_commithook) [rescode.html#constraint_datatype](rescode.md#constraint_datatype) [rescode.html#constraint_foreignkey](rescode.md#constraint_foreignkey) [rescode.html#constraint_notnull](rescode.md#constraint_notnull) [rescode.html#constraint_pinned](rescode.md#constraint_pinned) [rescode.html#constraint_primarykey](rescode.md#constraint_primarykey) [rescode.html#constraint_rowid](rescode.md#constraint_rowid) [rescode.html#constraint_trigger](rescode.md#constraint_trigger) [rescode.html#constraint_unique](rescode.md#constraint_unique) [rescode.html#corrupt_vtab](rescode.md#corrupt_vtab) [rescode.html#ioerr_access](rescode.md#ioerr_access) [rescode.html#ioerr_checkreservedlock](rescode.md#ioerr_checkreservedlock) [rescode.html#ioerr_close](rescode.md#ioerr_close) [rescode.html#ioerr_convpath](rescode.md#ioerr_convpath) [rescode.html#ioerr_corruptfs](rescode.md#ioerr_corruptfs) [rescode.html#ioerr_data](rescode.md#ioerr_data) [rescode.html#ioerr_delete](rescode.md#ioerr_delete) [rescode.html#ioerr_delete_noent](rescode.md#ioerr_delete_noent) [rescode.html#ioerr_dir_fsync](rescode.md#ioerr_dir_fsync) [rescode.html#ioerr_fstat](rescode.md#ioerr_fstat) [rescode.html#ioerr_fsync](rescode.md#ioerr_fsync) [rescode.html#ioerr_gettemppath](rescode.md#ioerr_gettemppath) [rescode.html#ioerr_lock](rescode.md#ioerr_lock) [rescode.html#ioerr_mmap](rescode.md#ioerr_mmap) [rescode.html#ioerr_rdlock](rescode.md#ioerr_rdlock) [rescode.html#ioerr_read](rescode.md#ioerr_read) [rescode.html#ioerr_seek](rescode.md#ioerr_seek) [rescode.html#ioerr_shmmap](rescode.md#ioerr_shmmap) [rescode.html#ioerr_shmopen](rescode.md#ioerr_shmopen) [rescode.html#ioerr_shmsize](rescode.md#ioerr_shmsize) [rescode.html#ioerr_short_read](rescode.md#ioerr_short_read) [rescode.html#ioerr_truncate](rescode.md#ioerr_truncate) [rescode.html#ioerr_unlock](rescode.md#ioerr_unlock) [rescode.html#ioerr_write](rescode.md#ioerr_write) [rescode.html#readonly_cantlock](rescode.md#readonly_cantlock) [rescode.html#readonly_dbmoved](rescode.md#readonly_dbmoved) [rescode.html#readonly_recovery](rescode.md#readonly_recovery) [rescode.html#readonly_rollback](rescode.md#readonly_rollback)
- extended error code → [c3ref/blob_read.html](c3ref/blob_read.md) [c3ref/blob_write.html](c3ref/blob_write.md) [c3ref/finalize.html](c3ref/finalize.md) [capi3ref.html#sqlite3_blob_read](capi3ref.md#sqlite3_blob_read) [capi3ref.html#sqlite3_blob_write](capi3ref.md#sqlite3_blob_write) [capi3ref.html#sqlite3_finalize](capi3ref.md#sqlite3_finalize) [errlog.html](errlog.md) [rescode.html#constraint](rescode.md#constraint)
- extended error codes → [c3ref/prepare.html](c3ref/prepare.md) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [rescode.html#notice](rescode.md#notice) [rescode.html#warning](rescode.md#warning) [unlock_notify.html](unlock_notify.md)
- extended result code → [c3ref/c_config_covering_index_scan.html#sqliteconfiglog](c3ref/c_config_covering_index_scan.md#sqliteconfiglog) [c3ref/errcode.html](c3ref/errcode.md) [capi3ref.html#sqlite3_errcode](capi3ref.md#sqlite3_errcode) [capi3ref.html#sqliteconfiglog](capi3ref.md#sqliteconfiglog)
- extended result code definitions → [c3ref/c_abort.html](c3ref/c_abort.md) [capi3ref.html#SQLITE_ABORT](capi3ref.md#SQLITE_ABORT) [rescode.html#extrc](rescode.md#extrc) [rescode.html#pve](rescode.md#pve)
- extended result codes → [c3ref/c_abort_rollback.html](c3ref/c_abort_rollback.md) [c3ref/extended_result_codes.html](c3ref/extended_result_codes.md) [c3ref/step.html](c3ref/step.md) [capi3ref.html#SQLITE_ABORT_ROLLBACK](capi3ref.md#SQLITE_ABORT_ROLLBACK) [capi3ref.html#sqlite3_extended_result_codes](capi3ref.md#sqlite3_extended_result_codes) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step)
- Extending FTS5 → [bindptr.html](bindptr.md) [changes.html#version_3_20_0](changes.md#version_3_20_0) [fts5.html#compiling_and_using_fts5](fts5.md#compiling_and_using_fts5) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- extension loading → [c3ref/enable_load_extension.html](c3ref/enable_load_extension.md) [capi3ref.html#sqlite3_enable_load_extension](capi3ref.md#sqlite3_enable_load_extension) [changes.html#version_3_7_17](changes.md#version_3_7_17) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- external content fts4 tables → [rbu.html#fts4_tables](rbu.md#fts4_tables)
- factored-select-stmt → [lang_select.html](lang_select.md)
- faster than the filesystem → [about.html](about.md) [aff_short.html](aff_short.md) [appfileformat.html](appfileformat.md) [features.html](features.md) [howitworks.html](howitworks.md) [index.html](index.md) [intern-v-extern-blob.html](intern-v-extern-blob.md) [whentouse.html#appfileformat](whentouse.md#appfileformat) [whentouse.html#container](whentouse.md#container) [whybytecode.html](whybytecode.md)
- file control → [c3ref/snapshot_recover.html](c3ref/snapshot_recover.md) [c3ref/total_changes.html](c3ref/total_changes.md) [capi3ref.html#sqlite3_snapshot_recover](capi3ref.md#sqlite3_snapshot_recover) [capi3ref.html#sqlite3_total_changes](capi3ref.md#sqlite3_total_changes) [wal.html#walfile](wal.md#walfile)
- file control opcode → [rescode.html#notfound](rescode.md#notfound)
- file control opcodes → [c3ref/file_control.html](c3ref/file_control.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html#sqlite3_file_control](capi3ref.md#sqlite3_file_control) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- file format → [about.html](about.md) [appfileformat.html](appfileformat.md) [arch.html](arch.md) [dbpage.html](dbpage.md) [formatchng.html](formatchng.md) [howitworks.html](howitworks.md) [imposter.html](imposter.md) [lts.html](lts.md) [oldnews.html](oldnews.md) [onefile.html](onefile.md) [qmplan.html](qmplan.md) [rowidtable.html](rowidtable.md) [schematab.html](schematab.md) [sqlar.html#dbasobj](sqlar.md#dbasobj) [stricttables.html](stricttables.md) [version3.html](version3.md) [walformat.html](walformat.md) [whentouse.html#container](whentouse.md#container) [whentouse.html#wireproto](whentouse.md#wireproto)
- file format version numbers → [c3ref/deserialize.html](c3ref/deserialize.md) [capi3ref.html#sqlite3_deserialize](capi3ref.md#sqlite3_deserialize) [walformat.html](walformat.md)
- file I/O functions → [changes.html#version_3_28_0](changes.md#version_3_28_0) [changes.html#version_3_8_6](changes.md#version_3_8_6) [cli.html#zipdb](cli.md#zipdb) [json1.html#jblobbug](json1.md#jblobbug) [releaselog/3_28_0.html](releaselog/3_28_0.md) [releaselog/3_8_6.html](releaselog/3_8_6.md) [zipfile.html](zipfile.md)
- file-format benefits → [whentouse.html#appfileformat](whentouse.md#appfileformat)
- FILTER clause on aggregate functions → [changes.html#version_3_30_0](changes.md#version_3_30_0) [changes.html#version_3_30_1](changes.md#version_3_30_1) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md)
- filter-clause → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- flattened → [changes.html#version_3_35_0](changes.md#version_3_35_0) [changes.html#version_3_50_1](changes.md#version_3_50_1) [lang_with.html#mathint](lang_with.md#mathint) [optoverview.html#coroutines](optoverview.md#coroutines) [optoverview.html#pushdown](optoverview.md#pushdown) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- flattening optimization → [changes.html#version_3_19_0](changes.md#version_3_19_0) [changes.html#version_3_19_1](changes.md#version_3_19_1) [changes.html#version_3_19_2](changes.md#version_3_19_2) [changes.html#version_3_20_0](changes.md#version_3_20_0) [eqp.html#or-opt](eqp.md#or-opt) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- Flexible typing is a feature → [datatype3.html](datatype3.md) [quirks.html](quirks.md)
- floating point values are approximations → [staleexpridx.html](staleexpridx.md)
- floating-point values → [datatype3.html#affinity](datatype3.md#affinity)
- floor → [lang_mathfunc.html](lang_mathfunc.md) [lang_mathfunc.html#trunc](lang_mathfunc.md#trunc)
- footprint → [different.html#small](different.md#small) [features.html](features.md) [index.html](index.md)
- foreign key actions → [c3ref/changes.html](c3ref/changes.md) [c3ref/total_changes.html](c3ref/total_changes.md) [capi3ref.html#sqlite3_changes](capi3ref.md#sqlite3_changes) [capi3ref.html#sqlite3_total_changes](capi3ref.md#sqlite3_total_changes) [changes.html#version_3_12_0](changes.md#version_3_12_0) [compile.html#omit_trigger](compile.md#omit_trigger) [foreignkeys.html#fk_actions](foreignkeys.md#fk_actions) [lang_droptable.html](lang_droptable.md) [pragma.html#pragma_count_changes](pragma.md#pragma_count_changes) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md)
- foreign key constraint → [compile.html#omit_foreign_key](compile.md#omit_foreign_key) [lang_altertable.html#altertabdropcol](lang_altertable.md#altertabdropcol) [lang_conflict.html](lang_conflict.md) [lang_createtable.html#rowid](lang_createtable.md#rowid) [pragma.html#pragma_foreign_key_list](pragma.md#pragma_foreign_key_list) [pragma.html#pragma_integrity_check](pragma.md#pragma_integrity_check) [rescode.html#constraint_foreignkey](rescode.md#constraint_foreignkey)
- foreign key constraints → [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigenablefkey](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenablefkey) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlitedbconfigenablefkey](capi3ref.md#sqlitedbconfigenablefkey) [changes.html#version_3_6_19](changes.md#version_3_6_19) [compile.html#default_foreign_keys](compile.md#default_foreign_keys) [compile.html#omit_trigger](compile.md#omit_trigger) [faq.html#q22](faq.md#q22) [lang_altertable.html#altertabaddcol](lang_altertable.md#altertabaddcol) [lang_altertable.html#altertabrename](lang_altertable.md#altertabrename) [lang_droptable.html](lang_droptable.md) [lang_returning.html](lang_returning.md) [oldnews.html](oldnews.md) [pragma.html#pragma_defer_foreign_keys](pragma.md#pragma_defer_foreign_keys) [pragma.html#pragma_foreign_key_check](pragma.md#pragma_foreign_key_check) [pragma.html#pragma_foreign_keys](pragma.md#pragma_foreign_keys) [releaselog/3_6_19.html](releaselog/3_6_19.md)
- FOREIGN KEY constraints → [fullsql.html](fullsql.md) [lang_conflict.html](lang_conflict.md) [stricttables.html](stricttables.md)
- foreign key constraints are enabled → [foreignkeys.html#fk_actions](foreignkeys.md#fk_actions)
- foreign-key-clause → [lang_altertable.html](lang_altertable.md) [lang_altertable.html#altertabaddcol](lang_altertable.md#altertabaddcol) [lang_createtable.html](lang_createtable.md)
- foreign_key_list pragma → [pragma.html#pragma_foreign_key_check](pragma.md#pragma_foreign_key_check)
- foreign_keys pragma → [changes.html#version_3_6_19](changes.md#version_3_6_19) [compile.html#default_foreign_keys](compile.md#default_foreign_keys) [lang_altertable.html#altertabaddcol](lang_altertable.md#altertabaddcol) [oldnews.html](oldnews.md) [releaselog/3_6_19.html](releaselog/3_6_19.md)
- format → [changes.html#version_3_38_0](changes.md#version_3_38_0) [lang_corefunc.html](lang_corefunc.md) [printf.html](printf.md) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md)
- format method → [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- format SQL function → [changes.html#version_3_50_0](changes.md#version_3_50_0) [changes.html#version_3_51_0](changes.md#version_3_51_0) [lang_corefunc.html#printf](lang_corefunc.md#printf) [printf.html](printf.md) [printf.html#percentw](printf.md#percentw) [printf.html#percentz](printf.md#percentz) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- forum → [fasterthanfs.html](fasterthanfs.md)
- fp-digits → [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- frame-spec → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- frames → [changes.html#version_3_28_0](changes.md#version_3_28_0) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- free-page list → [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_7_2](changes.md#version_3_7_2) [oldnews.html](oldnews.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_7_2.html](releaselog/3_7_2.md)
- freelist → [atomiccommit.html#freelistjrnl](atomiccommit.md#freelistjrnl) [pragma.html#pragma_auto_vacuum](pragma.md#pragma_auto_vacuum) [pragma.html#pragma_incremental_vacuum](pragma.md#pragma_incremental_vacuum) [pragma.html#pragma_secure_delete](pragma.md#pragma_secure_delete)
- FROM clause → [lang_select.html#simpleselect](lang_select.md#simpleselect)
- FTS auxiliary functions → [fts3.html#hiddencol](fts3.md#hiddencol) [fts3.html#simple_fts_queries](fts3.md#simple_fts_queries) [fts5.html#appendix_a](fts5.md#appendix_a) [vtab.html#hiddencol](vtab.md#hiddencol)
- FTS hidden column → [fts3.html#matchinfo](fts3.md#matchinfo) [fts3.html#snippet](fts3.md#snippet) [vtab.html#hiddencol](vtab.md#hiddencol)
- FTS MATCH → [bindptr.html](bindptr.md) [fts3.html#fts4](fts3.md#fts4) [fts3.html#hiddencol](fts3.md#hiddencol) [fts3.html#simple_fts_queries](fts3.md#simple_fts_queries) [vtab.html#hiddencol](vtab.md#hiddencol)
- FTS shadow tables → [fts3.html#\*fts4ickcmd](fts3.md#*fts4ickcmd) [fts3.html#fts4](fts3.md#fts4) [rbu.html#sqldiff](rbu.md#sqldiff) [vtab.html#xshadowname](vtab.md#xshadowname)
- FTS3 → [amalgamation.html](amalgamation.md) [bindptr.html](bindptr.md) [bindptr.html#ptrtyp](bindptr.md#ptrtyp) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigenablefts3tokenizer](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenablefts3tokenizer) [capi3ref.html#sqlitedbconfigenablefts3tokenizer](capi3ref.md#sqlitedbconfigenablefts3tokenizer) [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_39_1](changes.md#version_3_39_1) [changes.html#version_3_41_2](changes.md#version_3_41_2) [changes.html#version_3_44_0](changes.md#version_3_44_0) [changes.html#version_3_6_22](changes.md#version_3_6_22) [changes.html#version_3_6_23](changes.md#version_3_6_23) [changes.html#version_3_6_23_1](changes.md#version_3_6_23_1) [changes.html#version_3_7_16_1](changes.md#version_3_7_16_1) [changes.html#version_3_7_17](changes.md#version_3_7_17) [changes.html#version_3_7_7](changes.md#version_3_7_7) [changes.html#version_3_8_10](changes.md#version_3_8_10) [changes.html#version_3_8_11](changes.md#version_3_8_11) [compile.html#disable_fts3_unicode](compile.md#disable_fts3_unicode) [compile.html#fts3_max_expr_depth](compile.md#fts3_max_expr_depth) [cves.html#cvetab](cves.md#cvetab) [fts5.html#fts5shadowtables](fts5.md#fts5shadowtables) [news.html](news.md) [oldnews.html](oldnews.md) [pragma.html#pragma_secure_delete](pragma.md#pragma_secure_delete) [rbu.html#fts4_tables](rbu.md#fts4_tables) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md) [releaselog/3_41_2.html](releaselog/3_41_2.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md) [releaselog/3_6_22.html](releaselog/3_6_22.md) [releaselog/3_6_23.html](releaselog/3_6_23.md) [releaselog/3_6_23_1.html](releaselog/3_6_23_1.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md) [releaselog/3_7_17.html](releaselog/3_7_17.md) [releaselog/3_7_7.html](releaselog/3_7_7.md) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [sqldiff.html](sqldiff.md) [vtab.html#hiddencol](vtab.md#hiddencol) [vtab.html#xintegrity](vtab.md#xintegrity) [vtab.html#xshadowname](vtab.md#xshadowname)
- fts3 → [changes.html#version_3_6_21](changes.md#version_3_6_21) [fts5.html#appendix_a](fts5.md#appendix_a) [releaselog/3_6_21.html](releaselog/3_6_21.md)
- fts3_tokenizer → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigenablefts3tokenizer](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenablefts3tokenizer) [capi3ref.html#sqlitedbconfigenablefts3tokenizer](capi3ref.md#sqlitedbconfigenablefts3tokenizer) [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_12_0](changes.md#version_3_12_0) [changes.html#version_3_28_0](changes.md#version_3_28_0) [compile.html#enable_fts3_tokenizer](compile.md#enable_fts3_tokenizer) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- fts3tokenize virtual table → [changes.html#version_3_7_17](changes.md#version_3_7_17) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- FTS4 → [affcase1.html#smaller](affcase1.md#smaller) [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_44_0](changes.md#version_3_44_0) [changes.html#version_3_7_4](changes.md#version_3_7_4) [changes.html#version_3_7_9](changes.md#version_3_7_9) [changes.html#version_3_8_0](changes.md#version_3_8_0) [changes.html#version_3_8_1](changes.md#version_3_8_1) [changes.html#version_3_8_5](changes.md#version_3_8_5) [changes.html#version_3_8_6](changes.md#version_3_8_6) [compile.html#disable_fts4_deferred](compile.md#disable_fts4_deferred) [compile.html#fts3_max_expr_depth](compile.md#fts3_max_expr_depth) [oldnews.html](oldnews.md) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md) [releaselog/3_7_4.html](releaselog/3_7_4.md) [releaselog/3_7_9.html](releaselog/3_7_9.md) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md) [releaselog/3_8_1.html](releaselog/3_8_1.md) [releaselog/3_8_5.html](releaselog/3_8_5.md) [releaselog/3_8_6.html](releaselog/3_8_6.md) [spellfix1.html](spellfix1.md) [th3.html](th3.md)
- FTS4 automerge command → [changes.html#version_3_7_12](changes.md#version_3_7_12) [releaselog/3_7_12.html](releaselog/3_7_12.md)
- fts4 compress option → [fts3.html#fts4_options](fts3.md#fts4_options) [fts3.html#fts4order](fts3.md#fts4order)
- FTS4 content option → [changes.html#version_3_7_11](changes.md#version_3_7_11) [fts3.html#\*fts4ickcmd](fts3.md#*fts4ickcmd) [fts3.html#\*fts4rebuidcmd](fts3.md#*fts4rebuidcmd) [releaselog/3_7_11.html](releaselog/3_7_11.md)
- FTS4 integrity-check command → [changes.html#version_3_7_12](changes.md#version_3_7_12) [releaselog/3_7_12.html](releaselog/3_7_12.md)
- FTS4 languageid option → [changes.html#version_3_7_11](changes.md#version_3_7_11) [releaselog/3_7_11.html](releaselog/3_7_11.md)
- FTS4 matchinfo option → [fts3.html#fts4](fts3.md#fts4) [fts3.html#shadow_tables](fts3.md#shadow_tables)
- FTS4 merge command → [changes.html#version_3_7_12](changes.md#version_3_7_12) [releaselog/3_7_12.html](releaselog/3_7_12.md)
- FTS4 notindexed option → [changes.html#version_3_8_0](changes.md#version_3_8_0) [changes.html#version_3_8_5](changes.md#version_3_8_5) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- FTS4 options → [fts3.html#fts4](fts3.md#fts4)
- FTS4 order option → [changes.html#version_3_7_7](changes.md#version_3_7_7) [oldnews.html](oldnews.md) [releaselog/3_7_7.html](releaselog/3_7_7.md)
- fts4 prefix option → [fts3.html#fts4order](fts3.md#fts4order)
- FTS4 prefix option → [changes.html#version_3_7_7](changes.md#version_3_7_7) [oldnews.html](oldnews.md) [releaselog/3_7_7.html](releaselog/3_7_7.md)
- FTS4 rebuild command → [fts3.html#\_external_content_fts4_tables\_](fts3.md#_external_content_fts4_tables_)
- fts4aux → [changes.html#version_3_7_17](changes.md#version_3_7_17) [changes.html#version_3_7_6](changes.md#version_3_7_6) [changes.html#version_3_8_1](changes.md#version_3_8_1) [releaselog/3_7_17.html](releaselog/3_7_17.md) [releaselog/3_7_6.html](releaselog/3_7_6.md) [releaselog/3_8_1.html](releaselog/3_8_1.md) [spellfix1.html](spellfix1.md)
- fts4aux languageid column → [changes.html#version_3_8_1](changes.md#version_3_8_1) [releaselog/3_8_1.html](releaselog/3_8_1.md)
- FTS5 → [amalgamation.html](amalgamation.md) [bindptr.html#ptrtyp](bindptr.md#ptrtyp) [changes.html#version_3_11_1](changes.md#version_3_11_1) [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_19_0](changes.md#version_3_19_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_34_0](changes.md#version_3_34_0) [changes.html#version_3_37_1](changes.md#version_3_37_1) [changes.html#version_3_43_0](changes.md#version_3_43_0) [changes.html#version_3_44_0](changes.md#version_3_44_0) [changes.html#version_3_45_0](changes.md#version_3_45_0) [changes.html#version_3_46_1](changes.md#version_3_46_1) [changes.html#version_3_51_0](changes.md#version_3_51_0) [changes.html#version_3_8_11](changes.md#version_3_8_11) [changes.html#version_3_9_0](changes.md#version_3_9_0) [cves.html#cvetab](cves.md#cvetab) [fullsql.html](fullsql.md) [lemon.html](lemon.md) [news.html](news.md) [oldnews.html](oldnews.md) [pragma.html#pragma_secure_delete](pragma.md#pragma_secure_delete) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md) [releaselog/3_46_1.html](releaselog/3_46_1.md) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md) [sqldiff.html](sqldiff.md) [vtab.html#xintegrity](vtab.md#xintegrity) [vtab.html#xshadowname](vtab.md#xshadowname) [vtablist.html](vtablist.md)
- fts5 → [compile.html#enable_fts5](compile.md#enable_fts5)
- FTS5 automerge option → [fts5.html#appendix_a](fts5.md#appendix_a) [fts5.html#the_merge_command](fts5.md#the_merge_command) [fts5.html#the_optimize_command](fts5.md#the_optimize_command)
- FTS5 auxiliary functions → [fts5.html](fts5.md) [fts5.html#the_unindexed_column_option](fts5.md#the_unindexed_column_option)
- FTS5 bm25 → [fts5.html#\_auxiliary_functions\_](fts5.md#_auxiliary_functions_) [fts5.html#the_columnsize_option](fts5.md#the_columnsize_option)
- FTS5 column filters → [changes.html#version_3_19_0](changes.md#version_3_19_0) [fts5.html](fts5.md) [fts5.html#fts5_initial_token_queries](fts5.md#fts5_initial_token_queries) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md)
- FTS5 columnsize option → [fts5.html#appendix_a](fts5.md#appendix_a) [fts5.html#fts5_table_creation_and_initialization](fts5.md#fts5_table_creation_and_initialization)
- FTS5 content option → [fts5.html#fts5_table_creation_and_initialization](fts5.md#fts5_table_creation_and_initialization)
- FTS5 contentless tables → [fts5.html#the_columnsize_option](fts5.md#the_columnsize_option) [fts5.html#the_delete_all_command](fts5.md#the_delete_all_command) [fts5.html#the_delete_command](fts5.md#the_delete_command) [fts5.html#the_detail_option](fts5.md#the_detail_option) [fts5.html#the_rebuild_command](fts5.md#the_rebuild_command)
- FTS5 contentless-delete tables → [fts5.html#the_delete_all_command](fts5.md#the_delete_all_command) [fts5.html#the_deletemerge_configuration_option](fts5.md#the_deletemerge_configuration_option)
- FTS5 CREATE TABLE Options → [fts5.html](fts5.md)
- FTS5 custom auxiliary functions → [fts5.html](fts5.md) [fts5.html#\_auxiliary_functions\_](fts5.md#_auxiliary_functions_)
- FTS5 delete command → [fts5.html#contentless_delete_tables](fts5.md#contentless_delete_tables) [fts5.html#contentless_tables](fts5.md#contentless_tables)
- FTS5 delete-all command → [fts5.html#the_delete_command](fts5.md#the_delete_command)
- FTS5 detail option → [changes.html#version_3_11_0](changes.md#version_3_11_0) [fts5.html#fts5_table_creation_and_initialization](fts5.md#fts5_table_creation_and_initialization) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md)
- FTS5 external content tables → [fts5.html#fts5_table_creation_and_initialization](fts5.md#fts5_table_creation_and_initialization) [fts5.html#the_delete_all_command](fts5.md#the_delete_all_command) [fts5.html#the_delete_command](fts5.md#the_delete_command) [fts5.html#the_insttoken_configuration_option](fts5.md#the_insttoken_configuration_option) [fts5.html#the_rebuild_command](fts5.md#the_rebuild_command)
- FTS5 get_locale → [fts5.html#\_auxiliary_functions\_](fts5.md#_auxiliary_functions_) [fts5.html#the_locale_option](fts5.md#the_locale_option)
- FTS5 highlight → [fts5.html#\_auxiliary_functions\_](fts5.md#_auxiliary_functions_)
- FTS5 initial token → [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_22_0.html](releaselog/3_22_0.md)
- FTS5 insttoken → [changes.html#version_3_48_0](changes.md#version_3_48_0) [fts5.html#custom_auxiliary_functions_api_reference](fts5.md#custom_auxiliary_functions_api_reference) [releaselog/3_48_0.html](releaselog/3_48_0.md)
- FTS5 merge command → [fts5.html#appendix_a](fts5.md#appendix_a) [fts5.html#the_optimize_command](fts5.md#the_optimize_command)
- FTS5 optimize command → [fts5.html#the_merge_command](fts5.md#the_merge_command)
- FTS5 pgsz option → [fts5.html#the_merge_command](fts5.md#the_merge_command)
- FTS5 prefix indexes → [fts5.html#fts5_table_creation_and_initialization](fts5.md#fts5_table_creation_and_initialization)
- FTS5 query syntax → [fts5.html](fts5.md)
- FTS5 rank configuration option → [fts5.html#sorting_by_auxiliary_function_results](fts5.md#sorting_by_auxiliary_function_results)
- FTS5 secure-delete command → [changes.html#version_3_42_0](changes.md#version_3_42_0) [changes.html#version_3_46_1](changes.md#version_3_46_1) [news.html](news.md) [releaselog/3_42_0.html](releaselog/3_42_0.md) [releaselog/3_46_1.html](releaselog/3_46_1.md)
- fts5 shadow tables → [vtab.html#xshadowname](vtab.md#xshadowname)
- FTS5 snippet → [fts5.html#\_auxiliary_functions\_](fts5.md#_auxiliary_functions_)
- fts5 technical differences → [fts5.html#appendix_a](fts5.md#appendix_a)
- FTS5 tokendata option → [changes.html#version_3_45_0](changes.md#version_3_45_0) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- FTS5 tokenizers → [changes.html#version_3_46_1](changes.md#version_3_46_1) [fts5.html#fts5_phrases](fts5.md#fts5_phrases) [fts5.html#fts5_table_creation_and_initialization](fts5.md#fts5_table_creation_and_initialization) [releaselog/3_46_1.html](releaselog/3_46_1.md)
- FTS5 usermerge option → [fts5.html#the_merge_command](fts5.md#the_merge_command)
- fts5_insttoken → [changes.html#version_3_48_0](changes.md#version_3_48_0) [fts5.html#custom_auxiliary_functions_api_reference](fts5.md#custom_auxiliary_functions_api_reference) [releaselog/3_48_0.html](releaselog/3_48_0.md)
- fts5vocab → [changes.html#version_3_15_0](changes.md#version_3_15_0) [changes.html#version_3_51_1](changes.md#version_3_51_1) [fts5.html#appendix_a](fts5.md#appendix_a) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- Full-featured SQL → [about.html](about.md) [features.html](features.md)
- full-featured SQL → [index.html](index.md)
- full-text search → [aff_short.html](aff_short.md) [changes.html#version_3_7_17](changes.md#version_3_7_17) [howtocompile.html#dll](howtocompile.md#dll) [oldnews.html](oldnews.md) [releaselog/3_7_17.html](releaselog/3_7_17.md) [vtab.html](vtab.md) [vtablist.html](vtablist.md)
- full_column_names → [pragma.html#pragma_full_column_names](pragma.md#pragma_full_column_names) [pragma.html#pragma_short_column_names](pragma.md#pragma_short_column_names)
- fullfsync → [pragma.html#pragma_checkpoint_fullfsync](pragma.md#pragma_checkpoint_fullfsync) [pragma.html#pragma_synchronous](pragma.md#pragma_synchronous)
- function method → [changes.html#version_3_28_0](changes.md#version_3_28_0) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- function-arguments → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- function_list pragma → [changes.html#version_3_31_0](changes.md#version_3_31_0) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- functions within expressions → [lang_corefunc.html](lang_corefunc.md)
- fuzz testing → [testing.html#slt](testing.md#slt)
- generalized ALTER TABLE procedure → [lang_altertable.html#caution](lang_altertable.md#caution)
- generate_series → [changes.html#version_3_23_1](changes.md#version_3_23_1) [changes.html#version_3_34_0](changes.md#version_3_34_0) [changes.html#version_3_37_0](changes.md#version_3_37_0) [changes.html#version_3_47_0](changes.md#version_3_47_0) [cli.html#miscfeatures](cli.md#miscfeatures) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md)
- generated column → [changes.html#version_3_37_0](changes.md#version_3_37_0) [compile.html#omit_generated_columns](compile.md#omit_generated_columns) [deterministic.html](deterministic.md) [lang_altertable.html#altertabaddcol](lang_altertable.md#altertabaddcol) [lang_altertable.html#altertabdropcol](lang_altertable.md#altertabdropcol) [lang_createtable.html](lang_createtable.md) [lang_createtable.html#collateclause](lang_createtable.md#collateclause) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md)
- Generated columns → [stricttables.html](stricttables.md)
- generated columns → [c3ref/c_deterministic.html#sqlitedeterministic](c3ref/c_deterministic.md#sqlitedeterministic) [c3ref/c_deterministic.html#sqlitedirectonly](c3ref/c_deterministic.md#sqlitedirectonly) [c3ref/c_deterministic.html#sqliteinnocuous](c3ref/c_deterministic.md#sqliteinnocuous) [capi3ref.html#sqlitedeterministic](capi3ref.md#sqlitedeterministic) [capi3ref.html#sqlitedirectonly](capi3ref.md#sqlitedirectonly) [capi3ref.html#sqliteinnocuous](capi3ref.md#sqliteinnocuous) [changes.html#version_3_31_0](changes.md#version_3_31_0) [changes.html#version_3_41_2](changes.md#version_3_41_2) [changes.html#version_3_49_0](changes.md#version_3_49_0) [lang_altertable.html#altertabaddcol](lang_altertable.md#altertabaddcol) [news.html](news.md) [pragma.html#pragma_table_info](pragma.md#pragma_table_info) [pragma.html#pragma_table_list](pragma.md#pragma_table_list) [pragma.html#pragma_table_xinfo](pragma.md#pragma_table_xinfo) [pragma.html#pragma_trusted_schema](pragma.md#pragma_trusted_schema) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md)
- geopoly → [changes.html#version_3_26_0](changes.md#version_3_26_0) [releaselog/3_26_0.html](releaselog/3_26_0.md)
- GEOPOLY → [changes.html#version_3_44_0](changes.md#version_3_44_0) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md)
- Geopoly extension → [compile.html#enable_geopoly](compile.md#enable_geopoly)
- Geopoly module → [changes.html#version_3_25_0](changes.md#version_3_25_0) [releaselog/3_25_0.html](releaselog/3_25_0.md) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md) [vtab.html#xfindfunction](vtab.md#xfindfunction)
- geopoly_ccw → [changes.html#version_3_26_0](changes.md#version_3_26_0) [geopoly.html#xform](geopoly.md#xform) [releaselog/3_26_0.html](releaselog/3_26_0.md)
- geopoly_overlap → [vtab.html#xfindfunction](vtab.md#xfindfunction)
- geopoly_regular → [changes.html#version_3_26_0](changes.md#version_3_26_0) [releaselog/3_26_0.html](releaselog/3_26_0.md)
- geopoly_within → [vtab.html#xfindfunction](vtab.md#xfindfunction)
- get the canonical source code → [amalgamation.html#amalgbuild](amalgamation.md#amalgbuild)
- GLOB → [c3ref/c_limit_attached.html#sqlitelimitlikepatternlength](c3ref/c_limit_attached.md#sqlitelimitlikepatternlength) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/strglob.html](c3ref/strglob.md) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_strglob](capi3ref.md#sqlite3_strglob) [capi3ref.html#sqlitelimitlikepatternlength](capi3ref.md#sqlitelimitlikepatternlength) [changes.html#version_3_10_0](changes.md#version_3_10_0) [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_16_0](changes.md#version_3_16_0) [compile.html#omit_like_optimization](compile.md#omit_like_optimization) [compile.html#rcmd](compile.md#rcmd) [fullsql.html](fullsql.md) [lang_corefunc.html#glob](lang_corefunc.md#glob) [limits.html#max_like_pattern_length](limits.md#max_like_pattern_length) [oldnews.html](oldnews.md) [optoverview.html#like_opt](optoverview.md#like_opt) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [vfs.html#shim](vfs.md#shim) [vtab.html#xfindfunction](vtab.md#xfindfunction)
- glob → [cli.html#sqlar](cli.md#sqlar) [lang_corefunc.html](lang_corefunc.md) [lang_expr.html#glob](lang_expr.md#glob)
- GROUP BY → [lang_select.html#simpleselect](lang_select.md#simpleselect)
- GROUP BY clause → [changes.html#version_3_39_0](changes.md#version_3_39_0) [releaselog/3_39_0.html](releaselog/3_39_0.md) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- group_concat → [changes.html#version_3_46_1](changes.md#version_3_46_1) [changes.html#version_3_6_14_1](changes.md#version_3_6_14_1) [lang_aggfunc.html#aggfunclist](lang_aggfunc.md#aggfunclist) [releaselog/3_46_1.html](releaselog/3_46_1.md) [releaselog/3_6_14_1.html](releaselog/3_6_14_1.md)
- group_concat aggregate function → [changes.html#version_3_47_0](changes.md#version_3_47_0) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md)
- GROUPS frames → [changes.html#version_3_28_0](changes.md#version_3_28_0) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- hard_heap_limit pragma → [pragma.html#pragma_soft_heap_limit](pragma.md#pragma_soft_heap_limit)
- HAVE_ISNAN → [compile.html#have_isnan](compile.md#have_isnan)
- HAVING clause → [changes.html#version_3_39_0](changes.md#version_3_39_0) [releaselog/3_39_0.html](releaselog/3_39_0.md) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- hazards of upgrading to the NGQP → [oldnews.html](oldnews.md)
- hex → [base64.html](base64.md) [base85.html](base85.md) [bindptr.html#ptrleak](bindptr.md#ptrleak) [lang_corefunc.html](lang_corefunc.md) [lang_corefunc.html#randomblob](lang_corefunc.md#randomblob) [lang_corefunc.html#unhex](lang_corefunc.md#unhex)
- hexadecimal integer literals → [changes.html#version_3_8_6](changes.md#version_3_8_6) [compile.html#omit_hex_integer](compile.md#omit_hex_integer) [releaselog/3_8_6.html](releaselog/3_8_6.md)
- hexadecimal integers → [fullsql.html](fullsql.md) [lang_expr.html#castexpr](lang_expr.md#castexpr) [oldnews.html](oldnews.md)
- hidden column → [dbpage.html](dbpage.md) [dbstat.html#dbstatagg](dbstat.md#dbstatagg) [fts3.html#hiddencol](fts3.md#hiddencol) [fts3.html#the_languageid_option](fts3.md#the_languageid_option)
- hidden columns → [changes.html#version_3_26_0](changes.md#version_3_26_0) [compile.html#enable_hidden_columns](compile.md#enable_hidden_columns) [lang_returning.html](lang_returning.md) [lang_select.html#tabfunc1](lang_select.md#tabfunc1) [pragma.html#pragma_table_info](pragma.md#pragma_table_info) [pragma.html#pragma_table_list](pragma.md#pragma_table_list) [pragma.html#pragma_table_xinfo](pragma.md#pragma_table_xinfo) [releaselog/3_26_0.html](releaselog/3_26_0.md) [vtab.html#tabfunc2](vtab.md#tabfunc2)
- high-reliability → [index.html](index.md)
- Hipp → [printf.html#comma](printf.md#comma)
- host parameter → [c3ref/vtab_rhs_value.html](c3ref/vtab_rhs_value.md) [capi3ref.html#sqlite3_vtab_rhs_value](capi3ref.md#sqlite3_vtab_rhs_value) [vtab.html#colUsed](vtab.md#colUsed)
- hot journal → [changes.html#version_3_13_0](changes.md#version_3_13_0) [howtocorrupt.html#delhotjrnl](howtocorrupt.md#delhotjrnl) [lockingv3.html#rollback](lockingv3.md#rollback) [releaselog/3_13_0.html](releaselog/3_13_0.md) [rescode.html#notice_recover_rollback](rescode.md#notice_recover_rollback) [rescode.html#readonly_rollback](rescode.md#readonly_rollback) [rsync.html#intro](rsync.md#intro) [tclsqlite.html](tclsqlite.md)
- hot journal files → [howtocorrupt.html#delhotjrnl](howtocorrupt.md#delhotjrnl)
- how collation is determined → [lang_select.html#distinct](lang_select.md#distinct)
- How SQLite Works → [eqp.html](eqp.md)
- how to compile → [amalgamation.html](amalgamation.md) [cli.html#compiling](cli.md#compiling) [features.html](features.md)
- How To Compile SQLite → [amalgamation.html#amalgbuild](amalgamation.md#amalgbuild) [download.html#srctree](download.md#srctree) [fts5.html#compiling_and_using_fts5](fts5.md#compiling_and_using_fts5) [getthecode.html](getthecode.md) [quickstart.html](quickstart.md)
- how to corrupt → [atomiccommit.html#sect_9_0](atomiccommit.md#sect_9_0) [fts3.html#\*fts4ickcmd](fts3.md#*fts4ickcmd) [recovery.html](recovery.md)
- How To Corrupt Your Database Files → [rescode.html#corrupt](rescode.md#corrupt) [useovernet.html](useovernet.md)
- http://atulgawande.com/book/the-checklist-manifesto/ → [testing.html#cklist](testing.md#cklist)
- http://clang-analyzer.llvm.org/ → [testing.html#staticanalysis](testing.md#staticanalysis)
- http://code.google.com/android/ → [famous.html](famous.md)
- http://community.intuit.com/posts/database-error-sqlite-error-code1 → [famous.html](famous.md)
- http://dmalloc.com → [malloc.html](malloc.md)
- http://docs.python.org/lib/module-sqlite3.html → [famous.html](famous.md)
- http://en.wikipedia.org/wiki/ACID → [about.html](about.md) [transactional.html](transactional.md)
- http://en.wikipedia.org/wiki/Coordinated_Universal_Time → [lang_datefunc.html#tmval](lang_datefunc.md#tmval)
- http://en.wikipedia.org/wiki/Endianness → [about.html](about.md) [onefile.html](onefile.md)
- http://en.wikipedia.org/wiki/Fuzz_testing → [testing.html#fuzztesting](testing.md#fuzztesting)
- http://en.wikipedia.org/wiki/Gregorian_calendar → [lang_datefunc.html#subsec](lang_datefunc.md#subsec)
- http://en.wikipedia.org/wiki/ISO_8601 → [lang_datefunc.html](lang_datefunc.md)
- http://en.wikipedia.org/wiki/Julian_day → [lang_datefunc.html](lang_datefunc.md) [lang_datefunc.html#jlndy](lang_datefunc.md#jlndy) [lang_datefunc.html#tmval](lang_datefunc.md#tmval)
- http://en.wikipedia.org/wiki/Kibibyte → [oldnews.html](oldnews.md)
- http://en.wikipedia.org/wiki/Modified_Condition/Decision_Coverage → [testing.html#mcdc](testing.md#mcdc)
- http://en.wikipedia.org/wiki/OpenDocument → [affcase1.html](affcase1.md)
- http://en.wikipedia.org/wiki/Proleptic_Gregorian_calendar → [lang_datefunc.html#jlndy](lang_datefunc.md#jlndy)
- http://en.wikipedia.org/wiki/Public_Domain → [copyright.html](copyright.md)
- http://en.wikipedia.org/wiki/R-tree → [rtree.html](rtree.md)
- http://en.wikipedia.org/wiki/Serializability → [transactional.html](transactional.md)
- http://en.wikipedia.org/wiki/Syslog → [errlog.html](errlog.md)
- http://en.wikipedia.org/wiki/Unix_time → [lang_datefunc.html#jdmod](lang_datefunc.md#jdmod)
- http://en.wikipedia.org/wiki/UUID → [changes.html#version_3_3_13](changes.md#version_3_3_13) [releaselog/3_3_13.html](releaselog/3_3_13.md)
- http://en.wikipedia.org/wiki/Zip\_%28file_format%29 → [affcase1.html](affcase1.md)
- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32575 → [changes.html#version_3_4_2](changes.md#version_3_4_2) [releaselog/3_4_2.html](releaselog/3_4_2.md)
- http://gcc.gnu.org/onlinedocs/gcc/Gcov.html → [testing.html#coverage](testing.md#coverage) [th3.html](th3.md)
- http://geojson.org → [geopoly.html](geopoly.md)
- http://geonames.usgs.gov/domestic/download_data.htm → [spellfix1.html](spellfix1.md)
- http://git.savannah.gnu.org/cgit/readline.git?h=devel → [qmplan.html](qmplan.md)
- http://heartbleed.com → [malloc.html](malloc.md)
- http://lcamtuf.coredump.cx/afl/ → [changes.html#version_3_8_8](changes.md#version_3_8_8) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- http://linux.die.net/man/1/file → [appfileformat.html](appfileformat.md)
- http://llvm.org/docs/LibFuzzer.html → [testing.html#dbsqlfuzz](testing.md#dbsqlfuzz) [testing.html#slt](testing.md#slt)
- http://man.he.net/man3/fopen → [about.html](about.md) [whentouse.html](whentouse.md) [whentouse.html#container](whentouse.md#container)
- http://man.he.net/man3/fread → [whentouse.html#container](whentouse.md#container)
- http://man.he.net/man3/fwrite → [whentouse.html#container](whentouse.md#container)
- http://semver.org → [versionnumbers.html](versionnumbers.md)
- http://semver.org/ → [changes.html#version_3_9_0](changes.md#version_3_9_0) [oldnews.html](oldnews.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- http://System.Data.SQLite.org/ → [oldnews.html](oldnews.md)
- http://thrysoee.dk/editline/ → [qmplan.html](qmplan.md)
- http://tools.ietf.org/html/rfc3986 → [uri.html](uri.md)
- http://turbotax.intuit.com/ → [famous.html](famous.md)
- http://valgrind.org → [faq.html#q17](faq.md#q17) [malloc.html](malloc.md)
- http://valgrind.org/ → [oldnews.html](oldnews.md) [testing.html#valgrind](testing.md#valgrind)
- http://valgrind.org/docs/manual/cg-manual.html → [changes.html#version_3_8_11](changes.md#version_3_8_11) [changes.html#version_3_8_7](changes.md#version_3_8_7) [cpu.html](cpu.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- http://wiki.tcl-lang.org/21708 → [faq.html#q25](faq.md#q25)
- http://wiki.tcl-lang.org/2364 → [howtocompile.html#tcl](howtocompile.md#tcl)
- http://wiki.tcl-lang.org/2541 → [howtocompile.html#tcl](howtocompile.md#tcl)
- http://wiki.tcl-lang.org/9830 → [howtocompile.html#tcl](howtocompile.md#tcl)
- http://windows.microsoft.com/en-US/internet-explorer/products/ie/home → [uri.html](uri.md)
- http://www.adobe.com/ → [famous.html](famous.md)
- http://www.adobe.com/products/acrobat/readstep2.html → [famous.html](famous.md)
- http://www.adobe.com/products/photoshoplightroom/ → [famous.html](famous.md)
- http://www.airbus.com/ → [famous.html](famous.md)
- http://www.apple.com/ → [famous.html](famous.md)
- http://www.apple.com/itunes/ → [famous.html](famous.md)
- http://www.apple.com/safari/ → [uri.html](uri.md)
- http://www.apress.com → [oldnews.html](oldnews.md)
- http://www.bentley.com/ → [famous.html](famous.md)
- http://www.bloomberg.com/ → [oldnews.html](oldnews.md)
- http://www.bosch.com/ → [famous.html](famous.md)
- http://www.darwinsys.com/file/ → [aff_short.html](aff_short.md) [fileformat2.html#appid](fileformat2.md#appid) [pragma.html#pragma_application_id](pragma.md#pragma_application_id)
- http://www.devio.us/ → [oldnews.html](oldnews.md)
- http://www.dropbox.com/ → [famous.html](famous.md)
- http://www.fossil-scm.org → [privatebranch.html](privatebranch.md)
- http://www.fossil-scm.org/ → [appfileformat.html](appfileformat.md) [changes.html#version_3_6_18](changes.md#version_3_6_18) [oldnews.html](oldnews.md) [privatebranch.html](privatebranch.md) [releaselog/3_6_18.html](releaselog/3_6_18.md) [th3.html](th3.md)
- http://www.fossil-scm.org/fossil/doc/tip/www/selfcheck.wiki → [appfileformat.html](appfileformat.md)
- http://www.fossil-scm.org/index.html/doc/tip/www/quickstart.wiki → [privatebranch.html](privatebranch.md)
- http://www.ge.com/ → [famous.html](famous.md)
- http://www.git-scm.org/ → [privatebranch.html](privatebranch.md)
- http://www.google.com/chrome → [famous.html](famous.md)
- http://www.google.com/chrome/ → [uri.html](uri.md)
- http://www.intuit.com/ → [famous.html](famous.md)
- http://www.libreoffice.org/ → [affcase1.html](affcase1.md)
- http://www.mail-archive.com/sqlite-users%40sqlite.org/msg27326.html → [famous.html](famous.md)
- http://www.mail-archive.com/sqlite-users%40sqlite.org/msg27332.html → [famous.html](famous.md)
- http://www.mail-archive.com/sqlite-users%40sqlite.org/msg85350.html → [oldnews.html](oldnews.md)
- http://www.mail-archive.com/sqlite-users@sqlite.org/msg16931.html → [famous.html](famous.md)
- http://www.mcafee.com/ → [famous.html](famous.md)
- http://www.mercurial-scm.org/ → [sessionintro.html](sessionintro.md)
- http://www.microsoft.com/ → [famous.html](famous.md)
- http://www.mingw.org/ → [mingw.html](mingw.md)
- http://www.monotone.ca/ → [privatebranch.html](privatebranch.md)
- http://www.mozilla.com/ → [famous.html](famous.md)
- http://www.mozilla.com/en-US/firefox/new/ → [uri.html](uri.md)
- http://www.mozilla.com/thunderbird/ → [famous.html](famous.md)
- http://www.mozilla.org/ → [oldnews.html](oldnews.md)
- http://www.nds-association.org/ → [famous.html](famous.md)
- http://www.opera.com/ → [uri.html](uri.md)
- http://www.oracle.com/database/index.html → [about.html](about.md)
- http://www.paulgraham.com/ → [version3.html](version3.md)
- http://www.paulgraham.com/acl.html → [version3.html](version3.md)
- http://www.php.net/ → [famous.html](famous.md)
- http://www.postgresql.org/ → [changes.html#version_1_0](changes.md#version_1_0)
- http://www.quickbooks.com/ → [famous.html](famous.md)
- http://www.realbasic.com/ → [famous.html](famous.md)
- http://www.rfc-editor.org/rfc/rfc7159.txt → [oldnews.html](oldnews.md)
- http://www.selenic.com/mercurial/wiki/ → [privatebranch.html](privatebranch.md)
- http://www.stunnel.org/ → [howtocorrupt.html#stalefd](howtocorrupt.md#stalefd)
- http://www.symbian.com/ → [oldnews.html](oldnews.md)
- http://www.tcl-lang.org → [quickstart.html](quickstart.md) [tclsqlite.html](tclsqlite.md) [undoredo.html](undoredo.md)
- http://www.tcl-lang.org/ → [amalgamation.html#amalgbuild](amalgamation.md#amalgbuild) [lang_expr.html#varparam](lang_expr.md#varparam) [testing.html#tcl](testing.md#tcl)
- http://www.tcl-lang.org/cgi-bin/tct/tip/322.html → [changes.html#version_3_6_19](changes.md#version_3_6_19) [releaselog/3_6_19.html](releaselog/3_6_19.md)
- http://www.tcl-lang.org/community/tcl2004/ → [oldnews.html](oldnews.md)
- http://www.tcl-lang.org/doc/tea/ → [tclsqlite.html](tclsqlite.md)
- http://www.tcl.tk → [compile.html#tclapi](compile.md#tclapi)
- http://www.tcl.tk/ → [sqlanalyze.html](sqlanalyze.md) [th3.html](th3.md)
- http://www.valgrind.org/ → [qmplan.html](qmplan.md)
- http://www.w3c.org/TR/NOTE-datetime → [lang_datefunc.html#tmval](lang_datefunc.md#tmval)
- http://www.xojo.com/ → [famous.html](famous.md)
- http://zlib.net/ → [sqlar.html](sqlar.md)
- https://airsdk.harman.com → [famous.html](famous.md)
- https://aws.amazon.com/s3/ → [serverless.html](serverless.md)
- https://blog.regehr.org/archives/1576 → [assert.html](assert.md)
- https://code.facebook.com/posts/313033472212144/debugging-file-corruption-on-ios/ → [howtocorrupt.html#stalefd](howtocorrupt.md#stalefd)
- https://code.facebook.com/projects/658950180885092 → [famous.html](famous.md)
- https://core.tcl.tk/ → [qmplan.html](qmplan.md)
- https://csclub.uwaterloo.ca/~pbarfuss/dekker1971.pdf → [changes.html#version_3_47_0](changes.md#version_3_47_0) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md)
- https://datatracker.ietf.org/doc/html/rfc4648 → [base64.html](base64.md)
- https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting → [cves.html#cvetab](cves.md#cvetab)
- https://developers.google.com/open-source/osa#2005-google-oreilly-open-source-award-winners → [oldnews.html](oldnews.md)
- https://digitalocean.com → [qmplan.html](qmplan.md)
- https://docs.microsoft.com/en-us/azure/cosmos-db/serverless-computing-database → [serverless.html](serverless.md)
- https://en.wikipedia.org/wiki/Abstract_syntax_tree → [amalg-v-canon.html#canon](amalg-v-canon.md#canon) [howitworks.html](howitworks.md) [whybytecode.html](whybytecode.md)
- https://en.wikipedia.org/wiki/ANSI_escape_code → [climode.html#ctrlchr](climode.md#ctrlchr) [lang_corefunc.html#unistr_quote](lang_corefunc.md#unistr_quote) [printf.html#percentq](printf.md#percentq)
- https://en.wikipedia.org/wiki/Artificial_intelligence → [queryplanner.html](queryplanner.md)
- https://en.wikipedia.org/wiki/Assert.h → [assert.html](assert.md)
- https://en.wikipedia.org/wiki/Berkeley_DB → [howitworks.html](howitworks.md)
- https://en.wikipedia.org/wiki/Cmd.exe → [changes.html#version_3_10_0](changes.md#version_3_10_0) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md)
- https://en.wikipedia.org/wiki/Database_index#Clustered → [withoutrowid.html](withoutrowid.md)
- https://en.wikipedia.org/wiki/Database_transaction → [howitworks.html](howitworks.md)
- https://en.wikipedia.org/wiki/Dataflow_programming → [whybytecode.html](whybytecode.md)
- https://en.wikipedia.org/wiki/Declarative_programming → [howitworks.html](howitworks.md)
- https://en.wikipedia.org/wiki/DO-178B → [hirely.html](hirely.md) [qmplan.html](qmplan.md) [th3.html](th3.md)
- https://en.wikipedia.org/wiki/F2FS → [changes.html#version_3_21_0](changes.md#version_3_21_0) [compile.html#enable_batch_atomic_write](compile.md#enable_batch_atomic_write) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- https://en.wikipedia.org/wiki/GNU_Autotools → [changes.html#version_3_49_0](changes.md#version_3_49_0) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md)
- https://en.wikipedia.org/wiki/GNU_bison → [lemon.html](lemon.md)
- https://en.wikipedia.org/wiki/Grey_hat → [news.html](news.md)
- https://en.wikipedia.org/wiki/Hash_join → [optoverview.html#hashjoin](optoverview.md#hashjoin)
- https://en.wikipedia.org/wiki/Imperative_programming → [howitworks.html](howitworks.md)
- https://en.wikipedia.org/wiki/Information_schema → [pragma.html#pragfunc](pragma.md#pragfunc)
- https://en.wikipedia.org/wiki/Java_virtual_machine → [whybytecode.html](whybytecode.md)
- https://en.wikipedia.org/wiki/Julian_day → [quirks.html](quirks.md)
- https://en.wikipedia.org/wiki/LALR_parser → [howitworks.html](howitworks.md) [whybytecode.html](whybytecode.md)
- https://en.wikipedia.org/wiki/Library\_(computing) → [howitworks.html](howitworks.md)
- https://en.wikipedia.org/wiki/Linus%27s_law → [testing.html#3pfuzz](testing.md#3pfuzz)
- https://en.wikipedia.org/wiki/Modified_condition/decision_coverage → [th3.html](th3.md)
- https://en.wikipedia.org/wiki/Mutation_testing → [testing.html#mutationtests](testing.md#mutationtests)
- https://en.wikipedia.org/wiki/Online_analytical_processing → [whybytecode.html](whybytecode.md)
- https://en.wikipedia.org/wiki/Online_transaction_processing → [whybytecode.html](whybytecode.md)
- https://en.wikipedia.org/wiki/Patch\_(Unix) → [sessionintro.html](sessionintro.md)
- https://en.wikipedia.org/wiki/Pushdown_automaton → [amalg-v-canon.html#canon](amalg-v-canon.md#canon)
- https://en.wikipedia.org/wiki/Recursive_descent_parser → [compile.html#json_max_depth](compile.md#json_max_depth)
- https://en.wikipedia.org/wiki/Robustness_principle → [lang_select.html#nonstd](lang_select.md#nonstd) [quirks.html#dblquote](quirks.md#dblquote)
- https://en.wikipedia.org/wiki/RocksDB → [howitworks.html](howitworks.md)
- https://en.wikipedia.org/wiki/ROT13 → [loadext.html#write](loadext.md#write)
- https://en.wikipedia.org/wiki/RPM_Package_Manager → [famous.html](famous.md)
- https://en.wikipedia.org/wiki/Rule_of_Saint_Benedict → [codeofethics.html](codeofethics.md)
- https://en.wikipedia.org/wiki/Scalable_Vector_Graphics → [geopoly.html](geopoly.md) [geopoly.html#gsvg](geopoly.md#gsvg)
- https://en.wikipedia.org/wiki/SHA-3 → [cli.html#sha3sum](cli.md#sha3sum)
- https://en.wikipedia.org/wiki/SQL → [howitworks.html](howitworks.md)
- https://en.wikipedia.org/wiki/SQL_injection → [cves.html#cvetab](cves.md#cvetab)
- https://en.wikipedia.org/wiki/Star_schema → [queryplanner-ng.html#starq](queryplanner-ng.md#starq)
- https://en.wikipedia.org/wiki/Symbian → [sharedcache.html#dontuse](sharedcache.md#dontuse) [th3.html](th3.md)
- https://en.wikipedia.org/wiki/Tar\_(computing) → [sqlar.html](sqlar.md)
- https://en.wikipedia.org/wiki/Tcl → [changes.html#version_3_48_0](changes.md#version_3_48_0) [releaselog/3_48_0.html](releaselog/3_48_0.md) [vtablist.html](vtablist.md)
- https://en.wikipedia.org/wiki/Unit_in_the_last_place → [staleexpridx.html](staleexpridx.md)
- https://en.wikipedia.org/wiki/Unix_time → [lang_datefunc.html](lang_datefunc.md)
- https://en.wikipedia.org/wiki/Web_SQL_Database → [bindptr.html](bindptr.md)
- https://en.wikipedia.org/wiki/WebAssembly → [whybytecode.html](whybytecode.md)
- https://en.wikipedia.org/wiki/Windows_RT → [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- https://en.wikipedia.org/wiki/Yacc → [lemon.html](lemon.md)
- https://en.wikipedia.org/wiki/Zip\_%28file_format%29 → [zipfile.html](zipfile.md)
- https://en.wikipedia.org/wiki/Zip\_(file_format) → [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_22_0.html](releaselog/3_22_0.md) [sqlar.html](sqlar.md) [vtablist.html](vtablist.md)
- https://forums.mcafee.com/t5/WebAdvisor/SQLite-Temporary-Files/m-p/19512 → [famous.html](famous.md)
- https://fossil-scm.org → [qmplan.html](qmplan.md)
- https://fossil-scm.org/ → [changes.html#version_3_28_0](changes.md#version_3_28_0) [download.html#srctree](download.md#srctree) [flextypegood.html](flextypegood.md) [howtocorrupt.html#stalefd](howtocorrupt.md#stalefd) [qmplan.html](qmplan.md) [releaselog/3_28_0.html](releaselog/3_28_0.md) [sqlar.html#dbasobj](sqlar.md#dbasobj) [vtablist.html](vtablist.md) [whynotgit.html](whynotgit.md)
- https://fossil-scm.org/forum → [qmplan.html](qmplan.md)
- https://fossil-scm.org/forum/forumpost/c51b9a1169 → [howtocorrupt.html#stalefd](howtocorrupt.md#stalefd)
- https://fossil-scm.org/fossil → [whynotgit.html](whynotgit.md)
- https://fossil-scm.org/fossil/doc/trunk/www/checkin_names.wiki → [whynotgit.html](whynotgit.md)
- https://fossil-scm.org/fossil/doc/trunk/www/delta_format.wiki → [changes.html#version_3_28_0](changes.md#version_3_28_0) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- https://fossil-scm.org/fossil/doc/trunk/www/fossil-v-git.wiki → [whynotgit.html](whynotgit.md)
- https://fossil-scm.org/fossil/doc/trunk/www/permutedindex.html → [whynotgit.html](whynotgit.md)
- https://fossil-scm.org/fossil/doc/trunk/www/webpage-ex.md → [whynotgit.html](whynotgit.md)
- https://fossil-scm.org/fossil/file/src/foci.c → [vtablist.html](vtablist.md)
- https://fossil-scm.org/fossil/uv/download.html → [whynotgit.html](whynotgit.md)
- https://gcc.gnu.org/onlinedocs/gcc/Gcov.html → [qmplan.html](qmplan.md) [testing.html#mcdc](testing.md#mcdc)
- https://git-man-page-generator.lokaltog.net/ → [whynotgit.html](whynotgit.md)
- https://git-scm.com → [sessionintro.html](sessionintro.md)
- https://git-scm.org → [whynotgit.html](whynotgit.md)
- https://github.com/antirez/linenoise → [changes.html#version_3_8_8_3](changes.md#version_3_8_8_3) [qmplan.html](qmplan.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- https://github.com/chrisdavies/dbench → [fasterthanfs.html](fasterthanfs.md)
- https://github.com/facebook/osquery → [vtablist.html](vtablist.md)
- https://github.com/google/fuzzing/blob/master/docs/structure-aware-fuzzing.md → [testing.html#dbsqlfuzz](testing.md#dbsqlfuzz)
- https://github.com/google/fuzzing/blob/master/docs/structure-aware-fuzzing.md#user-content-example-sqlite → [testing.html#dbsqlfuzz](testing.md#dbsqlfuzz)
- https://github.com/google/oss-fuzz → [changes.html#version_3_16_2](changes.md#version_3_16_2) [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [testing.html#ossfuzz](testing.md#ossfuzz)
- https://github.com/libfuse/libfuse → [sqlar.html#cltools](sqlar.md#cltools)
- https://github.com/sqlite/sqlite → [amalg-v-canon.html#canon](amalg-v-canon.md#canon) [changes.html#version_3_28_0](changes.md#version_3_28_0) [releaselog/3_28_0.html](releaselog/3_28_0.md) [whynotgit.html](whynotgit.md)
- https://github.com/sqlite/sqlite/ → [qmplan.html](qmplan.md)
- https://github.com/sqlite/sqlite/commits/master → [whynotgit.html](whynotgit.md)
- https://github.com/sqlite/sqlite/commits/prefer-coroutine-sort-subquery → [whynotgit.html](whynotgit.md)
- https://github.com/sqlite/sqlite/network → [whynotgit.html](whynotgit.md)
- https://github.com/unicode-org/icu → [staleexpridx.html](staleexpridx.md)
- https://gitup.co/ → [whynotgit.html](whynotgit.md)
- https://golang.org → [assert.html](assert.md)
- https://golang.org/doc/faq#assertions → [assert.html](assert.md)
- https://golangexample.com/an-unscientific-benchmark-of-sqlite-vs-the-file-system-btrfs/ → [fasterthanfs.html](fasterthanfs.md)
- https://icu.unicode.org → [changes.html#version_3_4_0](changes.md#version_3_4_0) [changes.html#version_3_4_1](changes.md#version_3_4_1) [compile.html#enable_icu](compile.md#enable_icu) [quirks.html](quirks.md) [releaselog/3_4_0.html](releaselog/3_4_0.md) [releaselog/3_4_1.html](releaselog/3_4_1.md)
- https://json.org → [json1.html#howtocompile](json1.md#howtocompile) [json1.html#json5](json1.md#json5)
- https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/start-process?view=powershell-7.3 → [uri.html](uri.md)
- https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/start → [uri.html](uri.md)
- https://link.springer.com/book/10.1007/978-1-4302-3226-1 → [oldnews.html](oldnews.md)
- https://link.springer.com/referenceworkentry/10.1007/978-0-387-35973-1_1151 → [rtree.html](rtree.md)
- https://linode.com → [qmplan.html](qmplan.md)
- https://msteveb.github.io/autosetup/ → [changes.html#version_3_48_0](changes.md#version_3_48_0) [changes.html#version_3_49_0](changes.md#version_3_49_0) [news.html](news.md) [releaselog/3_48_0.html](releaselog/3_48_0.md) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md)
- https://news.ycombinator.com/item?id=16585120 → [whyc.html](whyc.md)
- https://news.ycombinator.com/item?id=16806955 → [whynotgit.html](whynotgit.md)
- https://news.ycombinator.com/item?id=17964243 → [news.html](news.md)
- https://news.ycombinator.com/item?id=33975635 → [whentouse.html#website](whentouse.md#website)
- https://nvd.nist.gov/vuln/detail/CVE-2025-29088 → [cves.html#cvetab](cves.md#cvetab)
- https://nvd.nist.gov/vuln/detail/CVE-2025-3277 → [cves.html#cvetab](cves.md#cvetab)
- https://odin.cse.buffalo.edu/papers/2015/TPCTC-sqlite-final.pdf → [sqlar.html#dbasobj](sqlar.md#dbasobj)
- https://osquery.readthedocs.io/en/stable/ → [vtablist.html](vtablist.md)
- https://postgresql.org → [json1.html#jsonbx](json1.md#jsonbx)
- https://pubs.opengroup.org/onlinepubs/9799919799/functions/strftime.html → [lang_datefunc.html#strftm](lang_datefunc.md#strftm)
- https://spec.json5.org/ → [json1.html#howtocompile](json1.md#howtocompile) [json1.html#json5](json1.md#json5)
- https://spec.json5.org/#introduction → [json1.html#json5](json1.md#json5)
- https://sqlite.org → [qmplan.html](qmplan.md)
- https://sqlite.org/ → [qmplan.html](qmplan.md) [whentouse.html#website](whentouse.md#website)
- https://sqlite.org/checklistapp → [qmplan.html](qmplan.md)
- https://sqlite.org/dbsqlfuzz → [qmplan.html](qmplan.md)
- https://sqlite.org/docsrc → [getthecode.html](getthecode.md) [qmplan.html](qmplan.md)
- https://sqlite.org/docsrc/finfo/pages/whynotgit.in → [whynotgit.html](whynotgit.md)
- https://sqlite.org/download.html → [amalg-v-canon.html#canon](amalg-v-canon.md#canon) [howtocompile.html#dll](howtocompile.md#dll) [withoutrowid.html#wtu](withoutrowid.md#wtu)
- https://sqlite.org/fiddle → [quickstart.html](quickstart.md)
- https://sqlite.org/forum → [optoverview.html#option2](optoverview.md#option2) [optoverview.html#uplus](optoverview.md#uplus) [qmplan.html](qmplan.md) [queryplanner-ng.html#howtofix](queryplanner-ng.md#howtofix) [whybytecode.html](whybytecode.md)
- https://sqlite.org/forum/about → [cves.html#cvetab](cves.md#cvetab)
- https://sqlite.org/forum/forum → [flextypegood.html](flextypegood.md) [quirks.html](quirks.md)
- https://sqlite.org/forum/forumpost/02d7be94d7 → [datatype3.html#affcompoundview](datatype3.md#affcompoundview)
- https://sqlite.org/forum/forumpost/0a539c76db3b9e29 → [changes.html#version_3_41_0](changes.md#version_3_41_0) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- https://sqlite.org/forum/forumpost/140a67d3d2 → [changes.html#version_3_35_2](changes.md#version_3_35_2) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- https://sqlite.org/forum/forumpost/171bcc2bcd → [changes.html#version_3_46_1](changes.md#version_3_46_1) [releaselog/3_46_1.html](releaselog/3_46_1.md)
- https://sqlite.org/forum/forumpost/174afeae5734d42d → [changes.html#version_3_39_1](changes.md#version_3_39_1) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- https://sqlite.org/forum/forumpost/23b8688ef4 → [changes.html#version_3_45_3](changes.md#version_3_45_3) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- https://sqlite.org/forum/forumpost/2568d1f6e6 → [changes.html#version_3_45_0](changes.md#version_3_45_0) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- https://sqlite.org/forum/forumpost/284955a3cd454a15 → [changes.html#version_3_45_3](changes.md#version_3_45_3) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- https://sqlite.org/forum/forumpost/3607259d3c → [changes.html#version_3_39_2](changes.md#version_3_39_2) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- https://sqlite.org/forum/forumpost/440f2a2f17 → [changes.html#version_3_45_2](changes.md#version_3_45_2) [news.html](news.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- https://sqlite.org/forum/forumpost/48f365daec → [cves.html#cvetab](cves.md#cvetab)
- https://sqlite.org/forum/forumpost/53de8864ba114bf6 → [cves.html#cvetab](cves.md#cvetab)
- https://sqlite.org/forum/forumpost/569a7209179a7f5e → [changes.html#version_3_47_2](changes.md#version_3_47_2) [releaselog/3_47_2.html](releaselog/3_47_2.md)
- https://sqlite.org/forum/forumpost/58540ce22dcd5fdcd → [changes.html#version_3_35_3](changes.md#version_3_35_3) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- https://sqlite.org/forum/forumpost/6f0958b03b → [changes.html#version_3_45_0](changes.md#version_3_45_0) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- https://sqlite.org/forum/forumpost/719a11e1314d1c70 → [changes.html#version_3_39_3](changes.md#version_3_39_3) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- https://sqlite.org/forum/forumpost/7481d2a6df8980ff → [lang_select.html#bareagg](lang_select.md#bareagg)
- https://sqlite.org/forum/forumpost/761eac3c82 → [cves.html#cvetab](cves.md#cvetab)
- https://sqlite.org/forum/forumpost/919c6579c8 → [changes.html#version_3_45_2](changes.md#version_3_45_2) [news.html](news.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- https://sqlite.org/forum/forumpost/9b9e4716c0d7bbd1 → [changes.html#version_3_39_3](changes.md#version_3_39_3) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- https://sqlite.org/forum/forumpost/9ed02582fe → [changes.html#version_3_35_3](changes.md#version_3_35_3) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- https://sqlite.org/forum/forumpost/aa5a0431c99e631 → [changes.html#version_3_35_3](changes.md#version_3_35_3) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- https://sqlite.org/forum/forumpost/afbbcb5b72 → [changes.html#version_3_35_3](changes.md#version_3_35_3) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- https://sqlite.org/forum/forumpost/b03d86f9516cb3a2 → [changes.html#version_3_37_2](changes.md#version_3_37_2) [howtocorrupt.html#svptbug](howtocorrupt.md#svptbug) [releaselog/3_37_2.html](releaselog/3_37_2.md)
- https://sqlite.org/forum/forumpost/b25edc1d4662ebca → [cves.html#cvetab](cves.md#cvetab)
- https://sqlite.org/forum/forumpost/b52a020ce4 → [changes.html#version_3_35_3](changes.md#version_3_35_3) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- https://sqlite.org/forum/forumpost/e60e4c295d22f8ce → [changes.html#version_3_46_1](changes.md#version_3_46_1) [releaselog/3_46_1.html](releaselog/3_46_1.md)
- https://sqlite.org/forum/forumpost/f4878de3e7dd4764 → [changes.html#version_3_50_3](changes.md#version_3_50_3) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- https://sqlite.org/forum/forumpost/f935c4708dd528d9 → [cves.html#cvetab](cves.md#cvetab)
- https://sqlite.org/optoverview.html#flattening → [news.html](news.md)
- https://sqlite.org/see/doc/trunk/www/readme.wiki → [changes.html#version_3_9_0](changes.md#version_3_9_0) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- https://sqlite.org/sqlar → [sqlar.html#cltools](sqlar.md#cltools)
- https://sqlite.org/sqlar/doc/trunk/README.md → [affcase1.html#smaller](affcase1.md#smaller)
- https://sqlite.org/sqllogictest → [qmplan.html](qmplan.md)
- https://sqlite.org/src → [amalg-v-canon.html#canon](amalg-v-canon.md#canon) [amalgamation.html](amalgamation.md) [changes.html#version_3_28_0](changes.md#version_3_28_0) [cksumvfs.html](cksumvfs.md) [cli.html#arinsup](cli.md#arinsup) [getthecode.html](getthecode.md) [howtocompile.html#amal](howtocompile.md#amal) [index.html](index.md) [privatebranch.html](privatebranch.md) [qmplan.html](qmplan.md) [releaselog/3_28_0.html](releaselog/3_28_0.md) [zipfile.html](zipfile.md)
- https://sqlite.org/src/artifact/18a53540aa3?ln=1679-1680 → [assert.html](assert.md)
- https://sqlite.org/src/artifact/18a53540aa3?ln=4371 → [assert.html](assert.md)
- https://sqlite.org/src/artifact/18a53540aa3?ln=5512-5516 → [assert.html](assert.md)
- https://sqlite.org/src/artifact/18a53540aa3?ln=5766 → [assert.html](assert.md)
- https://sqlite.org/src/artifact/55b5fb474?ln=55-62 → [testing.html#mutationtests](testing.md#mutationtests)
- https://sqlite.org/src/artifact/83f6b3318f7ee → [changes.html#version_3_8_11](changes.md#version_3_8_11) [changes.html#version_3_8_7](changes.md#version_3_8_7) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- https://sqlite.org/src/artifact/c1e97e4c6f?ln=1048 → [assert.html](assert.md)
- https://sqlite.org/src/artifact/c1e97e4c6f?ln=157 → [assert.html](assert.md)
- https://sqlite.org/src/artifact/c1e97e4c6f?ln=2130-2138 → [assert.html](assert.md)
- https://sqlite.org/src/artifact/d29c8048beb7e → [oldnews.html](oldnews.md)
- https://sqlite.org/src/artifact/d7cc99350?ln=403-443 → [changes.html#version_3_12_0](changes.md#version_3_12_0) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md)
- https://sqlite.org/src/artifact/f971962e92ebb8b0 → [changes.html#version_3_8_8](changes.md#version_3_8_8) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- https://sqlite.org/src/artifact?ci=trunk&filename=ext/misc/csv.c → [csv.html](csv.md)
- https://sqlite.org/src/artifact?ci=trunk&filename=ext/misc/fileio.c → [cli.html#fileio](cli.md#fileio)
- https://sqlite.org/src/artifact?ci=trunk&filename=ext/misc/series.c → [vtab.html#tabfunc2](vtab.md#tabfunc2)
- https://sqlite.org/src/artifact?ci=trunk&filename=ext/misc/vfsstat.c → [changes.html#version_3_14](changes.md#version_3_14) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- https://sqlite.org/src/artifact?ci=trunk&filename=magic.txt → [fileformat2.html#appid](fileformat2.md#appid) [pragma.html#pragma_application_id](pragma.md#pragma_application_id)
- https://sqlite.org/src/artifact?ci=trunk&filename=src/parse.y → [amalgamation.html](amalgamation.md)
- https://sqlite.org/src/artifact?ci=trunk&filename=tool/dbhash.c → [dbhash.html](dbhash.md)
- https://sqlite.org/src/dir/ext/icu → [changes.html#version_3_39_4](changes.md#version_3_39_4) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- https://sqlite.org/src/dir?ci=trunk&type=tree → [vtab.html#customvtab](vtab.md#customvtab)
- https://sqlite.org/src/doc/trunk/doc/compile-for-unix.md → [howtocompile.html](howtocompile.md)
- https://sqlite.org/src/doc/trunk/doc/compile-for-windows.md → [howtocompile.html](howtocompile.md)
- https://sqlite.org/src/doc/trunk/doc/lemon.html → [lemon.html](lemon.md)
- https://sqlite.org/src/doc/trunk/ext/misc/appendvfs.c → [cves.html#cvetab](cves.md#cvetab)
- https://sqlite.org/src/doc/trunk/ext/misc/vfstrace.c → [vfs.html#shim](vfs.md#shim)
- https://sqlite.org/src/doc/trunk/ext/userauth/user-auth.txt → [changes.html#version_3_8_7](changes.md#version_3_8_7) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- https://sqlite.org/src/doc/trunk/src/date.c → [cintro.html](cintro.md)
- https://sqlite.org/src/doc/trunk/src/func.c → [cintro.html](cintro.md)
- https://sqlite.org/src/doc/trunk/src/os_unix.c → [vfs.html](vfs.md)
- https://sqlite.org/src/doc/trunk/src/test_demovfs.c → [vfs.html#shim](vfs.md#shim)
- https://sqlite.org/src/doc/trunk/src/test_journal.c → [vfs.html#shim](vfs.md#shim)
- https://sqlite.org/src/doc/trunk/src/test_multiplex.c → [vfs.html#shim](vfs.md#shim)
- https://sqlite.org/src/doc/trunk/src/test_onefile.c → [vfs.html#shim](vfs.md#shim)
- https://sqlite.org/src/doc/trunk/src/test_quota.c → [vfs.html#shim](vfs.md#shim)
- https://sqlite.org/src/doc/trunk/src/test_vfs.c → [vfs.html#shim](vfs.md#shim)
- https://sqlite.org/src/doc/trunk/tool/dbtotxt.md → [changes.html#version_3_27_0](changes.md#version_3_27_0) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- https://sqlite.org/src/ext/checklist/top/index → [qmplan.html](qmplan.md)
- https://sqlite.org/src/fdiff?sbs=1&v1=7d539cedb1c&v2=ebad891b7494d&smhdr → [changes.html#version_3_8_4_3](changes.md#version_3_8_4_3) [oldnews.html](oldnews.md) [releaselog/3_8_4_3.html](releaselog/3_8_4_3.md)
- https://sqlite.org/src/fdiff?sbs=1&v1=869c95b0fc73026d&v2=232c242a0ccb3d67 → [changes.html#version_3_10_0](changes.md#version_3_10_0) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md)
- https://sqlite.org/src/fdiff?v1=e45e3f9daf38c5be&v2=714df4e1c82f629d&sbs=1 → [oldnews.html](oldnews.md)
- https://sqlite.org/src/file/doc/compile-for-unix.md → [amalg-v-canon.html#canon](amalg-v-canon.md#canon)
- https://sqlite.org/src/file/doc/compile-for-windows.md → [amalg-v-canon.html#canon](amalg-v-canon.md#canon)
- https://sqlite.org/src/file/doc/tcl-extension-testing.md → [tclsqlite.html](tclsqlite.md)
- https://sqlite.org/src/file/ext → [loadext.html#write](loadext.md#write)
- https://sqlite.org/src/file/ext/fts5/fts5parse.y → [lemon.html](lemon.md)
- https://sqlite.org/src/file/ext/misc → [base64.html](base64.md) [base85.html](base85.md) [cli.html#arinsup](cli.md#arinsup) [loadext.html#write](loadext.md#write) [uintcseq.html](uintcseq.md)
- https://sqlite.org/src/file/ext/misc/anycollseq.c → [changes.html#version_3_19_0](changes.md#version_3_19_0) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md)
- https://sqlite.org/src/file/ext/misc/appendvfs.c → [changes.html#version_3_22_0](changes.md#version_3_22_0) [changes.html#version_3_35_2](changes.md#version_3_35_2) [cli.html#arinsup](cli.md#arinsup) [cli.html#dotopen](cli.md#dotopen) [cli.html#sqlar](cli.md#sqlar) [releaselog/3_22_0.html](releaselog/3_22_0.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [vfs.html#shim](vfs.md#shim)
- https://sqlite.org/src/file/ext/misc/base64.c → [base64.html](base64.md)
- https://sqlite.org/src/file/ext/misc/base85.c → [base85.html](base85.md)
- https://sqlite.org/src/file/ext/misc/btreeinfo.c → [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_22_0.html](releaselog/3_22_0.md) [vtablist.html](vtablist.md)
- https://sqlite.org/src/file/ext/misc/carray.c → [loadext.html#write](loadext.md#write)
- https://sqlite.org/src/file/ext/misc/cksumvfs.c → [cksumvfs.html](cksumvfs.md)
- https://sqlite.org/src/file/ext/misc/closure.c → [vtablist.html](vtablist.md)
- https://sqlite.org/src/file/ext/misc/compress.c → [loadext.html#write](loadext.md#write)
- https://sqlite.org/src/file/ext/misc/csv.c → [vtab.html#customvtab](vtab.md#customvtab)
- https://sqlite.org/src/file/ext/misc/dbdata.c → [changes.html#version_3_29_0](changes.md#version_3_29_0) [releaselog/3_29_0.html](releaselog/3_29_0.md)
- https://sqlite.org/src/file/ext/misc/eval.c → [changes.html#version_3_23_1](changes.md#version_3_23_1) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/file/ext/misc/explain.c → [changes.html#version_3_26_0](changes.md#version_3_26_0) [releaselog/3_26_0.html](releaselog/3_26_0.md)
- https://sqlite.org/src/file/ext/misc/fileio.c → [changes.html#version_3_22_0](changes.md#version_3_22_0) [changes.html#version_3_23_0](changes.md#version_3_23_0) [cli.html#arinsup](cli.md#arinsup) [releaselog/3_22_0.html](releaselog/3_22_0.md) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [vtablist.html](vtablist.md)
- https://sqlite.org/src/file/ext/misc/fossildelta.c → [changes.html#version_3_28_0](changes.md#version_3_28_0) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- https://sqlite.org/src/file/ext/misc/memstat.c → [memstat.html](memstat.md)
- https://sqlite.org/src/file/ext/misc/normalize.c → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/file/ext/misc/regexp.c → [changes.html#version_3_36_0](changes.md#version_3_36_0) [releaselog/3_36_0.html](releaselog/3_36_0.md)
- https://sqlite.org/src/file/ext/misc/remember.c → [bindptr.html#ptrtyp](bindptr.md#ptrtyp) [changes.html#version_3_16_0](changes.md#version_3_16_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- https://sqlite.org/src/file/ext/misc/rot13.c → [loadext.html#write](loadext.md#write)
- https://sqlite.org/src/file/ext/misc/series.c → [loadext.html#write](loadext.md#write) [vtab.html#customvtab](vtab.md#customvtab)
- https://sqlite.org/src/file/ext/misc/sha1.c → [changes.html#version_3_17_0](changes.md#version_3_17_0) [releaselog/3_17_0.html](releaselog/3_17_0.md)
- https://sqlite.org/src/file/ext/misc/shathree.c → [cli.html#sha3sum](cli.md#sha3sum)
- https://sqlite.org/src/file/ext/misc/sqlar.c → [cli.html#arinsup](cli.md#arinsup) [sqlar.html#cltools](sqlar.md#cltools) [sqlar.html#dbasobj](sqlar.md#dbasobj)
- https://sqlite.org/src/file/ext/misc/stmt.c → [stmt.html](stmt.md)
- https://sqlite.org/src/file/ext/misc/templatevtab.c → [vtab.html#customvtab](vtab.md#customvtab) [vtablist.html](vtablist.md)
- https://sqlite.org/src/file/ext/misc/uint.c → [uintcseq.html](uintcseq.md)
- https://sqlite.org/src/file/ext/misc/unionvtab.c → [changes.html#version_3_21_0](changes.md#version_3_21_0) [releaselog/3_21_0.html](releaselog/3_21_0.md) [unionvtab.html](unionvtab.md)
- https://sqlite.org/src/file/ext/misc/uuid.c → [changes.html#version_3_31_0](changes.md#version_3_31_0) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- https://sqlite.org/src/file/ext/misc/vfsstat.c → [loadext.html#persist](loadext.md#persist) [vtablist.html](vtablist.md)
- https://sqlite.org/src/file/ext/misc/vtablog.c → [vtablist.html](vtablist.md)
- https://sqlite.org/src/file/ext/misc/wholenumber.c → [changes.html#version_3_35_3](changes.md#version_3_35_3) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [vtablist.html](vtablist.md)
- https://sqlite.org/src/file/ext/misc/zipfile.c → [zipfile.html](zipfile.md)
- https://sqlite.org/src/file/ext/qrf → [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [tclsqlite.html#format](tclsqlite.md#format)
- https://sqlite.org/src/file/ext/qrf/README.md → [tclsqlite.html#format](tclsqlite.md#format)
- https://sqlite.org/src/file/ext/qrf/README.md#spec → [tclsqlite.html#format](tclsqlite.md#format)
- https://sqlite.org/src/file/ext/recover/sqlite3recover.h → [recovery.html](recovery.md)
- https://sqlite.org/src/file/ext/session/changesetfuzz.c → [changes.html#version_3_26_0](changes.md#version_3_26_0) [releaselog/3_26_0.html](releaselog/3_26_0.md)
- https://sqlite.org/src/file/src/dbpage.c → [changes.html#version_3_21_0](changes.md#version_3_21_0) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- https://sqlite.org/src/file/src/json.c → [vtab.html#customvtab](vtab.md#customvtab)
- https://sqlite.org/src/file/src/parse.y → [amalg-v-canon.html#canon](amalg-v-canon.md#canon) [lemon.html](lemon.md)
- https://sqlite.org/src/file/src/printf.c → [printf.html#comma](printf.md#comma)
- https://sqlite.org/src/file/src/shell.c.in → [c_interface.html](c_interface.md) [cli.html#compiling](cli.md#compiling) [cli.html#param](cli.md#param) [completion.html](completion.md)
- https://sqlite.org/src/file/src/tclsqlite.c → [c_interface.html](c_interface.md) [tclsqlite.html](tclsqlite.md)
- https://sqlite.org/src/file/src/test_tclvar.c → [vtablist.html](vtablist.md)
- https://sqlite.org/src/file/src/vdbe.c → [opcode.html](opcode.md)
- https://sqlite.org/src/file/test/kvtest.c → [fasterthanfs.html](fasterthanfs.md)
- https://sqlite.org/src/file/test/ossfuzz.c → [testing.html#ossfuzz](testing.md#ossfuzz)
- https://sqlite.org/src/file/test/speedtest.md → [cpu.html](cpu.md)
- https://sqlite.org/src/file/test/speedtest.tcl → [cpu.html](cpu.md)
- https://sqlite.org/src/file/test/speedtest1.c → [cpu.html](cpu.md)
- https://sqlite.org/src/file/test/starschema1.test → [queryplanner-ng.html#starq](queryplanner-ng.md#starq)
- https://sqlite.org/src/file/tool/cg_anno.tcl → [cpu.html#microopt](cpu.md#microopt)
- https://sqlite.org/src/file/tool/lemon.c → [lemon.html](lemon.md)
- https://sqlite.org/src/file/tool/lempar.c → [lemon.html](lemon.md)
- https://sqlite.org/src/file/tool/speed-check.sh → [cpu.html](cpu.md) [cpu.html#microopt](cpu.md#microopt)
- https://sqlite.org/src/finfo?name=ext/misc/fileio.c → [changes.html#version_3_8_6](changes.md#version_3_8_6) [releaselog/3_8_6.html](releaselog/3_8_6.md)
- https://sqlite.org/src/finfo?name=ext/misc/spellfix.c → [spellfix1.html](spellfix1.md)
- https://sqlite.org/src/finfo?name=src/shell.c → [changes.html#version_3_21_0](changes.md#version_3_21_0) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- https://sqlite.org/src/info/0249d9aecf69948d → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/04925dee41a21f → [changes.html#version_3_21_0](changes.md#version_3_21_0) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- https://sqlite.org/src/info/05f43be8fdda9f → [compile.html#like_doesnt_match_blobs](compile.md#like_doesnt_match_blobs)
- https://sqlite.org/src/info/06796225f59c057c → [changes.html#version_3_18_0](changes.md#version_3_18_0) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md)
- https://sqlite.org/src/info/07d6a0453d → [changes.html#version_3_8_5](changes.md#version_3_8_5) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- https://sqlite.org/src/info/093420fc0eb7cba7 → [changes.html#version_3_23_1](changes.md#version_3_23_1) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/094d39a4c95ee4 → [changes.html#version_3_8_7_2](changes.md#version_3_8_7_2) [releaselog/3_8_7_2.html](releaselog/3_8_7_2.md)
- https://sqlite.org/src/info/0c4df46116e90f92 → [changes.html#version_3_14_2](changes.md#version_3_14_2) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- https://sqlite.org/src/info/0eab1ac759 → [changes.html#version_3_15_0](changes.md#version_3_15_0) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md)
- https://sqlite.org/src/info/0eb70d77cb05bb2272 → [changes.html#version_3_7_17](changes.md#version_3_7_17) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- https://sqlite.org/src/info/0fc59f908b → [changes.html#version_3_7_17](changes.md#version_3_7_17) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- https://sqlite.org/src/info/1079ad19993d13fa → [changes.html#version_3_30_1](changes.md#version_3_30_1) [releaselog/3_30_1.html](releaselog/3_30_1.md)
- https://sqlite.org/src/info/10fb063b11 → [changes.html#version_3_8_5](changes.md#version_3_8_5) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- https://sqlite.org/src/info/11d5aa455e0d98f3c1e6a08 → [changes.html#version_3_8_7](changes.md#version_3_8_7) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- https://sqlite.org/src/info/123c9ba32130a6c9 → [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_22_0.html](releaselog/3_22_0.md)
- https://sqlite.org/src/info/12ad822d9b827777 → [cves.html#cvetab](cves.md#cvetab)
- https://sqlite.org/src/info/132994c8b1063bfb → [changes.html#version_3_35_4](changes.md#version_3_35_4) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- https://sqlite.org/src/info/16c9801ceba49 → [changes.html#version_3_13_0](changes.md#version_3_13_0) [releaselog/3_13_0.html](releaselog/3_13_0.md)
- https://sqlite.org/src/info/190c2507 → [changes.html#version_3_16_2](changes.md#version_3_16_2) [releaselog/3_16_2.html](releaselog/3_16_2.md)
- https://sqlite.org/src/info/199df4168c → [changes.html#version_3_14_2](changes.md#version_3_14_2) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- https://sqlite.org/src/info/1a84668dcfdebaf12415d → [changes.html#version_3_25_3](changes.md#version_3_25_3) [releaselog/3_25_3.html](releaselog/3_25_3.md)
- https://sqlite.org/src/info/1c24a659e6d7f3a1 → [changes.html#version_3_35_1](changes.md#version_3_35_1) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- https://sqlite.org/src/info/1d958d90596593a774 → [changes.html#version_3_27_0](changes.md#version_3_27_0) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- https://sqlite.org/src/info/1e39b966ae9ee739 → [changes.html#version_3_23_1](changes.md#version_3_23_1) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/1ec41379c9c1e400 → [changes.html#version_3_15_0](changes.md#version_3_15_0) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md)
- https://sqlite.org/src/info/2025-02-16T10:57z → [cves.html#cvetab](cves.md#cvetab)
- https://sqlite.org/src/info/202502171416Z → [cves.html#cvetab](cves.md#cvetab)
- https://sqlite.org/src/info/2326c258d02ead33 → [changes.html#version_3_8_8_3](changes.md#version_3_8_8_3) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- https://sqlite.org/src/info/2500cdb9be05 → [changes.html#version_3_7_17](changes.md#version_3_7_17) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- https://sqlite.org/src/info/25e335f802dd → [changes.html#version_3_17_0](changes.md#version_3_17_0) [releaselog/3_17_0.html](releaselog/3_17_0.md)
- https://sqlite.org/src/info/25ee812710 → [changes.html#version_3_7_7_1](changes.md#version_3_7_7_1) [oldnews.html](oldnews.md) [releaselog/3_7_7_1.html](releaselog/3_7_7_1.md)
- https://sqlite.org/src/info/264b970c4379fd → [changes.html#version_3_8_5](changes.md#version_3_8_5) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- https://sqlite.org/src/info/27754b74ddf64 → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/2a5629202f → [changes.html#version_3_7_12](changes.md#version_3_7_12) [releaselog/3_7_12.html](releaselog/3_7_12.md)
- https://sqlite.org/src/info/2b8aed9f7c9e61e8 → [changes.html#version_3_23_1](changes.md#version_3_23_1) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/2c6c8689fb5f3d2f → [changes.html#version_3_35_2](changes.md#version_3_35_2) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- https://sqlite.org/src/info/2d1a5c67df → [oldnews.html](oldnews.md)
- https://sqlite.org/src/info/2df0107b → [changes.html#version_3_16_0](changes.md#version_3_16_0) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md)
- https://sqlite.org/src/info/2df6bbf1b8ca8 → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/2ea3e9fe63 → [changes.html#version_3_8_5](changes.md#version_3_8_5) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- https://sqlite.org/src/info/2f1b168ab4d4844 → [changes.html#version_3_15_2](changes.md#version_3_15_2) [releaselog/3_15_2.html](releaselog/3_15_2.md)
- https://sqlite.org/src/info/30027b613b4 → [changes.html#version_3_16_2](changes.md#version_3_16_2) [news.html](news.md) [releaselog/3_16_2.html](releaselog/3_16_2.md)
- https://sqlite.org/src/info/30475c820dc5ab8a8?ln=999,1026 → [recovery.html](recovery.md)
- https://sqlite.org/src/info/31338dca7e → [oldnews.html](oldnews.md)
- https://sqlite.org/src/info/343634942dd54ab → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/34a579141b2c5ac → [changes.html#version_3_15_1](changes.md#version_3_15_1) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md)
- https://sqlite.org/src/info/34cd55d6 → [oldnews.html](oldnews.md)
- https://sqlite.org/src/info/34cd55d68e0e6e7c9a0711aab81a2ee3c354b4c0 → [changes.html#version_3_8_10_2](changes.md#version_3_8_10_2) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md)
- https://sqlite.org/src/info/369d57fb8e5ccdff06f1 → [changes.html#version_3_8_7](changes.md#version_3_8_7) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- https://sqlite.org/src/info/36fae083b450e3a → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/385a5b56b9 → [changes.html#version_3_7_12](changes.md#version_3_7_12) [releaselog/3_7_12.html](releaselog/3_7_12.md)
- https://sqlite.org/src/info/38b1ae018f → [changes.html#version_3_7_16_1](changes.md#version_3_7_16_1) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md)
- https://sqlite.org/src/info/3a88d85f36704eebe1 → [changes.html#version_3_8_6](changes.md#version_3_8_6) [releaselog/3_8_6.html](releaselog/3_8_6.md)
- https://sqlite.org/src/info/3b4450072511e621 → [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_22_0.html](releaselog/3_22_0.md)
- https://sqlite.org/src/info/43107840f1c02 → [oldnews.html](oldnews.md)
- https://sqlite.org/src/info/47b2581aa9bfecec → [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_22_0.html](releaselog/3_22_0.md)
- https://sqlite.org/src/info/4ba5abf65c5b0f9a96a7a → [changes.html#version_3_24_0](changes.md#version_3_24_0) [releaselog/3_24_0.html](releaselog/3_24_0.md)
- https://sqlite.org/src/info/4c86b126f2 → [changes.html#version_3_8_3_1](changes.md#version_3_8_3_1) [changes.html#version_3_8_4](changes.md#version_3_8_4) [oldnews.html](oldnews.md) [releaselog/3_8_3_1.html](releaselog/3_8_3_1.md) [releaselog/3_8_4.html](releaselog/3_8_4.md) [releaselog/3_8_4_1.html](releaselog/3_8_4_1.md) [releaselog/3_8_4_2.html](releaselog/3_8_4_2.md) [releaselog/3_8_4_3.html](releaselog/3_8_4_3.md)
- https://sqlite.org/src/info/4e8e4857d32d401f → [changes.html#version_3_27_1](changes.md#version_3_27_1) [news.html](news.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- https://sqlite.org/src/info/4ef7e3cfca → [changes.html#version_3_8_4](changes.md#version_3_8_4) [releaselog/3_8_4.html](releaselog/3_8_4.md) [releaselog/3_8_4_1.html](releaselog/3_8_4_1.md) [releaselog/3_8_4_2.html](releaselog/3_8_4_2.md) [releaselog/3_8_4_3.html](releaselog/3_8_4_3.md)
- https://sqlite.org/src/info/4feb3159c6bc3f7e33959 → [changes.html#version_3_27_2](changes.md#version_3_27_2) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- https://sqlite.org/src/info/510cde277783b5fb → [changes.html#version_3_25_1](changes.md#version_3_25_1) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md)
- https://sqlite.org/src/info/5232c9777fe4fb13 → [changes.html#version_3_37_2](changes.md#version_3_37_2) [releaselog/3_37_2.html](releaselog/3_37_2.md)
- https://sqlite.org/src/info/525deb7a67fbd647 → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/5508b56fd24016c1 → [cves.html#cvetab](cves.md#cvetab)
- https://sqlite.org/src/info/55746f9e65f85 → [changes.html#version_3_8_5](changes.md#version_3_8_5) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- https://sqlite.org/src/info/559733b09e9630fa → [changes.html#version_3_15_0](changes.md#version_3_15_0) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md)
- https://sqlite.org/src/info/57eec374ae1d0a1d → [changes.html#version_3_9_1](changes.md#version_3_9_1) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- https://sqlite.org/src/info/57eec374ae1d0a1d4a → [oldnews.html](oldnews.md)
- https://sqlite.org/src/info/5948e09b8c415bc45d → [changes.html#version_3_27_0](changes.md#version_3_27_0) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- https://sqlite.org/src/info/598f5f7596b055 → [changes.html#version_3_7_15_2](changes.md#version_3_7_15_2) [releaselog/3_7_15_2.html](releaselog/3_7_15_2.md)
- https://sqlite.org/src/info/5d863f876e → [changes.html#version_3_7_5](changes.md#version_3_7_5) [releaselog/3_7_5.html](releaselog/3_7_5.md)
- https://sqlite.org/src/info/5e3c886796e5512e → [changes.html#version_3_12_0](changes.md#version_3_12_0) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md)
- https://sqlite.org/src/info/6097cb92745327a1 → [changes.html#version_3_18_0](changes.md#version_3_18_0) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md)
- https://sqlite.org/src/info/61fe9745 → [changes.html#version_3_18_2](changes.md#version_3_18_2) [changes.html#version_3_19_0](changes.md#version_3_19_0) [news.html](news.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md)
- https://sqlite.org/src/info/63595b74956a9391 → [cves.html#cvetab](cves.md#cvetab)
- https://sqlite.org/src/info/6484e6ce678fffab → [changes.html#version_3_31_0](changes.md#version_3_31_0) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- https://sqlite.org/src/info/65bdeb9739 → [changes.html#version_3_8_4](changes.md#version_3_8_4) [releaselog/3_8_4.html](releaselog/3_8_4.md) [releaselog/3_8_4_1.html](releaselog/3_8_4_1.md) [releaselog/3_8_4_2.html](releaselog/3_8_4_2.md) [releaselog/3_8_4_3.html](releaselog/3_8_4_3.md)
- https://sqlite.org/src/info/65eb38f6e46de8c75e188a17ec → [changes.html#version_3_25_3](changes.md#version_3_25_3) [releaselog/3_25_3.html](releaselog/3_25_3.md)
- https://sqlite.org/src/info/6709574d2a8d8 → [changes.html#version_3_7_17](changes.md#version_3_7_17) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- https://sqlite.org/src/info/689137afb6da41 → [changes.html#version_3_7_16_1](changes.md#version_3_7_16_1) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md)
- https://sqlite.org/src/info/69d642332d25aa3b7315a6d385 → [changes.html#version_3_25_3](changes.md#version_3_25_3) [releaselog/3_25_3.html](releaselog/3_25_3.md)
- https://sqlite.org/src/info/6bfb98dfc0c → [changes.html#version_3_7_16_1](changes.md#version_3_7_16_1) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md)
- https://sqlite.org/src/info/6c9b5514077fed34551 → [changes.html#version_3_19_0](changes.md#version_3_19_0) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md)
- https://sqlite.org/src/info/6ee8cb6ae5 → [changes.html#version_3_21_0](changes.md#version_3_21_0) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- https://sqlite.org/src/info/6f2222d550f5b0ee7ed → [changes.html#version_3_8_7_3](changes.md#version_3_8_7_3) [changes.html#version_3_8_8](changes.md#version_3_8_8) [releaselog/3_8_7_3.html](releaselog/3_8_7_3.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- https://sqlite.org/src/info/7310e2fb3d046a5 → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/73c2b50211d3ae26 → [changes.html#version_3_37_2](changes.md#version_3_37_2) [howtocorrupt.html#svptbug](howtocorrupt.md#svptbug) [releaselog/3_37_2.html](releaselog/3_37_2.md)
- https://sqlite.org/src/info/7486aa54b968e9b → [changes.html#version_3_21_0](changes.md#version_3_21_0) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- https://sqlite.org/src/info/7486aa54b968e9b5 → [changes.html#version_3_20_1](changes.md#version_3_20_1) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- https://sqlite.org/src/info/77b5b4235c9f7f11?ln=801-819 → [loadext.html#persist](loadext.md#persist)
- https://sqlite.org/src/info/79cad5e4b2e219dd197242e9e → [changes.html#version_3_25_0](changes.md#version_3_25_0) [releaselog/3_25_0.html](releaselog/3_25_0.md) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md)
- https://sqlite.org/src/info/7b3328086a5c116c → [changes.html#version_3_15_0](changes.md#version_3_15_0) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md)
- https://sqlite.org/src/info/7bbfb7d442 → [changes.html#version_3_7_10](changes.md#version_3_7_10) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- https://sqlite.org/src/info/7be932dfa60a8a6b3b26bcf76 → [changes.html#version_3_25_0](changes.md#version_3_25_0) [releaselog/3_25_0.html](releaselog/3_25_0.md) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md)
- https://sqlite.org/src/info/7c6d876f84e6e7e2 → [changes.html#version_3_32_3](changes.md#version_3_32_3) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- https://sqlite.org/src/info/7ce4e71c1b7251be → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/7d7525cb01b68 → [changes.html#version_3_12_2](changes.md#version_3_12_2) [changes.html#version_3_13_0](changes.md#version_3_13_0) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_13_0.html](releaselog/3_13_0.md)
- https://sqlite.org/src/info/7f7f8026eda38 → [changes.html#version_3_12_1](changes.md#version_3_12_1) [changes.html#version_3_13_0](changes.md#version_3_13_0) [news.html](news.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_13_0.html](releaselog/3_13_0.md)
- https://sqlite.org/src/info/7fa8049685b50b5aeb0c2 → [changes.html#version_3_24_0](changes.md#version_3_24_0) [releaselog/3_24_0.html](releaselog/3_24_0.md)
- https://sqlite.org/src/info/7fde638e94287d2c → [changes.html#version_3_19_2](changes.md#version_3_19_2) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md)
- https://sqlite.org/src/info/7ff3120e4f → [changes.html#version_3_7_16_2](changes.md#version_3_7_16_2) [oldnews.html](oldnews.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md)
- https://sqlite.org/src/info/7ffd1ca1d2ad4ec → [changes.html#version_3_17_0](changes.md#version_3_17_0) [releaselog/3_17_0.html](releaselog/3_17_0.md)
- https://sqlite.org/src/info/80177f0c226ff54 → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/80369eddd5c94 → [changes.html#version_3_10_2](changes.md#version_3_10_2) [news.html](news.md) [releaselog/3_10_2.html](releaselog/3_10_2.md)
- https://sqlite.org/src/info/80ba201079 → [changes.html#version_3_7_4](changes.md#version_3_7_4) [oldnews.html](oldnews.md) [releaselog/3_7_4.html](releaselog/3_7_4.md)
- https://sqlite.org/src/info/810dc8038872e212 → [changes.html#version_3_32_2](changes.md#version_3_32_2) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- https://sqlite.org/src/info/823779d31eb09cda → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/84bb08d8762920285f08f1c0?ln=7299,7361 → [recovery.html](recovery.md)
- https://sqlite.org/src/info/863c171b76cd36e0 → [wal.html#walresetbug](wal.md#walresetbug)
- https://sqlite.org/src/info/86ba67afafded936 → [changes.html#version_3_32_0](changes.md#version_3_32_0) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- https://sqlite.org/src/info/873cae2b6e25b → [changes.html#version_3_8_11](changes.md#version_3_8_11) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- https://sqlite.org/src/info/892fc34f173e99d8 → [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- https://sqlite.org/src/info/8a2adec1 → [changes.html#version_3_9_2](changes.md#version_3_9_2) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- https://sqlite.org/src/info/8c63ff0eca → [changes.html#version_3_8_4](changes.md#version_3_8_4) [releaselog/3_8_4.html](releaselog/3_8_4.md) [releaselog/3_8_4_1.html](releaselog/3_8_4_1.md) [releaselog/3_8_4_2.html](releaselog/3_8_4_2.md) [releaselog/3_8_4_3.html](releaselog/3_8_4_3.md)
- https://sqlite.org/src/info/8c9458e7 → [changes.html#version_3_16_1](changes.md#version_3_16_1) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md)
- https://sqlite.org/src/info/8f157e8010b22af0 → [changes.html#version_3_32_3](changes.md#version_3_32_3) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- https://sqlite.org/src/info/8fd39115d8f46 → [changes.html#version_3_8_11](changes.md#version_3_8_11) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- https://sqlite.org/src/info/96c1454cbfd9509 → [changes.html#version_3_15_0](changes.md#version_3_15_0) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md)
- https://sqlite.org/src/info/9766b47beb9ec72f → [cves.html#cvetab](cves.md#cvetab)
- https://sqlite.org/src/info/981329adeef51011052 → [changes.html#version_3_19_0](changes.md#version_3_19_0) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md)
- https://sqlite.org/src/info/98825a79ce1456863 → [changes.html#version_3_8_4_3](changes.md#version_3_8_4_3) [releaselog/3_8_4_3.html](releaselog/3_8_4_3.md)
- https://sqlite.org/src/info/98825a79ce145686392d8074032ae54863aa21a3 → [oldnews.html](oldnews.md)
- https://sqlite.org/src/info/98d973b8f5 → [changes.html#version_3_8_7](changes.md#version_3_8_7) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- https://sqlite.org/src/info/9936b2fa443fec03ff25 → [changes.html#version_3_25_0](changes.md#version_3_25_0) [news.html](news.md) [releaselog/3_25_0.html](releaselog/3_25_0.md) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md)
- https://sqlite.org/src/info/9a6daf340df99ba93c → [changes.html#version_3_8_6](changes.md#version_3_8_6) [oldnews.html](oldnews.md) [releaselog/3_8_6.html](releaselog/3_8_6.md)
- https://sqlite.org/src/info/9a8b09f8e6 → [changes.html#version_3_8_6](changes.md#version_3_8_6) [releaselog/3_8_6.html](releaselog/3_8_6.md)
- https://sqlite.org/src/info/9b78184be266fd70 → [news.html](news.md)
- https://sqlite.org/src/info/9fb26d37cefaba40 → [changes.html#version_3_32_3](changes.md#version_3_32_3) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- https://sqlite.org/src/info/a179fe7465 → [changes.html#version_3_7_16_1](changes.md#version_3_7_16_1) [oldnews.html](oldnews.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md)
- https://sqlite.org/src/info/a306e56ff68b8fa5 → [changes.html#version_3_12_2](changes.md#version_3_12_2) [changes.html#version_3_13_0](changes.md#version_3_13_0) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_13_0.html](releaselog/3_13_0.md)
- https://sqlite.org/src/info/a4e06e75a9ab61a12 → [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- https://sqlite.org/src/info/a59ae93ee990a55 → [changes.html#version_3_8_8](changes.md#version_3_8_8) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- https://sqlite.org/src/info/a5c8ed66ca → [changes.html#version_3_8_1](changes.md#version_3_8_1) [oldnews.html](oldnews.md) [releaselog/3_8_1.html](releaselog/3_8_1.md)
- https://sqlite.org/src/info/a7b7803e8d1e869 → [changes.html#version_3_7_15_1](changes.md#version_3_7_15_1) [releaselog/3_7_15_1.html](releaselog/3_7_15_1.md)
- https://sqlite.org/src/info/a8a0d2996a → [changes.html#version_3_8_5](changes.md#version_3_8_5) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- https://sqlite.org/src/info/aa98619ad08ddca → [changes.html#version_3_21_0](changes.md#version_3_21_0) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- https://sqlite.org/src/info/aa98619ad08ddcab → [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_22_0.html](releaselog/3_22_0.md)
- https://sqlite.org/src/info/ac0ff496b7e2 → [changes.html#version_3_7_10](changes.md#version_3_7_10) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- https://sqlite.org/src/info/ac661962a2aeab3c331 → [changes.html#version_3_9_2](changes.md#version_3_9_2) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- https://sqlite.org/src/info/ad2559db380abf8 → [changes.html#version_3_11_0](changes.md#version_3_11_0) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md)
- https://sqlite.org/src/info/b2fa5424e6fcb15 → [changes.html#version_3_8_6](changes.md#version_3_8_6) [releaselog/3_8_6.html](releaselog/3_8_6.md)
- https://sqlite.org/src/info/b41031ea2b537237 → [changes.html#version_3_25_1](changes.md#version_3_25_1) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md)
- https://sqlite.org/src/info/b706351ce2ecf59a → [changes.html#version_3_32_3](changes.md#version_3_32_3) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- https://sqlite.org/src/info/b75a9ca6b0499 → [changes.html#version_3_8_5](changes.md#version_3_8_5) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- https://sqlite.org/src/info/b7c8682cc1 → [changes.html#version_3_7_11](changes.md#version_3_7_11) [oldnews.html](oldnews.md) [releaselog/3_7_11.html](releaselog/3_7_11.md)
- https://sqlite.org/src/info/b850dd159918af56 → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/b899b6042f97f5 → [changes.html#version_3_21_0](changes.md#version_3_21_0) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- https://sqlite.org/src/info/b918d4b4e546d → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/b93be8729a895a528e2 → [changes.html#version_3_19_0](changes.md#version_3_19_0) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md)
- https://sqlite.org/src/info/ba7cbfaedc7e6 → [changes.html#version_3_8_7](changes.md#version_3_8_7) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- https://sqlite.org/src/info/ba82a4a41eac1 → [changes.html#version_3_7_17](changes.md#version_3_7_17) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- https://sqlite.org/src/info/bb4bdb9f7f654b0bb9 → [changes.html#version_3_27_0](changes.md#version_3_27_0) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- https://sqlite.org/src/info/bb8a9fd4a9b7fce5 → [changes.html#version_3_35_3](changes.md#version_3_35_3) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- https://sqlite.org/src/info/bc115541132dad136 → [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- https://sqlite.org/src/info/bc8d94f0fbd633fd9a → [changes.html#version_3_27_0](changes.md#version_3_27_0) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- https://sqlite.org/src/info/be436a7f4587ce5 → [changes.html#version_3_21_0](changes.md#version_3_21_0) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- https://sqlite.org/src/info/c2a19d81652f40568c → [changes.html#version_3_9_0](changes.md#version_3_9_0) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- https://sqlite.org/src/info/c2ad16f997ee9c → [changes.html#version_3_7_12_1](changes.md#version_3_7_12_1) [oldnews.html](oldnews.md) [releaselog/3_7_12_1.html](releaselog/3_7_12_1.md)
- https://sqlite.org/src/info/c34d0557f7 → [changes.html#version_3_8_4](changes.md#version_3_8_4) [releaselog/3_8_4.html](releaselog/3_8_4.md) [releaselog/3_8_4_1.html](releaselog/3_8_4_1.md) [releaselog/3_8_4_2.html](releaselog/3_8_4_2.md) [releaselog/3_8_4_3.html](releaselog/3_8_4_3.md)
- https://sqlite.org/src/info/c5ea805691bfc4204b1cb9e → [changes.html#version_3_8_8](changes.md#version_3_8_8) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- https://sqlite.org/src/info/c648539b52ca28c0 → [changes.html#version_3_9_3](changes.md#version_3_9_3) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- https://sqlite.org/src/info/c7facf7ac58d2cda → [wal.html#walresetbug](wal.md#walresetbug)
- https://sqlite.org/src/info/c8d3b9f0a750a529 → [changes.html#version_3_32_3](changes.md#version_3_32_3) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- https://sqlite.org/src/info/c94369cae9b561b1f996d0054b → [changes.html#version_3_25_0](changes.md#version_3_25_0) [releaselog/3_25_0.html](releaselog/3_25_0.md) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md)
- https://sqlite.org/src/info/cad1ab4cb7b0fc → [changes.html#version_3_19_1](changes.md#version_3_19_1) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md)
- https://sqlite.org/src/info/cad1ab4cb7b0fc344 → [news.html](news.md)
- https://sqlite.org/src/info/cb3aa0641d9a4 → [changes.html#version_3_10_1](changes.md#version_3_10_1) [news.html](news.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md)
- https://sqlite.org/src/info/cb91bf4290c211d → [changes.html#version_3_21_0](changes.md#version_3_21_0) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- https://sqlite.org/src/info/ce68383bf6aba → [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- https://sqlite.org/src/info/d06a25c84454a → [changes.html#version_3_11_0](changes.md#version_3_11_0) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md)
- https://sqlite.org/src/info/d0866b26f83e9c55e3 → [changes.html#version_3_27_0](changes.md#version_3_27_0) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- https://sqlite.org/src/info/d2889096e7bdeac6 → [changes.html#version_3_8_6](changes.md#version_3_8_6) [releaselog/3_8_6.html](releaselog/3_8_6.md)
- https://sqlite.org/src/info/d6ec09eccf68cfc → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/d75e67654aa96 → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/d8dc2b3a58cd5dc29 → [changes.html#version_3_24_0](changes.md#version_3_24_0) [releaselog/3_24_0.html](releaselog/3_24_0.md)
- https://sqlite.org/src/info/d96eba87698a428c1d → [changes.html#version_3_27_0](changes.md#version_3_27_0) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- https://sqlite.org/src/info/db87229497 → [changes.html#version_3_8_7_2](changes.md#version_3_8_7_2) [releaselog/3_8_7_2.html](releaselog/3_8_7_2.md)
- https://sqlite.org/src/info/dc3f932f5a147771 → [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_22_0.html](releaselog/3_22_0.md)
- https://sqlite.org/src/info/dc6ebeda9396087 → [changes.html#version_3_13_0](changes.md#version_3_13_0) [releaselog/3_13_0.html](releaselog/3_13_0.md)
- https://sqlite.org/src/info/dc9b1c91 → [changes.html#version_3_12_0](changes.md#version_3_12_0) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md)
- https://sqlite.org/src/info/de3403bf5ae → [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- https://sqlite.org/src/info/de7db14784a08053 → [changes.html#version_3_35_4](changes.md#version_3_35_4) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- https://sqlite.org/src/info/df46dfb631f75694 → [changes.html#version_3_27_2](changes.md#version_3_27_2) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- https://sqlite.org/src/info/e20dd54ab0e4383 → [changes.html#version_3_21_0](changes.md#version_3_21_0) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- https://sqlite.org/src/info/e367f31901ea8700 → [changes.html#version_3_32_3](changes.md#version_3_32_3) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- https://sqlite.org/src/info/e39d032577 → [changes.html#version_3_8_5](changes.md#version_3_8_5) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- https://sqlite.org/src/info/e4a18565a36884b00edf → [changes.html#version_3_8_7_3](changes.md#version_3_8_7_3) [releaselog/3_8_7_3.html](releaselog/3_8_7_3.md)
- https://sqlite.org/src/info/e636a050b7 → [changes.html#version_3_7_17](changes.md#version_3_7_17) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- https://sqlite.org/src/info/e6e962d6b0f06f46e → [changes.html#version_3_17_0](changes.md#version_3_17_0) [compile.html#enable_null_trim](compile.md#enable_null_trim) [releaselog/3_17_0.html](releaselog/3_17_0.md)
- https://sqlite.org/src/info/e6f1f2e34dceeb1ed6 → [changes.html#version_3_27_0](changes.md#version_3_27_0) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- https://sqlite.org/src/info/e8275b415a2f03bee → [changes.html#version_3_25_3](changes.md#version_3_25_3) [releaselog/3_25_3.html](releaselog/3_25_3.md)
- https://sqlite.org/src/info/e8d439c77685eca6 → [changes.html#version_3_14](changes.md#version_3_14) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- https://sqlite.org/src/info/e9654505cfda9 → [changes.html#version_3_8_5](changes.md#version_3_8_5) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- https://sqlite.org/src/info/eb5548a849 → [oldnews.html](oldnews.md)
- https://sqlite.org/src/info/eb703ba7b50c1a5 → [changes.html#version_3_18_0](changes.md#version_3_18_0) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md)
- https://sqlite.org/src/info/ec32177c99ccac2 → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/ec7addc87f97bcff → [whynotgit.html](whynotgit.md)
- https://sqlite.org/src/info/ee51301f316c09e9 → [changes.html#version_3_35_0](changes.md#version_3_35_0) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- https://sqlite.org/src/info/ef360601 → [changes.html#version_3_14_2](changes.md#version_3_14_2) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- https://sqlite.org/src/info/ef9318757b152e3a → [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_22_0.html](releaselog/3_22_0.md)
- https://sqlite.org/src/info/f09fcd17810f65f717 → [changes.html#version_3_27_0](changes.md#version_3_27_0) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- https://sqlite.org/src/info/f2369304e4 → [changes.html#version_3_7_17](changes.md#version_3_7_17) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- https://sqlite.org/src/info/f2ad7de056ab1dc9200 → [changes.html#version_3_8_11](changes.md#version_3_8_11) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- https://sqlite.org/src/info/f45ac567eaa9f9 → [changes.html#version_3_11_0](changes.md#version_3_11_0) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md)
- https://sqlite.org/src/info/f484b65f3d62305 → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/f68bf68513a1c15f → [changes.html#version_3_14](changes.md#version_3_14) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- https://sqlite.org/src/info/f68dc596c4e6018d → [changes.html#version_3_19_0](changes.md#version_3_19_0) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md)
- https://sqlite.org/src/info/f69b96e3076e → [changes.html#version_3_7_17](changes.md#version_3_7_17) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- https://sqlite.org/src/info/f7f8c97e97597 → [changes.html#version_3_13_0](changes.md#version_3_13_0) [releaselog/3_13_0.html](releaselog/3_13_0.md)
- https://sqlite.org/src/info/f97c4637102a3ae72b7911 → [oldnews.html](oldnews.md)
- https://sqlite.org/src/info/fab2c2b07b5d3 → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/fac496b61722daf2 → [changes.html#version_3_23_1](changes.md#version_3_23_1) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- https://sqlite.org/src/info/fc7bd6358f → [changes.html#version_3_7_16](changes.md#version_3_7_16) [oldnews.html](oldnews.md) [releaselog/3_7_16.html](releaselog/3_7_16.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md)
- https://sqlite.org/src/info/fccbde530a → [changes.html#version_3_8_4](changes.md#version_3_8_4) [releaselog/3_8_4.html](releaselog/3_8_4.md) [releaselog/3_8_4_1.html](releaselog/3_8_4_1.md) [releaselog/3_8_4_2.html](releaselog/3_8_4_2.md) [releaselog/3_8_4_3.html](releaselog/3_8_4_3.md)
- https://sqlite.org/src/info/fda22108 → [changes.html#version_3_18_1](changes.md#version_3_18_1) [changes.html#version_3_19_3](changes.md#version_3_19_3) [news.html](news.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md)
- https://sqlite.org/src/info/fef4bb4bd9185ec8f → [changes.html#version_3_15_1](changes.md#version_3_15_1) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md)
- https://sqlite.org/src/info/ff5be73dee → [changes.html#version_3_7_10](changes.md#version_3_7_10) [oldnews.html](oldnews.md) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- https://sqlite.org/src/repo-tabsize → [dbstat.html](dbstat.md)
- https://sqlite.org/src/timeline → [getthecode.html](getthecode.md) [np1queryprob.html](np1queryprob.md) [whynotgit.html](whynotgit.md)
- https://sqlite.org/src/timeline?c=2000-05-29+14:26:00 → [about.html](about.md)
- https://sqlite.org/src/timeline?c=2013-08-26 → [getthecode.html](getthecode.md)
- https://sqlite.org/src/timeline?c=2018-03-16&n=10 → [whynotgit.html](whynotgit.md)
- https://sqlite.org/src/timeline?c=f9372072a6 → [printf.html#comma](printf.md#comma)
- https://sqlite.org/src/timeline?from=version-3.41.0&to=version-3.41.1 → [changes.html#version_3_41_1](changes.md#version_3_41_1) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- https://sqlite.org/src/timeline?from=version-3.45.1&to=version-3.45.2&to2=branch-3.45 → [changes.html#version_3_45_2](changes.md#version_3_45_2) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- https://sqlite.org/src/timeline?from=version-3.45.2&to=version-3.45.3&to2=branch-3.45 → [changes.html#version_3_45_3](changes.md#version_3_45_3) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- https://sqlite.org/src/timeline?from=version-3.53.0&to=version-3.53.1&y=ci → [changes.html#version_3_53_1](changes.md#version_3_53_1) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_3.html](releaselog/3_53_3.md)
- https://sqlite.org/src/timeline?from=version-3.53.0&to=version-3.53.2&to2=branch-3.53&y=ci → [changes.html#version_3_53_2](changes.md#version_3_53_2) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md)
- https://sqlite.org/src/timeline?from=version-3.53.0&to=version-3.53.3&to2=branch-3.53&y=ci → [changes.html#version_3_53_3](changes.md#version_3_53_3) [releaselog/3_53_3.html](releaselog/3_53_3.md)
- https://sqlite.org/src/timeline?from=version-3.53.0&to=version-3.53.4&to2=branch-3.53&y=ci → [changes.html#version_3_53_4](changes.md#version_3_53_4) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- https://sqlite.org/src/timeline?p=version-3.32.3&bt=version-3.32.0 → [news.html](news.md)
- https://sqlite.org/src/timeline?p=version-3.38.1&bt=version-3.38.0 → [changes.html#version_3_38_1](changes.md#version_3_38_1) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md)
- https://sqlite.org/src/timeline?p=version-3.39.3&bt=version-3.39.2 → [changes.html#version_3_39_3](changes.md#version_3_39_3) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- https://sqlite.org/src/timeline?r=branch-3.25 → [news.html](news.md)
- https://sqlite.org/src/timeline?r=branch-3.40 → [news.html](news.md)
- https://sqlite.org/src/timeline?r=prefer-coroutine-sort-subquery → [whynotgit.html](whynotgit.md)
- https://sqlite.org/src/timeline?y=ci&c=0a2eb949f8a759e5 → [testing.html#ossfuzz](testing.md#ossfuzz)
- https://sqlite.org/src/timeline?y=ci&c=62f2235adf796c72 → [testing.html#ossfuzz](testing.md#ossfuzz)
- https://sqlite.org/src/timeline?y=ci&c=c422afb507dc8757 → [testing.html#ossfuzz](testing.md#ossfuzz)
- https://sqlite.org/src/timeline?y=t&u=mrigger&n=all → [testing.html#3pfuzz](testing.md#3pfuzz)
- https://sqlite.org/src/tktview/4baa46491212947 → [changes.html#version_3_15_0](changes.md#version_3_15_0) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md)
- https://sqlite.org/src/tktview?name=38a97a87a6 → [changes.html#version_3_10_0](changes.md#version_3_10_0) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md)
- https://sqlite.org/src/tktview?name=5d863f876e → [oldnews.html](oldnews.md)
- https://sqlite.org/src/tktview?name=8a2adec166 → [oldnews.html](oldnews.md)
- https://sqlite.org/src/tktview?name=ac661962a2 → [oldnews.html](oldnews.md)
- https://sqlite.org/src/tktview?name=f97c4637102a3ae72b79 → [changes.html#version_3_8_8_1](changes.md#version_3_8_8_1) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- https://sqlite.org/src/tree?ci=trunk → [vtab.html#tabfunc2](vtab.md#tabfunc2)
- https://sqlite.org/src/vdiff?from=e4ab094f8afce0817f4074e823fabe59fc29ebb4&to=83afe23e553e802c0947c80d0ffdd120423e7c52&sbs=1 → [oldnews.html](oldnews.md)
- https://sqlite.org/src/vpatch?from=version-3.9.0&to=version-3.9.1 → [oldnews.html](oldnews.md)
- https://sqlite.org/th3 → [qmplan.html](qmplan.md)
- https://sqlite.org/wasm → [changes.html#version_3_40_0](changes.md#version_3_40_0) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md)
- https://sqlite.org/wasm/doc/trunk/index.md → [news.html](news.md)
- https://stackoverflow.com/questions/27960605/find-all-the-direct-descendants-of-a-given-commit#27962018 → [whynotgit.html](whynotgit.md)
- https://support.google.com/mail/answer/6590 → [sqlar.html#dbasobj](sqlar.md#dbasobj)
- https://tools.ietf.org/html/rfc7396 → [json1.html#jpatch](json1.md#jpatch)
- https://tools.ietf.org/html/rfc7946 → [geopoly.html](geopoly.md) [geopoly.html#ccw](geopoly.md#ccw)
- https://tools.ietf.org/html/rfc8259#section-9 → [json1.html#varg](json1.md#varg)
- https://ttlc.intuit.com/post/show_full/cJf8mIhC4r4jjracfArQzM/when-i-try-to-update-turbotax-i-receive-an-unexpected-error-message → [famous.html](famous.md)
- https://www.airbus.com/en/products-services/commercial-aircraft/passenger-aircraft/a350-family → [famous.html](famous.md)
- https://www.bentley.com/en/products/product-line/modeling-and-visualization-software/microstation → [famous.html](famous.md)
- https://www.expensify.com/ → [famous.html](famous.md)
- https://www.facebook.com/ → [famous.html](famous.md)
- https://www.fossil-scm.org/ → [bindptr.html](bindptr.md) [dbstat.html](dbstat.md) [download.html#srctree](download.md#srctree) [getthecode.html](getthecode.md) [news.html](news.md) [np1queryprob.html](np1queryprob.md) [printf.html#comma](printf.md#comma) [rowvalue.html#rvinop](rowvalue.md#rvinop) [sessionintro.html](sessionintro.md) [whentouse.html#container](whentouse.md#container)
- https://www.fossil-scm.org/download.html → [getthecode.html#clone](getthecode.md#clone)
- https://www.fossil-scm.org/fossil/artifact/e5d6a82d?ln=1594-1605 → [rowvalue.html#rvinop](rowvalue.md#rvinop)
- https://www.fossil-scm.org/fossil/artifact/e5d6a82d?ln=1618-1628 → [rowvalue.html#rvinop](rowvalue.md#rvinop)
- https://www.fossil-scm.org/fossil/artifact/e5d6a82d?ln=1641-1650 → [rowvalue.html#rvinop](rowvalue.md#rvinop)
- https://www.fossil-scm.org/fossil/doc/trunk/www/quotes.wiki → [whynotgit.html](whynotgit.md)
- https://www.gnu.org/software/autoconf/ → [changes.html#version_3_48_0](changes.md#version_3_48_0) [releaselog/3_48_0.html](releaselog/3_48_0.md)
- https://www.gnu.org/software/gdbm/gdbm.html → [versionnumbers.html](versionnumbers.md)
- https://www.hwaci.com/ → [consortium.html](consortium.md)
- https://www.hwaci.com/sw/sqlite/cerod.html → [support.html#prosupport](support.md#prosupport)
- https://www.hwaci.com/sw/sqlite/see → [support.html#prosupport](support.md#prosupport)
- https://www.hwaci.com/sw/sqlite/zipvfs.html → [memstat.html](memstat.md) [support.html#prosupport](support.md#prosupport)
- https://www.ietf.org/rfc/rfc4180.txt → [changes.html#version_3_14](changes.md#version_3_14) [csv.html](csv.md) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [vtablist.html](vtablist.md)
- https://www.llvm.org/docs/LibFuzzer.html → [qmplan.html](qmplan.md)
- https://www.loc.gov → [lts.html](lts.md)
- https://www.loc.gov/ → [locrsf.html](locrsf.md)
- https://www.loc.gov/preservation/digital/formats/fdd/fdd000461.shtml#local → [locrsf.html](locrsf.md)
- https://www.loc.gov/preservation/resources/rfs/ → [locrsf.html](locrsf.md)
- https://www.loc.gov/preservation/resources/rfs/data.html → [locrsf.html](locrsf.md)
- https://www.microsoft.com/en-us/research/people/gray/ → [fasterthanfs.html](fasterthanfs.md)
- https://www.microsoft.com/en-us/research/publication/to-blob-or-not-to-blob-large-object-storage-in-a-database-or-a-filesystem/ → [fasterthanfs.html](fasterthanfs.md)
- https://www.neooffice.org/neojava/en/index.php → [affcase1.html](affcase1.md)
- https://www.postgresql.org → [lang_returning.html](lang_returning.md)
- https://www.reddit.com/r/programming/comments/84fzoc/why_is_sqlite_coded_in_c/ → [whyc.html](whyc.md)
- https://www.reddit.com/r/programming/comments/9ezy8c/serious_bug_causing_infinite_loop_in_some_queries/ → [news.html](news.md)
- https://www.rfc-editor.org/rfc/rfc8259.txt → [json1.html#howtocompile](json1.md#howtocompile)
- https://www.tcl-lang.org/doc/tea/TEAOverview.html → [changes.html#version_3_49_0](changes.md#version_3_49_0) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md)
- https://www.tcl.tk/man/tcl8.3/UserCmd/tclsh.htm → [cli.html#compiling](cli.md#compiling)
- https://www.theregister.com/2024/10/02/tcltk_version_9/ → [news.html](news.md)
- https://www2.eecs.berkeley.edu/Pubs/TechRpts/2006/EECS-2006-1.html → [faq.html#q6](faq.md#q6)
- https://www2.sqlite.org → [qmplan.html](qmplan.md)
- https://www2.sqlite.org/docsrc → [getthecode.html](getthecode.md) [qmplan.html](qmplan.md)
- https://www2.sqlite.org/forum → [qmplan.html](qmplan.md)
- https://www2.sqlite.org/src → [getthecode.html](getthecode.md) [qmplan.html](qmplan.md)
- https://www3.sqlite.org → [qmplan.html](qmplan.md)
- https://www3.sqlite.org/cgi/dbsqlfuzz → [qmplan.html](qmplan.md)
- https://www3.sqlite.org/cgi/docsrc → [qmplan.html](qmplan.md)
- https://www3.sqlite.org/cgi/forum → [qmplan.html](qmplan.md)
- https://www3.sqlite.org/cgi/src → [qmplan.html](qmplan.md)
- https://www3.sqlite.org/cgi/th3 → [qmplan.html](qmplan.md)
- https://www3.sqlite.org/docsrc → [getthecode.html](getthecode.md)
- https://www3.sqlite.org/src → [getthecode.html](getthecode.md)
- https://xkcd.com/1597/ → [whynotgit.html](whynotgit.md)
- https://zlib.net → [cli.html#compiling](cli.md#compiling) [compile.html#have_zlib](compile.md#have_zlib) [zipfile.html](zipfile.md)
- https://zlib.net/ → [qmplan.html](qmplan.md) [sqlar.html#cltools](sqlar.md#cltools) [sqlar.html#dbasobj](sqlar.md#dbasobj)
- IEEE 754 floating point values are approximations → [lang_aggfunc.html#sumunc](lang_aggfunc.md#sumunc)
- ieee754 extension → [changes.html#version_3_33_0](changes.md#version_3_33_0) [releaselog/3_33_0.html](releaselog/3_33_0.md)
- if → [changes.html#version_3_48_0](changes.md#version_3_48_0) [releaselog/3_48_0.html](releaselog/3_48_0.md)
- ifnull → [changes.html#version_3_6_21](changes.md#version_3_6_21) [lang_corefunc.html](lang_corefunc.md) [releaselog/3_6_21.html](releaselog/3_6_21.md)
- iif → [changes.html#version_3_48_0](changes.md#version_3_48_0) [lang_corefunc.html](lang_corefunc.md) [lang_expr.html#case](lang_expr.md#case) [releaselog/3_48_0.html](releaselog/3_48_0.md)
- iif SQL function → [changes.html#version_3_32_0](changes.md#version_3_32_0) [changes.html#version_3_48_0](changes.md#version_3_48_0) [changes.html#version_3_49_0](changes.md#version_3_49_0) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md) [releaselog/3_48_0.html](releaselog/3_48_0.md) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md)
- immutable query parameter → [wal.html#advantages](wal.md#advantages) [wal.html#readonly](wal.md#readonly) [walformat.html#locks](walformat.md#locks)
- imposter tables → [changes.html#version_3_51_0](changes.md#version_3_51_0) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- IN operator → [c3ref/vtab_in.html](c3ref/vtab_in.md) [capi3ref.html#sqlite3_vtab_in](capi3ref.md#sqlite3_vtab_in) [changes.html#version_3_12_2](changes.md#version_3_12_2) [changes.html#version_3_13_0](changes.md#version_3_13_0) [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_15_0](changes.md#version_3_15_0) [changes.html#version_3_38_0](changes.md#version_3_38_0) [changes.html#version_3_47_0](changes.md#version_3_47_0) [changes.html#version_3_8_6](changes.md#version_3_8_6) [oldnews.html](oldnews.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md) [releaselog/3_8_6.html](releaselog/3_8_6.md) [rowvalue.html#rvinop](rowvalue.md#rvinop)
- in-memory database → [c3ref/open.html#coreuriqueryparameters](c3ref/open.md#coreuriqueryparameters) [capi3ref.html#coreuriqueryparameters](capi3ref.md#coreuriqueryparameters) [changes.html#version_3_7_13](changes.md#version_3_7_13) [cli.html#zipdb](cli.md#zipdb) [compile.html#omit_memorydb](compile.md#omit_memorydb) [lang_attach.html](lang_attach.md) [pragma.html#pragma_journal_mode](pragma.md#pragma_journal_mode) [releaselog/3_7_13.html](releaselog/3_7_13.md)
- in-memory databases → [pragma.html#pragma_locking_mode](pragma.md#pragma_locking_mode) [pragma.html#pragma_temp_store](pragma.md#pragma_temp_store) [sharedcache.html#inmemsharedcache](sharedcache.md#inmemsharedcache)
- in-memory shared-cache → [changes.html#version_3_7_13](changes.md#version_3_7_13) [releaselog/3_7_13.html](releaselog/3_7_13.md)
- increase in the default page size → [news.html](news.md)
- incremental_vacuum → [changes.html#version_3_6_12](changes.md#version_3_6_12) [changes.html#version_3_7_2](changes.md#version_3_7_2) [fileformat2.html#ovflpgs](fileformat2.md#ovflpgs) [fileformat2.html#schemaformat](fileformat2.md#schemaformat) [howtocorrupt.html#cfgerr](howtocorrupt.md#cfgerr) [oldnews.html](oldnews.md) [pragma.html#pragma_auto_vacuum](pragma.md#pragma_auto_vacuum) [releaselog/3_6_12.html](releaselog/3_6_12.md) [releaselog/3_7_2.html](releaselog/3_7_2.md)
- index b-tree → [opcode.html#codes](opcode.md#codes)
- index_info → [changes.html#version_3_30_0](changes.md#version_3_30_0) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md)
- index_info pragma → [pragma.html#pragfunc](pragma.md#pragfunc) [pragma.html#pragma_index_xinfo](pragma.md#pragma_index_xinfo)
- index_xinfo → [changes.html#version_3_30_0](changes.md#version_3_30_0) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md)
- index_xinfo pragma → [pragma.html#pragma_index_info](pragma.md#pragma_index_info)
- INDEXED BY → [changes.html#version_3_33_0](changes.md#version_3_33_0) [changes.html#version_3_6_4](changes.md#version_3_6_4) [fullsql.html](fullsql.md) [lang.html](lang.md) [queryplanner-ng.html#howtofix](queryplanner-ng.md#howtofix) [releaselog/3_33_0.html](releaselog/3_33_0.md) [releaselog/3_6_4.html](releaselog/3_6_4.md)
- indexed expressions → [changes.html#version_3_41_0](changes.md#version_3_41_0) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- indexed-column → [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtable.html#primkeyconst](lang_createtable.md#primkeyconst) [lang_createtable.html#uniqueconst](lang_createtable.md#uniqueconst) [lang_createtrigger.html](lang_createtrigger.md) [lang_insert.html](lang_insert.md) [lang_upsert.html](lang_upsert.md) [partialindex.html](partialindex.md)
- Indexes → [stricttables.html](stricttables.md)
- Indexes On Expressions → [fullsql.html](fullsql.md) [lang_createindex.html#indexexpr](lang_createindex.md#indexexpr)
- indexes on expressions → [changes.html#version_3_15_0](changes.md#version_3_15_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_22_0](changes.md#version_3_22_0) [changes.html#version_3_23_0](changes.md#version_3_23_0) [changes.html#version_3_26_0](changes.md#version_3_26_0) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_30_0](changes.md#version_3_30_0) [changes.html#version_3_9_0](changes.md#version_3_9_0) [features.html](features.md) [lang_reindex.html](lang_reindex.md) [news.html](news.md) [oldnews.html](oldnews.md) [optoverview.html#where_clause](optoverview.md#where_clause) [rbu.html#rbu_updates](rbu.md#rbu_updates) [rbu.html#rbu_vacuum](rbu.md#rbu_vacuum) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_22_0.html](releaselog/3_22_0.md) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_26_0.html](releaselog/3_26_0.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md) [versionnumbers.html](versionnumbers.md)
- indexing → [eqp.html](eqp.md) [queryplanner-ng.html](queryplanner-ng.md)
- indexing tutorial → [imposter.html](imposter.md) [optoverview.html](optoverview.md)
- INSERT → [autoinc.html](autoinc.md) [c3ref/last_insert_rowid.html](c3ref/last_insert_rowid.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/reset.html](c3ref/reset.md) [c3ref/total_changes.html](c3ref/total_changes.md) [capi3ref.html#sqlite3_last_insert_rowid](capi3ref.md#sqlite3_last_insert_rowid) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite) [capi3ref.html#sqlite3_reset](capi3ref.md#sqlite3_reset) [capi3ref.html#sqlite3_total_changes](capi3ref.md#sqlite3_total_changes) [changes.html#version_3_35_0](changes.md#version_3_35_0) [changes.html#version_3_47_0](changes.md#version_3_47_0) [changes.html#version_3_7_11](changes.md#version_3_7_11) [changes.html#version_3_8_10_2](changes.md#version_3_8_10_2) [compile.html#omit_compound_select](compile.md#omit_compound_select) [conflict.html](conflict.md) [dbpage.html](dbpage.md) [faq.html#q1](faq.md#q1) [faq.html#q19](faq.md#q19) [fts3.html#fts4](fts3.md#fts4) [fts5.html](fts5.md) [fullsql.html](fullsql.md) [isolation.html](isolation.md) [lang.html](lang.md) [lang_analyze.html#statanal](lang_analyze.md#statanal) [lang_conflict.html](lang_conflict.md) [lang_createtable.html#dfltval](lang_createtable.md#dfltval) [lang_createtable.html#notnullconst](lang_createtable.md#notnullconst) [lang_createtable.html#primkeyconst](lang_createtable.md#primkeyconst) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_replace.html](lang_replace.md) [lang_returning.html](lang_returning.md) [lang_upsert.html](lang_upsert.md) [lang_upsert.html#parseambig](lang_upsert.md#parseambig) [lang_with.html](lang_with.md) [pragma.html](pragma.md) [pragma.html#pragma_count_changes](pragma.md#pragma_count_changes) [pragma.html#pragma_writable_schema](pragma.md#pragma_writable_schema) [rbu.html](rbu.md) [rbu.html#rbu_updates](rbu.md#rbu_updates) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md) [releaselog/3_7_11.html](releaselog/3_7_11.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md) [rtree.html](rtree.md) [vtab.html](vtab.md) [vtab.html#hiddencol](vtab.md#hiddencol)
- insert-stmt → [lang_createtrigger.html](lang_createtrigger.md) [lang_insert.html](lang_insert.md)
- INSTEAD OF trigger → [c3ref/changes.html](c3ref/changes.md) [capi3ref.html#sqlite3_changes](capi3ref.md#sqlite3_changes) [lang_createview.html](lang_createview.md) [pragma.html#pragma_count_changes](pragma.md#pragma_count_changes)
- instr → [changes.html#version_3_15_2](changes.md#version_3_15_2) [changes.html#version_3_7_15](changes.md#version_3_7_15) [lang_corefunc.html](lang_corefunc.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_7_15.html](releaselog/3_7_15.md)
- INTEGER PRIMARY KEY → [autoinc.html](autoinc.md) [c3ref/last_insert_rowid.html](c3ref/last_insert_rowid.md) [c3ref/table_column_metadata.html](c3ref/table_column_metadata.md) [capi3ref.html#sqlite3_last_insert_rowid](capi3ref.md#sqlite3_last_insert_rowid) [capi3ref.html#sqlite3_table_column_metadata](capi3ref.md#sqlite3_table_column_metadata) [changes.html#version_3_12_2](changes.md#version_3_12_2) [changes.html#version_3_13_0](changes.md#version_3_13_0) [changes.html#version_3_23_0](changes.md#version_3_23_0) [compile.html#omit_autoincrement](compile.md#omit_autoincrement) [datatype3.html#storageclasses](datatype3.md#storageclasses) [faq.html#q1](faq.md#q1) [faq.html#q3](faq.md#q3) [fileformat2.html##sqltab](fileformat2.md##sqltab) [fileformat2.html#ffschema](fileformat2.md#ffschema) [fileformat2.html#intschema](fileformat2.md#intschema) [fileformat2.html#seqtab](fileformat2.md#seqtab) [fts3.html#simple_fts_queries](fts3.md#simple_fts_queries) [gencol.html#vgc\*](gencol.md#vgc*) [lang_createtable.html#primkeyconst](lang_createtable.md#primkeyconst) [lang_createtable.html#uniqueconst](lang_createtable.md#uniqueconst) [lang_vacuum.html#howvacuumworks](lang_vacuum.md#howvacuumworks) [queryplanner.html#searching](queryplanner.md#searching) [quirks.html](quirks.md) [quirks.html#dblquote](quirks.md#dblquote) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [rowidtable.html](rowidtable.md) [schematab.html](schematab.md) [stricttables.html](stricttables.md) [withoutrowid.html](withoutrowid.md) [withoutrowid.html#bene](withoutrowid.md#bene)
- integrity_check → [pragma.html#pragma_quick_check](pragma.md#pragma_quick_check) [testing.html#crashtesting](testing.md#crashtesting)
- integrity_check pragma → [changes.html#version_3_6_23](changes.md#version_3_6_23) [compile.html#omit_integrity_check](compile.md#omit_integrity_check) [howtocorrupt.html#cfgerr](howtocorrupt.md#cfgerr) [releaselog/3_6_23.html](releaselog/3_6_23.md)
- internal indexes → [fileformat2.html#ffschema](fileformat2.md#ffschema) [optoverview.html#autoindex](optoverview.md#autoindex) [schematab.html](schematab.md)
- internal schema objects → [fileformat2.html#ffschema](fileformat2.md#ffschema)
- internal table → [autoinc.html](autoinc.md)
- internal tables → [lang_analyze.html](lang_analyze.md) [lang_analyze.html#statanal](lang_analyze.md#statanal)
- Internal Versus External BLOBs → [aff_short.html](aff_short.md) [appfileformat.html](appfileformat.md) [fasterthanfs.html](fasterthanfs.md) [whyc.html](whyc.md)
- invalid UTF → [c3ref/errcode.html](c3ref/errcode.md) [capi3ref.html#sqlite3_errcode](capi3ref.md#sqlite3_errcode)
- IS DISTINCT FROM → [changes.html#version_3_39_0](changes.md#version_3_39_0) [lang_select.html#distinct](lang_select.md#distinct) [releaselog/3_39_0.html](releaselog/3_39_0.md) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- IS NOT DISTINCT FROM → [changes.html#version_3_39_0](changes.md#version_3_39_0) [releaselog/3_39_0.html](releaselog/3_39_0.md) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- IS operator → [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_8_11](changes.md#version_3_8_11) [fullsql.html](fullsql.md) [oldnews.html](oldnews.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [windowfunctions.html#grouptype](windowfunctions.md#grouptype)
- jfuzz → [changes.html#version_3_45_1](changes.md#version_3_45_1) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- join order → [eqp.html](eqp.md) [optoverview.html](optoverview.md)
- join-clause → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- join-constraint → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#fromclause](lang_select.md#fromclause) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- join-operator → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#fromclause](lang_select.md#fromclause) [lang_select.html#nonstd](lang_select.md#nonstd) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- journal_mode → [changes.html#version_3_12_0](changes.md#version_3_12_0) [changes.html#version_3_5_9](changes.md#version_3_5_9) [lang_attach.html](lang_attach.md) [oldnews.html](oldnews.md) [pragma.html#pragma_synchronous](pragma.md#pragma_synchronous) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_5_9.html](releaselog/3_5_9.md) [tempfiles.html#tempdb](tempfiles.md#tempdb) [wal.html#fast](wal.md#fast) [wal.html#readonly](wal.md#readonly)
- journal_mode pragma → [atomiccommit.html#keepcache](atomiccommit.md#keepcache) [changes.html#version_3_6_5](changes.md#version_3_6_5) [compile.html#default_journal_size_limit](compile.md#default_journal_size_limit) [fileformat2.html#rollbackjournal](fileformat2.md#rollbackjournal) [isolation.html](isolation.md) [pragma.html#pragma_wal_autocheckpoint](pragma.md#pragma_wal_autocheckpoint) [pragma.html#pragma_wal_checkpoint](pragma.md#pragma_wal_checkpoint) [releaselog/3_6_5.html](releaselog/3_6_5.md) [tempfiles.html#rollbackjrnl](tempfiles.md#rollbackjrnl)
- journal_size_limit pragma → [compile.html#default_journal_size_limit](compile.md#default_journal_size_limit) [wal.html#bigwal](wal.md#bigwal)
- json → [changes.html#version_3_10_0](changes.md#version_3_10_0) [json1.html#jarray](json1.md#jarray) [json1.html#jobj](json1.md#jobj) [json1.html#jpretty](json1.md#jpretty) [json1.html#jset](json1.md#jset) [json1.html#json5](json1.md#json5) [json1.html#varg](json1.md#varg) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md)
- JSON BLOB input bug → [changes.html#version_3_45_1](changes.md#version_3_45_1) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- JSON function path arguments → [changes.html#version_3_31_0](changes.md#version_3_31_0) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- JSON SQL functions → [changes.html#version_3_42_0](changes.md#version_3_42_0) [changes.html#version_3_45_0](changes.md#version_3_45_0) [compile.html#enable_json1](compile.md#enable_json1) [compile.html#json_max_depth](compile.md#json_max_depth) [compile.html#omit_json](compile.md#omit_json) [lang_aggfunc.html](lang_aggfunc.md) [news.html](news.md) [releaselog/3_42_0.html](releaselog/3_42_0.md) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md) [testing.html#dbsqlfuzz](testing.md#dbsqlfuzz) [testing.html#slt](testing.md#slt)
- json1 → [amalgamation.html](amalgamation.md) [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_15_2](changes.md#version_3_15_2) [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_43_0](changes.md#version_3_43_0) [features.html](features.md) [fullsql.html](fullsql.md) [lang.html](lang.md) [lang_corefunc.html](lang_corefunc.md) [lang_expr.html#\*funcinexpr](lang_expr.md#*funcinexpr) [news.html](news.md) [oldnews.html](oldnews.md) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md)
- JSON5 → [json1.html#jvalid](json1.md#jvalid) [news.html](news.md)
- JSON5 extensions → [changes.html#version_3_42_0](changes.md#version_3_42_0) [releaselog/3_42_0.html](releaselog/3_42_0.md)
- json_array → [json1.html#jarrayb](json1.md#jarrayb) [json1.html#jobj](json1.md#jobj) [json1.html#jset](json1.md#jset) [json1.html#varg](json1.md#varg)
- json_array_insert → [changes.html#version_3_53_0](changes.md#version_3_53_0) [json1.html#jset](json1.md#jset) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- json_array_length → [changes.html#version_3_43_1](changes.md#version_3_43_1) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md)
- json_each → [changes.html#version_3_24_0](changes.md#version_3_24_0) [changes.html#version_3_41_0](changes.md#version_3_41_0) [flextypegood.html](flextypegood.md) [releaselog/3_24_0.html](releaselog/3_24_0.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md) [vtab.html#customvtab](vtab.md#customvtab) [vtablist.html](vtablist.md)
- json_error_position → [json1.html#howtocompile](json1.md#howtocompile)
- json_extract → [changes.html#version_3_19_0](changes.md#version_3_19_0) [json1.html#jexb](json1.md#jexb) [json1.html#jptr](json1.md#jptr) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md)
- json_group_array → [changes.html#version_3_10_0](changes.md#version_3_10_0) [changes.html#version_3_44_0](changes.md#version_3_44_0) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md)
- json_group_object → [changes.html#version_3_10_0](changes.md#version_3_10_0) [changes.html#version_3_50_0](changes.md#version_3_50_0) [lang_aggfunc.html#aggorderby](lang_aggfunc.md#aggorderby) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- json_insert → [json1.html#jsetb](json1.md#jsetb)
- json_object → [json1.html#jarray](json1.md#jarray) [json1.html#jobjb](json1.md#jobjb) [json1.html#jset](json1.md#jset)
- json_patch → [changes.html#version_3_18_0](changes.md#version_3_18_0) [json1.html#jpatchb](json1.md#jpatchb) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md)
- json_pretty → [changes.html#version_3_46_0](changes.md#version_3_46_0) [news.html](news.md) [releaselog/3_46_0.html](releaselog/3_46_0.md) [releaselog/3_46_1.html](releaselog/3_46_1.md)
- json_quote → [changes.html#version_3_14](changes.md#version_3_14) [json1.html#howtocompile](json1.md#howtocompile) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- json_remove → [changes.html#version_3_43_1](changes.md#version_3_43_1) [json1.html#jpatch](json1.md#jpatch) [json1.html#jrmb](json1.md#jrmb) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md)
- json_replace → [json1.html#jarrayins](json1.md#jarrayins) [json1.html#jsetb](json1.md#jsetb)
- json_set → [json1.html#jpatch](json1.md#jpatch) [json1.html#jquirk](json1.md#jquirk) [json1.html#jsetb](json1.md#jsetb)
- json_tree → [changes.html#version_3_41_0](changes.md#version_3_41_0) [flextypegood.html](flextypegood.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md) [vtab.html#customvtab](vtab.md#customvtab) [vtablist.html](vtablist.md)
- json_valid → [changes.html#version_3_45_0](changes.md#version_3_45_0) [json1.html#howtocompile](json1.md#howtocompile) [json1.html#json5](json1.md#json5) [json1.html#jsonbx](json1.md#jsonbx) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- JSONB → [changes.html#version_3_45_0](changes.md#version_3_45_0) [changes.html#version_3_45_1](changes.md#version_3_45_1) [changes.html#version_3_50_0](changes.md#version_3_50_0) [changes.html#version_3_51_0](changes.md#version_3_51_0) [climode.html#opt-textjsonb](climode.md#opt-textjsonb) [json1.html#jbtree](json1.md#jbtree) [json1.html#jgroupobjectb](json1.md#jgroupobjectb) [json1.html#jvalid](json1.md#jvalid) [news.html](news.md) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md) [testing.html#dbsqlfuzz](testing.md#dbsqlfuzz) [testing.html#slt](testing.md#slt)
- jsonb_array_insert → [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- jsonb_each → [changes.html#version_3_51_0](changes.md#version_3_51_0) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- jsonb_extract → [json1.html#jptr](json1.md#jptr)
- jsonb_replace → [changes.html#version_3_50_0](changes.md#version_3_50_0) [json1.html#jarrayins](json1.md#jarrayins) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- jsonb_set → [changes.html#version_3_50_0](changes.md#version_3_50_0) [changes.html#version_3_50_1](changes.md#version_3_50_1) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- jsonb_tree → [changes.html#version_3_51_0](changes.md#version_3_51_0) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- julianday modifier → [changes.html#version_3_38_0](changes.md#version_3_38_0) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md)
- keyword index → [doclist.html](doclist.md) [sitemap.html](sitemap.md)
- langexpr → [lang_vacuum.html#vacuuminto](lang_vacuum.md#vacuuminto)
- languageid → [fts3.html#f4alid](fts3.md#f4alid)
- last_insert_rowid → [deterministic.html](deterministic.md) [lang_corefunc.html](lang_corefunc.md) [withoutrowid.html](withoutrowid.md)
- last_insert_rowid SQL function → [c3ref/last_insert_rowid.html](c3ref/last_insert_rowid.md) [capi3ref.html#sqlite3_last_insert_rowid](capi3ref.md#sqlite3_last_insert_rowid)
- LEFT JOIN strength reduction optimization → [changes.html#version_3_23_0](changes.md#version_3_23_0) [changes.html#version_3_23_1](changes.md#version_3_23_1) [changes.html#version_3_27_0](changes.md#version_3_27_0) [news.html](news.md) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- legacy_file_format → [changes.html#version_3_14](changes.md#version_3_14) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- legacy_file_format pragma → [changes.html#version_3_31_0](changes.md#version_3_31_0) [lang_createindex.html#descidx](lang_createindex.md#descidx) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- Lemon → [amalg-v-canon.html#canon](amalg-v-canon.md#canon) [changes.html#version_2_8_7](changes.md#version_2_8_7) [changes.html#version_3_8_3](changes.md#version_3_8_3) [releaselog/3_8_3.html](releaselog/3_8_3.md)
- Lemon LALR parser generator → [changes.html#version_3_6_23](changes.md#version_3_6_23) [releaselog/3_6_23.html](releaselog/3_6_23.md)
- Lemon parser generator → [amalgamation.html](amalgamation.md) [arch.html](arch.md) [changes.html#version_1_0_28](changes.md#version_1_0_28) [changes.html#version_2_4_0](changes.md#version_2_4_0) [changes.html#version_3_12_0](changes.md#version_3_12_0) [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_17_0](changes.md#version_3_17_0) [changes.html#version_3_22_0](changes.md#version_3_22_0) [changes.html#version_3_8_3](changes.md#version_3_8_3) [compile.html#enable_update_delete_limit](compile.md#enable_update_delete_limit) [compile.html#omitfeatures](compile.md#omitfeatures) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_17_0.html](releaselog/3_17_0.md) [releaselog/3_22_0.html](releaselog/3_22_0.md) [releaselog/3_8_3.html](releaselog/3_8_3.md)
- length → [changes.html#version_3_7_12](changes.md#version_3_7_12) [lang_corefunc.html](lang_corefunc.md) [lang_corefunc.html#octet_length](lang_corefunc.md#octet_length) [releaselog/3_7_12.html](releaselog/3_7_12.md)
- length SQL function → [nulinstr.html](nulinstr.md)
- library size → [about.html](about.md)
- LIKE → [c3ref/c_limit_attached.html#sqlitelimitlikepatternlength](c3ref/c_limit_attached.md#sqlitelimitlikepatternlength) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/strlike.html](c3ref/strlike.md) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_strlike](capi3ref.md#sqlite3_strlike) [capi3ref.html#sqlitelimitlikepatternlength](capi3ref.md#sqlitelimitlikepatternlength) [changes.html#version_3_10_0](changes.md#version_3_10_0) [changes.html#version_3_10_2](changes.md#version_3_10_2) [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_16_0](changes.md#version_3_16_0) [changes.html#version_3_32_0](changes.md#version_3_32_0) [changes.html#version_3_35_0](changes.md#version_3_35_0) [cli.html#sha3sum](cli.md#sha3sum) [compile.html#case_sensitive_like](compile.md#case_sensitive_like) [compile.html#like_doesnt_match_blobs](compile.md#like_doesnt_match_blobs) [compile.html#omit_like_optimization](compile.md#omit_like_optimization) [compile.html#rcmd](compile.md#rcmd) [invalidutf.html](invalidutf.md) [lang_corefunc.html#like](lang_corefunc.md#like) [limits.html#max_like_pattern_length](limits.md#max_like_pattern_length) [oldnews.html](oldnews.md) [optoverview.html#like_opt](optoverview.md#like_opt) [pragma.html#pragma_case_sensitive_like](pragma.md#pragma_case_sensitive_like) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [vtab.html#xfindfunction](vtab.md#xfindfunction)
- like → [faq.html#q18](faq.md#q18) [lang_corefunc.html](lang_corefunc.md) [lang_expr.html#like](lang_expr.md#like) [optoverview.html#like_opt](optoverview.md#like_opt)
- LIKE optimization → [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_21_0](changes.md#version_3_21_0) [changes.html#version_3_23_0](changes.md#version_3_23_0) [changes.html#version_3_28_0](changes.md#version_3_28_0) [changes.html#version_3_29_0](changes.md#version_3_29_0) [changes.html#version_3_7_1](changes.md#version_3_7_1) [compile.html#rcmd](compile.md#rcmd) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_28_0.html](releaselog/3_28_0.md) [releaselog/3_29_0.html](releaselog/3_29_0.md) [releaselog/3_7_1.html](releaselog/3_7_1.md)
- likelihood → [changes.html#version_3_8_1](changes.md#version_3_8_1) [changes.html#version_3_8_8](changes.md#version_3_8_8) [lang_corefunc.html](lang_corefunc.md) [lang_corefunc.html#likely](lang_corefunc.md#likely) [lang_corefunc.html#unlikely](lang_corefunc.md#unlikely) [oldnews.html](oldnews.md) [queryplanner-ng.html#howtofix](queryplanner-ng.md#howtofix) [releaselog/3_8_1.html](releaselog/3_8_1.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- likely → [changes.html#version_3_8_6](changes.md#version_3_8_6) [changes.html#version_3_8_8](changes.md#version_3_8_8) [lang_corefunc.html](lang_corefunc.md) [lang_corefunc.html#likelihood](lang_corefunc.md#likelihood) [releaselog/3_8_6.html](releaselog/3_8_6.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- LIMIT → [lang_insert.html](lang_insert.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#values](lang_select.md#values)
- limit categories → [c3ref/limit.html](c3ref/limit.md) [capi3ref.html#sqlite3_limit](capi3ref.md#sqlite3_limit)
- limits → [c3ref/c_limit_attached.html](c3ref/c_limit_attached.md) [c3ref/limit.html](c3ref/limit.md) [capi3ref.html#SQLITE_LIMIT_ATTACHED](capi3ref.md#SQLITE_LIMIT_ATTACHED) [capi3ref.html#sqlite3_limit](capi3ref.md#sqlite3_limit) [compile.html#yystackdepth](compile.md#yystackdepth) [security.html](security.md) [testing.html#tension](testing.md#tension)
- line mode → [climode.html#opt-sw](climode.md#opt-sw)
- list of virtual tables → [vtab.html](vtab.md)
- literal-value → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- ln → [lang_mathfunc.html](lang_mathfunc.md)
- load_extension → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigenableloadextension](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenableloadextension) [c3ref/enable_load_extension.html](c3ref/enable_load_extension.md) [c3ref/load_extension.html](c3ref/load_extension.md) [capi3ref.html#sqlite3_enable_load_extension](capi3ref.md#sqlite3_enable_load_extension) [capi3ref.html#sqlite3_load_extension](capi3ref.md#sqlite3_load_extension) [capi3ref.html#sqlitedbconfigenableloadextension](capi3ref.md#sqlitedbconfigenableloadextension) [changes.html#version_3_13_0](changes.md#version_3_13_0) [lang_corefunc.html](lang_corefunc.md) [loadext.html](loadext.md) [releaselog/3_13_0.html](releaselog/3_13_0.md) [tclsqlite.html#enable_load_extension](tclsqlite.md#enable_load_extension)
- load_extension SQL function → [c3ref/c_deterministic.html#sqliteinnocuous](c3ref/c_deterministic.md#sqliteinnocuous) [c3ref/load_extension.html](c3ref/load_extension.md) [capi3ref.html#sqlite3_load_extension](capi3ref.md#sqlite3_load_extension) [capi3ref.html#sqliteinnocuous](capi3ref.md#sqliteinnocuous) [howtocompile.html#cli](howtocompile.md#cli)
- loadable extension → [base64.html](base64.md) [base85.html](base85.md) [carray.html](carray.md) [changes.html#version_3_16_0](changes.md#version_3_16_0) [changes.html#version_3_19_0](changes.md#version_3_19_0) [changes.html#version_3_32_0](changes.md#version_3_32_0) [changes.html#version_3_8_0](changes.md#version_3_8_0) [changes.html#version_3_8_6](changes.md#version_3_8_6) [changes.html#version_3_8_8](changes.md#version_3_8_8) [cksumvfs.html](cksumvfs.md) [cli.html#fileio](cli.md#fileio) [compile.html#enable_carray](compile.md#enable_carray) [compile.html#enable_percentile](compile.md#enable_percentile) [csv.html](csv.md) [lang_aggfunc.html#median](lang_aggfunc.md#median) [lang_aggfunc.html#percentile](lang_aggfunc.md#percentile) [lang_aggfunc.html#percentile_cont](lang_aggfunc.md#percentile_cont) [lang_aggfunc.html#percentile_disc](lang_aggfunc.md#percentile_disc) [lang_aggfunc.html#sumunc](lang_aggfunc.md#sumunc) [percentile.html](percentile.md) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md) [releaselog/3_8_6.html](releaselog/3_8_6.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md) [rescode.html#ok_load_permanently](rescode.md#ok_load_permanently) [series.html](series.md) [spellfix1.html](spellfix1.md) [swarmvtab.html#compiling_and_using_swarmvtab](swarmvtab.md#compiling_and_using_swarmvtab) [uintcseq.html](uintcseq.md) [unionvtab.html](unionvtab.md) [vtab.html#customvtab](vtab.md#customvtab) [zipfile.html](zipfile.md)
- loadable extensions → [appfunc.html](appfunc.md) [c3ref/api_routines.html](c3ref/api_routines.md) [capi3ref.html#sqlite3_api_routines](capi3ref.md#sqlite3_api_routines) [changes.html#version_3_31_1](changes.md#version_3_31_1) [cintro.html](cintro.md) [cli.html#arinsup](cli.md#arinsup) [releaselog/3_31_1.html](releaselog/3_31_1.md) [rescode.html#ok_load_permanently](rescode.md#ok_load_permanently)
- localtime modifier → [changes.html#version_3_38_1](changes.md#version_3_38_1) [compile.html#localtime_r](compile.md#localtime_r) [compile.html#localtime_s](compile.md#localtime_s) [deterministic.html#dtexception](deterministic.md#dtexception) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md)
- lock-byte page → [walformat.html#locks](walformat.md#locks)
- locking_mode → [changes.html#version_3_5_9](changes.md#version_3_5_9) [compile.html#default_journal_size_limit](compile.md#default_journal_size_limit) [compile.html#default_locking_mode](compile.md#default_locking_mode) [howtocorrupt.html#fakeusb](howtocorrupt.md#fakeusb) [releaselog/3_5_9.html](releaselog/3_5_9.md) [wal.html#busy](wal.md#busy) [wal.html#noshm](wal.md#noshm)
- log → [lang_mathfunc.html](lang_mathfunc.md)
- log2 → [lang_mathfunc.html](lang_mathfunc.md)
- long term support → [versionnumbers.html](versionnumbers.md)
- lookaside buffer → [news.html](news.md)
- lookaside memory → [c3ref/c_config_covering_index_scan.html#sqliteconfiglookaside](c3ref/c_config_covering_index_scan.md#sqliteconfiglookaside) [c3ref/c_prepare_dont_log.html#sqlitepreparepersistent](c3ref/c_prepare_dont_log.md#sqlitepreparepersistent) [capi3ref.html#sqliteconfiglookaside](capi3ref.md#sqliteconfiglookaside) [capi3ref.html#sqlitepreparepersistent](capi3ref.md#sqlitepreparepersistent) [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- lookaside memory allocator → [c3ref/c_dbconfig_defensive.html#sqlitedbconfiglookaside](c3ref/c_dbconfig_defensive.md#sqlitedbconfiglookaside) [capi3ref.html#sqlitedbconfiglookaside](capi3ref.md#sqlitedbconfiglookaside) [changes.html#version_3_16_0](changes.md#version_3_16_0) [changes.html#version_3_17_0](changes.md#version_3_17_0) [changes.html#version_3_31_0](changes.md#version_3_31_0) [changes.html#version_3_6_1](changes.md#version_3_6_1) [changes.html#version_3_7_9](changes.md#version_3_7_9) [compile.html#default_lookaside](compile.md#default_lookaside) [compile.html#omit_lookaside](compile.md#omit_lookaside) [debugging.html](debugging.md) [malloc.html#memstatus](malloc.md#memstatus) [malloc.html#nofrag](malloc.md#nofrag) [oldnews.html](oldnews.md) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_17_0.html](releaselog/3_17_0.md) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [releaselog/3_6_1.html](releaselog/3_6_1.md) [releaselog/3_7_9.html](releaselog/3_7_9.md)
- lower → [faq.html#q18](faq.md#q18) [lang_corefunc.html](lang_corefunc.md) [lang_corefunc.html#randomblob](lang_corefunc.md#randomblob)
- ltrim → [lang_corefunc.html](lang_corefunc.md)
- mailing lists → [bindptr.html](bindptr.md) [qmplan.html](qmplan.md)
- Manual Control Of Query Plans Using SQLITE_STAT Tables → [lang_analyze.html#statanal](lang_analyze.md#statanal)
- master journal → [changes.html#version_3_12_0](changes.md#version_3_12_0) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md)
- MATCH → [changes.html#version_3_14](changes.md#version_3_14) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [vtab.html#xfindfunction](vtab.md#xfindfunction)
- matchinfo → [bindptr.html](bindptr.md) [bindptr.html#ptrtyp](bindptr.md#ptrtyp) [changes.html#version_3_7_4](changes.md#version_3_7_4) [changes.html#version_3_8_10](changes.md#version_3_8_10) [changes.html#version_3_8_11](changes.md#version_3_8_11) [cves.html#cvetab](cves.md#cvetab) [fts3.html#appendix_a](fts3.md#appendix_a) [fts3.html#fts4](fts3.md#fts4) [fts3.html#fts4_options](fts3.md#fts4_options) [fts3.html#simple_fts_queries](fts3.md#simple_fts_queries) [fts3.html#the_matchinfo_option](fts3.md#the_matchinfo_option) [oldnews.html](oldnews.md) [releaselog/3_7_4.html](releaselog/3_7_4.md) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- matchinfo b flag → [changes.html#version_3_8_11](changes.md#version_3_8_11) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- matchinfo x flag → [fts3.html#matchinfo-y](fts3.md#matchinfo-y)
- matchinfo y flag → [changes.html#version_3_8_10](changes.md#version_3_8_10) [fts3.html#matchinfo-b](fts3.md#matchinfo-b) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md)
- MATERIALIZED → [changes.html#version_3_35_0](changes.md#version_3_35_0) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- math functions → [lang_expr.html#\*funcinexpr](lang_expr.md#*funcinexpr)
- mathfunc → [lang.html](lang.md) [lang_corefunc.html](lang_corefunc.md)
- max → [lang_corefunc.html](lang_corefunc.md)
- max_agg → [lang_aggfunc.html#aggfunclist](lang_aggfunc.md#aggfunclist) [lang_corefunc.html#max_scalar](lang_corefunc.md#max_scalar) [lang_expr.html#\*funcinexpr](lang_expr.md#*funcinexpr) [lang_select.html#bareagg](lang_select.md#bareagg)
- max_page_count → [c3ref/limit.html](c3ref/limit.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [capi3ref.html#sqlite3_limit](capi3ref.md#sqlite3_limit) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer)
- max_scalar → [lang_expr.html#\*funcinexpr](lang_expr.md#*funcinexpr)
- MC/DC → [lemon.html](lemon.md) [testing.html#tcl](testing.md#tcl) [testing.html#tension](testing.md#tension) [th3.html](th3.md)
- MC/DC testing → [assert.html](assert.md)
- median → [changes.html#version_3_47_0](changes.md#version_3_47_0) [lang_aggfunc.html#aggfunclist](lang_aggfunc.md#aggfunclist) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md)
- memory → [lang_attach.html](lang_attach.md) [tclsqlite.html](tclsqlite.md)
- memory allocation → [cintro.html](cintro.md) [testing.html#memtesting](testing.md#memtesting) [testing.html#oomtesting](testing.md#oomtesting)
- memory statistics → [malloc.html#memstatus](malloc.md#memstatus) [malloc.html#nofrag](malloc.md#nofrag)
- memory-mapped I/O → [changes.html#version_3_10_0](changes.md#version_3_10_0) [changes.html#version_3_7_17](changes.md#version_3_7_17) [fasterthanfs.html](fasterthanfs.md) [howtocorrupt.html#fakeusb](howtocorrupt.md#fakeusb) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- memsys2 → [testing.html#memtesting](testing.md#memtesting)
- memsys5 → [changes.html#version_3_40_1](changes.md#version_3_40_1) [changes.html#version_3_6_6](changes.md#version_3_6_6) [malloc.html#nofrag](malloc.md#nofrag) [news.html](news.md) [releaselog/3_40_1.html](releaselog/3_40_1.md) [releaselog/3_6_6.html](releaselog/3_6_6.md)
- merge command → [fts3.html#\*fts4automergecmd](fts3.md#*fts4automergecmd)
- microoptimizations → [changes.html#version_3_21_0](changes.md#version_3_21_0) [changes.html#version_3_39_0](changes.md#version_3_39_0) [news.html](news.md) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_39_0.html](releaselog/3_39_0.md) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- min → [lang_corefunc.html](lang_corefunc.md)
- min/max optimization → [changes.html#version_3_35_0](changes.md#version_3_35_0) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- min_agg → [lang_aggfunc.html#aggfunclist](lang_aggfunc.md#aggfunclist) [lang_corefunc.html#min_scalar](lang_corefunc.md#min_scalar) [lang_select.html#bareagg](lang_select.md#bareagg)
- mmap_size pragma → [compile.html#default_mmap_size](compile.md#default_mmap_size) [mmap.html](mmap.md)
- mod → [lang_mathfunc.html](lang_mathfunc.md)
- modeof → [changes.html#version_3_15_0](changes.md#version_3_15_0) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md)
- modifiers → [lang_datefunc.html](lang_datefunc.md)
- most used → [index.html](index.md)
- most widely deployed → [about.html](about.md) [appfileformat.html](appfileformat.md) [famous.html](famous.md) [testing.html#thoughts1](testing.md#thoughts1)
- mutation test script → [testing.html#mutationtests](testing.md#mutationtests)
- mutation testing → [th3.html#muttest](th3.md#muttest)
- mxFrame → [fileformat2.html#walread](fileformat2.md#walread) [walformat.html#locks](walformat.md#locks) [walformat.html#nbackfill](walformat.md#nbackfill) [walformat.html#recovery](walformat.md#recovery)
- N3 algorithm → [queryplanner-ng.html#starq](queryplanner-ng.md#starq)
- N3 query planning algorithm → [queryplanner-ng.html#starq](queryplanner-ng.md#starq)
- nBackfill → [walformat.html#locks](walformat.md#locks) [walformat.html#mxframe](walformat.md#mxframe) [walformat.html#recovery](walformat.md#recovery)
- NEAR queries → [compile.html#fts3_max_expr_depth](compile.md#fts3_max_expr_depth)
- nexec and ncycle → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigstmtscanstatus](c3ref/c_dbconfig_defensive.md#sqlitedbconfigstmtscanstatus) [c3ref/stmt_scanstatus.html](c3ref/stmt_scanstatus.md) [capi3ref.html#sqlite3_stmt_scanstatus](capi3ref.md#sqlite3_stmt_scanstatus) [capi3ref.html#sqlitedbconfigstmtscanstatus](capi3ref.md#sqlitedbconfigstmtscanstatus) [compile.html#enable_stmt_scanstatus](compile.md#enable_stmt_scanstatus)
- next generation query planner → [changes.html#version_3_8_0](changes.md#version_3_8_0) [eqp.html](eqp.md) [oldnews.html](oldnews.md) [queryplanner.html](queryplanner.md) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md) [versionnumbers.html](versionnumbers.md)
- Next Generation Query Planner → [howitworks.html](howitworks.md) [optoverview.html](optoverview.md) [optoverview.html#joins](optoverview.md#joins)
- NGQP → [changes.html#version_3_8_0](changes.md#version_3_8_0) [limits.html#max_sql_length](limits.md#max_sql_length) [oldnews.html](oldnews.md) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md)
- NOCASE → [faq.html#q18](faq.md#q18)
- non-deterministic functions → [changes.html#version_3_35_2](changes.md#version_3_35_2) [partialindex.html](partialindex.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- NOT MATERIALIZED → [changes.html#version_3_35_0](changes.md#version_3_35_0) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- NOT NULL → [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_8_6](changes.md#version_3_8_6) [conflict.html](conflict.md) [fullsql.html](fullsql.md) [lang_conflict.html](lang_conflict.md) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_8_6.html](releaselog/3_8_6.md)
- NOT NULL constraint → [changes.html#version_3_37_0](changes.md#version_3_37_0) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md) [rescode.html#constraint_notnull](rescode.md#constraint_notnull)
- NOT NULL constraints → [stricttables.html](stricttables.md)
- NUL characters in strings → [quirks.html#dblquote](quirks.md#dblquote)
- nullif → [lang_corefunc.html](lang_corefunc.md)
- NULLS FIRST → [changes.html#version_3_30_0](changes.md#version_3_30_0) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md)
- NULLS LAST → [changes.html#version_3_30_0](changes.md#version_3_30_0) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md)
- numeric literals → [changes.html#version_3_46_0](changes.md#version_3_46_0) [releaselog/3_46_0.html](releaselog/3_46_0.md) [releaselog/3_46_1.html](releaselog/3_46_1.md)
- numeric-literal → [lang_expr.html#litvalue](lang_expr.md#litvalue)
- object resolution → [lang_dropview.html](lang_dropview.md)
- octet_length → [changes.html#version_3_43_0](changes.md#version_3_43_0) [lang_corefunc.html](lang_corefunc.md) [lang_corefunc.html#length](lang_corefunc.md#length) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md)
- offsets → [bindptr.html](bindptr.md) [bindptr.html#ptrtyp](bindptr.md#ptrtyp) [fts3.html#appendix_a](fts3.md#appendix_a) [fts3.html#simple_fts_queries](fts3.md#simple_fts_queries)
- omit-left-join optimization → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- omitfeatures → [34to35.html](34to35.md) [changes.html#version_3_1_4](changes.md#version_3_1_4) [changes.html#version_3_5_2](changes.md#version_3_5_2) [faq.html#q23](faq.md#q23) [oldnews.html](oldnews.md) [releaselog/3_1_4.html](releaselog/3_1_4.md) [releaselog/3_5_2.html](releaselog/3_5_2.md)
- ON CONFLICT → [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/c_fail.html](c3ref/c_fail.md) [c3ref/c_vtab_constraint_support.html#sqlitevtabconstraintsupport](c3ref/c_vtab_constraint_support.md#sqlitevtabconstraintsupport) [c3ref/update_hook.html](c3ref/update_hook.md) [c3ref/vtab_on_conflict.html](c3ref/vtab_on_conflict.md) [capi3ref.html#SQLITE_FAIL](capi3ref.md#SQLITE_FAIL) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_update_hook](capi3ref.md#sqlite3_update_hook) [capi3ref.html#sqlite3_vtab_on_conflict](capi3ref.md#sqlite3_vtab_on_conflict) [capi3ref.html#sqlitevtabconstraintsupport](capi3ref.md#sqlitevtabconstraintsupport) [changes.html#version_3_6_18](changes.md#version_3_6_18) [changes.html#version_3_7_7](changes.md#version_3_7_7) [changes.html#version_3_8_11](changes.md#version_3_8_11) [fullsql.html](fullsql.md) [lang_createtable.html#notnullconst](lang_createtable.md#notnullconst) [lang_createtrigger.html](lang_createtrigger.md) [lang_createtrigger.html#raise](lang_createtrigger.md#raise) [lang_insert.html](lang_insert.md) [lang_replace.html](lang_replace.md) [lang_transaction.html](lang_transaction.md) [lang_update.html](lang_update.md) [oldnews.html](oldnews.md) [releaselog/3_6_18.html](releaselog/3_6_18.md) [releaselog/3_7_7.html](releaselog/3_7_7.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [tempfiles.html#stmtjrnl](tempfiles.md#stmtjrnl)
- ON CONFLICT clause → [lang.html](lang.md)
- ON CONFLICT clauses → [stricttables.html](stricttables.md)
- on-disk format → [stricttables.html](stricttables.md)
- opcode definitions → [opcode.html](opcode.md)
- OPEN_NOFOLLOW → [changes.html#version_3_31_0](changes.md#version_3_31_0) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- OpenOffice case study → [appfileformat.html](appfileformat.md)
- optimize command → [fts3.html#fts4](fts3.md#fts4)
- optimizer → [eqp.html](eqp.md)
- OR optimization → [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_24_0](changes.md#version_3_24_0) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_27_1](changes.md#version_3_27_1) [changes.html#version_3_8_11](changes.md#version_3_8_11) [changes.html#version_3_9_0](changes.md#version_3_9_0) [eqp.html#or-opt](eqp.md#or-opt) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_24_0.html](releaselog/3_24_0.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- or optimization → [changes.html#version_3_7_14](changes.md#version_3_7_14) [changes.html#version_3_7_4](changes.md#version_3_7_4) [releaselog/3_7_14.html](releaselog/3_7_14.md) [releaselog/3_7_4.html](releaselog/3_7_4.md)
- or-connected-terms → [changes.html#version_3_8_5](changes.md#version_3_8_5) [eqp.html#or-opt](eqp.md#or-opt) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- ORDER BY → [changes.html#version_3_30_0](changes.md#version_3_30_0) [changes.html#version_3_8_10](changes.md#version_3_8_10) [lang_insert.html](lang_insert.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#values](lang_select.md#values) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md)
- order by → [lang_createtable.html#createtabas](lang_createtable.md#createtabas)
- ordering-term → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- OS backend → [testing.html#journaltest](testing.md#journaltest)
- OSS Fuzz → [testing.html#fuzzcheck](testing.md#fuzzcheck)
- OUTER JOIN strength reduction → [changes.html#version_3_43_0](changes.md#version_3_43_0) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md)
- output mode → [cli.html#dotconn](cli.md#dotconn)
- over-clause → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- overflow pages → [changes.html#version_3_7_9](changes.md#version_3_7_9) [compile.html#direct_overflow_read](compile.md#direct_overflow_read) [fileformat2.html#btree](fileformat2.md#btree) [releaselog/3_7_9.html](releaselog/3_7_9.md)
- page cache → [changes.html#version_3_39_4](changes.md#version_3_39_4) [changes.html#version_3_7_9](changes.md#version_3_7_9) [compile.html#direct_overflow_read](compile.md#direct_overflow_read) [releaselog/3_39_4.html](releaselog/3_39_4.md) [releaselog/3_7_9.html](releaselog/3_7_9.md)
- page_count → [35to36.html](35to36.md) [changes.html#version_3_7_9](changes.md#version_3_7_9) [releaselog/3_7_9.html](releaselog/3_7_9.md)
- page_size → [arch.html](arch.md) [lang_vacuum.html](lang_vacuum.md) [pgszchng2016.html](pgszchng2016.md) [wal.html#advantages](wal.md#advantages)
- page_size pragma → [lang_vacuum.html](lang_vacuum.md) [pgszchng2016.html](pgszchng2016.md)
- pagecache memory allocator → [c3ref/c_status_malloc_count.html#sqlitestatuspagecachesize](c3ref/c_status_malloc_count.md#sqlitestatuspagecachesize) [c3ref/c_status_malloc_count.html#sqlitestatuspagecacheused](c3ref/c_status_malloc_count.md#sqlitestatuspagecacheused) [capi3ref.html#sqlitestatuspagecachesize](capi3ref.md#sqlitestatuspagecachesize) [capi3ref.html#sqlitestatuspagecacheused](capi3ref.md#sqlitestatuspagecacheused) [malloc.html#memstatus](malloc.md#memstatus) [malloc.html#nofrag](malloc.md#nofrag)
- parameter → [c3ref/bind_blob.html](c3ref/bind_blob.md) [c3ref/c_limit_attached.html#sqlitelimitvariablenumber](c3ref/c_limit_attached.md#sqlitelimitvariablenumber) [c3ref/prepare.html](c3ref/prepare.md) [capi3ref.html#sqlite3_bind_blob](capi3ref.md#sqlite3_bind_blob) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlitelimitvariablenumber](capi3ref.md#sqlitelimitvariablenumber) [carray.html#twoarg](carray.md#twoarg) [cintro.html](cintro.md) [fts3.html#f3tknzr](fts3.md#f3tknzr) [limits.html#max_variable_number](limits.md#max_variable_number) [optoverview.html#like_opt](optoverview.md#like_opt) [optoverview.html#rangequery](optoverview.md#rangequery)
- parameter binding → [c3ref/result_blob.html](c3ref/result_blob.md) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [carray.html](carray.md)
- parameters → [c3ref/get_auxdata.html](c3ref/get_auxdata.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html#sqlite3_get_auxdata](capi3ref.md#sqlite3_get_auxdata) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [changes.html#version_3_23_0](changes.md#version_3_23_0) [changes.html#version_3_32_0](changes.md#version_3_32_0) [cintro.html](cintro.md) [datatype3.html#storageclasses](datatype3.md#storageclasses) [limits.html#max_sql_length](limits.md#max_sql_length) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- parent key → [lang_createtable.html#rowid](lang_createtable.md#rowid)
- parent table → [lang_altertable.html#altertabrename](lang_altertable.md#altertabrename)
- partial index → [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_15_0](changes.md#version_3_15_0) [changes.html#version_3_28_0](changes.md#version_3_28_0) [changes.html#version_3_8_1](changes.md#version_3_8_1) [changes.html#version_3_8_7](changes.md#version_3_8_7) [changes.html#version_3_8_8](changes.md#version_3_8_8) [changes.html#version_3_8_8_3](changes.md#version_3_8_8_3) [deterministic.html](deterministic.md) [deterministic.html#dtexception](deterministic.md#dtexception) [fileformat2.html##sqltab](fileformat2.md##sqltab) [fullsql.html](fullsql.md) [lang_altertable.html#altertabdropcol](lang_altertable.md#altertabdropcol) [lang_createindex.html](lang_createindex.md) [oldnews.html](oldnews.md) [pragma.html#pragma_case_sensitive_like](pragma.md#pragma_case_sensitive_like) [pragma.html#pragma_index_list](pragma.md#pragma_index_list) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_28_0.html](releaselog/3_28_0.md) [releaselog/3_8_1.html](releaselog/3_8_1.md) [releaselog/3_8_7.html](releaselog/3_8_7.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- partial indexes → [c3ref/c_deterministic.html#sqlitedeterministic](c3ref/c_deterministic.md#sqlitedeterministic) [c3ref/c_deterministic.html#sqlitedirectonly](c3ref/c_deterministic.md#sqlitedirectonly) [c3ref/c_deterministic.html#sqliteinnocuous](c3ref/c_deterministic.md#sqliteinnocuous) [capi3ref.html#sqlitedeterministic](capi3ref.md#sqlitedeterministic) [capi3ref.html#sqlitedirectonly](capi3ref.md#sqlitedirectonly) [capi3ref.html#sqliteinnocuous](capi3ref.md#sqliteinnocuous) [changes.html#version_3_16_0](changes.md#version_3_16_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_8_0](changes.md#version_3_8_0) [changes.html#version_3_9_0](changes.md#version_3_9_0) [features.html](features.md) [fileformat2.html#stat1tab](fileformat2.md#stat1tab) [pragma.html#pragma_legacy_alter_table](pragma.md#pragma_legacy_alter_table) [pragma.html#pragma_trusted_schema](pragma.md#pragma_trusted_schema) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md) [versionnumbers.html](versionnumbers.md)
- partial indices → [oldnews.html](oldnews.md)
- partial sorting by index → [changes.html#version_3_8_5](changes.md#version_3_8_5) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- partition → [windowfunctions.html#exprrange](windowfunctions.md#exprrange) [windowfunctions.html#frameboundary](windowfunctions.md#frameboundary)
- patchset → [session.html#sqlite3_changeset_iter](session.md#sqlite3_changeset_iter) [session/changeset_iter.html](session/changeset_iter.md)
- patchsets → [session.html#sqlite3_changegroup](session.md#sqlite3_changegroup) [session/changegroup.html](session/changegroup.md)
- PENDING lock → [rescode.html#ioerr_lock](rescode.md#ioerr_lock)
- percentile → [changes.html#version_3_47_0](changes.md#version_3_47_0) [lang_aggfunc.html#aggfunclist](lang_aggfunc.md#aggfunclist) [lang_aggfunc.html#percentile_cont](lang_aggfunc.md#percentile_cont) [percentile.html#\*medianfunc](percentile.md#*medianfunc) [percentile.html#\*percentilecontfunc](percentile.md#*percentilecontfunc) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md)
- percentile extension → [changes.html#version_3_51_0](changes.md#version_3_51_0) [compile.html#enable_percentile](compile.md#enable_percentile) [lang_aggfunc.html#median](lang_aggfunc.md#median) [lang_aggfunc.html#percentile](lang_aggfunc.md#percentile) [lang_aggfunc.html#percentile_cont](lang_aggfunc.md#percentile_cont) [lang_aggfunc.html#percentile_disc](lang_aggfunc.md#percentile_disc) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- percentile_cont → [changes.html#version_3_47_0](changes.md#version_3_47_0) [compile.html#enable_ordered_set_aggregates](compile.md#enable_ordered_set_aggregates) [lang_aggfunc.html#aggfunclist](lang_aggfunc.md#aggfunclist) [lang_aggfunc.html#median](lang_aggfunc.md#median) [lang_aggfunc.html#percentile](lang_aggfunc.md#percentile) [lang_aggfunc.html#percentile_disc](lang_aggfunc.md#percentile_disc) [percentile.html#\*percentilediscfunc](percentile.md#*percentilediscfunc) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md)
- percentile_disc → [changes.html#version_3_47_0](changes.md#version_3_47_0) [lang_aggfunc.html#aggfunclist](lang_aggfunc.md#aggfunclist) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md)
- permuted index → [doclist.html](doclist.md) [keyword_index.html](keyword_index.md)
- persistent journal mode → [pragma.html#pragma_journal_size_limit](pragma.md#pragma_journal_size_limit)
- persistent loadable extensions → [changes.html#version_3_14](changes.md#version_3_14) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- phrase queries → [compile.html#fts3_max_expr_depth](compile.md#fts3_max_expr_depth)
- pi → [lang_mathfunc.html](lang_mathfunc.md)
- pointer passing interface → [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/result_blob.html](c3ref/result_blob.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob)
- pointer passing interfaces → [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- pointer value → [c3ref/value_dup.html](c3ref/value_dup.md) [capi3ref.html#sqlite3_value_dup](capi3ref.md#sqlite3_value_dup)
- posix-close-bug → [changes.html#version_3_51_0](changes.md#version_3_51_0) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- pow → [lang_mathfunc.html](lang_mathfunc.md)
- power-safe → [fasterthanfs.html](fasterthanfs.md)
- power-safe transactions → [fasterthanfs.html](fasterthanfs.md)
- powersafe overwrite → [c3ref/open.html#coreuriqueryparameters](c3ref/open.md#coreuriqueryparameters) [capi3ref.html#coreuriqueryparameters](capi3ref.md#coreuriqueryparameters) [changes.html#version_3_7_10](changes.md#version_3_7_10) [compile.html#powersafe_overwrite](compile.md#powersafe_overwrite) [oldnews.html](oldnews.md) [releaselog/3_7_10.html](releaselog/3_7_10.md) [uri.html#uripsow](uri.md#uripsow)
- PRAGMA → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlpragma](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlpragma) [c3ref/limit.html](c3ref/limit.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [capi3ref.html#sqlite3_limit](capi3ref.md#sqlite3_limit) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlitefcntlpragma](capi3ref.md#sqlitefcntlpragma) [changes.html#version_3_16_2](changes.md#version_3_16_2) [changes.html#version_3_7_11](changes.md#version_3_7_11) [changes.html#version_3_7_17](changes.md#version_3_7_17) [compile.html#debug](compile.md#debug) [compile.html#omit_deprecated](compile.md#omit_deprecated) [compile.html#omit_flag_pragmas](compile.md#omit_flag_pragmas) [compile.html#omit_pragma](compile.md#omit_pragma) [lang.html](lang.md) [lang_explain.html](lang_explain.md) [lang_transaction.html](lang_transaction.md) [oldnews.html](oldnews.md) [opcode.html#subprog](opcode.md#subprog) [pragma.html#pragma_defer_foreign_keys](pragma.md#pragma_defer_foreign_keys) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_7_11.html](releaselog/3_7_11.md) [releaselog/3_7_17.html](releaselog/3_7_17.md) [testing.html#crashtesting](testing.md#crashtesting) [vtablist.html](vtablist.md)
- PRAGMA analysis_limit → [changes.html#version_3_32_0](changes.md#version_3_32_0) [lang_analyze.html#approx](lang_analyze.md#approx) [lang_analyze.html#pragopt](lang_analyze.md#pragopt) [pragma.html#pragma_optimize](pragma.md#pragma_optimize) [pragma.html#toc](pragma.md#toc) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- PRAGMA application_id → [c3ref/snapshot_open.html](c3ref/snapshot_open.md) [capi3ref.html#sqlite3_snapshot_open](capi3ref.md#sqlite3_snapshot_open) [changes.html#version_3_7_17](changes.md#version_3_7_17) [fileformat2.html#appid](fileformat2.md#appid) [fileformat2.html#database_header](fileformat2.md#database_header) [pragma.html#toc](pragma.md#toc) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- PRAGMA auto_vacuum → [compile.html#default_autovacuum](compile.md#default_autovacuum) [compile.html#omit_autovacuum](compile.md#omit_autovacuum) [pragma.html#toc](pragma.md#toc)
- PRAGMA automatic_index → [compile.html#default_automatic_index](compile.md#default_automatic_index) [pragma.html#toc](pragma.md#toc)
- PRAGMA busy_timeout → [c3ref/busy_handler.html](c3ref/busy_handler.md) [c3ref/busy_timeout.html](c3ref/busy_timeout.md) [capi3ref.html#sqlite3_busy_handler](capi3ref.md#sqlite3_busy_handler) [capi3ref.html#sqlite3_busy_timeout](capi3ref.md#sqlite3_busy_timeout) [pragma.html#toc](pragma.md#toc)
- PRAGMA cache_size → [c3ref/c_config_covering_index_scan.html#sqliteconfigpmasz](c3ref/c_config_covering_index_scan.md#sqliteconfigpmasz) [c3ref/pcache_methods2.html#thexcachesizepagecachemethod](c3ref/pcache_methods2.md#thexcachesizepagecachemethod) [capi3ref.html#sqliteconfigpmasz](capi3ref.md#sqliteconfigpmasz) [capi3ref.html#thexcachesizepagecachemethod](capi3ref.md#thexcachesizepagecachemethod) [changes.html#version_3_14_1](changes.md#version_3_14_1) [changes.html#version_3_7_10](changes.md#version_3_7_10) [changes.html#version_3_8_11_1](changes.md#version_3_8_11_1) [compile.html#default_cache_size](compile.md#default_cache_size) [oldnews.html](oldnews.md) [pragma.html#pragma_cache_spill](pragma.md#pragma_cache_spill) [pragma.html#toc](pragma.md#toc) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_7_10.html](releaselog/3_7_10.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- PRAGMA cache_spill → [changes.html#version_3_10_0](changes.md#version_3_10_0) [pragma.html#toc](pragma.md#toc) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md)
- PRAGMA case_sensitive_like → [changes.html#version_3_28_0](changes.md#version_3_28_0) [changes.html#version_3_44_0](changes.md#version_3_44_0) [changes.html#version_3_7_7_1](changes.md#version_3_7_7_1) [compile.html#omit_case_sensitive_like_pragma](compile.md#omit_case_sensitive_like_pragma) [oldnews.html](oldnews.md) [pragma.html#toc](pragma.md#toc) [releaselog/3_28_0.html](releaselog/3_28_0.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md) [releaselog/3_7_7_1.html](releaselog/3_7_7_1.md)
- PRAGMA cell_size_check → [changes.html#version_3_8_11](changes.md#version_3_8_11) [pragma.html#toc](pragma.md#toc) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [security.html#baddb](security.md#baddb)
- PRAGMA checkpoint_fullfsync → [changes.html#version_3_21_0](changes.md#version_3_21_0) [changes.html#version_3_7_4](changes.md#version_3_7_4) [pragma.html#toc](pragma.md#toc) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_7_4.html](releaselog/3_7_4.md)
- PRAGMA collation_list → [pragma.html#toc](pragma.md#toc)
- PRAGMA compile_options → [changes.html#version_3_14](changes.md#version_3_14) [pragma.html#toc](pragma.md#toc) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- PRAGMA count_changes → [compile.html#omit_deprecated](compile.md#omit_deprecated) [pragma.html#toc](pragma.md#toc)
- PRAGMA data_store_directory → [changes.html#version_3_39_3](changes.md#version_3_39_3) [compile.html#omit_deprecated](compile.md#omit_deprecated) [pragma.html#toc](pragma.md#toc) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- PRAGMA data_version → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntldataversion](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntldataversion) [c3ref/total_changes.html](c3ref/total_changes.md) [capi3ref.html#sqlite3_total_changes](capi3ref.md#sqlite3_total_changes) [capi3ref.html#sqlitefcntldataversion](capi3ref.md#sqlitefcntldataversion) [changes.html#version_3_8_8](changes.md#version_3_8_8) [oldnews.html](oldnews.md) [pragma.html#toc](pragma.md#toc) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- PRAGMA database_list → [pragma.html#toc](pragma.md#toc)
- PRAGMA default_cache_size → [compile.html#omit_deprecated](compile.md#omit_deprecated) [pragma.html#toc](pragma.md#toc)
- PRAGMA defer_foreign_keys → [changes.html#version_3_12_0](changes.md#version_3_12_0) [pragma.html#toc](pragma.md#toc) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md)
- PRAGMA empty_result_callbacks → [changes.html#version_3_23_1](changes.md#version_3_23_1) [compile.html#omit_deprecated](compile.md#omit_deprecated) [pragma.html#toc](pragma.md#toc) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- PRAGMA encoding → [invalidutf.html](invalidutf.md) [pragma.html#toc](pragma.md#toc)
- PRAGMA foreign_key_check → [changes.html#version_3_19_0](changes.md#version_3_19_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_7_16](changes.md#version_3_7_16) [lang_altertable.html#otheralter](lang_altertable.md#otheralter) [pragma.html#pragma_integrity_check](pragma.md#pragma_integrity_check) [pragma.html#toc](pragma.md#toc) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_7_16.html](releaselog/3_7_16.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md)
- PRAGMA foreign_key_list → [foreignkeys.html#fk_enable](foreignkeys.md#fk_enable) [pragma.html#toc](pragma.md#toc)
- PRAGMA foreign_keys → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigenablefkey](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenablefkey) [capi3ref.html#sqlitedbconfigenablefkey](capi3ref.md#sqlitedbconfigenablefkey) [faq.html#q22](faq.md#q22) [foreignkeys.html#fk_actions](foreignkeys.md#fk_actions) [foreignkeys.html#fk_enable](foreignkeys.md#fk_enable) [lang_altertable.html#altertabrename](lang_altertable.md#altertabrename) [lang_altertable.html#otheralter](lang_altertable.md#otheralter) [pragma.html#toc](pragma.md#toc) [quirks.html](quirks.md)
- PRAGMA freelist_count → [pragma.html#toc](pragma.md#toc)
- PRAGMA full_column_names → [compile.html#omit_deprecated](compile.md#omit_deprecated) [pragma.html#toc](pragma.md#toc)
- PRAGMA fullfsync → [pragma.html#toc](pragma.md#toc)
- PRAGMA function → [news.html](news.md)
- PRAGMA function_list → [changes.html#version_3_30_0](changes.md#version_3_30_0) [compile.html#introspection_pragmas](compile.md#introspection_pragmas) [compile.html#omit_introspection_pragmas](compile.md#omit_introspection_pragmas) [pragma.html#toc](pragma.md#toc) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md)
- PRAGMA functions → [changes.html#version_3_16_0](changes.md#version_3_16_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [news.html](news.md) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [vtablist.html](vtablist.md)
- PRAGMA hard_heap_limit → [c3ref/hard_heap_limit64.html](c3ref/hard_heap_limit64.md) [capi3ref.html#sqlite3_hard_heap_limit64](capi3ref.md#sqlite3_hard_heap_limit64) [changes.html#version_3_31_0](changes.md#version_3_31_0) [pragma.html#toc](pragma.md#toc) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- PRAGMA ignore_check_constraints → [lang_createtable.html#ckconst](lang_createtable.md#ckconst) [lang_createtable.html#notnullconst](lang_createtable.md#notnullconst) [pragma.html#toc](pragma.md#toc)
- PRAGMA incremental_vacuum → [c3ref/data_count.html](c3ref/data_count.md) [capi3ref.html#sqlite3_data_count](capi3ref.md#sqlite3_data_count) [changes.html#version_3_35_3](changes.md#version_3_35_3) [changes.html#version_3_7_16](changes.md#version_3_7_16) [pragma.html#toc](pragma.md#toc) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [releaselog/3_7_16.html](releaselog/3_7_16.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md)
- PRAGMA index_info → [pragma.html#toc](pragma.md#toc) [withoutrowid.html#wtu](withoutrowid.md#wtu)
- PRAGMA index_list → [pragma.html#toc](pragma.md#toc)
- PRAGMA index_xinfo → [changes.html#version_3_8_9](changes.md#version_3_8_9) [oldnews.html](oldnews.md) [pragma.html#toc](pragma.md#toc) [releaselog/3_8_9.html](releaselog/3_8_9.md)
- PRAGMA integrity_check → [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_19_0](changes.md#version_3_19_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_21_0](changes.md#version_3_21_0) [changes.html#version_3_25_0](changes.md#version_3_25_0) [changes.html#version_3_33_0](changes.md#version_3_33_0) [changes.html#version_3_40_0](changes.md#version_3_40_0) [changes.html#version_3_41_0](changes.md#version_3_41_0) [changes.html#version_3_41_1](changes.md#version_3_41_1) [changes.html#version_3_42_0](changes.md#version_3_42_0) [changes.html#version_3_44_0](changes.md#version_3_44_0) [changes.html#version_3_45_1](changes.md#version_3_45_1) [changes.html#version_3_7_12](changes.md#version_3_7_12) [changes.html#version_3_7_14](changes.md#version_3_7_14) [changes.html#version_3_7_16](changes.md#version_3_7_16) [changes.html#version_3_8_10](changes.md#version_3_8_10) [changes.html#version_3_8_6](changes.md#version_3_8_6) [cli.html#selftest](cli.md#selftest) [cves.html#cvetab](cves.md#cvetab) [fts3.html#\*fts4ickcmd](fts3.md#*fts4ickcmd) [invalidutf.html](invalidutf.md) [lang_altertable.html#caution](lang_altertable.md#caution) [lang_createtable.html#notnullconst](lang_createtable.md#notnullconst) [mmap.html](mmap.md) [oldnews.html](oldnews.md) [pragma.html#pragma_case_sensitive_like](pragma.md#pragma_case_sensitive_like) [pragma.html#pragma_quick_check](pragma.md#pragma_quick_check) [pragma.html#toc](pragma.md#toc) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_25_0.html](releaselog/3_25_0.md) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md) [releaselog/3_33_0.html](releaselog/3_33_0.md) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md) [releaselog/3_42_0.html](releaselog/3_42_0.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md) [releaselog/3_7_12.html](releaselog/3_7_12.md) [releaselog/3_7_14.html](releaselog/3_7_14.md) [releaselog/3_7_16.html](releaselog/3_7_16.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md) [releaselog/3_8_6.html](releaselog/3_8_6.md) [rtree.html#rtreecheck](rtree.md#rtreecheck) [security.html#baddb](security.md#baddb) [staleexpridx.html](staleexpridx.md) [staleexpridx.html#selfheal](staleexpridx.md#selfheal) [stricttables.html](stricttables.md) [testing.html#ioerrtesting](testing.md#ioerrtesting) [vtab.html#xintegrity](vtab.md#xintegrity)
- PRAGMA journal_mode → [atomiccommit.html#sprjrnl](atomiccommit.md#sprjrnl) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigdefensive](c3ref/c_dbconfig_defensive.md#sqlitedbconfigdefensive) [capi3ref.html#sqlitedbconfigdefensive](capi3ref.md#sqlitedbconfigdefensive) [changes.html#version_3_6_4](changes.md#version_3_6_4) [changes.html#version_3_8_7_1](changes.md#version_3_8_7_1) [dbhash.html](dbhash.md) [fasterthanfs.html](fasterthanfs.md) [fileformat2.html#walindexformat](fileformat2.md#walindexformat) [howtocorrupt.html#cfgerr](howtocorrupt.md#cfgerr) [isolation.html](isolation.md) [lang_transaction.html#immediate](lang_transaction.md#immediate) [lockingv3.html#hot_journals](lockingv3.md#hot_journals) [lockingv3.html#writing](lockingv3.md#writing) [oldnews.html](oldnews.md) [pragma.html#toc](pragma.md#toc) [releaselog/3_6_4.html](releaselog/3_6_4.md) [releaselog/3_8_7_1.html](releaselog/3_8_7_1.md) [tempfiles.html#superjrnl](tempfiles.md#superjrnl)
- PRAGMA journal_size_limit → [pragma.html#pragma_journal_mode](pragma.md#pragma_journal_mode) [pragma.html#toc](pragma.md#toc)
- PRAGMA legacy_alter_table → [c3ref/c_dbconfig_defensive.html#sqlitedbconfiglegacyaltertable](c3ref/c_dbconfig_defensive.md#sqlitedbconfiglegacyaltertable) [capi3ref.html#sqlitedbconfiglegacyaltertable](capi3ref.md#sqlitedbconfiglegacyaltertable) [changes.html#version_3_25_2](changes.md#version_3_25_2) [changes.html#version_3_26_0](changes.md#version_3_26_0) [lang_altertable.html#altertabrename](lang_altertable.md#altertabrename) [news.html](news.md) [pragma.html#toc](pragma.md#toc) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md) [releaselog/3_26_0.html](releaselog/3_26_0.md) [vtab.html#xrename](vtab.md#xrename)
- PRAGMA legacy_file_format → [changes.html#version_3_7_10](changes.md#version_3_7_10) [compile.html#default_file_format](compile.md#default_file_format) [pragma.html#toc](pragma.md#toc) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- PRAGMA locking_mode → [changes.html#version_3_7_4](changes.md#version_3_7_4) [pragma.html#toc](pragma.md#toc) [releaselog/3_7_4.html](releaselog/3_7_4.md) [tempfiles.html#rollbackjrnl](tempfiles.md#rollbackjrnl) [tempfiles.html#shmfile](tempfiles.md#shmfile) [walformat.html#shm](walformat.md#shm)
- PRAGMA max_page_count → [pragma.html#toc](pragma.md#toc)
- PRAGMA mmap_size → [c3ref/c_config_covering_index_scan.html#sqliteconfigmmapsize](c3ref/c_config_covering_index_scan.md#sqliteconfigmmapsize) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlmmapsize](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlmmapsize) [capi3ref.html#sqliteconfigmmapsize](capi3ref.md#sqliteconfigmmapsize) [capi3ref.html#sqlitefcntlmmapsize](capi3ref.md#sqlitefcntlmmapsize) [changes.html#version_3_45_1](changes.md#version_3_45_1) [compile.html#max_mmap_size](compile.md#max_mmap_size) [mmap.html](mmap.md) [pragma.html#pragma_mmap_size](pragma.md#pragma_mmap_size) [pragma.html#toc](pragma.md#toc) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md) [security.html#baddb](security.md#baddb)
- PRAGMA module_list → [changes.html#version_3_30_0](changes.md#version_3_30_0) [compile.html#introspection_pragmas](compile.md#introspection_pragmas) [compile.html#omit_introspection_pragmas](compile.md#omit_introspection_pragmas) [pragma.html#toc](pragma.md#toc) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md)
- PRAGMA optimize → [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_46_0](changes.md#version_3_46_0) [lang_analyze.html#approx](lang_analyze.md#approx) [lang_analyze.html#autoanalyze](lang_analyze.md#autoanalyze) [lang_analyze.html#pragopt](lang_analyze.md#pragopt) [news.html](news.md) [optoverview.html#option2](optoverview.md#option2) [pragma.html#pragma_analysis_limit](pragma.md#pragma_analysis_limit) [pragma.html#toc](pragma.md#toc) [queryplanner-ng.html#fossilcasestudy](queryplanner-ng.md#fossilcasestudy) [queryplanner-ng.html#howtofix](queryplanner-ng.md#howtofix) [queryplanner-ng.html#qpstab](queryplanner-ng.md#qpstab) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_46_0.html](releaselog/3_46_0.md) [releaselog/3_46_1.html](releaselog/3_46_1.md)
- PRAGMA page_count → [changes.html#version_3_6_1](changes.md#version_3_6_1) [pragma.html#toc](pragma.md#toc) [releaselog/3_6_0.html](releaselog/3_6_0.md)
- PRAGMA page_size → [compile.html#default_page_size](compile.md#default_page_size) [dbhash.html](dbhash.md) [pragma.html#pragma_cache_size](pragma.md#pragma_cache_size) [pragma.html#toc](pragma.md#toc) [psow.html](psow.md)
- PRAGMA parser_trace → [opcode.html#subprog](opcode.md#subprog) [pragma.html#toc](pragma.md#toc)
- PRAGMA pragma_list → [changes.html#version_3_30_0](changes.md#version_3_30_0) [compile.html#introspection_pragmas](compile.md#introspection_pragmas) [compile.html#omit_introspection_pragmas](compile.md#omit_introspection_pragmas) [pragma.html#toc](pragma.md#toc) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md)
- PRAGMA query_only → [pragma.html#toc](pragma.md#toc)
- PRAGMA quick_check → [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_21_0](changes.md#version_3_21_0) [changes.html#version_3_7_14](changes.md#version_3_7_14) [changes.html#version_3_8_10](changes.md#version_3_8_10) [lang_createtable.html#notnullconst](lang_createtable.md#notnullconst) [pragma.html#pragma_integrity_check](pragma.md#pragma_integrity_check) [pragma.html#toc](pragma.md#toc) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_7_14.html](releaselog/3_7_14.md) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md) [security.html#baddb](security.md#baddb) [stricttables.html](stricttables.md) [vtab.html#xintegrity](vtab.md#xintegrity)
- PRAGMA read_uncommitted → [isolation.html](isolation.md) [pragma.html#toc](pragma.md#toc)
- PRAGMA recursive_triggers → [changes.html#version_3_6_18](changes.md#version_3_6_18) [foreignkeys.html#fk_actions](foreignkeys.md#fk_actions) [limits.html#max_trigger_depth](limits.md#max_trigger_depth) [pragma.html#toc](pragma.md#toc) [releaselog/3_6_18.html](releaselog/3_6_18.md)
- PRAGMA reverse_unordered_selects → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigreversescanorder](c3ref/c_dbconfig_defensive.md#sqlitedbconfigreversescanorder) [capi3ref.html#sqlitedbconfigreversescanorder](capi3ref.md#sqlitedbconfigreversescanorder) [changes.html#version_3_12_2](changes.md#version_3_12_2) [changes.html#version_3_13_0](changes.md#version_3_13_0) [changes.html#version_3_21_0](changes.md#version_3_21_0) [compile.html#reverse_unordered_selects](compile.md#reverse_unordered_selects) [pragma.html#toc](pragma.md#toc) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- PRAGMA schema_version → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigdefensive](c3ref/c_dbconfig_defensive.md#sqlitedbconfigdefensive) [capi3ref.html#sqlitedbconfigdefensive](capi3ref.md#sqlitedbconfigdefensive) [changes.html#version_3_40_0](changes.md#version_3_40_0) [howtocorrupt.html#cfgerr](howtocorrupt.md#cfgerr) [lang_altertable.html#caution](lang_altertable.md#caution) [pragma.html#toc](pragma.md#toc) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md)
- PRAGMA secure_delete → [changes.html#version_3_20_0](changes.md#version_3_20_0) [lang_vacuum.html](lang_vacuum.md) [pragma.html#toc](pragma.md#toc) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- PRAGMA short_column_names → [compile.html#omit_deprecated](compile.md#omit_deprecated) [pragma.html#toc](pragma.md#toc)
- PRAGMA shrink_memory → [oldnews.html](oldnews.md) [pragma.html#toc](pragma.md#toc)
- PRAGMA soft_heap_limit → [c3ref/hard_heap_limit64.html](c3ref/hard_heap_limit64.md) [capi3ref.html#sqlite3_hard_heap_limit64](capi3ref.md#sqlite3_hard_heap_limit64) [pragma.html#toc](pragma.md#toc)
- PRAGMA stats → [changes.html#version_3_8_1](changes.md#version_3_8_1) [oldnews.html](oldnews.md) [pragma.html#toc](pragma.md#toc) [releaselog/3_8_1.html](releaselog/3_8_1.md)
- PRAGMA synchronous → [atomiccommit.html#sprjrnl](atomiccommit.md#sprjrnl) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlsync](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlsync) [c3ref/c_sync_dataonly.html](c3ref/c_sync_dataonly.md) [capi3ref.html#SQLITE_SYNC_DATAONLY](capi3ref.md#SQLITE_SYNC_DATAONLY) [capi3ref.html#sqlitefcntlsync](capi3ref.md#sqlitefcntlsync) [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_12_0](changes.md#version_3_12_0) [changes.html#version_3_40_0](changes.md#version_3_40_0) [changes.html#version_3_7_5](changes.md#version_3_7_5) [compile.html#default_synchronous](compile.md#default_synchronous) [compile.html#default_wal_synchronous](compile.md#default_wal_synchronous) [compile.html#extra_durable](compile.md#extra_durable) [compile.html#rcmd](compile.md#rcmd) [faq.html#q19](faq.md#q19) [fasterthanfs.html](fasterthanfs.md) [howtocorrupt.html#cfgerr](howtocorrupt.md#cfgerr) [lang_vacuum.html#vacuuminto](lang_vacuum.md#vacuuminto) [oldnews.html](oldnews.md) [pragma.html#toc](pragma.md#toc) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md) [releaselog/3_7_5.html](releaselog/3_7_5.md) [tempfiles.html#superjrnl](tempfiles.md#superjrnl) [wal.html#fast](wal.md#fast)
- PRAGMA table_info → [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_26_0](changes.md#version_3_26_0) [changes.html#version_3_7_16](changes.md#version_3_7_16) [gencol.html#vgc\*](gencol.md#vgc*) [pragma.html#pragma_table_xinfo](pragma.md#pragma_table_xinfo) [pragma.html#toc](pragma.md#toc) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_26_0.html](releaselog/3_26_0.md) [releaselog/3_7_16.html](releaselog/3_7_16.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md) [vtab.html#hiddencol](vtab.md#hiddencol) [withoutrowid.html#wtu](withoutrowid.md#wtu)
- PRAGMA table_list → [changes.html#version_3_37_0](changes.md#version_3_37_0) [pragma.html#toc](pragma.md#toc) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md)
- PRAGMA table_xinfo → [changes.html#version_3_26_0](changes.md#version_3_26_0) [gencol.html#vgc\*](gencol.md#vgc*) [pragma.html#pragma_table_info](pragma.md#pragma_table_info) [pragma.html#toc](pragma.md#toc) [releaselog/3_26_0.html](releaselog/3_26_0.md) [withoutrowid.html#wtu](withoutrowid.md#wtu)
- PRAGMA temp_store → [changes.html#version_3_37_2](changes.md#version_3_37_2) [compile.html#temp_store](compile.md#temp_store) [howtocorrupt.html#svptbug](howtocorrupt.md#svptbug) [news.html](news.md) [pragma.html#toc](pragma.md#toc) [releaselog/3_37_2.html](releaselog/3_37_2.md)
- PRAGMA temp_store_directory → [changes.html#version_3_39_3](changes.md#version_3_39_3) [compile.html#omit_deprecated](compile.md#omit_deprecated) [pragma.html#toc](pragma.md#toc) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md) [tempfiles.html#tempdir](tempfiles.md#tempdir)
- PRAGMA threads → [c3ref/c_config_covering_index_scan.html#sqliteconfigpmasz](c3ref/c_config_covering_index_scan.md#sqliteconfigpmasz) [capi3ref.html#sqliteconfigpmasz](capi3ref.md#sqliteconfigpmasz) [changes.html#version_3_8_7](changes.md#version_3_8_7) [compile.html#sorter_pmasz](compile.md#sorter_pmasz) [oldnews.html](oldnews.md) [pragma.html#toc](pragma.md#toc) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- PRAGMA trusted_schema → [appfunc.html#sec](appfunc.md#sec) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigtrustedschema](c3ref/c_dbconfig_defensive.md#sqlitedbconfigtrustedschema) [c3ref/c_deterministic.html#sqliteinnocuous](c3ref/c_deterministic.md#sqliteinnocuous) [capi3ref.html#sqlitedbconfigtrustedschema](capi3ref.md#sqlitedbconfigtrustedschema) [capi3ref.html#sqliteinnocuous](capi3ref.md#sqliteinnocuous) [compile.html#trusted_schema](compile.md#trusted_schema) [pragma.html#toc](pragma.md#toc) [security.html#baddb](security.md#baddb) [tclsqlite.html#enable_load_extension](tclsqlite.md#enable_load_extension) [tclsqlite.html#function](tclsqlite.md#function)
- PRAGMA user_version → [pragma.html#toc](pragma.md#toc)
- PRAGMA vdbe_addoptrace → [changes.html#version_3_7_16](changes.md#version_3_7_16) [opcode.html#subprog](opcode.md#subprog) [pragma.html#toc](pragma.md#toc) [releaselog/3_7_16.html](releaselog/3_7_16.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md)
- PRAGMA vdbe_debug → [changes.html#version_3_7_16](changes.md#version_3_7_16) [opcode.html#subprog](opcode.md#subprog) [pragma.html#toc](pragma.md#toc) [releaselog/3_7_16.html](releaselog/3_7_16.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md)
- PRAGMA vdbe_listing → [opcode.html#subprog](opcode.md#subprog) [pragma.html#toc](pragma.md#toc)
- PRAGMA vdbe_trace → [changes.html#version_3_27_0](changes.md#version_3_27_0) [opcode.html#subprog](opcode.md#subprog) [pragma.html#toc](pragma.md#toc) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [whybytecode.html](whybytecode.md)
- PRAGMA wal_autocheckpoint → [pragma.html#toc](pragma.md#toc)
- PRAGMA wal_checkpoint → [c3ref/wal_checkpoint_v2.html](c3ref/wal_checkpoint_v2.md) [c3ref/wal_hook.html](c3ref/wal_hook.md) [capi3ref.html#sqlite3_wal_checkpoint_v2](capi3ref.md#sqlite3_wal_checkpoint_v2) [capi3ref.html#sqlite3_wal_hook](capi3ref.md#sqlite3_wal_hook) [changes.html#version_3_51_0](changes.md#version_3_51_0) [changes.html#version_3_8_8](changes.md#version_3_8_8) [pragma.html#toc](pragma.md#toc) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- PRAGMA writable_schema → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigdefensive](c3ref/c_dbconfig_defensive.md#sqlitedbconfigdefensive) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigwritableschema](c3ref/c_dbconfig_defensive.md#sqlitedbconfigwritableschema) [capi3ref.html#sqlitedbconfigdefensive](capi3ref.md#sqlitedbconfigdefensive) [capi3ref.html#sqlitedbconfigwritableschema](capi3ref.md#sqlitedbconfigwritableschema) [changes.html#version_3_28_0](changes.md#version_3_28_0) [changes.html#version_3_38_0](changes.md#version_3_38_0) [changes.html#version_3_44_0](changes.md#version_3_44_0) [faq.html#q7](faq.md#q7) [howtocorrupt.html#cfgerr](howtocorrupt.md#cfgerr) [imposter.html](imposter.md) [lang_altertable.html#altertabdropcol](lang_altertable.md#altertabdropcol) [lang_altertable.html#caution](lang_altertable.md#caution) [pragma.html#toc](pragma.md#toc) [releaselog/3_28_0.html](releaselog/3_28_0.md) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md) [stricttables.html](stricttables.md)
- pragma-stmt → [pragma.html#syntax](pragma.md#syntax)
- pragma-value → [pragma.html#syntax](pragma.md#syntax)
- precompiled amalgamation tarball → [changes.html#version_3_49_0](changes.md#version_3_49_0) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md)
- precompiled amalgamation tarballs → [changes.html#version_3_43_0](changes.md#version_3_43_0) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md)
- predicate push-down → [changes.html#version_3_47_0](changes.md#version_3_47_0) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md)
- prefix queries → [fts3.html#fts4order](fts3.md#fts4order) [fts3.html#the_prefix_option](fts3.md#the_prefix_option)
- prepared statement → [arch.html](arch.md) [bytecodevtab.html](bytecodevtab.md) [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/bind_parameter_count.html](c3ref/bind_parameter_count.md) [c3ref/bind_parameter_name.html](c3ref/bind_parameter_name.md) [c3ref/busy_handler.html](c3ref/busy_handler.md) [c3ref/c_config_covering_index_scan.html#sqliteconfigmultithread](c3ref/c_config_covering_index_scan.md#sqliteconfigmultithread) [c3ref/c_config_covering_index_scan.html#sqliteconfigserialized](c3ref/c_config_covering_index_scan.md#sqliteconfigserialized) [c3ref/c_limit_attached.html#sqlitelimitworkerthreads](c3ref/c_limit_attached.md#sqlitelimitworkerthreads) [c3ref/c_trace.html#sqlitetraceprofile](c3ref/c_trace.md#sqlitetraceprofile) [c3ref/c_trace.html#sqlitetracerow](c3ref/c_trace.md#sqlitetracerow) [c3ref/c_trace.html#sqlitetracestmt](c3ref/c_trace.md#sqlitetracestmt) [c3ref/carray_bind.html](c3ref/carray_bind.md) [c3ref/clear_bindings.html](c3ref/clear_bindings.md) [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/column_count.html](c3ref/column_count.md) [c3ref/column_database_name.html](c3ref/column_database_name.md) [c3ref/column_decltype.html](c3ref/column_decltype.md) [c3ref/column_name.html](c3ref/column_name.md) [c3ref/data_count.html](c3ref/data_count.md) [c3ref/db_handle.html](c3ref/db_handle.md) [c3ref/expanded_sql.html](c3ref/expanded_sql.md) [c3ref/finalize.html](c3ref/finalize.md) [c3ref/next_stmt.html](c3ref/next_stmt.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/reset.html](c3ref/reset.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [c3ref/step.html](c3ref/step.md) [c3ref/stmt_busy.html](c3ref/stmt_busy.md) [c3ref/stmt_explain.html](c3ref/stmt_explain.md) [c3ref/stmt_readonly.html](c3ref/stmt_readonly.md) [c3ref/stmt_status.html](c3ref/stmt_status.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_bind_parameter_count](capi3ref.md#sqlite3_bind_parameter_count) [capi3ref.html#sqlite3_bind_parameter_name](capi3ref.md#sqlite3_bind_parameter_name) [capi3ref.html#sqlite3_busy_handler](capi3ref.md#sqlite3_busy_handler) [capi3ref.html#sqlite3_carray_bind](capi3ref.md#sqlite3_carray_bind) [capi3ref.html#sqlite3_clear_bindings](capi3ref.md#sqlite3_clear_bindings) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_column_count](capi3ref.md#sqlite3_column_count) [capi3ref.html#sqlite3_column_database_name](capi3ref.md#sqlite3_column_database_name) [capi3ref.html#sqlite3_column_decltype](capi3ref.md#sqlite3_column_decltype) [capi3ref.html#sqlite3_column_name](capi3ref.md#sqlite3_column_name) [capi3ref.html#sqlite3_data_count](capi3ref.md#sqlite3_data_count) [capi3ref.html#sqlite3_db_handle](capi3ref.md#sqlite3_db_handle) [capi3ref.html#sqlite3_expanded_sql](capi3ref.md#sqlite3_expanded_sql) [capi3ref.html#sqlite3_finalize](capi3ref.md#sqlite3_finalize) [capi3ref.html#sqlite3_next_stmt](capi3ref.md#sqlite3_next_stmt) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_reset](capi3ref.md#sqlite3_reset) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [capi3ref.html#sqlite3_stmt_busy](capi3ref.md#sqlite3_stmt_busy) [capi3ref.html#sqlite3_stmt_explain](capi3ref.md#sqlite3_stmt_explain) [capi3ref.html#sqlite3_stmt_readonly](capi3ref.md#sqlite3_stmt_readonly) [capi3ref.html#sqlite3_stmt_status](capi3ref.md#sqlite3_stmt_status) [capi3ref.html#sqliteconfigmultithread](capi3ref.md#sqliteconfigmultithread) [capi3ref.html#sqliteconfigserialized](capi3ref.md#sqliteconfigserialized) [capi3ref.html#sqlitelimitworkerthreads](capi3ref.md#sqlitelimitworkerthreads) [capi3ref.html#sqlitetraceprofile](capi3ref.md#sqlitetraceprofile) [capi3ref.html#sqlitetracerow](capi3ref.md#sqlitetracerow) [capi3ref.html#sqlitetracestmt](capi3ref.md#sqlitetracestmt) [changes.html#version_3_28_0](changes.md#version_3_28_0) [cintro.html](cintro.md) [compile.html#default_worker_threads](compile.md#default_worker_threads) [compile.html#max_worker_threads](compile.md#max_worker_threads) [compile.html#omit_autoreset](compile.md#omit_autoreset) [custombuild.html](custombuild.md) [faq.html#q15](faq.md#q15) [howitworks.html](howitworks.md) [lang_explain.html](lang_explain.md) [malloc.html](malloc.md) [malloc.html#nofrag](malloc.md#nofrag) [opcode.html](opcode.md) [optoverview.html#like_opt](optoverview.md#like_opt) [pragma.html#pragma_threads](pragma.md#pragma_threads) [releaselog/3_28_0.html](releaselog/3_28_0.md) [rescode.html#misuse](rescode.md#misuse) [rescode.html#schema](rescode.md#schema) [stmt.html](stmt.md) [threadsafe.html](threadsafe.md) [vfs.html](vfs.md) [vtablist.html](vtablist.md) [whybytecode.html](whybytecode.md)
- prepared statements → [35to36.html](35to36.md) [bytecodevtab.html](bytecodevtab.md) [c3ref/c_config_covering_index_scan.html#sqliteconfigmultithread](c3ref/c_config_covering_index_scan.md#sqliteconfigmultithread) [c3ref/c_config_covering_index_scan.html#sqliteconfigserialized](c3ref/c_config_covering_index_scan.md#sqliteconfigserialized) [c3ref/close.html](c3ref/close.md) [capi3ref.html#sqlite3_close](capi3ref.md#sqlite3_close) [capi3ref.html#sqliteconfigmultithread](capi3ref.md#sqliteconfigmultithread) [capi3ref.html#sqliteconfigserialized](capi3ref.md#sqliteconfigserialized) [changes.html#version_3_6_20](changes.md#version_3_6_20) [cintro.html](cintro.md) [compile.html#enable_explain_comments](compile.md#enable_explain_comments) [compile.html#rcmd](compile.md#rcmd) [compile.html#threadsafe](compile.md#threadsafe) [custombuild.html](custombuild.md) [datatype3.html#storageclasses](datatype3.md#storageclasses) [malloc.html](malloc.md) [malloc.html#lookaside](malloc.md#lookaside) [malloc.html#nofrag](malloc.md#nofrag) [oldnews.html](oldnews.md) [releaselog/3_6_20.html](releaselog/3_6_20.md) [stmt.html](stmt.md)
- PRIMARY KEY → [expridx.html](expridx.md) [fileformat2.html#ffschema](fileformat2.md#ffschema) [fileformat2.html#intschema](fileformat2.md#intschema) [fts5.html](fts5.md) [gencol.html#vgc\*](gencol.md#vgc*) [lang_conflict.html](lang_conflict.md) [rowidtable.html](rowidtable.md) [schematab.html](schematab.md) [sqldiff.html](sqldiff.md) [withoutrowid.html](withoutrowid.md)
- PRIMARY KEY constraint → [optoverview.html#autoindex](optoverview.md#autoindex) [pragma.html#pragma_index_info](pragma.md#pragma_index_info) [pragma.html#pragma_index_list](pragma.md#pragma_index_list) [pragma.html#pragma_index_xinfo](pragma.md#pragma_index_xinfo) [rescode.html#constraint_primarykey](rescode.md#constraint_primarykey)
- printf → [changes.html#version_3_8_3](changes.md#version_3_8_3) [lang_corefunc.html](lang_corefunc.md) [oldnews.html](oldnews.md) [releaselog/3_8_3.html](releaselog/3_8_3.md)
- printf SQL function → [c3ref/mprintf.html](c3ref/mprintf.md) [capi3ref.html#sqlite3_mprintf](capi3ref.md#sqlite3_mprintf) [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_38_0](changes.md#version_3_38_0) [compile.html#printf_precision_limit](compile.md#printf_precision_limit) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md) [security.html](security.md)
- professional support → [about.html](about.md) [support.html#prosupport](support.md#prosupport)
- protected sqlite3_value → [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/result_blob.html](c3ref/result_blob.md) [c3ref/value_blob.html](c3ref/value_blob.md) [c3ref/value_dup.html](c3ref/value_dup.md) [c3ref/vtab_in_first.html](c3ref/vtab_in_first.md) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [capi3ref.html#sqlite3_value_dup](capi3ref.md#sqlite3_value_dup) [capi3ref.html#sqlite3_vtab_in_first](capi3ref.md#sqlite3_vtab_in_first)
- PSOW → [atomiccommit.html#hardware](atomiccommit.md#hardware)
- public-domain → [index.html](index.md)
- push-down optimization → [changes.html#version_3_23_0](changes.md#version_3_23_0) [changes.html#version_3_35_0](changes.md#version_3_35_0) [changes.html#version_3_35_4](changes.md#version_3_35_4) [lang_with.html#mathint](lang_with.md#mathint) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- Q → [c3ref/mprintf.html](c3ref/mprintf.md) [capi3ref.html#sqlite3_mprintf](capi3ref.md#sqlite3_mprintf) [printf.html](printf.md)
- q → [c3ref/mprintf.html](c3ref/mprintf.md) [capi3ref.html#sqlite3_mprintf](capi3ref.md#sqlite3_mprintf) [printf.html](printf.md)
- Q and q conversions → [changes.html#version_3_50_0](changes.md#version_3_50_0) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- qbox → [changes.html#version_3_38_0](changes.md#version_3_38_0) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md)
- qualified-table-name → [lang_createtrigger.html](lang_createtrigger.md) [lang_delete.html](lang_delete.md) [lang_indexedby.html](lang_indexedby.md) [lang_update.html](lang_update.md)
- queries against graphs → [changes.html#version_3_34_0](changes.md#version_3_34_0) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md)
- query flattener → [changes.html#version_3_21_0](changes.md#version_3_21_0) [changes.html#version_3_22_0](changes.md#version_3_22_0) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_30_1](changes.md#version_3_30_1) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_22_0.html](releaselog/3_22_0.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_30_1.html](releaselog/3_30_1.md)
- query parameters with special meaning to SQLite → [c3ref/open.html#coreuriqueryparameters](c3ref/open.md#coreuriqueryparameters) [capi3ref.html#coreuriqueryparameters](capi3ref.md#coreuriqueryparameters)
- query planner → [arch.html](arch.md) [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_29_0](changes.md#version_3_29_0) [changes.html#version_3_49_0](changes.md#version_3_49_0) [compile.html#enable_stat4](compile.md#enable_stat4) [fullsql.html](fullsql.md) [queryplanner-ng.html](queryplanner-ng.md) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_29_0.html](releaselog/3_29_0.md) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md)
- query planner checklist → [lang_indexedby.html](lang_indexedby.md) [oldnews.html](oldnews.md) [optoverview.html#crossjoin](optoverview.md#crossjoin) [queryplanner-ng.html#hazards](queryplanner-ng.md#hazards)
- query planner stability guarantee → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigenableqpsg](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenableqpsg) [capi3ref.html#sqlitedbconfigenableqpsg](capi3ref.md#sqlitedbconfigenableqpsg) [changes.html#version_3_20_0](changes.md#version_3_20_0) [compile.html#enable_qpsg](compile.md#enable_qpsg) [compile.html#enable_stat4](compile.md#enable_stat4) [lang_analyze.html#statanal](lang_analyze.md#statanal) [oldnews.html](oldnews.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- query-time index → [changes.html#version_3_49_0](changes.md#version_3_49_0) [optoverview.html#flattening](optoverview.md#flattening) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md)
- query_only pragma → [changes.html#version_3_8_0](changes.md#version_3_8_0) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md)
- quick_check → [changes.html#version_3_7_9](changes.md#version_3_7_9) [releaselog/3_7_9.html](releaselog/3_7_9.md)
- quickstart → [c3ref/intro.html](c3ref/intro.md) [capi3ref.html](capi3ref.md)
- Quirks → [omitted.html](omitted.md)
- quote → [lang_corefunc.html](lang_corefunc.md) [lang_corefunc.html#unistr_quote](lang_corefunc.md#unistr_quote)
- quote SQL function → [nulinstr.html](nulinstr.md) [undoredo.html](undoredo.md)
- R-Tree extension → [changes.html#version_3_17_0](changes.md#version_3_17_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_22_0](changes.md#version_3_22_0) [changes.html#version_3_24_0](changes.md#version_3_24_0) [changes.html#version_3_8_2](changes.md#version_3_8_2) [changes.html#version_3_8_5](changes.md#version_3_8_5) [changes.html#version_3_8_6](changes.md#version_3_8_6) [changes.html#version_3_8_8](changes.md#version_3_8_8) [floatingpoint.html#fpapprox](floatingpoint.md#fpapprox) [geopoly.html](geopoly.md) [geopoly.html#ccw](geopoly.md#ccw) [howtocompile.html#dll](howtocompile.md#dll) [news.html](news.md) [releaselog/3_17_0.html](releaselog/3_17_0.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_22_0.html](releaselog/3_22_0.md) [releaselog/3_24_0.html](releaselog/3_24_0.md) [releaselog/3_8_2.html](releaselog/3_8_2.md) [releaselog/3_8_5.html](releaselog/3_8_5.md) [releaselog/3_8_6.html](releaselog/3_8_6.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md) [rescode.html#locked_vtab](rescode.md#locked_vtab)
- R-Trees → [fullsql.html](fullsql.md) [th3.html](th3.md) [vtab.html](vtab.md) [vtablist.html](vtablist.md)
- radians → [lang_mathfunc.html](lang_mathfunc.md)
- RAISE function → [changes.html#version_3_47_0](changes.md#version_3_47_0) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md) [rescode.html#constraint_trigger](rescode.md#constraint_trigger)
- raise-function → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createtrigger.html#raise](lang_createtrigger.md#raise) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- random → [c3ref/c_deterministic.html#sqliteinnocuous](c3ref/c_deterministic.md#sqliteinnocuous) [c3ref/create_function.html](c3ref/create_function.md) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [capi3ref.html#sqliteinnocuous](capi3ref.md#sqliteinnocuous) [deterministic.html](deterministic.md) [expridx.html](expridx.md) [lang_corefunc.html](lang_corefunc.md) [lang_createindex.html#indexexpr](lang_createindex.md#indexexpr)
- randomblob → [c3ref/c_deterministic.html#sqlitedeterministic](c3ref/c_deterministic.md#sqlitedeterministic) [capi3ref.html#sqlitedeterministic](capi3ref.md#sqlitedeterministic) [lang_corefunc.html](lang_corefunc.md)
- RANGE n FOLLOWING → [changes.html#version_3_28_0](changes.md#version_3_28_0) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- RANGE n PRECEDING → [changes.html#version_3_28_0](changes.md#version_3_28_0) [releaselog/3_28_0.html](releaselog/3_28_0.md) [windowfunctions.html#rangetype](windowfunctions.md#rangetype)
- RBU → [amalgamation.html](amalgamation.md) [changes.html#version_3_12_0](changes.md#version_3_12_0) [changes.html#version_3_30_0](changes.md#version_3_30_0) [changes.html#version_3_8_11](changes.md#version_3_8_11) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- RBU Database Contents → [rbu.html#rbu_updates](rbu.md#rbu_updates)
- RBU Database Tables → [rbu.html#rbu_updates](rbu.md#rbu_updates)
- RBU extension → [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_28_0](changes.md#version_3_28_0) [compile.html#enable_rbu](compile.md#enable_rbu) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- RBU FTS3/4 Tables → [rbu.html#database_tables](rbu.md#database_tables)
- RBU Update → [rbu.html](rbu.md)
- RBU Vacuum → [rbu.html](rbu.md)
- read-only WAL databases → [wal.html#advantages](wal.md#advantages)
- read_uncommitted → [sharedcache.html#dontuse](sharedcache.md#dontuse)
- read_uncommitted pragma → [isolation.html](isolation.md)
- recommended application security practices → [news.html](news.md)
- recommended by the US Library of Congress → [aff_short.html](aff_short.md) [appfileformat.html](appfileformat.md)
- recommended compile-time option → [changes.html#version_3_29_0](changes.md#version_3_29_0) [releaselog/3_29_0.html](releaselog/3_29_0.md)
- recommended compile-time options → [fasterthanfs.html](fasterthanfs.md)
- recommended storage format → [about.html](about.md) [famous.html](famous.md) [lang_altertable.html#altertableishard](lang_altertable.md#altertableishard) [lts.html](lts.md) [onefile.html](onefile.md)
- Recommended usage patterns for ANALYZE → [queryplanner-ng.html#qpstab](queryplanner-ng.md#qpstab)
- record format → [changes.html#version_3_21_0](changes.md#version_3_21_0) [fileformat2.html#stat4tab](fileformat2.md#stat4tab) [opcode.html#codes](opcode.md#codes) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- recovery → [walformat.html#locks](walformat.md#locks)
- recovery extension → [changes.html#version_3_40_0](changes.md#version_3_40_0) [changes.html#version_3_41_0](changes.md#version_3_41_0) [changes.html#version_3_41_2](changes.md#version_3_41_2) [news.html](news.md) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- recursive common table expression → [series.html](series.md)
- recursive common table expressions → [changes.html#version_3_34_0](changes.md#version_3_34_0) [cves.html#cvetab](cves.md#cvetab) [fullsql.html](fullsql.md) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md)
- recursive-cte → [lang_with.html#recursivecte](lang_with.md#recursivecte)
- recursive_triggers pragma → [lang_conflict.html](lang_conflict.md) [oldnews.html](oldnews.md)
- REGEXP → [changes.html#version_3_10_0](changes.md#version_3_10_0) [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_39_1](changes.md#version_3_39_1) [cli.html#miscfeatures](cli.md#miscfeatures) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md) [vtab.html#xfindfunction](vtab.md#xfindfunction)
- REINDEX → [changes.html#version_3_53_0](changes.md#version_3_53_0) [compile.html#omit_reindex](compile.md#omit_reindex) [dbhash.html](dbhash.md) [deterministic.html#dtexception](deterministic.md#dtexception) [fts3.html#\*fts4rebuidcmd](fts3.md#*fts4rebuidcmd) [fullsql.html](fullsql.md) [imposter.html](imposter.md) [lang.html](lang.md) [lang_naming.html](lang_naming.md) [oldnews.html](oldnews.md) [pragma.html#pragma_case_sensitive_like](pragma.md#pragma_case_sensitive_like) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [rescode.html#corrupt_index](rescode.md#corrupt_index) [staleexpridx.html](staleexpridx.md) [staleexpridx.html#selfheal](staleexpridx.md#selfheal)
- reindex-stmt → [lang_reindex.html](lang_reindex.md)
- RELEASE → [c3ref/stmt_readonly.html](c3ref/stmt_readonly.md) [capi3ref.html#sqlite3_stmt_readonly](capi3ref.md#sqlite3_stmt_readonly) [changes.html#version_3_7_12](changes.md#version_3_7_12) [fullsql.html](fullsql.md) [lang_transaction.html](lang_transaction.md) [releaselog/3_7_12.html](releaselog/3_7_12.md)
- release history → [versionnumbers.html](versionnumbers.md)
- release testing checklists → [qmplan.html](qmplan.md)
- release-stmt → [lang_savepoint.html](lang_savepoint.md)
- relfootprint → [compile.html](compile.md) [compile.html#omitfeatures](compile.md#omitfeatures)
- rename column → [lang_altertable.html#otheralter](lang_altertable.md#otheralter)
- rename table → [lang_altertable.html#caution](lang_altertable.md#caution) [lang_altertable.html#otheralter](lang_altertable.md#otheralter)
- REPLACE → [c3ref/changes.html](c3ref/changes.md) [capi3ref.html#sqlite3_changes](capi3ref.md#sqlite3_changes) [changes.html#version_3_16_2](changes.md#version_3_16_2) [changes.html#version_3_19_0](changes.md#version_3_19_0) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_7_7](changes.md#version_3_7_7) [dbpage.html](dbpage.md) [fullsql.html](fullsql.md) [lang.html](lang.md) [news.html](news.md) [oldnews.html](oldnews.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_7_7.html](releaselog/3_7_7.md)
- replace → [changes.html#version_3_19_0](changes.md#version_3_19_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [invalidutf.html](invalidutf.md) [lang_corefunc.html](lang_corefunc.md) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- replace SQL function → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- reserve bytes → [changes.html#version_3_53_0](changes.md#version_3_53_0) [cksumvfs.html](cksumvfs.md) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- reset the WAL → [walformat.html#locks](walformat.md#locks) [walformat.html#mxframe](walformat.md#mxframe) [walformat.html#nbackfill](walformat.md#nbackfill)
- result code → [c3ref/c_config_covering_index_scan.html#sqliteconfiglog](c3ref/c_config_covering_index_scan.md#sqliteconfiglog) [c3ref/c_fail.html](c3ref/c_fail.md) [c3ref/errcode.html](c3ref/errcode.md) [capi3ref.html#SQLITE_FAIL](capi3ref.md#SQLITE_FAIL) [capi3ref.html#sqlite3_errcode](capi3ref.md#sqlite3_errcode) [capi3ref.html#sqliteconfiglog](capi3ref.md#sqliteconfiglog)
- result code definitions → [rescode.html#pve](rescode.md#pve)
- result codes → [c3ref/c_abort_rollback.html](c3ref/c_abort_rollback.md) [c3ref/intro.html](c3ref/intro.md) [c3ref/step.html](c3ref/step.md) [capi3ref.html#SQLITE_ABORT_ROLLBACK](capi3ref.md#SQLITE_ABORT_ROLLBACK) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step)
- result-column → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- RETURNING → [c3ref/reset.html](c3ref/reset.md) [capi3ref.html#sqlite3_reset](capi3ref.md#sqlite3_reset) [changes.html#version_3_35_0](changes.md#version_3_35_0) [changes.html#version_3_35_4](changes.md#version_3_35_4) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
- RETURNING clause → [lang.html](lang.md) [lang_delete.html](lang_delete.md)
- returning-clause → [lang_createtrigger.html](lang_createtrigger.md) [lang_delete.html](lang_delete.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_update.html](lang_update.md)
- reverse_unordered_selects pragma → [changes.html#version_3_6_12](changes.md#version_3_6_12) [releaselog/3_6_12.html](releaselog/3_6_12.md)
- RIGHT and FULL OUTER JOIN → [changes.html#version_3_39_0](changes.md#version_3_39_0) [releaselog/3_39_0.html](releaselog/3_39_0.md) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- Robson proof → [malloc.html#memstatus](malloc.md#memstatus) [malloc.html#memsys5](malloc.md#memsys5) [malloc.html#nofrag](malloc.md#nofrag) [malloc.html#pagecache](malloc.md#pagecache)
- ROLLBACK → [c3ref/c_txn_none.html#sqlitetxnread](c3ref/c_txn_none.md#sqlitetxnread) [c3ref/c_txn_none.html#sqlitetxnwrite](c3ref/c_txn_none.md#sqlitetxnwrite) [c3ref/commit_hook.html](c3ref/commit_hook.md) [c3ref/get_autocommit.html](c3ref/get_autocommit.md) [c3ref/stmt_readonly.html](c3ref/stmt_readonly.md) [capi3ref.html#sqlite3_commit_hook](capi3ref.md#sqlite3_commit_hook) [capi3ref.html#sqlite3_get_autocommit](capi3ref.md#sqlite3_get_autocommit) [capi3ref.html#sqlite3_stmt_readonly](capi3ref.md#sqlite3_stmt_readonly) [capi3ref.html#sqlitetxnread](capi3ref.md#sqlitetxnread) [capi3ref.html#sqlitetxnwrite](capi3ref.md#sqlitetxnwrite) [changes.html#version_3_6_5](changes.md#version_3_6_5) [changes.html#version_3_7_11](changes.md#version_3_7_11) [changes.html#version_3_8_6](changes.md#version_3_8_6) [changes.html#version_3_8_7_2](changes.md#version_3_8_7_2) [foreignkeys.html#fk_enable](foreignkeys.md#fk_enable) [fullsql.html](fullsql.md) [isolation.html](isolation.md) [lang.html](lang.md) [lang_savepoint.html](lang_savepoint.md) [oldnews.html](oldnews.md) [pragma.html#pragma_journal_mode](pragma.md#pragma_journal_mode) [releaselog/3_6_5.html](releaselog/3_6_5.md) [releaselog/3_7_11.html](releaselog/3_7_11.md) [releaselog/3_8_6.html](releaselog/3_8_6.md) [releaselog/3_8_7_2.html](releaselog/3_8_7_2.md) [rescode.html#abort](rescode.md#abort) [rescode.html#abort_rollback](rescode.md#abort_rollback) [wal.html#advantages](wal.md#advantages)
- rollback journal → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntljournalpointer](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntljournalpointer) [capi3ref.html#sqlitefcntljournalpointer](capi3ref.md#sqlitefcntljournalpointer) [compile.html#default_journal_size_limit](compile.md#default_journal_size_limit) [compile.html#enable_batch_atomic_write](compile.md#enable_batch_atomic_write) [errlog.html](errlog.md) [news.html](news.md) [pragma.html#pragma_journal_size_limit](pragma.md#pragma_journal_size_limit) [pragma.html#pragma_synchronous](pragma.md#pragma_synchronous) [rescode.html#readonly_dbmoved](rescode.md#readonly_dbmoved) [shortnames.html](shortnames.md) [shortnames.html#db83corrupt](shortnames.md#db83corrupt) [wal.html](wal.md)
- rollback-stmt → [lang_savepoint.html](lang_savepoint.md) [lang_transaction.html](lang_transaction.md)
- round → [changes.html#version_3_29_0](changes.md#version_3_29_0) [lang_corefunc.html](lang_corefunc.md) [releaselog/3_29_0.html](releaselog/3_29_0.md)
- row value → [changes.html#version_3_15_2](changes.md#version_3_15_2) [changes.html#version_3_23_0](changes.md#version_3_23_0) [fullsql.html](fullsql.md) [lang_expr.html#in_op](lang_expr.md#in_op) [lang_expr.html#subq](lang_expr.md#subq) [lang_update.html](lang_update.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- row value IN operator → [changes.html#version_3_38_1](changes.md#version_3_38_1) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md)
- row values → [changes.html#version_3_15_0](changes.md#version_3_15_0) [changes.html#version_3_15_1](changes.md#version_3_15_1) [changes.html#version_3_16_1](changes.md#version_3_16_1) [changes.html#version_3_23_0](changes.md#version_3_23_0) [news.html](news.md) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- ROWID → [autoinc.html](autoinc.md) [c3ref/last_insert_rowid.html](c3ref/last_insert_rowid.md) [c3ref/randomness.html](c3ref/randomness.md) [capi3ref.html#sqlite3_last_insert_rowid](capi3ref.md#sqlite3_last_insert_rowid) [capi3ref.html#sqlite3_randomness](capi3ref.md#sqlite3_randomness) [compile.html#enable_sorter_references](compile.md#enable_sorter_references) [gencol.html#vgc\*](gencol.md#vgc*) [imposter.html](imposter.md) [lang_corefunc.html#last_insert_rowid](lang_corefunc.md#last_insert_rowid) [lang_vacuum.html#howvacuumworks](lang_vacuum.md#howvacuumworks) [quirks.html](quirks.md) [rbu.html#database_tables](rbu.md#database_tables) [vtab.html#worid](vtab.md#worid)
- rowid → [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/last_insert_rowid.html](c3ref/last_insert_rowid.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/table_column_metadata.html](c3ref/table_column_metadata.md) [c3ref/update_hook.html](c3ref/update_hook.md) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_last_insert_rowid](capi3ref.md#sqlite3_last_insert_rowid) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite) [capi3ref.html#sqlite3_table_column_metadata](capi3ref.md#sqlite3_table_column_metadata) [capi3ref.html#sqlite3_update_hook](capi3ref.md#sqlite3_update_hook) [changes.html#version_3_19_0](changes.md#version_3_19_0) [changes.html#version_3_36_0](changes.md#version_3_36_0) [changes.html#version_3_8_7_1](changes.md#version_3_8_7_1) [fileformat2.html##sqltab](fileformat2.md##sqltab) [fileformat2.html#btypes](fileformat2.md#btypes) [fileformat2.html#varint](fileformat2.md#varint) [foreignkeys.html#parentchild](foreignkeys.md#parentchild) [lang_createtable.html#createtabas](lang_createtable.md#createtabas) [lang_createtable.html#primkeyconst](lang_createtable.md#primkeyconst) [lang_expr.html#in_op](lang_expr.md#in_op) [lang_indexedby.html](lang_indexedby.md) [optoverview.html#covidx](optoverview.md#covidx) [pragma.html#pragma_foreign_key_check](pragma.md#pragma_foreign_key_check) [pragma.html#pragma_index_info](pragma.md#pragma_index_info) [pragma.html#pragma_index_xinfo](pragma.md#pragma_index_xinfo) [queryplanner.html#searching](queryplanner.md#searching) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md) [releaselog/3_36_0.html](releaselog/3_36_0.md) [releaselog/3_8_7_1.html](releaselog/3_8_7_1.md) [rescode.html#constraint_rowid](rescode.md#constraint_rowid) [rescode.html#mismatch](rescode.md#mismatch) [rowidtable.html](rowidtable.md) [sqldiff.html](sqldiff.md) [stricttables.html](stricttables.md) [vtab.html#xrowid](vtab.md#xrowid) [vtab.html#xupdate](vtab.md#xupdate) [withoutrowid.html](withoutrowid.md) [withoutrowid.html#bene](withoutrowid.md#bene)
- rowid table → [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/update_hook.html](c3ref/update_hook.md) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite) [capi3ref.html#sqlite3_update_hook](capi3ref.md#sqlite3_update_hook) [changes.html#version_3_13_0](changes.md#version_3_13_0) [compile.html#enable_preupdate_hook](compile.md#enable_preupdate_hook) [releaselog/3_13_0.html](releaselog/3_13_0.md)
- rowid tables → [sessionintro.html](sessionintro.md) [unionvtab.html](unionvtab.md)
- RTREE → [aff_short.html](aff_short.md) [amalgamation.html](amalgamation.md) [changes.html#version_3_44_0](changes.md#version_3_44_0) [changes.html#version_3_7_13](changes.md#version_3_7_13) [changes.html#version_3_7_16](changes.md#version_3_7_16) [changes.html#version_3_7_7](changes.md#version_3_7_7) [oldnews.html](oldnews.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md) [releaselog/3_7_13.html](releaselog/3_7_13.md) [releaselog/3_7_16.html](releaselog/3_7_16.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md) [releaselog/3_7_7.html](releaselog/3_7_7.md) [vtab.html#xintegrity](vtab.md#xintegrity) [vtab.html#xshadowname](vtab.md#xshadowname)
- rtree → [35to36.html](35to36.md) [changes.html#version_3_6_1](changes.md#version_3_6_1) [changes.html#version_3_7_12](changes.md#version_3_7_12) [compile.html#enable_rtree](compile.md#enable_rtree) [fts5.html#fts5shadowtables](fts5.md#fts5shadowtables) [releaselog/3_6_0.html](releaselog/3_6_0.md) [releaselog/3_7_12.html](releaselog/3_7_12.md) [sqldiff.html](sqldiff.md)
- rtree shadow tables → [vtab.html#xshadowname](vtab.md#xshadowname)
- rtreecheck → [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_22_0.html](releaselog/3_22_0.md)
- rtrim → [lang_corefunc.html](lang_corefunc.md)
- rules for determining column affinity → [lang_expr.html#castexpr](lang_expr.md#castexpr)
- Run-Time Loadable Extensions → [cli.html#dotload](cli.md#dotload)
- running ANALYZE via PRAGMA optimize → [changes.html#version_3_46_0](changes.md#version_3_46_0) [releaselog/3_46_0.html](releaselog/3_46_0.md) [releaselog/3_46_1.html](releaselog/3_46_1.md)
- safe command-line option → [changes.html#version_3_40_1](changes.md#version_3_40_1) [news.html](news.md) [releaselog/3_40_1.html](releaselog/3_40_1.md)
- SAVEPOINT → [c3ref/stmt_readonly.html](c3ref/stmt_readonly.md) [capi3ref.html#sqlite3_stmt_readonly](capi3ref.md#sqlite3_stmt_readonly) [changes.html#version_3_12_1](changes.md#version_3_12_1) [changes.html#version_3_13_0](changes.md#version_3_13_0) [changes.html#version_3_37_2](changes.md#version_3_37_2) [changes.html#version_3_6_8](changes.md#version_3_6_8) [changes.html#version_3_7_7](changes.md#version_3_7_7) [changes.html#version_3_7_9](changes.md#version_3_7_9) [dbpage.html](dbpage.md) [foreignkeys.html#fk_enable](foreignkeys.md#fk_enable) [fullsql.html](fullsql.md) [howtocorrupt.html#svptbug](howtocorrupt.md#svptbug) [lang.html](lang.md) [lang_transaction.html](lang_transaction.md) [news.html](news.md) [oldnews.html](oldnews.md) [pragma.html#pragma_foreign_keys](pragma.md#pragma_foreign_keys) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_37_2.html](releaselog/3_37_2.md) [releaselog/3_6_8.html](releaselog/3_6_8.md) [releaselog/3_7_7.html](releaselog/3_7_7.md) [releaselog/3_7_9.html](releaselog/3_7_9.md) [session.html#SQLITE_CHANGESETAPPLY_FKNOACTION](session.md#SQLITE_CHANGESETAPPLY_FKNOACTION) [session/c_changesetapply_fknoaction.html](session/c_changesetapply_fknoaction.md)
- SAVEPOINT bug → [changes.html#version_3_37_2](changes.md#version_3_37_2) [news.html](news.md) [releaselog/3_37_2.html](releaselog/3_37_2.md)
- savepoint-stmt → [lang_savepoint.html](lang_savepoint.md)
- scalar functions → [lang_aggfunc.html#aggorderby](lang_aggfunc.md#aggorderby) [lang_mathfunc.html](lang_mathfunc.md) [windowfunctions.html](windowfunctions.md)
- scanstatus options → [c3ref/stmt_scanstatus.html](c3ref/stmt_scanstatus.md) [capi3ref.html#sqlite3_stmt_scanstatus](capi3ref.md#sqlite3_stmt_scanstatus)
- schema format → [fileformat2.html#serialtype](fileformat2.md#serialtype)
- schema format number → [changes.html#version_3_7_10](changes.md#version_3_7_10) [compile.html#default_file_format](compile.md#default_file_format) [lang_createindex.html#descidx](lang_createindex.md#descidx) [oldnews.html](oldnews.md) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- schema storage → [schematab.html](schematab.md)
- schema_version → [compile.html#omit_schema_version_pragmas](compile.md#omit_schema_version_pragmas)
- schema_version pragma → [pragma.html#pragma_user_version](pragma.md#pragma_user_version)
- search application tips → [fts3.html#matchinfo-b](fts3.md#matchinfo-b)
- secure_delete pragma → [changes.html#version_3_6_23](changes.md#version_3_6_23) [compile.html#secure_delete](compile.md#secure_delete) [oldnews.html](oldnews.md) [releaselog/3_6_23.html](releaselog/3_6_23.md)
- security → [hirely.html](hirely.md)
- segment btree → [fts3.html#fts4](fts3.md#fts4)
- SELECT → [35to36.html](35to36.md) [c3ref/c_limit_attached.html#sqlitelimitcolumn](c3ref/c_limit_attached.md#sqlitelimitcolumn) [c3ref/column_database_name.html](c3ref/column_database_name.md) [c3ref/column_decltype.html](c3ref/column_decltype.md) [c3ref/column_name.html](c3ref/column_name.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [c3ref/stmt_readonly.html](c3ref/stmt_readonly.md) [capi3ref.html#sqlite3_column_database_name](capi3ref.md#sqlite3_column_database_name) [capi3ref.html#sqlite3_column_decltype](capi3ref.md#sqlite3_column_decltype) [capi3ref.html#sqlite3_column_name](capi3ref.md#sqlite3_column_name) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlite3_stmt_readonly](capi3ref.md#sqlite3_stmt_readonly) [capi3ref.html#sqlitelimitcolumn](capi3ref.md#sqlitelimitcolumn) [changes.html#version_3_8_3](changes.md#version_3_8_3) [changes.html#version_3_9_0](changes.md#version_3_9_0) [compile.html#omit_compound_select](compile.md#omit_compound_select) [compile.html#reverse_unordered_selects](compile.md#reverse_unordered_selects) [datatype3.html#affcompoundview](datatype3.md#affcompoundview) [datatype3.html#affview](datatype3.md#affview) [datatype3.html#colrules](datatype3.md#colrules) [dbpage.html](dbpage.md) [fts3.html#simple_fts_queries](fts3.md#simple_fts_queries) [isolation.html](isolation.md) [lang.html](lang.md) [lang_analyze.html#statanal](lang_analyze.md#statanal) [lang_createview.html](lang_createview.md) [lang_expr.html#cosub](lang_expr.md#cosub) [lang_expr.html#subq](lang_expr.md#subq) [lang_indexedby.html](lang_indexedby.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_transaction.html#immediate](lang_transaction.md#immediate) [lang_upsert.html#parseambig](lang_upsert.md#parseambig) [lang_with.html](lang_with.md) [lang_with.html#mathint](lang_with.md#mathint) [limits.html#max_compound_select](limits.md#max_compound_select) [oldnews.html](oldnews.md) [pragma.html](pragma.md) [pragma.html#pragfunc](pragma.md#pragfunc) [pragma.html#pragma_full_column_names](pragma.md#pragma_full_column_names) [pragma.html#pragma_reverse_unordered_selects](pragma.md#pragma_reverse_unordered_selects) [pragma.html#pragma_short_column_names](pragma.md#pragma_short_column_names) [releaselog/3_8_3.html](releaselog/3_8_3.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md) [unionvtab.html](unionvtab.md) [vtab.html#hiddencol](vtab.md#hiddencol) [vtab.html#tabfunc2](vtab.md#tabfunc2)
- SELECT statement → [changes.html#version_3_39_0](changes.md#version_3_39_0) [releaselog/3_39_0.html](releaselog/3_39_0.md) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- select-core → [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect)
- select-stmt → [changes.html#version_3_35_3](changes.md#version_3_35_3) [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [lang_with.html#recursivecte](lang_with.md#recursivecte) [partialindex.html](partialindex.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- self-contained → [index.html](index.md)
- self-healing index → [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- serial types → [fileformat2.html#schemaformat](fileformat2.md#schemaformat)
- series → [vtablist.html](vtablist.md)
- server-side database → [whentouse.html#dbcklst](whentouse.md#dbcklst)
- serverless → [different.html#serverless](different.md#serverless) [howitworks.html](howitworks.md) [quirks.html](quirks.md)
- session → [amalgamation.html](amalgamation.md) [changes.html#version_3_13_0](changes.md#version_3_13_0) [changes.html#version_3_26_0](changes.md#version_3_26_0) [compile.html#enable_preupdate_hook](compile.md#enable_preupdate_hook) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_26_0.html](releaselog/3_26_0.md) [session.html#sqlite3_session](session.md#sqlite3_session) [session/intro.html](session/intro.md) [session/session.html](session/session.md)
- session extension → [changes.html#version_3_17_0](changes.md#version_3_17_0) [changes.html#version_3_42_0](changes.md#version_3_42_0) [changes.html#version_3_49_0](changes.md#version_3_49_0) [changes.html#version_3_51_0](changes.md#version_3_51_0) [changes.html#version_3_53_0](changes.md#version_3_53_0) [compile.html#enable_session](compile.md#enable_session) [cves.html#cvetab](cves.md#cvetab) [releaselog/3_17_0.html](releaselog/3_17_0.md) [releaselog/3_42_0.html](releaselog/3_42_0.md) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [session.html](session.md) [session/intro.html](session/intro.md) [sqldiff.html](sqldiff.md)
- Session Extension C-language Interface → [sessionintro.html](sessionintro.md)
- shadow tables → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigdefensive](c3ref/c_dbconfig_defensive.md#sqlitedbconfigdefensive) [capi3ref.html#sqlitedbconfigdefensive](capi3ref.md#sqlitedbconfigdefensive) [changes.html#version_3_26_0](changes.md#version_3_26_0) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_39_4](changes.md#version_3_39_4) [cves.html#cvetab](cves.md#cvetab) [fileformat2.html#btypes](fileformat2.md#btypes) [fts5.html#fts5shadowtables](fts5.md#fts5shadowtables) [pragma.html#pragma_secure_delete](pragma.md#pragma_secure_delete) [pragma.html#pragma_table_list](pragma.md#pragma_table_list) [releaselog/3_26_0.html](releaselog/3_26_0.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_39_4.html](releaselog/3_39_4.md) [rtree.html](rtree.md) [rtree.html#xshadow](rtree.md#xshadow) [vtab.html#xrename](vtab.md#xrename)
- shared cache → [c3ref/open.html](c3ref/open.md) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [changes.html#version_3_7_13](changes.md#version_3_7_13) [changes.html#version_3_7_15](changes.md#version_3_7_15) [compile.html#rcmd](compile.md#rcmd) [inmemorydb.html#sharedmemdb](inmemorydb.md#sharedmemdb) [isolation.html](isolation.md) [pragma.html#pragma_data_version](pragma.md#pragma_data_version) [releaselog/3_7_13.html](releaselog/3_7_13.md) [releaselog/3_7_15.html](releaselog/3_7_15.md) [rescode.html#busy](rescode.md#busy) [rescode.html#locked](rescode.md#locked)
- shared cache mode → [c3ref/backup_finish.html#sqlite3backuppagecount](c3ref/backup_finish.md#sqlite3backuppagecount) [c3ref/c_dbstatus_options.html#sqlitedbstatusschemaused](c3ref/c_dbstatus_options.md#sqlitedbstatusschemaused) [capi3ref.html#sqlite3backuppagecount](capi3ref.md#sqlite3backuppagecount) [capi3ref.html#sqlitedbstatusschemaused](capi3ref.md#sqlitedbstatusschemaused) [changes.html#version_3_6_17](changes.md#version_3_6_17) [changes.html#version_3_6_18](changes.md#version_3_6_18) [changes.html#version_3_7_15](changes.md#version_3_7_15) [changes.html#version_3_7_17](changes.md#version_3_7_17) [changes.html#version_3_8_7_3](changes.md#version_3_8_7_3) [changes.html#version_3_8_8](changes.md#version_3_8_8) [compile.html#omit_shared_cache](compile.md#omit_shared_cache) [isolation.html](isolation.md) [lang_detach.html](lang_detach.md) [oldnews.html](oldnews.md) [releaselog/3_6_17.html](releaselog/3_6_17.md) [releaselog/3_6_18.html](releaselog/3_6_18.md) [releaselog/3_7_15.html](releaselog/3_7_15.md) [releaselog/3_7_17.html](releaselog/3_7_17.md) [releaselog/3_8_7_3.html](releaselog/3_8_7_3.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md) [rescode.html#locked_sharedcache](rescode.md#locked_sharedcache) [uri.html#uricache](uri.md#uricache) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab)
- shared lock → [c3ref/backup_finish.html#sqlite3backupstep](c3ref/backup_finish.md#sqlite3backupstep) [capi3ref.html#sqlite3backupstep](capi3ref.md#sqlite3backupstep)
- shims → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntltrace](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntltrace) [capi3ref.html#sqlitefcntltrace](capi3ref.md#sqlitefcntltrace)
- shm file → [changes.html#version_3_33_0](changes.md#version_3_33_0) [changes.html#version_3_43_0](changes.md#version_3_43_0) [compile.html#omit_seh](compile.md#omit_seh) [releaselog/3_33_0.html](releaselog/3_33_0.md) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md) [rescode.html#ioerr_shmsize](rescode.md#ioerr_shmsize)
- short filenames → [changes.html#version_3_7_7](changes.md#version_3_7_7) [releaselog/3_7_7.html](releaselog/3_7_7.md)
- short_column_names → [pragma.html#pragma_full_column_names](pragma.md#pragma_full_column_names)
- shrink_memory pragma → [changes.html#version_3_7_10](changes.md#version_3_7_10) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- sign → [lang_corefunc.html](lang_corefunc.md)
- signed-number → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [pragma.html#syntax](pragma.md#syntax) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- simple fts queries → [fts3.html#fts4](fts3.md#fts4) [fts3.html#full_text_index_queries](fts3.md#full_text_index_queries) [fts3.html#termprefix](fts3.md#termprefix)
- simple SELECT → [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#limitoffset](lang_select.md#limitoffset) [lang_select.html#orderby](lang_select.md#orderby)
- simple-function-invocation → [lang_corefunc.html](lang_corefunc.md) [lang_expr.html#\*funcinexpr](lang_expr.md#*funcinexpr)
- simple-select-stmt → [lang_select.html#simpleselect](lang_select.md#simpleselect)
- sin → [lang_mathfunc.html](lang_mathfunc.md)
- sinh → [lang_mathfunc.html](lang_mathfunc.md)
- skip-scan → [changes.html#version_3_8_7](changes.md#version_3_8_7) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- skip-scan optimization → [changes.html#version_3_8_11](changes.md#version_3_8_11) [changes.html#version_3_8_2](changes.md#version_3_8_2) [changes.html#version_3_8_4_1](changes.md#version_3_8_4_1) [changes.html#version_3_8_6](changes.md#version_3_8_6) [changes.html#version_3_8_8](changes.md#version_3_8_8) [fileformat2.html#stat1tab](fileformat2.md#stat1tab) [oldnews.html](oldnews.md) [optoverview.html#where_clause](optoverview.md#where_clause) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [releaselog/3_8_2.html](releaselog/3_8_2.md) [releaselog/3_8_4_1.html](releaselog/3_8_4_1.md) [releaselog/3_8_4_2.html](releaselog/3_8_4_2.md) [releaselog/3_8_4_3.html](releaselog/3_8_4_3.md) [releaselog/3_8_6.html](releaselog/3_8_6.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- snapshot → [c3ref/snapshot_open.html](c3ref/snapshot_open.md) [capi3ref.html#sqlite3_snapshot_open](capi3ref.md#sqlite3_snapshot_open)
- snippet → [bindptr.html](bindptr.md) [bindptr.html#ptrtyp](bindptr.md#ptrtyp) [cves.html#cvetab](cves.md#cvetab) [fts3.html#appendix_a](fts3.md#appendix_a) [fts3.html#simple_fts_queries](fts3.md#simple_fts_queries)
- soft_heap_limit pragma → [changes.html#version_3_8_1](changes.md#version_3_8_1) [pragma.html#pragma_hard_heap_limit](pragma.md#pragma_hard_heap_limit) [releaselog/3_8_1.html](releaselog/3_8_1.md)
- solve Sudoku puzzles → [oldnews.html](oldnews.md)
- sort order → [lang_createindex.html#descidx](lang_createindex.md#descidx)
- sorting → [eqp.html#or-opt](eqp.md#or-opt)
- soundex → [lang_corefunc.html](lang_corefunc.md)
- soundex SQL function → [compile.html#soundex](compile.md#soundex)
- spellfix1 → [changes.html#version_3_11_1](changes.md#version_3_11_1) [changes.html#version_3_7_16](changes.md#version_3_7_16) [changes.html#version_3_8_11](changes.md#version_3_8_11) [changes.html#version_3_8_3](changes.md#version_3_8_3) [changes.html#version_3_8_7](changes.md#version_3_8_7) [news.html](news.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_7_16.html](releaselog/3_7_16.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [releaselog/3_8_3.html](releaselog/3_8_3.md) [releaselog/3_8_7.html](releaselog/3_8_7.md) [vtablist.html](vtablist.md)
- SQL Archive → [compile.html#have_zlib](compile.md#have_zlib)
- SQL fuzzing → [changes.html#version_3_8_10](changes.md#version_3_8_10) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md)
- SQL keywords → [lang.html](lang.md)
- SQL Logic Tests → [qmplan.html](qmplan.md)
- SQL parameter → [c3ref/bind_parameter_name.html](c3ref/bind_parameter_name.md) [c3ref/result_blob.html](c3ref/result_blob.md) [capi3ref.html#sqlite3_bind_parameter_name](capi3ref.md#sqlite3_bind_parameter_name) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob)
- SQL parameters → [c3ref/bind_parameter_count.html](c3ref/bind_parameter_count.md) [capi3ref.html#sqlite3_bind_parameter_count](capi3ref.md#sqlite3_bind_parameter_count)
- sql-stmt → [lang.html](lang.md) [lang_explain.html](lang_explain.md)
- sql-stmt-list → [lang.html](lang.md)
- sqldiff → [changes.html#version_3_10_0](changes.md#version_3_10_0) [changes.html#version_3_14_1](changes.md#version_3_14_1) [changes.html#version_3_35_2](changes.md#version_3_35_2) [changes.html#version_3_47_0](changes.md#version_3_47_0) [rbu.html#sqldiff](rbu.md#sqldiff) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md)
- sqldiff --rbu → [rbu.html#database_contents](rbu.md#database_contents)
- sqldiff.exe → [changes.html#version_3_8_10](changes.md#version_3_8_10) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md)
- SQLite amalgamation source file → [lang_mathfunc.html](lang_mathfunc.md)
- SQLite Archive → [appfileformat.html](appfileformat.md) [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_22_0.html](releaselog/3_22_0.md) [whentouse.html#container](whentouse.md#container) [whynotgit.html](whynotgit.md)
- SQLite Archive files → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [whentouse.html#container](whentouse.md#container)
- SQLite Archive format → [cli.html#sqlar](cli.md#sqlar)
- SQLite Archive smaller than ZIP → [appfileformat.html](appfileformat.md)
- SQLite Consortium → [oldnews.html](oldnews.md)
- SQLite database file format → [lang_altertable.html#altertableishard](lang_altertable.md#altertableishard)
- SQLite extension → [c3ref/auto_extension.html](c3ref/auto_extension.md) [c3ref/load_extension.html](c3ref/load_extension.md) [capi3ref.html#sqlite3_auto_extension](capi3ref.md#sqlite3_auto_extension) [capi3ref.html#sqlite3_load_extension](capi3ref.md#sqlite3_load_extension)
- SQLite extensions → [lang_corefunc.html#load_extension](lang_corefunc.md#load_extension)
- SQLite query planner → [cli.html#expert](cli.md#expert) [howitworks.html](howitworks.md) [lang_indexedby.html](lang_indexedby.md) [queryplanner.html](queryplanner.md)
- SQLite Shared-Cache Mode → [c3ref/enable_shared_cache.html](c3ref/enable_shared_cache.md) [c3ref/unlock_notify.html](c3ref/unlock_notify.md) [capi3ref.html#sqlite3_enable_shared_cache](capi3ref.md#sqlite3_enable_shared_cache) [capi3ref.html#sqlite3_unlock_notify](capi3ref.md#sqlite3_unlock_notify) [pragma.html#pragma_read_uncommitted](pragma.md#pragma_read_uncommitted)
- SQLite source code repositories → [cli.html#fileio](cli.md#fileio)
- sqlite3 → [backup.html](backup.md) [c3ref/close.html](c3ref/close.md) [c3ref/intro.html](c3ref/intro.md) [c3ref/objlist.html](c3ref/objlist.md) [c3ref/open.html](c3ref/open.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_close](capi3ref.md#sqlite3_close) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [cintro.html](cintro.md) [isolation.html](isolation.md) [sharedcache.html#dontuse](sharedcache.md#dontuse) [tclsqlite.html#trace_v2](tclsqlite.md#trace_v2) [unlock_notify.html](unlock_notify.md) [windowfunctions.html#udfwinfunc](windowfunctions.md#udfwinfunc)
- sqlite3.exe → [cves.html#cvetab](cves.md#cvetab)
- sqlite3.exe command-line shell → [sqlar.html#cltools](sqlar.md#cltools) [whentouse.html#container](whentouse.md#container)
- sqlite3_aggregate_context → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [cintro.html](cintro.md) [windowfunctions.html#udfwinfunc](windowfunctions.md#udfwinfunc)
- sqlite3_aggregate_count → [compile.html#omit_deprecated](compile.md#omit_deprecated)
- sqlite3_analyzer → [changes.html#version_3_47_0](changes.md#version_3_47_0) [changes.html#version_3_48_0](changes.md#version_3_48_0) [news.html](news.md) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md) [releaselog/3_48_0.html](releaselog/3_48_0.md) [vtablist.html](vtablist.md)
- sqlite3_analyzer.exe → [changes.html#version_3_20_0](changes.md#version_3_20_0) [dbstat.html](dbstat.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- sqlite3_api_routines → [c3ref/objlist.html](c3ref/objlist.md) [capi3ref.html](capi3ref.md)
- sqlite3_auto_extension → [c3ref/cancel_auto_extension.html](c3ref/cancel_auto_extension.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/reset_auto_extension.html](c3ref/reset_auto_extension.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_cancel_auto_extension](capi3ref.md#sqlite3_cancel_auto_extension) [capi3ref.html#sqlite3_reset_auto_extension](capi3ref.md#sqlite3_reset_auto_extension) [changes.html#version_3_6_7](changes.md#version_3_6_7) [loadext.html#persist](loadext.md#persist) [loadext.html#statext](loadext.md#statext) [releaselog/3_6_7.html](releaselog/3_6_7.md)
- sqlite3_autovacuum_pages → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_37_0](changes.md#version_3_37_0) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md)
- sqlite3_backup → [backup.html](backup.md) [c3ref/backup_finish.html#sqlite3backupfinish](c3ref/backup_finish.md#sqlite3backupfinish) [c3ref/backup_finish.html#sqlite3backupinit](c3ref/backup_finish.md#sqlite3backupinit) [c3ref/backup_finish.html#sqlite3backuppagecount](c3ref/backup_finish.md#sqlite3backuppagecount) [c3ref/backup_finish.html#sqlite3backupstep](c3ref/backup_finish.md#sqlite3backupstep) [c3ref/close.html](c3ref/close.md) [c3ref/objlist.html](c3ref/objlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_close](capi3ref.md#sqlite3_close) [capi3ref.html#sqlite3backupfinish](capi3ref.md#sqlite3backupfinish) [capi3ref.html#sqlite3backupinit](capi3ref.md#sqlite3backupinit) [capi3ref.html#sqlite3backuppagecount](capi3ref.md#sqlite3backuppagecount) [capi3ref.html#sqlite3backupstep](capi3ref.md#sqlite3backupstep) [changes.html#version_3_6_14_1](changes.md#version_3_6_14_1) [oldnews.html](oldnews.md) [releaselog/3_6_14_1.html](releaselog/3_6_14_1.md)
- sqlite3_backup_finish → [backup.html](backup.md) [c3ref/backup.html](c3ref/backup.md) [c3ref/close.html](c3ref/close.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_backup](capi3ref.md#sqlite3_backup) [capi3ref.html#sqlite3_close](capi3ref.md#sqlite3_close)
- sqlite3_backup_init → [backup.html](backup.md) [c3ref/backup.html](c3ref/backup.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_backup](capi3ref.md#sqlite3_backup) [changes.html#version_3_6_11](changes.md#version_3_6_11) [releaselog/3_6_11.html](releaselog/3_6_11.md)
- sqlite3_backup_pagecount → [backup.html](backup.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md)
- sqlite3_backup_remaining → [backup.html](backup.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md)
- sqlite3_backup_step → [backup.html](backup.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [rescode.html#done](rescode.md#done)
- sqlite3_bind_blob → [bindptr.html](bindptr.md) [c3ref/bind_parameter_count.html](c3ref/bind_parameter_count.md) [c3ref/bind_parameter_index.html](c3ref/bind_parameter_index.md) [c3ref/bind_parameter_name.html](c3ref/bind_parameter_name.md) [c3ref/clear_bindings.html](c3ref/clear_bindings.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/reset.html](c3ref/reset.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3.html](capi3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_bind_parameter_count](capi3ref.md#sqlite3_bind_parameter_count) [capi3ref.html#sqlite3_bind_parameter_index](capi3ref.md#sqlite3_bind_parameter_index) [capi3ref.html#sqlite3_bind_parameter_name](capi3ref.md#sqlite3_bind_parameter_name) [capi3ref.html#sqlite3_clear_bindings](capi3ref.md#sqlite3_clear_bindings) [capi3ref.html#sqlite3_reset](capi3ref.md#sqlite3_reset) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [fts3.html#f3tknzr](fts3.md#f3tknzr) [lang_expr.html#varparam](lang_expr.md#varparam) [limits.html#max_sql_length](limits.md#max_sql_length) [rescode.html#range](rescode.md#range)
- sqlite3_bind_blob64 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [changes.html#version_3_8_7](changes.md#version_3_8_7) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- sqlite3_bind_double → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [compile.html#omit_floating_point](compile.md#omit_floating_point)
- sqlite3_bind_int → [arch.html](arch.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [cintro.html](cintro.md) [cli.html#param](cli.md#param)
- sqlite3_bind_int64 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt)
- sqlite3_bind_null → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt)
- sqlite3_bind_parameter_count → [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/bind_parameter_index.html](c3ref/bind_parameter_index.md) [c3ref/bind_parameter_name.html](c3ref/bind_parameter_name.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_bind_parameter_index](capi3ref.md#sqlite3_bind_parameter_index) [capi3ref.html#sqlite3_bind_parameter_name](capi3ref.md#sqlite3_bind_parameter_name) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt)
- sqlite3_bind_parameter_index → [c3ref/bind_blob.html](c3ref/bind_blob.md) [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/bind_parameter_count.html](c3ref/bind_parameter_count.md) [c3ref/bind_parameter_name.html](c3ref/bind_parameter_name.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_bind_blob](capi3ref.md#sqlite3_bind_blob) [capi3ref.html#sqlite3_bind_parameter_count](capi3ref.md#sqlite3_bind_parameter_count) [capi3ref.html#sqlite3_bind_parameter_name](capi3ref.md#sqlite3_bind_parameter_name) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [lang_expr.html#varparam](lang_expr.md#varparam)
- sqlite3_bind_parameter_name → [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/bind_parameter_count.html](c3ref/bind_parameter_count.md) [c3ref/bind_parameter_index.html](c3ref/bind_parameter_index.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_bind_parameter_count](capi3ref.md#sqlite3_bind_parameter_count) [capi3ref.html#sqlite3_bind_parameter_index](capi3ref.md#sqlite3_bind_parameter_index) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [lang_expr.html#varparam](lang_expr.md#varparam)
- sqlite3_bind_pointer → [bindptr.html](bindptr.md) [bindptr.html#ptrleak](bindptr.md#ptrleak) [bindptr.html#ptrtyp](bindptr.md#ptrtyp) [bytecodevtab.html](bytecodevtab.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [carray.html#twoarg](carray.md#twoarg) [changes.html#version_3_20_0](changes.md#version_3_20_0) [fts5.html#extending_fts5](fts5.md#extending_fts5) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- sqlite3_bind_text → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [fts3.html#f3tknzr](fts3.md#f3tknzr) [fts3.html#limitations](fts3.md#limitations) [optoverview.html#like_opt](optoverview.md#like_opt)
- sqlite3_bind_text16 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/result_blob.html](c3ref/result_blob.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [compile.html#omit_utf16](compile.md#omit_utf16)
- sqlite3_bind_text64 → [c3ref/c_any.html#sqliteutf8zt](c3ref/c_any.md#sqliteutf8zt) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqliteutf8zt](capi3ref.md#sqliteutf8zt) [changes.html#version_3_53_0](changes.md#version_3_53_0) [changes.html#version_3_8_7](changes.md#version_3_8_7) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- sqlite3_bind_value → [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value)
- sqlite3_bind_zeroblob → [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [changes.html#version_3_4_0](changes.md#version_3_4_0) [releaselog/3_4_0.html](releaselog/3_4_0.md)
- sqlite3_bind_zeroblob64 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [changes.html#version_3_8_11](changes.md#version_3_8_11) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- sqlite3_blob → [c3ref/objlist.html](c3ref/objlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_17_0](changes.md#version_3_17_0) [changes.html#version_3_19_0](changes.md#version_3_19_0) [changes.html#version_3_7_4](changes.md#version_3_7_4) [compile.html#omit_incrblob](compile.md#omit_incrblob) [lang_transaction.html#immediate](lang_transaction.md#immediate) [malloc.html#nofrag](malloc.md#nofrag) [releaselog/3_17_0.html](releaselog/3_17_0.md) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md) [releaselog/3_7_4.html](releaselog/3_7_4.md) [withoutrowid.html](withoutrowid.md)
- sqlite3_blob_bytes → [c3ref/blob.html](c3ref/blob.md) [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/blob_read.html](c3ref/blob_read.md) [c3ref/blob_reopen.html](c3ref/blob_reopen.md) [c3ref/blob_write.html](c3ref/blob_write.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_blob](capi3ref.md#sqlite3_blob) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_blob_read](capi3ref.md#sqlite3_blob_read) [capi3ref.html#sqlite3_blob_reopen](capi3ref.md#sqlite3_blob_reopen) [capi3ref.html#sqlite3_blob_write](capi3ref.md#sqlite3_blob_write)
- sqlite3_blob_close → [c3ref/blob.html](c3ref/blob.md) [c3ref/blob_bytes.html](c3ref/blob_bytes.md) [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/blob_read.html](c3ref/blob_read.md) [c3ref/blob_write.html](c3ref/blob_write.md) [c3ref/close.html](c3ref/close.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_blob](capi3ref.md#sqlite3_blob) [capi3ref.html#sqlite3_blob_bytes](capi3ref.md#sqlite3_blob_bytes) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_blob_read](capi3ref.md#sqlite3_blob_read) [capi3ref.html#sqlite3_blob_write](capi3ref.md#sqlite3_blob_write) [capi3ref.html#sqlite3_close](capi3ref.md#sqlite3_close) [lang_transaction.html#immediate](lang_transaction.md#immediate)
- sqlite3_blob_open → [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/blob.html](c3ref/blob.md) [c3ref/blob_bytes.html](c3ref/blob_bytes.md) [c3ref/blob_close.html](c3ref/blob_close.md) [c3ref/blob_read.html](c3ref/blob_read.md) [c3ref/blob_reopen.html](c3ref/blob_reopen.md) [c3ref/blob_write.html](c3ref/blob_write.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_blob](capi3ref.md#sqlite3_blob) [capi3ref.html#sqlite3_blob_bytes](capi3ref.md#sqlite3_blob_bytes) [capi3ref.html#sqlite3_blob_close](capi3ref.md#sqlite3_blob_close) [capi3ref.html#sqlite3_blob_read](capi3ref.md#sqlite3_blob_read) [capi3ref.html#sqlite3_blob_reopen](capi3ref.md#sqlite3_blob_reopen) [capi3ref.html#sqlite3_blob_write](capi3ref.md#sqlite3_blob_write) [changes.html#version_3_4_0](changes.md#version_3_4_0) [lang_corefunc.html#zeroblob](lang_corefunc.md#zeroblob) [releaselog/3_4_0.html](releaselog/3_4_0.md) [unionvtab.html](unionvtab.md) [withoutrowid.html](withoutrowid.md)
- sqlite3_blob_read → [c3ref/blob.html](c3ref/blob.md) [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/blob_reopen.html](c3ref/blob_reopen.md) [c3ref/blob_write.html](c3ref/blob_write.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_blob](capi3ref.md#sqlite3_blob) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_blob_reopen](capi3ref.md#sqlite3_blob_reopen) [capi3ref.html#sqlite3_blob_write](capi3ref.md#sqlite3_blob_write) [changes.html#version_3_8_9](changes.md#version_3_8_9) [fasterthanfs.html](fasterthanfs.md) [releaselog/3_8_9.html](releaselog/3_8_9.md)
- sqlite3_blob_reopen → [c3ref/blob.html](c3ref/blob.md) [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/blob_reopen.html](c3ref/blob_reopen.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_blob](capi3ref.md#sqlite3_blob) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_blob_reopen](capi3ref.md#sqlite3_blob_reopen) [changes.html#version_3_17_0](changes.md#version_3_17_0) [changes.html#version_3_7_4](changes.md#version_3_7_4) [compile.html#enable_null_trim](compile.md#enable_null_trim) [releaselog/3_17_0.html](releaselog/3_17_0.md) [releaselog/3_7_4.html](releaselog/3_7_4.md)
- sqlite3_blob_write → [c3ref/blob.html](c3ref/blob.md) [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/blob_read.html](c3ref/blob_read.md) [c3ref/blob_reopen.html](c3ref/blob_reopen.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_blob](capi3ref.md#sqlite3_blob) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_blob_read](capi3ref.md#sqlite3_blob_read) [capi3ref.html#sqlite3_blob_reopen](capi3ref.md#sqlite3_blob_reopen) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite) [changes.html#version_3_8_9](changes.md#version_3_8_9) [releaselog/3_8_9.html](releaselog/3_8_9.md)
- sqlite3_busy_handler → [backup.html](backup.md) [c3ref/backup_finish.html#sqlite3backupstep](c3ref/backup_finish.md#sqlite3backupstep) [c3ref/busy_timeout.html](c3ref/busy_timeout.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/wal_checkpoint_v2.html](c3ref/wal_checkpoint_v2.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_busy_timeout](capi3ref.md#sqlite3_busy_timeout) [capi3ref.html#sqlite3_wal_checkpoint_v2](capi3ref.md#sqlite3_wal_checkpoint_v2) [capi3ref.html#sqlite3backupstep](capi3ref.md#sqlite3backupstep) [faq.html#q5](faq.md#q5) [pragma.html#pragma_busy_timeout](pragma.md#pragma_busy_timeout) [pragma.html#pragma_wal_checkpoint](pragma.md#pragma_wal_checkpoint) [rescode.html#busy](rescode.md#busy)
- sqlite3_busy_timeout → [34to35.html](34to35.md) [backup.html](backup.md) [c3ref/busy_handler.html](c3ref/busy_handler.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_busy_handler](capi3ref.md#sqlite3_busy_handler) [changes.html#version_3_50_0](changes.md#version_3_50_0) [faq.html#q5](faq.md#q5) [pragma.html#pragma_busy_timeout](pragma.md#pragma_busy_timeout) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md) [rescode.html#busy](rescode.md#busy)
- sqlite3_cancel_auto_extension → [c3ref/auto_extension.html](c3ref/auto_extension.md) [c3ref/cancel_auto_extension.html](c3ref/cancel_auto_extension.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_auto_extension](capi3ref.md#sqlite3_auto_extension) [capi3ref.html#sqlite3_cancel_auto_extension](capi3ref.md#sqlite3_cancel_auto_extension) [changes.html#version_3_8_0](changes.md#version_3_8_0) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md)
- sqlite3_carray_bind → [c3ref/c_carray_blob.html](c3ref/c_carray_blob.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_CARRAY_BLOB](capi3ref.md#SQLITE_CARRAY_BLOB) [changes.html#version_3_34_0](changes.md#version_3_34_0) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md)
- sqlite3_carray_bind_v2 → [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- sqlite3_changegroup → [session.html](session.md) [session/objlist.html](session/objlist.md) [sessionintro.html#changeset](sessionintro.md#changeset)
- sqlite3_changes → [c3ref/changes.html](c3ref/changes.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/total_changes.html](c3ref/total_changes.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_changes](capi3ref.md#sqlite3_changes) [capi3ref.html#sqlite3_total_changes](capi3ref.md#sqlite3_total_changes) [changes.html#version_3_6_5](changes.md#version_3_6_5) [changes.html#version_3_8_11_1](changes.md#version_3_8_11_1) [lang_conflict.html](lang_conflict.md) [lang_createtrigger.html#instead_of_trigger](lang_createtrigger.md#instead_of_trigger) [lang_delete.html#truncateopt](lang_delete.md#truncateopt) [pragma.html#pragma_count_changes](pragma.md#pragma_count_changes) [releaselog/3_6_5.html](releaselog/3_6_5.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- sqlite3_changes64 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_37_0](changes.md#version_3_37_0) [lang_corefunc.html#changes](lang_corefunc.md#changes) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md)
- sqlite3_changeset_iter → [session.html](session.md) [session/objlist.html](session/objlist.md)
- sqlite3_clear_bindings → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/reset.html](c3ref/reset.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_reset](capi3ref.md#sqlite3_reset) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt)
- sqlite3_close → [backup.html](backup.md) [c3ref/close.html](c3ref/close.md) [c3ref/create_collation.html](c3ref/create_collation.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/open.html](c3ref/open.md) [c3ref/snapshot_recover.html](c3ref/snapshot_recover.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/unlock_notify.html](c3ref/unlock_notify.md) [capi3.html](capi3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_close](capi3ref.md#sqlite3_close) [capi3ref.html#sqlite3_create_collation](capi3ref.md#sqlite3_create_collation) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [capi3ref.html#sqlite3_snapshot_recover](capi3ref.md#sqlite3_snapshot_recover) [capi3ref.html#sqlite3_unlock_notify](capi3ref.md#sqlite3_unlock_notify) [cintro.html](cintro.md) [howtocorrupt.html#fork](howtocorrupt.md#fork) [malloc.html](malloc.md) [quickstart.html](quickstart.md) [stmt.html](stmt.md) [tempfiles.html#tempdb](tempfiles.md#tempdb) [wal.html#walfile](wal.md#walfile) [walformat.html#locks](walformat.md#locks) [walformat.html#shm](walformat.md#shm)
- sqlite3_close_v2 → [c3ref/close.html](c3ref/close.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_close](capi3ref.md#sqlite3_close) [changes.html#version_3_7_14](changes.md#version_3_7_14) [oldnews.html](oldnews.md) [releaselog/3_7_14.html](releaselog/3_7_14.md) [walformat.html#locks](walformat.md#locks)
- sqlite3_collation_needed → [c3ref/create_collation.html](c3ref/create_collation.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_create_collation](capi3ref.md#sqlite3_create_collation)
- sqlite3_collation_needed16 → [c3ref/create_collation.html](c3ref/create_collation.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_create_collation](capi3ref.md#sqlite3_create_collation)
- sqlite3_column_blob → [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3.html](capi3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [changes.html#version_3_4_0](changes.md#version_3_4_0) [cintro.html](cintro.md) [releaselog/3_4_0.html](releaselog/3_4_0.md)
- sqlite3_column_bytes → [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [cintro.html](cintro.md)
- sqlite3_column_bytes16 → [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [cintro.html](cintro.md)
- sqlite3_column_count → [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/data_count.html](c3ref/data_count.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3.html](capi3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_data_count](capi3ref.md#sqlite3_data_count) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [changes.html#version_3_16_2](changes.md#version_3_16_2) [cintro.html](cintro.md) [releaselog/3_16_2.html](releaselog/3_16_2.md)
- sqlite3_column_database_name → [c3ref/column_database_name.html](c3ref/column_database_name.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_database_name](capi3ref.md#sqlite3_column_database_name) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [compile.html#enable_column_metadata](compile.md#enable_column_metadata)
- sqlite3_column_database_name16 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [compile.html#enable_column_metadata](compile.md#enable_column_metadata)
- sqlite3_column_decltype → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [compile.html#omit_decltype](compile.md#omit_decltype)
- sqlite3_column_decltype16 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [compile.html#omit_decltype](compile.md#omit_decltype)
- sqlite3_column_double → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [cintro.html](cintro.md) [compile.html#omit_floating_point](compile.md#omit_floating_point)
- sqlite3_column_int → [c3ref/data_count.html](c3ref/data_count.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_data_count](capi3ref.md#sqlite3_data_count) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [cintro.html](cintro.md) [opcode.html](opcode.md) [rescode.html#range](rescode.md#range)
- sqlite3_column_int64 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [cintro.html](cintro.md) [oldnews.html](oldnews.md)
- sqlite3_column_name → [c3ref/exec.html](c3ref/exec.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_exec](capi3ref.md#sqlite3_exec) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [changes.html#version_3_20_0](changes.md#version_3_20_0) [faq.html#q28](faq.md#q28) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- sqlite3_column_name16 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt)
- sqlite3_column_origin_name → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [compile.html#enable_column_metadata](compile.md#enable_column_metadata)
- sqlite3_column_origin_name16 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [compile.html#enable_column_metadata](compile.md#enable_column_metadata)
- sqlite3_column_table_name → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [compile.html#enable_column_metadata](compile.md#enable_column_metadata)
- sqlite3_column_table_name16 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [compile.html#enable_column_metadata](compile.md#enable_column_metadata)
- sqlite3_column_text → [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/exec.html](c3ref/exec.md) [c3ref/free_table.html](c3ref/free_table.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_exec](capi3ref.md#sqlite3_exec) [capi3ref.html#sqlite3_free_table](capi3ref.md#sqlite3_free_table) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [cintro.html](cintro.md) [floatingpoint.html#\*rounding](floatingpoint.md#*rounding) [invalidutf.html](invalidutf.md) [opcode.html](opcode.md)
- sqlite3_column_text16 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [cintro.html](cintro.md) [compile.html#omit_utf16](compile.md#omit_utf16) [invalidutf.html](invalidutf.md)
- sqlite3_column_type → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3.html](capi3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [cintro.html](cintro.md)
- sqlite3_column_value → [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [cintro.html](cintro.md)
- sqlite3_commit_hook → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/update_hook.html](c3ref/update_hook.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_update_hook](capi3ref.md#sqlite3_update_hook) [rescode.html#constraint_commithook](rescode.md#constraint_commithook)
- sqlite3_compileoption_get → [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_6_23](changes.md#version_3_6_23) [compile.html#omit_compileoption_diags](compile.md#omit_compileoption_diags) [lang_corefunc.html#sqlite_compileoption_get](lang_corefunc.md#sqlite_compileoption_get) [oldnews.html](oldnews.md) [pragma.html#pragma_compile_options](pragma.md#pragma_compile_options) [releaselog/3_6_23.html](releaselog/3_6_23.md) [th3.html](th3.md)
- sqlite3_compileoption_used → [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_6_23](changes.md#version_3_6_23) [changes.html#version_3_8_10_1](changes.md#version_3_8_10_1) [compile.html#omit_compileoption_diags](compile.md#omit_compileoption_diags) [lang_corefunc.html#sqlite_compileoption_used](lang_corefunc.md#sqlite_compileoption_used) [oldnews.html](oldnews.md) [releaselog/3_6_23.html](releaselog/3_6_23.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md)
- sqlite3_complete → [arch.html](arch.md) [c3ref/complete.html](c3ref/complete.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_complete](capi3ref.md#sqlite3_complete) [compile.html#omit_complete](compile.md#omit_complete)
- sqlite3_complete16 → [c3ref/complete.html](c3ref/complete.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_complete](capi3ref.md#sqlite3_complete) [compile.html#omit_complete](compile.md#omit_complete)
- sqlite3_config → [35to36.html](35to36.md) [c3ref/c_config_covering_index_scan.html](c3ref/c_config_covering_index_scan.md) [c3ref/c_config_covering_index_scan.html#sqliteconfiggetmutex](c3ref/c_config_covering_index_scan.md#sqliteconfiggetmutex) [c3ref/c_config_covering_index_scan.html#sqliteconfigmalloc](c3ref/c_config_covering_index_scan.md#sqliteconfigmalloc) [c3ref/c_config_covering_index_scan.html#sqliteconfigmultithread](c3ref/c_config_covering_index_scan.md#sqliteconfigmultithread) [c3ref/c_config_covering_index_scan.html#sqliteconfigmutex](c3ref/c_config_covering_index_scan.md#sqliteconfigmutex) [c3ref/c_config_covering_index_scan.html#sqliteconfigserialized](c3ref/c_config_covering_index_scan.md#sqliteconfigserialized) [c3ref/c_config_covering_index_scan.html#sqliteconfigsinglethread](c3ref/c_config_covering_index_scan.md#sqliteconfigsinglethread) [c3ref/db_config.html](c3ref/db_config.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/hard_heap_limit64.html](c3ref/hard_heap_limit64.md) [c3ref/initialize.html](c3ref/initialize.md) [c3ref/log.html](c3ref/log.md) [c3ref/mem_methods.html](c3ref/mem_methods.md) [c3ref/open.html#urifilenamesinsqlite3open](c3ref/open.md#urifilenamesinsqlite3open) [c3ref/pcache_methods2.html](c3ref/pcache_methods2.md) [c3ref/threadsafe.html](c3ref/threadsafe.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_CONFIG_COVERING_INDEX_SCAN](capi3ref.md#SQLITE_CONFIG_COVERING_INDEX_SCAN) [capi3ref.html#sqlite3_db_config](capi3ref.md#sqlite3_db_config) [capi3ref.html#sqlite3_hard_heap_limit64](capi3ref.md#sqlite3_hard_heap_limit64) [capi3ref.html#sqlite3_initialize](capi3ref.md#sqlite3_initialize) [capi3ref.html#sqlite3_log](capi3ref.md#sqlite3_log) [capi3ref.html#sqlite3_mem_methods](capi3ref.md#sqlite3_mem_methods) [capi3ref.html#sqlite3_pcache_methods2](capi3ref.md#sqlite3_pcache_methods2) [capi3ref.html#sqlite3_threadsafe](capi3ref.md#sqlite3_threadsafe) [capi3ref.html#sqliteconfiggetmutex](capi3ref.md#sqliteconfiggetmutex) [capi3ref.html#sqliteconfigmalloc](capi3ref.md#sqliteconfigmalloc) [capi3ref.html#sqliteconfigmultithread](capi3ref.md#sqliteconfigmultithread) [capi3ref.html#sqliteconfigmutex](capi3ref.md#sqliteconfigmutex) [capi3ref.html#sqliteconfigserialized](capi3ref.md#sqliteconfigserialized) [capi3ref.html#sqliteconfigsinglethread](capi3ref.md#sqliteconfigsinglethread) [capi3ref.html#urifilenamesinsqlite3open](capi3ref.md#urifilenamesinsqlite3open) [changes.html#version_3_12_0](changes.md#version_3_12_0) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_42_0](changes.md#version_3_42_0) [changes.html#version_3_6_1](changes.md#version_3_6_1) [changes.html#version_3_6_23](changes.md#version_3_6_23) [changes.html#version_3_8_8](changes.md#version_3_8_8) [cintro.html](cintro.md) [compile.html#default_lookaside](compile.md#default_lookaside) [compile.html#default_memstatus](compile.md#default_memstatus) [compile.html#default_mmap_size](compile.md#default_mmap_size) [compile.html#enable_memsys3](compile.md#enable_memsys3) [compile.html#enable_memsys5](compile.md#enable_memsys5) [compile.html#enable_sorter_references](compile.md#enable_sorter_references) [compile.html#enable_sqllog](compile.md#enable_sqllog) [compile.html#max_memory](compile.md#max_memory) [compile.html#memdb_default_maxsize](compile.md#memdb_default_maxsize) [compile.html#threadsafe](compile.md#threadsafe) [compile.html#zero_malloc](compile.md#zero_malloc) [custombuild.html](custombuild.md) [errlog.html](errlog.md) [lang_vacuum.html#vacuuminto](lang_vacuum.md#vacuuminto) [loadext.html#statext](loadext.md#statext) [malloc.html#lookaside](malloc.md#lookaside) [malloc.html#memstatus](malloc.md#memstatus) [malloc.html#memsys5](malloc.md#memsys5) [malloc.html#memsysx](malloc.md#memsysx) [malloc.html#pagecache](malloc.md#pagecache) [mmap.html](mmap.md) [news.html](news.md) [pragma.html#pragma_mmap_size](pragma.md#pragma_mmap_size) [privatebranch.html](privatebranch.md) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_42_0.html](releaselog/3_42_0.md) [releaselog/3_6_0.html](releaselog/3_6_0.md) [releaselog/3_6_1.html](releaselog/3_6_1.md) [releaselog/3_6_23.html](releaselog/3_6_23.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md) [security.html](security.md) [testing.html#oomtesting](testing.md#oomtesting) [threadsafe.html](threadsafe.md) [uri.html](uri.md)
- sqlite3_context → [c3ref/aggregate_context.html](c3ref/aggregate_context.md) [c3ref/objlist.html](c3ref/objlist.md) [c3ref/result_blob.html](c3ref/result_blob.md) [c3ref/result_subtype.html](c3ref/result_subtype.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_aggregate_context](capi3ref.md#sqlite3_aggregate_context) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [capi3ref.html#sqlite3_result_subtype](capi3ref.md#sqlite3_result_subtype) [changes.html#version_3_8_10](changes.md#version_3_8_10) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md) [windowfunctions.html#udfwinfunc](windowfunctions.md#udfwinfunc)
- sqlite3_context_db_handle → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [changes.html#version_3_5_8](changes.md#version_3_5_8) [oldnews.html](oldnews.md) [releaselog/3_5_8.html](releaselog/3_5_8.md)
- sqlite3_create_collation → [c3ref/c_any.html#sqliteutf16aligned](c3ref/c_any.md#sqliteutf16aligned) [c3ref/collation_needed.html](c3ref/collation_needed.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_collation_needed](capi3ref.md#sqlite3_collation_needed) [capi3ref.html#sqliteutf16aligned](capi3ref.md#sqliteutf16aligned) [cintro.html](cintro.md) [datatype3.html#collation](datatype3.md#collation) [faq.html#q18](faq.md#q18) [fileformat2.html#serialtype](fileformat2.md#serialtype) [fullsql.html](fullsql.md)
- sqlite3_create_collation16 → [c3ref/collation_needed.html](c3ref/collation_needed.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_collation_needed](capi3ref.md#sqlite3_collation_needed)
- sqlite3_create_collation_v2 → [c3ref/collation_needed.html](c3ref/collation_needed.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_collation_needed](capi3ref.md#sqlite3_collation_needed)
- sqlite3_create_filename → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/uri_boolean.html](c3ref/uri_boolean.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_uri_boolean](capi3ref.md#sqlite3_uri_boolean) [changes.html#version_3_32_0](changes.md#version_3_32_0) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- sqlite3_create_function → [appfunc.html](appfunc.md) [c3ref/c_any.html#sqliteany](c3ref/c_any.md#sqliteany) [c3ref/c_deterministic.html](c3ref/c_deterministic.md) [c3ref/context_db_handle.html](c3ref/context_db_handle.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/result_blob.html](c3ref/result_blob.md) [c3ref/result_subtype.html](c3ref/result_subtype.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/user_data.html](c3ref/user_data.md) [c3ref/value_subtype.html](c3ref/value_subtype.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_DETERMINISTIC](capi3ref.md#SQLITE_DETERMINISTIC) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_context_db_handle](capi3ref.md#sqlite3_context_db_handle) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [capi3ref.html#sqlite3_result_subtype](capi3ref.md#sqlite3_result_subtype) [capi3ref.html#sqlite3_user_data](capi3ref.md#sqlite3_user_data) [capi3ref.html#sqlite3_value_subtype](capi3ref.md#sqlite3_value_subtype) [capi3ref.html#sqliteany](capi3ref.md#sqliteany) [changes.html#version_3_6_15](changes.md#version_3_6_15) [changes.html#version_3_8_3](changes.md#version_3_8_3) [cintro.html](cintro.md) [faq.html#q18](faq.md#q18) [fts3.html#appendix_a](fts3.md#appendix_a) [fts3.html#the_compress_and_uncompress_options](fts3.md#the_compress_and_uncompress_options) [lang_aggfunc.html](lang_aggfunc.md) [lang_corefunc.html](lang_corefunc.md) [lang_corefunc.html#glob](lang_corefunc.md#glob) [lang_corefunc.html#like](lang_corefunc.md#like) [lang_expr.html#\*funcinexpr](lang_expr.md#*funcinexpr) [news.html](news.md) [optoverview.html#like_opt](optoverview.md#like_opt) [pragma.html#pragma_case_sensitive_like](pragma.md#pragma_case_sensitive_like) [releaselog/3_6_15.html](releaselog/3_6_15.md) [releaselog/3_8_3.html](releaselog/3_8_3.md) [rtree.html#readwrite](rtree.md#readwrite)
- sqlite3_create_function16 → [appfunc.html](appfunc.md) [c3ref/c_deterministic.html](c3ref/c_deterministic.md) [c3ref/context_db_handle.html](c3ref/context_db_handle.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/result_blob.html](c3ref/result_blob.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/user_data.html](c3ref/user_data.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_DETERMINISTIC](capi3ref.md#SQLITE_DETERMINISTIC) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_context_db_handle](capi3ref.md#sqlite3_context_db_handle) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [capi3ref.html#sqlite3_user_data](capi3ref.md#sqlite3_user_data)
- sqlite3_create_function_v2 → [appfunc.html](appfunc.md) [c3ref/c_deterministic.html](c3ref/c_deterministic.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_DETERMINISTIC](capi3ref.md#SQLITE_DETERMINISTIC) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_7_3](changes.md#version_3_7_3) [deterministic.html#dtexception](deterministic.md#dtexception) [oldnews.html](oldnews.md) [rbu.html#sqldiff](rbu.md#sqldiff) [releaselog/3_7_3.html](releaselog/3_7_3.md)
- sqlite3_create_module → [c3ref/drop_modules.html](c3ref/drop_modules.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/module.html](c3ref/module.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_drop_modules](capi3ref.md#sqlite3_drop_modules) [capi3ref.html#sqlite3_module](capi3ref.md#sqlite3_module) [changes.html#version_3_7_13](changes.md#version_3_7_13) [cintro.html](cintro.md) [lang_createvtab.html](lang_createvtab.md) [releaselog/3_7_13.html](releaselog/3_7_13.md) [rtree.html](rtree.md) [vtab.html](vtab.md) [vtab.html#customvtab](vtab.md#customvtab) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab) [vtab.html#xcreate](vtab.md#xcreate)
- sqlite3_create_module_v2 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/module.html](c3ref/module.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_module](capi3ref.md#sqlite3_module) [changes.html#version_3_7_13](changes.md#version_3_7_13) [lang_createvtab.html](lang_createvtab.md) [releaselog/3_7_13.html](releaselog/3_7_13.md) [vtab.html#customvtab](vtab.md#customvtab) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab) [vtab.html#xcreate](vtab.md#xcreate)
- sqlite3_create_window_function → [appfunc.html](appfunc.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#udfwinfunc](windowfunctions.md#udfwinfunc)
- sqlite3_data_count → [c3ref/column_count.html](c3ref/column_count.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3.html](capi3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_count](capi3ref.md#sqlite3_column_count) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [changes.html#version_3_7_9](changes.md#version_3_7_9) [releaselog/3_7_9.html](releaselog/3_7_9.md)
- sqlite3_data_directory → [c3ref/objlist.html](c3ref/objlist.md) [c3ref/win32_set_directory.html](c3ref/win32_set_directory.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_win32_set_directory](capi3ref.md#sqlite3_win32_set_directory) [pragma.html#pragma_data_store_directory](pragma.md#pragma_data_store_directory)
- sqlite3_database_file_object → [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_32_0](changes.md#version_3_32_0) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- sqlite3_db_cacheflush → [c3ref/db_cacheflush.html](c3ref/db_cacheflush.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_db_cacheflush](capi3ref.md#sqlite3_db_cacheflush) [changes.html#version_3_10_0](changes.md#version_3_10_0) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md)
- sqlite3_db_config → [appfunc.html#sec](appfunc.md#sec) [bytecodevtab.html#nexec](bytecodevtab.md#nexec) [c3ref/c_config_covering_index_scan.html#sqliteconfiglookaside](c3ref/c_config_covering_index_scan.md#sqliteconfiglookaside) [c3ref/c_dbconfig_defensive.html](c3ref/c_dbconfig_defensive.md) [c3ref/c_dbconfig_defensive.html#dbconfigarguments](c3ref/c_dbconfig_defensive.md#dbconfigarguments) [c3ref/c_dbconfig_defensive.html#sqlitedbconfiglookaside](c3ref/c_dbconfig_defensive.md#sqlitedbconfiglookaside) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigmaindbname](c3ref/c_dbconfig_defensive.md#sqlitedbconfigmaindbname) [c3ref/c_dbconfig_defensive.html#sqlitedbconfignockptonclose](c3ref/c_dbconfig_defensive.md#sqlitedbconfignockptonclose) [c3ref/enable_load_extension.html](c3ref/enable_load_extension.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/load_extension.html](c3ref/load_extension.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_DBCONFIG_DEFENSIVE](capi3ref.md#SQLITE_DBCONFIG_DEFENSIVE) [capi3ref.html#dbconfigarguments](capi3ref.md#dbconfigarguments) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_enable_load_extension](capi3ref.md#sqlite3_enable_load_extension) [capi3ref.html#sqlite3_load_extension](capi3ref.md#sqlite3_load_extension) [capi3ref.html#sqliteconfiglookaside](capi3ref.md#sqliteconfiglookaside) [capi3ref.html#sqlitedbconfiglookaside](capi3ref.md#sqlitedbconfiglookaside) [capi3ref.html#sqlitedbconfigmaindbname](capi3ref.md#sqlitedbconfigmaindbname) [capi3ref.html#sqlitedbconfignockptonclose](capi3ref.md#sqlitedbconfignockptonclose) [changes.html#version_3_12_0](changes.md#version_3_12_0) [changes.html#version_3_13_0](changes.md#version_3_13_0) [changes.html#version_3_16_0](changes.md#version_3_16_0) [changes.html#version_3_24_0](changes.md#version_3_24_0) [changes.html#version_3_28_0](changes.md#version_3_28_0) [changes.html#version_3_29_0](changes.md#version_3_29_0) [changes.html#version_3_30_0](changes.md#version_3_30_0) [changes.html#version_3_31_0](changes.md#version_3_31_0) [changes.html#version_3_42_0](changes.md#version_3_42_0) [changes.html#version_3_49_0](changes.md#version_3_49_0) [changes.html#version_3_53_0](changes.md#version_3_53_0) [changes.html#version_3_6_1](changes.md#version_3_6_1) [cintro.html](cintro.md) [compile.html#default_lookaside](compile.md#default_lookaside) [compile.html#enable_fts3_tokenizer](compile.md#enable_fts3_tokenizer) [compile.html#enable_qpsg](compile.md#enable_qpsg) [cves.html#cvetab](cves.md#cvetab) [fileformat2.html#schemaformat](fileformat2.md#schemaformat) [fts3.html#f3tknzr](fts3.md#f3tknzr) [lang_altertable.html#altertabrename](lang_altertable.md#altertabrename) [loadext.html](loadext.md) [malloc.html#lookaside](malloc.md#lookaside) [news.html](news.md) [pragma.html#pragma_legacy_alter_table](pragma.md#pragma_legacy_alter_table) [pragma.html#pragma_legacy_file_format](pragma.md#pragma_legacy_file_format) [pragma.html#pragma_trusted_schema](pragma.md#pragma_trusted_schema) [privatebranch.html](privatebranch.md) [queryplanner-ng.html#qpstab](queryplanner-ng.md#qpstab) [quirks.html#dblquote](quirks.md#dblquote) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_24_0.html](releaselog/3_24_0.md) [releaselog/3_28_0.html](releaselog/3_28_0.md) [releaselog/3_29_0.html](releaselog/3_29_0.md) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [releaselog/3_42_0.html](releaselog/3_42_0.md) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [releaselog/3_6_1.html](releaselog/3_6_1.md) [security.html#baddb](security.md#baddb) [tclsqlite.html#config](tclsqlite.md#config) [vtab.html#xshadowname](vtab.md#xshadowname)
- sqlite3_db_filename → [c3ref/filename_database.html](c3ref/filename_database.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/uri_boolean.html](c3ref/uri_boolean.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_filename_database](capi3ref.md#sqlite3_filename_database) [capi3ref.html#sqlite3_uri_boolean](capi3ref.md#sqlite3_uri_boolean) [changes.html#version_3_7_10](changes.md#version_3_7_10) [oldnews.html](oldnews.md) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- sqlite3_db_handle → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [unlock_notify.html](unlock_notify.md)
- sqlite3_db_mutex → [c3ref/errcode.html](c3ref/errcode.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_errcode](capi3ref.md#sqlite3_errcode) [changes.html#version_3_6_5](changes.md#version_3_6_5) [releaselog/3_6_5.html](releaselog/3_6_5.md)
- sqlite3_db_name → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_39_0](changes.md#version_3_39_0) [releaselog/3_39_0.html](releaselog/3_39_0.md) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- sqlite3_db_readonly → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/open.html](c3ref/open.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [changes.html#version_3_12_0](changes.md#version_3_12_0) [changes.html#version_3_34_0](changes.md#version_3_34_0) [changes.html#version_3_7_11](changes.md#version_3_7_11) [changes.html#version_3_8_5](changes.md#version_3_8_5) [pragma.html#pragma_query_only](pragma.md#pragma_query_only) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md) [releaselog/3_7_11.html](releaselog/3_7_11.md) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- sqlite3_db_release_memory → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/release_memory.html](c3ref/release_memory.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_release_memory](capi3ref.md#sqlite3_release_memory) [changes.html#version_3_7_10](changes.md#version_3_7_10) [oldnews.html](oldnews.md) [pragma.html#pragma_shrink_memory](pragma.md#pragma_shrink_memory) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- sqlite3_db_status → [c3ref/c_dbstatus_options.html](c3ref/c_dbstatus_options.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/status.html](c3ref/status.md) [c3ref/stmt_status.html](c3ref/stmt_status.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_DBSTATUS options](capi3ref.md#SQLITE_DBSTATUS%20options) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_status](capi3ref.md#sqlite3_status) [capi3ref.html#sqlite3_stmt_status](capi3ref.md#sqlite3_stmt_status) [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_23_0](changes.md#version_3_23_0) [changes.html#version_3_51_0](changes.md#version_3_51_0) [changes.html#version_3_6_1](changes.md#version_3_6_1) [changes.html#version_3_7_0](changes.md#version_3_7_0) [changes.html#version_3_7_1](changes.md#version_3_7_1) [changes.html#version_3_7_12](changes.md#version_3_7_12) [changes.html#version_3_7_5](changes.md#version_3_7_5) [changes.html#version_3_7_9](changes.md#version_3_7_9) [changes.html#version_3_8_0](changes.md#version_3_8_0) [malloc.html#memstatus](malloc.md#memstatus) [memstat.html](memstat.md) [oldnews.html](oldnews.md) [pragma.html#pragma_defer_foreign_keys](pragma.md#pragma_defer_foreign_keys) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md) [releaselog/3_6_1.html](releaselog/3_6_1.md) [releaselog/3_7_0.html](releaselog/3_7_0.md) [releaselog/3_7_1.html](releaselog/3_7_1.md) [releaselog/3_7_12.html](releaselog/3_7_12.md) [releaselog/3_7_5.html](releaselog/3_7_5.md) [releaselog/3_7_9.html](releaselog/3_7_9.md) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md) [vtablist.html](vtablist.md)
- sqlite3_db_status64 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_51_0](changes.md#version_3_51_0) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- sqlite3_declare_vtab → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/vtab_collation.html](c3ref/vtab_collation.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_vtab_collation](capi3ref.md#sqlite3_vtab_collation) [csv.html](csv.md) [fts3.html#simple_fts_queries](fts3.md#simple_fts_queries) [vtab.html#hiddencol](vtab.md#hiddencol) [vtab.html#worid](vtab.md#worid) [vtab.html#xbestindex](vtab.md#xbestindex) [vtab.html#xconnect](vtab.md#xconnect) [vtab.html#xcreate](vtab.md#xcreate) [vtab.html#xupdate](vtab.md#xupdate)
- sqlite3_deserialize → [c3ref/c_config_covering_index_scan.html#sqliteconfigmemdbmaxsize](c3ref/c_config_covering_index_scan.md#sqliteconfigmemdbmaxsize) [c3ref/c_deserialize_freeonclose.html](c3ref/c_deserialize_freeonclose.md) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlsizelimit](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlsizelimit) [c3ref/c_serialize_nocopy.html](c3ref/c_serialize_nocopy.md) [c3ref/db_name.html](c3ref/db_name.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/serialize.html](c3ref/serialize.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_DESERIALIZE_FREEONCLOSE](capi3ref.md#SQLITE_DESERIALIZE_FREEONCLOSE) [capi3ref.html#SQLITE_SERIALIZE_NOCOPY](capi3ref.md#SQLITE_SERIALIZE_NOCOPY) [capi3ref.html#sqlite3_db_name](capi3ref.md#sqlite3_db_name) [capi3ref.html#sqlite3_serialize](capi3ref.md#sqlite3_serialize) [capi3ref.html#sqliteconfigmemdbmaxsize](capi3ref.md#sqliteconfigmemdbmaxsize) [capi3ref.html#sqlitefcntlsizelimit](capi3ref.md#sqlitefcntlsizelimit) [changes.html#version_3_23_0](changes.md#version_3_23_0) [changes.html#version_3_26_0](changes.md#version_3_26_0) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_36_0](changes.md#version_3_36_0) [changes.html#version_3_37_0](changes.md#version_3_37_0) [changes.html#version_3_41_0](changes.md#version_3_41_0) [cli.html#dotopen](cli.md#dotopen) [compile.html#enable_deserialize](compile.md#enable_deserialize) [compile.html#memdb_default_maxsize](compile.md#memdb_default_maxsize) [compile.html#omit_deserialize](compile.md#omit_deserialize) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_26_0.html](releaselog/3_26_0.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_36_0.html](releaselog/3_36_0.md) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- sqlite3_drop_modules → [c3ref/create_module.html](c3ref/create_module.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_create_module](capi3ref.md#sqlite3_create_module) [changes.html#version_3_30_0](changes.md#version_3_30_0) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md)
- sqlite3_enable_load_extension → [34to35.html](34to35.md) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigenableloadextension](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenableloadextension) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/load_extension.html](c3ref/load_extension.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_load_extension](capi3ref.md#sqlite3_load_extension) [capi3ref.html#sqlitedbconfigenableloadextension](capi3ref.md#sqlitedbconfigenableloadextension) [compile.html#omit_load_extension](compile.md#omit_load_extension) [lang_corefunc.html#load_extension](lang_corefunc.md#load_extension) [loadext.html](loadext.md) [tclsqlite.html#enable_load_extension](tclsqlite.md#enable_load_extension)
- sqlite3_enable_shared_cache → [34to35.html](34to35.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/open.html](c3ref/open.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [changes.html#version_3_5_0](changes.md#version_3_5_0) [compile.html#omit_shared_cache](compile.md#omit_shared_cache) [pragma.html#pragma_read_uncommitted](pragma.md#pragma_read_uncommitted) [releaselog/3_5_0.html](releaselog/3_5_0.md) [sharedcache.html#dontuse](sharedcache.md#dontuse)
- sqlite3_errcode → [backup.html](backup.md) [c3ref/backup_finish.html#sqlite3backupinit](c3ref/backup_finish.md#sqlite3backupinit) [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/blob_write.html](c3ref/blob_write.md) [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/db_cacheflush.html](c3ref/db_cacheflush.md) [c3ref/file_control.html](c3ref/file_control.md) [c3ref/free_table.html](c3ref/free_table.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/set_errmsg.html](c3ref/set_errmsg.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/value_blob.html](c3ref/value_blob.md) [c3ref/wal_checkpoint_v2.html](c3ref/wal_checkpoint_v2.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_blob_write](capi3ref.md#sqlite3_blob_write) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_db_cacheflush](capi3ref.md#sqlite3_db_cacheflush) [capi3ref.html#sqlite3_file_control](capi3ref.md#sqlite3_file_control) [capi3ref.html#sqlite3_free_table](capi3ref.md#sqlite3_free_table) [capi3ref.html#sqlite3_set_errmsg](capi3ref.md#sqlite3_set_errmsg) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [capi3ref.html#sqlite3_wal_checkpoint_v2](capi3ref.md#sqlite3_wal_checkpoint_v2) [capi3ref.html#sqlite3backupinit](capi3ref.md#sqlite3backupinit) [session.html#sqlite3changeset_apply](session.md#sqlite3changeset_apply) [session/sqlite3changeset_apply.html](session/sqlite3changeset_apply.md)
- sqlite3_errmsg → [backup.html](backup.md) [c3ref/backup_finish.html#sqlite3backupinit](c3ref/backup_finish.md#sqlite3backupinit) [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/blob_write.html](c3ref/blob_write.md) [c3ref/db_cacheflush.html](c3ref/db_cacheflush.md) [c3ref/file_control.html](c3ref/file_control.md) [c3ref/free_table.html](c3ref/free_table.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/open.html](c3ref/open.md) [c3ref/set_errmsg.html](c3ref/set_errmsg.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/step.html](c3ref/step.md) [c3ref/wal_checkpoint_v2.html](c3ref/wal_checkpoint_v2.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_blob_write](capi3ref.md#sqlite3_blob_write) [capi3ref.html#sqlite3_db_cacheflush](capi3ref.md#sqlite3_db_cacheflush) [capi3ref.html#sqlite3_file_control](capi3ref.md#sqlite3_file_control) [capi3ref.html#sqlite3_free_table](capi3ref.md#sqlite3_free_table) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [capi3ref.html#sqlite3_set_errmsg](capi3ref.md#sqlite3_set_errmsg) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [capi3ref.html#sqlite3_wal_checkpoint_v2](capi3ref.md#sqlite3_wal_checkpoint_v2) [capi3ref.html#sqlite3backupinit](capi3ref.md#sqlite3backupinit) [changes.html#version_3_20_0](changes.md#version_3_20_0) [invalidutf.html](invalidutf.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [rescode.html#constraint](rescode.md#constraint) [session.html#sqlite3changeset_apply](session.md#sqlite3changeset_apply) [session/sqlite3changeset_apply.html](session/sqlite3changeset_apply.md)
- sqlite3_errmsg16 → [c3ref/backup_finish.html#sqlite3backupinit](c3ref/backup_finish.md#sqlite3backupinit) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/open.html](c3ref/open.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [capi3ref.html#sqlite3backupinit](capi3ref.md#sqlite3backupinit) [rescode.html#constraint](rescode.md#constraint)
- sqlite3_error_offset → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_38_0](changes.md#version_3_38_0) [changes.html#version_3_41_2](changes.md#version_3_41_2) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- sqlite3_errstr → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_7_15](changes.md#version_3_7_15) [releaselog/3_7_15.html](releaselog/3_7_15.md)
- sqlite3_exec → [backup.html](backup.md) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigresetdatabase](c3ref/c_dbconfig_defensive.md#sqlitedbconfigresetdatabase) [c3ref/free_table.html](c3ref/free_table.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/stmt_readonly.html](c3ref/stmt_readonly.md) [capi3.html](capi3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_free_table](capi3ref.md#sqlite3_free_table) [capi3ref.html#sqlite3_stmt_readonly](capi3ref.md#sqlite3_stmt_readonly) [capi3ref.html#sqlitedbconfigresetdatabase](capi3ref.md#sqlitedbconfigresetdatabase) [cintro.html](cintro.md) [cli.html#dotrules](cli.md#dotrules) [faq.html#q15](faq.md#q15) [lang.html](lang.md) [oldnews.html](oldnews.md) [pragma.html#pragma_empty_result_callbacks](pragma.md#pragma_empty_result_callbacks) [quickstart.html](quickstart.md) [rescode.html#abort](rescode.md#abort)
- sqlite3_expanded_sql → [c3ref/c_trace.html#sqlitetracestmt](c3ref/c_trace.md#sqlitetracestmt) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqlitetracestmt](capi3ref.md#sqlitetracestmt) [changes.html#version_3_14](changes.md#version_3_14) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- sqlite3_expired → [compile.html#omit_deprecated](compile.md#omit_deprecated)
- sqlite3_extended_errcode → [c3ref/c_abort_rollback.html](c3ref/c_abort_rollback.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_ABORT_ROLLBACK](capi3ref.md#SQLITE_ABORT_ROLLBACK) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_6_5](changes.md#version_3_6_5) [releaselog/3_6_5.html](releaselog/3_6_5.md) [rescode.html#pve](rescode.md#pve)
- sqlite3_extended_result_codes → [c3ref/c_abort_rollback.html](c3ref/c_abort_rollback.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/open.html#openexrescode](c3ref/open.md#openexrescode) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_ABORT_ROLLBACK](capi3ref.md#SQLITE_ABORT_ROLLBACK) [capi3ref.html#openexrescode](capi3ref.md#openexrescode) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [rescode.html#pve](rescode.md#pve)
- sqlite3_file → [34to35.html](34to35.md) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlbeginatomicwrite](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlbeginatomicwrite) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlfilepointer](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlfilepointer) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlfilestat](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlfilestat) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntljournalpointer](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntljournalpointer) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlnullio](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlnullio) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlpragma](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlpragma) [c3ref/database_file_object.html](c3ref/database_file_object.md) [c3ref/file.html](c3ref/file.md) [c3ref/file_control.html](c3ref/file_control.md) [c3ref/io_methods.html](c3ref/io_methods.md) [c3ref/objlist.html](c3ref/objlist.md) [c3ref/vfs.html](c3ref/vfs.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_database_file_object](capi3ref.md#sqlite3_database_file_object) [capi3ref.html#sqlite3_file](capi3ref.md#sqlite3_file) [capi3ref.html#sqlite3_file_control](capi3ref.md#sqlite3_file_control) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods) [capi3ref.html#sqlite3_vfs](capi3ref.md#sqlite3_vfs) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen) [capi3ref.html#sqlitefcntlbeginatomicwrite](capi3ref.md#sqlitefcntlbeginatomicwrite) [capi3ref.html#sqlitefcntlfilepointer](capi3ref.md#sqlitefcntlfilepointer) [capi3ref.html#sqlitefcntlfilestat](capi3ref.md#sqlitefcntlfilestat) [capi3ref.html#sqlitefcntljournalpointer](capi3ref.md#sqlitefcntljournalpointer) [capi3ref.html#sqlitefcntlnullio](capi3ref.md#sqlitefcntlnullio) [capi3ref.html#sqlitefcntlpragma](capi3ref.md#sqlitefcntlpragma) [vfs.html#shim](vfs.md#shim)
- sqlite3_file_control → [34to35.html](34to35.md) [c3ref/c_config_covering_index_scan.html#sqliteconfigmemdbmaxsize](c3ref/c_config_covering_index_scan.md#sqliteconfigmemdbmaxsize) [c3ref/c_fcntl_begin_atomic_write.html](c3ref/c_fcntl_begin_atomic_write.md) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlchunksize](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlchunksize) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlcommitphasetwo](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlcommitphasetwo) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlfilestat](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlfilestat) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlpersistwal](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlpersistwal) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlpowersafeoverwrite](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlpowersafeoverwrite) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlsync](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlsync) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlvfsname](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlvfsname) [c3ref/file_control.html](c3ref/file_control.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_FCNTL_BEGIN_ATOMIC_WRITE](capi3ref.md#SQLITE_FCNTL_BEGIN_ATOMIC_WRITE) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_file_control](capi3ref.md#sqlite3_file_control) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods) [capi3ref.html#sqliteconfigmemdbmaxsize](capi3ref.md#sqliteconfigmemdbmaxsize) [capi3ref.html#sqlitefcntlchunksize](capi3ref.md#sqlitefcntlchunksize) [capi3ref.html#sqlitefcntlcommitphasetwo](capi3ref.md#sqlitefcntlcommitphasetwo) [capi3ref.html#sqlitefcntlfilestat](capi3ref.md#sqlitefcntlfilestat) [capi3ref.html#sqlitefcntlpersistwal](capi3ref.md#sqlitefcntlpersistwal) [capi3ref.html#sqlitefcntlpowersafeoverwrite](capi3ref.md#sqlitefcntlpowersafeoverwrite) [capi3ref.html#sqlitefcntlsync](capi3ref.md#sqlitefcntlsync) [capi3ref.html#sqlitefcntlvfsname](capi3ref.md#sqlitefcntlvfsname) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_41_0](changes.md#version_3_41_0) [changes.html#version_3_7_1](changes.md#version_3_7_1) [changes.html#version_3_7_4](changes.md#version_3_7_4) [changes.html#version_3_7_5](changes.md#version_3_7_5) [compile.html#enable_batch_atomic_write](compile.md#enable_batch_atomic_write) [compile.html#memdb_default_maxsize](compile.md#memdb_default_maxsize) [memstat.html](memstat.md) [pragma.html](pragma.md) [psow.html#tornpage](psow.md#tornpage) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md) [releaselog/3_7_1.html](releaselog/3_7_1.md) [releaselog/3_7_4.html](releaselog/3_7_4.md) [releaselog/3_7_5.html](releaselog/3_7_5.md) [rescode.html#notfound](rescode.md#notfound) [walformat.html#locks](walformat.md#locks) [walformat.html#shm](walformat.md#shm)
- sqlite3_filename → [c3ref/filename.html](c3ref/filename.md) [c3ref/objlist.html](c3ref/objlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_filename](capi3ref.md#sqlite3_filename) [changes.html#version_3_40_0](changes.md#version_3_40_0) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md)
- sqlite3_filename_database → [c3ref/create_filename.html](c3ref/create_filename.md) [c3ref/db_filename.html](c3ref/db_filename.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_create_filename](capi3ref.md#sqlite3_create_filename) [capi3ref.html#sqlite3_db_filename](capi3ref.md#sqlite3_db_filename) [changes.html#version_3_31_0](changes.md#version_3_31_0) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- sqlite3_filename_journal → [c3ref/create_filename.html](c3ref/create_filename.md) [c3ref/db_filename.html](c3ref/db_filename.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_create_filename](capi3ref.md#sqlite3_create_filename) [capi3ref.html#sqlite3_db_filename](capi3ref.md#sqlite3_db_filename) [changes.html#version_3_31_0](changes.md#version_3_31_0) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- sqlite3_filename_wal → [c3ref/create_filename.html](c3ref/create_filename.md) [c3ref/db_filename.html](c3ref/db_filename.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_create_filename](capi3ref.md#sqlite3_create_filename) [capi3ref.html#sqlite3_db_filename](capi3ref.md#sqlite3_db_filename) [changes.html#version_3_31_0](changes.md#version_3_31_0) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- sqlite3_finalize → [c3ref/c_prepare_dont_log.html#sqlitepreparepersistent](c3ref/c_prepare_dont_log.md#sqlitepreparepersistent) [c3ref/close.html](c3ref/close.md) [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/column_database_name.html](c3ref/column_database_name.md) [c3ref/column_name.html](c3ref/column_name.md) [c3ref/exec.html](c3ref/exec.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/get_auxdata.html](c3ref/get_auxdata.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/step.html](c3ref/step.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_close](capi3ref.md#sqlite3_close) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_column_database_name](capi3ref.md#sqlite3_column_database_name) [capi3ref.html#sqlite3_column_name](capi3ref.md#sqlite3_column_name) [capi3ref.html#sqlite3_exec](capi3ref.md#sqlite3_exec) [capi3ref.html#sqlite3_get_auxdata](capi3ref.md#sqlite3_get_auxdata) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqlitepreparepersistent](capi3ref.md#sqlitepreparepersistent) [changes.html#version_3_7_6](changes.md#version_3_7_6) [changes.html#version_3_8_11](changes.md#version_3_8_11) [cintro.html](cintro.md) [lang_transaction.html#immediate](lang_transaction.md#immediate) [malloc.html](malloc.md) [opcode.html](opcode.md) [pragma.html](pragma.md) [releaselog/3_7_6.html](releaselog/3_7_6.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [rescode.html#misuse](rescode.md#misuse) [stmt.html](stmt.md)
- sqlite3_free → [34to35.html](34to35.md) [c3ref/auto_extension.html](c3ref/auto_extension.md) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntltempfilename](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntltempfilename) [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/data_directory.html](c3ref/data_directory.md) [c3ref/deserialize.html](c3ref/deserialize.md) [c3ref/exec.html](c3ref/exec.md) [c3ref/expanded_sql.html](c3ref/expanded_sql.md) [c3ref/free.html](c3ref/free.md) [c3ref/free_table.html](c3ref/free_table.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/index_info.html](c3ref/index_info.md) [c3ref/load_extension.html](c3ref/load_extension.md) [c3ref/memory_highwater.html](c3ref/memory_highwater.md) [c3ref/mprintf.html](c3ref/mprintf.md) [c3ref/str_finish.html](c3ref/str_finish.md) [c3ref/temp_directory.html](c3ref/temp_directory.md) [c3ref/vtab.html](c3ref/vtab.md) [c3ref/win32_set_directory.html](c3ref/win32_set_directory.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_auto_extension](capi3ref.md#sqlite3_auto_extension) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_data_directory](capi3ref.md#sqlite3_data_directory) [capi3ref.html#sqlite3_deserialize](capi3ref.md#sqlite3_deserialize) [capi3ref.html#sqlite3_exec](capi3ref.md#sqlite3_exec) [capi3ref.html#sqlite3_expanded_sql](capi3ref.md#sqlite3_expanded_sql) [capi3ref.html#sqlite3_free](capi3ref.md#sqlite3_free) [capi3ref.html#sqlite3_free_table](capi3ref.md#sqlite3_free_table) [capi3ref.html#sqlite3_index_info](capi3ref.md#sqlite3_index_info) [capi3ref.html#sqlite3_load_extension](capi3ref.md#sqlite3_load_extension) [capi3ref.html#sqlite3_memory_highwater](capi3ref.md#sqlite3_memory_highwater) [capi3ref.html#sqlite3_mprintf](capi3ref.md#sqlite3_mprintf) [capi3ref.html#sqlite3_str_finish](capi3ref.md#sqlite3_str_finish) [capi3ref.html#sqlite3_temp_directory](capi3ref.md#sqlite3_temp_directory) [capi3ref.html#sqlite3_vtab](capi3ref.md#sqlite3_vtab) [capi3ref.html#sqlite3_win32_set_directory](capi3ref.md#sqlite3_win32_set_directory) [capi3ref.html#sqlitefcntltempfilename](capi3ref.md#sqlitefcntltempfilename) [custombuild.html](custombuild.md) [malloc.html](malloc.md) [printf.html#percentz](printf.md#percentz) [session.html#sqlite3session_changeset](session.md#sqlite3session_changeset) [session/sqlite3session_changeset.html](session/sqlite3session_changeset.md) [vtab.html#colUsed](vtab.md#colUsed) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab) [vtab.html#xconnect](vtab.md#xconnect) [vtab.html#xcreate](vtab.md#xcreate) [vtab.html#xintegrity](vtab.md#xintegrity)
- sqlite3_free_filename → [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_32_0](changes.md#version_3_32_0) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- sqlite3_free_table → [c3ref/free_table.html](c3ref/free_table.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_free_table](capi3ref.md#sqlite3_free_table) [compile.html#omit_get_table](compile.md#omit_get_table)
- sqlite3_get_autocommit → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [lang_transaction.html#immediate](lang_transaction.md#immediate)
- sqlite3_get_auxdata → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/get_clientdata.html](c3ref/get_clientdata.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [capi3ref.html#sqlite3_get_clientdata](capi3ref.md#sqlite3_get_clientdata)
- sqlite3_get_clientdata → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/get_auxdata.html](c3ref/get_auxdata.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_get_auxdata](capi3ref.md#sqlite3_get_auxdata) [changes.html#version_3_44_0](changes.md#version_3_44_0) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md)
- sqlite3_get_table → [arch.html](arch.md) [c3ref/free_table.html](c3ref/free_table.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_free_table](capi3ref.md#sqlite3_free_table) [cintro.html](cintro.md) [compile.html#omit_get_table](compile.md#omit_get_table) [lang.html](lang.md)
- sqlite3_global_recover → [compile.html#omit_deprecated](compile.md#omit_deprecated)
- sqlite3_hard_heap_limit64 → [c3ref/c_config_covering_index_scan.html#sqliteconfigmemstatus](c3ref/c_config_covering_index_scan.md#sqliteconfigmemstatus) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqliteconfigmemstatus](capi3ref.md#sqliteconfigmemstatus) [changes.html#version_3_31_0](changes.md#version_3_31_0) [pragma.html#pragma_hard_heap_limit](pragma.md#pragma_hard_heap_limit) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [security.html](security.md)
- sqlite3_index_info → [c3ref/c_index_constraint_eq.html](c3ref/c_index_constraint_eq.md) [c3ref/c_index_scan_hex.html](c3ref/c_index_scan_hex.md) [c3ref/objlist.html](c3ref/objlist.md) [c3ref/vtab_collation.html](c3ref/vtab_collation.md) [c3ref/vtab_distinct.html](c3ref/vtab_distinct.md) [c3ref/vtab_in.html](c3ref/vtab_in.md) [c3ref/vtab_rhs_value.html](c3ref/vtab_rhs_value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_INDEX_CONSTRAINT_EQ](capi3ref.md#SQLITE_INDEX_CONSTRAINT_EQ) [capi3ref.html#SQLITE_INDEX_SCAN_HEX](capi3ref.md#SQLITE_INDEX_SCAN_HEX) [capi3ref.html#sqlite3_vtab_collation](capi3ref.md#sqlite3_vtab_collation) [capi3ref.html#sqlite3_vtab_distinct](capi3ref.md#sqlite3_vtab_distinct) [capi3ref.html#sqlite3_vtab_in](capi3ref.md#sqlite3_vtab_in) [capi3ref.html#sqlite3_vtab_rhs_value](capi3ref.md#sqlite3_vtab_rhs_value) [changes.html#version_3_10_0](changes.md#version_3_10_0) [changes.html#version_3_8_2](changes.md#version_3_8_2) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [releaselog/3_8_2.html](releaselog/3_8_2.md) [vtab.html#colUsed](vtab.md#colUsed) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab) [vtab.html#xbestindex](vtab.md#xbestindex) [vtab.html#xfilter](vtab.md#xfilter) [vtab.html#xfindfunction](vtab.md#xfindfunction)
- sqlite3_initialize → [35to36.html](35to36.md) [c3ref/c_config_covering_index_scan.html](c3ref/c_config_covering_index_scan.md) [c3ref/complete.html](c3ref/complete.md) [c3ref/config.html](c3ref/config.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/mutex_methods.html](c3ref/mutex_methods.md) [c3ref/pcache_methods2.html#thexinitpagecachemethod](c3ref/pcache_methods2.md#thexinitpagecachemethod) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_CONFIG_COVERING_INDEX_SCAN](capi3ref.md#SQLITE_CONFIG_COVERING_INDEX_SCAN) [capi3ref.html#sqlite3_complete](capi3ref.md#sqlite3_complete) [capi3ref.html#sqlite3_config](capi3ref.md#sqlite3_config) [capi3ref.html#sqlite3_mutex_methods](capi3ref.md#sqlite3_mutex_methods) [capi3ref.html#thexinitpagecachemethod](capi3ref.md#thexinitpagecachemethod) [changes.html#version_3_42_0](changes.md#version_3_42_0) [changes.html#version_3_6_1](changes.md#version_3_6_1) [changes.html#version_3_9_0](changes.md#version_3_9_0) [compile.html#omit_autoinit](compile.md#omit_autoinit) [compile.html#rcmd](compile.md#rcmd) [custombuild.html](custombuild.md) [loadext.html#statext](loadext.md#statext) [releaselog/3_42_0.html](releaselog/3_42_0.md) [releaselog/3_6_0.html](releaselog/3_6_0.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- sqlite3_int64 → [c3ref/c_config_covering_index_scan.html#sqliteconfigmemdbmaxsize](c3ref/c_config_covering_index_scan.md#sqliteconfigmemdbmaxsize) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlsizelimit](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlsizelimit) [c3ref/c_scanstat_est.html#sqlitescanstatnloop](c3ref/c_scanstat_est.md#sqlitescanstatnloop) [c3ref/c_scanstat_est.html#sqlitescanstatnvisit](c3ref/c_scanstat_est.md#sqlitescanstatnvisit) [c3ref/objlist.html](c3ref/objlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqliteconfigmemdbmaxsize](capi3ref.md#sqliteconfigmemdbmaxsize) [capi3ref.html#sqlitefcntlsizelimit](capi3ref.md#sqlitefcntlsizelimit) [capi3ref.html#sqlitescanstatnloop](capi3ref.md#sqlitescanstatnloop) [capi3ref.html#sqlitescanstatnvisit](capi3ref.md#sqlitescanstatnvisit) [carray.html#onearg](carray.md#onearg) [windowfunctions.html#udfwinfunc](windowfunctions.md#udfwinfunc)
- sqlite3_interrupt → [arch.html](arch.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_16_0](changes.md#version_3_16_0) [changes.html#version_3_31_0](changes.md#version_3_31_0) [changes.html#version_3_41_0](changes.md#version_3_41_0) [lang_transaction.html#immediate](lang_transaction.md#immediate) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md) [rescode.html#interrupt](rescode.md#interrupt) [security.html](security.md) [tclsqlite.html#interrupt](tclsqlite.md#interrupt)
- sqlite3_io_methods → [34to35.html](34to35.md) [35to36.html](35to36.md) [c3ref/c_fcntl_begin_atomic_write.html](c3ref/c_fcntl_begin_atomic_write.md) [c3ref/c_iocap_atomic.html](c3ref/c_iocap_atomic.md) [c3ref/c_lock_exclusive.html](c3ref/c_lock_exclusive.md) [c3ref/c_shm_exclusive.html](c3ref/c_shm_exclusive.md) [c3ref/c_shm_nlock.html](c3ref/c_shm_nlock.md) [c3ref/c_sync_dataonly.html](c3ref/c_sync_dataonly.md) [c3ref/file.html](c3ref/file.md) [c3ref/file_control.html](c3ref/file_control.md) [c3ref/objlist.html](c3ref/objlist.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_FCNTL_BEGIN_ATOMIC_WRITE](capi3ref.md#SQLITE_FCNTL_BEGIN_ATOMIC_WRITE) [capi3ref.html#SQLITE_IOCAP_ATOMIC](capi3ref.md#SQLITE_IOCAP_ATOMIC) [capi3ref.html#SQLITE_LOCK_EXCLUSIVE](capi3ref.md#SQLITE_LOCK_EXCLUSIVE) [capi3ref.html#SQLITE_SHM_EXCLUSIVE](capi3ref.md#SQLITE_SHM_EXCLUSIVE) [capi3ref.html#SQLITE_SHM_NLOCK](capi3ref.md#SQLITE_SHM_NLOCK) [capi3ref.html#SQLITE_SYNC_DATAONLY](capi3ref.md#SQLITE_SYNC_DATAONLY) [capi3ref.html#sqlite3_file](capi3ref.md#sqlite3_file) [capi3ref.html#sqlite3_file_control](capi3ref.md#sqlite3_file_control) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen) [changes.html#version_3_48_0](changes.md#version_3_48_0) [compile.html#enable_atomic_write](compile.md#enable_atomic_write) [fileformat2.html#walcksm](fileformat2.md#walcksm) [mmap.html](mmap.md) [releaselog/3_48_0.html](releaselog/3_48_0.md) [rescode.html#ioerr_checkreservedlock](rescode.md#ioerr_checkreservedlock) [rescode.html#ioerr_close](rescode.md#ioerr_close) [rescode.html#ioerr_mmap](rescode.md#ioerr_mmap) [rescode.html#ioerr_rdlock](rescode.md#ioerr_rdlock) [rescode.html#ioerr_seek](rescode.md#ioerr_seek) [rescode.html#ioerr_shmmap](rescode.md#ioerr_shmmap) [rescode.html#ioerr_shmopen](rescode.md#ioerr_shmopen) [rescode.html#ioerr_shmsize](rescode.md#ioerr_shmsize) [rescode.html#ioerr_truncate](rescode.md#ioerr_truncate) [rescode.html#ioerr_unlock](rescode.md#ioerr_unlock) [vfs.html#shim](vfs.md#shim) [wal.html#noshm](wal.md#noshm) [walformat.html#locks](walformat.md#locks)
- sqlite3_is_interrupted → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/interrupt.html](c3ref/interrupt.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_interrupt](capi3ref.md#sqlite3_interrupt) [changes.html#version_3_41_0](changes.md#version_3_41_0) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- sqlite3_keyword_check → [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_24_0](changes.md#version_3_24_0) [lang_keywords.html](lang_keywords.md) [releaselog/3_24_0.html](releaselog/3_24_0.md)
- sqlite3_keyword_count → [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_24_0](changes.md#version_3_24_0) [lang_keywords.html](lang_keywords.md) [releaselog/3_24_0.html](releaselog/3_24_0.md)
- sqlite3_keyword_name → [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_24_0](changes.md#version_3_24_0) [lang_keywords.html](lang_keywords.md) [releaselog/3_24_0.html](releaselog/3_24_0.md)
- sqlite3_last_insert_rowid → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/last_insert_rowid.html](c3ref/last_insert_rowid.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_last_insert_rowid](capi3ref.md#sqlite3_last_insert_rowid) [changes.html#version_3_18_0](changes.md#version_3_18_0) [faq.html#q1](faq.md#q1) [lang_corefunc.html#last_insert_rowid](lang_corefunc.md#last_insert_rowid) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [vtab.html#xupdate](vtab.md#xupdate) [withoutrowid.html](withoutrowid.md)
- sqlite3_libversion → [c3ref/c_scm_branch.html](c3ref/c_scm_branch.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_SCM_BRANCH](capi3ref.md#SQLITE_SCM_BRANCH) [lang_corefunc.html#sqlite_version](lang_corefunc.md#sqlite_version)
- sqlite3_libversion_number → [c3ref/c_scm_branch.html](c3ref/c_scm_branch.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/index_info.html](c3ref/index_info.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_SCM_BRANCH](capi3ref.md#SQLITE_SCM_BRANCH) [capi3ref.html#sqlite3_index_info](capi3ref.md#sqlite3_index_info) [versionnumbers.html](versionnumbers.md) [vtab.html#xbestindex](vtab.md#xbestindex)
- sqlite3_limit → [c3ref/bind_blob.html](c3ref/bind_blob.md) [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/c_limit_attached.html](c3ref/c_limit_attached.md) [c3ref/create_function.html](c3ref/create_function.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/limit.html](c3ref/limit.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/str_new.html](c3ref/str_new.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_LIMIT_ATTACHED](capi3ref.md#SQLITE_LIMIT_ATTACHED) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_bind_blob](capi3ref.md#sqlite3_bind_blob) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [capi3ref.html#sqlite3_limit](capi3ref.md#sqlite3_limit) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlite3_str_new](capi3ref.md#sqlite3_str_new) [changes.html#version_3_39_1](changes.md#version_3_39_1) [changes.html#version_3_53_0](changes.md#version_3_53_0) [changes.html#version_3_5_8](changes.md#version_3_5_8) [changes.html#version_3_8_7](changes.md#version_3_8_7) [cintro.html](cintro.md) [compile.html#max_worker_threads](compile.md#max_worker_threads) [compile.html#printf_precision_limit](compile.md#printf_precision_limit) [compile.html#yystackdepth](compile.md#yystackdepth) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html#tablecoldef](lang_createtable.md#tablecoldef) [lang_expr.html#varparam](lang_expr.md#varparam) [limits.html](limits.md) [limits.html#max_attached](limits.md#max_attached) [limits.html#max_column](limits.md#max_column) [limits.html#max_compound_select](limits.md#max_compound_select) [limits.html#max_expr_depth](limits.md#max_expr_depth) [limits.html#max_function_arg](limits.md#max_function_arg) [limits.html#max_length](limits.md#max_length) [limits.html#max_like_pattern_length](limits.md#max_like_pattern_length) [limits.html#max_sql_length](limits.md#max_sql_length) [limits.html#max_variable_number](limits.md#max_variable_number) [oldnews.html](oldnews.md) [pragma.html#pragma_recursive_triggers](pragma.md#pragma_recursive_triggers) [pragma.html#pragma_threads](pragma.md#pragma_threads) [privatebranch.html](privatebranch.md) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [releaselog/3_5_8.html](releaselog/3_5_8.md) [releaselog/3_8_7.html](releaselog/3_8_7.md) [rescode.html#toobig](rescode.md#toobig) [security.html](security.md)
- sqlite3_load_extension → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigenableloadextension](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenableloadextension) [c3ref/enable_load_extension.html](c3ref/enable_load_extension.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/load_extension.html](c3ref/load_extension.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_enable_load_extension](capi3ref.md#sqlite3_enable_load_extension) [capi3ref.html#sqlite3_load_extension](capi3ref.md#sqlite3_load_extension) [capi3ref.html#sqlitedbconfigenableloadextension](capi3ref.md#sqlitedbconfigenableloadextension) [changes.html#version_3_13_0](changes.md#version_3_13_0) [changes.html#version_3_7_17](changes.md#version_3_7_17) [cksumvfs.html](cksumvfs.md) [compile.html#omit_load_extension](compile.md#omit_load_extension) [csv.html](csv.md) [howtocompile.html#cli](howtocompile.md#cli) [lang_corefunc.html#load_extension](lang_corefunc.md#load_extension) [loadext.html](loadext.md) [loadext.html#persist](loadext.md#persist) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_7_17.html](releaselog/3_7_17.md) [rescode.html#ok_load_permanently](rescode.md#ok_load_permanently)
- sqlite3_log → [c3ref/c_config_covering_index_scan.html#sqliteconfiglog](c3ref/c_config_covering_index_scan.md#sqliteconfiglog) [c3ref/c_prepare_dont_log.html#sqlitepreparedontlog](c3ref/c_prepare_dont_log.md#sqlitepreparedontlog) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/log.html](c3ref/log.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_log](capi3ref.md#sqlite3_log) [capi3ref.html#sqliteconfiglog](capi3ref.md#sqliteconfiglog) [capi3ref.html#sqlitepreparedontlog](capi3ref.md#sqlitepreparedontlog) [changes.html#version_3_6_23](changes.md#version_3_6_23) [errlog.html](errlog.md) [oldnews.html](oldnews.md) [releaselog/3_6_23.html](releaselog/3_6_23.md) [rescode.html#notice](rescode.md#notice) [rescode.html#notice_recover_rollback](rescode.md#notice_recover_rollback) [rescode.html#notice_recover_wal](rescode.md#notice_recover_wal) [rescode.html#warning](rescode.md#warning) [rescode.html#warning_autoindex](rescode.md#warning_autoindex)
- sqlite3_malloc → [34to35.html](34to35.md) [c3ref/c_config_covering_index_scan.html#sqliteconfigpagecache](c3ref/c_config_covering_index_scan.md#sqliteconfigpagecache) [c3ref/c_dbconfig_defensive.html#sqlitedbconfiglookaside](c3ref/c_dbconfig_defensive.md#sqlitedbconfiglookaside) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntltempfilename](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntltempfilename) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlvfsname](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlvfsname) [c3ref/c_status_malloc_count.html#sqlitestatusmallocsize](c3ref/c_status_malloc_count.md#sqlitestatusmallocsize) [c3ref/c_status_malloc_count.html#sqlitestatusmemoryused](c3ref/c_status_malloc_count.md#sqlitestatusmemoryused) [c3ref/c_status_malloc_count.html#sqlitestatuspagecacheoverflow](c3ref/c_status_malloc_count.md#sqlitestatuspagecacheoverflow) [c3ref/data_directory.html](c3ref/data_directory.md) [c3ref/exec.html](c3ref/exec.md) [c3ref/expanded_sql.html](c3ref/expanded_sql.md) [c3ref/free.html](c3ref/free.md) [c3ref/free_table.html](c3ref/free_table.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/load_extension.html](c3ref/load_extension.md) [c3ref/mem_methods.html](c3ref/mem_methods.md) [c3ref/memory_highwater.html](c3ref/memory_highwater.md) [c3ref/mutex_methods.html](c3ref/mutex_methods.md) [c3ref/result_blob.html](c3ref/result_blob.md) [c3ref/temp_directory.html](c3ref/temp_directory.md) [c3ref/win32_set_directory.html](c3ref/win32_set_directory.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_data_directory](capi3ref.md#sqlite3_data_directory) [capi3ref.html#sqlite3_exec](capi3ref.md#sqlite3_exec) [capi3ref.html#sqlite3_expanded_sql](capi3ref.md#sqlite3_expanded_sql) [capi3ref.html#sqlite3_free](capi3ref.md#sqlite3_free) [capi3ref.html#sqlite3_free_table](capi3ref.md#sqlite3_free_table) [capi3ref.html#sqlite3_load_extension](capi3ref.md#sqlite3_load_extension) [capi3ref.html#sqlite3_mem_methods](capi3ref.md#sqlite3_mem_methods) [capi3ref.html#sqlite3_memory_highwater](capi3ref.md#sqlite3_memory_highwater) [capi3ref.html#sqlite3_mutex_methods](capi3ref.md#sqlite3_mutex_methods) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [capi3ref.html#sqlite3_temp_directory](capi3ref.md#sqlite3_temp_directory) [capi3ref.html#sqlite3_win32_set_directory](capi3ref.md#sqlite3_win32_set_directory) [capi3ref.html#sqliteconfigpagecache](capi3ref.md#sqliteconfigpagecache) [capi3ref.html#sqlitedbconfiglookaside](capi3ref.md#sqlitedbconfiglookaside) [capi3ref.html#sqlitefcntltempfilename](capi3ref.md#sqlitefcntltempfilename) [capi3ref.html#sqlitefcntlvfsname](capi3ref.md#sqlitefcntlvfsname) [capi3ref.html#sqlitestatusmallocsize](capi3ref.md#sqlitestatusmallocsize) [capi3ref.html#sqlitestatusmemoryused](capi3ref.md#sqlitestatusmemoryused) [capi3ref.html#sqlitestatuspagecacheoverflow](capi3ref.md#sqlitestatuspagecacheoverflow) [compile.html#default_pcache_initsz](compile.md#default_pcache_initsz) [compile.html#rcmd](compile.md#rcmd) [custombuild.html](custombuild.md) [malloc.html](malloc.md) [malloc.html#lookaside](malloc.md#lookaside) [malloc.html#memsys5](malloc.md#memsys5) [rescode.html#nomem](rescode.md#nomem) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab) [vtab.html#xconnect](vtab.md#xconnect) [vtab.html#xcreate](vtab.md#xcreate) [vtab.html#xupdate](vtab.md#xupdate)
- sqlite3_malloc64 → [c3ref/c_deserialize_freeonclose.html](c3ref/c_deserialize_freeonclose.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/mprintf.html](c3ref/mprintf.md) [c3ref/serialize.html](c3ref/serialize.md) [c3ref/str_finish.html](c3ref/str_finish.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_DESERIALIZE_FREEONCLOSE](capi3ref.md#SQLITE_DESERIALIZE_FREEONCLOSE) [capi3ref.html#sqlite3_mprintf](capi3ref.md#sqlite3_mprintf) [capi3ref.html#sqlite3_serialize](capi3ref.md#sqlite3_serialize) [capi3ref.html#sqlite3_str_finish](capi3ref.md#sqlite3_str_finish) [changes.html#version_3_8_7](changes.md#version_3_8_7) [compile.html#max_allocation_size](compile.md#max_allocation_size) [printf.html](printf.md) [releaselog/3_8_7.html](releaselog/3_8_7.md) [vtab.html#xintegrity](vtab.md#xintegrity)
- sqlite3_mem_methods → [35to36.html](35to36.md) [c3ref/c_config_covering_index_scan.html#sqliteconfiggetmalloc](c3ref/c_config_covering_index_scan.md#sqliteconfiggetmalloc) [c3ref/c_config_covering_index_scan.html#sqliteconfigmalloc](c3ref/c_config_covering_index_scan.md#sqliteconfigmalloc) [c3ref/c_status_malloc_count.html#sqlitestatusmemoryused](c3ref/c_status_malloc_count.md#sqlitestatusmemoryused) [c3ref/objlist.html](c3ref/objlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqliteconfiggetmalloc](capi3ref.md#sqliteconfiggetmalloc) [capi3ref.html#sqliteconfigmalloc](capi3ref.md#sqliteconfigmalloc) [capi3ref.html#sqlitestatusmemoryused](capi3ref.md#sqlitestatusmemoryused) [custombuild.html](custombuild.md) [malloc.html#memsysx](malloc.md#memsysx)
- sqlite3_memory_alarm → [34to35.html](34to35.md) [changes.html#version_3_9_0](changes.md#version_3_9_0) [compile.html#omit_deprecated](compile.md#omit_deprecated) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- sqlite3_memory_highwater → [34to35.html](34to35.md) [35to36.html](35to36.md) [c3ref/c_config_covering_index_scan.html#sqliteconfigmemstatus](c3ref/c_config_covering_index_scan.md#sqliteconfigmemstatus) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/memory_highwater.html](c3ref/memory_highwater.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_memory_highwater](capi3ref.md#sqlite3_memory_highwater) [capi3ref.html#sqliteconfigmemstatus](capi3ref.md#sqliteconfigmemstatus) [changes.html#version_3_8_11](changes.md#version_3_8_11) [compile.html#default_memstatus](compile.md#default_memstatus) [custombuild.html](custombuild.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [security.html](security.md)
- sqlite3_memory_used → [34to35.html](34to35.md) [35to36.html](35to36.md) [c3ref/c_config_covering_index_scan.html#sqliteconfigmemstatus](c3ref/c_config_covering_index_scan.md#sqliteconfigmemstatus) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/memory_highwater.html](c3ref/memory_highwater.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_memory_highwater](capi3ref.md#sqlite3_memory_highwater) [capi3ref.html#sqliteconfigmemstatus](capi3ref.md#sqliteconfigmemstatus) [changes.html#version_3_8_11](changes.md#version_3_8_11) [compile.html#default_memstatus](compile.md#default_memstatus) [compile.html#max_memory](compile.md#max_memory) [custombuild.html](custombuild.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- sqlite3_module → [c3ref/objlist.html](c3ref/objlist.md) [capi3ref.html](capi3ref.md) [vtab.html#customvtab](vtab.md#customvtab) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab) [vtab.html#xBegin](vtab.md#xBegin) [vtab.html#xcommit](vtab.md#xcommit) [vtab.html#xconnect](vtab.md#xconnect) [vtab.html#xcreate](vtab.md#xcreate) [vtab.html#xrollback](vtab.md#xrollback) [vtab.html#xsync](vtab.md#xsync) [vtab.html#xupdate](vtab.md#xupdate)
- sqlite3_module.xBestIndex → [changes.html#version_3_10_0](changes.md#version_3_10_0) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [vtab.html#tabfunc2](vtab.md#tabfunc2)
- sqlite3_module.xClose → [c3ref/vtab_cursor.html](c3ref/vtab_cursor.md) [capi3ref.html#sqlite3_vtab_cursor](capi3ref.md#sqlite3_vtab_cursor) [vtab.html#xopen](vtab.md#xopen)
- sqlite3_module.xOpen → [c3ref/vtab_cursor.html](c3ref/vtab_cursor.md) [capi3ref.html#sqlite3_vtab_cursor](capi3ref.md#sqlite3_vtab_cursor) [vtab.html#xclose](vtab.md#xclose) [vtab.html#xfilter](vtab.md#xfilter)
- sqlite3_module.xRename → [pragma.html#pragma_legacy_alter_table](pragma.md#pragma_legacy_alter_table)
- sqlite3_module.xSync → [vtab.html#xcommit](vtab.md#xcommit)
- sqlite3_mprintf → [arch.html](arch.md) [c3ref/auto_extension.html](c3ref/auto_extension.md) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlpragma](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlpragma) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/vtab.html](c3ref/vtab.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_auto_extension](capi3ref.md#sqlite3_auto_extension) [capi3ref.html#sqlite3_vtab](capi3ref.md#sqlite3_vtab) [capi3ref.html#sqlitefcntlpragma](capi3ref.md#sqlitefcntlpragma) [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_50_0](changes.md#version_3_50_0) [changes.html#version_3_5_9](changes.md#version_3_5_9) [changes.html#version_3_7_9](changes.md#version_3_7_9) [compile.html#omit_autoinit](compile.md#omit_autoinit) [compile.html#printf_precision_limit](compile.md#printf_precision_limit) [lang_corefunc.html#format](lang_corefunc.md#format) [printf.html](printf.md) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md) [releaselog/3_5_9.html](releaselog/3_5_9.md) [releaselog/3_7_9.html](releaselog/3_7_9.md) [vtab.html#colUsed](vtab.md#colUsed) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab) [vtab.html#xconnect](vtab.md#xconnect) [vtab.html#xcreate](vtab.md#xcreate) [vtab.html#xupdate](vtab.md#xupdate)
- sqlite3_msize → [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_8_7](changes.md#version_3_8_7) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- sqlite3_mutex → [34to35.html](34to35.md) [c3ref/db_mutex.html](c3ref/db_mutex.md) [c3ref/mutex.html](c3ref/mutex.md) [c3ref/objlist.html](c3ref/objlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_db_mutex](capi3ref.md#sqlite3_db_mutex) [capi3ref.html#sqlite3_mutex](capi3ref.md#sqlite3_mutex)
- sqlite3_mutex_alloc → [34to35.html](34to35.md) [c3ref/c_mutex_fast.html](c3ref/c_mutex_fast.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/mutex.html](c3ref/mutex.md) [c3ref/mutex_methods.html](c3ref/mutex_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_MUTEX_FAST](capi3ref.md#SQLITE_MUTEX_FAST) [capi3ref.html#sqlite3_mutex](capi3ref.md#sqlite3_mutex) [capi3ref.html#sqlite3_mutex_methods](capi3ref.md#sqlite3_mutex_methods)
- sqlite3_mutex_enter → [34to35.html](34to35.md) [35to36.html](35to36.md) [c3ref/errcode.html](c3ref/errcode.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/mutex_methods.html](c3ref/mutex_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_errcode](capi3ref.md#sqlite3_errcode) [capi3ref.html#sqlite3_mutex_methods](capi3ref.md#sqlite3_mutex_methods)
- sqlite3_mutex_free → [34to35.html](34to35.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/mutex_methods.html](c3ref/mutex_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_mutex_methods](capi3ref.md#sqlite3_mutex_methods)
- sqlite3_mutex_held → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/mutex_alloc.html](c3ref/mutex_alloc.md) [c3ref/mutex_methods.html](c3ref/mutex_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_mutex_alloc](capi3ref.md#sqlite3_mutex_alloc) [capi3ref.html#sqlite3_mutex_methods](capi3ref.md#sqlite3_mutex_methods) [testing.html#mutextesting](testing.md#mutextesting)
- sqlite3_mutex_leave → [34to35.html](34to35.md) [c3ref/errcode.html](c3ref/errcode.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/mutex_methods.html](c3ref/mutex_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_errcode](capi3ref.md#sqlite3_errcode) [capi3ref.html#sqlite3_mutex_methods](capi3ref.md#sqlite3_mutex_methods)
- sqlite3_mutex_methods → [35to36.html](35to36.md) [c3ref/c_config_covering_index_scan.html#sqliteconfiggetmutex](c3ref/c_config_covering_index_scan.md#sqliteconfiggetmutex) [c3ref/c_config_covering_index_scan.html#sqliteconfigmutex](c3ref/c_config_covering_index_scan.md#sqliteconfigmutex) [c3ref/objlist.html](c3ref/objlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqliteconfiggetmutex](capi3ref.md#sqliteconfiggetmutex) [capi3ref.html#sqliteconfigmutex](capi3ref.md#sqliteconfigmutex)
- sqlite3_mutex_notheld → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/mutex_alloc.html](c3ref/mutex_alloc.md) [c3ref/mutex_methods.html](c3ref/mutex_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_mutex_alloc](capi3ref.md#sqlite3_mutex_alloc) [capi3ref.html#sqlite3_mutex_methods](capi3ref.md#sqlite3_mutex_methods) [testing.html#mutextesting](testing.md#mutextesting)
- sqlite3_mutex_try → [34to35.html](34to35.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/mutex_methods.html](c3ref/mutex_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_mutex_methods](capi3ref.md#sqlite3_mutex_methods)
- sqlite3_next_stmt → [35to36.html](35to36.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/next_stmt.html](c3ref/next_stmt.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/stmt_busy.html](c3ref/stmt_busy.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_next_stmt](capi3ref.md#sqlite3_next_stmt) [capi3ref.html#sqlite3_stmt_busy](capi3ref.md#sqlite3_stmt_busy) [changes.html#version_3_6_1](changes.md#version_3_6_1) [releaselog/3_6_0.html](releaselog/3_6_0.md)
- sqlite3_normalized_sql → [c3ref/c_prepare_dont_log.html#sqlitepreparenormalize](c3ref/c_prepare_dont_log.md#sqlitepreparenormalize) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqlitepreparenormalize](capi3ref.md#sqlitepreparenormalize) [changes.html#version_3_26_0](changes.md#version_3_26_0) [changes.html#version_3_27_0](changes.md#version_3_27_0) [compile.html#enable_normalize](compile.md#enable_normalize) [releaselog/3_26_0.html](releaselog/3_26_0.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- sqlite3_open → [34to35.html](34to35.md) [backup.html](backup.md) [c3ref/auto_extension.html](c3ref/auto_extension.md) [c3ref/c_config_covering_index_scan.html#sqliteconfiguri](c3ref/c_config_covering_index_scan.md#sqliteconfiguri) [c3ref/close.html](c3ref/close.md) [c3ref/enable_shared_cache.html](c3ref/enable_shared_cache.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/initialize.html](c3ref/initialize.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/temp_directory.html](c3ref/temp_directory.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3.html](capi3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_auto_extension](capi3ref.md#sqlite3_auto_extension) [capi3ref.html#sqlite3_close](capi3ref.md#sqlite3_close) [capi3ref.html#sqlite3_enable_shared_cache](capi3ref.md#sqlite3_enable_shared_cache) [capi3ref.html#sqlite3_initialize](capi3ref.md#sqlite3_initialize) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_temp_directory](capi3ref.md#sqlite3_temp_directory) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen) [capi3ref.html#sqliteconfiguri](capi3ref.md#sqliteconfiguri) [cintro.html](cintro.md) [cksumvfs.html](cksumvfs.md) [cli.html#dotopen](cli.md#dotopen) [compile.html#omit_autoinit](compile.md#omit_autoinit) [compile.html#omit_memorydb](compile.md#omit_memorydb) [compile.html#rcmd](compile.md#rcmd) [inmemorydb.html](inmemorydb.md) [inmemorydb.html#temp_db](inmemorydb.md#temp_db) [isolation.html](isolation.md) [lang_attach.html](lang_attach.md) [malloc.html#lookaside](malloc.md#lookaside) [malloc.html#nofrag](malloc.md#nofrag) [pragma.html#pragma_encoding](pragma.md#pragma_encoding) [quickstart.html](quickstart.md) [rescode.html#cantopen_symlink](rescode.md#cantopen_symlink) [sharedcache.html#dontuse](sharedcache.md#dontuse) [shortnames.html](shortnames.md) [tempfiles.html#superjrnl](tempfiles.md#superjrnl) [threadsafe.html](threadsafe.md) [uri.html](uri.md) [vfs.html](vfs.md) [wal.html#walfile](wal.md#walfile)
- sqlite3_open16 → [34to35.html](34to35.md) [c3ref/auto_extension.html](c3ref/auto_extension.md) [c3ref/c_config_covering_index_scan.html#sqliteconfiguri](c3ref/c_config_covering_index_scan.md#sqliteconfiguri) [c3ref/close.html](c3ref/close.md) [c3ref/enable_shared_cache.html](c3ref/enable_shared_cache.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_auto_extension](capi3ref.md#sqlite3_auto_extension) [capi3ref.html#sqlite3_close](capi3ref.md#sqlite3_close) [capi3ref.html#sqlite3_enable_shared_cache](capi3ref.md#sqlite3_enable_shared_cache) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen) [capi3ref.html#sqliteconfiguri](capi3ref.md#sqliteconfiguri) [cintro.html](cintro.md) [compile.html#omit_memorydb](compile.md#omit_memorydb) [inmemorydb.html](inmemorydb.md) [sharedcache.html#dontuse](sharedcache.md#dontuse) [tempfiles.html#superjrnl](tempfiles.md#superjrnl) [threadsafe.html](threadsafe.md) [uri.html](uri.md) [vfs.html](vfs.md)
- sqlite3_open_v2 → [34to35.html](34to35.md) [35to36.html](35to36.md) [c3ref/auto_extension.html](c3ref/auto_extension.md) [c3ref/c_config_covering_index_scan.html#sqliteconfiguri](c3ref/c_config_covering_index_scan.md#sqliteconfiguri) [c3ref/c_open_autoproxy.html](c3ref/c_open_autoproxy.md) [c3ref/close.html](c3ref/close.md) [c3ref/enable_shared_cache.html](c3ref/enable_shared_cache.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/open.html#openexrescode](c3ref/open.md#openexrescode) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/system_errno.html](c3ref/system_errno.md) [c3ref/temp_directory.html](c3ref/temp_directory.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_OPEN_AUTOPROXY](capi3ref.md#SQLITE_OPEN_AUTOPROXY) [capi3ref.html#openexrescode](capi3ref.md#openexrescode) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_auto_extension](capi3ref.md#sqlite3_auto_extension) [capi3ref.html#sqlite3_close](capi3ref.md#sqlite3_close) [capi3ref.html#sqlite3_enable_shared_cache](capi3ref.md#sqlite3_enable_shared_cache) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_system_errno](capi3ref.md#sqlite3_system_errno) [capi3ref.html#sqlite3_temp_directory](capi3ref.md#sqlite3_temp_directory) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen) [capi3ref.html#sqliteconfiguri](capi3ref.md#sqliteconfiguri) [changes.html#version_3_31_0](changes.md#version_3_31_0) [changes.html#version_3_37_0](changes.md#version_3_37_0) [changes.html#version_3_39_0](changes.md#version_3_39_0) [changes.html#version_3_5_0](changes.md#version_3_5_0) [changes.html#version_3_6_1](changes.md#version_3_6_1) [changes.html#version_3_6_18](changes.md#version_3_6_18) [cintro.html](cintro.md) [cksumvfs.html](cksumvfs.md) [compile.html#enable_locking_style](compile.md#enable_locking_style) [compile.html#omit_memorydb](compile.md#omit_memorydb) [compile.html#threadsafe](compile.md#threadsafe) [custombuild.html](custombuild.md) [howtocorrupt.html#posix_close_bug](howtocorrupt.md#posix_close_bug) [howtocorrupt.html#stalefd](howtocorrupt.md#stalefd) [inmemorydb.html](inmemorydb.md) [lang_attach.html](lang_attach.md) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md) [releaselog/3_39_0.html](releaselog/3_39_0.md) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md) [releaselog/3_5_0.html](releaselog/3_5_0.md) [releaselog/3_6_0.html](releaselog/3_6_0.md) [releaselog/3_6_18.html](releaselog/3_6_18.md) [sharedcache.html#dontuse](sharedcache.md#dontuse) [tempfiles.html#superjrnl](tempfiles.md#superjrnl) [threadsafe.html](threadsafe.md) [uri.html](uri.md) [uri.html#urimodeof](uri.md#urimodeof) [vfs.html](vfs.md)
- sqlite3_os_end → [35to36.html](35to36.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [compile.html#os_other](compile.md#os_other) [custombuild.html](custombuild.md)
- sqlite3_os_init → [35to36.html](35to36.md) [c3ref/config.html](c3ref/config.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_config](capi3ref.md#sqlite3_config) [compile.html#os_other](compile.md#os_other) [custombuild.html](custombuild.md)
- sqlite3_overload_function → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3)
- sqlite3_pcache → [c3ref/objlist.html](c3ref/objlist.md) [c3ref/pcache_methods2.html#thexdestroypagecachemethod](c3ref/pcache_methods2.md#thexdestroypagecachemethod) [capi3ref.html](capi3ref.md) [capi3ref.html#thexdestroypagecachemethod](capi3ref.md#thexdestroypagecachemethod)
- sqlite3_pcache_methods2 → [c3ref/c_config_covering_index_scan.html#sqliteconfiggetpcache2](c3ref/c_config_covering_index_scan.md#sqliteconfiggetpcache2) [c3ref/c_config_covering_index_scan.html#sqliteconfigpcache2](c3ref/c_config_covering_index_scan.md#sqliteconfigpcache2) [c3ref/objlist.html](c3ref/objlist.md) [c3ref/pcache.html](c3ref/pcache.md) [c3ref/pcache_page.html](c3ref/pcache_page.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_pcache](capi3ref.md#sqlite3_pcache) [capi3ref.html#sqlite3_pcache_page](capi3ref.md#sqlite3_pcache_page) [capi3ref.html#sqliteconfiggetpcache2](capi3ref.md#sqliteconfiggetpcache2) [capi3ref.html#sqliteconfigpcache2](capi3ref.md#sqliteconfigpcache2) [changes.html#version_3_6_6](changes.md#version_3_6_6) [changes.html#version_3_7_10](changes.md#version_3_7_10) [pragma.html#pragma_cache_size](pragma.md#pragma_cache_size) [releaselog/3_6_6.html](releaselog/3_6_6.md) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- sqlite3_pcache_page → [c3ref/objlist.html](c3ref/objlist.md) [capi3ref.html](capi3ref.md)
- sqlite3_prepare → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigstmtscanstatus](c3ref/c_dbconfig_defensive.md#sqlitedbconfigstmtscanstatus) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/progress_handler.html](c3ref/progress_handler.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/step.html](c3ref/step.md) [c3ref/stmt.html](c3ref/stmt.md) [c3ref/stmt_explain.html](c3ref/stmt_explain.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_progress_handler](capi3ref.md#sqlite3_progress_handler) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqlite3_stmt_explain](capi3ref.md#sqlite3_stmt_explain) [capi3ref.html#sqlitedbconfigstmtscanstatus](capi3ref.md#sqlitedbconfigstmtscanstatus) [changes.html#version_3_26_0](changes.md#version_3_26_0) [changes.html#version_3_41_0](changes.md#version_3_41_0) [changes.html#version_3_46_1](changes.md#version_3_46_1) [cintro.html](cintro.md) [cli.html#dotrules](cli.md#dotrules) [faq.html#q15](faq.md#q15) [lang.html](lang.md) [lang_explain.html](lang_explain.md) [limits.html#max_sql_length](limits.md#max_sql_length) [oldnews.html](oldnews.md) [optoverview.html#like_opt](optoverview.md#like_opt) [pragma.html](pragma.md) [pragma.html#pragma_foreign_keys](pragma.md#pragma_foreign_keys) [pragma.html#pragma_recursive_triggers](pragma.md#pragma_recursive_triggers) [pragma.html#pragma_schema_version](pragma.md#pragma_schema_version) [queryplanner-ng.html#qpstab](queryplanner-ng.md#qpstab) [releaselog/3_26_0.html](releaselog/3_26_0.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md) [releaselog/3_46_1.html](releaselog/3_46_1.md) [rescode.html#schema](rescode.md#schema) [stmt.html](stmt.md) [unlock_notify.html](unlock_notify.md) [vtab.html#obc](vtab.md#obc) [vtab.html#xbestindex](vtab.md#xbestindex) [vtab.html#xfindfunction](vtab.md#xfindfunction) [whybytecode.html](whybytecode.md)
- sqlite3_prepare16 → [c3ref/bind_parameter_name.html](c3ref/bind_parameter_name.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/step.html](c3ref/step.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_bind_parameter_name](capi3ref.md#sqlite3_bind_parameter_name) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [compile.html#omit_utf16](compile.md#omit_utf16) [lang.html](lang.md) [optoverview.html#like_opt](optoverview.md#like_opt) [rescode.html#schema](rescode.md#schema)
- sqlite3_prepare16_v2 → [c3ref/bind_parameter_index.html](c3ref/bind_parameter_index.md) [c3ref/bind_parameter_name.html](c3ref/bind_parameter_name.md) [c3ref/expanded_sql.html](c3ref/expanded_sql.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/step.html](c3ref/step.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_bind_parameter_index](capi3ref.md#sqlite3_bind_parameter_index) [capi3ref.html#sqlite3_bind_parameter_name](capi3ref.md#sqlite3_bind_parameter_name) [capi3ref.html#sqlite3_expanded_sql](capi3ref.md#sqlite3_expanded_sql) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [lang.html](lang.md) [optoverview.html#like_opt](optoverview.md#like_opt)
- sqlite3_prepare16_v3 → [c3ref/bind_parameter_index.html](c3ref/bind_parameter_index.md) [c3ref/bind_parameter_name.html](c3ref/bind_parameter_name.md) [c3ref/c_prepare_dont_log.html](c3ref/c_prepare_dont_log.md) [c3ref/c_prepare_dont_log.html#sqlitepreparepersistent](c3ref/c_prepare_dont_log.md#sqlitepreparepersistent) [c3ref/expanded_sql.html](c3ref/expanded_sql.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/step.html](c3ref/step.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_PREPARE_DONT_LOG](capi3ref.md#SQLITE_PREPARE_DONT_LOG) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_bind_parameter_index](capi3ref.md#sqlite3_bind_parameter_index) [capi3ref.html#sqlite3_bind_parameter_name](capi3ref.md#sqlite3_bind_parameter_name) [capi3ref.html#sqlite3_expanded_sql](capi3ref.md#sqlite3_expanded_sql) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqlitepreparepersistent](capi3ref.md#sqlitepreparepersistent) [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- sqlite3_prepare_v2 → [arch.html](arch.md) [c3ref/bind_blob.html](c3ref/bind_blob.md) [c3ref/c_limit_attached.html#sqlitelimitvdbeop](c3ref/c_limit_attached.md#sqlitelimitvdbeop) [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/commit_hook.html](c3ref/commit_hook.md) [c3ref/db_handle.html](c3ref/db_handle.md) [c3ref/exec.html](c3ref/exec.md) [c3ref/expanded_sql.html](c3ref/expanded_sql.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/progress_handler.html](c3ref/progress_handler.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/step.html](c3ref/step.md) [c3ref/stmt.html](c3ref/stmt.md) [c3ref/stmt_explain.html](c3ref/stmt_explain.md) [c3ref/update_hook.html](c3ref/update_hook.md) [capi3.html](capi3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_bind_blob](capi3ref.md#sqlite3_bind_blob) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_commit_hook](capi3ref.md#sqlite3_commit_hook) [capi3ref.html#sqlite3_db_handle](capi3ref.md#sqlite3_db_handle) [capi3ref.html#sqlite3_exec](capi3ref.md#sqlite3_exec) [capi3ref.html#sqlite3_expanded_sql](capi3ref.md#sqlite3_expanded_sql) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_progress_handler](capi3ref.md#sqlite3_progress_handler) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqlite3_stmt_explain](capi3ref.md#sqlite3_stmt_explain) [capi3ref.html#sqlite3_update_hook](capi3ref.md#sqlite3_update_hook) [capi3ref.html#sqlitelimitvdbeop](capi3ref.md#sqlitelimitvdbeop) [changes.html#version_3_15_0](changes.md#version_3_15_0) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_5_3](changes.md#version_3_5_3) [cintro.html](cintro.md) [errlog.html](errlog.md) [faq.html#q15](faq.md#q15) [lang.html](lang.md) [lang_comment.html](lang_comment.md) [limits.html#max_column](limits.md#max_column) [malloc.html#lookaside](malloc.md#lookaside) [malloc.html#nofrag](malloc.md#nofrag) [news.html](news.md) [opcode.html](opcode.md) [optoverview.html#like_opt](optoverview.md#like_opt) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_5_3.html](releaselog/3_5_3.md) [rescode.html#error_missing_collseq](rescode.md#error_missing_collseq) [rescode.html#error_retry](rescode.md#error_retry) [rescode.html#schema](rescode.md#schema) [rescode.html#toobig](rescode.md#toobig) [unlock_notify.html](unlock_notify.md) [vfs.html](vfs.md)
- sqlite3_prepare_v3 → [c3ref/c_prepare_dont_log.html](c3ref/c_prepare_dont_log.md) [c3ref/c_prepare_dont_log.html#sqlitepreparefromddl](c3ref/c_prepare_dont_log.md#sqlitepreparefromddl) [c3ref/c_prepare_dont_log.html#sqlitepreparepersistent](c3ref/c_prepare_dont_log.md#sqlitepreparepersistent) [c3ref/expanded_sql.html](c3ref/expanded_sql.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/step.html](c3ref/step.md) [c3ref/stmt.html](c3ref/stmt.md) [c3ref/stmt_explain.html](c3ref/stmt_explain.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_PREPARE_DONT_LOG](capi3ref.md#SQLITE_PREPARE_DONT_LOG) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_expanded_sql](capi3ref.md#sqlite3_expanded_sql) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqlite3_stmt_explain](capi3ref.md#sqlite3_stmt_explain) [capi3ref.html#sqlitepreparefromddl](capi3ref.md#sqlitepreparefromddl) [capi3ref.html#sqlitepreparepersistent](capi3ref.md#sqlitepreparepersistent) [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_48_0](changes.md#version_3_48_0) [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_48_0.html](releaselog/3_48_0.md) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [security.html#baddb](security.md#baddb) [vtab.html#customvtab](vtab.md#customvtab)
- sqlite3_preupdate_blobwrite → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite)
- sqlite3_preupdate_count → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite)
- sqlite3_preupdate_depth → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite)
- sqlite3_preupdate_hook → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/update_hook.html](c3ref/update_hook.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite) [capi3ref.html#sqlite3_update_hook](capi3ref.md#sqlite3_update_hook) [compile.html#enable_preupdate_hook](compile.md#enable_preupdate_hook) [session.html#sqlite3session_create](session.md#sqlite3session_create) [session/sqlite3session_create.html](session/sqlite3session_create.md)
- sqlite3_preupdate_new → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite)
- sqlite3_preupdate_old → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite)
- sqlite3_profile → [c3ref/c_trace.html#sqlitetraceprofile](c3ref/c_trace.md#sqlitetraceprofile) [c3ref/trace_v2.html](c3ref/trace_v2.md) [capi3ref.html#sqlite3_trace_v2](capi3ref.md#sqlite3_trace_v2) [capi3ref.html#sqlitetraceprofile](capi3ref.md#sqlitetraceprofile) [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_8_11](changes.md#version_3_8_11) [compile.html#omit_trace](compile.md#omit_trace) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- sqlite3_progress_handler → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_41_0](changes.md#version_3_41_0) [compile.html#rcmd](compile.md#rcmd) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md) [security.html](security.md)
- sqlite3_randomness → [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_5_8](changes.md#version_3_5_8) [changes.html#version_3_8_3](changes.md#version_3_8_3) [oldnews.html](oldnews.md) [releaselog/3_5_8.html](releaselog/3_5_8.md) [releaselog/3_8_3.html](releaselog/3_8_3.md)
- sqlite3_realloc → [34to35.html](34to35.md) [c3ref/c_status_malloc_count.html#sqlitestatusmallocsize](c3ref/c_status_malloc_count.md#sqlitestatusmallocsize) [c3ref/free.html](c3ref/free.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/mem_methods.html](c3ref/mem_methods.md) [c3ref/memory_highwater.html](c3ref/memory_highwater.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_free](capi3ref.md#sqlite3_free) [capi3ref.html#sqlite3_mem_methods](capi3ref.md#sqlite3_mem_methods) [capi3ref.html#sqlite3_memory_highwater](capi3ref.md#sqlite3_memory_highwater) [capi3ref.html#sqlitestatusmallocsize](capi3ref.md#sqlitestatusmallocsize) [malloc.html](malloc.md) [rescode.html#nomem](rescode.md#nomem)
- sqlite3_realloc64 → [c3ref/c_deserialize_freeonclose.html](c3ref/c_deserialize_freeonclose.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_DESERIALIZE_FREEONCLOSE](capi3ref.md#SQLITE_DESERIALIZE_FREEONCLOSE) [changes.html#version_3_8_7](changes.md#version_3_8_7) [compile.html#max_allocation_size](compile.md#max_allocation_size) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- sqlite3_rebaser → [session.html](session.md) [session/objlist.html](session/objlist.md)
- sqlite3_release_memory → [34to35.html](34to35.md) [c3ref/db_release_memory.html](c3ref/db_release_memory.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_db_release_memory](capi3ref.md#sqlite3_db_release_memory) [changes.html#version_3_5_0](changes.md#version_3_5_0) [compile.html#enable_memory_management](compile.md#enable_memory_management) [releaselog/3_5_0.html](releaselog/3_5_0.md)
- sqlite3_reset → [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/c_stmtstatus_counter.html#sqlitestmtstatusrun](c3ref/c_stmtstatus_counter.md#sqlitestmtstatusrun) [c3ref/clear_bindings.html](c3ref/clear_bindings.md) [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/finalize.html](c3ref/finalize.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/get_auxdata.html](c3ref/get_auxdata.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/reset.html](c3ref/reset.md) [c3ref/step.html](c3ref/step.md) [c3ref/stmt.html](c3ref/stmt.md) [c3ref/stmt_busy.html](c3ref/stmt_busy.md) [c3ref/stmt_explain.html](c3ref/stmt_explain.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_clear_bindings](capi3ref.md#sqlite3_clear_bindings) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_finalize](capi3ref.md#sqlite3_finalize) [capi3ref.html#sqlite3_get_auxdata](capi3ref.md#sqlite3_get_auxdata) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_reset](capi3ref.md#sqlite3_reset) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqlite3_stmt_busy](capi3ref.md#sqlite3_stmt_busy) [capi3ref.html#sqlite3_stmt_explain](capi3ref.md#sqlite3_stmt_explain) [capi3ref.html#sqlitestmtstatusrun](capi3ref.md#sqlitestmtstatusrun) [changes.html#version_3_8_11](changes.md#version_3_8_11) [cintro.html](cintro.md) [compile.html#omit_autoreset](compile.md#omit_autoreset) [lang_transaction.html#immediate](lang_transaction.md#immediate) [opcode.html](opcode.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [stmt.html](stmt.md) [unlock_notify.html](unlock_notify.md)
- sqlite3_reset_auto_extension → [c3ref/auto_extension.html](c3ref/auto_extension.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_auto_extension](capi3ref.md#sqlite3_auto_extension)
- sqlite3_result_blob → [appfunc.html](appfunc.md) [bindptr.html](bindptr.md) [c3ref/c_static.html](c3ref/c_static.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_STATIC](capi3ref.md#SQLITE_STATIC) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [vtab.html#xcolumn](vtab.md#xcolumn)
- sqlite3_result_blob64 → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [changes.html#version_3_8_7](changes.md#version_3_8_7) [releaselog/3_8_7.html](releaselog/3_8_7.md) [vtab.html#xcolumn](vtab.md#xcolumn)
- sqlite3_result_double → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [compile.html#omit_floating_point](compile.md#omit_floating_point) [vtab.html#xcolumn](vtab.md#xcolumn)
- sqlite3_result_error → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [windowfunctions.html#udfwinfunc](windowfunctions.md#udfwinfunc)
- sqlite3_result_error16 → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context)
- sqlite3_result_error_code → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [changes.html#version_3_5_6](changes.md#version_3_5_6) [releaselog/3_5_6.html](releaselog/3_5_6.md)
- sqlite3_result_error_nomem → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context)
- sqlite3_result_error_toobig → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context)
- sqlite3_result_int → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/vtab_nochange.html](c3ref/vtab_nochange.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [capi3ref.html#sqlite3_vtab_nochange](capi3ref.md#sqlite3_vtab_nochange) [cintro.html](cintro.md) [vtab.html#xcolumn](vtab.md#xcolumn) [vtab.html#xupdate](vtab.md#xupdate)
- sqlite3_result_int64 → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [vtab.html#xcolumn](vtab.md#xcolumn) [windowfunctions.html#udfwinfunc](windowfunctions.md#udfwinfunc)
- sqlite3_result_null → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/result_blob.html](c3ref/result_blob.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [vtab.html#xcolumn](vtab.md#xcolumn)
- sqlite3_result_pointer → [appfunc.html](appfunc.md) [bindptr.html](bindptr.md) [bindptr.html#ptrleak](bindptr.md#ptrleak) [bindptr.html#ptrtyp](bindptr.md#ptrtyp) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [changes.html#version_3_20_1](changes.md#version_3_20_1) [changes.html#version_3_21_0](changes.md#version_3_21_0) [news.html](news.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_21_0.html](releaselog/3_21_0.md) [vtab.html#xcolumn](vtab.md#xcolumn)
- sqlite3_result_subtype → [appfunc.html](appfunc.md) [bindptr.html](bindptr.md) [c3ref/c_deterministic.html#sqliteresultsubtype](c3ref/c_deterministic.md#sqliteresultsubtype) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value_subtype.html](c3ref/value_subtype.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [capi3ref.html#sqlite3_value_subtype](capi3ref.md#sqlite3_value_subtype) [capi3ref.html#sqliteresultsubtype](capi3ref.md#sqliteresultsubtype) [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_45_0](changes.md#version_3_45_0) [changes.html#version_3_9_0](changes.md#version_3_9_0) [compile.html#rcmd](compile.md#rcmd) [compile.html#strict_subtype](compile.md#strict_subtype) [news.html](news.md) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- sqlite3_result_text → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [vtab.html#xcolumn](vtab.md#xcolumn)
- sqlite3_result_text16 → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [vtab.html#xcolumn](vtab.md#xcolumn)
- sqlite3_result_text16be → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [vtab.html#xcolumn](vtab.md#xcolumn)
- sqlite3_result_text16le → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [vtab.html#xcolumn](vtab.md#xcolumn)
- sqlite3_result_text64 → [appfunc.html](appfunc.md) [c3ref/c_any.html#sqliteutf8zt](c3ref/c_any.md#sqliteutf8zt) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [capi3ref.html#sqliteutf8zt](capi3ref.md#sqliteutf8zt) [changes.html#version_3_53_0](changes.md#version_3_53_0) [changes.html#version_3_8_7](changes.md#version_3_8_7) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [releaselog/3_8_7.html](releaselog/3_8_7.md) [vtab.html#xcolumn](vtab.md#xcolumn)
- sqlite3_result_value → [appfunc.html](appfunc.md) [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [vtab.html#xcolumn](vtab.md#xcolumn)
- sqlite3_result_zeroblob → [appfunc.html](appfunc.md) [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [lang_corefunc.html#zeroblob](lang_corefunc.md#zeroblob) [vtab.html#xcolumn](vtab.md#xcolumn)
- sqlite3_result_zeroblob64 → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [changes.html#version_3_8_11](changes.md#version_3_8_11) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [vtab.html#xcolumn](vtab.md#xcolumn)
- sqlite3_rollback_hook → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/update_hook.html](c3ref/update_hook.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_update_hook](capi3ref.md#sqlite3_update_hook)
- sqlite3_rsync → [backup.html](backup.md) [c3ref/backup_finish.html#sqlite3backuppagecount](c3ref/backup_finish.md#sqlite3backuppagecount) [capi3ref.html#sqlite3backuppagecount](capi3ref.md#sqlite3backuppagecount) [changes.html#version_3_47_0](changes.md#version_3_47_0) [changes.html#version_3_50_0](changes.md#version_3_50_0) [changes.html#version_3_50_1](changes.md#version_3_50_1) [changes.html#version_3_53_0](changes.md#version_3_53_0) [howtocorrupt.html#stalefd](howtocorrupt.md#stalefd) [news.html](news.md) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- sqlite3_rtree_query_callback → [changes.html#version_3_8_5](changes.md#version_3_8_5) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- sqlite3_serialize → [c3ref/c_serialize_nocopy.html](c3ref/c_serialize_nocopy.md) [c3ref/db_name.html](c3ref/db_name.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_SERIALIZE_NOCOPY](capi3ref.md#SQLITE_SERIALIZE_NOCOPY) [capi3ref.html#sqlite3_db_name](capi3ref.md#sqlite3_db_name) [changes.html#version_3_23_0](changes.md#version_3_23_0) [changes.html#version_3_36_0](changes.md#version_3_36_0) [compile.html#enable_deserialize](compile.md#enable_deserialize) [compile.html#omit_deserialize](compile.md#omit_deserialize) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_36_0.html](releaselog/3_36_0.md)
- sqlite3_session → [session.html](session.md) [session/objlist.html](session/objlist.md)
- sqlite3_set_authorizer → [arch.html](arch.md) [bindptr.html](bindptr.md) [c3ref/c_alter_table.html](c3ref/c_alter_table.md) [c3ref/c_deny.html](c3ref/c_deny.md) [c3ref/c_fail.html](c3ref/c_fail.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/limit.html](c3ref/limit.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_ALTER_TABLE](capi3ref.md#SQLITE_ALTER_TABLE) [capi3ref.html#SQLITE_DENY](capi3ref.md#SQLITE_DENY) [capi3ref.html#SQLITE_FAIL](capi3ref.md#SQLITE_FAIL) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_limit](capi3ref.md#sqlite3_limit) [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_7_17](changes.md#version_3_7_17) [compile.html#omit_authorization](compile.md#omit_authorization) [lang_delete.html#truncateopt](lang_delete.md#truncateopt) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_7_17.html](releaselog/3_7_17.md) [rescode.html#auth](rescode.md#auth) [schematab.html](schematab.md) [security.html](security.md)
- sqlite3_set_auxdata → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/get_clientdata.html](c3ref/get_clientdata.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [capi3ref.html#sqlite3_get_clientdata](capi3ref.md#sqlite3_get_clientdata) [changes.html#version_3_12_0](changes.md#version_3_12_0) [changes.html#version_3_39_4](changes.md#version_3_39_4) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- sqlite3_set_clientdata → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/get_auxdata.html](c3ref/get_auxdata.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_get_auxdata](capi3ref.md#sqlite3_get_auxdata) [changes.html#version_3_44_0](changes.md#version_3_44_0) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md)
- sqlite3_set_errmsg → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_51_0](changes.md#version_3_51_0) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- sqlite3_set_last_insert_rowid → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/last_insert_rowid.html](c3ref/last_insert_rowid.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_last_insert_rowid](capi3ref.md#sqlite3_last_insert_rowid) [changes.html#version_3_18_0](changes.md#version_3_18_0) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md)
- sqlite3_setlk_timeout → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_50_0](changes.md#version_3_50_0) [changes.html#version_3_50_1](changes.md#version_3_50_1) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- sqlite3_shutdown → [35to36.html](35to36.md) [c3ref/c_config_covering_index_scan.html](c3ref/c_config_covering_index_scan.md) [c3ref/config.html](c3ref/config.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/mem_methods.html](c3ref/mem_methods.md) [c3ref/mutex_methods.html](c3ref/mutex_methods.md) [c3ref/pcache_methods2.html#thexshutdownpagecachemethod](c3ref/pcache_methods2.md#thexshutdownpagecachemethod) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_CONFIG_COVERING_INDEX_SCAN](capi3ref.md#SQLITE_CONFIG_COVERING_INDEX_SCAN) [capi3ref.html#sqlite3_config](capi3ref.md#sqlite3_config) [capi3ref.html#sqlite3_mem_methods](capi3ref.md#sqlite3_mem_methods) [capi3ref.html#sqlite3_mutex_methods](capi3ref.md#sqlite3_mutex_methods) [capi3ref.html#thexshutdownpagecachemethod](capi3ref.md#thexshutdownpagecachemethod) [changes.html#version_3_6_1](changes.md#version_3_6_1) [changes.html#version_3_6_15](changes.md#version_3_6_15) [custombuild.html](custombuild.md) [releaselog/3_6_0.html](releaselog/3_6_0.md) [releaselog/3_6_15.html](releaselog/3_6_15.md)
- sqlite3_sleep → [34to35.html](34to35.md) [backup.html](backup.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_42_0](changes.md#version_3_42_0) [releaselog/3_42_0.html](releaselog/3_42_0.md)
- sqlite3_snapshot → [c3ref/objlist.html](c3ref/objlist.md) [c3ref/snapshot_free.html](c3ref/snapshot_free.md) [c3ref/snapshot_get.html](c3ref/snapshot_get.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_snapshot_free](capi3ref.md#sqlite3_snapshot_free) [capi3ref.html#sqlite3_snapshot_get](capi3ref.md#sqlite3_snapshot_get) [compile.html#enable_snapshot](compile.md#enable_snapshot)
- sqlite3_snapshot_cmp → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/snapshot.html](c3ref/snapshot.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_snapshot](capi3ref.md#sqlite3_snapshot) [compile.html#enable_snapshot](compile.md#enable_snapshot)
- sqlite3_snapshot_free → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/snapshot.html](c3ref/snapshot.md) [c3ref/snapshot_free.html](c3ref/snapshot_free.md) [c3ref/snapshot_get.html](c3ref/snapshot_get.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_snapshot](capi3ref.md#sqlite3_snapshot) [capi3ref.html#sqlite3_snapshot_free](capi3ref.md#sqlite3_snapshot_free) [capi3ref.html#sqlite3_snapshot_get](capi3ref.md#sqlite3_snapshot_get) [changes.html#version_3_10_0](changes.md#version_3_10_0) [compile.html#enable_snapshot](compile.md#enable_snapshot) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md)
- sqlite3_snapshot_get → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/snapshot.html](c3ref/snapshot.md) [c3ref/snapshot_get.html](c3ref/snapshot_get.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_snapshot](capi3ref.md#sqlite3_snapshot) [capi3ref.html#sqlite3_snapshot_get](capi3ref.md#sqlite3_snapshot_get) [changes.html#version_3_10_0](changes.md#version_3_10_0) [compile.html#enable_snapshot](compile.md#enable_snapshot) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md)
- sqlite3_snapshot_open → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/snapshot.html](c3ref/snapshot.md) [c3ref/snapshot_open.html](c3ref/snapshot_open.md) [c3ref/snapshot_recover.html](c3ref/snapshot_recover.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_snapshot](capi3ref.md#sqlite3_snapshot) [capi3ref.html#sqlite3_snapshot_open](capi3ref.md#sqlite3_snapshot_open) [capi3ref.html#sqlite3_snapshot_recover](capi3ref.md#sqlite3_snapshot_recover) [changes.html#version_3_10_0](changes.md#version_3_10_0) [compile.html#enable_snapshot](compile.md#enable_snapshot) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [rescode.html#error_snapshot](rescode.md#error_snapshot)
- sqlite3_snapshot_recover → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/snapshot.html](c3ref/snapshot.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_snapshot](capi3ref.md#sqlite3_snapshot) [compile.html#enable_snapshot](compile.md#enable_snapshot)
- sqlite3_snprintf → [c3ref/c_config_covering_index_scan.html#sqliteconfiglog](c3ref/c_config_covering_index_scan.md#sqliteconfiglog) [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/log.html](c3ref/log.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_log](capi3ref.md#sqlite3_log) [capi3ref.html#sqliteconfiglog](capi3ref.md#sqliteconfiglog) [changes.html#version_3_4_0](changes.md#version_3_4_0) [lang_expr.html#castexpr](lang_expr.md#castexpr) [oldnews.html](oldnews.md) [printf.html](printf.md) [printf.html#comma](printf.md#comma) [releaselog/3_4_0.html](releaselog/3_4_0.md)
- sqlite3_soft_heap_limit → [34to35.html](34to35.md) [changes.html#version_3_4_2](changes.md#version_3_4_2) [changes.html#version_3_5_0](changes.md#version_3_5_0) [changes.html#version_3_7_3](changes.md#version_3_7_3) [compile.html#max_memory](compile.md#max_memory) [releaselog/3_4_2.html](releaselog/3_4_2.md) [releaselog/3_5_0.html](releaselog/3_5_0.md) [releaselog/3_7_3.html](releaselog/3_7_3.md)
- sqlite3_soft_heap_limit64 → [c3ref/c_config_covering_index_scan.html#sqliteconfigmemstatus](c3ref/c_config_covering_index_scan.md#sqliteconfigmemstatus) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/soft_heap_limit.html](c3ref/soft_heap_limit.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_soft_heap_limit](capi3ref.md#sqlite3_soft_heap_limit) [capi3ref.html#sqliteconfigmemstatus](capi3ref.md#sqliteconfigmemstatus) [changes.html#version_3_7_3](changes.md#version_3_7_3) [custombuild.html](custombuild.md) [malloc.html](malloc.md) [malloc.html#memstatus](malloc.md#memstatus) [oldnews.html](oldnews.md) [pragma.html#pragma_soft_heap_limit](pragma.md#pragma_soft_heap_limit) [releaselog/3_7_3.html](releaselog/3_7_3.md)
- sqlite3_sourceid → [c3ref/c_scm_branch.html](c3ref/c_scm_branch.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_SCM_BRANCH](capi3ref.md#SQLITE_SCM_BRANCH) [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_21_0](changes.md#version_3_21_0) [changes.html#version_3_6_18](changes.md#version_3_6_18) [lang_corefunc.html#sqlite_source_id](lang_corefunc.md#sqlite_source_id) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_6_18.html](releaselog/3_6_18.md) [th3.html](th3.md)
- sqlite3_sql → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt)
- sqlite3_status → [35to36.html](35to36.md) [c3ref/c_status_malloc_count.html](c3ref/c_status_malloc_count.md) [c3ref/c_status_malloc_count.html#sqlitestatusmallocsize](c3ref/c_status_malloc_count.md#sqlitestatusmallocsize) [c3ref/c_status_malloc_count.html#sqlitestatuspagecachesize](c3ref/c_status_malloc_count.md#sqlitestatuspagecachesize) [c3ref/db_status.html](c3ref/db_status.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt_status.html](c3ref/stmt_status.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_STATUS_MALLOC_COUNT](capi3ref.md#SQLITE_STATUS_MALLOC_COUNT) [capi3ref.html#sqlite3_db_status](capi3ref.md#sqlite3_db_status) [capi3ref.html#sqlite3_stmt_status](capi3ref.md#sqlite3_stmt_status) [capi3ref.html#sqlitestatusmallocsize](capi3ref.md#sqlitestatusmallocsize) [capi3ref.html#sqlitestatuspagecachesize](capi3ref.md#sqlitestatuspagecachesize) [changes.html#version_3_6_1](changes.md#version_3_6_1) [compile.html#disable_pagecache_overflow_stats](compile.md#disable_pagecache_overflow_stats) [compile.html#rcmd](compile.md#rcmd) [compile.html#yytrackmaxstackdepth](compile.md#yytrackmaxstackdepth) [malloc.html#memstatus](malloc.md#memstatus) [releaselog/3_6_0.html](releaselog/3_6_0.md) [releaselog/3_6_1.html](releaselog/3_6_1.md)
- sqlite3_status64 → [c3ref/c_config_covering_index_scan.html#sqliteconfigmemstatus](c3ref/c_config_covering_index_scan.md#sqliteconfigmemstatus) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqliteconfigmemstatus](capi3ref.md#sqliteconfigmemstatus) [changes.html#version_3_8_9](changes.md#version_3_8_9) [compile.html#default_memstatus](compile.md#default_memstatus) [compile.html#max_memory](compile.md#max_memory) [memstat.html](memstat.md) [oldnews.html](oldnews.md) [releaselog/3_8_9.html](releaselog/3_8_9.md) [vtablist.html](vtablist.md)
- sqlite3_step → [arch.html](arch.md) [backup.html](backup.md) [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/busy_timeout.html](c3ref/busy_timeout.md) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigstmtscanstatus](c3ref/c_dbconfig_defensive.md#sqlitedbconfigstmtscanstatus) [c3ref/c_stmtstatus_counter.html#sqlitestmtstatusrun](c3ref/c_stmtstatus_counter.md#sqlitestmtstatusrun) [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/column_database_name.html](c3ref/column_database_name.md) [c3ref/column_name.html](c3ref/column_name.md) [c3ref/commit_hook.html](c3ref/commit_hook.md) [c3ref/data_count.html](c3ref/data_count.md) [c3ref/exec.html](c3ref/exec.md) [c3ref/finalize.html](c3ref/finalize.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/profile.html](c3ref/profile.md) [c3ref/progress_handler.html](c3ref/progress_handler.md) [c3ref/reset.html](c3ref/reset.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [c3ref/stmt.html](c3ref/stmt.md) [c3ref/stmt_busy.html](c3ref/stmt_busy.md) [c3ref/unlock_notify.html](c3ref/unlock_notify.md) [c3ref/update_hook.html](c3ref/update_hook.md) [capi3.html](capi3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_busy_timeout](capi3ref.md#sqlite3_busy_timeout) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_column_database_name](capi3ref.md#sqlite3_column_database_name) [capi3ref.html#sqlite3_column_name](capi3ref.md#sqlite3_column_name) [capi3ref.html#sqlite3_commit_hook](capi3ref.md#sqlite3_commit_hook) [capi3ref.html#sqlite3_data_count](capi3ref.md#sqlite3_data_count) [capi3ref.html#sqlite3_exec](capi3ref.md#sqlite3_exec) [capi3ref.html#sqlite3_finalize](capi3ref.md#sqlite3_finalize) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_profile](capi3ref.md#sqlite3_profile) [capi3ref.html#sqlite3_progress_handler](capi3ref.md#sqlite3_progress_handler) [capi3ref.html#sqlite3_reset](capi3ref.md#sqlite3_reset) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqlite3_stmt_busy](capi3ref.md#sqlite3_stmt_busy) [capi3ref.html#sqlite3_unlock_notify](capi3ref.md#sqlite3_unlock_notify) [capi3ref.html#sqlite3_update_hook](capi3ref.md#sqlite3_update_hook) [capi3ref.html#sqlitedbconfigstmtscanstatus](capi3ref.md#sqlitedbconfigstmtscanstatus) [capi3ref.html#sqlitestmtstatusrun](capi3ref.md#sqlitestmtstatusrun) [changes.html#version_3_5_3](changes.md#version_3_5_3) [changes.html#version_3_8_1](changes.md#version_3_8_1) [cintro.html](cintro.md) [compile.html#omit_autoreset](compile.md#omit_autoreset) [eqp.html](eqp.md) [errlog.html](errlog.md) [faq.html#q15](faq.md#q15) [isolation.html](isolation.md) [lang_corefunc.html#likelihood](lang_corefunc.md#likelihood) [lang_corefunc.html#likely](lang_corefunc.md#likely) [lang_corefunc.html#unlikely](lang_corefunc.md#unlikely) [lang_datefunc.html#tmval](lang_datefunc.md#tmval) [lang_explain.html](lang_explain.md) [lang_returning.html](lang_returning.md) [malloc.html#lookaside](malloc.md#lookaside) [malloc.html#nofrag](malloc.md#nofrag) [opcode.html](opcode.md) [optoverview.html#like_opt](optoverview.md#like_opt) [pragma.html](pragma.md) [releaselog/3_5_3.html](releaselog/3_5_3.md) [releaselog/3_8_1.html](releaselog/3_8_1.md) [rescode.html#done](rescode.md#done) [rescode.html#row](rescode.md#row) [rescode.html#schema](rescode.md#schema) [stmt.html](stmt.md) [unlock_notify.html](unlock_notify.md) [vfs.html](vfs.md)
- sqlite3_stmt → [arch.html](arch.md) [c3ref/bind_blob.html](c3ref/bind_blob.md) [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/intro.html](c3ref/intro.md) [c3ref/objlist.html](c3ref/objlist.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_bind_blob](capi3ref.md#sqlite3_bind_blob) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [cintro.html](cintro.md) [tclsqlite.html#trace_v2](tclsqlite.md#trace_v2) [unlock_notify.html](unlock_notify.md) [whybytecode.html](whybytecode.md)
- sqlite3_stmt_busy → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [changes.html#version_3_7_10](changes.md#version_3_7_10) [changes.html#version_3_8_6](changes.md#version_3_8_6) [oldnews.html](oldnews.md) [releaselog/3_7_10.html](releaselog/3_7_10.md) [releaselog/3_8_6.html](releaselog/3_8_6.md)
- sqlite3_stmt_explain → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [changes.html#version_3_43_0](changes.md#version_3_43_0) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md)
- sqlite3_stmt_isexplain → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [changes.html#version_3_28_0](changes.md#version_3_28_0) [changes.html#version_3_31_1](changes.md#version_3_31_1) [releaselog/3_28_0.html](releaselog/3_28_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- sqlite3_stmt_readonly → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [changes.html#version_3_7_4](changes.md#version_3_7_4) [changes.html#version_3_7_5](changes.md#version_3_7_5) [releaselog/3_7_4.html](releaselog/3_7_4.md) [releaselog/3_7_5.html](releaselog/3_7_5.md)
- sqlite3_stmt_scanstatus → [c3ref/c_scanstat_est.html](c3ref/c_scanstat_est.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [c3ref/stmt_scanstatus_reset.html](c3ref/stmt_scanstatus_reset.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_SCANSTAT_EST](capi3ref.md#SQLITE_SCANSTAT_EST) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqlite3_stmt_scanstatus_reset](capi3ref.md#sqlite3_stmt_scanstatus_reset) [changes.html#version_3_8_8](changes.md#version_3_8_8) [compile.html#enable_stmt_scanstatus](compile.md#enable_stmt_scanstatus) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- sqlite3_stmt_scanstatus_reset → [bytecodevtab.html#nexec](bytecodevtab.md#nexec) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [c3ref/stmt_scanstatus.html](c3ref/stmt_scanstatus.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqlite3_stmt_scanstatus](capi3ref.md#sqlite3_stmt_scanstatus)
- sqlite3_stmt_scanstatus_v2 → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigstmtscanstatus](c3ref/c_dbconfig_defensive.md#sqlitedbconfigstmtscanstatus) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [capi3ref.html#sqlitedbconfigstmtscanstatus](capi3ref.md#sqlitedbconfigstmtscanstatus) [changes.html#version_3_41_0](changes.md#version_3_41_0) [compile.html#enable_stmt_scanstatus](compile.md#enable_stmt_scanstatus) [profile.html](profile.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- sqlite3_stmt_status → [c3ref/c_stmtstatus_counter.html](c3ref/c_stmtstatus_counter.md) [c3ref/db_status.html](c3ref/db_status.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/stmt.html](c3ref/stmt.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_STMTSTATUS counter](capi3ref.md#SQLITE_STMTSTATUS%20counter) [capi3ref.html#sqlite3_db_status](capi3ref.md#sqlite3_db_status) [capi3ref.html#sqlite3_stmt](capi3ref.md#sqlite3_stmt) [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_6_4](changes.md#version_3_6_4) [changes.html#version_3_8_0](changes.md#version_3_8_0) [lang_indexedby.html](lang_indexedby.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_6_4.html](releaselog/3_6_4.md) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md) [tclsqlite.html#status](tclsqlite.md#status)
- sqlite3_str → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlfilestat](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlfilestat) [c3ref/objlist.html](c3ref/objlist.md) [c3ref/str_append.html](c3ref/str_append.md) [c3ref/str_errcode.html](c3ref/str_errcode.md) [c3ref/str_finish.html](c3ref/str_finish.md) [c3ref/str_new.html](c3ref/str_new.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_str_append](capi3ref.md#sqlite3_str_append) [capi3ref.html#sqlite3_str_errcode](capi3ref.md#sqlite3_str_errcode) [capi3ref.html#sqlite3_str_finish](capi3ref.md#sqlite3_str_finish) [capi3ref.html#sqlite3_str_new](capi3ref.md#sqlite3_str_new) [capi3ref.html#sqlitefcntlfilestat](capi3ref.md#sqlitefcntlfilestat) [changes.html#version_3_24_0](changes.md#version_3_24_0) [releaselog/3_24_0.html](releaselog/3_24_0.md)
- sqlite3_str_append → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/str.html](c3ref/str.md) [c3ref/str_append.html](c3ref/str_append.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_str](capi3ref.md#sqlite3_str) [capi3ref.html#sqlite3_str_append](capi3ref.md#sqlite3_str_append)
- sqlite3_str_appendall → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/str.html](c3ref/str.md) [c3ref/str_append.html](c3ref/str_append.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_str](capi3ref.md#sqlite3_str) [capi3ref.html#sqlite3_str_append](capi3ref.md#sqlite3_str_append)
- sqlite3_str_appendchar → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/str.html](c3ref/str.md) [c3ref/str_append.html](c3ref/str_append.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_str](capi3ref.md#sqlite3_str) [capi3ref.html#sqlite3_str_append](capi3ref.md#sqlite3_str_append)
- sqlite3_str_appendf → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/str.html](c3ref/str.md) [c3ref/str_append.html](c3ref/str_append.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_str](capi3ref.md#sqlite3_str) [capi3ref.html#sqlite3_str_append](capi3ref.md#sqlite3_str_append) [compile.html#printf_precision_limit](compile.md#printf_precision_limit) [printf.html](printf.md)
- sqlite3_str_errcode → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/str.html](c3ref/str.md) [c3ref/str_append.html](c3ref/str_append.md) [c3ref/str_errcode.html](c3ref/str_errcode.md) [c3ref/str_new.html](c3ref/str_new.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_str](capi3ref.md#sqlite3_str) [capi3ref.html#sqlite3_str_append](capi3ref.md#sqlite3_str_append) [capi3ref.html#sqlite3_str_errcode](capi3ref.md#sqlite3_str_errcode) [capi3ref.html#sqlite3_str_new](capi3ref.md#sqlite3_str_new)
- sqlite3_str_finish → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/str.html](c3ref/str.md) [c3ref/str_finish.html](c3ref/str_finish.md) [c3ref/str_new.html](c3ref/str_new.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_str](capi3ref.md#sqlite3_str) [capi3ref.html#sqlite3_str_finish](capi3ref.md#sqlite3_str_finish) [capi3ref.html#sqlite3_str_new](capi3ref.md#sqlite3_str_new)
- sqlite3_str_free → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/str.html](c3ref/str.md) [c3ref/str_finish.html](c3ref/str_finish.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_str](capi3ref.md#sqlite3_str) [capi3ref.html#sqlite3_str_finish](capi3ref.md#sqlite3_str_finish) [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- sqlite3_str_length → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/str.html](c3ref/str.md) [c3ref/str_errcode.html](c3ref/str_errcode.md) [c3ref/str_new.html](c3ref/str_new.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_str](capi3ref.md#sqlite3_str) [capi3ref.html#sqlite3_str_errcode](capi3ref.md#sqlite3_str_errcode) [capi3ref.html#sqlite3_str_new](capi3ref.md#sqlite3_str_new)
- sqlite3_str_new → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/str.html](c3ref/str.md) [c3ref/str_append.html](c3ref/str_append.md) [c3ref/str_new.html](c3ref/str_new.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_str](capi3ref.md#sqlite3_str) [capi3ref.html#sqlite3_str_append](capi3ref.md#sqlite3_str_append) [capi3ref.html#sqlite3_str_new](capi3ref.md#sqlite3_str_new)
- sqlite3_str_reset → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/str.html](c3ref/str.md) [c3ref/str_append.html](c3ref/str_append.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_str](capi3ref.md#sqlite3_str) [capi3ref.html#sqlite3_str_append](capi3ref.md#sqlite3_str_append)
- sqlite3_str_truncate → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/str.html](c3ref/str.md) [c3ref/str_append.html](c3ref/str_append.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_str](capi3ref.md#sqlite3_str) [capi3ref.html#sqlite3_str_append](capi3ref.md#sqlite3_str_append) [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- sqlite3_str_value → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/str.html](c3ref/str.md) [c3ref/str_errcode.html](c3ref/str_errcode.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_str](capi3ref.md#sqlite3_str) [capi3ref.html#sqlite3_str_errcode](capi3ref.md#sqlite3_str_errcode)
- sqlite3_str_vappendf → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/str.html](c3ref/str.md) [c3ref/str_append.html](c3ref/str_append.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_str](capi3ref.md#sqlite3_str) [capi3ref.html#sqlite3_str_append](capi3ref.md#sqlite3_str_append) [printf.html](printf.md)
- sqlite3_strglob → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/strglob.html](c3ref/strglob.md) [c3ref/strlike.html](c3ref/strlike.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_strglob](capi3ref.md#sqlite3_strglob) [capi3ref.html#sqlite3_strlike](capi3ref.md#sqlite3_strlike) [changes.html#version_3_40_0](changes.md#version_3_40_0) [changes.html#version_3_7_17](changes.md#version_3_7_17) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- sqlite3_stricmp → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/strglob.html](c3ref/strglob.md) [c3ref/stricmp.html](c3ref/stricmp.md) [c3ref/strlike.html](c3ref/strlike.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_strglob](capi3ref.md#sqlite3_strglob) [capi3ref.html#sqlite3_stricmp](capi3ref.md#sqlite3_stricmp) [capi3ref.html#sqlite3_strlike](capi3ref.md#sqlite3_strlike) [changes.html#version_3_7_11](changes.md#version_3_7_11) [releaselog/3_7_11.html](releaselog/3_7_11.md)
- sqlite3_strlike → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/strglob.html](c3ref/strglob.md) [c3ref/strlike.html](c3ref/strlike.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_strglob](capi3ref.md#sqlite3_strglob) [capi3ref.html#sqlite3_strlike](capi3ref.md#sqlite3_strlike) [changes.html#version_3_10_0](changes.md#version_3_10_0) [changes.html#version_3_40_0](changes.md#version_3_40_0) [compile.html#like_doesnt_match_blobs](compile.md#like_doesnt_match_blobs) [pragma.html#pragma_case_sensitive_like](pragma.md#pragma_case_sensitive_like) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md)
- sqlite3_strnicmp → [c3ref/create_collation.html](c3ref/create_collation.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/strglob.html](c3ref/strglob.md) [c3ref/stricmp.html](c3ref/stricmp.md) [c3ref/strlike.html](c3ref/strlike.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_create_collation](capi3ref.md#sqlite3_create_collation) [capi3ref.html#sqlite3_strglob](capi3ref.md#sqlite3_strglob) [capi3ref.html#sqlite3_stricmp](capi3ref.md#sqlite3_stricmp) [capi3ref.html#sqlite3_strlike](capi3ref.md#sqlite3_strlike) [changes.html#version_3_6_17](changes.md#version_3_6_17) [changes.html#version_3_7_11](changes.md#version_3_7_11) [datatype3.html#collation](datatype3.md#collation) [oldnews.html](oldnews.md) [releaselog/3_6_17.html](releaselog/3_6_17.md) [releaselog/3_7_11.html](releaselog/3_7_11.md)
- sqlite3_system_errno → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_12_0](changes.md#version_3_12_0) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md)
- sqlite3_table_column_metadata → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_8_8](changes.md#version_3_8_8) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- sqlite3_temp_directory → [c3ref/objlist.html](c3ref/objlist.md) [c3ref/open.html#urifilenameexamples](c3ref/open.md#urifilenameexamples) [c3ref/win32_set_directory.html](c3ref/win32_set_directory.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_win32_set_directory](capi3ref.md#sqlite3_win32_set_directory) [capi3ref.html#urifilenameexamples](capi3ref.md#urifilenameexamples) [changes.html#version_3_8_1](changes.md#version_3_8_1) [pragma.html#pragma_temp_store_directory](pragma.md#pragma_temp_store_directory) [releaselog/3_8_1.html](releaselog/3_8_1.md) [tempfiles.html#tempdir](tempfiles.md#tempdir)
- sqlite3_test_control → [c3ref/c_testctrl_always.html](c3ref/c_testctrl_always.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_TESTCTRL_ALWAYS](capi3ref.md#SQLITE_TESTCTRL_ALWAYS) [changes.html#version_3_8_4](changes.md#version_3_8_4) [compile.html#untestable](compile.md#untestable) [imposter.html](imposter.md) [releaselog/3_8_4.html](releaselog/3_8_4.md) [releaselog/3_8_4_1.html](releaselog/3_8_4_1.md) [releaselog/3_8_4_2.html](releaselog/3_8_4_2.md) [releaselog/3_8_4_3.html](releaselog/3_8_4_3.md) [testing.html#defcode](testing.md#defcode) [testing.html#disopttest](testing.md#disopttest) [wal.html#walresetbug](wal.md#walresetbug)
- sqlite3_thread_cleanup → [34to35.html](34to35.md) [compile.html#omit_deprecated](compile.md#omit_deprecated)
- sqlite3_threadsafe → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [compile.html#threadsafe](compile.md#threadsafe) [custombuild.html](custombuild.md) [faq.html#q6](faq.md#q6) [threadsafe.html](threadsafe.md)
- sqlite3_total_changes → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntldataversion](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntldataversion) [c3ref/changes.html](c3ref/changes.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/total_changes.html](c3ref/total_changes.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_changes](capi3ref.md#sqlite3_changes) [capi3ref.html#sqlite3_total_changes](capi3ref.md#sqlite3_total_changes) [capi3ref.html#sqlitefcntldataversion](capi3ref.md#sqlitefcntldataversion) [changes.html#version_3_6_5](changes.md#version_3_6_5) [fts3.html#\*fts4mergecmd](fts3.md#*fts4mergecmd) [fts5.html#the_merge_command](fts5.md#the_merge_command) [lang_createtrigger.html#instead_of_trigger](lang_createtrigger.md#instead_of_trigger) [lang_delete.html#truncateopt](lang_delete.md#truncateopt) [pragma.html#pragma_count_changes](pragma.md#pragma_count_changes) [releaselog/3_6_5.html](releaselog/3_6_5.md)
- sqlite3_total_changes64 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_37_0](changes.md#version_3_37_0) [lang_corefunc.html#total_changes](lang_corefunc.md#total_changes) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md)
- sqlite3_trace → [c3ref/c_trace.html#sqlitetracestmt](c3ref/c_trace.md#sqlitetracestmt) [c3ref/profile.html](c3ref/profile.md) [c3ref/trace_v2.html](c3ref/trace_v2.md) [capi3ref.html#sqlite3_profile](capi3ref.md#sqlite3_profile) [capi3ref.html#sqlite3_trace_v2](capi3ref.md#sqlite3_trace_v2) [capi3ref.html#sqlitetracestmt](capi3ref.md#sqlitetracestmt) [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_6_21](changes.md#version_3_6_21) [changes.html#version_3_7_15](changes.md#version_3_7_15) [changes.html#version_3_7_17](changes.md#version_3_7_17) [changes.html#version_3_7_5](changes.md#version_3_7_5) [changes.html#version_3_8_7](changes.md#version_3_8_7) [compile.html#omit_trace](compile.md#omit_trace) [compile.html#trace_size_limit](compile.md#trace_size_limit) [oldnews.html](oldnews.md) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_6_21.html](releaselog/3_6_21.md) [releaselog/3_7_15.html](releaselog/3_7_15.md) [releaselog/3_7_17.html](releaselog/3_7_17.md) [releaselog/3_7_5.html](releaselog/3_7_5.md) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- sqlite3_trace_v2 → [c3ref/c_trace.html](c3ref/c_trace.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/profile.html](c3ref/profile.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_TRACE](capi3ref.md#SQLITE_TRACE) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_profile](capi3ref.md#sqlite3_profile) [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_14_2](changes.md#version_3_14_2) [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_22_0.html](releaselog/3_22_0.md)
- sqlite3_transfer_bindings → [compile.html#omit_deprecated](compile.md#omit_deprecated)
- sqlite3_txn_state → [c3ref/c_txn_none.html](c3ref/c_txn_none.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_TXN_NONE](capi3ref.md#SQLITE_TXN_NONE) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_34_0](changes.md#version_3_34_0) [cli.html#dotdatabases](cli.md#dotdatabases) [lang_transaction.html#immediate](lang_transaction.md#immediate) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md)
- sqlite3_unlock_notify → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [changes.html#version_3_6_12](changes.md#version_3_6_12) [compile.html#enable_unlock_notify](compile.md#enable_unlock_notify) [releaselog/3_6_12.html](releaselog/3_6_12.md) [tclsqlite.html#unlock_notify](tclsqlite.md#unlock_notify) [unlock_notify.html](unlock_notify.md)
- sqlite3_update_hook → [c3ref/commit_hook.html](c3ref/commit_hook.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_commit_hook](capi3ref.md#sqlite3_commit_hook) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite) [compile.html#enable_preupdate_hook](compile.md#enable_preupdate_hook) [lang_conflict.html](lang_conflict.md) [withoutrowid.html](withoutrowid.md)
- sqlite3_uri_boolean → [c3ref/create_filename.html](c3ref/create_filename.md) [c3ref/db_filename.html](c3ref/db_filename.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_create_filename](capi3ref.md#sqlite3_create_filename) [capi3ref.html#sqlite3_db_filename](capi3ref.md#sqlite3_db_filename) [changes.html#version_3_7_10](changes.md#version_3_7_10) [oldnews.html](oldnews.md) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- sqlite3_uri_int64 → [c3ref/create_filename.html](c3ref/create_filename.md) [c3ref/db_filename.html](c3ref/db_filename.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_create_filename](capi3ref.md#sqlite3_create_filename) [capi3ref.html#sqlite3_db_filename](capi3ref.md#sqlite3_db_filename) [changes.html#version_3_7_10](changes.md#version_3_7_10) [oldnews.html](oldnews.md) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- sqlite3_uri_key → [c3ref/create_filename.html](c3ref/create_filename.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_create_filename](capi3ref.md#sqlite3_create_filename) [changes.html#version_3_31_0](changes.md#version_3_31_0) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- sqlite3_uri_parameter → [c3ref/create_filename.html](c3ref/create_filename.md) [c3ref/db_filename.html](c3ref/db_filename.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_create_filename](capi3ref.md#sqlite3_create_filename) [capi3ref.html#sqlite3_db_filename](capi3ref.md#sqlite3_db_filename) [changes.html#version_3_31_0](changes.md#version_3_31_0) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- sqlite3_user_data → [appfunc.html](appfunc.md) [c3ref/context.html](c3ref/context.md) [c3ref/create_function.html](c3ref/create_function.md) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_context](capi3ref.md#sqlite3_context) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [cintro.html](cintro.md)
- sqlite3_value → [appfunc.html](appfunc.md) [bindptr.html#ptrtyp](bindptr.md#ptrtyp) [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/objlist.html](c3ref/objlist.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/result_blob.html](c3ref/result_blob.md) [c3ref/value_blob.html](c3ref/value_blob.md) [c3ref/value_dup.html](c3ref/value_dup.md) [c3ref/value_encoding.html](c3ref/value_encoding.md) [c3ref/vtab_in.html](c3ref/vtab_in.md) [c3ref/vtab_rhs_value.html](c3ref/vtab_rhs_value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [capi3ref.html#sqlite3_value_dup](capi3ref.md#sqlite3_value_dup) [capi3ref.html#sqlite3_value_encoding](capi3ref.md#sqlite3_value_encoding) [capi3ref.html#sqlite3_vtab_in](capi3ref.md#sqlite3_vtab_in) [capi3ref.html#sqlite3_vtab_rhs_value](capi3ref.md#sqlite3_vtab_rhs_value) [opcode.html](opcode.md) [windowfunctions.html#udfwinfunc](windowfunctions.md#udfwinfunc)
- sqlite3_value_blob → [bindptr.html](bindptr.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob)
- sqlite3_value_bytes → [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [c3ref/value_blob.html](c3ref/value_blob.md) [c3ref/value_encoding.html](c3ref/value_encoding.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [capi3ref.html#sqlite3_value_encoding](capi3ref.md#sqlite3_value_encoding)
- sqlite3_value_bytes16 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [c3ref/value_blob.html](c3ref/value_blob.md) [c3ref/value_encoding.html](c3ref/value_encoding.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [capi3ref.html#sqlite3_value_encoding](capi3ref.md#sqlite3_value_encoding)
- sqlite3_value_double → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [compile.html#omit_floating_point](compile.md#omit_floating_point)
- sqlite3_value_dup → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [c3ref/value_blob.html](c3ref/value_blob.md) [c3ref/value_dup.html](c3ref/value_dup.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [capi3ref.html#sqlite3_value_dup](capi3ref.md#sqlite3_value_dup) [changes.html#version_3_8_11](changes.md#version_3_8_11) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- sqlite3_value_encoding → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [changes.html#version_3_40_0](changes.md#version_3_40_0) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md)
- sqlite3_value_free → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [changes.html#version_3_8_11](changes.md#version_3_8_11) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- sqlite3_value_frombind → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [changes.html#version_3_28_0](changes.md#version_3_28_0) [changes.html#version_3_31_1](changes.md#version_3_31_1) [releaselog/3_28_0.html](releaselog/3_28_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- sqlite3_value_int → [appfunc.html](appfunc.md) [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [cintro.html](cintro.md)
- sqlite3_value_int64 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [windowfunctions.html#udfwinfunc](windowfunctions.md#udfwinfunc)
- sqlite3_value_nochange → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [c3ref/vtab_nochange.html](c3ref/vtab_nochange.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [capi3ref.html#sqlite3_vtab_nochange](capi3ref.md#sqlite3_vtab_nochange) [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_22_0.html](releaselog/3_22_0.md) [vtab.html#xupdate](vtab.md#xupdate)
- sqlite3_value_numeric_type → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value)
- sqlite3_value_pointer → [bindptr.html](bindptr.md) [bindptr.html#ptrleak](bindptr.md#ptrleak) [bindptr.html#ptrtyp](bindptr.md#ptrtyp) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/result_blob.html](c3ref/result_blob.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value)
- sqlite3_value_subtype → [bindptr.html](bindptr.md) [c3ref/c_deterministic.html#sqlitesubtype](c3ref/c_deterministic.md#sqlitesubtype) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [capi3ref.html#sqlitesubtype](capi3ref.md#sqlitesubtype) [changes.html#version_3_47_0](changes.md#version_3_47_0) [changes.html#version_3_9_0](changes.md#version_3_9_0) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- sqlite3_value_text → [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [c3ref/value_blob.html](c3ref/value_blob.md) [c3ref/value_encoding.html](c3ref/value_encoding.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [capi3ref.html#sqlite3_value_encoding](capi3ref.md#sqlite3_value_encoding) [changes.html#version_3_16_2](changes.md#version_3_16_2) [floatingpoint.html#\*rounding](floatingpoint.md#*rounding) [releaselog/3_16_2.html](releaselog/3_16_2.md)
- sqlite3_value_text16 → [c3ref/create_function.html](c3ref/create_function.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [c3ref/value_blob.html](c3ref/value_blob.md) [c3ref/value_encoding.html](c3ref/value_encoding.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [capi3ref.html#sqlite3_value_encoding](capi3ref.md#sqlite3_value_encoding)
- sqlite3_value_text16be → [c3ref/create_function.html](c3ref/create_function.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [c3ref/value_encoding.html](c3ref/value_encoding.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [capi3ref.html#sqlite3_value_encoding](capi3ref.md#sqlite3_value_encoding)
- sqlite3_value_text16le → [c3ref/create_function.html](c3ref/create_function.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [c3ref/value_encoding.html](c3ref/value_encoding.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [capi3ref.html#sqlite3_value_encoding](capi3ref.md#sqlite3_value_encoding)
- sqlite3_value_type → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [windowfunctions.html#udfwinfunc](windowfunctions.md#udfwinfunc)
- sqlite3_version → [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [deterministic.html](deterministic.md)
- sqlite3_vfs → [34to35.html](34to35.md) [35to36.html](35to36.md) [c3ref/c_access_exists.html](c3ref/c_access_exists.md) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlvfspointer](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlvfspointer) [c3ref/data_directory.html](c3ref/data_directory.md) [c3ref/database_file_object.html](c3ref/database_file_object.md) [c3ref/file.html](c3ref/file.md) [c3ref/file_control.html](c3ref/file_control.md) [c3ref/initialize.html](c3ref/initialize.md) [c3ref/objlist.html](c3ref/objlist.md) [c3ref/open.html#opennofollow](c3ref/open.md#opennofollow) [c3ref/randomness.html](c3ref/randomness.md) [c3ref/sleep.html](c3ref/sleep.md) [c3ref/temp_directory.html](c3ref/temp_directory.md) [c3ref/vfs_find.html](c3ref/vfs_find.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_ACCESS_EXISTS](capi3ref.md#SQLITE_ACCESS_EXISTS) [capi3ref.html#opennofollow](capi3ref.md#opennofollow) [capi3ref.html#sqlite3_data_directory](capi3ref.md#sqlite3_data_directory) [capi3ref.html#sqlite3_database_file_object](capi3ref.md#sqlite3_database_file_object) [capi3ref.html#sqlite3_file](capi3ref.md#sqlite3_file) [capi3ref.html#sqlite3_file_control](capi3ref.md#sqlite3_file_control) [capi3ref.html#sqlite3_initialize](capi3ref.md#sqlite3_initialize) [capi3ref.html#sqlite3_randomness](capi3ref.md#sqlite3_randomness) [capi3ref.html#sqlite3_sleep](capi3ref.md#sqlite3_sleep) [capi3ref.html#sqlite3_temp_directory](capi3ref.md#sqlite3_temp_directory) [capi3ref.html#sqlite3_vfs_find](capi3ref.md#sqlite3_vfs_find) [capi3ref.html#sqlitefcntlvfspointer](capi3ref.md#sqlitefcntlvfspointer) [changes.html#version_3_6_1](changes.md#version_3_6_1) [changes.html#version_3_6_7](changes.md#version_3_6_7) [changes.html#version_3_7_4](changes.md#version_3_7_4) [changes.html#version_3_7_6](changes.md#version_3_7_6) [compile.html#os_other](compile.md#os_other) [custombuild.html](custombuild.md) [howtocorrupt.html#posix_close_bug](howtocorrupt.md#posix_close_bug) [lang_datefunc.html#tmval](lang_datefunc.md#tmval) [loadext.html#persist](loadext.md#persist) [loadext.html#statext](loadext.md#statext) [oldnews.html](oldnews.md) [releaselog/3_6_0.html](releaselog/3_6_0.md) [releaselog/3_6_7.html](releaselog/3_6_7.md) [releaselog/3_7_4.html](releaselog/3_7_4.md) [releaselog/3_7_6.html](releaselog/3_7_6.md) [rescode.html#ioerr_access](rescode.md#ioerr_access) [rescode.html#ioerr_delete](rescode.md#ioerr_delete) [rescode.html#ioerr_delete_noent](rescode.md#ioerr_delete_noent) [rescode.html#notfound](rescode.md#notfound) [rescode.html#ok_load_permanently](rescode.md#ok_load_permanently) [testing.html#crashtesting](testing.md#crashtesting) [testing.html#ioerrtesting](testing.md#ioerrtesting) [vfs.html#shim](vfs.md#shim)
- sqlite3_vfs.xOpen → [c3ref/c_open_autoproxy.html](c3ref/c_open_autoproxy.md) [c3ref/create_filename.html](c3ref/create_filename.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html#SQLITE_OPEN_AUTOPROXY](capi3ref.md#SQLITE_OPEN_AUTOPROXY) [capi3ref.html#sqlite3_create_filename](capi3ref.md#sqlite3_create_filename) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- sqlite3_vfs_find → [34to35.html](34to35.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/vfs.html](c3ref/vfs.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_vfs](capi3ref.md#sqlite3_vfs) [compile.html#rcmd](compile.md#rcmd)
- sqlite3_vfs_register → [34to35.html](34to35.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/vfs.html](c3ref/vfs.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_vfs](capi3ref.md#sqlite3_vfs) [changes.html#version_3_7_14](changes.md#version_3_7_14) [cintro.html](cintro.md) [compile.html#omit_autoinit](compile.md#omit_autoinit) [compile.html#os_other](compile.md#os_other) [custombuild.html](custombuild.md) [oldnews.html](oldnews.md) [privatebranch.html](privatebranch.md) [releaselog/3_7_14.html](releaselog/3_7_14.md) [uri.html#urivfs](uri.md#urivfs) [vfs.html](vfs.md) [vfs.html#shim](vfs.md#shim)
- sqlite3_vfs_unregister → [34to35.html](34to35.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/vfs.html](c3ref/vfs.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_vfs](capi3ref.md#sqlite3_vfs)
- sqlite3_vmprintf → [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [printf.html](printf.md)
- sqlite3_vsnprintf → [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_7_5](changes.md#version_3_7_5) [oldnews.html](oldnews.md) [printf.html](printf.md) [releaselog/3_7_5.html](releaselog/3_7_5.md)
- sqlite3_vtab → [c3ref/objlist.html](c3ref/objlist.md) [capi3ref.html](capi3ref.md) [compile.html#omit_virtualtable](compile.md#omit_virtualtable) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab) [vtab.html#xconnect](vtab.md#xconnect) [vtab.html#xcreate](vtab.md#xcreate) [vtab.html#xdisconnect](vtab.md#xdisconnect) [vtab.html#xfindfunction](vtab.md#xfindfunction) [vtab.html#xintegrity](vtab.md#xintegrity)
- sqlite3_vtab_collation → [c3ref/c_index_constraint_eq.html](c3ref/c_index_constraint_eq.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/index_info.html](c3ref/index_info.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_INDEX_CONSTRAINT_EQ](capi3ref.md#SQLITE_INDEX_CONSTRAINT_EQ) [capi3ref.html#sqlite3_index_info](capi3ref.md#sqlite3_index_info) [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_22_0.html](releaselog/3_22_0.md) [vtab.html#xbestindex](vtab.md#xbestindex)
- sqlite3_vtab_config → [c3ref/c_vtab_constraint_support.html](c3ref/c_vtab_constraint_support.md) [c3ref/c_vtab_constraint_support.html#sqlitevtabconstraintsupport](c3ref/c_vtab_constraint_support.md#sqlitevtabconstraintsupport) [c3ref/c_vtab_constraint_support.html#sqlitevtabdirectonly](c3ref/c_vtab_constraint_support.md#sqlitevtabdirectonly) [c3ref/c_vtab_constraint_support.html#sqlitevtabinnocuous](c3ref/c_vtab_constraint_support.md#sqlitevtabinnocuous) [c3ref/c_vtab_constraint_support.html#sqlitevtabusesallschemas](c3ref/c_vtab_constraint_support.md#sqlitevtabusesallschemas) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_VTAB_CONSTRAINT_SUPPORT](capi3ref.md#SQLITE_VTAB_CONSTRAINT_SUPPORT) [capi3ref.html#sqlitevtabconstraintsupport](capi3ref.md#sqlitevtabconstraintsupport) [capi3ref.html#sqlitevtabdirectonly](capi3ref.md#sqlitevtabdirectonly) [capi3ref.html#sqlitevtabinnocuous](capi3ref.md#sqlitevtabinnocuous) [capi3ref.html#sqlitevtabusesallschemas](capi3ref.md#sqlitevtabusesallschemas) [changes.html#version_3_31_0](changes.md#version_3_31_0) [changes.html#version_3_7_7](changes.md#version_3_7_7) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [releaselog/3_7_7.html](releaselog/3_7_7.md) [vtab.html#customvtab](vtab.md#customvtab) [vtab.html#xconnect](vtab.md#xconnect) [vtab.html#xcreate](vtab.md#xcreate)
- sqlite3_vtab_cursor → [c3ref/objlist.html](c3ref/objlist.md) [capi3ref.html](capi3ref.md) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab) [vtab.html#xclose](vtab.md#xclose) [vtab.html#xnext](vtab.md#xnext) [vtab.html#xopen](vtab.md#xopen) [vtab.html#xrowid](vtab.md#xrowid) [vtab.html#xupdate](vtab.md#xupdate)
- sqlite3_vtab_distinct → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/index_info.html](c3ref/index_info.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_index_info](capi3ref.md#sqlite3_index_info) [changes.html#version_3_38_0](changes.md#version_3_38_0) [changes.html#version_3_39_0](changes.md#version_3_39_0) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md) [releaselog/3_39_0.html](releaselog/3_39_0.md) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md) [vtab.html#obc](vtab.md#obc)
- sqlite3_vtab_in → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/vtab_in_first.html](c3ref/vtab_in_first.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_vtab_in_first](capi3ref.md#sqlite3_vtab_in_first) [changes.html#version_3_38_0](changes.md#version_3_38_0) [changes.html#version_3_41_0](changes.md#version_3_41_0) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- sqlite3_vtab_in_first → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/vtab_in.html](c3ref/vtab_in.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_vtab_in](capi3ref.md#sqlite3_vtab_in) [changes.html#version_3_41_0](changes.md#version_3_41_0) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- sqlite3_vtab_in_next → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/vtab_in.html](c3ref/vtab_in.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_vtab_in](capi3ref.md#sqlite3_vtab_in) [changes.html#version_3_41_0](changes.md#version_3_41_0) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- sqlite3_vtab_nochange → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [changes.html#version_3_22_0](changes.md#version_3_22_0) [releaselog/3_22_0.html](releaselog/3_22_0.md) [vtab.html#xupdate](vtab.md#xupdate)
- sqlite3_vtab_on_conflict → [c3ref/c_deny.html](c3ref/c_deny.md) [c3ref/c_fail.html](c3ref/c_fail.md) [c3ref/c_vtab_constraint_support.html#sqlitevtabconstraintsupport](c3ref/c_vtab_constraint_support.md#sqlitevtabconstraintsupport) [c3ref/funclist.html](c3ref/funclist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_DENY](capi3ref.md#SQLITE_DENY) [capi3ref.html#SQLITE_FAIL](capi3ref.md#SQLITE_FAIL) [capi3ref.html#sqlitevtabconstraintsupport](capi3ref.md#sqlitevtabconstraintsupport) [rescode.html#abort](rescode.md#abort)
- sqlite3_vtab_rhs_value → [c3ref/c_index_constraint_eq.html](c3ref/c_index_constraint_eq.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/index_info.html](c3ref/index_info.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_INDEX_CONSTRAINT_EQ](capi3ref.md#SQLITE_INDEX_CONSTRAINT_EQ) [capi3ref.html#sqlite3_index_info](capi3ref.md#sqlite3_index_info) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [changes.html#version_3_38_0](changes.md#version_3_38_0) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md) [rescode.html#notfound](rescode.md#notfound) [vtab.html#colUsed](vtab.md#colUsed) [vtab.html#xfindfunction](vtab.md#xfindfunction)
- sqlite3_wal_autocheckpoint → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/wal_autocheckpoint.html](c3ref/wal_autocheckpoint.md) [c3ref/wal_hook.html](c3ref/wal_hook.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_wal_autocheckpoint](capi3ref.md#sqlite3_wal_autocheckpoint) [capi3ref.html#sqlite3_wal_hook](capi3ref.md#sqlite3_wal_hook) [pragma.html#pragma_wal_autocheckpoint](pragma.md#pragma_wal_autocheckpoint) [wal.html#fast](wal.md#fast) [walformat.html#walidxfmt](walformat.md#walidxfmt)
- sqlite3_wal_checkpoint → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [oldnews.html](oldnews.md) [pragma.html#pragma_wal_checkpoint](pragma.md#pragma_wal_checkpoint) [wal.html#fast](wal.md#fast)
- sqlite3_wal_checkpoint_v2 → [c3ref/c_checkpoint_full.html](c3ref/c_checkpoint_full.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/wal_autocheckpoint.html](c3ref/wal_autocheckpoint.md) [c3ref/wal_checkpoint.html](c3ref/wal_checkpoint.md) [c3ref/wal_hook.html](c3ref/wal_hook.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_CHECKPOINT_FULL](capi3ref.md#SQLITE_CHECKPOINT_FULL) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_wal_autocheckpoint](capi3ref.md#sqlite3_wal_autocheckpoint) [capi3ref.html#sqlite3_wal_checkpoint](capi3ref.md#sqlite3_wal_checkpoint) [capi3ref.html#sqlite3_wal_hook](capi3ref.md#sqlite3_wal_hook) [changes.html#version_3_51_0](changes.md#version_3_51_0) [changes.html#version_3_7_6](changes.md#version_3_7_6) [changes.html#version_3_8_8](changes.md#version_3_8_8) [changes.html#version_3_8_8_2](changes.md#version_3_8_8_2) [pragma.html#pragma_wal_autocheckpoint](pragma.md#pragma_wal_autocheckpoint) [pragma.html#pragma_wal_checkpoint](pragma.md#pragma_wal_checkpoint) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md) [releaselog/3_7_6.html](releaselog/3_7_6.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md) [wal.html#fast](wal.md#fast)
- sqlite3_wal_hook → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/sqlite3.html](c3ref/sqlite3.md) [c3ref/wal_autocheckpoint.html](c3ref/wal_autocheckpoint.md) [c3ref/wal_hook.html](c3ref/wal_hook.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3](capi3ref.md#sqlite3) [capi3ref.html#sqlite3_wal_autocheckpoint](capi3ref.md#sqlite3_wal_autocheckpoint) [capi3ref.html#sqlite3_wal_hook](capi3ref.md#sqlite3_wal_hook) [tclsqlite.html#wal_hook](tclsqlite.md#wal_hook) [wal.html#fast](wal.md#fast)
- sqlite3_win32_set_directory → [c3ref/c_win32_data_directory_type.html](c3ref/c_win32_data_directory_type.md) [c3ref/funclist.html](c3ref/funclist.md) [c3ref/win32_set_directory.html](c3ref/win32_set_directory.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_WIN32_DATA_DIRECTORY_TYPE](capi3ref.md#SQLITE_WIN32_DATA_DIRECTORY_TYPE) [capi3ref.html#sqlite3_win32_set_directory](capi3ref.md#sqlite3_win32_set_directory)
- sqlite3_win32_set_directory16 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/win32_set_directory.html](c3ref/win32_set_directory.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_win32_set_directory](capi3ref.md#sqlite3_win32_set_directory)
- sqlite3_win32_set_directory8 → [c3ref/funclist.html](c3ref/funclist.md) [c3ref/win32_set_directory.html](c3ref/win32_set_directory.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_win32_set_directory](capi3ref.md#sqlite3_win32_set_directory)
- sqlite3changegroup_add → [session.html](session.md) [session.html#sqlite3_changegroup](session.md#sqlite3_changegroup) [session.html#sqlite3changegroup_add_change](session.md#sqlite3changegroup_add_change) [session/changegroup.html](session/changegroup.md) [session/funclist.html](session/funclist.md) [session/sqlite3changegroup_add_change.html](session/sqlite3changegroup_add_change.md)
- sqlite3changegroup_add_change → [session.html](session.md) [session.html#sqlite3_changegroup](session.md#sqlite3_changegroup) [session/changegroup.html](session/changegroup.md) [session/funclist.html](session/funclist.md)
- sqlite3changegroup_add_strm → [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3changegroup_change_begin → [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3changegroup_change_blob → [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3changegroup_change_double → [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3changegroup_change_finish → [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3changegroup_change_int64 → [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3changegroup_change_null → [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3changegroup_change_text → [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3changegroup_config → [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3changegroup_delete → [session.html](session.md) [session.html#sqlite3_changegroup](session.md#sqlite3_changegroup) [session/changegroup.html](session/changegroup.md) [session/funclist.html](session/funclist.md)
- sqlite3changegroup_new → [session.html](session.md) [session.html#sqlite3_changegroup](session.md#sqlite3_changegroup) [session/changegroup.html](session/changegroup.md) [session/funclist.html](session/funclist.md)
- sqlite3changegroup_output → [session.html](session.md) [session.html#sqlite3_changegroup](session.md#sqlite3_changegroup) [session/changegroup.html](session/changegroup.md) [session/funclist.html](session/funclist.md)
- sqlite3changegroup_schema → [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3changeset_apply → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [session.html](session.md) [session.html#sqlite3changegroup_add_strm](session.md#sqlite3changegroup_add_strm) [session.html#sqlite3changeset_conflict](session.md#sqlite3changeset_conflict) [session.html#sqlite3changeset_finalize](session.md#sqlite3changeset_finalize) [session.html#sqlite3changeset_new](session.md#sqlite3changeset_new) [session.html#sqlite3changeset_next](session.md#sqlite3changeset_next) [session.html#sqlite3changeset_old](session.md#sqlite3changeset_old) [session.html#sqlite3changeset_op](session.md#sqlite3changeset_op) [session.html#sqlite3session_changeset](session.md#sqlite3session_changeset) [session/funclist.html](session/funclist.md) [session/sqlite3changegroup_add_strm.html](session/sqlite3changegroup_add_strm.md) [session/sqlite3changeset_conflict.html](session/sqlite3changeset_conflict.md) [session/sqlite3changeset_finalize.html](session/sqlite3changeset_finalize.md) [session/sqlite3changeset_new.html](session/sqlite3changeset_new.md) [session/sqlite3changeset_next.html](session/sqlite3changeset_next.md) [session/sqlite3changeset_old.html](session/sqlite3changeset_old.md) [session/sqlite3changeset_op.html](session/sqlite3changeset_op.md) [session/sqlite3session_changeset.html](session/sqlite3session_changeset.md) [sessionintro.html#changeset](sessionintro.md#changeset)
- sqlite3changeset_apply_v2 → [session.html#SQLITE_CHANGESETAPPLY_FKNOACTION](session.md#SQLITE_CHANGESETAPPLY_FKNOACTION) [session.html#sqlite3changegroup_add_strm](session.md#sqlite3changegroup_add_strm) [session/c_changesetapply_fknoaction.html](session/c_changesetapply_fknoaction.md) [session/sqlite3changegroup_add_strm.html](session/sqlite3changegroup_add_strm.md)
- sqlite3changeset_apply_v2_strm → [session.html#SQLITE_CHANGESETAPPLY_FKNOACTION](session.md#SQLITE_CHANGESETAPPLY_FKNOACTION) [session/c_changesetapply_fknoaction.html](session/c_changesetapply_fknoaction.md)
- sqlite3changeset_apply_v3 → [changes.html#version_3_51_0](changes.md#version_3_51_0) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- sqlite3changeset_concat → [session.html](session.md) [session.html#sqlite3changegroup_add_strm](session.md#sqlite3changegroup_add_strm) [session.html#sqlite3changeset_start](session.md#sqlite3changeset_start) [session/funclist.html](session/funclist.md) [session/sqlite3changegroup_add_strm.html](session/sqlite3changegroup_add_strm.md) [session/sqlite3changeset_start.html](session/sqlite3changeset_start.md) [sessionintro.html#changeset](sessionintro.md#changeset)
- sqlite3changeset_conflict → [session.html](session.md) [session.html#sqlite3_changeset_iter](session.md#sqlite3_changeset_iter) [session/changeset_iter.html](session/changeset_iter.md) [session/funclist.html](session/funclist.md)
- sqlite3changeset_finalize → [session.html](session.md) [session.html#sqlite3_changeset_iter](session.md#sqlite3_changeset_iter) [session.html#sqlite3changeset_start](session.md#sqlite3changeset_start) [session/changeset_iter.html](session/changeset_iter.md) [session/funclist.html](session/funclist.md) [session/sqlite3changeset_start.html](session/sqlite3changeset_start.md) [sessionintro.html#changeset](sessionintro.md#changeset)
- sqlite3changeset_fk_conflicts → [session.html](session.md) [session.html#sqlite3_changeset_iter](session.md#sqlite3_changeset_iter) [session/changeset_iter.html](session/changeset_iter.md) [session/funclist.html](session/funclist.md)
- sqlite3changeset_invert → [session.html](session.md) [session.html#sqlite3changegroup_add_strm](session.md#sqlite3changegroup_add_strm) [session.html#sqlite3changeset_start](session.md#sqlite3changeset_start) [session/funclist.html](session/funclist.md) [session/sqlite3changegroup_add_strm.html](session/sqlite3changegroup_add_strm.md) [session/sqlite3changeset_start.html](session/sqlite3changeset_start.md) [sessionintro.html#changeset](sessionintro.md#changeset)
- sqlite3changeset_new → [session.html](session.md) [session.html#sqlite3_changeset_iter](session.md#sqlite3_changeset_iter) [session.html#sqlite3changeset_finalize](session.md#sqlite3changeset_finalize) [session.html#sqlite3changeset_start](session.md#sqlite3changeset_start) [session/changeset_iter.html](session/changeset_iter.md) [session/funclist.html](session/funclist.md) [session/sqlite3changeset_finalize.html](session/sqlite3changeset_finalize.md) [session/sqlite3changeset_start.html](session/sqlite3changeset_start.md) [sessionintro.html#changeset](sessionintro.md#changeset)
- sqlite3changeset_next → [session.html](session.md) [session.html#sqlite3_changeset_iter](session.md#sqlite3_changeset_iter) [session.html#sqlite3changeset_finalize](session.md#sqlite3changeset_finalize) [session.html#sqlite3changeset_new](session.md#sqlite3changeset_new) [session.html#sqlite3changeset_old](session.md#sqlite3changeset_old) [session.html#sqlite3changeset_op](session.md#sqlite3changeset_op) [session.html#sqlite3changeset_start](session.md#sqlite3changeset_start) [session/changeset_iter.html](session/changeset_iter.md) [session/funclist.html](session/funclist.md) [session/sqlite3changeset_finalize.html](session/sqlite3changeset_finalize.md) [session/sqlite3changeset_new.html](session/sqlite3changeset_new.md) [session/sqlite3changeset_old.html](session/sqlite3changeset_old.md) [session/sqlite3changeset_op.html](session/sqlite3changeset_op.md) [session/sqlite3changeset_start.html](session/sqlite3changeset_start.md) [sessionintro.html#changeset](sessionintro.md#changeset)
- sqlite3changeset_old → [session.html](session.md) [session.html#sqlite3_changeset_iter](session.md#sqlite3_changeset_iter) [session.html#sqlite3changeset_start](session.md#sqlite3changeset_start) [session/changeset_iter.html](session/changeset_iter.md) [session/funclist.html](session/funclist.md) [session/sqlite3changeset_start.html](session/sqlite3changeset_start.md) [sessionintro.html#changeset](sessionintro.md#changeset)
- sqlite3changeset_op → [session.html](session.md) [session.html#sqlite3_changeset_iter](session.md#sqlite3_changeset_iter) [session.html#sqlite3changeset_start](session.md#sqlite3changeset_start) [session/changeset_iter.html](session/changeset_iter.md) [session/funclist.html](session/funclist.md) [session/sqlite3changeset_start.html](session/sqlite3changeset_start.md) [sessionintro.html#changeset](sessionintro.md#changeset)
- sqlite3changeset_pk → [session.html](session.md) [session.html#sqlite3_changeset_iter](session.md#sqlite3_changeset_iter) [session/changeset_iter.html](session/changeset_iter.md) [session/funclist.html](session/funclist.md)
- sqlite3changeset_start → [session.html](session.md) [session.html#sqlite3_changeset_iter](session.md#sqlite3_changeset_iter) [session.html#sqlite3changegroup_add_strm](session.md#sqlite3changegroup_add_strm) [session.html#sqlite3changeset_finalize](session.md#sqlite3changeset_finalize) [session.html#sqlite3changeset_new](session.md#sqlite3changeset_new) [session.html#sqlite3changeset_next](session.md#sqlite3changeset_next) [session.html#sqlite3changeset_old](session.md#sqlite3changeset_old) [session.html#sqlite3changeset_op](session.md#sqlite3changeset_op) [session.html#sqlite3session_changeset](session.md#sqlite3session_changeset) [session/changeset_iter.html](session/changeset_iter.md) [session/funclist.html](session/funclist.md) [session/sqlite3changegroup_add_strm.html](session/sqlite3changegroup_add_strm.md) [session/sqlite3changeset_finalize.html](session/sqlite3changeset_finalize.md) [session/sqlite3changeset_new.html](session/sqlite3changeset_new.md) [session/sqlite3changeset_next.html](session/sqlite3changeset_next.md) [session/sqlite3changeset_old.html](session/sqlite3changeset_old.md) [session/sqlite3changeset_op.html](session/sqlite3changeset_op.md) [session/sqlite3session_changeset.html](session/sqlite3session_changeset.md) [sessionintro.html#changeset](sessionintro.md#changeset)
- sqlite3changeset_start_v2 → [changes.html#version_3_26_0](changes.md#version_3_26_0) [releaselog/3_26_0.html](releaselog/3_26_0.md) [session.html#SQLITE_CHANGESETSTART_INVERT](session.md#SQLITE_CHANGESETSTART_INVERT) [session.html#sqlite3_changeset_iter](session.md#sqlite3_changeset_iter) [session/c_changesetstart_invert.html](session/c_changesetstart_invert.md) [session/changeset_iter.html](session/changeset_iter.md)
- sqlite3changeset_start_v2_strm → [session.html#SQLITE_CHANGESETSTART_INVERT](session.md#SQLITE_CHANGESETSTART_INVERT) [session/c_changesetstart_invert.html](session/c_changesetstart_invert.md)
- sqlite3rebaser_configure → [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3rebaser_create → [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3rebaser_delete → [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3rebaser_rebase → [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3session_attach → [session.html](session.md) [session.html#sqlite3_session](session.md#sqlite3_session) [session.html#sqlite3session_diff](session.md#sqlite3session_diff) [session/funclist.html](session/funclist.md) [session/session.html](session/session.md) [session/sqlite3session_diff.html](session/sqlite3session_diff.md) [sessionintro.html#changeset](sessionintro.md#changeset)
- sqlite3session_changeset → [session.html](session.md) [session.html#sqlite3_session](session.md#sqlite3_session) [session.html#sqlite3changegroup_add_strm](session.md#sqlite3changegroup_add_strm) [session.html#sqlite3changeset_start](session.md#sqlite3changeset_start) [session.html#sqlite3session_attach](session.md#sqlite3session_attach) [session.html#sqlite3session_diff](session.md#sqlite3session_diff) [session.html#sqlite3session_enable](session.md#sqlite3session_enable) [session.html#sqlite3session_isempty](session.md#sqlite3session_isempty) [session/funclist.html](session/funclist.md) [session/session.html](session/session.md) [session/sqlite3changegroup_add_strm.html](session/sqlite3changegroup_add_strm.md) [session/sqlite3changeset_start.html](session/sqlite3changeset_start.md) [session/sqlite3session_attach.html](session/sqlite3session_attach.md) [session/sqlite3session_diff.html](session/sqlite3session_diff.md) [session/sqlite3session_enable.html](session/sqlite3session_enable.md) [session/sqlite3session_isempty.html](session/sqlite3session_isempty.md) [sessionintro.html#changeset](sessionintro.md#changeset)
- sqlite3session_changeset_size → [session.html](session.md) [session.html#SQLITE_SESSION_OBJCONFIG_ROWID](session.md#SQLITE_SESSION_OBJCONFIG_ROWID) [session.html#sqlite3_session](session.md#sqlite3_session) [session/c_session_objconfig_rowid.html](session/c_session_objconfig_rowid.md) [session/funclist.html](session/funclist.md) [session/session.html](session/session.md)
- sqlite3session_config → [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3session_create → [session.html](session.md) [session.html#sqlite3_session](session.md#sqlite3_session) [session.html#sqlite3session_delete](session.md#sqlite3session_delete) [session/funclist.html](session/funclist.md) [session/session.html](session/session.md) [session/sqlite3session_delete.html](session/sqlite3session_delete.md) [sessionintro.html#changeset](sessionintro.md#changeset)
- sqlite3session_delete → [session.html](session.md) [session.html#sqlite3_session](session.md#sqlite3_session) [session.html#sqlite3session_create](session.md#sqlite3session_create) [session/funclist.html](session/funclist.md) [session/session.html](session/session.md) [session/sqlite3session_create.html](session/sqlite3session_create.md) [sessionintro.html#changeset](sessionintro.md#changeset)
- sqlite3session_diff → [session.html](session.md) [session.html#sqlite3_session](session.md#sqlite3_session) [session/funclist.html](session/funclist.md) [session/session.html](session/session.md)
- sqlite3session_enable → [session.html](session.md) [session.html#sqlite3_session](session.md#sqlite3_session) [session.html#sqlite3session_changeset](session.md#sqlite3session_changeset) [session/funclist.html](session/funclist.md) [session/session.html](session/session.md) [session/sqlite3session_changeset.html](session/sqlite3session_changeset.md)
- sqlite3session_indirect → [session.html](session.md) [session.html#sqlite3_session](session.md#sqlite3_session) [session.html#sqlite3changeset_op](session.md#sqlite3changeset_op) [session/funclist.html](session/funclist.md) [session/session.html](session/session.md) [session/sqlite3changeset_op.html](session/sqlite3changeset_op.md)
- sqlite3session_isempty → [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3session_memory_used → [session.html](session.md) [session/funclist.html](session/funclist.md)
- sqlite3session_object_config → [session.html](session.md) [session.html#sqlite3_session](session.md#sqlite3_session) [session/funclist.html](session/funclist.md) [session/session.html](session/session.md)
- sqlite3session_patchset → [session.html](session.md) [session.html#sqlite3_session](session.md#sqlite3_session) [session.html#sqlite3changegroup_add_strm](session.md#sqlite3changegroup_add_strm) [session/funclist.html](session/funclist.md) [session/session.html](session/session.md) [session/sqlite3changegroup_add_strm.html](session/sqlite3changegroup_add_strm.md) [sessionintro.html#changeset](sessionintro.md#changeset)
- sqlite3session_table_filter → [session.html](session.md) [session.html#sqlite3_session](session.md#sqlite3_session) [session/funclist.html](session/funclist.md) [session/session.html](session/session.md)
- SQLITE_4_BYTE_ALIGNED_MALLOC → [c3ref/free.html](c3ref/free.md) [capi3ref.html#sqlite3_free](capi3ref.md#sqlite3_free)
- SQLITE_ABORT → [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/blob_read.html](c3ref/blob_read.md) [c3ref/blob_write.html](c3ref/blob_write.md) [c3ref/c_fail.html](c3ref/c_fail.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vtab_on_conflict.html](c3ref/vtab_on_conflict.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_FAIL](capi3ref.md#SQLITE_FAIL) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_blob_read](capi3ref.md#sqlite3_blob_read) [capi3ref.html#sqlite3_blob_write](capi3ref.md#sqlite3_blob_write) [capi3ref.html#sqlite3_vtab_on_conflict](capi3ref.md#sqlite3_vtab_on_conflict) [changes.html#version_3_8_7_2](changes.md#version_3_8_7_2) [lang_transaction.html#immediate](lang_transaction.md#immediate) [oldnews.html](oldnews.md) [releaselog/3_8_7_2.html](releaselog/3_8_7_2.md) [rescode.html#abort_rollback](rescode.md#abort_rollback) [rescode.html#interrupt](rescode.md#interrupt) [rescode.html#pve](rescode.md#pve)
- SQLITE_ABORT_ROLLBACK → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_8_7_2](changes.md#version_3_8_7_2) [lang_transaction.html#immediate](lang_transaction.md#immediate) [oldnews.html](oldnews.md) [releaselog/3_8_7_2.html](releaselog/3_8_7_2.md) [rescode.html#abort](rescode.md#abort) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_ACCESS_EXISTS → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vfs.html#sqlite3vfsxaccess](c3ref/vfs.md#sqlite3vfsxaccess) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3vfsxaccess](capi3ref.md#sqlite3vfsxaccess)
- SQLITE_ACCESS_READ → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vfs.html#sqlite3vfsxaccess](c3ref/vfs.md#sqlite3vfsxaccess) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3vfsxaccess](capi3ref.md#sqlite3vfsxaccess)
- SQLITE_ACCESS_READWRITE → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vfs.html#sqlite3vfsxaccess](c3ref/vfs.md#sqlite3vfsxaccess) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3vfsxaccess](capi3ref.md#sqlite3vfsxaccess)
- SQLITE_ALLOW_COVERING_INDEX_SCAN → [c3ref/c_config_covering_index_scan.html#sqliteconfigcoveringindexscan](c3ref/c_config_covering_index_scan.md#sqliteconfigcoveringindexscan) [capi3ref.html#sqliteconfigcoveringindexscan](capi3ref.md#sqliteconfigcoveringindexscan)
- SQLITE_ALLOW_URI_AUTHORITY → [changes.html#version_3_8_0](changes.md#version_3_8_0) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md) [uri.html](uri.md)
- SQLITE_ALTER_TABLE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_ANALYZE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_ANY → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_APICALL → [compile.html#apicall](compile.md#apicall) [compile.html#cdecl](compile.md#cdecl) [compile.html#sysapi](compile.md#sysapi) [compile.html#tclapi](compile.md#tclapi)
- SQLITE_ATTACH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_AUTH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#auth_user](rescode.md#auth_user) [rescode.html#pve](rescode.md#pve)
- SQLITE_AUTH_USER → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_BLOB → [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob)
- SQLITE_BUSY → [34to35.html](34to35.md) [backup.html](backup.md) [c3ref/backup_finish.html#sqlite3backupfinish](c3ref/backup_finish.md#sqlite3backupfinish) [c3ref/backup_finish.html#sqlite3backupstep](c3ref/backup_finish.md#sqlite3backupstep) [c3ref/busy_handler.html](c3ref/busy_handler.md) [c3ref/busy_timeout.html](c3ref/busy_timeout.md) [c3ref/c_dbconfig_defensive.html#sqlitedbconfiglookaside](c3ref/c_dbconfig_defensive.md#sqlitedbconfiglookaside) [c3ref/close.html](c3ref/close.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/get_autocommit.html](c3ref/get_autocommit.md) [c3ref/step.html](c3ref/step.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_busy_handler](capi3ref.md#sqlite3_busy_handler) [capi3ref.html#sqlite3_busy_timeout](capi3ref.md#sqlite3_busy_timeout) [capi3ref.html#sqlite3_close](capi3ref.md#sqlite3_close) [capi3ref.html#sqlite3_get_autocommit](capi3ref.md#sqlite3_get_autocommit) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [capi3ref.html#sqlite3backupfinish](capi3ref.md#sqlite3backupfinish) [capi3ref.html#sqlite3backupstep](capi3ref.md#sqlite3backupstep) [capi3ref.html#sqlitedbconfiglookaside](capi3ref.md#sqlitedbconfiglookaside) [changes.html#version_3_4_0](changes.md#version_3_4_0) [changes.html#version_3_6_5](changes.md#version_3_6_5) [compile.html#omit_autoreset](compile.md#omit_autoreset) [isolation.html](isolation.md) [lang_transaction.html](lang_transaction.md) [lang_transaction.html#immediate](lang_transaction.md#immediate) [news.html](news.md) [pragma.html#pragma_wal_checkpoint](pragma.md#pragma_wal_checkpoint) [releaselog/3_4_0.html](releaselog/3_4_0.md) [releaselog/3_6_5.html](releaselog/3_6_5.md) [rescode.html#busy_recovery](rescode.md#busy_recovery) [rescode.html#busy_snapshot](rescode.md#busy_snapshot) [rescode.html#locked](rescode.md#locked) [rescode.html#pve](rescode.md#pve) [wal.html#busy](wal.md#busy)
- SQLITE_BUSY_RECOVERY → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#busy](rescode.md#busy) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_BUSY_SNAPSHOT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_8_0](changes.md#version_3_8_0) [isolation.html](isolation.md) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md) [rescode.html#busy](rescode.md#busy) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_BUSY_TIMEOUT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CALLBACK → [compile.html#tclapi](compile.md#tclapi)
- SQLITE_CANTOPEN → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/deserialize.html](c3ref/deserialize.md) [c3ref/system_errno.html](c3ref/system_errno.md) [c3ref/vfs.html#sqlite3vfsxaccess](c3ref/vfs.md#sqlite3vfsxaccess) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_deserialize](capi3ref.md#sqlite3_deserialize) [capi3ref.html#sqlite3_system_errno](capi3ref.md#sqlite3_system_errno) [capi3ref.html#sqlite3vfsxaccess](capi3ref.md#sqlite3vfsxaccess) [rescode.html#cantopen_convpath](rescode.md#cantopen_convpath) [rescode.html#cantopen_fullpath](rescode.md#cantopen_fullpath) [rescode.html#cantopen_isdir](rescode.md#cantopen_isdir) [rescode.html#pve](rescode.md#pve)
- SQLITE_CANTOPEN_CONVPATH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc) [rescode.html#ioerr_convpath](rescode.md#ioerr_convpath)
- SQLITE_CANTOPEN_DIRTYWAL → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CANTOPEN_FULLPATH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CANTOPEN_ISDIR → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CANTOPEN_NOTEMPDIR → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CANTOPEN_SYMLINK → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CARRAY_BLOB → [c3ref/carray_bind.html](c3ref/carray_bind.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_carray_bind](capi3ref.md#sqlite3_carray_bind)
- SQLITE_CARRAY_DOUBLE → [c3ref/carray_bind.html](c3ref/carray_bind.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_carray_bind](capi3ref.md#sqlite3_carray_bind)
- SQLITE_CARRAY_INT32 → [c3ref/carray_bind.html](c3ref/carray_bind.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_carray_bind](capi3ref.md#sqlite3_carray_bind)
- SQLITE_CARRAY_INT64 → [c3ref/carray_bind.html](c3ref/carray_bind.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_carray_bind](capi3ref.md#sqlite3_carray_bind)
- SQLITE_CARRAY_TEXT → [c3ref/carray_bind.html](c3ref/carray_bind.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_carray_bind](capi3ref.md#sqlite3_carray_bind)
- SQLITE_CASE_SENSITIVE_LIKE → [optoverview.html#like_opt](optoverview.md#like_opt)
- SQLITE_CDECL → [compile.html#apicall](compile.md#apicall) [compile.html#cdecl](compile.md#cdecl) [compile.html#sysapi](compile.md#sysapi) [compile.html#tclapi](compile.md#tclapi)
- SQLITE_CHANGEGROUP_CONFIG_PATCHSET → [session.html](session.md) [session.html#sqlite3changegroup_config](session.md#sqlite3changegroup_config) [session/constlist.html](session/constlist.md) [session/sqlite3changegroup_config.html](session/sqlite3changegroup_config.md)
- SQLITE_CHANGESET_ABORT → [session.html](session.md) [session.html#sqlite3changeset_apply](session.md#sqlite3changeset_apply) [session/constlist.html](session/constlist.md) [session/sqlite3changeset_apply.html](session/sqlite3changeset_apply.md)
- SQLITE_CHANGESET_CONFLICT → [session.html](session.md) [session.html#sqlite3changeset_apply](session.md#sqlite3changeset_apply) [session.html#sqlite3changeset_conflict](session.md#sqlite3changeset_conflict) [session/constlist.html](session/constlist.md) [session/sqlite3changeset_apply.html](session/sqlite3changeset_apply.md) [session/sqlite3changeset_conflict.html](session/sqlite3changeset_conflict.md)
- SQLITE_CHANGESET_CONSTRAINT → [session.html#sqlite3changeset_apply](session.md#sqlite3changeset_apply) [session/sqlite3changeset_apply.html](session/sqlite3changeset_apply.md)
- SQLITE_CHANGESET_DATA → [session.html#sqlite3changeset_apply](session.md#sqlite3changeset_apply) [session.html#sqlite3changeset_conflict](session.md#sqlite3changeset_conflict) [session/sqlite3changeset_apply.html](session/sqlite3changeset_apply.md) [session/sqlite3changeset_conflict.html](session/sqlite3changeset_conflict.md)
- SQLITE_CHANGESET_NOTFOUND → [session.html#sqlite3changeset_apply](session.md#sqlite3changeset_apply) [session/sqlite3changeset_apply.html](session/sqlite3changeset_apply.md)
- SQLITE_CHANGESET_OMIT → [session.html#sqlite3changeset_apply](session.md#sqlite3changeset_apply) [session/sqlite3changeset_apply.html](session/sqlite3changeset_apply.md)
- SQLITE_CHANGESET_REPLACE → [session.html#sqlite3changeset_apply](session.md#sqlite3changeset_apply) [session/sqlite3changeset_apply.html](session/sqlite3changeset_apply.md)
- SQLITE_CHANGESETAPPLY_FKNOACTION → [session.html](session.md) [session/constlist.html](session/constlist.md)
- SQLITE_CHANGESETAPPLY_INVERT → [changes.html#version_3_26_0](changes.md#version_3_26_0) [releaselog/3_26_0.html](releaselog/3_26_0.md)
- SQLITE_CHANGESETAPPLY_NOSAVEPOINT → [session.html#sqlite3changeset_apply](session.md#sqlite3changeset_apply) [session/sqlite3changeset_apply.html](session/sqlite3changeset_apply.md)
- SQLITE_CHANGESETSTART_INVERT → [changes.html#version_3_26_0](changes.md#version_3_26_0) [releaselog/3_26_0.html](releaselog/3_26_0.md) [session.html](session.md) [session.html#sqlite3changeset_start](session.md#sqlite3changeset_start) [session/constlist.html](session/constlist.md) [session/sqlite3changeset_start.html](session/sqlite3changeset_start.md)
- SQLITE_CHECKPOINT_FULL → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_CHECKPOINT_NOOP → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_51_0](changes.md#version_3_51_0) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- SQLITE_CHECKPOINT_PASSIVE → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/wal_checkpoint.html](c3ref/wal_checkpoint.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_wal_checkpoint](capi3ref.md#sqlite3_wal_checkpoint) [pragma.html#pragma_wal_checkpoint](pragma.md#pragma_wal_checkpoint)
- SQLITE_CHECKPOINT_RESTART → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [wal.html#bigwal](wal.md#bigwal)
- SQLITE_CHECKPOINT_TRUNCATE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_8_8](changes.md#version_3_8_8) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md) [wal.html#bigwal](wal.md#bigwal)
- sqlite_compileoption_get → [c3ref/compileoption_get.html](c3ref/compileoption_get.md) [capi3ref.html#sqlite3_compileoption_get](capi3ref.md#sqlite3_compileoption_get) [changes.html#version_3_6_23](changes.md#version_3_6_23) [compile.html#omit_compileoption_diags](compile.md#omit_compileoption_diags) [lang_corefunc.html](lang_corefunc.md) [oldnews.html](oldnews.md) [pragma.html#pragma_compile_options](pragma.md#pragma_compile_options) [releaselog/3_6_23.html](releaselog/3_6_23.md)
- sqlite_compileoption_used → [c3ref/compileoption_get.html](c3ref/compileoption_get.md) [capi3ref.html#sqlite3_compileoption_get](capi3ref.md#sqlite3_compileoption_get) [changes.html#version_3_6_23](changes.md#version_3_6_23) [compile.html#omit_compileoption_diags](compile.md#omit_compileoption_diags) [lang_corefunc.html](lang_corefunc.md) [oldnews.html](oldnews.md) [releaselog/3_6_23.html](releaselog/3_6_23.md)
- SQLITE_CONFIG_COVERING_INDEX_SCAN → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [compile.html#allow_covering_index_scan](compile.md#allow_covering_index_scan)
- SQLITE_CONFIG_GETMALLOC → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/mem_methods.html](c3ref/mem_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_mem_methods](capi3ref.md#sqlite3_mem_methods) [malloc.html#memsysx](malloc.md#memsysx)
- SQLITE_CONFIG_GETMUTEX → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/mutex_methods.html](c3ref/mutex_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_mutex_methods](capi3ref.md#sqlite3_mutex_methods)
- SQLITE_CONFIG_GETPCACHE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_7_10](changes.md#version_3_7_10) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- SQLITE_CONFIG_GETPCACHE2 → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_7_10](changes.md#version_3_7_10) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- SQLITE_CONFIG_HEAP → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [compile.html#enable_memsys3](compile.md#enable_memsys3) [compile.html#enable_memsys5](compile.md#enable_memsys5) [compile.html#zero_malloc](compile.md#zero_malloc) [malloc.html#memsys5](malloc.md#memsys5) [malloc.html#memsysx](malloc.md#memsysx) [malloc.html#nofrag](malloc.md#nofrag) [news.html](news.md) [security.html](security.md)
- SQLITE_CONFIG_LOG → [c3ref/c_prepare_dont_log.html#sqlitepreparedontlog](c3ref/c_prepare_dont_log.md#sqlitepreparedontlog) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/log.html](c3ref/log.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_log](capi3ref.md#sqlite3_log) [capi3ref.html#sqlitepreparedontlog](capi3ref.md#sqlitepreparedontlog) [changes.html#version_3_42_0](changes.md#version_3_42_0) [changes.html#version_3_6_23](changes.md#version_3_6_23) [changes.html#version_3_8_0](changes.md#version_3_8_0) [errlog.html](errlog.md) [oldnews.html](oldnews.md) [releaselog/3_42_0.html](releaselog/3_42_0.md) [releaselog/3_6_23.html](releaselog/3_6_23.md) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md)
- SQLITE_CONFIG_LOOKASIDE → [c3ref/c_dbconfig_defensive.html#sqlitedbconfiglookaside](c3ref/c_dbconfig_defensive.md#sqlitedbconfiglookaside) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitedbconfiglookaside](capi3ref.md#sqlitedbconfiglookaside) [changes.html#version_3_6_1](changes.md#version_3_6_1) [compile.html#default_lookaside](compile.md#default_lookaside) [debugging.html](debugging.md) [malloc.html#lookaside](malloc.md#lookaside) [news.html](news.md) [releaselog/3_6_1.html](releaselog/3_6_1.md)
- SQLITE_CONFIG_MALLOC → [35to36.html](35to36.md) [c3ref/c_config_covering_index_scan.html#sqliteconfigheap](c3ref/c_config_covering_index_scan.md#sqliteconfigheap) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/mem_methods.html](c3ref/mem_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_mem_methods](capi3ref.md#sqlite3_mem_methods) [capi3ref.html#sqliteconfigheap](capi3ref.md#sqliteconfigheap) [compile.html#malloc_usable_size](compile.md#malloc_usable_size) [compile.html#zero_malloc](compile.md#zero_malloc) [malloc.html#memsysx](malloc.md#memsysx) [testing.html#oomtesting](testing.md#oomtesting)
- SQLITE_CONFIG_MEMDB_MAXSIZE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_27_0](changes.md#version_3_27_0) [compile.html#memdb_default_maxsize](compile.md#memdb_default_maxsize) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- SQLITE_CONFIG_MEMSTATUS → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/hard_heap_limit64.html](c3ref/hard_heap_limit64.md) [c3ref/mem_methods.html](c3ref/mem_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_hard_heap_limit64](capi3ref.md#sqlite3_hard_heap_limit64) [capi3ref.html#sqlite3_mem_methods](capi3ref.md#sqlite3_mem_methods) [compile.html#default_memstatus](compile.md#default_memstatus) [compile.html#max_memory](compile.md#max_memory) [custombuild.html](custombuild.md) [malloc.html#memstatus](malloc.md#memstatus) [malloc.html#memsysx](malloc.md#memsysx)
- SQLITE_CONFIG_MMAP_SIZE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [compile.html#default_mmap_size](compile.md#default_mmap_size) [compile.html#max_mmap_size](compile.md#max_mmap_size) [mmap.html](mmap.md) [pragma.html#pragma_mmap_size](pragma.md#pragma_mmap_size)
- SQLITE_CONFIG_MULTITHREAD → [35to36.html](35to36.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/threadsafe.html](c3ref/threadsafe.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_threadsafe](capi3ref.md#sqlite3_threadsafe) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [compile.html#threadsafe](compile.md#threadsafe) [custombuild.html](custombuild.md) [threadsafe.html](threadsafe.md)
- SQLITE_CONFIG_MUTEX → [35to36.html](35to36.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/mutex_methods.html](c3ref/mutex_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_mutex_methods](capi3ref.md#sqlite3_mutex_methods) [changes.html#version_3_6_1](changes.md#version_3_6_1) [releaselog/3_6_0.html](releaselog/3_6_0.md)
- SQLITE_CONFIG_PAGECACHE → [c3ref/c_config_covering_index_scan.html#sqliteconfigheap](c3ref/c_config_covering_index_scan.md#sqliteconfigheap) [c3ref/c_config_covering_index_scan.html#sqliteconfigpcachehdrsz](c3ref/c_config_covering_index_scan.md#sqliteconfigpcachehdrsz) [c3ref/c_status_malloc_count.html#sqlitestatusmemoryused](c3ref/c_status_malloc_count.md#sqlitestatusmemoryused) [c3ref/c_status_malloc_count.html#sqlitestatuspagecacheoverflow](c3ref/c_status_malloc_count.md#sqlitestatuspagecacheoverflow) [c3ref/c_status_malloc_count.html#sqlitestatuspagecacheused](c3ref/c_status_malloc_count.md#sqlitestatuspagecacheused) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/hard_heap_limit64.html](c3ref/hard_heap_limit64.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_hard_heap_limit64](capi3ref.md#sqlite3_hard_heap_limit64) [capi3ref.html#sqliteconfigheap](capi3ref.md#sqliteconfigheap) [capi3ref.html#sqliteconfigpcachehdrsz](capi3ref.md#sqliteconfigpcachehdrsz) [capi3ref.html#sqlitestatusmemoryused](capi3ref.md#sqlitestatusmemoryused) [capi3ref.html#sqlitestatuspagecacheoverflow](capi3ref.md#sqlitestatuspagecacheoverflow) [capi3ref.html#sqlitestatuspagecacheused](capi3ref.md#sqlitestatuspagecacheused) [changes.html#version_3_6_1](changes.md#version_3_6_1) [changes.html#version_3_7_3](changes.md#version_3_7_3) [changes.html#version_3_8_8](changes.md#version_3_8_8) [compile.html#default_pcache_initsz](compile.md#default_pcache_initsz) [malloc.html#pagecache](malloc.md#pagecache) [releaselog/3_6_1.html](releaselog/3_6_1.md) [releaselog/3_7_3.html](releaselog/3_7_3.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- SQLITE_CONFIG_PCACHE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_7_10](changes.md#version_3_7_10) [oldnews.html](oldnews.md) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- SQLITE_CONFIG_PCACHE2 → [c3ref/c_config_covering_index_scan.html#sqliteconfigpagecache](c3ref/c_config_covering_index_scan.md#sqliteconfigpagecache) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/hard_heap_limit64.html](c3ref/hard_heap_limit64.md) [c3ref/pcache_methods2.html](c3ref/pcache_methods2.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_hard_heap_limit64](capi3ref.md#sqlite3_hard_heap_limit64) [capi3ref.html#sqlite3_pcache_methods2](capi3ref.md#sqlite3_pcache_methods2) [capi3ref.html#sqliteconfigpagecache](capi3ref.md#sqliteconfigpagecache) [changes.html#version_3_7_10](changes.md#version_3_7_10) [oldnews.html](oldnews.md) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- SQLITE_CONFIG_PCACHE_HDRSZ → [c3ref/c_config_covering_index_scan.html#sqliteconfigpagecache](c3ref/c_config_covering_index_scan.md#sqliteconfigpagecache) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqliteconfigpagecache](capi3ref.md#sqliteconfigpagecache) [changes.html#version_3_42_0](changes.md#version_3_42_0) [changes.html#version_3_8_8](changes.md#version_3_8_8) [malloc.html#pagecache](malloc.md#pagecache) [releaselog/3_42_0.html](releaselog/3_42_0.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- SQLITE_CONFIG_PMASZ → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_8_8](changes.md#version_3_8_8) [compile.html#sorter_pmasz](compile.md#sorter_pmasz) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- SQLITE_CONFIG_ROWID_IN_VIEW → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_CONFIG_SCRATCH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_6_1](changes.md#version_3_6_1) [releaselog/3_6_1.html](releaselog/3_6_1.md)
- SQLITE_CONFIG_SERIALIZED → [35to36.html](35to36.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/threadsafe.html](c3ref/threadsafe.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_threadsafe](capi3ref.md#sqlite3_threadsafe) [compile.html#threadsafe](compile.md#threadsafe) [threadsafe.html](threadsafe.md)
- SQLITE_CONFIG_SINGLETHREAD → [35to36.html](35to36.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/threadsafe.html](c3ref/threadsafe.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_threadsafe](capi3ref.md#sqlite3_threadsafe) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [compile.html#threadsafe](compile.md#threadsafe) [threadsafe.html](threadsafe.md)
- SQLITE_CONFIG_SMALL_MALLOC → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_21_0](changes.md#version_3_21_0) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- SQLITE_CONFIG_SORTERREF_SIZE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [compile.html#enable_sorter_references](compile.md#enable_sorter_references)
- SQLITE_CONFIG_SQLLOG → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [compile.html#enable_sqllog](compile.md#enable_sqllog)
- SQLITE_CONFIG_STMTJRNL_SPILL → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_12_0](changes.md#version_3_12_0) [compile.html#stmtjrnl_spill](compile.md#stmtjrnl_spill) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md)
- SQLITE_CONFIG_URI → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/open.html#urifilenamesinsqlite3open](c3ref/open.md#urifilenamesinsqlite3open) [capi3ref.html](capi3ref.md) [capi3ref.html#urifilenamesinsqlite3open](capi3ref.md#urifilenamesinsqlite3open) [lang_vacuum.html#vacuuminto](lang_vacuum.md#vacuuminto) [uri.html](uri.md)
- SQLITE_CONFIG_WIN32_HEAPSIZE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_CONSTRAINT → [c3ref/c_vtab_constraint_support.html#sqlitevtabconstraintsupport](c3ref/c_vtab_constraint_support.md#sqlitevtabconstraintsupport) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitevtabconstraintsupport](capi3ref.md#sqlitevtabconstraintsupport) [changes.html#version_3_26_0](changes.md#version_3_26_0) [lang_createtrigger.html#raise](lang_createtrigger.md#raise) [releaselog/3_26_0.html](releaselog/3_26_0.md) [rescode.html#constraint_check](rescode.md#constraint_check) [rescode.html#constraint_commithook](rescode.md#constraint_commithook) [rescode.html#constraint_datatype](rescode.md#constraint_datatype) [rescode.html#constraint_foreignkey](rescode.md#constraint_foreignkey) [rescode.html#constraint_notnull](rescode.md#constraint_notnull) [rescode.html#constraint_pinned](rescode.md#constraint_pinned) [rescode.html#constraint_primarykey](rescode.md#constraint_primarykey) [rescode.html#constraint_rowid](rescode.md#constraint_rowid) [rescode.html#constraint_trigger](rescode.md#constraint_trigger) [rescode.html#constraint_unique](rescode.md#constraint_unique) [rescode.html#pve](rescode.md#pve) [vtab.html#obc](vtab.md#obc)
- SQLITE_CONSTRAINT_CHECK → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CONSTRAINT_COMMITHOOK → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CONSTRAINT_DATATYPE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CONSTRAINT_FOREIGNKEY → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CONSTRAINT_FUNCTION → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CONSTRAINT_NOTNULL → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CONSTRAINT_PINNED → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CONSTRAINT_PRIMARYKEY → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CONSTRAINT_ROWID → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CONSTRAINT_TRIGGER → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CONSTRAINT_UNIQUE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CONSTRAINT_VTAB → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_COPY → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer)
- SQLITE_CORRUPT → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/open.html#coreuriqueryparameters](c3ref/open.md#coreuriqueryparameters) [c3ref/step.html](c3ref/step.md) [capi3ref.html](capi3ref.md) [capi3ref.html#coreuriqueryparameters](capi3ref.md#coreuriqueryparameters) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [faq.html#q21](faq.md#q21) [imposter.html](imposter.md) [rescode.html#corrupt_index](rescode.md#corrupt_index) [rescode.html#corrupt_vtab](rescode.md#corrupt_vtab) [rescode.html#pve](rescode.md#pve) [session.html#sqlite3changeset_finalize](session.md#sqlite3changeset_finalize) [session/sqlite3changeset_finalize.html](session/sqlite3changeset_finalize.md) [tclsqlite.html#deserialize](tclsqlite.md#deserialize) [testing.html#tension](testing.md#tension) [uri.html#uriimmutable](uri.md#uriimmutable)
- SQLITE_CORRUPT_INDEX → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CORRUPT_SEQUENCE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CORRUPT_VTAB → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [fts5.html#the_insttoken_configuration_option](fts5.md#the_insttoken_configuration_option) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_CREATE_INDEX → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_CREATE_TABLE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_CREATE_TEMP_INDEX → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_CREATE_TEMP_TABLE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_CREATE_TEMP_TRIGGER → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_CREATE_TEMP_VIEW → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_CREATE_TRIGGER → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_CREATE_VIEW → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_CREATE_VTABLE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_DBCONFIG_DEFENSIVE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_26_0](changes.md#version_3_26_0) [changes.html#version_3_39_4](changes.md#version_3_39_4) [changes.html#version_3_40_0](changes.md#version_3_40_0) [changes.html#version_3_44_0](changes.md#version_3_44_0) [cli.html#testing_mode](cli.md#testing_mode) [cves.html#cvetab](cves.md#cvetab) [dbpage.html](dbpage.md) [pragma.html#pragma_journal_mode](pragma.md#pragma_journal_mode) [pragma.html#pragma_schema_version](pragma.md#pragma_schema_version) [pragma.html#pragma_writable_schema](pragma.md#pragma_writable_schema) [releaselog/3_26_0.html](releaselog/3_26_0.md) [releaselog/3_39_4.html](releaselog/3_39_4.md) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md) [security.html](security.md) [vtab.html#xshadowname](vtab.md#xshadowname)
- SQLITE_DBCONFIG_DQS_DDL → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_29_0](changes.md#version_3_29_0) [compile.html#dqs](compile.md#dqs) [news.html](news.md) [quirks.html#dblquote](quirks.md#dblquote) [releaselog/3_29_0.html](releaselog/3_29_0.md)
- SQLITE_DBCONFIG_DQS_DML → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_29_0](changes.md#version_3_29_0) [compile.html#dqs](compile.md#dqs) [news.html](news.md) [quirks.html#dblquote](quirks.md#dblquote) [releaselog/3_29_0.html](releaselog/3_29_0.md)
- SQLITE_DBCONFIG_ENABLE_ATTACH_CREATE → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigenableattachwrite](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenableattachwrite) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitedbconfigenableattachwrite](capi3ref.md#sqlitedbconfigenableattachwrite) [changes.html#version_3_49_0](changes.md#version_3_49_0) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md)
- SQLITE_DBCONFIG_ENABLE_ATTACH_WRITE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_49_0](changes.md#version_3_49_0) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md)
- SQLITE_DBCONFIG_ENABLE_COMMENTS → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_49_0](changes.md#version_3_49_0) [changes.html#version_3_50_0](changes.md#version_3_50_0) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- SQLITE_DBCONFIG_ENABLE_FKEY → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_12_0](changes.md#version_3_12_0) [changes.html#version_3_28_0](changes.md#version_3_28_0) [compile.html#enable_fts3_tokenizer](compile.md#enable_fts3_tokenizer) [fts3.html#f3tknzr](fts3.md#f3tknzr) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/enable_load_extension.html](c3ref/enable_load_extension.md) [c3ref/load_extension.html](c3ref/load_extension.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_enable_load_extension](capi3ref.md#sqlite3_enable_load_extension) [capi3ref.html#sqlite3_load_extension](capi3ref.md#sqlite3_load_extension) [changes.html#version_3_13_0](changes.md#version_3_13_0) [loadext.html](loadext.md) [releaselog/3_13_0.html](releaselog/3_13_0.md)
- SQLITE_DBCONFIG_ENABLE_QPSG → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_20_0](changes.md#version_3_20_0) [compile.html#enable_qpsg](compile.md#enable_qpsg) [queryplanner-ng.html#qpstab](queryplanner-ng.md#qpstab) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- SQLITE_DBCONFIG_ENABLE_TRIGGER → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_35_0](changes.md#version_3_35_0) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [security.html#baddb](security.md#baddb)
- SQLITE_DBCONFIG_ENABLE_VIEW → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_30_0](changes.md#version_3_30_0) [changes.html#version_3_35_0](changes.md#version_3_35_0) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [security.html#baddb](security.md#baddb)
- SQLITE_DBCONFIG_FP_DIGITS → [c3ref/c_dbconfig_defensive.html#dbconfigarguments](c3ref/c_dbconfig_defensive.md#dbconfigarguments) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#dbconfigarguments](capi3ref.md#dbconfigarguments) [changes.html#version_3_53_0](changes.md#version_3_53_0) [floatingpoint.html#\*fpdigits](floatingpoint.md#*fpdigits) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- SQLITE_DBCONFIG_LEGACY_ALTER_TABLE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [lang_altertable.html#altertabrename](lang_altertable.md#altertabrename) [pragma.html#pragma_legacy_alter_table](pragma.md#pragma_legacy_alter_table)
- SQLITE_DBCONFIG_LEGACY_FILE_FORMAT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_31_0](changes.md#version_3_31_0) [fileformat2.html#schemaformat](fileformat2.md#schemaformat) [pragma.html#pragma_legacy_file_format](pragma.md#pragma_legacy_file_format) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- SQLITE_DBCONFIG_LOOKASIDE → [c3ref/c_config_covering_index_scan.html#sqliteconfiglookaside](c3ref/c_config_covering_index_scan.md#sqliteconfiglookaside) [c3ref/c_dbconfig_defensive.html#dbconfigarguments](c3ref/c_dbconfig_defensive.md#dbconfigarguments) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/db_config.html](c3ref/db_config.md) [capi3ref.html](capi3ref.md) [capi3ref.html#dbconfigarguments](capi3ref.md#dbconfigarguments) [capi3ref.html#sqlite3_db_config](capi3ref.md#sqlite3_db_config) [capi3ref.html#sqliteconfiglookaside](capi3ref.md#sqliteconfiglookaside) [changes.html#version_3_49_1](changes.md#version_3_49_1) [compile.html#default_lookaside](compile.md#default_lookaside) [cves.html#cvetab](cves.md#cvetab) [malloc.html#lookaside](malloc.md#lookaside) [news.html](news.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md)
- SQLITE_DBCONFIG_MAINDBNAME → [c3ref/c_dbconfig_defensive.html#dbconfigarguments](c3ref/c_dbconfig_defensive.md#dbconfigarguments) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#dbconfigarguments](capi3ref.md#dbconfigarguments) [changes.html#version_3_15_0](changes.md#version_3_15_0) [dbpage.html](dbpage.md) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md)
- SQLITE_DBCONFIG_MAX → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_16_0](changes.md#version_3_16_0) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md)
- SQLITE_DBCONFIG_RESET_DATABASE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_24_0](changes.md#version_3_24_0) [releaselog/3_24_0.html](releaselog/3_24_0.md)
- SQLITE_DBCONFIG_REVERSE_SCANORDER → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_42_0](changes.md#version_3_42_0) [releaselog/3_42_0.html](releaselog/3_42_0.md)
- SQLITE_DBCONFIG_STMT_SCANSTATUS → [bytecodevtab.html#nexec](bytecodevtab.md#nexec) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_42_0](changes.md#version_3_42_0) [releaselog/3_42_0.html](releaselog/3_42_0.md)
- SQLITE_DBCONFIG_TRIGGER_EQP → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_DBCONFIG_TRUSTED_SCHEMA → [appfunc.html#sec](appfunc.md#sec) [c3ref/c_deterministic.html#sqliteinnocuous](c3ref/c_deterministic.md#sqliteinnocuous) [c3ref/c_prepare_dont_log.html#sqlitepreparefromddl](c3ref/c_prepare_dont_log.md#sqlitepreparefromddl) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqliteinnocuous](capi3ref.md#sqliteinnocuous) [capi3ref.html#sqlitepreparefromddl](capi3ref.md#sqlitepreparefromddl) [changes.html#version_3_31_0](changes.md#version_3_31_0) [cli.html#testing_mode](cli.md#testing_mode) [compile.html#trusted_schema](compile.md#trusted_schema) [pragma.html#pragma_trusted_schema](pragma.md#pragma_trusted_schema) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [security.html#baddb](security.md#baddb) [vtab.html#customvtab](vtab.md#customvtab)
- SQLITE_DBCONFIG_WRITABLE_SCHEMA → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_28_0](changes.md#version_3_28_0) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- sqlite_dbpage → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigdefensive](c3ref/c_dbconfig_defensive.md#sqlitedbconfigdefensive) [capi3ref.html#sqlitedbconfigdefensive](capi3ref.md#sqlitedbconfigdefensive) [changes.html#version_3_47_0](changes.md#version_3_47_0) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md) [vtablist.html](vtablist.md)
- SQLITE_DBPAGE virtual table → [compile.html#enable_dbpage_vtab](compile.md#enable_dbpage_vtab)
- SQLITE_DBSTATUS options → [c3ref/db_status.html](c3ref/db_status.md) [capi3ref.html#sqlite3_db_status](capi3ref.md#sqlite3_db_status)
- SQLITE_DBSTATUS_CACHE_HIT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_7_9](changes.md#version_3_7_9) [releaselog/3_7_9.html](releaselog/3_7_9.md)
- SQLITE_DBSTATUS_CACHE_MISS → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_7_9](changes.md#version_3_7_9) [releaselog/3_7_9.html](releaselog/3_7_9.md)
- SQLITE_DBSTATUS_CACHE_SPILL → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- SQLITE_DBSTATUS_CACHE_USED → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_7_0](changes.md#version_3_7_0) [memstat.html](memstat.md) [releaselog/3_7_0.html](releaselog/3_7_0.md)
- SQLITE_DBSTATUS_CACHE_USED_SHARED → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_14](changes.md#version_3_14) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- SQLITE_DBSTATUS_CACHE_WRITE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_7_12](changes.md#version_3_7_12) [releaselog/3_7_12.html](releaselog/3_7_12.md)
- SQLITE_DBSTATUS_DEFERRED_FKS → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_8_0](changes.md#version_3_8_0) [pragma.html#pragma_defer_foreign_keys](pragma.md#pragma_defer_foreign_keys) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md)
- SQLITE_DBSTATUS_LOOKASIDE_HIT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_7_5](changes.md#version_3_7_5) [oldnews.html](oldnews.md) [releaselog/3_7_5.html](releaselog/3_7_5.md)
- SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_7_5](changes.md#version_3_7_5) [releaselog/3_7_5.html](releaselog/3_7_5.md)
- SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_7_5](changes.md#version_3_7_5) [releaselog/3_7_5.html](releaselog/3_7_5.md)
- SQLITE_DBSTATUS_LOOKASIDE_USED → [c3ref/c_dbconfig_defensive.html#sqlitedbconfiglookaside](c3ref/c_dbconfig_defensive.md#sqlitedbconfiglookaside) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitedbconfiglookaside](capi3ref.md#sqlitedbconfiglookaside) [malloc.html#memstatus](malloc.md#memstatus)
- SQLITE_DBSTATUS_MAX → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_DBSTATUS_SCHEMA_USED → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_7_1](changes.md#version_3_7_1) [releaselog/3_7_1.html](releaselog/3_7_1.md)
- SQLITE_DBSTATUS_STMT_USED → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_7_1](changes.md#version_3_7_1) [releaselog/3_7_1.html](releaselog/3_7_1.md)
- SQLITE_DBSTATUS_TEMPBUF_SPILL → [c3ref/c_dbstatus_options.html#sqlitedbstatusdeferredfks](c3ref/c_dbstatus_options.md#sqlitedbstatusdeferredfks) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitedbstatusdeferredfks](capi3ref.md#sqlitedbstatusdeferredfks) [changes.html#version_3_51_0](changes.md#version_3_51_0) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- SQLITE_DEBUG → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntllockstate](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntllockstate) [capi3ref.html#sqlitefcntllockstate](capi3ref.md#sqlitefcntllockstate) [changes.html#version_3_39_1](changes.md#version_3_39_1) [changes.html#version_3_8_7](changes.md#version_3_8_7) [compile.html#enable_explain_comments](compile.md#enable_explain_comments) [debugging.html](debugging.md) [opcode.html#subprog](opcode.md#subprog) [pragma.html#pragma_parser_trace](pragma.md#pragma_parser_trace) [pragma.html#pragma_vdbe_addoptrace](pragma.md#pragma_vdbe_addoptrace) [pragma.html#pragma_vdbe_debug](pragma.md#pragma_vdbe_debug) [pragma.html#pragma_vdbe_listing](pragma.md#pragma_vdbe_listing) [pragma.html#pragma_vdbe_trace](pragma.md#pragma_vdbe_trace) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md) [releaselog/3_8_7.html](releaselog/3_8_7.md) [th3.html](th3.md)
- SQLITE_DEFAULT_AUTOMATIC_INDEX → [changes.html#version_3_8_0](changes.md#version_3_8_0) [compile.html#omit_automatic_index](compile.md#omit_automatic_index) [optoverview.html#autoindex](optoverview.md#autoindex) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md)
- SQLITE_DEFAULT_AUTOVACUUM → [pragma.html#pragma_auto_vacuum](pragma.md#pragma_auto_vacuum)
- SQLITE_DEFAULT_CACHE_SIZE → [changes.html#version_3_12_0](changes.md#version_3_12_0) [pragma.html#pragma_cache_size](pragma.md#pragma_cache_size) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md)
- SQLITE_DEFAULT_FILE_FORMAT → [fileformat2.html#schemaformat](fileformat2.md#schemaformat)
- SQLITE_DEFAULT_FOREIGN_KEYS → [changes.html#version_3_7_5](changes.md#version_3_7_5) [faq.html#q22](faq.md#q22) [pragma.html#pragma_foreign_keys](pragma.md#pragma_foreign_keys) [releaselog/3_7_5.html](releaselog/3_7_5.md)
- SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT → [pragma.html#pragma_journal_mode](pragma.md#pragma_journal_mode) [pragma.html#pragma_journal_size_limit](pragma.md#pragma_journal_size_limit)
- SQLITE_DEFAULT_LOCKING_MODE → [pragma.html#pragma_locking_mode](pragma.md#pragma_locking_mode)
- SQLITE_DEFAULT_LOOKASIDE → [changes.html#version_3_17_0](changes.md#version_3_17_0) [malloc.html#lookaside](malloc.md#lookaside) [news.html](news.md) [releaselog/3_17_0.html](releaselog/3_17_0.md)
- SQLITE_DEFAULT_MEMSTATUS → [c3ref/c_config_covering_index_scan.html#sqliteconfigmemstatus](c3ref/c_config_covering_index_scan.md#sqliteconfigmemstatus) [c3ref/hard_heap_limit64.html](c3ref/hard_heap_limit64.md) [capi3ref.html#sqlite3_hard_heap_limit64](capi3ref.md#sqlite3_hard_heap_limit64) [capi3ref.html#sqliteconfigmemstatus](capi3ref.md#sqliteconfigmemstatus) [compile.html#max_memory](compile.md#max_memory) [compile.html#rcmd](compile.md#rcmd)
- SQLITE_DEFAULT_MMAP_SIZE → [compile.html#max_mmap_size](compile.md#max_mmap_size) [mmap.html](mmap.md) [pragma.html#pragma_mmap_size](pragma.md#pragma_mmap_size)
- SQLITE_DEFAULT_PAGE_SIZE → [changes.html#version_3_12_0](changes.md#version_3_12_0) [pragma.html#pragma_page_size](pragma.md#pragma_page_size) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md)
- SQLITE_DEFAULT_PCACHE_INITSZ → [changes.html#version_3_17_0](changes.md#version_3_17_0) [releaselog/3_17_0.html](releaselog/3_17_0.md)
- SQLITE_DEFAULT_SYNCHRONOUS → [changes.html#version_3_12_0](changes.md#version_3_12_0) [compile.html#default_wal_synchronous](compile.md#default_wal_synchronous) [compile.html#extra_durable](compile.md#extra_durable) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md)
- SQLITE_DEFAULT_WAL_AUTOCHECKPOINT → [c3ref/wal_autocheckpoint.html](c3ref/wal_autocheckpoint.md) [capi3ref.html#sqlite3_wal_autocheckpoint](capi3ref.md#sqlite3_wal_autocheckpoint) [pragma.html#pragma_wal_autocheckpoint](pragma.md#pragma_wal_autocheckpoint) [wal.html#ckpt](wal.md#ckpt)
- SQLITE_DEFAULT_WAL_SYNCHRONOUS → [changes.html#version_3_12_0](changes.md#version_3_12_0) [compile.html#rcmd](compile.md#rcmd) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md)
- SQLITE_DEFAULT_WORKER_THREADS → [changes.html#version_3_8_7](changes.md#version_3_8_7) [compile.html#max_worker_threads](compile.md#max_worker_threads) [pragma.html#pragma_threads](pragma.md#pragma_threads) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- SQLITE_DELETE → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [c3ref/update_hook.html](c3ref/update_hook.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlite3_update_hook](capi3ref.md#sqlite3_update_hook) [lang_delete.html#truncateopt](lang_delete.md#truncateopt) [session.html#sqlite3changeset_old](session.md#sqlite3changeset_old) [session.html#sqlite3changeset_op](session.md#sqlite3changeset_op) [session/sqlite3changeset_old.html](session/sqlite3changeset_old.md) [session/sqlite3changeset_op.html](session/sqlite3changeset_op.md)
- SQLITE_DENY → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer)
- SQLITE_DESERIALIZE_FREEONCLOSE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_DESERIALIZE_READONLY → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_27_0](changes.md#version_3_27_0) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- SQLITE_DESERIALIZE_RESIZEABLE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_DETACH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_DETERMINISTIC → [appfunc.html](appfunc.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/create_function.html](c3ref/create_function.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [changes.html#version_3_31_0](changes.md#version_3_31_0) [changes.html#version_3_8_3](changes.md#version_3_8_3) [deterministic.html#dtexception](deterministic.md#dtexception) [expridx.html](expridx.md) [json1.html](json1.md) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [releaselog/3_8_3.html](releaselog/3_8_3.md)
- SQLITE_DIRECT_OVERFLOW_READ → [changes.html#version_3_17_0](changes.md#version_3_17_0) [changes.html#version_3_45_0](changes.md#version_3_45_0) [changes.html#version_3_7_9](changes.md#version_3_7_9) [releaselog/3_17_0.html](releaselog/3_17_0.md) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md) [releaselog/3_7_9.html](releaselog/3_7_9.md)
- SQLITE_DIRECTONLY → [appfunc.html](appfunc.md) [appfunc.html#sec](appfunc.md#sec) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/create_function.html](c3ref/create_function.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [changes.html#version_3_30_0](changes.md#version_3_30_0) [changes.html#version_3_31_0](changes.md#version_3_31_0) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [security.html#baddb](security.md#baddb)
- SQLITE_DISABLE_FTS4_DEFERRED → [changes.html#version_3_7_14](changes.md#version_3_7_14) [releaselog/3_7_14.html](releaselog/3_7_14.md)
- SQLITE_DISABLE_INTRINSIC → [changes.html#version_3_17_0](changes.md#version_3_17_0) [releaselog/3_17_0.html](releaselog/3_17_0.md)
- SQLITE_DONE → [c3ref/backup_finish.html#sqlite3backupfinish](c3ref/backup_finish.md#sqlite3backupfinish) [c3ref/backup_finish.html#sqlite3backupstep](c3ref/backup_finish.md#sqlite3backupstep) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/data_count.html](c3ref/data_count.md) [c3ref/step.html](c3ref/step.md) [c3ref/stmt_busy.html](c3ref/stmt_busy.md) [c3ref/vtab_in_first.html](c3ref/vtab_in_first.md) [c3ref/wal_hook.html](c3ref/wal_hook.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_data_count](capi3ref.md#sqlite3_data_count) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [capi3ref.html#sqlite3_stmt_busy](capi3ref.md#sqlite3_stmt_busy) [capi3ref.html#sqlite3_vtab_in_first](capi3ref.md#sqlite3_vtab_in_first) [capi3ref.html#sqlite3_wal_hook](capi3ref.md#sqlite3_wal_hook) [capi3ref.html#sqlite3backupfinish](capi3ref.md#sqlite3backupfinish) [capi3ref.html#sqlite3backupstep](capi3ref.md#sqlite3backupstep) [rescode.html](rescode.md) [rescode.html#pve](rescode.md#pve)
- SQLITE_DQS → [compile.html#rcmd](compile.md#rcmd)
- SQLITE_DROP_INDEX → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_DROP_TABLE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_DROP_TEMP_INDEX → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_DROP_TEMP_TABLE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_DROP_TEMP_TRIGGER → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_DROP_TEMP_VIEW → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_DROP_TRIGGER → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_DROP_VIEW → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_DROP_VTABLE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_EMPTY → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#pve](rescode.md#pve)
- SQLITE_ENABLE_8_3_NAMES → [shortnames.html](shortnames.md) [wal.html#walfile](wal.md#walfile)
- SQLITE_ENABLE_API_ARMOR → [changes.html#version_3_8_8](changes.md#version_3_8_8) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- SQLITE_ENABLE_ATOMIC_WRITE → [rescode.html#ioerr_begin_atomic](rescode.md#ioerr_begin_atomic) [rescode.html#ioerr_commit_atomic](rescode.md#ioerr_commit_atomic) [rescode.html#ioerr_rollback_atomic](rescode.md#ioerr_rollback_atomic)
- SQLITE_ENABLE_BATCH_ATOMIC_WRITE → [changes.html#version_3_21_0](changes.md#version_3_21_0) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- SQLITE_ENABLE_COLUMN_METADATA → [c3ref/column_database_name.html](c3ref/column_database_name.md) [capi3ref.html#sqlite3_column_database_name](capi3ref.md#sqlite3_column_database_name) [changes.html#version_3_8_8](changes.md#version_3_8_8) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- SQLITE_ENABLE_DBPAGE_VTAB → [dbpage.html](dbpage.md)
- SQLITE_ENABLE_DBSTAT_VTAB → [changes.html#version_3_8_10](changes.md#version_3_8_10) [changes.html#version_3_8_10_1](changes.md#version_3_8_10_1) [dbstat.html](dbstat.md) [oldnews.html](oldnews.md) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md) [vtab.html#epovtab](vtab.md#epovtab)
- SQLITE_ENABLE_DESERIALIZE → [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
- SQLITE_ENABLE_EXPLAIN_COMMENTS → [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_8_2](changes.md#version_3_8_2) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_8_2.html](releaselog/3_8_2.md)
- SQLITE_ENABLE_FTS3 → [fts3.html#compiling_and_enabling_fts3_and_fts4](fts3.md#compiling_and_enabling_fts3_and_fts4)
- SQLITE_ENABLE_FTS3_PARENTHESIS → [changes.html#version_3_39_1](changes.md#version_3_39_1) [changes.html#version_3_6_8](changes.md#version_3_6_8) [fts3.html#compiling_and_enabling_fts3_and_fts4](fts3.md#compiling_and_enabling_fts3_and_fts4) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md) [releaselog/3_6_8.html](releaselog/3_6_8.md)
- SQLITE_ENABLE_FTS3_TOKENIZER → [changes.html#version_3_11_0](changes.md#version_3_11_0) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md)
- SQLITE_ENABLE_FTS5 → [changes.html#version_3_9_0](changes.md#version_3_9_0) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- SQLITE_ENABLE_JSON1 → [changes.html#version_3_9_0](changes.md#version_3_9_0) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- SQLITE_ENABLE_MEMORY_MANAGEMENT → [c3ref/db_release_memory.html](c3ref/db_release_memory.md) [c3ref/release_memory.html](c3ref/release_memory.md) [capi3ref.html#sqlite3_db_release_memory](capi3ref.md#sqlite3_db_release_memory) [capi3ref.html#sqlite3_release_memory](capi3ref.md#sqlite3_release_memory) [changes.html#version_3_7_3](changes.md#version_3_7_3) [malloc.html#memstatus](malloc.md#memstatus) [releaselog/3_7_3.html](releaselog/3_7_3.md)
- SQLITE_ENABLE_MEMSYS3 → [c3ref/c_config_covering_index_scan.html#sqliteconfigheap](c3ref/c_config_covering_index_scan.md#sqliteconfigheap) [capi3ref.html#sqliteconfigheap](capi3ref.md#sqliteconfigheap) [malloc.html#memsysx](malloc.md#memsysx)
- SQLITE_ENABLE_MEMSYS5 → [c3ref/c_config_covering_index_scan.html#sqliteconfigheap](c3ref/c_config_covering_index_scan.md#sqliteconfigheap) [capi3ref.html#sqliteconfigheap](capi3ref.md#sqliteconfigheap) [malloc.html#memsys5](malloc.md#memsys5)
- SQLITE_ENABLE_NORMALIZE → [c3ref/expanded_sql.html](c3ref/expanded_sql.md) [capi3ref.html#sqlite3_expanded_sql](capi3ref.md#sqlite3_expanded_sql)
- SQLITE_ENABLE_NULL_TRIM → [changes.html#version_3_17_0](changes.md#version_3_17_0) [releaselog/3_17_0.html](releaselog/3_17_0.md)
- SQLITE_ENABLE_ORDERED_SET_AGGREGATES → [percentile.html#\*percentilecontfunc](percentile.md#*percentilecontfunc) [percentile.html#\*percentilediscfunc](percentile.md#*percentilediscfunc)
- SQLITE_ENABLE_PREUPDATE_HOOK → [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite)
- SQLITE_ENABLE_QPSG → [changes.html#version_3_20_0](changes.md#version_3_20_0) [queryplanner-ng.html#qpstab](queryplanner-ng.md#qpstab) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- SQLITE_ENABLE_RBU → [rbu.html](rbu.md)
- SQLITE_ENABLE_RTREE → [rtree.html](rtree.md)
- SQLITE_ENABLE_SNAPSHOT → [c3ref/snapshot_cmp.html](c3ref/snapshot_cmp.md) [c3ref/snapshot_free.html](c3ref/snapshot_free.md) [c3ref/snapshot_get.html](c3ref/snapshot_get.md) [c3ref/snapshot_open.html](c3ref/snapshot_open.md) [c3ref/snapshot_recover.html](c3ref/snapshot_recover.md) [capi3ref.html#sqlite3_snapshot_cmp](capi3ref.md#sqlite3_snapshot_cmp) [capi3ref.html#sqlite3_snapshot_free](capi3ref.md#sqlite3_snapshot_free) [capi3ref.html#sqlite3_snapshot_get](capi3ref.md#sqlite3_snapshot_get) [capi3ref.html#sqlite3_snapshot_open](capi3ref.md#sqlite3_snapshot_open) [capi3ref.html#sqlite3_snapshot_recover](capi3ref.md#sqlite3_snapshot_recover)
- SQLITE_ENABLE_SORTER_REFERENCES → [c3ref/c_config_covering_index_scan.html#sqliteconfigsorterrefsize](c3ref/c_config_covering_index_scan.md#sqliteconfigsorterrefsize) [capi3ref.html#sqliteconfigsorterrefsize](capi3ref.md#sqliteconfigsorterrefsize)
- SQLITE_ENABLE_SQLLOG → [c3ref/c_config_covering_index_scan.html#sqliteconfigsqllog](c3ref/c_config_covering_index_scan.md#sqliteconfigsqllog) [capi3ref.html#sqliteconfigsqllog](capi3ref.md#sqliteconfigsqllog)
- SQLITE_ENABLE_STAT2 → [changes.html#version_3_6_18](changes.md#version_3_6_18) [changes.html#version_3_6_20](changes.md#version_3_6_20) [changes.html#version_3_7_6](changes.md#version_3_7_6) [changes.html#version_3_7_9](changes.md#version_3_7_9) [lang_analyze.html#statanal](lang_analyze.md#statanal) [oldnews.html](oldnews.md) [releaselog/3_6_18.html](releaselog/3_6_18.md) [releaselog/3_6_20.html](releaselog/3_6_20.md) [releaselog/3_7_6.html](releaselog/3_7_6.md) [releaselog/3_7_9.html](releaselog/3_7_9.md)
- SQLITE_ENABLE_STAT3 → [changes.html#version_3_30_0](changes.md#version_3_30_0) [changes.html#version_3_7_9](changes.md#version_3_7_9) [changes.html#version_3_8_3_1](changes.md#version_3_8_3_1) [compile.html#enable_stat2](compile.md#enable_stat2) [compile.html#enable_stat4](compile.md#enable_stat4) [fileformat2.html#stat3tab](fileformat2.md#stat3tab) [lang_analyze.html#statanal](lang_analyze.md#statanal) [oldnews.html](oldnews.md) [optoverview.html#rangequery](optoverview.md#rangequery) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md) [releaselog/3_7_9.html](releaselog/3_7_9.md) [releaselog/3_8_3_1.html](releaselog/3_8_3_1.md)
- SQLITE_ENABLE_STAT4 → [c3ref/get_auxdata.html](c3ref/get_auxdata.md) [c3ref/prepare.html](c3ref/prepare.md) [capi3ref.html#sqlite3_get_auxdata](capi3ref.md#sqlite3_get_auxdata) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [changes.html#version_3_41_2](changes.md#version_3_41_2) [changes.html#version_3_8_1](changes.md#version_3_8_1) [changes.html#version_3_8_3_1](changes.md#version_3_8_3_1) [changes.html#version_3_8_4](changes.md#version_3_8_4) [compile.html#enable_stat3](compile.md#enable_stat3) [fileformat2.html#stat3tab](fileformat2.md#stat3tab) [fileformat2.html#stat4tab](fileformat2.md#stat4tab) [lang_analyze.html#statanal](lang_analyze.md#statanal) [oldnews.html](oldnews.md) [optoverview.html#rangequery](optoverview.md#rangequery) [releaselog/3_41_2.html](releaselog/3_41_2.md) [releaselog/3_8_1.html](releaselog/3_8_1.md) [releaselog/3_8_3_1.html](releaselog/3_8_3_1.md) [releaselog/3_8_4.html](releaselog/3_8_4.md) [releaselog/3_8_4_1.html](releaselog/3_8_4_1.md) [releaselog/3_8_4_2.html](releaselog/3_8_4_2.md) [releaselog/3_8_4_3.html](releaselog/3_8_4_3.md)
- SQLITE_ENABLE_STMT_SCANSTATUS → [bytecodevtab.html#nexec](bytecodevtab.md#nexec) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigstmtscanstatus](c3ref/c_dbconfig_defensive.md#sqlitedbconfigstmtscanstatus) [c3ref/stmt_scanstatus.html](c3ref/stmt_scanstatus.md) [c3ref/stmt_scanstatus_reset.html](c3ref/stmt_scanstatus_reset.md) [capi3ref.html#sqlite3_stmt_scanstatus](capi3ref.md#sqlite3_stmt_scanstatus) [capi3ref.html#sqlite3_stmt_scanstatus_reset](capi3ref.md#sqlite3_stmt_scanstatus_reset) [capi3ref.html#sqlitedbconfigstmtscanstatus](capi3ref.md#sqlitedbconfigstmtscanstatus) [changes.html#version_3_41_0](changes.md#version_3_41_0) [changes.html#version_3_8_8](changes.md#version_3_8_8) [profile.html](profile.md) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- SQLITE_ENABLE_STMTVTAB → [stmt.html](stmt.md)
- SQLITE_ENABLE_TREE_EXPLAIN → [changes.html#version_3_7_10](changes.md#version_3_7_10) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- SQLITE_ENABLE_UNKNOWN_SQL_FUNCTION → [changes.html#version_3_14](changes.md#version_3_14) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- SQLITE_ENABLE_UNLOCK_NOTIFY → [c3ref/unlock_notify.html](c3ref/unlock_notify.md) [capi3ref.html#sqlite3_unlock_notify](capi3ref.md#sqlite3_unlock_notify) [unlock_notify.html](unlock_notify.md)
- SQLITE_ENABLE_UPDATE_DELETE_LIMIT → [changes.html#version_3_22_0](changes.md#version_3_22_0) [changes.html#version_3_6_4](changes.md#version_3_6_4) [howtocompile.html#amal](howtocompile.md#amal) [lang_createtrigger.html](lang_createtrigger.md) [lang_delete.html](lang_delete.md) [lang_returning.html](lang_returning.md) [lang_update.html#upfrom](lang_update.md#upfrom) [releaselog/3_22_0.html](releaselog/3_22_0.md) [releaselog/3_6_4.html](releaselog/3_6_4.md)
- SQLITE_ERROR → [c3ref/blob_read.html](c3ref/blob_read.md) [c3ref/blob_write.html](c3ref/blob_write.md) [c3ref/c_config_covering_index_scan.html#sqliteconfiggetmutex](c3ref/c_config_covering_index_scan.md#sqliteconfiggetmutex) [c3ref/c_config_covering_index_scan.html#sqliteconfigheap](c3ref/c_config_covering_index_scan.md#sqliteconfigheap) [c3ref/c_config_covering_index_scan.html#sqliteconfigmultithread](c3ref/c_config_covering_index_scan.md#sqliteconfigmultithread) [c3ref/c_config_covering_index_scan.html#sqliteconfigmutex](c3ref/c_config_covering_index_scan.md#sqliteconfigmutex) [c3ref/c_config_covering_index_scan.html#sqliteconfigserialized](c3ref/c_config_covering_index_scan.md#sqliteconfigserialized) [c3ref/c_config_covering_index_scan.html#sqliteconfigsinglethread](c3ref/c_config_covering_index_scan.md#sqliteconfigsinglethread) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/load_extension.html](c3ref/load_extension.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/step.html](c3ref/step.md) [c3ref/vtab_in_first.html](c3ref/vtab_in_first.md) [c3ref/win32_set_directory.html](c3ref/win32_set_directory.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_blob_read](capi3ref.md#sqlite3_blob_read) [capi3ref.html#sqlite3_blob_write](capi3ref.md#sqlite3_blob_write) [capi3ref.html#sqlite3_load_extension](capi3ref.md#sqlite3_load_extension) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [capi3ref.html#sqlite3_vtab_in_first](capi3ref.md#sqlite3_vtab_in_first) [capi3ref.html#sqlite3_win32_set_directory](capi3ref.md#sqlite3_win32_set_directory) [capi3ref.html#sqliteconfiggetmutex](capi3ref.md#sqliteconfiggetmutex) [capi3ref.html#sqliteconfigheap](capi3ref.md#sqliteconfigheap) [capi3ref.html#sqliteconfigmultithread](capi3ref.md#sqliteconfigmultithread) [capi3ref.html#sqliteconfigmutex](capi3ref.md#sqliteconfigmutex) [capi3ref.html#sqliteconfigserialized](capi3ref.md#sqliteconfigserialized) [capi3ref.html#sqliteconfigsinglethread](capi3ref.md#sqliteconfigsinglethread) [changes.html#version_3_46_1](changes.md#version_3_46_1) [changes.html#version_3_6_15](changes.md#version_3_6_15) [changes.html#version_3_6_5](changes.md#version_3_6_5) [changes.html#version_3_7_5](changes.md#version_3_7_5) [releaselog/3_46_1.html](releaselog/3_46_1.md) [releaselog/3_6_15.html](releaselog/3_6_15.md) [releaselog/3_6_5.html](releaselog/3_6_5.md) [releaselog/3_7_5.html](releaselog/3_7_5.md) [rescode.html#pve](rescode.md#pve) [vtab.html#xconnect](vtab.md#xconnect) [vtab.html#xcreate](vtab.md#xcreate)
- SQLITE_ERROR_KEY → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_ERROR_MISSING_COLLSEQ → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_ERROR_RESERVESIZE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_ERROR_RETRY → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#error_missing_collseq](rescode.md#error_missing_collseq) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_ERROR_SNAPSHOT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_ERROR_UNABLE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_EXTRA_DURABLE → [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_12_0](changes.md#version_3_12_0) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md)
- SQLITE_FAIL → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vtab_on_conflict.html](c3ref/vtab_on_conflict.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_vtab_on_conflict](capi3ref.md#sqlite3_vtab_on_conflict)
- SQLITE_FCNTL_BEGIN_ATOMIC_WRITE → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlbeginatomicwrite](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlbeginatomicwrite) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlcommitatomicwrite](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlcommitatomicwrite) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlrollbackatomicwrite](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlrollbackatomicwrite) [c3ref/c_iocap_atomic.html](c3ref/c_iocap_atomic.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_IOCAP_ATOMIC](capi3ref.md#SQLITE_IOCAP_ATOMIC) [capi3ref.html#sqlitefcntlbeginatomicwrite](capi3ref.md#sqlitefcntlbeginatomicwrite) [capi3ref.html#sqlitefcntlcommitatomicwrite](capi3ref.md#sqlitefcntlcommitatomicwrite) [capi3ref.html#sqlitefcntlrollbackatomicwrite](capi3ref.md#sqlitefcntlrollbackatomicwrite) [compile.html#enable_batch_atomic_write](compile.md#enable_batch_atomic_write) [rescode.html#ioerr_begin_atomic](rescode.md#ioerr_begin_atomic)
- SQLITE_FCNTL_BLOCK_ON_CONNECT → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlblockonconnect](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlblockonconnect) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlblockonconnect](capi3ref.md#sqlitefcntlblockonconnect)
- SQLITE_FCNTL_BUSYHANDLER → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlbusyhandler](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlbusyhandler) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlbusyhandler](capi3ref.md#sqlitefcntlbusyhandler) [changes.html#version_3_7_15](changes.md#version_3_7_15) [releaselog/3_7_15.html](releaselog/3_7_15.md)
- SQLITE_FCNTL_CHUNK_SIZE → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlchunksize](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlchunksize) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlchunksize](capi3ref.md#sqlitefcntlchunksize) [changes.html#version_3_7_1](changes.md#version_3_7_1) [releaselog/3_7_1.html](releaselog/3_7_1.md)
- SQLITE_FCNTL_CKPT_DONE → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlckptdone](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlckptdone) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlckptdone](capi3ref.md#sqlitefcntlckptdone)
- SQLITE_FCNTL_CKPT_START → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlckptstart](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlckptstart) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlckptstart](capi3ref.md#sqlitefcntlckptstart)
- SQLITE_FCNTL_CKSM_FILE → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlcksmfile](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlcksmfile) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlcksmfile](capi3ref.md#sqlitefcntlcksmfile)
- SQLITE_FCNTL_COMMIT_ATOMIC_WRITE → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlbeginatomicwrite](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlbeginatomicwrite) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlcommitatomicwrite](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlcommitatomicwrite) [c3ref/c_iocap_atomic.html](c3ref/c_iocap_atomic.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_IOCAP_ATOMIC](capi3ref.md#SQLITE_IOCAP_ATOMIC) [capi3ref.html#sqlitefcntlbeginatomicwrite](capi3ref.md#sqlitefcntlbeginatomicwrite) [capi3ref.html#sqlitefcntlcommitatomicwrite](capi3ref.md#sqlitefcntlcommitatomicwrite) [compile.html#enable_batch_atomic_write](compile.md#enable_batch_atomic_write) [rescode.html#ioerr_commit_atomic](rescode.md#ioerr_commit_atomic)
- SQLITE_FCNTL_COMMIT_PHASETWO → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlcommitphasetwo](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlcommitphasetwo) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlcommitphasetwo](capi3ref.md#sqlitefcntlcommitphasetwo)
- SQLITE_FCNTL_DATA_VERSION → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntldataversion](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntldataversion) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/file_control.html](c3ref/file_control.md) [c3ref/total_changes.html](c3ref/total_changes.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_file_control](capi3ref.md#sqlite3_file_control) [capi3ref.html#sqlite3_total_changes](capi3ref.md#sqlite3_total_changes) [capi3ref.html#sqlitefcntldataversion](capi3ref.md#sqlitefcntldataversion) [changes.html#version_3_25_0](changes.md#version_3_25_0) [releaselog/3_25_0.html](releaselog/3_25_0.md) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md)
- SQLITE_FCNTL_EXTERNAL_READER → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlexternalreader](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlexternalreader) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlexternalreader](capi3ref.md#sqlitefcntlexternalreader)
- SQLITE_FCNTL_FILE_POINTER → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlfilepointer](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlfilepointer) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntljournalpointer](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntljournalpointer) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/file_control.html](c3ref/file_control.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_file_control](capi3ref.md#sqlite3_file_control) [capi3ref.html#sqlitefcntlfilepointer](capi3ref.md#sqlitefcntlfilepointer) [capi3ref.html#sqlitefcntljournalpointer](capi3ref.md#sqlitefcntljournalpointer) [changes.html#version_3_7_4](changes.md#version_3_7_4) [releaselog/3_7_4.html](releaselog/3_7_4.md)
- SQLITE_FCNTL_FILESTAT → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlfilestat](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlfilestat) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlfilestat](capi3ref.md#sqlitefcntlfilestat)
- SQLITE_FCNTL_GET_LOCKPROXYFILE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_FCNTL_HAS_MOVED → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlhasmoved](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlhasmoved) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlhasmoved](capi3ref.md#sqlitefcntlhasmoved)
- SQLITE_FCNTL_JOURNAL_POINTER → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlfilepointer](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlfilepointer) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntljournalpointer](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntljournalpointer) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/file_control.html](c3ref/file_control.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_file_control](capi3ref.md#sqlite3_file_control) [capi3ref.html#sqlitefcntlfilepointer](capi3ref.md#sqlitefcntlfilepointer) [capi3ref.html#sqlitefcntljournalpointer](capi3ref.md#sqlitefcntljournalpointer) [changes.html#version_3_10_1](changes.md#version_3_10_1) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md)
- SQLITE_FCNTL_LAST_ERRNO → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_FCNTL_LOCK_TIMEOUT → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntllocktimeout](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntllocktimeout) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntllocktimeout](capi3ref.md#sqlitefcntllocktimeout)
- SQLITE_FCNTL_LOCKSTATE → [34to35.html](34to35.md) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntllockstate](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntllockstate) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntllockstate](capi3ref.md#sqlitefcntllockstate)
- SQLITE_FCNTL_MMAP_SIZE → [c3ref/c_config_covering_index_scan.html#sqliteconfigmmapsize](c3ref/c_config_covering_index_scan.md#sqliteconfigmmapsize) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlmmapsize](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlmmapsize) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqliteconfigmmapsize](capi3ref.md#sqliteconfigmmapsize) [capi3ref.html#sqlitefcntlmmapsize](capi3ref.md#sqlitefcntlmmapsize) [compile.html#max_mmap_size](compile.md#max_mmap_size)
- SQLITE_FCNTL_NULL_IO → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlnullio](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlnullio) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlnullio](capi3ref.md#sqlitefcntlnullio) [changes.html#version_3_48_0](changes.md#version_3_48_0) [releaselog/3_48_0.html](releaselog/3_48_0.md)
- SQLITE_FCNTL_OVERWRITE → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntloverwrite](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntloverwrite) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntloverwrite](capi3ref.md#sqlitefcntloverwrite) [changes.html#version_3_7_9](changes.md#version_3_7_9) [releaselog/3_7_9.html](releaselog/3_7_9.md)
- SQLITE_FCNTL_PDB → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_FCNTL_PERSIST_WAL → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlpersistwal](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlpersistwal) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/snapshot_recover.html](c3ref/snapshot_recover.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_snapshot_recover](capi3ref.md#sqlite3_snapshot_recover) [capi3ref.html#sqlitefcntlpersistwal](capi3ref.md#sqlitefcntlpersistwal) [wal.html#walfile](wal.md#walfile) [walformat.html#locks](walformat.md#locks) [walformat.html#shm](walformat.md#shm)
- SQLITE_FCNTL_POWERSAFE_OVERWRITE → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlpowersafeoverwrite](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlpowersafeoverwrite) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlpowersafeoverwrite](capi3ref.md#sqlitefcntlpowersafeoverwrite) [psow.html#tornpage](psow.md#tornpage)
- SQLITE_FCNTL_PRAGMA → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlpragma](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlpragma) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlpragma](capi3ref.md#sqlitefcntlpragma) [changes.html#version_3_7_11](changes.md#version_3_7_11) [pragma.html](pragma.md) [pragma.html#pragfunc](pragma.md#pragfunc) [releaselog/3_7_11.html](releaselog/3_7_11.md)
- SQLITE_FCNTL_RBU → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlrbu](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlrbu) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlrbu](capi3ref.md#sqlitefcntlrbu)
- SQLITE_FCNTL_RESERVE_BYTES → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_FCNTL_RESET_CACHE → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlresetcache](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlresetcache) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlresetcache](capi3ref.md#sqlitefcntlresetcache) [changes.html#version_3_41_0](changes.md#version_3_41_0) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlbeginatomicwrite](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlbeginatomicwrite) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlrollbackatomicwrite](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlrollbackatomicwrite) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlbeginatomicwrite](capi3ref.md#sqlitefcntlbeginatomicwrite) [capi3ref.html#sqlitefcntlrollbackatomicwrite](capi3ref.md#sqlitefcntlrollbackatomicwrite) [rescode.html#ioerr_rollback_atomic](rescode.md#ioerr_rollback_atomic)
- SQLITE_FCNTL_SET_LOCKPROXYFILE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_FCNTL_SIZE_HINT → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlbeginatomicwrite](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlbeginatomicwrite) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlsizehint](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlsizehint) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlbeginatomicwrite](capi3ref.md#sqlitefcntlbeginatomicwrite) [capi3ref.html#sqlitefcntlsizehint](capi3ref.md#sqlitefcntlsizehint) [changes.html#version_3_7_6_1](changes.md#version_3_7_6_1) [oldnews.html](oldnews.md) [releaselog/3_7_6_1.html](releaselog/3_7_6_1.md)
- SQLITE_FCNTL_SIZE_LIMIT → [c3ref/c_config_covering_index_scan.html#sqliteconfigmemdbmaxsize](c3ref/c_config_covering_index_scan.md#sqliteconfigmemdbmaxsize) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlsizelimit](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlsizelimit) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqliteconfigmemdbmaxsize](capi3ref.md#sqliteconfigmemdbmaxsize) [capi3ref.html#sqlitefcntlsizelimit](capi3ref.md#sqlitefcntlsizelimit) [changes.html#version_3_27_0](changes.md#version_3_27_0) [compile.html#memdb_default_maxsize](compile.md#memdb_default_maxsize) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- SQLITE_FCNTL_SYNC → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlsync](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlsync) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlsync](capi3ref.md#sqlitefcntlsync)
- SQLITE_FCNTL_SYNC_OMITTED → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_7_5](changes.md#version_3_7_5) [releaselog/3_7_5.html](releaselog/3_7_5.md)
- SQLITE_FCNTL_TEMPFILENAME → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntltempfilename](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntltempfilename) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntltempfilename](capi3ref.md#sqlitefcntltempfilename)
- SQLITE_FCNTL_TRACE → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntltrace](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntltrace) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntltrace](capi3ref.md#sqlitefcntltrace) [compile.html#use_fcntl_trace](compile.md#use_fcntl_trace)
- SQLITE_FCNTL_VFS_POINTER → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlvfspointer](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlvfspointer) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/file_control.html](c3ref/file_control.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_file_control](capi3ref.md#sqlite3_file_control) [capi3ref.html#sqlitefcntlvfspointer](capi3ref.md#sqlitefcntlvfspointer)
- SQLITE_FCNTL_VFSNAME → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlvfsname](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlvfsname) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlvfsname](capi3ref.md#sqlitefcntlvfsname)
- SQLITE_FCNTL_WAL_BLOCK → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlwalblock](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlwalblock) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlwalblock](capi3ref.md#sqlitefcntlwalblock)
- SQLITE_FCNTL_WIN32_AV_RETRY → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlwin32avretry](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlwin32avretry) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlwin32avretry](capi3ref.md#sqlitefcntlwin32avretry)
- SQLITE_FCNTL_WIN32_GET_HANDLE → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlwin32gethandle](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlwin32gethandle) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlwin32gethandle](capi3ref.md#sqlitefcntlwin32gethandle) [changes.html#version_3_15_1](changes.md#version_3_15_1) [changes.html#version_3_16_0](changes.md#version_3_16_0) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md)
- SQLITE_FCNTL_WIN32_SET_HANDLE → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlwin32sethandle](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlwin32sethandle) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlwin32sethandle](capi3ref.md#sqlitefcntlwin32sethandle)
- SQLITE_FCNTL_ZIPVFS → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlzipvfs](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlzipvfs) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitefcntlzipvfs](capi3ref.md#sqlitefcntlzipvfs)
- SQLITE_FLOAT → [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob)
- SQLITE_FORMAT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#pve](rescode.md#pve)
- SQLITE_FTS3_MAX_EXPR_DEPTH → [changes.html#version_3_8_0](changes.md#version_3_8_0) [compile.html#yystackdepth](compile.md#yystackdepth) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md)
- SQLITE_FULL → [34to35.html](34to35.md) [autoinc.html](autoinc.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/get_autocommit.html](c3ref/get_autocommit.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_get_autocommit](capi3ref.md#sqlite3_get_autocommit) [changes.html#version_3_5_1](changes.md#version_3_5_1) [faq.html#q1](faq.md#q1) [fileformat2.html#seqtab](fileformat2.md#seqtab) [lang_transaction.html#immediate](lang_transaction.md#immediate) [releaselog/3_5_1.html](releaselog/3_5_1.md) [rescode.html#ioerr](rescode.md#ioerr) [rescode.html#pve](rescode.md#pve) [vfs.html#shim](vfs.md#shim)
- SQLITE_FUNCTION → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_HAVE_ISNAN → [changes.html#version_3_6_14](changes.md#version_3_6_14) [releaselog/3_6_14.html](releaselog/3_6_14.md)
- SQLITE_IGNORE → [c3ref/c_fail.html](c3ref/c_fail.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [c3ref/vtab_on_conflict.html](c3ref/vtab_on_conflict.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_FAIL](capi3ref.md#SQLITE_FAIL) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlite3_vtab_on_conflict](capi3ref.md#sqlite3_vtab_on_conflict) [lang_delete.html#truncateopt](lang_delete.md#truncateopt)
- SQLITE_INDEX_CONSTRAINT_EQ → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/index_info.html](c3ref/index_info.md) [c3ref/vtab_in.html](c3ref/vtab_in.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_index_info](capi3ref.md#sqlite3_index_info) [capi3ref.html#sqlite3_vtab_in](capi3ref.md#sqlite3_vtab_in)
- SQLITE_INDEX_CONSTRAINT_FUNCTION → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [vtab.html#xbestindex](vtab.md#xbestindex) [vtab.html#xfindfunction](vtab.md#xfindfunction)
- SQLITE_INDEX_CONSTRAINT_GE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_INDEX_CONSTRAINT_GLOB → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_INDEX_CONSTRAINT_GT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_INDEX_CONSTRAINT_IS → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_INDEX_CONSTRAINT_ISNOT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_INDEX_CONSTRAINT_ISNOTNULL → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vtab_rhs_value.html](c3ref/vtab_rhs_value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_vtab_rhs_value](capi3ref.md#sqlite3_vtab_rhs_value) [vtab.html#colUsed](vtab.md#colUsed)
- SQLITE_INDEX_CONSTRAINT_ISNULL → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vtab_rhs_value.html](c3ref/vtab_rhs_value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_vtab_rhs_value](capi3ref.md#sqlite3_vtab_rhs_value) [vtab.html#colUsed](vtab.md#colUsed)
- SQLITE_INDEX_CONSTRAINT_LE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_INDEX_CONSTRAINT_LIKE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_INDEX_CONSTRAINT_LIMIT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_38_0](changes.md#version_3_38_0) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md)
- SQLITE_INDEX_CONSTRAINT_LT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_INDEX_CONSTRAINT_MATCH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_INDEX_CONSTRAINT_NE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_INDEX_CONSTRAINT_OFFSET → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_38_0](changes.md#version_3_38_0) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md) [vtab.html#colUsed](vtab.md#colUsed)
- SQLITE_INDEX_CONSTRAINT_REGEXP → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_INDEX_SCAN_HEX → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/index_info.html](c3ref/index_info.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_index_info](capi3ref.md#sqlite3_index_info)
- SQLITE_INDEX_SCAN_UNIQUE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_INNOCUOUS → [appfunc.html](appfunc.md) [appfunc.html#sec](appfunc.md#sec) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigtrustedschema](c3ref/c_dbconfig_defensive.md#sqlitedbconfigtrustedschema) [c3ref/c_prepare_dont_log.html#sqlitepreparefromddl](c3ref/c_prepare_dont_log.md#sqlitepreparefromddl) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitedbconfigtrustedschema](capi3ref.md#sqlitedbconfigtrustedschema) [capi3ref.html#sqlitepreparefromddl](capi3ref.md#sqlitepreparefromddl) [changes.html#version_3_31_0](changes.md#version_3_31_0) [json1.html](json1.md) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- SQLITE_INSERT → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/update_hook.html](c3ref/update_hook.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite) [capi3ref.html#sqlite3_update_hook](capi3ref.md#sqlite3_update_hook) [session.html#sqlite3changeset_new](session.md#sqlite3changeset_new) [session.html#sqlite3changeset_op](session.md#sqlite3changeset_op) [session/sqlite3changeset_new.html](session/sqlite3changeset_new.md) [session/sqlite3changeset_op.html](session/sqlite3changeset_op.md)
- SQLITE_INTEGER → [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob)
- SQLITE_INTERNAL → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_46_1](changes.md#version_3_46_1) [releaselog/3_46_1.html](releaselog/3_46_1.md) [rescode.html#pve](rescode.md#pve)
- SQLITE_INTERRUPT → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/get_autocommit.html](c3ref/get_autocommit.md) [c3ref/interrupt.html](c3ref/interrupt.md) [c3ref/step.html](c3ref/step.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_get_autocommit](capi3ref.md#sqlite3_get_autocommit) [capi3ref.html#sqlite3_interrupt](capi3ref.md#sqlite3_interrupt) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [lang_transaction.html#immediate](lang_transaction.md#immediate) [rescode.html#abort](rescode.md#abort) [rescode.html#pve](rescode.md#pve)
- SQLITE_IOCAP_ATOMIC → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods) [compile.html#enable_atomic_write](compile.md#enable_atomic_write) [psow.html#tornpage](psow.md#tornpage)
- SQLITE_IOCAP_ATOMIC16K → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- SQLITE_IOCAP_ATOMIC1K → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- SQLITE_IOCAP_ATOMIC2K → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- SQLITE_IOCAP_ATOMIC32K → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- SQLITE_IOCAP_ATOMIC4K → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- SQLITE_IOCAP_ATOMIC512 → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- SQLITE_IOCAP_ATOMIC64K → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- SQLITE_IOCAP_ATOMIC8K → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- SQLITE_IOCAP_BATCH_ATOMIC → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- SQLITE_IOCAP_IMMUTABLE → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [c3ref/open.html#coreuriqueryparameters](c3ref/open.md#coreuriqueryparameters) [capi3ref.html](capi3ref.md) [capi3ref.html#coreuriqueryparameters](capi3ref.md#coreuriqueryparameters) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods) [changes.html#version_3_8_5](changes.md#version_3_8_5) [releaselog/3_8_5.html](releaselog/3_8_5.md) [uri.html#uriimmutable](uri.md#uriimmutable)
- SQLITE_IOCAP_POWERSAFE_OVERWRITE → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlpowersafeoverwrite](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlpowersafeoverwrite) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods) [capi3ref.html#sqlitefcntlpowersafeoverwrite](capi3ref.md#sqlitefcntlpowersafeoverwrite) [changes.html#version_3_7_10](changes.md#version_3_7_10) [psow.html#tornpage](psow.md#tornpage) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- SQLITE_IOCAP_SAFE_APPEND → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- SQLITE_IOCAP_SEQUENTIAL → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- SQLITE_IOCAP_SUBPAGE_READ → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods) [changes.html#version_3_47_1](changes.md#version_3_47_1) [changes.html#version_3_48_0](changes.md#version_3_48_0) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md) [releaselog/3_48_0.html](releaselog/3_48_0.md)
- SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- SQLITE_IOERR → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/get_autocommit.html](c3ref/get_autocommit.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_get_autocommit](capi3ref.md#sqlite3_get_autocommit) [changes.html#version_3_5_1](changes.md#version_3_5_1) [lang_transaction.html#immediate](lang_transaction.md#immediate) [releaselog/3_5_1.html](releaselog/3_5_1.md) [rescode.html#ioerr_access](rescode.md#ioerr_access) [rescode.html#ioerr_checkreservedlock](rescode.md#ioerr_checkreservedlock) [rescode.html#ioerr_close](rescode.md#ioerr_close) [rescode.html#ioerr_convpath](rescode.md#ioerr_convpath) [rescode.html#ioerr_corruptfs](rescode.md#ioerr_corruptfs) [rescode.html#ioerr_data](rescode.md#ioerr_data) [rescode.html#ioerr_delete](rescode.md#ioerr_delete) [rescode.html#ioerr_delete_noent](rescode.md#ioerr_delete_noent) [rescode.html#ioerr_dir_fsync](rescode.md#ioerr_dir_fsync) [rescode.html#ioerr_fstat](rescode.md#ioerr_fstat) [rescode.html#ioerr_fsync](rescode.md#ioerr_fsync) [rescode.html#ioerr_gettemppath](rescode.md#ioerr_gettemppath) [rescode.html#ioerr_lock](rescode.md#ioerr_lock) [rescode.html#ioerr_mmap](rescode.md#ioerr_mmap) [rescode.html#ioerr_rdlock](rescode.md#ioerr_rdlock) [rescode.html#ioerr_read](rescode.md#ioerr_read) [rescode.html#ioerr_seek](rescode.md#ioerr_seek) [rescode.html#ioerr_shmmap](rescode.md#ioerr_shmmap) [rescode.html#ioerr_shmopen](rescode.md#ioerr_shmopen) [rescode.html#ioerr_shmsize](rescode.md#ioerr_shmsize) [rescode.html#ioerr_short_read](rescode.md#ioerr_short_read) [rescode.html#ioerr_truncate](rescode.md#ioerr_truncate) [rescode.html#ioerr_unlock](rescode.md#ioerr_unlock) [rescode.html#ioerr_write](rescode.md#ioerr_write) [rescode.html#pve](rescode.md#pve)
- SQLITE_IOERR_ACCESS → [35to36.html](35to36.md) [c3ref/backup_finish.html#sqlite3backupstep](c3ref/backup_finish.md#sqlite3backupstep) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3backupstep](capi3ref.md#sqlite3backupstep) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_AUTH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_BADKEY → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_IOERR_BEGIN_ATOMIC → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_BLOCKED → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_CHECKRESERVEDLOCK → [35to36.html](35to36.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_CLOSE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_CODEC → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_IOERR_COMMIT_ATOMIC → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_CONVPATH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#cantopen_convpath](rescode.md#cantopen_convpath) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_CORRUPTFS → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_DATA → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_DELETE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_DELETE_NOENT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_DIR_CLOSE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_DIR_FSYNC → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_FSTAT → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_FSYNC → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_GETTEMPPATH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_IN_PAGE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_IOERR_LOCK → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_MMAP → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_NOMEM → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_RDLOCK → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_READ → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_ROLLBACK_ATOMIC → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_SEEK → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_SHMLOCK → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_SHMMAP → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_SHMOPEN → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_SHMSIZE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_SHORT_READ → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_TRUNCATE → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_UNLOCK → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_VNODE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_IOERR_WRITE → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_JSON_MAX_DEPTH → [compile.html#yystackdepth](compile.md#yystackdepth)
- SQLITE_LIKE_DOESNT_MATCH_BLOBS → [changes.html#version_3_10_0](changes.md#version_3_10_0) [compile.html#rcmd](compile.md#rcmd) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md)
- SQLITE_LIMIT_ATTACHED → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [lang_attach.html](lang_attach.md) [limits.html#max_attached](limits.md#max_attached)
- SQLITE_LIMIT_COLUMN → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [lang_createindex.html](lang_createindex.md) [limits.html#max_column](limits.md#max_column)
- SQLITE_LIMIT_COMPOUND_SELECT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_46_1](changes.md#version_3_46_1) [changes.html#version_3_8_8](changes.md#version_3_8_8) [lang_select.html#values](lang_select.md#values) [limits.html#max_compound_select](limits.md#max_compound_select) [releaselog/3_46_1.html](releaselog/3_46_1.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- SQLITE_LIMIT_EXPR_DEPTH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [limits.html#max_expr_depth](limits.md#max_expr_depth)
- SQLITE_LIMIT_FUNCTION_ARG → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/create_function.html](c3ref/create_function.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [limits.html#max_function_arg](limits.md#max_function_arg)
- SQLITE_LIMIT_LENGTH → [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/expanded_sql.html](c3ref/expanded_sql.md) [c3ref/str_new.html](c3ref/str_new.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_expanded_sql](capi3ref.md#sqlite3_expanded_sql) [capi3ref.html#sqlite3_str_new](capi3ref.md#sqlite3_str_new) [changes.html#version_3_48_0](changes.md#version_3_48_0) [compile.html#printf_precision_limit](compile.md#printf_precision_limit) [limits.html](limits.md) [limits.html#max_length](limits.md#max_length) [releaselog/3_48_0.html](releaselog/3_48_0.md) [rescode.html#toobig](rescode.md#toobig)
- SQLITE_LIMIT_LIKE_PATTERN_LENGTH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [limits.html#max_like_pattern_length](limits.md#max_like_pattern_length)
- SQLITE_LIMIT_PARSER_DEPTH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- SQLITE_LIMIT_SQL_LENGTH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_39_1](changes.md#version_3_39_1) [limits.html#max_sql_length](limits.md#max_sql_length) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md) [rescode.html#toobig](rescode.md#toobig)
- SQLITE_LIMIT_TRIGGER_DEPTH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [foreignkeys.html#fk_actions](foreignkeys.md#fk_actions) [pragma.html#pragma_recursive_triggers](pragma.md#pragma_recursive_triggers)
- SQLITE_LIMIT_VARIABLE_NUMBER → [c3ref/bind_blob.html](c3ref/bind_blob.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_bind_blob](capi3ref.md#sqlite3_bind_blob) [lang_expr.html#varparam](lang_expr.md#varparam) [limits.html#max_variable_number](limits.md#max_variable_number)
- SQLITE_LIMIT_VDBE_OP → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_18_0](changes.md#version_3_18_0) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md)
- SQLITE_LIMIT_WORKER_THREADS → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_8_7](changes.md#version_3_8_7) [compile.html#max_worker_threads](compile.md#max_worker_threads) [pragma.html#pragma_threads](pragma.md#pragma_threads) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- SQLITE_LOCK_EXCLUSIVE → [34to35.html](34to35.md) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntllockstate](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntllockstate) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods) [capi3ref.html#sqlitefcntllockstate](capi3ref.md#sqlitefcntllockstate)
- SQLITE_LOCK_NONE → [34to35.html](34to35.md) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntllockstate](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntllockstate) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods) [capi3ref.html#sqlitefcntllockstate](capi3ref.md#sqlitefcntllockstate)
- SQLITE_LOCK_PENDING → [34to35.html](34to35.md) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntllockstate](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntllockstate) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods) [capi3ref.html#sqlitefcntllockstate](capi3ref.md#sqlitefcntllockstate)
- SQLITE_LOCK_RESERVED → [34to35.html](34to35.md) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntllockstate](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntllockstate) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods) [capi3ref.html#sqlitefcntllockstate](capi3ref.md#sqlitefcntllockstate)
- SQLITE_LOCK_SHARED → [34to35.html](34to35.md) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntllockstate](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntllockstate) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods) [capi3ref.html#sqlitefcntllockstate](capi3ref.md#sqlitefcntllockstate)
- SQLITE_LOCKED → [c3ref/backup_finish.html#sqlite3backupfinish](c3ref/backup_finish.md#sqlite3backupfinish) [c3ref/backup_finish.html#sqlite3backupstep](c3ref/backup_finish.md#sqlite3backupstep) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/unlock_notify.html](c3ref/unlock_notify.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_unlock_notify](capi3ref.md#sqlite3_unlock_notify) [capi3ref.html#sqlite3backupfinish](capi3ref.md#sqlite3backupfinish) [capi3ref.html#sqlite3backupstep](capi3ref.md#sqlite3backupstep) [compile.html#omit_autoreset](compile.md#omit_autoreset) [rescode.html#busy](rescode.md#busy) [rescode.html#pve](rescode.md#pve) [rtree.html#readwrite](rtree.md#readwrite)
- SQLITE_LOCKED_SHAREDCACHE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_LOCKED_VTAB → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- sqlite_master table → [changes.html#version_3_30_0](changes.md#version_3_30_0) [changes.html#version_3_8_11](changes.md#version_3_8_11) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- SQLITE_MAX_ALLOCATION_SIZE → [changes.html#version_3_40_0](changes.md#version_3_40_0) [compile.html#max_memory](compile.md#max_memory) [compile.html#yystackdepth](compile.md#yystackdepth) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md) [security.html](security.md)
- SQLITE_MAX_ATTACHED → [changes.html#version_3_7_6](changes.md#version_3_7_6) [changes.html#version_3_8_6](changes.md#version_3_8_6) [compile.html#yystackdepth](compile.md#yystackdepth) [releaselog/3_7_6.html](releaselog/3_7_6.md) [releaselog/3_8_6.html](releaselog/3_8_6.md)
- SQLITE_MAX_COLUMN → [compile.html#yystackdepth](compile.md#yystackdepth) [lang_createtable.html#tablecoldef](lang_createtable.md#tablecoldef)
- SQLITE_MAX_COMPOUND_SELECT → [compile.html#yystackdepth](compile.md#yystackdepth)
- SQLITE_MAX_EXPR_DEPTH → [compile.html#rcmd](compile.md#rcmd) [compile.html#yystackdepth](compile.md#yystackdepth)
- SQLITE_MAX_FUNCTION_ARG → [appfunc.html](appfunc.md) [changes.html#version_3_48_0](changes.md#version_3_48_0) [compile.html#yystackdepth](compile.md#yystackdepth) [releaselog/3_48_0.html](releaselog/3_48_0.md)
- SQLITE_MAX_LENGTH → [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/str_errcode.html](c3ref/str_errcode.md) [c3ref/str_new.html](c3ref/str_new.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_str_errcode](capi3ref.md#sqlite3_str_errcode) [capi3ref.html#sqlite3_str_new](capi3ref.md#sqlite3_str_new) [compile.html#yystackdepth](compile.md#yystackdepth) [datatype3.html#affname](datatype3.md#affname) [fts5.html#\_summary_of_technical_differences\_](fts5.md#_summary_of_technical_differences_) [lang_createtable.html#tablecoldef](lang_createtable.md#tablecoldef) [rescode.html#toobig](rescode.md#toobig)
- SQLITE_MAX_LIKE_PATTERN_LENGTH → [compile.html#yystackdepth](compile.md#yystackdepth)
- SQLITE_MAX_MEMORY → [changes.html#version_3_18_0](changes.md#version_3_18_0) [compile.html#default_memstatus](compile.md#default_memstatus) [compile.html#max_allocation_size](compile.md#max_allocation_size) [compile.html#yystackdepth](compile.md#yystackdepth) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md)
- SQLITE_MAX_MMAP_SIZE → [c3ref/c_config_covering_index_scan.html#sqliteconfigmmapsize](c3ref/c_config_covering_index_scan.md#sqliteconfigmmapsize) [capi3ref.html#sqliteconfigmmapsize](capi3ref.md#sqliteconfigmmapsize) [compile.html#default_mmap_size](compile.md#default_mmap_size) [compile.html#yystackdepth](compile.md#yystackdepth) [mmap.html](mmap.md) [pragma.html#pragma_mmap_size](pragma.md#pragma_mmap_size)
- SQLITE_MAX_PAGE_COUNT → [changes.html#version_3_45_0](changes.md#version_3_45_0) [compile.html#yystackdepth](compile.md#yystackdepth) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- SQLITE_MAX_SCHEMA_RETRY → [c3ref/prepare.html](c3ref/prepare.md) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [changes.html#version_3_7_17](changes.md#version_3_7_17) [releaselog/3_7_17.html](releaselog/3_7_17.md) [rescode.html#schema](rescode.md#schema)
- SQLITE_MAX_SQL_LENGTH → [compile.html#yystackdepth](compile.md#yystackdepth) [rescode.html#toobig](rescode.md#toobig)
- SQLITE_MAX_TRIGGER_DEPTH → [foreignkeys.html#fk_actions](foreignkeys.md#fk_actions) [pragma.html#pragma_recursive_triggers](pragma.md#pragma_recursive_triggers)
- SQLITE_MAX_VARIABLE_NUMBER → [changes.html#version_3_32_0](changes.md#version_3_32_0) [compile.html#yystackdepth](compile.md#yystackdepth) [lang_expr.html#varparam](lang_expr.md#varparam) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- SQLITE_MAX_WORKER_THREADS → [compile.html#default_worker_threads](compile.md#default_worker_threads)
- SQLITE_MEMDB_DEFAULT_MAXSIZE → [c3ref/c_config_covering_index_scan.html#sqliteconfigmemdbmaxsize](c3ref/c_config_covering_index_scan.md#sqliteconfigmemdbmaxsize) [capi3ref.html#sqliteconfigmemdbmaxsize](capi3ref.md#sqliteconfigmemdbmaxsize) [changes.html#version_3_27_0](changes.md#version_3_27_0) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- SQLITE_MEMDEBUG → [malloc.html](malloc.md) [malloc.html#memdebug](malloc.md#memdebug) [testing.html#memtesting](testing.md#memtesting) [th3.html](th3.md)
- sqlite_memstat → [vtablist.html](vtablist.md)
- SQLITE_MINIMUM_FILE_DESCRIPTOR → [changes.html#version_3_8_1](changes.md#version_3_8_1) [howtocorrupt.html#stalefd](howtocorrupt.md#stalefd) [releaselog/3_8_1.html](releaselog/3_8_1.md)
- SQLITE_MISMATCH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#pve](rescode.md#pve)
- SQLITE_MISUSE → [appfunc.html](appfunc.md) [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/create_function.html](c3ref/create_function.md) [c3ref/step.html](c3ref/step.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [changes.html#version_3_5_3](changes.md#version_3_5_3) [changes.html#version_3_6_15](changes.md#version_3_6_15) [compile.html#omit_autoreset](compile.md#omit_autoreset) [releaselog/3_5_3.html](releaselog/3_5_3.md) [releaselog/3_6_15.html](releaselog/3_6_15.md) [rescode.html#pve](rescode.md#pve) [session.html#sqlite3changeset_conflict](session.md#sqlite3changeset_conflict) [session.html#sqlite3changeset_finalize](session.md#sqlite3changeset_finalize) [session.html#sqlite3changeset_new](session.md#sqlite3changeset_new) [session.html#sqlite3changeset_old](session.md#sqlite3changeset_old) [session.html#sqlite3changeset_op](session.md#sqlite3changeset_op) [session/sqlite3changeset_conflict.html](session/sqlite3changeset_conflict.md) [session/sqlite3changeset_finalize.html](session/sqlite3changeset_finalize.md) [session/sqlite3changeset_new.html](session/sqlite3changeset_new.md) [session/sqlite3changeset_old.html](session/sqlite3changeset_old.md) [session/sqlite3changeset_op.html](session/sqlite3changeset_op.md)
- SQLITE_MUTEX_FAST → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_MUTEX_RECURSIVE → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_MUTEX_STATIC_APP1 → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_MUTEX_STATIC_APP2 → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_MUTEX_STATIC_APP3 → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_MUTEX_STATIC_LRU → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_MUTEX_STATIC_LRU2 → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_MUTEX_STATIC_MAIN → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/mem_methods.html](c3ref/mem_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_mem_methods](capi3ref.md#sqlite3_mem_methods)
- SQLITE_MUTEX_STATIC_MEM → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/mem_methods.html](c3ref/mem_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_mem_methods](capi3ref.md#sqlite3_mem_methods)
- SQLITE_MUTEX_STATIC_MEM2 → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_MUTEX_STATIC_OPEN → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_MUTEX_STATIC_PMEM → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_MUTEX_STATIC_PRNG → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_MUTEX_STATIC_VFS1 → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_8_11](changes.md#version_3_8_11) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- SQLITE_MUTEX_STATIC_VFS2 → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_MUTEX_STATIC_VFS3 → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_NOLFS → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#pve](rescode.md#pve)
- SQLITE_NOMEM → [c3ref/backup_finish.html#sqlite3backupstep](c3ref/backup_finish.md#sqlite3backupstep) [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/get_autocommit.html](c3ref/get_autocommit.md) [c3ref/hard_heap_limit64.html](c3ref/hard_heap_limit64.md) [c3ref/str_errcode.html](c3ref/str_errcode.md) [c3ref/win32_set_directory.html](c3ref/win32_set_directory.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_get_autocommit](capi3ref.md#sqlite3_get_autocommit) [capi3ref.html#sqlite3_hard_heap_limit64](capi3ref.md#sqlite3_hard_heap_limit64) [capi3ref.html#sqlite3_str_errcode](capi3ref.md#sqlite3_str_errcode) [capi3ref.html#sqlite3_win32_set_directory](capi3ref.md#sqlite3_win32_set_directory) [capi3ref.html#sqlite3backupstep](capi3ref.md#sqlite3backupstep) [lang_transaction.html#immediate](lang_transaction.md#immediate) [malloc.html](malloc.md) [malloc.html#nofrag](malloc.md#nofrag) [rescode.html#ioerr_nomem](rescode.md#ioerr_nomem) [rescode.html#pve](rescode.md#pve) [session.html#sqlite3changeset_finalize](session.md#sqlite3changeset_finalize) [session/sqlite3changeset_finalize.html](session/sqlite3changeset_finalize.md) [vtab.html#obc](vtab.md#obc)
- SQLITE_NOTADB → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#pve](rescode.md#pve)
- SQLITE_NOTFOUND → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlpragma](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlpragma) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [c3ref/vtab_rhs_value.html](c3ref/vtab_rhs_value.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods) [capi3ref.html#sqlite3_vtab_rhs_value](capi3ref.md#sqlite3_vtab_rhs_value) [capi3ref.html#sqlitefcntlpragma](capi3ref.md#sqlitefcntlpragma) [changes.html#version_3_7_5](changes.md#version_3_7_5) [releaselog/3_7_5.html](releaselog/3_7_5.md) [rescode.html#pve](rescode.md#pve) [vtab.html#colUsed](vtab.md#colUsed)
- SQLITE_NOTICE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#pve](rescode.md#pve)
- SQLITE_NOTICE_RBU → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_NOTICE_RECOVER_ROLLBACK → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_NOTICE_RECOVER_WAL → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_NULL → [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob)
- sqlite_offset → [changes.html#version_3_22_0](changes.md#version_3_22_0) [compile.html#enable_offset_sql_func](compile.md#enable_offset_sql_func) [lang_corefunc.html](lang_corefunc.md) [releaselog/3_22_0.html](releaselog/3_22_0.md)
- sqlite_offset SQL function → [changes.html#version_3_38_1](changes.md#version_3_38_1) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md)
- SQLITE_OK → [34to35.html](34to35.md) [c3ref/backup_finish.html#sqlite3backupfinish](c3ref/backup_finish.md#sqlite3backupfinish) [c3ref/backup_finish.html#sqlite3backupstep](c3ref/backup_finish.md#sqlite3backupstep) [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/c_deny.html](c3ref/c_deny.md) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlcommitatomicwrite](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlcommitatomicwrite) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlpragma](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlpragma) [c3ref/close.html](c3ref/close.md) [c3ref/config.html](c3ref/config.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/enable_shared_cache.html](c3ref/enable_shared_cache.md) [c3ref/initialize.html](c3ref/initialize.md) [c3ref/intro.html](c3ref/intro.md) [c3ref/load_extension.html](c3ref/load_extension.md) [c3ref/mutex_alloc.html](c3ref/mutex_alloc.md) [c3ref/open.html](c3ref/open.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/reset.html](c3ref/reset.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [c3ref/str_errcode.html](c3ref/str_errcode.md) [c3ref/vfs.html#sqlite3vfsxaccess](c3ref/vfs.md#sqlite3vfsxaccess) [c3ref/wal_hook.html](c3ref/wal_hook.md) [c3ref/win32_set_directory.html](c3ref/win32_set_directory.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_DENY](capi3ref.md#SQLITE_DENY) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_close](capi3ref.md#sqlite3_close) [capi3ref.html#sqlite3_config](capi3ref.md#sqlite3_config) [capi3ref.html#sqlite3_enable_shared_cache](capi3ref.md#sqlite3_enable_shared_cache) [capi3ref.html#sqlite3_initialize](capi3ref.md#sqlite3_initialize) [capi3ref.html#sqlite3_load_extension](capi3ref.md#sqlite3_load_extension) [capi3ref.html#sqlite3_mutex_alloc](capi3ref.md#sqlite3_mutex_alloc) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_reset](capi3ref.md#sqlite3_reset) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlite3_str_errcode](capi3ref.md#sqlite3_str_errcode) [capi3ref.html#sqlite3_wal_hook](capi3ref.md#sqlite3_wal_hook) [capi3ref.html#sqlite3_win32_set_directory](capi3ref.md#sqlite3_win32_set_directory) [capi3ref.html#sqlite3backupfinish](capi3ref.md#sqlite3backupfinish) [capi3ref.html#sqlite3backupstep](capi3ref.md#sqlite3backupstep) [capi3ref.html#sqlite3vfsxaccess](capi3ref.md#sqlite3vfsxaccess) [capi3ref.html#sqlitefcntlcommitatomicwrite](capi3ref.md#sqlitefcntlcommitatomicwrite) [capi3ref.html#sqlitefcntlpragma](capi3ref.md#sqlitefcntlpragma) [pragma.html#pragma_wal_checkpoint](pragma.md#pragma_wal_checkpoint) [rescode.html](rescode.md) [rescode.html#pve](rescode.md#pve) [vtab.html#xcolumn](vtab.md#xcolumn) [vtab.html#xconnect](vtab.md#xconnect) [vtab.html#xcreate](vtab.md#xcreate) [vtab.html#xfilter](vtab.md#xfilter) [vtab.html#xnext](vtab.md#xnext) [vtab.html#xopen](vtab.md#xopen) [vtab.html#xrename](vtab.md#xrename) [vtab.html#xrowid](vtab.md#xrowid) [vtab.html#xupdate](vtab.md#xupdate)
- SQLITE_OK_LOAD_PERMANENTLY → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_14](changes.md#version_3_14) [loadext.html#persist](loadext.md#persist) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_OK_SYMLINK → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_OMIT_ALTERTABLE → [howtocompile.html#amal](howtocompile.md#amal)
- SQLITE_OMIT_ANALYZE → [howtocompile.html#amal](howtocompile.md#amal)
- SQLITE_OMIT_ATTACH → [howtocompile.html#amal](howtocompile.md#amal)
- SQLITE_OMIT_AUTOINCREMENT → [howtocompile.html#amal](howtocompile.md#amal)
- SQLITE_OMIT_AUTOINIT → [c3ref/initialize.html](c3ref/initialize.md) [capi3ref.html#sqlite3_initialize](capi3ref.md#sqlite3_initialize) [changes.html#version_3_7_14](changes.md#version_3_7_14) [compile.html#rcmd](compile.md#rcmd) [releaselog/3_7_14.html](releaselog/3_7_14.md)
- SQLITE_OMIT_AUTOMATIC_INDEX → [compile.html#default_automatic_index](compile.md#default_automatic_index) [optoverview.html#autoindex](optoverview.md#autoindex)
- SQLITE_OMIT_AUTORESET → [c3ref/step.html](c3ref/step.md) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [changes.html#version_3_7_5](changes.md#version_3_7_5) [changes.html#version_3_8_9](changes.md#version_3_8_9) [releaselog/3_7_5.html](releaselog/3_7_5.md) [releaselog/3_8_9.html](releaselog/3_8_9.md)
- SQLITE_OMIT_BUILTIN_TEST → [changes.html#version_3_16_0](changes.md#version_3_16_0) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md)
- SQLITE_OMIT_CAST → [howtocompile.html#amal](howtocompile.md#amal)
- SQLITE_OMIT_COMPILEOPTION_DIAGS → [c3ref/compileoption_get.html](c3ref/compileoption_get.md) [capi3ref.html#sqlite3_compileoption_get](capi3ref.md#sqlite3_compileoption_get)
- SQLITE_OMIT_COMPOUND_SELECT → [howtocompile.html#amal](howtocompile.md#amal)
- SQLITE_OMIT_DATETIME_FUNCS → [compile.html#gmtime_r](compile.md#gmtime_r)
- SQLITE_OMIT_DECLTYPE → [compile.html#rcmd](compile.md#rcmd)
- SQLITE_OMIT_DEPRECATED → [changes.html#version_3_11_0](changes.md#version_3_11_0) [compile.html#rcmd](compile.md#rcmd) [pragma.html#pragma_case_sensitive_like](pragma.md#pragma_case_sensitive_like) [pragma.html#pragma_count_changes](pragma.md#pragma_count_changes) [pragma.html#pragma_data_store_directory](pragma.md#pragma_data_store_directory) [pragma.html#pragma_default_cache_size](pragma.md#pragma_default_cache_size) [pragma.html#pragma_empty_result_callbacks](pragma.md#pragma_empty_result_callbacks) [pragma.html#pragma_full_column_names](pragma.md#pragma_full_column_names) [pragma.html#pragma_short_column_names](pragma.md#pragma_short_column_names) [pragma.html#pragma_temp_store_directory](pragma.md#pragma_temp_store_directory) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md)
- SQLITE_OMIT_DESERIALIZE → [c3ref/deserialize.html](c3ref/deserialize.md) [c3ref/serialize.html](c3ref/serialize.md) [capi3ref.html#sqlite3_deserialize](capi3ref.md#sqlite3_deserialize) [capi3ref.html#sqlite3_serialize](capi3ref.md#sqlite3_serialize) [compile.html#enable_deserialize](compile.md#enable_deserialize)
- SQLITE_OMIT_EXPLAIN → [howtocompile.html#amal](howtocompile.md#amal)
- SQLITE_OMIT_FLOATING_POINT → [changes.html#version_3_3_3](changes.md#version_3_3_3) [changes.html#version_3_6_23](changes.md#version_3_6_23) [changes.html#version_3_7_14](changes.md#version_3_7_14) [oldnews.html](oldnews.md) [releaselog/3_3_0.html](releaselog/3_3_0.md) [releaselog/3_6_23.html](releaselog/3_6_23.md) [releaselog/3_7_14.html](releaselog/3_7_14.md)
- SQLITE_OMIT_FOREIGN_KEY → [foreignkeys.html#fk_enable](foreignkeys.md#fk_enable) [howtocompile.html#amal](howtocompile.md#amal)
- SQLITE_OMIT_INTROSPECTION_PRAGMAS → [compile.html#introspection_pragmas](compile.md#introspection_pragmas)
- SQLITE_OMIT_LOAD_EXTENSION → [34to35.html](34to35.md) [howtocompile.html#cli](howtocompile.md#cli) [loadext.html#statext](loadext.md#statext)
- SQLITE_OMIT_PRAGMA → [howtocompile.html#amal](howtocompile.md#amal)
- SQLITE_OMIT_PROGRESS_CALLBACK → [compile.html#rcmd](compile.md#rcmd)
- SQLITE_OMIT_REINDEX → [howtocompile.html#amal](howtocompile.md#amal)
- SQLITE_OMIT_SEH → [changes.html#version_3_44_0](changes.md#version_3_44_0) [compile.html#use_seh](compile.md#use_seh) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md)
- SQLITE_OMIT_SHARED_CACHE → [compile.html#rcmd](compile.md#rcmd)
- SQLITE_OMIT_SUBQUERY → [howtocompile.html#amal](howtocompile.md#amal)
- SQLITE_OMIT_TEMPDB → [howtocompile.html#amal](howtocompile.md#amal)
- SQLITE_OMIT_TRACE → [c3ref/expanded_sql.html](c3ref/expanded_sql.md) [capi3ref.html#sqlite3_expanded_sql](capi3ref.md#sqlite3_expanded_sql)
- SQLITE_OMIT_TRIGGER → [foreignkeys.html#fk_enable](foreignkeys.md#fk_enable) [howtocompile.html#amal](howtocompile.md#amal)
- SQLITE_OMIT_TRUNCATE_OPTIMIZATION → [changes.html#version_3_6_4](changes.md#version_3_6_4) [changes.html#version_3_6_5](changes.md#version_3_6_5) [lang_delete.html#truncateopt](lang_delete.md#truncateopt) [releaselog/3_6_4.html](releaselog/3_6_4.md) [releaselog/3_6_5.html](releaselog/3_6_5.md)
- SQLITE_OMIT_VACUUM → [howtocompile.html#amal](howtocompile.md#amal)
- SQLITE_OMIT_VIEW → [howtocompile.html#amal](howtocompile.md#amal)
- SQLITE_OMIT_VIRTUALTABLE → [fts3.html#compiling_and_enabling_fts3_and_fts4](fts3.md#compiling_and_enabling_fts3_and_fts4) [howtocompile.html#amal](howtocompile.md#amal)
- SQLITE_OMIT_WINDOWFUNC → [changes.html#version_3_39_1](changes.md#version_3_39_1) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md)
- SQLITE_OPEN_AUTOPROXY → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_OPEN_CREATE → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/open.html](c3ref/open.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen)
- SQLITE_OPEN_DELETEONCLOSE → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen)
- SQLITE_OPEN_EXCLUSIVE → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen)
- SQLITE_OPEN_EXRESCODE → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/open.html#openexrescode](c3ref/open.md#openexrescode) [capi3ref.html](capi3ref.md) [capi3ref.html#openexrescode](capi3ref.md#openexrescode) [changes.html#version_3_37_0](changes.md#version_3_37_0) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md)
- SQLITE_OPEN_FULLMUTEX → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/open.html](c3ref/open.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [compile.html#threadsafe](compile.md#threadsafe) [threadsafe.html](threadsafe.md)
- SQLITE_OPEN_MAIN_DB → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen)
- SQLITE_OPEN_MAIN_JOURNAL → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/database_file_object.html](c3ref/database_file_object.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_database_file_object](capi3ref.md#sqlite3_database_file_object) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen)
- SQLITE_OPEN_MEMORY → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/open.html](c3ref/open.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open)
- SQLITE_OPEN_NOFOLLOW → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/open.html#opennofollow](c3ref/open.md#opennofollow) [capi3ref.html](capi3ref.md) [capi3ref.html#opennofollow](capi3ref.md#opennofollow) [changes.html#version_3_39_0](changes.md#version_3_39_0) [releaselog/3_39_0.html](releaselog/3_39_0.md) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md) [rescode.html#cantopen_symlink](rescode.md#cantopen_symlink)
- SQLITE_OPEN_NOMUTEX → [35to36.html](35to36.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/open.html](c3ref/open.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [changes.html#version_3_6_1](changes.md#version_3_6_1) [compile.html#threadsafe](compile.md#threadsafe) [releaselog/3_6_0.html](releaselog/3_6_0.md) [threadsafe.html](threadsafe.md)
- SQLITE_OPEN_PRIVATECACHE → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/open.html](c3ref/open.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [changes.html#version_3_6_18](changes.md#version_3_6_18) [releaselog/3_6_18.html](releaselog/3_6_18.md) [sharedcache.html#dontuse](sharedcache.md#dontuse)
- SQLITE_OPEN_READONLY → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/intro.html](c3ref/intro.md) [c3ref/open.html](c3ref/open.md) [c3ref/open.html#coreuriqueryparameters](c3ref/open.md#coreuriqueryparameters) [c3ref/open.html#opennofollow](c3ref/open.md#opennofollow) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#coreuriqueryparameters](capi3ref.md#coreuriqueryparameters) [capi3ref.html#opennofollow](capi3ref.md#opennofollow) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen)
- SQLITE_OPEN_READWRITE → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/open.html](c3ref/open.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen)
- SQLITE_OPEN_SHAREDCACHE → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/enable_shared_cache.html](c3ref/enable_shared_cache.md) [c3ref/open.html](c3ref/open.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_enable_shared_cache](capi3ref.md#sqlite3_enable_shared_cache) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [changes.html#version_3_6_18](changes.md#version_3_6_18) [releaselog/3_6_18.html](releaselog/3_6_18.md) [sharedcache.html#dontuse](sharedcache.md#dontuse)
- SQLITE_OPEN_SUBJOURNAL → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen)
- SQLITE_OPEN_SUPER_JOURNAL → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen)
- SQLITE_OPEN_TEMP_DB → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen)
- SQLITE_OPEN_TEMP_JOURNAL → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen)
- SQLITE_OPEN_TRANSIENT_DB → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen)
- SQLITE_OPEN_URI → [c3ref/c_config_covering_index_scan.html#sqliteconfiguri](c3ref/c_config_covering_index_scan.md#sqliteconfiguri) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/open.html](c3ref/open.md) [c3ref/open.html#urifilenamesinsqlite3open](c3ref/open.md#urifilenamesinsqlite3open) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [capi3ref.html#sqliteconfiguri](capi3ref.md#sqliteconfiguri) [capi3ref.html#urifilenamesinsqlite3open](capi3ref.md#urifilenamesinsqlite3open) [lang_vacuum.html#vacuuminto](lang_vacuum.md#vacuuminto) [uri.html](uri.md)
- SQLITE_OPEN_WAL → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/database_file_object.html](c3ref/database_file_object.md) [c3ref/vfs.html#sqlite3vfsxopen](c3ref/vfs.md#sqlite3vfsxopen) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_database_file_object](capi3ref.md#sqlite3_database_file_object) [capi3ref.html#sqlite3vfsxopen](capi3ref.md#sqlite3vfsxopen)
- SQLITE_OS_OTHER → [c3ref/initialize.html](c3ref/initialize.md) [capi3ref.html#sqlite3_initialize](capi3ref.md#sqlite3_initialize)
- SQLITE_PERM → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#pve](rescode.md#pve)
- SQLITE_POWERSAFE_OVERWRITE → [changes.html#version_3_7_10](changes.md#version_3_7_10) [psow.html#tornpage](psow.md#tornpage) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- SQLITE_PRAGMA → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_PREPARE_DONT_LOG → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_48_0](changes.md#version_3_48_0) [releaselog/3_48_0.html](releaselog/3_48_0.md)
- SQLITE_PREPARE_FROM_DDL → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/prepare.html](c3ref/prepare.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [security.html#baddb](security.md#baddb) [vtab.html#customvtab](vtab.md#customvtab)
- SQLITE_PREPARE_NO_VTAB → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_27_0](changes.md#version_3_27_0) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- SQLITE_PREPARE_NORMALIZE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_27_0](changes.md#version_3_27_0) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md)
- SQLITE_PREPARE_PERSISTENT → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/prepare.html](c3ref/prepare.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- SQLITE_PRINTF_PRECISION_LIMIT → [compile.html#yystackdepth](compile.md#yystackdepth)
- SQLITE_PROTOCOL → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_33_0](changes.md#version_3_33_0) [changes.html#version_3_8_6](changes.md#version_3_8_6) [releaselog/3_33_0.html](releaselog/3_33_0.md) [releaselog/3_8_6.html](releaselog/3_8_6.md) [rescode.html#pve](rescode.md#pve)
- SQLITE_QUERY_PLANNER_LIMIT → [compile.html#query_planner_limit_incr](compile.md#query_planner_limit_incr)
- SQLITE_QUERY_PLANNER_LIMIT_INCR → [compile.html#query_planner_limit](compile.md#query_planner_limit)
- SQLITE_RANGE → [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [rescode.html#pve](rescode.md#pve) [session.html#sqlite3changeset_conflict](session.md#sqlite3changeset_conflict) [session.html#sqlite3changeset_new](session.md#sqlite3changeset_new) [session.html#sqlite3changeset_old](session.md#sqlite3changeset_old) [session/sqlite3changeset_conflict.html](session/sqlite3changeset_conflict.md) [session/sqlite3changeset_new.html](session/sqlite3changeset_new.md) [session/sqlite3changeset_old.html](session/sqlite3changeset_old.md)
- SQLITE_READ → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [changes.html#version_3_19_0](changes.md#version_3_19_0) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md)
- SQLITE_READONLY → [c3ref/backup_finish.html#sqlite3backupstep](c3ref/backup_finish.md#sqlite3backupstep) [c3ref/blob_write.html](c3ref/blob_write.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_blob_write](capi3ref.md#sqlite3_blob_write) [capi3ref.html#sqlite3backupstep](capi3ref.md#sqlite3backupstep) [pragma.html#pragma_query_only](pragma.md#pragma_query_only) [rescode.html#pve](rescode.md#pve) [rescode.html#readonly_cantlock](rescode.md#readonly_cantlock) [rescode.html#readonly_dbmoved](rescode.md#readonly_dbmoved) [rescode.html#readonly_recovery](rescode.md#readonly_recovery) [rescode.html#readonly_rollback](rescode.md#readonly_rollback)
- SQLITE_READONLY_CANTINIT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_READONLY_CANTLOCK → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_READONLY_DBMOVED → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_8_3](changes.md#version_3_8_3) [releaselog/3_8_3.html](releaselog/3_8_3.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_READONLY_DIRECTORY → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_READONLY_RECOVERY → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_READONLY_ROLLBACK → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_RECURSIVE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_REINDEX → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_REPLACE → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vtab_on_conflict.html](c3ref/vtab_on_conflict.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_vtab_on_conflict](capi3ref.md#sqlite3_vtab_on_conflict)
- SQLITE_RESULT_SUBTYPE → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/result_subtype.html](c3ref/result_subtype.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_result_subtype](capi3ref.md#sqlite3_result_subtype) [changes.html#version_3_45_0](changes.md#version_3_45_0) [compile.html#rcmd](compile.md#rcmd) [compile.html#strict_subtype](compile.md#strict_subtype) [news.html](news.md) [releaselog/3_45_0.html](releaselog/3_45_0.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- SQLITE_REVERSE_UNORDERED_SELECTS → [changes.html#version_3_8_8](changes.md#version_3_8_8) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- SQLITE_ROLLBACK → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/vtab_on_conflict.html](c3ref/vtab_on_conflict.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_vtab_on_conflict](capi3ref.md#sqlite3_vtab_on_conflict)
- SQLITE_ROW → [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/data_count.html](c3ref/data_count.md) [c3ref/step.html](c3ref/step.md) [c3ref/wal_hook.html](c3ref/wal_hook.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_data_count](capi3ref.md#sqlite3_data_count) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [capi3ref.html#sqlite3_wal_hook](capi3ref.md#sqlite3_wal_hook) [compile.html#omit_autoreset](compile.md#omit_autoreset) [opcode.html](opcode.md) [rescode.html](rescode.md) [rescode.html#pve](rescode.md#pve) [session.html#sqlite3changeset_op](session.md#sqlite3changeset_op) [session/sqlite3changeset_op.html](session/sqlite3changeset_op.md)
- SQLITE_RTREE_INT_ONLY → [changes.html#version_3_7_12](changes.md#version_3_7_12) [releaselog/3_7_12.html](releaselog/3_7_12.md)
- SQLITE_SAVEPOINT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SCANSTAT_COMPLEX → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/stmt_scanstatus.html](c3ref/stmt_scanstatus.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_stmt_scanstatus](capi3ref.md#sqlite3_stmt_scanstatus)
- SQLITE_SCANSTAT_EST → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SCANSTAT_EXPLAIN → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SCANSTAT_NAME → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SCANSTAT_NCYCLE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SCANSTAT_NLOOP → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SCANSTAT_NVISIT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SCANSTAT_PARENTID → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SCANSTAT_SELECTID → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SCHEMA → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/prepare.html](c3ref/prepare.md) [c3ref/step.html](c3ref/step.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_prepare](capi3ref.md#sqlite3_prepare) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [changes.html#version_3_7_15](changes.md#version_3_7_15) [changes.html#version_3_7_7_1](changes.md#version_3_7_7_1) [faq.html#q15](faq.md#q15) [fileformat2.html#filesize](fileformat2.md#filesize) [oldnews.html](oldnews.md) [pragma.html#pragma_foreign_keys](pragma.md#pragma_foreign_keys) [pragma.html#pragma_recursive_triggers](pragma.md#pragma_recursive_triggers) [releaselog/3_7_15.html](releaselog/3_7_15.md) [releaselog/3_7_7_1.html](releaselog/3_7_7_1.md) [rescode.html#pve](rescode.md#pve)
- sqlite_schema → [atomiccommit.html#rdlck](atomiccommit.md#rdlck) [changes.html#version_3_50_0](changes.md#version_3_50_0) [cli.html#dtables](cli.md#dtables) [cli.html#sha3sum](cli.md#sha3sum) [fileformat2.html#btypes](fileformat2.md#btypes) [fileformat2.html#ffschema](fileformat2.md#ffschema) [lang_altertable.html#altertableishard](lang_altertable.md#altertableishard) [lang_droptrigger.html](lang_droptrigger.md) [lemon.html](lemon.md) [pragma.html#pragma_integrity_check](pragma.md#pragma_integrity_check) [pragma.html#pragma_writable_schema](pragma.md#pragma_writable_schema) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md) [sharedcache.html#dontuse](sharedcache.md#dontuse)
- sqlite_schema table → [changes.html#version_3_38_0](changes.md#version_3_38_0) [compile.html#printf_precision_limit](compile.md#printf_precision_limit) [foreignkeys.html#fk_actions](foreignkeys.md#fk_actions) [imposter.html](imposter.md) [lang_altertable.html#altertabaddcol](lang_altertable.md#altertabaddcol) [lang_altertable.html#altertabdropcol](lang_altertable.md#altertabdropcol) [lang_altertable.html#caution](lang_altertable.md#caution) [pragma.html#pragma_schema_version](pragma.md#pragma_schema_version) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md) [security.html](security.md) [sharedcache.html#dontuse](sharedcache.md#dontuse) [unlock_notify.html](unlock_notify.md) [whybytecode.html](whybytecode.md)
- SQLITE_SCM_BRANCH → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SCM_DATETIME → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SCM_TAGS → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SECURE_DELETE → [changes.html#version_3_6_21](changes.md#version_3_6_21) [faq.html#q20](faq.md#q20) [pragma.html#pragma_secure_delete](pragma.md#pragma_secure_delete) [releaselog/3_6_21.html](releaselog/3_6_21.md)
- SQLITE_SELECT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SELFORDER1 → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [compile.html#enable_ordered_set_aggregates](compile.md#enable_ordered_set_aggregates)
- sqlite_sequence → [autoinc.html](autoinc.md) [changes.html#version_3_24_0](changes.md#version_3_24_0) [releaselog/3_24_0.html](releaselog/3_24_0.md)
- SQLITE_SERIALIZE_NOCOPY → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SESSION_CONFIG_STRMSIZE → [session.html](session.md) [session/constlist.html](session/constlist.md)
- SQLITE_SESSION_OBJCONFIG_ROWID → [session.html](session.md) [session.html#sqlite3session_object_config](session.md#sqlite3session_object_config) [session/constlist.html](session/constlist.md) [session/sqlite3session_object_config.html](session/sqlite3session_object_config.md)
- SQLITE_SESSION_OBJCONFIG_SIZE → [session.html#sqlite3session_object_config](session.md#sqlite3session_object_config) [session/sqlite3session_object_config.html](session/sqlite3session_object_config.md)
- SQLITE_SETLK_BLOCK_ON_CONNECT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SHM_EXCLUSIVE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SHM_LOCK → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SHM_NLOCK → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SHM_SHARED → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SHM_UNLOCK → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_SORTER_PMASZ → [c3ref/c_config_covering_index_scan.html#sqliteconfigpmasz](c3ref/c_config_covering_index_scan.md#sqliteconfigpmasz) [capi3ref.html#sqliteconfigpmasz](capi3ref.md#sqliteconfigpmasz) [changes.html#version_3_8_8](changes.md#version_3_8_8) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- SQLITE_SOUNDEX → [lang_corefunc.html#soundex](lang_corefunc.md#soundex)
- sqlite_source_id → [c3ref/c_scm_branch.html](c3ref/c_scm_branch.md) [c3ref/libversion.html](c3ref/libversion.md) [capi3ref.html#SQLITE_SCM_BRANCH](capi3ref.md#SQLITE_SCM_BRANCH) [capi3ref.html#sqlite3_libversion](capi3ref.md#sqlite3_libversion) [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_6_18](changes.md#version_3_6_18) [lang_corefunc.html](lang_corefunc.md) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_6_18.html](releaselog/3_6_18.md)
- SQLITE_SOURCE_ID → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/libversion.html](c3ref/libversion.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_libversion](capi3ref.md#sqlite3_libversion) [changes.html#version_3_18_0](changes.md#version_3_18_0) [changes.html#version_3_6_18](changes.md#version_3_6_18) [releaselog/3_18_0.html](releaselog/3_18_0.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_6_18.html](releaselog/3_6_18.md) [th3.html](th3.md)
- sqlite_stat1 → [changes.html#version_3_13_0](changes.md#version_3_13_0) [changes.html#version_3_33_0](changes.md#version_3_33_0) [changes.html#version_3_8_1](changes.md#version_3_8_1) [lang_analyze.html#pragopt](lang_analyze.md#pragopt) [lang_analyze.html#statanal](lang_analyze.md#statanal) [oldnews.html](oldnews.md) [optoverview.html#manctrl](optoverview.md#manctrl) [optoverview.html#multi_index](optoverview.md#multi_index) [queryplanner-ng.html#fossilcasestudy](queryplanner-ng.md#fossilcasestudy) [queryplanner-ng.html#howtofix](queryplanner-ng.md#howtofix) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_33_0.html](releaselog/3_33_0.md) [releaselog/3_8_1.html](releaselog/3_8_1.md)
- SQLITE_STAT1 → [queryplanner-ng.html#fossilcasestudy](queryplanner-ng.md#fossilcasestudy) [queryplanner-ng.html#hazards](queryplanner-ng.md#hazards) [queryplanner-ng.html#howtofix](queryplanner-ng.md#howtofix)
- sqlite_stat2 → [lang_analyze.html#statanal](lang_analyze.md#statanal)
- sqlite_stat3 → [lang_analyze.html#statanal](lang_analyze.md#statanal) [optoverview.html#rangequery](optoverview.md#rangequery)
- sqlite_stat4 → [changes.html#version_3_8_6](changes.md#version_3_8_6) [changes.html#version_3_8_7](changes.md#version_3_8_7) [compile.html#enable_stat4](compile.md#enable_stat4) [lang_analyze.html#statanal](lang_analyze.md#statanal) [optoverview.html#rangequery](optoverview.md#rangequery) [releaselog/3_8_6.html](releaselog/3_8_6.md) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- SQLITE_STAT4 → [th3.html](th3.md)
- SQLITE_STATIC → [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/carray_bind.html](c3ref/carray_bind.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_carray_bind](capi3ref.md#sqlite3_carray_bind) [carray.html#onearg](carray.md#onearg)
- SQLITE_STATUS_MALLOC_COUNT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_STATUS_MALLOC_SIZE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [memstat.html](memstat.md)
- SQLITE_STATUS_MEMORY_USED → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [compile.html#default_memstatus](compile.md#default_memstatus) [compile.html#max_memory](compile.md#max_memory) [malloc.html#memstatus](malloc.md#memstatus) [malloc.html#nofrag](malloc.md#nofrag) [memstat.html](memstat.md)
- SQLITE_STATUS_PAGECACHE_OVERFLOW → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [compile.html#disable_pagecache_overflow_stats](compile.md#disable_pagecache_overflow_stats)
- SQLITE_STATUS_PAGECACHE_SIZE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_6_1](changes.md#version_3_6_1) [compile.html#disable_pagecache_overflow_stats](compile.md#disable_pagecache_overflow_stats) [releaselog/3_6_1.html](releaselog/3_6_1.md)
- SQLITE_STATUS_PAGECACHE_USED → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_STATUS_PARSER_STACK → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [compile.html#yytrackmaxstackdepth](compile.md#yytrackmaxstackdepth)
- SQLITE_STATUS_SCRATCH_OVERFLOW → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_STATUS_SCRATCH_SIZE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_6_1](changes.md#version_3_6_1) [releaselog/3_6_1.html](releaselog/3_6_1.md)
- SQLITE_STATUS_SCRATCH_USED → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- sqlite_stmt → [changes.html#version_3_39_1](changes.md#version_3_39_1) [releaselog/3_39_1.html](releaselog/3_39_1.md) [releaselog/3_39_2.html](releaselog/3_39_2.md) [releaselog/3_39_3.html](releaselog/3_39_3.md) [releaselog/3_39_4.html](releaselog/3_39_4.md) [vtablist.html](vtablist.md)
- SQLITE_STMT virtual table → [changes.html#version_3_20_0](changes.md#version_3_20_0) [compile.html#enable_stmtvtab](compile.md#enable_stmtvtab) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- SQLITE_STMTJRNL_SPILL → [c3ref/c_config_covering_index_scan.html#sqliteconfigstmtjrnlspill](c3ref/c_config_covering_index_scan.md#sqliteconfigstmtjrnlspill) [capi3ref.html#sqliteconfigstmtjrnlspill](capi3ref.md#sqliteconfigstmtjrnlspill) [changes.html#version_3_12_0](changes.md#version_3_12_0) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md)
- SQLITE_STMTSTATUS counter → [c3ref/stmt_status.html](c3ref/stmt_status.md) [capi3ref.html#sqlite3_stmt_status](capi3ref.md#sqlite3_stmt_status)
- SQLITE_STMTSTATUS counters → [c3ref/stmt_status.html](c3ref/stmt_status.md) [capi3ref.html#sqlite3_stmt_status](capi3ref.md#sqlite3_stmt_status)
- SQLITE_STMTSTATUS_AUTOINDEX → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [stmt.html](stmt.md)
- SQLITE_STMTSTATUS_FILTER_HIT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_STMTSTATUS_FILTER_MISS → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_STMTSTATUS_FULLSCAN_STEP → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [lang_indexedby.html](lang_indexedby.md) [stmt.html](stmt.md)
- SQLITE_STMTSTATUS_MEMUSED → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [stmt.html](stmt.md)
- SQLITE_STMTSTATUS_REPREPARE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [stmt.html](stmt.md)
- SQLITE_STMTSTATUS_RUN → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [stmt.html](stmt.md)
- SQLITE_STMTSTATUS_SORT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [lang_indexedby.html](lang_indexedby.md) [stmt.html](stmt.md)
- SQLITE_STMTSTATUS_VM_STEP → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_8_0](changes.md#version_3_8_0) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md) [stmt.html](stmt.md)
- SQLITE_STRICT_SUBTYPE → [compile.html#rcmd](compile.md#rcmd)
- SQLITE_SUBTYPE → [appfunc.html](appfunc.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/value_subtype.html](c3ref/value_subtype.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_value_subtype](capi3ref.md#sqlite3_value_subtype) [changes.html#version_3_31_0](changes.md#version_3_31_0) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- SQLITE_SYNC_DATAONLY → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- SQLITE_SYNC_FULL → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- SQLITE_SYNC_NORMAL → [34to35.html](34to35.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/io_methods.html](c3ref/io_methods.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_io_methods](capi3ref.md#sqlite3_io_methods)
- SQLITE_SYSAPI → [compile.html#apicall](compile.md#apicall) [compile.html#cdecl](compile.md#cdecl) [compile.html#sysapi](compile.md#sysapi) [compile.html#tclapi](compile.md#tclapi)
- SQLITE_TEMP_STORE → [35to36.html](35to36.md) [inmemorydb.html#temp_db](inmemorydb.md#temp_db) [pragma.html#pragma_temp_store](pragma.md#pragma_temp_store) [tempfiles.html#otheropt](tempfiles.md#otheropt) [tempfiles.html#tempstore](tempfiles.md#tempstore)
- SQLITE_TESTCTRL_ALWAYS → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [testing.html#defcode](testing.md#defcode)
- SQLITE_TESTCTRL_ASSERT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_ATOF → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_BENIGN_MALLOC_HOOKS → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_BITVEC_TEST → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_BYTEORDER → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_8_5](changes.md#version_3_8_5) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- SQLITE_TESTCTRL_EXPLAIN_STMT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_7_10](changes.md#version_3_7_10) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- SQLITE_TESTCTRL_EXTRA_SCHEMA_CHECKS → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_FAULT_INSTALL → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_FIRST → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_FK_NO_ACTION → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_GETOPT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_IMPOSTER → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_INTERNAL_FUNCTIONS → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_ISINIT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_ISKEYWORD → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_JSON_SELFCHECK → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_LAST → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_LOCALTIME_FAULT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_LOGEST → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_NEVER_CORRUPT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_ONCE_RESET_THRESHOLD → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_OPTIMIZATIONS → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [testing.html#disopttest](testing.md#disopttest)
- SQLITE_TESTCTRL_PARSER_COVERAGE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_PENDING_BYTE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_PRNG_RESET → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_PRNG_RESTORE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_PRNG_SAVE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_PRNG_SEED → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_RESERVE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_RESULT_INTREAL → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_SCRATCHMALLOC → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_SEEK_COUNT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_SORTER_MMAP → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_TRACEFLAGS → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_TUNE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_USELONGDOUBLE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TESTCTRL_VDBE_COVERAGE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_8_4](changes.md#version_3_8_4) [releaselog/3_8_4.html](releaselog/3_8_4.md) [releaselog/3_8_4_1.html](releaselog/3_8_4_1.md) [releaselog/3_8_4_2.html](releaselog/3_8_4_2.md) [releaselog/3_8_4_3.html](releaselog/3_8_4_3.md)
- SQLITE_TEXT → [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob)
- SQLITE_THREADSAFE → [c3ref/c_config_covering_index_scan.html#sqliteconfiggetmutex](c3ref/c_config_covering_index_scan.md#sqliteconfiggetmutex) [c3ref/c_config_covering_index_scan.html#sqliteconfigmultithread](c3ref/c_config_covering_index_scan.md#sqliteconfigmultithread) [c3ref/c_config_covering_index_scan.html#sqliteconfigmutex](c3ref/c_config_covering_index_scan.md#sqliteconfigmutex) [c3ref/c_config_covering_index_scan.html#sqliteconfigserialized](c3ref/c_config_covering_index_scan.md#sqliteconfigserialized) [c3ref/c_config_covering_index_scan.html#sqliteconfigsinglethread](c3ref/c_config_covering_index_scan.md#sqliteconfigsinglethread) [c3ref/threadsafe.html](c3ref/threadsafe.md) [c3ref/value.html](c3ref/value.md) [capi3ref.html#sqlite3_threadsafe](capi3ref.md#sqlite3_threadsafe) [capi3ref.html#sqlite3_value](capi3ref.md#sqlite3_value) [capi3ref.html#sqliteconfiggetmutex](capi3ref.md#sqliteconfiggetmutex) [capi3ref.html#sqliteconfigmultithread](capi3ref.md#sqliteconfigmultithread) [capi3ref.html#sqliteconfigmutex](capi3ref.md#sqliteconfigmutex) [capi3ref.html#sqliteconfigserialized](capi3ref.md#sqliteconfigserialized) [capi3ref.html#sqliteconfigsinglethread](capi3ref.md#sqliteconfigsinglethread) [compile.html#rcmd](compile.md#rcmd) [threadsafe.html](threadsafe.md)
- SQLITE_TOOBIG → [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/str_errcode.html](c3ref/str_errcode.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_str_errcode](capi3ref.md#sqlite3_str_errcode) [compile.html#printf_precision_limit](compile.md#printf_precision_limit) [rescode.html#pve](rescode.md#pve)
- SQLITE_TRACE → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/trace_v2.html](c3ref/trace_v2.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_trace_v2](capi3ref.md#sqlite3_trace_v2)
- SQLITE_TRACE_CLOSE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TRACE_PROFILE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TRACE_ROW → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TRACE_SIZE_LIMIT → [c3ref/expanded_sql.html](c3ref/expanded_sql.md) [c3ref/profile.html](c3ref/profile.md) [capi3ref.html#sqlite3_expanded_sql](capi3ref.md#sqlite3_expanded_sql) [capi3ref.html#sqlite3_profile](capi3ref.md#sqlite3_profile) [changes.html#version_3_7_17](changes.md#version_3_7_17) [compile.html#yystackdepth](compile.md#yystackdepth) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- SQLITE_TRACE_STMT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TRANSACTION → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TRANSIENT → [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/carray_bind.html](c3ref/carray_bind.md) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_carray_bind](capi3ref.md#sqlite3_carray_bind) [carray.html#onearg](carray.md#onearg)
- SQLITE_TXN_NONE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TXN_READ → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_TXN_WRITE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_UNTESTABLE → [changes.html#version_3_16_0](changes.md#version_3_16_0) [compile.html#omit_builtin_test](compile.md#omit_builtin_test) [releaselog/3_16_0.html](releaselog/3_16_0.md) [releaselog/3_16_1.html](releaselog/3_16_1.md) [releaselog/3_16_2.html](releaselog/3_16_2.md)
- SQLITE_UPDATE → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/update_hook.html](c3ref/update_hook.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite) [capi3ref.html#sqlite3_update_hook](capi3ref.md#sqlite3_update_hook) [session.html#sqlite3changeset_new](session.md#sqlite3changeset_new) [session.html#sqlite3changeset_old](session.md#sqlite3changeset_old) [session.html#sqlite3changeset_op](session.md#sqlite3changeset_op) [session/sqlite3changeset_new.html](session/sqlite3changeset_new.md) [session/sqlite3changeset_old.html](session/sqlite3changeset_old.md) [session/sqlite3changeset_op.html](session/sqlite3changeset_op.md)
- SQLITE_USE_FCNTL_TRACE → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntltrace](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntltrace) [capi3ref.html#sqlitefcntltrace](capi3ref.md#sqlitefcntltrace)
- SQLITE_USE_SEH → [changes.html#version_3_43_0](changes.md#version_3_43_0) [changes.html#version_3_44_0](changes.md#version_3_44_0) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md)
- SQLITE_USE_URI → [c3ref/c_config_covering_index_scan.html#sqliteconfiguri](c3ref/c_config_covering_index_scan.md#sqliteconfiguri) [c3ref/open.html#urifilenamesinsqlite3open](c3ref/open.md#urifilenamesinsqlite3open) [capi3ref.html#sqliteconfiguri](capi3ref.md#sqliteconfiguri) [capi3ref.html#urifilenamesinsqlite3open](capi3ref.md#urifilenamesinsqlite3open) [uri.html](uri.md)
- SQLITE_UTF16 → [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/create_collation.html](c3ref/create_collation.md) [c3ref/create_function.html](c3ref/create_function.md) [c3ref/result_blob.html](c3ref/result_blob.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_create_collation](capi3ref.md#sqlite3_create_collation) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob)
- SQLITE_UTF16_ALIGNED → [c3ref/constlist.html](c3ref/constlist.md) [c3ref/create_collation.html](c3ref/create_collation.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlite3_create_collation](capi3ref.md#sqlite3_create_collation)
- SQLITE_UTF16BE → [appfunc.html](appfunc.md) [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/collation_needed.html](c3ref/collation_needed.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/create_collation.html](c3ref/create_collation.md) [c3ref/create_function.html](c3ref/create_function.md) [c3ref/result_blob.html](c3ref/result_blob.md) [c3ref/value_encoding.html](c3ref/value_encoding.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_collation_needed](capi3ref.md#sqlite3_collation_needed) [capi3ref.html#sqlite3_create_collation](capi3ref.md#sqlite3_create_collation) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [capi3ref.html#sqlite3_value_encoding](capi3ref.md#sqlite3_value_encoding)
- SQLITE_UTF16LE → [appfunc.html](appfunc.md) [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/collation_needed.html](c3ref/collation_needed.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/create_collation.html](c3ref/create_collation.md) [c3ref/create_function.html](c3ref/create_function.md) [c3ref/result_blob.html](c3ref/result_blob.md) [c3ref/value_encoding.html](c3ref/value_encoding.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_collation_needed](capi3ref.md#sqlite3_collation_needed) [capi3ref.html#sqlite3_create_collation](capi3ref.md#sqlite3_create_collation) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [capi3ref.html#sqlite3_value_encoding](capi3ref.md#sqlite3_value_encoding)
- SQLITE_UTF8 → [appfunc.html](appfunc.md) [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/c_deterministic.html](c3ref/c_deterministic.md) [c3ref/collation_needed.html](c3ref/collation_needed.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/create_collation.html](c3ref/create_collation.md) [c3ref/create_function.html](c3ref/create_function.md) [c3ref/result_blob.html](c3ref/result_blob.md) [c3ref/value_encoding.html](c3ref/value_encoding.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_DETERMINISTIC](capi3ref.md#SQLITE_DETERMINISTIC) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_collation_needed](capi3ref.md#sqlite3_collation_needed) [capi3ref.html#sqlite3_create_collation](capi3ref.md#sqlite3_create_collation) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [capi3ref.html#sqlite3_value_encoding](capi3ref.md#sqlite3_value_encoding)
- SQLITE_UTF8_ZT → [c3ref/bind_blob.html#byteorderdeterminationrules](c3ref/bind_blob.md#byteorderdeterminationrules) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/result_blob.html](c3ref/result_blob.md) [capi3ref.html](capi3ref.md) [capi3ref.html#byteorderdeterminationrules](capi3ref.md#byteorderdeterminationrules) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- sqlite_version → [c3ref/c_scm_branch.html](c3ref/c_scm_branch.md) [c3ref/libversion.html](c3ref/libversion.md) [capi3ref.html#SQLITE_SCM_BRANCH](capi3ref.md#SQLITE_SCM_BRANCH) [capi3ref.html#sqlite3_libversion](capi3ref.md#sqlite3_libversion) [deterministic.html#dtexception](deterministic.md#dtexception) [expridx.html](expridx.md) [lang_corefunc.html](lang_corefunc.md) [lang_createindex.html#indexexpr](lang_createindex.md#indexexpr)
- SQLITE_VERSION → [c3ref/c_scm_branch.html](c3ref/c_scm_branch.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/libversion.html](c3ref/libversion.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_SCM_BRANCH](capi3ref.md#SQLITE_SCM_BRANCH) [capi3ref.html#sqlite3_libversion](capi3ref.md#sqlite3_libversion)
- SQLITE_VERSION_NUMBER → [c3ref/c_scm_branch.html](c3ref/c_scm_branch.md) [c3ref/constlist.html](c3ref/constlist.md) [c3ref/libversion.html](c3ref/libversion.md) [capi3ref.html](capi3ref.md) [capi3ref.html#SQLITE_SCM_BRANCH](capi3ref.md#SQLITE_SCM_BRANCH) [capi3ref.html#sqlite3_libversion](capi3ref.md#sqlite3_libversion) [fileformat2.html#database_header](fileformat2.md#database_header) [fileformat2.html#validfor](fileformat2.md#validfor) [versionnumbers.html](versionnumbers.md)
- SQLITE_VTAB_CONSTRAINT_SUPPORT → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_VTAB_DIRECTONLY → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_31_0](changes.md#version_3_31_0) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [security.html#baddb](security.md#baddb) [vtab.html#customvtab](vtab.md#customvtab) [vtab.html#xcreate](vtab.md#xcreate)
- SQLITE_VTAB_INNOCUOUS → [c3ref/c_dbconfig_defensive.html#sqlitedbconfigtrustedschema](c3ref/c_dbconfig_defensive.md#sqlitedbconfigtrustedschema) [c3ref/c_prepare_dont_log.html#sqlitepreparefromddl](c3ref/c_prepare_dont_log.md#sqlitepreparefromddl) [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [capi3ref.html#sqlitedbconfigtrustedschema](capi3ref.md#sqlitedbconfigtrustedschema) [capi3ref.html#sqlitepreparefromddl](capi3ref.md#sqlitepreparefromddl) [changes.html#version_3_31_0](changes.md#version_3_31_0) [changes.html#version_3_44_0](changes.md#version_3_44_0) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md) [vtab.html#customvtab](vtab.md#customvtab)
- SQLITE_VTAB_USES_ALL_SCHEMAS → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_WARNING → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [rescode.html#pve](rescode.md#pve)
- SQLITE_WARNING_AUTOINDEX → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md) [changes.html#version_3_8_0](changes.md#version_3_8_0) [optoverview.html#autoindex](optoverview.md#autoindex) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md) [rescode.html#extrc](rescode.md#extrc)
- SQLITE_WIN32_DATA_DIRECTORY_TYPE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_WIN32_HEAP_CREATE → [malloc.html#win32heap](malloc.md#win32heap)
- SQLITE_WIN32_MALLOC → [c3ref/c_config_covering_index_scan.html#sqliteconfigwin32heapsize](c3ref/c_config_covering_index_scan.md#sqliteconfigwin32heapsize) [capi3ref.html#sqliteconfigwin32heapsize](capi3ref.md#sqliteconfigwin32heapsize) [malloc.html#win32heap](malloc.md#win32heap)
- SQLITE_WIN32_MALLOC_VALIDATE → [malloc.html#win32heap](malloc.md#win32heap)
- SQLITE_WIN32_TEMP_DIRECTORY_TYPE → [c3ref/constlist.html](c3ref/constlist.md) [capi3ref.html](capi3ref.md)
- SQLITE_ZERO_MALLOC → [changes.html#version_3_6_5](changes.md#version_3_6_5) [malloc.html#memsysx](malloc.md#memsysx) [releaselog/3_6_5.html](releaselog/3_6_5.md) [selfcontained.html](selfcontained.md)
- sqrt → [lang_mathfunc.html](lang_mathfunc.md)
- stale expression index → [changes.html#version_3_53_0](changes.md#version_3_53_0) [howtocorrupt.html#cfgerr](howtocorrupt.md#cfgerr) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- stale expression indexes → [changes.html#version_3_53_0](changes.md#version_3_53_0) [expridx.html](expridx.md) [news.html](news.md) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- star-query → [changes.html#version_3_49_0](changes.md#version_3_49_0) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md)
- statement journal → [c3ref/c_config_covering_index_scan.html#sqliteconfigstmtjrnlspill](c3ref/c_config_covering_index_scan.md#sqliteconfigstmtjrnlspill) [capi3ref.html#sqliteconfigstmtjrnlspill](capi3ref.md#sqliteconfigstmtjrnlspill) [changes.html#version_3_12_0](changes.md#version_3_12_0) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md)
- Statement journals → [c3ref/c_config_covering_index_scan.html#sqliteconfigstmtjrnlspill](c3ref/c_config_covering_index_scan.md#sqliteconfigstmtjrnlspill) [capi3ref.html#sqliteconfigstmtjrnlspill](capi3ref.md#sqliteconfigstmtjrnlspill)
- statement journals → [compile.html#stmtjrnl_spill](compile.md#stmtjrnl_spill)
- status parameters → [c3ref/status.html](c3ref/status.md) [capi3ref.html#sqlite3_status](capi3ref.md#sqlite3_status)
- storage class → [lang_expr.html#castexpr](lang_expr.md#castexpr)
- STORED generated columns → [staleexpridx.html#selfheal](staleexpridx.md#selfheal)
- strategies → [eqp.html](eqp.md)
- strftime → [lang_datefunc.html#subsec](lang_datefunc.md#subsec)
- strftime SQL function → [changes.html#version_3_44_0](changes.md#version_3_44_0) [changes.html#version_3_46_0](changes.md#version_3_46_0) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md) [releaselog/3_46_0.html](releaselog/3_46_0.md) [releaselog/3_46_1.html](releaselog/3_46_1.md)
- STRICT → [datatype3.html#affname](datatype3.md#affname) [lang_createtable.html#primkeyconst](lang_createtable.md#primkeyconst) [quirks.html](quirks.md)
- STRICT table → [pragma.html#pragma_table_list](pragma.md#pragma_table_list)
- STRICT tables → [changes.html#version_3_37_0](changes.md#version_3_37_0) [datatype3.html](datatype3.md) [flextypegood.html](flextypegood.md) [news.html](news.md) [quirks.html](quirks.md) [recovery.html](recovery.md) [releaselog/3_37_0.html](releaselog/3_37_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md)
- strict type checking → [lang_createtable.html](lang_createtable.md)
- string_agg → [changes.html#version_3_44_0](changes.md#version_3_44_0) [lang_aggfunc.html#aggorderby](lang_aggfunc.md#aggorderby) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md)
- subprograms → [opcode.html](opcode.md)
- Subqueries → [fullsql.html](fullsql.md)
- subsec modifier → [lang_datefunc.html#dttm](lang_datefunc.md#dttm) [lang_datefunc.html#uepch](lang_datefunc.md#uepch)
- subsecond modifier → [changes.html#version_3_42_0](changes.md#version_3_42_0) [releaselog/3_42_0.html](releaselog/3_42_0.md)
- substr → [arch.html](arch.md) [changes.html#version_3_6_21](changes.md#version_3_6_21) [fts3.html#fts3tok](fts3.md#fts3tok) [invalidutf.html](invalidutf.md) [lang_corefunc.html](lang_corefunc.md) [releaselog/3_6_21.html](releaselog/3_6_21.md)
- substr SQL function → [changes.html#version_3_34_0](changes.md#version_3_34_0) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md)
- sum → [changes.html#version_3_43_1](changes.md#version_3_43_1) [changes.html#version_3_45_3](changes.md#version_3_45_3) [lang_select.html#bareagg](lang_select.md#bareagg) [news.html](news.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- sumFunc → [lang_aggfunc.html#aggfunclist](lang_aggfunc.md#aggfunclist)
- swarmvtab → [vtablist.html](vtablist.md)
- swarmvtab context → [swarmvtab.html#overview](swarmvtab.md#overview)
- synchronous → [tempfiles.html#tempdb](tempfiles.md#tempdb)
- synchronous pragma → [c3ref/c_sync_dataonly.html](c3ref/c_sync_dataonly.md) [capi3ref.html#SQLITE_SYNC_DATAONLY](capi3ref.md#SQLITE_SYNC_DATAONLY) [howtocorrupt.html#fork](howtocorrupt.md#fork)
- syntax diagrams → [changes.html#version_3_34_0](changes.md#version_3_34_0) [lang.html](lang.md) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md)
- table b-tree → [opcode.html#codes](opcode.md#codes)
- table data format → [stricttables.html](stricttables.md)
- table-constraint → [lang_createtable.html](lang_createtable.md) [lang_createtable.html#primkeyconst](lang_createtable.md#primkeyconst) [lang_createtable.html#tablecoldef](lang_createtable.md#tablecoldef) [lang_createtable.html#uniqueconst](lang_createtable.md#uniqueconst)
- table-options → [lang_createtable.html](lang_createtable.md)
- table-or-subquery → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- table-valued function → [carray.html](carray.md) [changes.html#version_3_22_0](changes.md#version_3_22_0) [changes.html#version_3_23_0](changes.md#version_3_23_0) [changes.html#version_3_9_0](changes.md#version_3_9_0) [completion.html](completion.md) [dbpage.html](dbpage.md) [fts5.html](fts5.md) [fullsql.html](fullsql.md) [json1.html#jbtree](json1.md#jbtree) [lang_expr.html#in_op](lang_expr.md#in_op) [lang_select.html#tabfunc1](lang_select.md#tabfunc1) [loadext.html#write](loadext.md#write) [releaselog/3_22_0.html](releaselog/3_22_0.md) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md) [series.html](series.md) [vtablist.html](vtablist.md) [zipfile.html](zipfile.md)
- table-valued functions → [appfunc.html](appfunc.md) [bytecodevtab.html](bytecodevtab.md) [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_26_0](changes.md#version_3_26_0) [changes.html#version_3_9_0](changes.md#version_3_9_0) [json1.html](json1.md) [json1.html#jbtree](json1.md#jbtree) [lang_select.html#tabfunc1](lang_select.md#tabfunc1) [oldnews.html](oldnews.md) [pragma.html#pragfunc](pragma.md#pragfunc) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_26_0.html](releaselog/3_26_0.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab) [vtab.html#erpotvf](vtab.md#erpotvf) [vtab.html#xshadowname](vtab.md#xshadowname) [vtablist.html](vtablist.md)
- table-valued functions in the FROM clause → [dbstat.html](dbstat.md)
- tabular modes → [climode.html#opt-sw](climode.md#opt-sw)
- tabular output modes → [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- tan → [lang_mathfunc.html](lang_mathfunc.md)
- tanh → [lang_mathfunc.html](lang_mathfunc.md)
- Tcl extension → [lang_expr.html#varparam](lang_expr.md#varparam)
- TCL Interface → [arch.html](arch.md) [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_28_0](changes.md#version_3_28_0) [changes.html#version_3_30_0](changes.md#version_3_30_0) [changes.html#version_3_47_0](changes.md#version_3_47_0) [changes.html#version_3_51_0](changes.md#version_3_51_0) [changes.html#version_3_53_0](changes.md#version_3_53_0) [changes.html#version_3_6_19](changes.md#version_3_6_19) [changes.html#version_3_7_10](changes.md#version_3_7_10) [compile.html#tclapi](compile.md#tclapi) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_28_0.html](releaselog/3_28_0.md) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [releaselog/3_6_19.html](releaselog/3_6_19.md) [releaselog/3_7_10.html](releaselog/3_7_10.md)
- TCL interface eval method → [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- TCL test suite → [compile.html#tclapi](compile.md#tclapi) [malloc.html](malloc.md) [qmplan.html](qmplan.md)
- TEMP triggers → [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- temp_store pragma → [inmemorydb.html#temp_db](inmemorydb.md#temp_db) [tempfiles.html#otheropt](tempfiles.md#otheropt) [tempfiles.html#tempstore](tempfiles.md#tempstore)
- temp_store_directory → [pragma.html#pragma_temp_store](pragma.md#pragma_temp_store)
- temp_store_directory pragma → [c3ref/c_access_exists.html](c3ref/c_access_exists.md) [c3ref/temp_directory.html](c3ref/temp_directory.md) [capi3ref.html#SQLITE_ACCESS_EXISTS](capi3ref.md#SQLITE_ACCESS_EXISTS) [capi3ref.html#sqlite3_temp_directory](capi3ref.md#sqlite3_temp_directory)
- temporary directory search algorithm → [changes.html#version_3_13_0](changes.md#version_3_13_0) [releaselog/3_13_0.html](releaselog/3_13_0.md)
- temporary disk files → [rescode.html#cantopen](rescode.md#cantopen) [rescode.html#full](rescode.md#full) [shortnames.html](shortnames.md)
- temporary tables → [pragma.html#pragma_temp_store](pragma.md#pragma_temp_store) [pragma.html#pragma_temp_store_directory](pragma.md#pragma_temp_store_directory)
- tempstore → [compile.html#temp_store](compile.md#temp_store)
- test coverage → [about.html](about.md) [changes.html#version_3_6_17](changes.md#version_3_6_17) [faq.html#q17](faq.md#q17) [features.html](features.md) [malloc.html](malloc.md) [oldnews.html](oldnews.md) [releaselog/3_6_17.html](releaselog/3_6_17.md) [support.html#prosupport](support.md#prosupport) [th3.html](th3.md)
- test harnesses → [th3.html](th3.md)
- test suite → [limits.html](limits.md) [tclsqlite.html](tclsqlite.md)
- testcase macros → [testing.html#tension](testing.md#tension)
- tested → [appfileformat.html](appfileformat.md) [oldnews.html](oldnews.md)
- testing → [amalg-v-canon.html#canon](amalg-v-canon.md#canon) [assert.html](assert.md) [changes.html#version_3_8_10](changes.md#version_3_8_10) [hirely.html](hirely.md) [howtocorrupt.html#cfgerr](howtocorrupt.md#cfgerr) [malloc.html](malloc.md) [oldnews.html](oldnews.md) [qmplan.html](qmplan.md) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md)
- text encoding → [fileformat2.html#serialtype](fileformat2.md#serialtype)
- TH3 → [malloc.html](malloc.md) [oldnews.html](oldnews.md) [qmplan.html](qmplan.md) [support.html#prosupport](support.md#prosupport) [testing.html#coverage](testing.md#coverage) [testing.html#stmtvbr](testing.md#stmtvbr) [testing.html#tcl](testing.md#tcl)
- the - and - operators → [changes.html#version_3_38_0](changes.md#version_3_38_0) [changes.html#version_3_46_0](changes.md#version_3_46_0) [lang_expr.html#collateop](lang_expr.md#collateop) [lang_expr.html#extract](lang_expr.md#extract) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md) [releaselog/3_46_0.html](releaselog/3_46_0.md) [releaselog/3_46_1.html](releaselog/3_46_1.md)
- the - operator → [changes.html#version_3_47_0](changes.md#version_3_47_0) [json1.html#jobj](json1.md#jobj) [json1.html#jset](json1.md#jset) [json1.html#varg](json1.md#varg) [releaselog/3_47_0.html](releaselog/3_47_0.md) [releaselog/3_47_1.html](releaselog/3_47_1.md) [releaselog/3_47_2.html](releaselog/3_47_2.md) [staleexpridx.html](staleexpridx.md)
- the amalgamation → [c3ref/libversion.html](c3ref/libversion.md) [capi3ref.html#sqlite3_libversion](capi3ref.md#sqlite3_libversion) [carray.html](carray.md) [changes.html#version_3_51_0](changes.md#version_3_51_0) [compile.html#enable_carray](compile.md#enable_carray) [compile.html#enable_percentile](compile.md#enable_percentile) [lang_aggfunc.html#median](lang_aggfunc.md#median) [lang_aggfunc.html#percentile](lang_aggfunc.md#percentile) [lang_aggfunc.html#percentile_cont](lang_aggfunc.md#percentile_cont) [lang_aggfunc.html#percentile_disc](lang_aggfunc.md#percentile_disc) [percentile.html](percentile.md) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md)
- The Fossil NGQP Upgrade Case Study → [optoverview.html#crossjoin](optoverview.md#crossjoin)
- the json1 extension → [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_9_0](changes.md#version_3_9_0) [changes.html#version_3_9_1](changes.md#version_3_9_1) [oldnews.html](oldnews.md) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- The Use Of assert In SQLite → [howtocorrupt.html#svptbug](howtocorrupt.md#svptbug) [testing.html#asserts](testing.md#asserts)
- Things That Can Go Wrong → [lockingv3.html#how_to_corrupt](lockingv3.md#how_to_corrupt)
- threading mode → [c3ref/c_config_covering_index_scan.html#sqliteconfigmultithread](c3ref/c_config_covering_index_scan.md#sqliteconfigmultithread) [c3ref/c_config_covering_index_scan.html#sqliteconfigserialized](c3ref/c_config_covering_index_scan.md#sqliteconfigserialized) [c3ref/c_config_covering_index_scan.html#sqliteconfigsinglethread](c3ref/c_config_covering_index_scan.md#sqliteconfigsinglethread) [c3ref/db_mutex.html](c3ref/db_mutex.md) [c3ref/errcode.html](c3ref/errcode.md) [c3ref/open.html](c3ref/open.md) [c3ref/threadsafe.html](c3ref/threadsafe.md) [capi3ref.html#sqlite3_db_mutex](capi3ref.md#sqlite3_db_mutex) [capi3ref.html#sqlite3_errcode](capi3ref.md#sqlite3_errcode) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open) [capi3ref.html#sqlite3_threadsafe](capi3ref.md#sqlite3_threadsafe) [capi3ref.html#sqliteconfigmultithread](capi3ref.md#sqliteconfigmultithread) [capi3ref.html#sqliteconfigserialized](capi3ref.md#sqliteconfigserialized) [capi3ref.html#sqliteconfigsinglethread](capi3ref.md#sqliteconfigsinglethread) [cintro.html](cintro.md) [compile.html#threadsafe](compile.md#threadsafe) [faq.html#q6](faq.md#q6)
- time → [lang_datefunc.html#subsec](lang_datefunc.md#subsec)
- time shift modifiers → [changes.html#version_3_43_0](changes.md#version_3_43_0) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md)
- time-value → [lang_datefunc.html](lang_datefunc.md)
- time-values → [lang_datefunc.html](lang_datefunc.md)
- timediff SQL function → [changes.html#version_3_43_0](changes.md#version_3_43_0) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md)
- tokenizer → [fts3.html#compiling_and_enabling_fts3_and_fts4](fts3.md#compiling_and_enabling_fts3_and_fts4) [fts3.html#f4alid](fts3.md#f4alid) [fts3.html#fts4](fts3.md#fts4) [fts3.html#simple_fts_queries](fts3.md#simple_fts_queries)
- total → [changes.html#version_3_43_1](changes.md#version_3_43_1) [lang_aggfunc.html#avg](lang_aggfunc.md#avg) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md)
- total aggregate function → [floatingpoint.html#decimal_sum](floatingpoint.md#decimal_sum)
- total_changes → [lang_corefunc.html](lang_corefunc.md)
- transaction state → [c3ref/txn_state.html](c3ref/txn_state.md) [capi3ref.html#sqlite3_txn_state](capi3ref.md#sqlite3_txn_state)
- transactional → [fasterthanfs.html](fasterthanfs.md)
- treats the CROSS JOIN operator specially → [optoverview.html#joins](optoverview.md#joins) [queryplanner-ng.html#howtofix](queryplanner-ng.md#howtofix)
- trigger → [changes.html#version_3_45_3](changes.md#version_3_45_3) [news.html](news.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- triggers → [lang_returning.html](lang_returning.md)
- trigram indexes → [changes.html#version_3_34_0](changes.md#version_3_34_0) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md)
- trim → [lang_corefunc.html](lang_corefunc.md)
- trunc → [lang_mathfunc.html](lang_mathfunc.md)
- truncate optimization → [c3ref/set_authorizer.html](c3ref/set_authorizer.md) [c3ref/update_hook.html](c3ref/update_hook.md) [capi3ref.html#sqlite3_set_authorizer](capi3ref.md#sqlite3_set_authorizer) [capi3ref.html#sqlite3_update_hook](capi3ref.md#sqlite3_update_hook) [changes.html#version_3_6_21](changes.md#version_3_6_21) [changes.html#version_3_6_5](changes.md#version_3_6_5) [compile.html#omit_truncate_optimization](compile.md#omit_truncate_optimization) [releaselog/3_6_21.html](releaselog/3_6_21.md) [releaselog/3_6_5.html](releaselog/3_6_5.md)
- trusted_schema pragma → [changes.html#version_3_31_0](changes.md#version_3_31_0) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md)
- type affinity → [rtree.html](rtree.md) [rtree.html#auxcol](rtree.md#auxcol)
- type-name → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- typeof → [arch.html](arch.md) [changes.html#version_3_7_12](changes.md#version_3_7_12) [lang_corefunc.html](lang_corefunc.md) [releaselog/3_7_12.html](releaselog/3_7_12.md)
- UINT collating sequence → [changes.html#version_3_32_0](changes.md#version_3_32_0) [cli.html#miscfeatures](cli.md#miscfeatures) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md)
- unhex → [base64.html](base64.md) [changes.html#version_3_41_0](changes.md#version_3_41_0) [lang_corefunc.html](lang_corefunc.md) [lang_corefunc.html#hex](lang_corefunc.md#hex) [releaselog/3_41_0.html](releaselog/3_41_0.md) [releaselog/3_41_1.html](releaselog/3_41_1.md) [releaselog/3_41_2.html](releaselog/3_41_2.md)
- unicode → [changes.html#version_3_7_16](changes.md#version_3_7_16) [lang_corefunc.html](lang_corefunc.md) [releaselog/3_7_16.html](releaselog/3_7_16.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md)
- unicode61 → [changes.html#version_3_8_0](changes.md#version_3_8_0) [changes.html#version_3_8_6](changes.md#version_3_8_6) [compile.html#disable_fts3_unicode](compile.md#disable_fts3_unicode) [releaselog/3_8_0.html](releaselog/3_8_0.md) [releaselog/3_8_0_1.html](releaselog/3_8_0_1.md) [releaselog/3_8_0_2.html](releaselog/3_8_0_2.md) [releaselog/3_8_6.html](releaselog/3_8_6.md)
- unindexed → [fts5.html#appendix_a](fts5.md#appendix_a) [fts5.html#fts5_table_creation_and_initialization](fts5.md#fts5_table_creation_and_initialization)
- UNION virtual table → [changes.html#version_3_20_0](changes.md#version_3_20_0) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md)
- unionvtab → [swarmvtab.html#compiling_and_using_swarmvtab](swarmvtab.md#compiling_and_using_swarmvtab) [vtablist.html](vtablist.md)
- UNIQUE → [changes.html#version_3_8_6](changes.md#version_3_8_6) [conflict.html](conflict.md) [expridx.html](expridx.md) [fileformat2.html#ffschema](fileformat2.md#ffschema) [fileformat2.html#intschema](fileformat2.md#intschema) [fullsql.html](fullsql.md) [lang_conflict.html](lang_conflict.md) [releaselog/3_8_6.html](releaselog/3_8_6.md) [schematab.html](schematab.md) [withoutrowid.html#bene](withoutrowid.md#bene)
- UNIQUE constraint → [optoverview.html#autoindex](optoverview.md#autoindex) [pragma.html#pragma_index_info](pragma.md#pragma_index_info) [pragma.html#pragma_index_list](pragma.md#pragma_index_list) [pragma.html#pragma_index_xinfo](pragma.md#pragma_index_xinfo) [rescode.html#constraint_unique](rescode.md#constraint_unique) [rowidtable.html](rowidtable.md)
- UNIQUE constraints → [stricttables.html](stricttables.md)
- unique index → [lang_upsert.html](lang_upsert.md) [withoutrowid.html#bene](withoutrowid.md#bene)
- unistr → [changes.html#version_3_50_0](changes.md#version_3_50_0) [lang_corefunc.html](lang_corefunc.md) [lang_corefunc.html#unistr_quote](lang_corefunc.md#unistr_quote) [printf.html#percentq](printf.md#percentq) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- unistr SQL function → [printf.html#alt1](printf.md#alt1)
- unistr_quote → [changes.html#version_3_50_0](changes.md#version_3_50_0) [lang_corefunc.html](lang_corefunc.md) [lang_corefunc.html#quote](lang_corefunc.md#quote) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- unixepoch → [lang_datefunc.html#subsec](lang_datefunc.md#subsec)
- unixepoch function → [changes.html#version_3_38_0](changes.md#version_3_38_0) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md)
- unixepoch modifier → [lang_datefunc.html](lang_datefunc.md) [lang_datefunc.html#tmval](lang_datefunc.md#tmval)
- unlikely → [changes.html#version_3_8_1](changes.md#version_3_8_1) [changes.html#version_3_8_8](changes.md#version_3_8_8) [lang_corefunc.html](lang_corefunc.md) [lang_corefunc.html#likelihood](lang_corefunc.md#likelihood) [lang_corefunc.html#likely](lang_corefunc.md#likely) [oldnews.html](oldnews.md) [queryplanner-ng.html#howtofix](queryplanner-ng.md#howtofix) [releaselog/3_8_1.html](releaselog/3_8_1.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md)
- unlink corruption → [errlog.html](errlog.md)
- unlinked database files → [changes.html#version_3_7_17](changes.md#version_3_7_17) [releaselog/3_7_17.html](releaselog/3_7_17.md)
- unprotected sqlite3_value → [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/result_blob.html](c3ref/result_blob.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_result_blob](capi3ref.md#sqlite3_result_blob) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob)
- untrusted database files → [appfileformat.html](appfileformat.md)
- UPDATE → [c3ref/blob_open.html](c3ref/blob_open.md) [c3ref/column_count.html](c3ref/column_count.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/total_changes.html](c3ref/total_changes.md) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [capi3ref.html#sqlite3_column_count](capi3ref.md#sqlite3_column_count) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite) [capi3ref.html#sqlite3_total_changes](capi3ref.md#sqlite3_total_changes) [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_17_0](changes.md#version_3_17_0) [changes.html#version_3_24_0](changes.md#version_3_24_0) [changes.html#version_3_26_0](changes.md#version_3_26_0) [changes.html#version_3_35_0](changes.md#version_3_35_0) [changes.html#version_3_6_4](changes.md#version_3_6_4) [changes.html#version_3_7_17](changes.md#version_3_7_17) [compile.html#enable_update_delete_limit](compile.md#enable_update_delete_limit) [conflict.html](conflict.md) [dbpage.html](dbpage.md) [fts3.html#fts4](fts3.md#fts4) [fts5.html](fts5.md) [fullsql.html](fullsql.md) [isolation.html](isolation.md) [lang.html](lang.md) [lang_altertable.html#caution](lang_altertable.md#caution) [lang_analyze.html#statanal](lang_analyze.md#statanal) [lang_createtable.html#notnullconst](lang_createtable.md#notnullconst) [lang_createtable.html#primkeyconst](lang_createtable.md#primkeyconst) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_indexedby.html](lang_indexedby.md) [lang_returning.html](lang_returning.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [pragma.html#pragma_count_changes](pragma.md#pragma_count_changes) [pragma.html#pragma_writable_schema](pragma.md#pragma_writable_schema) [rbu.html](rbu.md) [rbu.html#rbu_updates](rbu.md#rbu_updates) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_17_0.html](releaselog/3_17_0.md) [releaselog/3_24_0.html](releaselog/3_24_0.md) [releaselog/3_26_0.html](releaselog/3_26_0.md) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [releaselog/3_6_4.html](releaselog/3_6_4.md) [releaselog/3_7_17.html](releaselog/3_7_17.md) [rowvalue.html](rowvalue.md) [rowvalue.html#rvinop](rowvalue.md#rvinop) [rtree.html](rtree.md) [vtab.html](vtab.md) [vtab.html#xupdate](vtab.md#xupdate)
- UPDATE FROM → [c3ref/vtab_nochange.html](c3ref/vtab_nochange.md) [capi3ref.html#sqlite3_vtab_nochange](capi3ref.md#sqlite3_vtab_nochange) [changes.html#version_3_33_0](changes.md#version_3_33_0) [lang_returning.html](lang_returning.md) [releaselog/3_33_0.html](releaselog/3_33_0.md)
- UPDATE trigger → [rescode.html#constraint_pinned](rescode.md#constraint_pinned)
- update-stmt → [lang_createtrigger.html](lang_createtrigger.md) [lang_update.html](lang_update.md)
- update-stmt-limited → [lang_update.html#upfrom](lang_update.md#upfrom)
- upluscontrol → [lang_indexedby.html](lang_indexedby.md) [queryplanner-ng.html#howtofix](queryplanner-ng.md#howtofix)
- upper → [faq.html#q18](faq.md#q18) [lang_corefunc.html](lang_corefunc.md)
- upsert → [pragma.html#pragma_count_changes](pragma.md#pragma_count_changes)
- UPSERT → [changes.html#version_3_24_0](changes.md#version_3_24_0) [changes.html#version_3_35_0](changes.md#version_3_35_0) [changes.html#version_3_37_1](changes.md#version_3_37_1) [changes.html#version_3_45_2](changes.md#version_3_45_2) [changes.html#version_3_45_3](changes.md#version_3_45_3) [fullsql.html](fullsql.md) [lang.html](lang.md) [lang_conflict.html](lang_conflict.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [news.html](news.md) [releaselog/3_24_0.html](releaselog/3_24_0.md) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- upsert clause → [lang_insert.html](lang_insert.md)
- upsert-clause → [lang_createtrigger.html](lang_createtrigger.md) [lang_insert.html](lang_insert.md) [lang_upsert.html](lang_upsert.md)
- URI filename → [c3ref/open.html#urifilenamesinsqlite3open](c3ref/open.md#urifilenamesinsqlite3open) [c3ref/uri_boolean.html](c3ref/uri_boolean.md) [capi3ref.html#sqlite3_uri_boolean](capi3ref.md#sqlite3_uri_boolean) [capi3ref.html#urifilenamesinsqlite3open](capi3ref.md#urifilenamesinsqlite3open) [changes.html#version_3_53_0](changes.md#version_3_53_0) [compile.html#use_uri](compile.md#use_uri) [inmemorydb.html#sharedmemdb](inmemorydb.md#sharedmemdb) [lang_attach.html](lang_attach.md) [lang_vacuum.html#vacuuminto](lang_vacuum.md#vacuuminto) [psow.html#tornpage](psow.md#tornpage) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [sharedcache.html#inmemsharedcache](sharedcache.md#inmemsharedcache) [tclsqlite.html](tclsqlite.md)
- URI filename examples → [uri.html#urivfs](uri.md#urivfs)
- URI filenames → [c3ref/open.html#urifilenamesinsqlite3open](c3ref/open.md#urifilenamesinsqlite3open) [capi3ref.html#urifilenamesinsqlite3open](capi3ref.md#urifilenamesinsqlite3open) [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_7_10](changes.md#version_3_7_10) [changes.html#version_3_7_13](changes.md#version_3_7_13) [changes.html#version_3_7_7](changes.md#version_3_7_7) [compile.html#allow_uri_authority](compile.md#allow_uri_authority) [compile.html#enable_8_3_names](compile.md#enable_8_3_names) [inmemorydb.html](inmemorydb.md) [oldnews.html](oldnews.md) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_7_10.html](releaselog/3_7_10.md) [releaselog/3_7_13.html](releaselog/3_7_13.md) [releaselog/3_7_7.html](releaselog/3_7_7.md) [sharedcache.html#dontuse](sharedcache.md#dontuse) [shortnames.html](shortnames.md) [tclsqlite.html](tclsqlite.md) [vfs.html](vfs.md)
- URI filenames in sqlite3_open → [uri.html#urivfs](uri.md#urivfs)
- URI query parameters → [changes.html#version_3_8_5](changes.md#version_3_8_5) [releaselog/3_8_5.html](releaselog/3_8_5.md)
- use of shared cache mode is discouraged → [c3ref/enable_shared_cache.html](c3ref/enable_shared_cache.md) [c3ref/open.html](c3ref/open.md) [capi3ref.html#sqlite3_enable_shared_cache](capi3ref.md#sqlite3_enable_shared_cache) [capi3ref.html#sqlite3_open](capi3ref.md#sqlite3_open)
- user-defined window functions → [c3ref/create_function.html](c3ref/create_function.md) [capi3ref.html#sqlite3_create_function](capi3ref.md#sqlite3_create_function) [windowfunctions.html#aggwinfunc](windowfunctions.md#aggwinfunc)
- user_version → [compile.html#omit_schema_version_pragmas](compile.md#omit_schema_version_pragmas)
- user_version pragma → [fileformat2.html#database_header](fileformat2.md#database_header) [fileformat2.html#enc](fileformat2.md#enc) [pragma.html#pragma_application_id](pragma.md#pragma_application_id) [pragma.html#pragma_schema_version](pragma.md#pragma_schema_version)
- using SQLite for websites → [np1queryprob.html](np1queryprob.md)
- Using the SQLite Online Backup API → [c3ref/backup.html](c3ref/backup.md) [c3ref/backup_finish.html](c3ref/backup_finish.md) [capi3ref.html#sqlite3_backup](capi3ref.md#sqlite3_backup) [capi3ref.html#sqlite3_backup_finish](capi3ref.md#sqlite3_backup_finish)
- Using the SQLite Unlock Notification Feature → [c3ref/unlock_notify.html](c3ref/unlock_notify.md) [capi3ref.html#sqlite3_unlock_notify](capi3ref.md#sqlite3_unlock_notify) [compile.html#enable_unlock_notify](compile.md#enable_unlock_notify)
- utc and localtime modifiers → [changes.html#version_3_46_0](changes.md#version_3_46_0) [releaselog/3_46_0.html](releaselog/3_46_0.md) [releaselog/3_46_1.html](releaselog/3_46_1.md)
- utc modifier → [changes.html#version_3_10_0](changes.md#version_3_10_0) [deterministic.html#dtexception](deterministic.md#dtexception) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md)
- VACUUM → [c3ref/c_dbconfig_defensive.html#sqlitedbconfiglegacyfileformat](c3ref/c_dbconfig_defensive.md#sqlitedbconfiglegacyfileformat) [c3ref/c_dbconfig_defensive.html#sqlitedbconfigresetdatabase](c3ref/c_dbconfig_defensive.md#sqlitedbconfigresetdatabase) [capi3ref.html#sqlitedbconfiglegacyfileformat](capi3ref.md#sqlitedbconfiglegacyfileformat) [capi3ref.html#sqlitedbconfigresetdatabase](capi3ref.md#sqlitedbconfigresetdatabase) [changes.html#version_3_15_0](changes.md#version_3_15_0) [changes.html#version_3_15_1](changes.md#version_3_15_1) [changes.html#version_3_19_0](changes.md#version_3_19_0) [changes.html#version_3_31_0](changes.md#version_3_31_0) [changes.html#version_3_35_0](changes.md#version_3_35_0) [changes.html#version_3_51_0](changes.md#version_3_51_0) [changes.html#version_3_5_8](changes.md#version_3_5_8) [changes.html#version_3_7_5](changes.md#version_3_7_5) [changes.html#version_3_7_9](changes.md#version_3_7_9) [changes.html#version_3_8_1](changes.md#version_3_8_1) [changes.html#version_3_8_10](changes.md#version_3_8_10) [changes.html#version_3_9_0](changes.md#version_3_9_0) [cli.html#sha3sum](cli.md#sha3sum) [compile.html#omit_vacuum](compile.md#omit_vacuum) [dbhash.html](dbhash.md) [dbstat.html#dbstatagg](dbstat.md#dbstatagg) [faq.html#q20](faq.md#q20) [fts3.html#\*fts4optcmd](fts3.md#*fts4optcmd) [fts3.html#fts4](fts3.md#fts4) [fullsql.html](fullsql.md) [howtocorrupt.html#cfgerr](howtocorrupt.md#cfgerr) [imposter.html](imposter.md) [lang.html](lang.md) [mmap.html](mmap.md) [oldnews.html](oldnews.md) [pragma.html#pragma_auto_vacuum](pragma.md#pragma_auto_vacuum) [pragma.html#pragma_journal_size_limit](pragma.md#pragma_journal_size_limit) [pragma.html#pragma_page_size](pragma.md#pragma_page_size) [pragma.html#pragma_schema_version](pragma.md#pragma_schema_version) [pragma.html#pragma_secure_delete](pragma.md#pragma_secure_delete) [rbu.html](rbu.md) [releaselog/3_15_0.html](releaselog/3_15_0.md) [releaselog/3_15_1.html](releaselog/3_15_1.md) [releaselog/3_15_2.html](releaselog/3_15_2.md) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [releaselog/3_35_0.html](releaselog/3_35_0.md) [releaselog/3_35_1.html](releaselog/3_35_1.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [releaselog/3_51_0.html](releaselog/3_51_0.md) [releaselog/3_51_1.html](releaselog/3_51_1.md) [releaselog/3_51_2.html](releaselog/3_51_2.md) [releaselog/3_51_3.html](releaselog/3_51_3.md) [releaselog/3_5_8.html](releaselog/3_5_8.md) [releaselog/3_7_5.html](releaselog/3_7_5.md) [releaselog/3_7_9.html](releaselog/3_7_9.md) [releaselog/3_8_1.html](releaselog/3_8_1.md) [releaselog/3_8_10.html](releaselog/3_8_10.md) [releaselog/3_8_10_1.html](releaselog/3_8_10_1.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md) [rowidtable.html](rowidtable.md) [tempfiles.html](tempfiles.md) [tempfiles.html#vacuumdb](tempfiles.md#vacuumdb) [wal.html#advantages](wal.md#advantages)
- VACUUM INTO → [backup.html](backup.md) [c3ref/backup_finish.html#sqlite3backuppagecount](c3ref/backup_finish.md#sqlite3backuppagecount) [capi3ref.html#sqlite3backuppagecount](capi3ref.md#sqlite3backuppagecount) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_28_0](changes.md#version_3_28_0) [changes.html#version_3_40_0](changes.md#version_3_40_0) [changes.html#version_3_53_0](changes.md#version_3_53_0) [howtocorrupt.html#stalefd](howtocorrupt.md#stalefd) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_28_0.html](releaselog/3_28_0.md) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- vacuum-stmt → [lang_vacuum.html](lang_vacuum.md)
- VALUES → [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#orderby](lang_select.md#orderby)
- VALUES clause → [changes.html#version_3_46_1](changes.md#version_3_46_1) [changes.html#version_3_8_3](changes.md#version_3_8_3) [changes.html#version_3_8_8](changes.md#version_3_8_8) [lang_select.html#limitoffset](lang_select.md#limitoffset) [oldnews.html](oldnews.md) [releaselog/3_46_1.html](releaselog/3_46_1.md) [releaselog/3_8_3.html](releaselog/3_8_3.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md) [unionvtab.html](unionvtab.md)
- variable-length integer → [fileformat2.html#record_format](fileformat2.md#record_format) [rowidtable.html](rowidtable.md)
- varint → [fileformat2.html#record_format](fileformat2.md#record_format)
- VDBE → [changes.html#version_3_8_6](changes.md#version_3_8_6) [compile.html#debug](compile.md#debug) [releaselog/3_8_6.html](releaselog/3_8_6.md)
- vdbe_trace → [debugging.html](debugging.md) [opcode.html#subprog](opcode.md#subprog)
- Version 3.0.0 → [lockingv3.html](lockingv3.md)
- version 3.0.0 → [chronology.html](chronology.md) [fileformat2.html#schemaformat](fileformat2.md#schemaformat)
- version 3.0.1 → [chronology.html](chronology.md)
- version 3.0.2 → [chronology.html](chronology.md)
- version 3.0.3 → [chronology.html](chronology.md)
- version 3.0.4 → [chronology.html](chronology.md)
- version 3.0.5 → [chronology.html](chronology.md)
- version 3.0.6 → [chronology.html](chronology.md)
- version 3.0.7 → [chronology.html](chronology.md)
- version 3.0.8 → [chronology.html](chronology.md)
- version 3.1.0 → [chronology.html](chronology.md)
- version 3.1.1 → [chronology.html](chronology.md)
- version 3.1.2 → [chronology.html](chronology.md)
- version 3.1.3 → [chronology.html](chronology.md) [fileformat2.html#schemaformat](fileformat2.md#schemaformat)
- version 3.1.4 → [chronology.html](chronology.md) [fileformat2.html#schemaformat](fileformat2.md#schemaformat)
- version 3.1.5 → [chronology.html](chronology.md)
- version 3.1.6 → [chronology.html](chronology.md)
- version 3.10.0 → [chronology.html](chronology.md) [howtocorrupt.html#alias](howtocorrupt.md#alias) [news.html](news.md) [vtab.html#colUsed](vtab.md#colUsed)
- version 3.10.1 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.10.2 → [chronology.html](chronology.md)
- version 3.11.0 → [chronology.html](chronology.md) [fts3.html#f3tknzr](fts3.md#f3tknzr) [news.html](news.md) [wal.html#advantages](wal.md#advantages) [wal.html#bigwal](wal.md#bigwal)
- Version 3.11.0 → [compile.html#enable_fts3_tokenizer](compile.md#enable_fts3_tokenizer)
- version 3.11.1 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.12.0 → [changes.html#version_3_14](changes.md#version_3_14) [chronology.html](chronology.md) [news.html](news.md) [pgszchng2016.html](pgszchng2016.md) [pragma.html#pragma_page_size](pragma.md#pragma_page_size) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md)
- Version 3.12.0 → [compile.html#enable_fts3_tokenizer](compile.md#enable_fts3_tokenizer)
- version 3.12.0 page size change → [changes.html#version_3_12_0](changes.md#version_3_12_0) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md)
- version 3.12.1 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.12.2 → [chronology.html](chronology.md)
- version 3.13.0 → [chronology.html](chronology.md) [news.html](news.md) [sessionintro.html](sessionintro.md)
- version 3.14 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.14.0 → [vtab.html#worid](vtab.md#worid)
- version 3.14.1 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.14.2 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.15.0 → [chronology.html](chronology.md) [lang_update.html](lang_update.md) [lang_vacuum.html](lang_vacuum.md) [news.html](news.md) [rowvalue.html#rvinop](rowvalue.md#rvinop) [uri.html#coreqp](uri.md#coreqp)
- version 3.15.1 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.15.2 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.16.0 → [changes.html#version_3_18_1](changes.md#version_3_18_1) [changes.html#version_3_19_3](changes.md#version_3_19_3) [chronology.html](chronology.md) [news.html](news.md) [releaselog/3_18_1.html](releaselog/3_18_1.md) [releaselog/3_18_2.html](releaselog/3_18_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md)
- version 3.16.1 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.16.2 → [chronology.html](chronology.md)
- version 3.17.0 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.18.0 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.18.1 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.18.2 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.19.0 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.19.1 → [chronology.html](chronology.md)
- version 3.19.2 → [chronology.html](chronology.md)
- version 3.19.3 → [chronology.html](chronology.md) [news.html](news.md)
- Version 3.19.3 → [news.html](news.md)
- version 3.2.0 → [chronology.html](chronology.md)
- version 3.2.1 → [chronology.html](chronology.md)
- version 3.2.2 → [chronology.html](chronology.md)
- version 3.2.3 → [chronology.html](chronology.md)
- version 3.2.4 → [chronology.html](chronology.md)
- version 3.2.5 → [chronology.html](chronology.md)
- version 3.2.6 → [chronology.html](chronology.md)
- version 3.2.7 → [chronology.html](chronology.md)
- version 3.2.8 → [chronology.html](chronology.md)
- version 3.20.0 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.20.1 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.21.0 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.22.0 → [chronology.html](chronology.md) [news.html](news.md) [sqlar.html#cltools](sqlar.md#cltools) [wal.html#advantages](wal.md#advantages) [wal.html#readonly](wal.md#readonly)
- version 3.23.0 → [chronology.html](chronology.md) [news.html](news.md) [quirks.html](quirks.md) [sqlar.html#cltools](sqlar.md#cltools)
- version 3.23.1 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.24.0 → [c3ref/c_dbconfig_defensive.html#sqlitedbconfiglegacyaltertable](c3ref/c_dbconfig_defensive.md#sqlitedbconfiglegacyaltertable) [capi3ref.html#sqlitedbconfiglegacyaltertable](capi3ref.md#sqlitedbconfiglegacyaltertable) [changes.html#version_3_45_3](changes.md#version_3_45_3) [chronology.html](chronology.md) [news.html](news.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- version 3.25.0 → [chronology.html](chronology.md) [news.html](news.md) [windowfunctions.html#udfwinfunc](windowfunctions.md#udfwinfunc)
- version 3.25.1 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.25.2 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.25.3 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.26.0 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.27.0 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.27.1 → [chronology.html](chronology.md)
- version 3.27.2 → [chronology.html](chronology.md)
- version 3.28.0 → [chronology.html](chronology.md) [news.html](news.md) [windowfunctions.html#udfwinfunc](windowfunctions.md#udfwinfunc)
- version 3.29.0 → [chronology.html](chronology.md) [compile.html#enable_stat3](compile.md#enable_stat3) [news.html](news.md) [testing.html#aflfuzz](testing.md#aflfuzz)
- version 3.3.0 → [chronology.html](chronology.md) [sharedcache.html#sqlite_shared_cache_mode](sharedcache.md#sqlite_shared_cache_mode)
- version 3.3.1 → [chronology.html](chronology.md)
- version 3.3.10 → [chronology.html](chronology.md)
- version 3.3.11 → [chronology.html](chronology.md)
- version 3.3.12 → [chronology.html](chronology.md)
- version 3.3.13 → [chronology.html](chronology.md)
- version 3.3.14 → [chronology.html](chronology.md)
- Version 3.3.14 → [changes.html#version_3_3_16](changes.md#version_3_3_16) [releaselog/3_3_16.html](releaselog/3_3_16.md)
- version 3.3.15 → [chronology.html](chronology.md)
- Version 3.3.15 → [changes.html#version_3_3_16](changes.md#version_3_3_16) [releaselog/3_3_16.html](releaselog/3_3_16.md)
- version 3.3.16 → [chronology.html](chronology.md)
- version 3.3.17 → [chronology.html](chronology.md)
- version 3.3.2 → [chronology.html](chronology.md)
- version 3.3.3 → [chronology.html](chronology.md)
- version 3.3.4 → [chronology.html](chronology.md)
- version 3.3.5 → [chronology.html](chronology.md)
- version 3.3.6 → [chronology.html](chronology.md)
- version 3.3.7 → [chronology.html](chronology.md)
- version 3.3.8 → [chronology.html](chronology.md)
- version 3.3.9 → [changes.html#version_3_8_11](changes.md#version_3_8_11) [chronology.html](chronology.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md)
- version 3.30.0 → [chronology.html](chronology.md) [news.html](news.md) [pragma.html#pragma_index_info](pragma.md#pragma_index_info) [pragma.html#pragma_index_xinfo](pragma.md#pragma_index_xinfo)
- version 3.30.1 → [chronology.html](chronology.md)
- version 3.31.0 → [c3ref/uri_boolean.html](c3ref/uri_boolean.md) [capi3ref.html#sqlite3_uri_boolean](capi3ref.md#sqlite3_uri_boolean) [chronology.html](chronology.md) [cves.html#cvetab](cves.md#cvetab) [news.html](news.md)
- version 3.31.1 → [chronology.html](chronology.md)
- version 3.32.0 → [chronology.html](chronology.md) [cves.html#cvetab](cves.md#cvetab) [news.html](news.md)
- version 3.32.1 → [chronology.html](chronology.md) [cves.html#cvetab](cves.md#cvetab)
- version 3.32.2 → [chronology.html](chronology.md)
- version 3.32.3 → [chronology.html](chronology.md) [cves.html#cvetab](cves.md#cvetab)
- version 3.33.0 → [chronology.html](chronology.md)
- version 3.34.0 → [chronology.html](chronology.md) [cves.html#cvetab](cves.md#cvetab) [lang_with.html#recursivecte](lang_with.md#recursivecte)
- version 3.34.1 → [chronology.html](chronology.md) [cves.html#cvetab](cves.md#cvetab)
- version 3.35.0 → [changes.html#version_3_36_0](changes.md#version_3_36_0) [changes.html#version_3_37_1](changes.md#version_3_37_1) [changes.html#version_3_37_2](changes.md#version_3_37_2) [changes.html#version_3_45_2](changes.md#version_3_45_2) [chronology.html](chronology.md) [howtocorrupt.html#svptbug](howtocorrupt.md#svptbug) [news.html](news.md) [releaselog/3_36_0.html](releaselog/3_36_0.md) [releaselog/3_37_1.html](releaselog/3_37_1.md) [releaselog/3_37_2.html](releaselog/3_37_2.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md)
- version 3.35.1 → [chronology.html](chronology.md)
- version 3.35.2 → [chronology.html](chronology.md)
- version 3.35.3 → [chronology.html](chronology.md)
- version 3.35.4 → [chronology.html](chronology.md)
- version 3.35.5 → [chronology.html](chronology.md)
- version 3.36.0 → [chronology.html](chronology.md)
- Version 3.37.0 → [amalgamation.html](amalgamation.md)
- version 3.37.0 → [chronology.html](chronology.md)
- version 3.37.1 → [chronology.html](chronology.md)
- version 3.37.2 → [chronology.html](chronology.md) [howtocorrupt.html#svptbug](howtocorrupt.md#svptbug)
- version 3.38.0 → [chronology.html](chronology.md)
- version 3.38.1 → [chronology.html](chronology.md)
- version 3.38.2 → [chronology.html](chronology.md)
- version 3.38.3 → [chronology.html](chronology.md)
- version 3.38.4 → [chronology.html](chronology.md)
- version 3.38.5 → [chronology.html](chronology.md)
- version 3.39.0 → [chronology.html](chronology.md)
- version 3.39.1 → [chronology.html](chronology.md)
- version 3.39.2 → [chronology.html](chronology.md) [cves.html#cvetab](cves.md#cvetab)
- version 3.39.3 → [chronology.html](chronology.md)
- version 3.39.4 → [chronology.html](chronology.md)
- version 3.4.0 → [chronology.html](chronology.md)
- version 3.4.1 → [chronology.html](chronology.md)
- version 3.4.2 → [chronology.html](chronology.md)
- version 3.40.0 → [changes.html#version_3_44_0](changes.md#version_3_44_0) [changes.html#version_3_49_2](changes.md#version_3_49_2) [chronology.html](chronology.md) [news.html](news.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md) [releaselog/3_49_2.html](releaselog/3_49_2.md)
- version 3.40.1 → [chronology.html](chronology.md)
- version 3.41.0 → [chronology.html](chronology.md)
- version 3.41.1 → [chronology.html](chronology.md)
- version 3.41.2 → [chronology.html](chronology.md)
- version 3.42.0 → [chronology.html](chronology.md) [cves.html#cvetab](cves.md#cvetab) [testing.html](testing.md)
- version 3.43.0 → [chronology.html](chronology.md)
- version 3.43.1 → [chronology.html](chronology.md) [cves.html#cvetab](cves.md#cvetab)
- version 3.43.2 → [chronology.html](chronology.md) [cves.html#cvetab](cves.md#cvetab)
- version 3.44.0 → [changes.html#version_3_45_1](changes.md#version_3_45_1) [changes.html#version_3_49_1](changes.md#version_3_49_1) [chronology.html](chronology.md) [releaselog/3_45_1.html](releaselog/3_45_1.md) [releaselog/3_45_2.html](releaselog/3_45_2.md) [releaselog/3_45_3.html](releaselog/3_45_3.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md)
- version 3.44.1 → [chronology.html](chronology.md)
- version 3.44.2 → [chronology.html](chronology.md)
- version 3.45.0 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.45.1 → [chronology.html](chronology.md)
- version 3.45.2 → [chronology.html](chronology.md)
- version 3.45.3 → [chronology.html](chronology.md)
- version 3.46.0 → [chronology.html](chronology.md)
- version 3.46.1 → [chronology.html](chronology.md)
- version 3.47.0 → [chronology.html](chronology.md)
- Version 3.47.0 → [news.html](news.md)
- version 3.47.1 → [chronology.html](chronology.md)
- version 3.47.2 → [chronology.html](chronology.md)
- version 3.48.0 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.49.0 → [chronology.html](chronology.md) [news.html](news.md)
- Version 3.49.0 → [changes.html#version_3_50_0](changes.md#version_3_50_0) [releaselog/3_50_0.html](releaselog/3_50_0.md) [releaselog/3_50_1.html](releaselog/3_50_1.md) [releaselog/3_50_2.html](releaselog/3_50_2.md) [releaselog/3_50_3.html](releaselog/3_50_3.md) [releaselog/3_50_4.html](releaselog/3_50_4.md)
- version 3.49.1 → [chronology.html](chronology.md) [cves.html#cvetab](cves.md#cvetab)
- version 3.49.2 → [chronology.html](chronology.md)
- version 3.5.0 → [35to36.html](35to36.md) [c3ref/enable_shared_cache.html](c3ref/enable_shared_cache.md) [c3ref/vfs.html](c3ref/vfs.md) [capi3ref.html#sqlite3_enable_shared_cache](capi3ref.md#sqlite3_enable_shared_cache) [capi3ref.html#sqlite3_vfs](capi3ref.md#sqlite3_vfs) [chronology.html](chronology.md) [custombuild.html](custombuild.md) [fts3.html#fts4](fts3.md#fts4) [sharedcache.html#dontuse](sharedcache.md#dontuse) [sharedcache.html#sqlite_shared_cache_mode](sharedcache.md#sqlite_shared_cache_mode)
- version 3.5.1 → [chronology.html](chronology.md)
- version 3.5.2 → [chronology.html](chronology.md)
- version 3.5.3 → [chronology.html](chronology.md)
- version 3.5.4 → [chronology.html](chronology.md) [tempfiles.html#views](tempfiles.md#views)
- version 3.5.5 → [chronology.html](chronology.md)
- version 3.5.6 → [chronology.html](chronology.md)
- version 3.5.7 → [chronology.html](chronology.md)
- version 3.5.8 → [changes.html#version_3_5_9](changes.md#version_3_5_9) [chronology.html](chronology.md) [releaselog/3_5_9.html](releaselog/3_5_9.md)
- version 3.5.9 → [c3ref/vfs.html](c3ref/vfs.md) [capi3ref.html#sqlite3_vfs](capi3ref.md#sqlite3_vfs) [chronology.html](chronology.md)
- version 3.50.0 → [chronology.html](chronology.md)
- version 3.50.1 → [chronology.html](chronology.md)
- version 3.50.2 → [chronology.html](chronology.md) [cves.html#cvetab](cves.md#cvetab)
- version 3.50.3 → [chronology.html](chronology.md) [cves.html#cvetab](cves.md#cvetab)
- version 3.50.4 → [chronology.html](chronology.md)
- version 3.51.0 → [chronology.html](chronology.md) [news.html](news.md)
- version 3.51.1 → [chronology.html](chronology.md)
- version 3.51.2 → [chronology.html](chronology.md)
- version 3.51.3 → [chronology.html](chronology.md)
- version 3.52.0 → [chronology.html](chronology.md) [climode.html](climode.md) [cves.html#cvetab](cves.md#cvetab) [news.html](news.md) [tclsqlite.html#format](tclsqlite.md#format)
- version 3.53.0 → [changes.html#version_3_52_0](changes.md#version_3_52_0) [chronology.html](chronology.md) [news.html](news.md) [releaselog/3_52_0.html](releaselog/3_52_0.md)
- version 3.53.1 → [chronology.html](chronology.md)
- version 3.53.2 → [chronology.html](chronology.md) [cves.html#cvetab](cves.md#cvetab)
- version 3.53.3 → [chronology.html](chronology.md)
- version 3.53.4 → [chronology.html](chronology.md)
- version 3.6.0 → [c3ref/vfs.html](c3ref/vfs.md) [capi3ref.html#sqlite3_vfs](capi3ref.md#sqlite3_vfs) [chronology.html](chronology.md)
- version 3.6.1 → [chronology.html](chronology.md) [malloc.html#lookaside](malloc.md#lookaside) [malloc.html#memstatus](malloc.md#memstatus)
- version 3.6.10 → [chronology.html](chronology.md)
- version 3.6.11 → [chronology.html](chronology.md)
- version 3.6.12 → [changes.html#version_3_6_13](changes.md#version_3_6_13) [chronology.html](chronology.md) [releaselog/3_6_13.html](releaselog/3_6_13.md)
- version 3.6.13 → [chronology.html](chronology.md)
- version 3.6.14 → [changes.html#version_3_6_14_2](changes.md#version_3_6_14_2) [chronology.html](chronology.md) [oldnews.html](oldnews.md) [releaselog/3_6_14_2.html](releaselog/3_6_14_2.md)
- version 3.6.14.1 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.6.14.2 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.6.15 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.6.16 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.6.16.1 → [chronology.html](chronology.md)
- version 3.6.17 → [chronology.html](chronology.md) [sharedcache.html#dontuse](sharedcache.md#dontuse) [th3.html](th3.md) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab)
- version 3.6.18 → [c3ref/c_scm_branch.html](c3ref/c_scm_branch.md) [capi3ref.html#SQLITE_SCM_BRANCH](capi3ref.md#SQLITE_SCM_BRANCH) [chronology.html](chronology.md) [limits.html#max_trigger_depth](limits.md#max_trigger_depth) [pragma.html#pragma_recursive_triggers](pragma.md#pragma_recursive_triggers)
- version 3.6.19 → [chronology.html](chronology.md) [faq.html#q22](faq.md#q22) [foreignkeys.html](foreignkeys.md) [foreignkeys.html#fk_enable](foreignkeys.md#fk_enable) [oldnews.html](oldnews.md) [pragma.html#pragma_foreign_keys](pragma.md#pragma_foreign_keys) [quirks.html](quirks.md)
- version 3.6.2 → [chronology.html](chronology.md)
- version 3.6.20 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.6.21 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.6.22 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.6.23 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.6.23.1 → [c3ref/step.html](c3ref/step.md) [capi3ref.html#sqlite3_step](capi3ref.md#sqlite3_step) [chronology.html](chronology.md) [compile.html#omit_autoreset](compile.md#omit_autoreset) [oldnews.html](oldnews.md)
- version 3.6.3 → [chronology.html](chronology.md)
- version 3.6.4 → [atomiccommit.html#safeappend](atomiccommit.md#safeappend) [changes.html#version_3_6_6_1](changes.md#version_3_6_6_1) [chronology.html](chronology.md) [oldnews.html](oldnews.md) [releaselog/3_6_6_1.html](releaselog/3_6_6_1.md)
- version 3.6.5 → [chronology.html](chronology.md) [lang_delete.html#truncateopt](lang_delete.md#truncateopt) [oldnews.html](oldnews.md)
- version 3.6.6 → [changes.html#version_3_6_6_2](changes.md#version_3_6_6_2) [chronology.html](chronology.md) [oldnews.html](oldnews.md) [releaselog/3_6_6_2.html](releaselog/3_6_6_2.md)
- version 3.6.6.1 → [chronology.html](chronology.md)
- version 3.6.6.2 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.6.7 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.6.8 → [chronology.html](chronology.md)
- version 3.6.9 → [chronology.html](chronology.md)
- version 3.7.0 → [c3ref/vfs.html](c3ref/vfs.md) [capi3ref.html#sqlite3_vfs](capi3ref.md#sqlite3_vfs) [chronology.html](chronology.md) [fileformat2.html#walformat](fileformat2.md#walformat) [howtocorrupt.html#fakeusb](howtocorrupt.md#fakeusb) [isolation.html](isolation.md) [oldnews.html](oldnews.md) [pragma.html#pragma_journal_mode](pragma.md#pragma_journal_mode) [wal.html](wal.md)
- version 3.7.0.1 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.1 → [chronology.html](chronology.md) [fileformat2.html#database_header](fileformat2.md#database_header) [oldnews.html](oldnews.md)
- version 3.7.10 → [changes.html#version_3_7_11](changes.md#version_3_7_11) [chronology.html](chronology.md) [compile.html#default_file_format](compile.md#default_file_format) [oldnews.html](oldnews.md) [pragma.html#pragma_cache_size](pragma.md#pragma_cache_size) [psow.html](psow.md) [psow.html#tornpage](psow.md#tornpage) [releaselog/3_7_11.html](releaselog/3_7_11.md)
- version 3.7.11 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.12 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.12.1 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.13 → [chronology.html](chronology.md) [fts3.html#unicode61](fts3.md#unicode61) [oldnews.html](oldnews.md) [sharedcache.html#inmemsharedcache](sharedcache.md#inmemsharedcache)
- version 3.7.14 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.14.1 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.15 → [changes.html#version_3_7_15_1](changes.md#version_3_7_15_1) [changes.html#version_3_7_15_2](changes.md#version_3_7_15_2) [changes.html#version_3_7_16_1](changes.md#version_3_7_16_1) [chronology.html](chronology.md) [oldnews.html](oldnews.md) [releaselog/3_7_15_1.html](releaselog/3_7_15_1.md) [releaselog/3_7_15_2.html](releaselog/3_7_15_2.md) [releaselog/3_7_16_1.html](releaselog/3_7_16_1.md) [releaselog/3_7_16_2.html](releaselog/3_7_16_2.md)
- version 3.7.15.1 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.15.2 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.16 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.16.1 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.16.2 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.17 → [chronology.html](chronology.md) [fts3.html#fts4aux](fts3.md#fts4aux) [howtocorrupt.html#alias](howtocorrupt.md#alias) [howtocorrupt.html#unlink](howtocorrupt.md#unlink) [mmap.html](mmap.md) [oldnews.html](oldnews.md) [pragma.html#pragma_automatic_index](pragma.md#pragma_automatic_index)
- version 3.7.2 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.3 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.4 → [chronology.html](chronology.md) [fts3.html#fts4](fts3.md#fts4) [oldnews.html](oldnews.md) [wal.html#noshm](wal.md#noshm)
- version 3.7.5 → [chronology.html](chronology.md) [compile.html#omit_autoreset](compile.md#omit_autoreset) [oldnews.html](oldnews.md)
- version 3.7.6 → [c3ref/vfs.html](c3ref/vfs.md) [capi3ref.html#sqlite3_vfs](capi3ref.md#sqlite3_vfs) [chronology.html](chronology.md) [fts3.html#fts4aux](fts3.md#fts4aux) [howtocorrupt.html#cfgerr](howtocorrupt.md#cfgerr) [oldnews.html](oldnews.md)
- version 3.7.6.1 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.6.2 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.6.3 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.7 → [chronology.html](chronology.md) [oldnews.html](oldnews.md) [uri.html](uri.md) [vtab.html#xsavepoint](vtab.md#xsavepoint)
- version 3.7.7.1 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.7.8 → [chronology.html](chronology.md) [intern-v-extern-blob.html](intern-v-extern-blob.md) [oldnews.html](oldnews.md)
- version 3.7.9 → [atomiccommit.html#hardware](atomiccommit.md#hardware) [changes.html#version_3_7_11](changes.md#version_3_7_11) [chronology.html](chronology.md) [compile.html#enable_stat2](compile.md#enable_stat2) [oldnews.html](oldnews.md) [psow.html](psow.md) [releaselog/3_7_11.html](releaselog/3_7_11.md)
- version 3.8.0 → [changes.html#version_3_8_11](changes.md#version_3_8_11) [changes.html#version_3_8_7](changes.md#version_3_8_7) [chronology.html](chronology.md) [oldnews.html](oldnews.md) [optoverview.html#autoindex](optoverview.md#autoindex) [partialindex.html](partialindex.md) [queryplanner-ng.html](queryplanner-ng.md) [queryplanner-ng.html#qpstab](queryplanner-ng.md#qpstab) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- version 3.8.0.1 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.8.0.2 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.8.1 → [chronology.html](chronology.md) [compile.html#enable_stat3](compile.md#enable_stat3) [howtocorrupt.html#stalefd](howtocorrupt.md#stalefd) [oldnews.html](oldnews.md)
- version 3.8.10 → [chronology.html](chronology.md) [testing.html#aflfuzz](testing.md#aflfuzz)
- version 3.8.10.1 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.8.10.2 → [chronology.html](chronology.md)
- version 3.8.11 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.8.11.1 → [chronology.html](chronology.md) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab)
- version 3.8.2 → [c3ref/index_info.html](c3ref/index_info.md) [capi3ref.html#sqlite3_index_info](capi3ref.md#sqlite3_index_info) [chronology.html](chronology.md) [lang_createtable.html#rowid](lang_createtable.md#rowid) [oldnews.html](oldnews.md) [withoutrowid.html](withoutrowid.md)
- version 3.8.3 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.8.3.1 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.8.4 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.8.4.1 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- Version 3.8.4.2 → [oldnews.html](oldnews.md)
- version 3.8.4.2 → [chronology.html](chronology.md)
- version 3.8.4.3 → [chronology.html](chronology.md)
- version 3.8.5 → [chronology.html](chronology.md) [oldnews.html](oldnews.md) [rtree.html#customquery](rtree.md#customquery)
- version 3.8.6 → [chronology.html](chronology.md) [datatype3.html#affinity](datatype3.md#affinity) [oldnews.html](oldnews.md)
- version 3.8.7 → [changes.html#version_3_8_10_2](changes.md#version_3_8_10_2) [chronology.html](chronology.md) [oldnews.html](oldnews.md) [releaselog/3_8_10_2.html](releaselog/3_8_10_2.md)
- version 3.8.7.1 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.8.7.2 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.8.7.3 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.8.7.4 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.8.8 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.8.8.1 → [chronology.html](chronology.md)
- version 3.8.8.2 → [chronology.html](chronology.md)
- version 3.8.8.3 → [chronology.html](chronology.md)
- version 3.8.9 → [chronology.html](chronology.md)
- version 3.9.0 → [c3ref/index_info.html](c3ref/index_info.md) [capi3ref.html#sqlite3_index_info](capi3ref.md#sqlite3_index_info) [changes.html#version_3_12_2](changes.md#version_3_12_2) [changes.html#version_3_13_0](changes.md#version_3_13_0) [chronology.html](chronology.md) [expridx.html](expridx.md) [fts5.html#compiling_and_using_fts5](fts5.md#compiling_and_using_fts5) [lang_createindex.html#indexexpr](lang_createindex.md#indexexpr) [oldnews.html](oldnews.md) [rbu.html#sqldiff](rbu.md#sqldiff) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_13_0.html](releaselog/3_13_0.md) [versionnumbers.html](versionnumbers.md) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab)
- version 3.9.1 → [chronology.html](chronology.md) [oldnews.html](oldnews.md)
- version 3.9.2 → [changes.html#version_3_9_3](changes.md#version_3_9_3) [chronology.html](chronology.md) [oldnews.html](oldnews.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- version 3.9.3 → [chronology.html](chronology.md)
- version numbering conventions → [changes.html#version_3_9_0](changes.md#version_3_9_0) [qmplan.html](qmplan.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- version-valid-for number → [fileformat2.html#database_header](fileformat2.md#database_header) [fileformat2.html#filesize](fileformat2.md#filesize) [rsync.html#intro](rsync.md#intro)
- VFS → [arch.html](arch.md) [atomiccommit.html#hardware](atomiccommit.md#hardware) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlwin32avretry](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlwin32avretry) [c3ref/database_file_object.html](c3ref/database_file_object.md) [c3ref/db_filename.html](c3ref/db_filename.md) [c3ref/filename.html](c3ref/filename.md) [c3ref/filename_database.html](c3ref/filename_database.md) [c3ref/free.html](c3ref/free.md) [c3ref/open.html#coreuriqueryparameters](c3ref/open.md#coreuriqueryparameters) [c3ref/uri_boolean.html](c3ref/uri_boolean.md) [c3ref/vfs.html](c3ref/vfs.md) [capi3ref.html#coreuriqueryparameters](capi3ref.md#coreuriqueryparameters) [capi3ref.html#sqlite3_database_file_object](capi3ref.md#sqlite3_database_file_object) [capi3ref.html#sqlite3_db_filename](capi3ref.md#sqlite3_db_filename) [capi3ref.html#sqlite3_filename](capi3ref.md#sqlite3_filename) [capi3ref.html#sqlite3_filename_database](capi3ref.md#sqlite3_filename_database) [capi3ref.html#sqlite3_free](capi3ref.md#sqlite3_free) [capi3ref.html#sqlite3_uri_boolean](capi3ref.md#sqlite3_uri_boolean) [capi3ref.html#sqlite3_vfs](capi3ref.md#sqlite3_vfs) [capi3ref.html#sqlitefcntlwin32avretry](capi3ref.md#sqlitefcntlwin32avretry) [changes.html#version_3_25_0](changes.md#version_3_25_0) [changes.html#version_3_35_3](changes.md#version_3_35_3) [changes.html#version_3_43_0](changes.md#version_3_43_0) [changes.html#version_3_7_10](changes.md#version_3_7_10) [changes.html#version_3_7_11](changes.md#version_3_7_11) [changes.html#version_3_7_12](changes.md#version_3_7_12) [changes.html#version_3_7_14](changes.md#version_3_7_14) [changes.html#version_3_7_15](changes.md#version_3_7_15) [changes.html#version_3_7_17](changes.md#version_3_7_17) [changes.html#version_3_8_11](changes.md#version_3_8_11) [changes.html#version_3_8_5](changes.md#version_3_8_5) [cli.html#arinsup](cli.md#arinsup) [compile.html#enable_locking_style](compile.md#enable_locking_style) [compile.html#fdatasync](compile.md#fdatasync) [compile.html#minimum_file_descriptor](compile.md#minimum_file_descriptor) [fileformat2.html#lockbyte](fileformat2.md#lockbyte) [loadext.html#statext](loadext.md#statext) [oldnews.html](oldnews.md) [pragma.html](pragma.md) [pragma.html#pragma_synchronous](pragma.md#pragma_synchronous) [psow.html](psow.md) [psow.html#tornpage](psow.md#tornpage) [releaselog/3_25_0.html](releaselog/3_25_0.md) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md) [releaselog/3_7_10.html](releaselog/3_7_10.md) [releaselog/3_7_11.html](releaselog/3_7_11.md) [releaselog/3_7_12.html](releaselog/3_7_12.md) [releaselog/3_7_14.html](releaselog/3_7_14.md) [releaselog/3_7_15.html](releaselog/3_7_15.md) [releaselog/3_7_17.html](releaselog/3_7_17.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [releaselog/3_8_5.html](releaselog/3_8_5.md) [rescode.html#cantopen_convpath](rescode.md#cantopen_convpath) [rescode.html#ioerr_convpath](rescode.md#ioerr_convpath) [rescode.html#ioerr_dir_fsync](rescode.md#ioerr_dir_fsync) [rescode.html#ioerr_fstat](rescode.md#ioerr_fstat) [rescode.html#ioerr_fsync](rescode.md#ioerr_fsync) [rescode.html#ioerr_gettemppath](rescode.md#ioerr_gettemppath) [rescode.html#ioerr_nomem](rescode.md#ioerr_nomem) [rescode.html#ioerr_read](rescode.md#ioerr_read) [rescode.html#ioerr_short_read](rescode.md#ioerr_short_read) [rescode.html#ioerr_truncate](rescode.md#ioerr_truncate) [rescode.html#ioerr_write](rescode.md#ioerr_write) [rescode.html#notfound](rescode.md#notfound) [rescode.html#readonly_cantinit](rescode.md#readonly_cantinit) [selfcontained.html](selfcontained.md) [tclsqlite.html](tclsqlite.md) [tempfiles.html#shmfile](tempfiles.md#shmfile) [tempfiles.html#tempdir](tempfiles.md#tempdir) [testing.html#coverage](testing.md#coverage) [testing.html#crashtesting](testing.md#crashtesting) [uri.html](uri.md) [uri.html#coreqp](uri.md#coreqp) [uri.html#urivfs](uri.md#urivfs) [wal.html#bigwal](wal.md#bigwal) [wal.html#fast](wal.md#fast) [walformat.html](walformat.md)
- VFS shim → [c3ref/create_filename.html](c3ref/create_filename.md) [capi3ref.html#sqlite3_create_filename](capi3ref.md#sqlite3_create_filename) [changes.html#version_3_22_0](changes.md#version_3_22_0) [changes.html#version_3_32_0](changes.md#version_3_32_0) [cksumvfs.html](cksumvfs.md) [releaselog/3_22_0.html](releaselog/3_22_0.md) [releaselog/3_32_0.html](releaselog/3_32_0.md) [releaselog/3_32_1.html](releaselog/3_32_1.md) [releaselog/3_32_2.html](releaselog/3_32_2.md) [releaselog/3_32_3.html](releaselog/3_32_3.md) [vtablist.html](vtablist.md)
- VFSes → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlvfsname](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlvfsname) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlvfspointer](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlvfspointer) [c3ref/open.html#coreuriqueryparameters](c3ref/open.md#coreuriqueryparameters) [capi3ref.html#coreuriqueryparameters](capi3ref.md#coreuriqueryparameters) [capi3ref.html#sqlitefcntlvfsname](capi3ref.md#sqlitefcntlvfsname) [capi3ref.html#sqlitefcntlvfspointer](capi3ref.md#sqlitefcntlvfspointer) [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_7_10](changes.md#version_3_7_10) [cintro.html](cintro.md) [cli.html#dotload](cli.md#dotload) [compile.html#powersafe_overwrite](compile.md#powersafe_overwrite) [loadext.html](loadext.md) [loadext.html#persist](loadext.md#persist) [oldnews.html](oldnews.md) [psow.html](psow.md) [psow.html#tornpage](psow.md#tornpage) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_7_10.html](releaselog/3_7_10.md) [rescode.html#internal](rescode.md#internal) [rescode.html#ioerr_lock](rescode.md#ioerr_lock) [rescode.html#ok_load_permanently](rescode.md#ok_load_permanently) [uri.html#uripsow](uri.md#uripsow) [wal.html#noshm](wal.md#noshm) [walformat.html](walformat.md)
- view → [changes.html#version_3_7_15](changes.md#version_3_7_15) [changes.html#version_3_8_7](changes.md#version_3_8_7) [lang_with.html#ordinarycte](lang_with.md#ordinarycte) [news.html](news.md) [oldnews.html](oldnews.md) [releaselog/3_7_15.html](releaselog/3_7_15.md) [releaselog/3_8_7.html](releaselog/3_8_7.md)
- VIEW → [changes.html#version_3_9_0](changes.md#version_3_9_0) [datatype3.html#affcompoundview](datatype3.md#affcompoundview) [datatype3.html#affview](datatype3.md#affview) [datatype3.html#expraff](datatype3.md#expraff) [pragma.html#pragfunc](pragma.md#pragfunc) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- views → [changes.html#version_3_12_1](changes.md#version_3_12_1) [changes.html#version_3_13_0](changes.md#version_3_13_0) [changes.html#version_3_17_0](changes.md#version_3_17_0) [changes.html#version_3_25_0](changes.md#version_3_25_0) [lang_with.html](lang_with.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_17_0.html](releaselog/3_17_0.md) [releaselog/3_25_0.html](releaselog/3_25_0.md) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md)
- VIRTUAL generated column → [expridx.html](expridx.md) [howtocorrupt.html#cfgerr](howtocorrupt.md#cfgerr) [staleexpridx.html](staleexpridx.md)
- virtual machine → [compile.html#enable_offset_sql_func](compile.md#enable_offset_sql_func)
- virtual machine instructions → [c3ref/progress_handler.html](c3ref/progress_handler.md) [capi3ref.html#sqlite3_progress_handler](capi3ref.md#sqlite3_progress_handler) [lang_explain.html](lang_explain.md) [vdbe.html](vdbe.md)
- virtual table → [c3ref/c_fail.html](c3ref/c_fail.md) [c3ref/c_index_constraint_eq.html](c3ref/c_index_constraint_eq.md) [c3ref/c_vtab_constraint_support.html](c3ref/c_vtab_constraint_support.md) [c3ref/c_vtab_constraint_support.html#sqlitevtabconstraintsupport](c3ref/c_vtab_constraint_support.md#sqlitevtabconstraintsupport) [c3ref/c_vtab_constraint_support.html#sqlitevtabdirectonly](c3ref/c_vtab_constraint_support.md#sqlitevtabdirectonly) [c3ref/c_vtab_constraint_support.html#sqlitevtabinnocuous](c3ref/c_vtab_constraint_support.md#sqlitevtabinnocuous) [c3ref/c_vtab_constraint_support.html#sqlitevtabusesallschemas](c3ref/c_vtab_constraint_support.md#sqlitevtabusesallschemas) [c3ref/create_module.html](c3ref/create_module.md) [c3ref/index_info.html](c3ref/index_info.md) [c3ref/last_insert_rowid.html](c3ref/last_insert_rowid.md) [c3ref/module.html](c3ref/module.md) [c3ref/overload_function.html](c3ref/overload_function.md) [c3ref/value_blob.html](c3ref/value_blob.md) [c3ref/vtab.html](c3ref/vtab.md) [c3ref/vtab_collation.html](c3ref/vtab_collation.md) [c3ref/vtab_config.html](c3ref/vtab_config.md) [c3ref/vtab_cursor.html](c3ref/vtab_cursor.md) [c3ref/vtab_distinct.html](c3ref/vtab_distinct.md) [c3ref/vtab_in.html](c3ref/vtab_in.md) [c3ref/vtab_in_first.html](c3ref/vtab_in_first.md) [c3ref/vtab_nochange.html](c3ref/vtab_nochange.md) [c3ref/vtab_on_conflict.html](c3ref/vtab_on_conflict.md) [c3ref/vtab_rhs_value.html](c3ref/vtab_rhs_value.md) [capi3ref.html#SQLITE_FAIL](capi3ref.md#SQLITE_FAIL) [capi3ref.html#SQLITE_INDEX_CONSTRAINT_EQ](capi3ref.md#SQLITE_INDEX_CONSTRAINT_EQ) [capi3ref.html#SQLITE_VTAB_CONSTRAINT_SUPPORT](capi3ref.md#SQLITE_VTAB_CONSTRAINT_SUPPORT) [capi3ref.html#sqlite3_create_module](capi3ref.md#sqlite3_create_module) [capi3ref.html#sqlite3_index_info](capi3ref.md#sqlite3_index_info) [capi3ref.html#sqlite3_last_insert_rowid](capi3ref.md#sqlite3_last_insert_rowid) [capi3ref.html#sqlite3_module](capi3ref.md#sqlite3_module) [capi3ref.html#sqlite3_overload_function](capi3ref.md#sqlite3_overload_function) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [capi3ref.html#sqlite3_vtab](capi3ref.md#sqlite3_vtab) [capi3ref.html#sqlite3_vtab_collation](capi3ref.md#sqlite3_vtab_collation) [capi3ref.html#sqlite3_vtab_config](capi3ref.md#sqlite3_vtab_config) [capi3ref.html#sqlite3_vtab_cursor](capi3ref.md#sqlite3_vtab_cursor) [capi3ref.html#sqlite3_vtab_distinct](capi3ref.md#sqlite3_vtab_distinct) [capi3ref.html#sqlite3_vtab_in](capi3ref.md#sqlite3_vtab_in) [capi3ref.html#sqlite3_vtab_in_first](capi3ref.md#sqlite3_vtab_in_first) [capi3ref.html#sqlite3_vtab_nochange](capi3ref.md#sqlite3_vtab_nochange) [capi3ref.html#sqlite3_vtab_on_conflict](capi3ref.md#sqlite3_vtab_on_conflict) [capi3ref.html#sqlite3_vtab_rhs_value](capi3ref.md#sqlite3_vtab_rhs_value) [capi3ref.html#sqlitevtabconstraintsupport](capi3ref.md#sqlitevtabconstraintsupport) [capi3ref.html#sqlitevtabdirectonly](capi3ref.md#sqlitevtabdirectonly) [capi3ref.html#sqlitevtabinnocuous](capi3ref.md#sqlitevtabinnocuous) [capi3ref.html#sqlitevtabusesallschemas](capi3ref.md#sqlitevtabusesallschemas) [changes.html#version_3_12_0](changes.md#version_3_12_0) [changes.html#version_3_20_0](changes.md#version_3_20_0) [changes.html#version_3_23_0](changes.md#version_3_23_0) [changes.html#version_3_26_0](changes.md#version_3_26_0) [changes.html#version_3_35_2](changes.md#version_3_35_2) [changes.html#version_3_53_0](changes.md#version_3_53_0) [changes.html#version_3_7_13](changes.md#version_3_7_13) [changes.html#version_3_7_9](changes.md#version_3_7_9) [changes.html#version_3_8_2](changes.md#version_3_8_2) [cintro.html](cintro.md) [cves.html#cvetab](cves.md#cvetab) [fullsql.html](fullsql.md) [lang_createvtab.html](lang_createvtab.md) [lang_select.html#tabfunc1](lang_select.md#tabfunc1) [loadext.html#write](loadext.md#write) [pragma.html#pragma_legacy_alter_table](pragma.md#pragma_legacy_alter_table) [pragma.html#pragma_module_list](pragma.md#pragma_module_list) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_20_0.html](releaselog/3_20_0.md) [releaselog/3_20_1.html](releaselog/3_20_1.md) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_26_0.html](releaselog/3_26_0.md) [releaselog/3_35_2.html](releaselog/3_35_2.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md) [releaselog/3_7_13.html](releaselog/3_7_13.md) [releaselog/3_7_9.html](releaselog/3_7_9.md) [releaselog/3_8_2.html](releaselog/3_8_2.md) [rescode.html#constraint](rescode.md#constraint) [rescode.html#corrupt_vtab](rescode.md#corrupt_vtab) [rowidtable.html](rowidtable.md) [spellfix1.html](spellfix1.md) [sqldiff.html#sqldiff_vtab](sqldiff.md#sqldiff_vtab) [unionvtab.html](unionvtab.md) [vtab.html#tabfunc2](vtab.md#tabfunc2) [vtablist.html](vtablist.md)
- virtual table configuration option → [c3ref/vtab_config.html](c3ref/vtab_config.md) [capi3ref.html#sqlite3_vtab_config](capi3ref.md#sqlite3_vtab_config)
- virtual table configuration options → [c3ref/vtab_config.html](c3ref/vtab_config.md) [capi3ref.html#sqlite3_vtab_config](capi3ref.md#sqlite3_vtab_config)
- virtual table list → [vtab.html#customvtab](vtab.md#customvtab)
- virtual table module → [c3ref/create_module.html](c3ref/create_module.md) [c3ref/declare_vtab.html](c3ref/declare_vtab.md) [c3ref/index_info.html](c3ref/index_info.md) [c3ref/overload_function.html](c3ref/overload_function.md) [c3ref/vtab.html](c3ref/vtab.md) [c3ref/vtab_cursor.html](c3ref/vtab_cursor.md) [capi3ref.html#sqlite3_create_module](capi3ref.md#sqlite3_create_module) [capi3ref.html#sqlite3_declare_vtab](capi3ref.md#sqlite3_declare_vtab) [capi3ref.html#sqlite3_index_info](capi3ref.md#sqlite3_index_info) [capi3ref.html#sqlite3_overload_function](capi3ref.md#sqlite3_overload_function) [capi3ref.html#sqlite3_vtab](capi3ref.md#sqlite3_vtab) [capi3ref.html#sqlite3_vtab_cursor](capi3ref.md#sqlite3_vtab_cursor) [fts5.html](fts5.md)
- virtual tables → [bytecodevtab.html](bytecodevtab.md) [c3ref/column_blob.html](c3ref/column_blob.md) [c3ref/preupdate_blobwrite.html](c3ref/preupdate_blobwrite.md) [c3ref/stmt_readonly.html](c3ref/stmt_readonly.md) [c3ref/value_blob.html](c3ref/value_blob.md) [capi3ref.html#sqlite3_column_blob](capi3ref.md#sqlite3_column_blob) [capi3ref.html#sqlite3_preupdate_blobwrite](capi3ref.md#sqlite3_preupdate_blobwrite) [capi3ref.html#sqlite3_stmt_readonly](capi3ref.md#sqlite3_stmt_readonly) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [changes.html#version_3_10_0](changes.md#version_3_10_0) [changes.html#version_3_12_0](changes.md#version_3_12_0) [changes.html#version_3_12_2](changes.md#version_3_12_2) [changes.html#version_3_13_0](changes.md#version_3_13_0) [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_38_0](changes.md#version_3_38_0) [changes.html#version_3_38_1](changes.md#version_3_38_1) [changes.html#version_3_44_0](changes.md#version_3_44_0) [changes.html#version_3_6_14](changes.md#version_3_6_14) [changes.html#version_3_6_17](changes.md#version_3_6_17) [changes.html#version_3_7_7](changes.md#version_3_7_7) [cli.html#dotload](cli.md#dotload) [compile.html#trusted_schema](compile.md#trusted_schema) [fileformat2.html#btypes](fileformat2.md#btypes) [fileformat2.html#ffschema](fileformat2.md#ffschema) [fts3.html#simple_fts_queries](fts3.md#simple_fts_queries) [lang_returning.html](lang_returning.md) [lang_upsert.html#parseambig](lang_upsert.md#parseambig) [loadext.html](loadext.md) [oldnews.html](oldnews.md) [pragma.html#pragma_secure_delete](pragma.md#pragma_secure_delete) [pragma.html#pragma_table_list](pragma.md#pragma_table_list) [releaselog/3_10_0.html](releaselog/3_10_0.md) [releaselog/3_10_1.html](releaselog/3_10_1.md) [releaselog/3_10_2.html](releaselog/3_10_2.md) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_38_0.html](releaselog/3_38_0.md) [releaselog/3_38_1.html](releaselog/3_38_1.md) [releaselog/3_38_2.html](releaselog/3_38_2.md) [releaselog/3_38_3.html](releaselog/3_38_3.md) [releaselog/3_38_4.html](releaselog/3_38_4.md) [releaselog/3_38_5.html](releaselog/3_38_5.md) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md) [releaselog/3_6_14.html](releaselog/3_6_14.md) [releaselog/3_6_17.html](releaselog/3_6_17.md) [releaselog/3_7_7.html](releaselog/3_7_7.md) [rescode.html#constraint_vtab](rescode.md#constraint_vtab) [rescode.html#corrupt_vtab](rescode.md#corrupt_vtab) [rescode.html#internal](rescode.md#internal) [schematab.html](schematab.md) [sessionintro.html](sessionintro.md)
- w → [c3ref/mprintf.html](c3ref/mprintf.md) [capi3ref.html#sqlite3_mprintf](capi3ref.md#sqlite3_mprintf) [printf.html](printf.md)
- WAL → [atomiccommit.html](atomiccommit.md) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlpersistwal](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlpersistwal) [capi3ref.html#sqlitefcntlpersistwal](capi3ref.md#sqlitefcntlpersistwal) [changes.html#version_3_7_0](changes.md#version_3_7_0) [changes.html#version_3_7_3](changes.md#version_3_7_3) [changes.html#version_3_7_4](changes.md#version_3_7_4) [changes.html#version_3_7_7](changes.md#version_3_7_7) [compile.html#default_wal_autocheckpoint](compile.md#default_wal_autocheckpoint) [compile.html#omit_wal](compile.md#omit_wal) [fileformat2.html#database_header](fileformat2.md#database_header) [fileformat2.html#vnums](fileformat2.md#vnums) [fileformat2.html#walformat](fileformat2.md#walformat) [howtocorrupt.html#cfgerr](howtocorrupt.md#cfgerr) [howtocorrupt.html#fakeusb](howtocorrupt.md#fakeusb) [howtocorrupt.html#fork](howtocorrupt.md#fork) [howtocorrupt.html#roguejrnl](howtocorrupt.md#roguejrnl) [lang_attach.html](lang_attach.md) [lockingv3.html#rollback](lockingv3.md#rollback) [oldnews.html](oldnews.md) [pragma.html#pragma_locking_mode](pragma.md#pragma_locking_mode) [pragma.html#pragma_synchronous](pragma.md#pragma_synchronous) [releaselog/3_7_0.html](releaselog/3_7_0.md) [releaselog/3_7_3.html](releaselog/3_7_3.md) [releaselog/3_7_4.html](releaselog/3_7_4.md) [releaselog/3_7_7.html](releaselog/3_7_7.md) [rsync.html#intro](rsync.md#intro)
- WAL file → [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlpersistwal](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlpersistwal) [c3ref/snapshot_recover.html](c3ref/snapshot_recover.md) [capi3ref.html#sqlite3_snapshot_recover](capi3ref.md#sqlite3_snapshot_recover) [capi3ref.html#sqlitefcntlpersistwal](capi3ref.md#sqlitefcntlpersistwal) [fileformat2.html#walformat](fileformat2.md#walformat)
- WAL file format → [wal.html#walfile](wal.md#walfile)
- WAL format → [walformat.html](walformat.md)
- WAL mode → [arch.html](arch.md) [c3ref/c_dbconfig_defensive.html#sqlitedbconfignockptonclose](c3ref/c_dbconfig_defensive.md#sqlitedbconfignockptonclose) [c3ref/deserialize.html](c3ref/deserialize.md) [c3ref/snapshot.html](c3ref/snapshot.md) [c3ref/snapshot_get.html](c3ref/snapshot_get.md) [c3ref/snapshot_open.html](c3ref/snapshot_open.md) [c3ref/wal_checkpoint_v2.html](c3ref/wal_checkpoint_v2.md) [capi3ref.html#sqlite3_deserialize](capi3ref.md#sqlite3_deserialize) [capi3ref.html#sqlite3_snapshot](capi3ref.md#sqlite3_snapshot) [capi3ref.html#sqlite3_snapshot_get](capi3ref.md#sqlite3_snapshot_get) [capi3ref.html#sqlite3_snapshot_open](capi3ref.md#sqlite3_snapshot_open) [capi3ref.html#sqlite3_wal_checkpoint_v2](capi3ref.md#sqlite3_wal_checkpoint_v2) [capi3ref.html#sqlitedbconfignockptonclose](capi3ref.md#sqlitedbconfignockptonclose) [changes.html#version_3_11_0](changes.md#version_3_11_0) [changes.html#version_3_17_0](changes.md#version_3_17_0) [changes.html#version_3_22_0](changes.md#version_3_22_0) [changes.html#version_3_33_0](changes.md#version_3_33_0) [changes.html#version_3_34_0](changes.md#version_3_34_0) [changes.html#version_3_43_0](changes.md#version_3_43_0) [changes.html#version_3_7_14](changes.md#version_3_7_14) [changes.html#version_3_7_6_3](changes.md#version_3_7_6_3) [changes.html#version_3_8_6](changes.md#version_3_8_6) [compile.html#default_journal_size_limit](compile.md#default_journal_size_limit) [compile.html#default_wal_synchronous](compile.md#default_wal_synchronous) [compile.html#omit_seh](compile.md#omit_seh) [compile.html#rcmd](compile.md#rcmd) [fasterthanfs.html](fasterthanfs.md) [fileformat2.html](fileformat2.md) [formatchng.html](formatchng.md) [howtocorrupt.html#fakeusb](howtocorrupt.md#fakeusb) [howtocorrupt.html#posix_close_bug](howtocorrupt.md#posix_close_bug) [isolation.html](isolation.md) [lang_transaction.html#immediate](lang_transaction.md#immediate) [lockingv3.html](lockingv3.md) [news.html](news.md) [oldnews.html](oldnews.md) [pragma.html#pragma_journal_size_limit](pragma.md#pragma_journal_size_limit) [pragma.html#pragma_page_size](pragma.md#pragma_page_size) [pragma.html#pragma_synchronous](pragma.md#pragma_synchronous) [pragma.html#pragma_wal_checkpoint](pragma.md#pragma_wal_checkpoint) [psow.html](psow.md) [rbu.html#rbu_updates](rbu.md#rbu_updates) [rbu.html#rbu_vacuum](rbu.md#rbu_vacuum) [releaselog/3_11_0.html](releaselog/3_11_0.md) [releaselog/3_11_1.html](releaselog/3_11_1.md) [releaselog/3_17_0.html](releaselog/3_17_0.md) [releaselog/3_22_0.html](releaselog/3_22_0.md) [releaselog/3_33_0.html](releaselog/3_33_0.md) [releaselog/3_34_0.html](releaselog/3_34_0.md) [releaselog/3_34_1.html](releaselog/3_34_1.md) [releaselog/3_43_0.html](releaselog/3_43_0.md) [releaselog/3_43_1.html](releaselog/3_43_1.md) [releaselog/3_43_2.html](releaselog/3_43_2.md) [releaselog/3_7_14.html](releaselog/3_7_14.md) [releaselog/3_7_6_3.html](releaselog/3_7_6_3.md) [releaselog/3_8_6.html](releaselog/3_8_6.md) [rescode.html#busy_recovery](rescode.md#busy_recovery) [rescode.html#busy_snapshot](rescode.md#busy_snapshot) [rescode.html#ioerr_shmsize](rescode.md#ioerr_shmsize) [rescode.html#notice_recover_wal](rescode.md#notice_recover_wal) [rescode.html#protocol](rescode.md#protocol) [rescode.html#readonly_cantinit](rescode.md#readonly_cantinit) [rescode.html#readonly_cantlock](rescode.md#readonly_cantlock) [rescode.html#readonly_recovery](rescode.md#readonly_recovery) [sharedcache.html#dontuse](sharedcache.md#dontuse) [tclsqlite.html#wal_hook](tclsqlite.md#wal_hook) [tempfiles.html#shmfile](tempfiles.md#shmfile) [tempfiles.html#superjrnl](tempfiles.md#superjrnl) [tempfiles.html#walfile](tempfiles.md#walfile) [useovernet.html](useovernet.md) [versionnumbers.html](versionnumbers.md) [walformat.html](walformat.md)
- WAL read algorithm → [fileformat2.html#walindexformat](fileformat2.md#walindexformat)
- WAL reset → [walformat.html#locks](walformat.md#locks) [walformat.html#nbackfill](walformat.md#nbackfill)
- WAL without shared memory → [howtocorrupt.html#fakeusb](howtocorrupt.md#fakeusb) [pragma.html#pragma_locking_mode](pragma.md#pragma_locking_mode)
- wal-index → [vfs.html](vfs.md) [wal.html#advantages](wal.md#advantages) [wal.html#bigwal](wal.md#bigwal) [wal.html#bkwrds](wal.md#bkwrds)
- WAL-index File Format → [fileformat2.html#walindexformat](fileformat2.md#walindexformat)
- WAL-mode locks → [walformat.html#locks](walformat.md#locks)
- WAL-reset bug → [howtocorrupt.html#cfgerr](howtocorrupt.md#cfgerr) [news.html](news.md)
- WAL-reset database corruption bug → [changes.html#version_3_51_3](changes.md#version_3_51_3) [changes.html#version_3_53_0](changes.md#version_3_53_0) [releaselog/3_51_3.html](releaselog/3_51_3.md) [releaselog/3_53_0.html](releaselog/3_53_0.md) [releaselog/3_53_1.html](releaselog/3_53_1.md) [releaselog/3_53_2.html](releaselog/3_53_2.md) [releaselog/3_53_3.html](releaselog/3_53_3.md) [releaselog/3_53_4.html](releaselog/3_53_4.md)
- wal_autocheckpoint pragma → [c3ref/wal_autocheckpoint.html](c3ref/wal_autocheckpoint.md) [c3ref/wal_hook.html](c3ref/wal_hook.md) [capi3ref.html#sqlite3_wal_autocheckpoint](capi3ref.md#sqlite3_wal_autocheckpoint) [capi3ref.html#sqlite3_wal_hook](capi3ref.md#sqlite3_wal_hook) [wal.html#fast](wal.md#fast)
- wal_checkpoint pragma → [changes.html#version_3_7_6](changes.md#version_3_7_6) [releaselog/3_7_6.html](releaselog/3_7_6.md) [wal.html#fast](wal.md#fast)
- WHERE clause → [lang_select.html#simpleselect](lang_select.md#simpleselect)
- WHERE-clause push-down optimization → [changes.html#version_3_13_0](changes.md#version_3_13_0) [changes.html#version_3_42_0](changes.md#version_3_42_0) [changes.html#version_3_46_0](changes.md#version_3_46_0) [changes.html#version_3_9_0](changes.md#version_3_9_0) [releaselog/3_13_0.html](releaselog/3_13_0.md) [releaselog/3_42_0.html](releaselog/3_42_0.md) [releaselog/3_46_0.html](releaselog/3_46_0.md) [releaselog/3_46_1.html](releaselog/3_46_1.md) [releaselog/3_9_0.html](releaselog/3_9_0.md) [releaselog/3_9_1.html](releaselog/3_9_1.md) [releaselog/3_9_2.html](releaselog/3_9_2.md) [releaselog/3_9_3.html](releaselog/3_9_3.md)
- Why SQLite Uses Bytecode → [opcode.html](opcode.md)
- window chaining → [changes.html#version_3_28_0](changes.md#version_3_28_0) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- window function → [appfunc.html](appfunc.md) [changes.html#version_3_27_2](changes.md#version_3_27_2) [changes.html#version_3_46_1](changes.md#version_3_46_1) [news.html](news.md) [optoverview.html#flattening](optoverview.md#flattening) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_46_1.html](releaselog/3_46_1.md)
- Window functions → [appfunc.html](appfunc.md)
- window functions → [appfunc.html](appfunc.md) [changes.html#version_3_25_0](changes.md#version_3_25_0) [changes.html#version_3_25_2](changes.md#version_3_25_2) [changes.html#version_3_25_3](changes.md#version_3_25_3) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_28_0](changes.md#version_3_28_0) [compile.html#omit_windowfunc](compile.md#omit_windowfunc) [features.html](features.md) [fullsql.html](fullsql.md) [lang_aggfunc.html#aggorderby](lang_aggfunc.md#aggorderby) [lang_corefunc.html](lang_corefunc.md) [lang_expr.html#\*funcinexpr](lang_expr.md#*funcinexpr) [lang_returning.html](lang_returning.md) [lang_with.html#recursivecte](lang_with.md#recursivecte) [news.html](news.md) [releaselog/3_25_0.html](releaselog/3_25_0.md) [releaselog/3_25_1.html](releaselog/3_25_1.md) [releaselog/3_25_2.html](releaselog/3_25_2.md) [releaselog/3_25_3.html](releaselog/3_25_3.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_28_0.html](releaselog/3_28_0.md)
- window-defn → [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [windowfunctions.html](windowfunctions.md) [windowfunctions.html#framespec](windowfunctions.md#framespec) [windowfunctions.html#wexcls](windowfunctions.md#wexcls)
- window-function-invocation → [lang_expr.html#\*funcinexpr](lang_expr.md#*funcinexpr) [windowfunctions.html](windowfunctions.md)
- winfunc → [lang.html](lang.md)
- WITH → [fullsql.html](fullsql.md) [lang_select.html](lang_select.md)
- WITH clause → [changes.html#version_3_23_0](changes.md#version_3_23_0) [changes.html#version_3_8_3](changes.md#version_3_8_3) [lang.html](lang.md) [lang_select.html#values](lang_select.md#values) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [releaselog/3_8_3.html](releaselog/3_8_3.md)
- with-clause → [lang_with.html](lang_with.md)
- WITHOUT ROWID → [autoinc.html](autoinc.md) [c3ref/last_insert_rowid.html](c3ref/last_insert_rowid.md) [c3ref/table_column_metadata.html](c3ref/table_column_metadata.md) [c3ref/update_hook.html](c3ref/update_hook.md) [capi3ref.html#sqlite3_last_insert_rowid](capi3ref.md#sqlite3_last_insert_rowid) [capi3ref.html#sqlite3_table_column_metadata](capi3ref.md#sqlite3_table_column_metadata) [capi3ref.html#sqlite3_update_hook](capi3ref.md#sqlite3_update_hook) [changes.html#version_3_16_2](changes.md#version_3_16_2) [changes.html#version_3_17_0](changes.md#version_3_17_0) [changes.html#version_3_19_0](changes.md#version_3_19_0) [changes.html#version_3_22_0](changes.md#version_3_22_0) [changes.html#version_3_30_0](changes.md#version_3_30_0) [changes.html#version_3_40_0](changes.md#version_3_40_0) [changes.html#version_3_49_0](changes.md#version_3_49_0) [changes.html#version_3_8_11](changes.md#version_3_8_11) [changes.html#version_3_8_11_1](changes.md#version_3_8_11_1) [changes.html#version_3_8_2](changes.md#version_3_8_2) [changes.html#version_3_8_5](changes.md#version_3_8_5) [changes.html#version_3_8_6](changes.md#version_3_8_6) [changes.html#version_3_8_8](changes.md#version_3_8_8) [fileformat2.html##sqltab](fileformat2.md##sqltab) [fileformat2.html#btypes](fileformat2.md#btypes) [fileformat2.html#ffschema](fileformat2.md#ffschema) [fileformat2.html#stat1tab](fileformat2.md#stat1tab) [fileformat2.html#stat4tab](fileformat2.md#stat4tab) [imposter.html](imposter.md) [lang_createtable.html](lang_createtable.md) [lang_createtable.html#primkeyconst](lang_createtable.md#primkeyconst) [lang_createtable.html#rowid](lang_createtable.md#rowid) [lang_createtable.html#uniqueconst](lang_createtable.md#uniqueconst) [lang_expr.html#in_op](lang_expr.md#in_op) [news.html](news.md) [oldnews.html](oldnews.md) [optoverview.html#or_opt](optoverview.md#or_opt) [pragma.html#pragma_foreign_key_check](pragma.md#pragma_foreign_key_check) [pragma.html#pragma_index_info](pragma.md#pragma_index_info) [pragma.html#pragma_index_xinfo](pragma.md#pragma_index_xinfo) [pragma.html#pragma_table_list](pragma.md#pragma_table_list) [queryplanner.html#partialsort](queryplanner.md#partialsort) [queryplanner.html#searching](queryplanner.md#searching) [quirks.html](quirks.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_17_0.html](releaselog/3_17_0.md) [releaselog/3_19_0.html](releaselog/3_19_0.md) [releaselog/3_19_1.html](releaselog/3_19_1.md) [releaselog/3_19_2.html](releaselog/3_19_2.md) [releaselog/3_19_3.html](releaselog/3_19_3.md) [releaselog/3_22_0.html](releaselog/3_22_0.md) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md) [releaselog/3_40_0.html](releaselog/3_40_0.md) [releaselog/3_40_1.html](releaselog/3_40_1.md) [releaselog/3_49_0.html](releaselog/3_49_0.md) [releaselog/3_49_1.html](releaselog/3_49_1.md) [releaselog/3_49_2.html](releaselog/3_49_2.md) [releaselog/3_8_11.html](releaselog/3_8_11.md) [releaselog/3_8_11_1.html](releaselog/3_8_11_1.md) [releaselog/3_8_2.html](releaselog/3_8_2.md) [releaselog/3_8_5.html](releaselog/3_8_5.md) [releaselog/3_8_6.html](releaselog/3_8_6.md) [releaselog/3_8_8.html](releaselog/3_8_8.md) [releaselog/3_8_8_1.html](releaselog/3_8_8_1.md) [releaselog/3_8_8_2.html](releaselog/3_8_8_2.md) [releaselog/3_8_8_3.html](releaselog/3_8_8_3.md) [rowidtable.html](rowidtable.md) [schematab.html](schematab.md) [sessionintro.html](sessionintro.md) [sqldiff.html](sqldiff.md) [stricttables.html](stricttables.md) [vtab.html#worid](vtab.md#worid)
- WITHOUT ROWID virtual table → [vtab.html#xupdate](vtab.md#xupdate)
- WITHOUT ROWID virtual tables → [changes.html#version_3_14](changes.md#version_3_14) [changes.html#version_3_21_0](changes.md#version_3_21_0) [releaselog/3_14.html](releaselog/3_14.md) [releaselog/3_14_1.html](releaselog/3_14_1.md) [releaselog/3_14_2.html](releaselog/3_14_2.md) [releaselog/3_21_0.html](releaselog/3_21_0.md)
- writable_schema → [changes.html#version_3_30_0](changes.md#version_3_30_0) [releaselog/3_30_0.html](releaselog/3_30_0.md) [releaselog/3_30_1.html](releaselog/3_30_1.md)
- write-ahead log → [atomiccommit.html](atomiccommit.md) [c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntljournalpointer](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntljournalpointer) [c3ref/wal_autocheckpoint.html](c3ref/wal_autocheckpoint.md) [c3ref/wal_checkpoint.html](c3ref/wal_checkpoint.md) [capi3ref.html#sqlite3_wal_autocheckpoint](capi3ref.md#sqlite3_wal_autocheckpoint) [capi3ref.html#sqlite3_wal_checkpoint](capi3ref.md#sqlite3_wal_checkpoint) [capi3ref.html#sqlitefcntljournalpointer](capi3ref.md#sqlitefcntljournalpointer) [compile.html#omit_wal](compile.md#omit_wal) [errlog.html](errlog.md) [howtocorrupt.html#roguejrnl](howtocorrupt.md#roguejrnl) [lang_returning.html](lang_returning.md) [lang_vacuum.html](lang_vacuum.md) [lang_vacuum.html#howvacuumworks](lang_vacuum.md#howvacuumworks) [lockingv3.html](lockingv3.md) [oldnews.html](oldnews.md) [pragma.html#pragma_journal_mode](pragma.md#pragma_journal_mode) [pragma.html#pragma_wal_autocheckpoint](pragma.md#pragma_wal_autocheckpoint) [pragma.html#pragma_wal_checkpoint](pragma.md#pragma_wal_checkpoint) [shortnames.html](shortnames.md) [shortnames.html#db83corrupt](shortnames.md#db83corrupt)
- xBegin → [vtab.html#xcommit](vtab.md#xcommit) [vtab.html#xrollback](vtab.md#xrollback) [vtab.html#xsync](vtab.md#xsync)
- xBestIndex → [c3ref/index_info.html](c3ref/index_info.md) [c3ref/vtab_collation.html](c3ref/vtab_collation.md) [c3ref/vtab_distinct.html](c3ref/vtab_distinct.md) [c3ref/vtab_in.html](c3ref/vtab_in.md) [c3ref/vtab_in_first.html](c3ref/vtab_in_first.md) [c3ref/vtab_rhs_value.html](c3ref/vtab_rhs_value.md) [capi3ref.html#sqlite3_index_info](capi3ref.md#sqlite3_index_info) [capi3ref.html#sqlite3_vtab_collation](capi3ref.md#sqlite3_vtab_collation) [capi3ref.html#sqlite3_vtab_distinct](capi3ref.md#sqlite3_vtab_distinct) [capi3ref.html#sqlite3_vtab_in](capi3ref.md#sqlite3_vtab_in) [capi3ref.html#sqlite3_vtab_in_first](capi3ref.md#sqlite3_vtab_in_first) [capi3ref.html#sqlite3_vtab_rhs_value](capi3ref.md#sqlite3_vtab_rhs_value) [changes.html#version_3_12_0](changes.md#version_3_12_0) [changes.html#version_3_21_0](changes.md#version_3_21_0) [changes.html#version_3_26_0](changes.md#version_3_26_0) [changes.html#version_3_35_3](changes.md#version_3_35_3) [releaselog/3_12_0.html](releaselog/3_12_0.md) [releaselog/3_12_1.html](releaselog/3_12_1.md) [releaselog/3_12_2.html](releaselog/3_12_2.md) [releaselog/3_21_0.html](releaselog/3_21_0.md) [releaselog/3_26_0.html](releaselog/3_26_0.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md) [rescode.html#constraint](rescode.md#constraint) [rescode.html#notfound](rescode.md#notfound) [vtab.html#xfilter](vtab.md#xfilter) [vtab.html#xfindfunction](vtab.md#xfindfunction)
- xColumn → [c3ref/value_blob.html](c3ref/value_blob.md) [c3ref/vtab_cursor.html](c3ref/vtab_cursor.md) [c3ref/vtab_nochange.html](c3ref/vtab_nochange.md) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [capi3ref.html#sqlite3_vtab_cursor](capi3ref.md#sqlite3_vtab_cursor) [capi3ref.html#sqlite3_vtab_nochange](capi3ref.md#sqlite3_vtab_nochange) [changes.html#version_3_23_0](changes.md#version_3_23_0) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md) [vtab.html#xfilter](vtab.md#xfilter) [vtab.html#xupdate](vtab.md#xupdate)
- xCommit → [vtab.html#xBegin](vtab.md#xBegin) [vtab.html#xsync](vtab.md#xsync)
- xConnect → [c3ref/c_vtab_constraint_support.html#sqlitevtabconstraintsupport](c3ref/c_vtab_constraint_support.md#sqlitevtabconstraintsupport) [c3ref/c_vtab_constraint_support.html#sqlitevtabdirectonly](c3ref/c_vtab_constraint_support.md#sqlitevtabdirectonly) [c3ref/c_vtab_constraint_support.html#sqlitevtabinnocuous](c3ref/c_vtab_constraint_support.md#sqlitevtabinnocuous) [c3ref/c_vtab_constraint_support.html#sqlitevtabusesallschemas](c3ref/c_vtab_constraint_support.md#sqlitevtabusesallschemas) [c3ref/create_module.html](c3ref/create_module.md) [c3ref/declare_vtab.html](c3ref/declare_vtab.md) [c3ref/vtab_config.html](c3ref/vtab_config.md) [capi3ref.html#sqlite3_create_module](capi3ref.md#sqlite3_create_module) [capi3ref.html#sqlite3_declare_vtab](capi3ref.md#sqlite3_declare_vtab) [capi3ref.html#sqlite3_vtab_config](capi3ref.md#sqlite3_vtab_config) [capi3ref.html#sqlitevtabconstraintsupport](capi3ref.md#sqlitevtabconstraintsupport) [capi3ref.html#sqlitevtabdirectonly](capi3ref.md#sqlitevtabdirectonly) [capi3ref.html#sqlitevtabinnocuous](capi3ref.md#sqlitevtabinnocuous) [capi3ref.html#sqlitevtabusesallschemas](capi3ref.md#sqlitevtabusesallschemas) [changes.html#version_3_31_0](changes.md#version_3_31_0) [lang_createvtab.html](lang_createvtab.md) [releaselog/3_31_0.html](releaselog/3_31_0.md) [releaselog/3_31_1.html](releaselog/3_31_1.md) [vtab.html#customvtab](vtab.md#customvtab) [vtab.html#epovtab](vtab.md#epovtab) [vtab.html#xbestindex](vtab.md#xbestindex) [vtab.html#xcreate](vtab.md#xcreate) [vtab.html#xdisconnect](vtab.md#xdisconnect) [vtab.html#xupdate](vtab.md#xupdate)
- xCreate → [c3ref/c_vtab_constraint_support.html#sqlitevtabconstraintsupport](c3ref/c_vtab_constraint_support.md#sqlitevtabconstraintsupport) [c3ref/c_vtab_constraint_support.html#sqlitevtabdirectonly](c3ref/c_vtab_constraint_support.md#sqlitevtabdirectonly) [c3ref/c_vtab_constraint_support.html#sqlitevtabinnocuous](c3ref/c_vtab_constraint_support.md#sqlitevtabinnocuous) [c3ref/c_vtab_constraint_support.html#sqlitevtabusesallschemas](c3ref/c_vtab_constraint_support.md#sqlitevtabusesallschemas) [c3ref/create_module.html](c3ref/create_module.md) [c3ref/declare_vtab.html](c3ref/declare_vtab.md) [c3ref/vtab_config.html](c3ref/vtab_config.md) [capi3ref.html#sqlite3_create_module](capi3ref.md#sqlite3_create_module) [capi3ref.html#sqlite3_declare_vtab](capi3ref.md#sqlite3_declare_vtab) [capi3ref.html#sqlite3_vtab_config](capi3ref.md#sqlite3_vtab_config) [capi3ref.html#sqlitevtabconstraintsupport](capi3ref.md#sqlitevtabconstraintsupport) [capi3ref.html#sqlitevtabdirectonly](capi3ref.md#sqlitevtabdirectonly) [capi3ref.html#sqlitevtabinnocuous](capi3ref.md#sqlitevtabinnocuous) [capi3ref.html#sqlitevtabusesallschemas](capi3ref.md#sqlitevtabusesallschemas) [lang_createvtab.html](lang_createvtab.md) [vtab.html](vtab.md) [vtab.html#customvtab](vtab.md#customvtab) [vtab.html#epoonlyvtab](vtab.md#epoonlyvtab) [vtab.html#epovtab](vtab.md#epovtab) [vtab.html#sqlite3_module.xDestroy](vtab.md#sqlite3_module.xDestroy) [vtab.html#xbestindex](vtab.md#xbestindex) [vtab.html#xconnect](vtab.md#xconnect) [vtab.html#xupdate](vtab.md#xupdate)
- xDestroy → [vtab.html#xdisconnect](vtab.md#xdisconnect)
- xDisconnect → [vtab.html#sqlite3_module.xDestroy](vtab.md#sqlite3_module.xDestroy)
- xEof → [c3ref/vtab_cursor.html](c3ref/vtab_cursor.md) [capi3ref.html#sqlite3_vtab_cursor](capi3ref.md#sqlite3_vtab_cursor) [vtab.html#xfilter](vtab.md#xfilter) [vtab.html#xnext](vtab.md#xnext)
- xFilter → [c3ref/index_info.html](c3ref/index_info.md) [c3ref/vtab_cursor.html](c3ref/vtab_cursor.md) [c3ref/vtab_in.html](c3ref/vtab_in.md) [c3ref/vtab_in_first.html](c3ref/vtab_in_first.md) [capi3ref.html#sqlite3_index_info](capi3ref.md#sqlite3_index_info) [capi3ref.html#sqlite3_vtab_cursor](capi3ref.md#sqlite3_vtab_cursor) [capi3ref.html#sqlite3_vtab_in](capi3ref.md#sqlite3_vtab_in) [capi3ref.html#sqlite3_vtab_in_first](capi3ref.md#sqlite3_vtab_in_first) [vtab.html#colUsed](vtab.md#colUsed) [vtab.html#xbestindex](vtab.md#xbestindex) [vtab.html#xeof](vtab.md#xeof) [vtab.html#xfindfunction](vtab.md#xfindfunction) [vtab.html#xnext](vtab.md#xnext) [vtab.html#xopen](vtab.md#xopen)
- xFindFunction → [c3ref/c_index_constraint_eq.html](c3ref/c_index_constraint_eq.md) [c3ref/overload_function.html](c3ref/overload_function.md) [capi3ref.html#SQLITE_INDEX_CONSTRAINT_EQ](capi3ref.md#SQLITE_INDEX_CONSTRAINT_EQ) [capi3ref.html#sqlite3_overload_function](capi3ref.md#sqlite3_overload_function) [vtab.html#colUsed](vtab.md#colUsed) [vtab.html#xbestindex](vtab.md#xbestindex)
- xIntegrity method → [changes.html#version_3_44_0](changes.md#version_3_44_0) [releaselog/3_44_0.html](releaselog/3_44_0.md) [releaselog/3_44_1.html](releaselog/3_44_1.md) [releaselog/3_44_2.html](releaselog/3_44_2.md)
- xNext → [c3ref/index_info.html](c3ref/index_info.md) [c3ref/vtab_cursor.html](c3ref/vtab_cursor.md) [capi3ref.html#sqlite3_index_info](capi3ref.md#sqlite3_index_info) [capi3ref.html#sqlite3_vtab_cursor](capi3ref.md#sqlite3_vtab_cursor) [vtab.html#xeof](vtab.md#xeof) [vtab.html#xfilter](vtab.md#xfilter)
- xRelease → [changes.html#version_3_7_7](changes.md#version_3_7_7) [releaselog/3_7_7.html](releaselog/3_7_7.md)
- xRollback → [vtab.html#xBegin](vtab.md#xBegin) [vtab.html#xsync](vtab.md#xsync)
- xRollbackTo → [changes.html#version_3_7_7](changes.md#version_3_7_7) [releaselog/3_7_7.html](releaselog/3_7_7.md)
- xRowid → [c3ref/vtab_cursor.html](c3ref/vtab_cursor.md) [capi3ref.html#sqlite3_vtab_cursor](capi3ref.md#sqlite3_vtab_cursor) [vtab.html#xfilter](vtab.md#xfilter)
- xSavepoint → [changes.html#version_3_7_7](changes.md#version_3_7_7) [releaselog/3_7_7.html](releaselog/3_7_7.md)
- xUpdate → [c3ref/c_vtab_constraint_support.html#sqlitevtabconstraintsupport](c3ref/c_vtab_constraint_support.md#sqlitevtabconstraintsupport) [c3ref/value_blob.html](c3ref/value_blob.md) [c3ref/vtab_nochange.html](c3ref/vtab_nochange.md) [c3ref/vtab_on_conflict.html](c3ref/vtab_on_conflict.md) [capi3ref.html#sqlite3_value_blob](capi3ref.md#sqlite3_value_blob) [capi3ref.html#sqlite3_vtab_nochange](capi3ref.md#sqlite3_vtab_nochange) [capi3ref.html#sqlite3_vtab_on_conflict](capi3ref.md#sqlite3_vtab_on_conflict) [capi3ref.html#sqlitevtabconstraintsupport](capi3ref.md#sqlitevtabconstraintsupport) [vtab.html#worid](vtab.md#worid)
- YYSTACKDEPTH → [compile.html#yystackdepth](compile.md#yystackdepth) [compile.html#yytrackmaxstackdepth](compile.md#yytrackmaxstackdepth)
- YYTRACKMAXSTACKDEPTH → [c3ref/c_status_malloc_count.html#sqlitestatusparserstack](c3ref/c_status_malloc_count.md#sqlitestatusparserstack) [capi3ref.html#sqlitestatusparserstack](capi3ref.md#sqlitestatusparserstack)
- z → [c3ref/mprintf.html](c3ref/mprintf.md) [capi3ref.html#sqlite3_mprintf](capi3ref.md#sqlite3_mprintf) [printf.html](printf.md)
- zeroblob → [c3ref/blob_open.html](c3ref/blob_open.md) [capi3ref.html#sqlite3_blob_open](capi3ref.md#sqlite3_blob_open) [changes.html#version_3_16_2](changes.md#version_3_16_2) [changes.html#version_3_27_0](changes.md#version_3_27_0) [changes.html#version_3_8_4](changes.md#version_3_8_4) [lang_corefunc.html](lang_corefunc.md) [releaselog/3_16_2.html](releaselog/3_16_2.md) [releaselog/3_27_0.html](releaselog/3_27_0.md) [releaselog/3_27_1.html](releaselog/3_27_1.md) [releaselog/3_27_2.html](releaselog/3_27_2.md) [releaselog/3_8_4.html](releaselog/3_8_4.md) [releaselog/3_8_4_1.html](releaselog/3_8_4_1.md) [releaselog/3_8_4_2.html](releaselog/3_8_4_2.md) [releaselog/3_8_4_3.html](releaselog/3_8_4_3.md)
- zipfile → [cli.html#arinsup](cli.md#arinsup) [cves.html#cvetab](cves.md#cvetab) [sqlar.html#dbasobj](sqlar.md#dbasobj) [vtablist.html](vtablist.md)
- Zipfile virtual table → [changes.html#version_3_22_0](changes.md#version_3_22_0) [changes.html#version_3_23_0](changes.md#version_3_23_0) [cli.html#zipdb](cli.md#zipdb) [cves.html#cvetab](cves.md#cvetab) [releaselog/3_22_0.html](releaselog/3_22_0.md) [releaselog/3_23_0.html](releaselog/3_23_0.md) [releaselog/3_23_1.html](releaselog/3_23_1.md)
---
# Begin adding a change to a changegroup
*Sección: Guides | Origen: https://www.sqlite.org/session/sqlite3changegroup_change_begin.html*
[](../session/intro.md)
## Session Module C Interface
## Begin adding a change to a changegroup
> int sqlite3changegroup_change_begin(\
> sqlite3_changegroup\*,\
> int eOp,\
> const char \*zTab,\
> int bIndirect,\
> char \*\*pzErr\
> );\
This API is used, in concert with other sqlite3changegroup_change_xxx() APIs, to add changes to a changegroup object one at a time. To add a single change, the caller must:
1\. Invoke sqlite3changegroup_change_begin() to indicate the type of change (INSERT, UPDATE or DELETE), the affected table and whether or not the change should be marked as indirect.
2\. Invoke sqlite3changegroup_change_int64() or one of the other four value functions - \_null(), \_double(), \_text() or \_blob() - one or more times to specify old.\* and new.\* values for the change being constructed.
3\. Invoke sqlite3changegroup_change_finish() to either finish adding the change to the group, or to discard the change altogether.
The first argument to this function must be a pointer to the existing changegroup object that the change will be added to. The second argument must be SQLITE_INSERT, SQLITE_UPDATE or SQLITE_DELETE. The third is the name of the table that the change affects, and the fourth is a boolean flag specifying whether the change should be marked as "indirect" (if bIndirect is non-zero) or not indirect (if bIndirect is zero).
Following a successful call to this function, this function may not be called again on the same changegroup object until after sqlite3changegroup_change_finish() has been called. Doing so is an SQLITE_MISUSE error.
The changegroup object passed as the first argument must be already configured with schema data for the specified table. It may be configured either by calling sqlite3changegroup_schema() with a database that contains the table, or sqlite3changegroup_add() with a changeset that contains the table. If the changegroup object has not been configured with a schema for the specified table when this function is called, SQLITE_ERROR is returned.
If successful, SQLITE_OK is returned. Otherwise, if an error occurs, an SQLite error code is returned. In this case, if argument pzErr is non-NULL, then (\*pzErr) may be set to point to a buffer containing a utf-8 formated, nul-terminated, English language error message. It is the responsibility of the caller to eventually free this buffer using sqlite3_free().
See also lists of [Objects](../session/objlist.md), [Constants](../session/constlist.md), and [Functions](../session/funclist.md).
---
# Benefits of SQLite As A File Format
*Sección: Guides | Origen: https://www.sqlite.org/aff_short.html*
# SQLite As An Application File Format
*(Note: The current page is a brief summary of why SQLite makes a good application file format. The topic is considered at greater detail in a [separate technical note](appfileformat.md).)*
SQLite has been used with great success as the on-disk file format for desktop applications such as version control systems, financial analysis tools, media cataloging and editing suites, CAD packages, record keeping programs, and so forth. The traditional File/Open operation calls sqlite3_open() to attach to the database file. Updates happen automatically as application content is revised so the File/Save menu option becomes superfluous. The File/Save_As menu option can be implemented using the [backup API](backup.md).
There are many advantages to using SQLite as an application file format, including:
1. **Better performance**
- Reading and writing from an SQLite database is often faster than reading and writing individual files from disk. See [35% Faster Than The Filesystem](fasterthanfs.md) and [Internal Versus External BLOBs](intern-v-extern-blob.md).
- The application only has to load the data it needs, rather than reading the entire file and holding a complete parse in memory.
- Small edits only overwrite the parts of the file that change, reducing write time and wear on SSD drives.
2. **Reduced application cost and complexity**
- No application file I/O code to write and debug.
- Content can be accessed and updated using concise SQL queries instead of lengthy and error-prone procedural routines.
- The file format can be extended in future releases simply by adding new tables and/or columns, preserving backwards compatibility.
- Applications can leverage the [full-text search](fts3.md) and [RTREE](rtree.md) indexes and use triggers to implement an [automated undo/redo stack](undoredo.md).
- Performance problems can often be resolved, even late in the development cycle, using [CREATE INDEX](lang_createindex.md), avoiding costly redesign, rewrite, and retest efforts.
3. **Portability**
- The application file is portable across all operating systems, 32-bit and 64-bit and big- and little-endian architectures.
- A federation of programs, perhaps all written in different programming languages, can access the same application file with no compatibility concerns.
- Multiple processes can attach to the same application file and can read and write without interfering with each another.
- Diverse content which might otherwise be stored as a "pile-of-files" is encapsulated into a single disk file for simpler transport via scp/ftp, USB stick, and/or email attachment.
4. **Reliability**
- Content can be updated continuously and atomically so that little or no work is lost in a power failure or crash.
- Bugs are far less likely in SQLite than in custom-written file I/O code.
- SQL queries are many times smaller than the equivalent procedural code, and since the number of bugs per line of code is roughly constant, this means fewer bugs overall.
5. **Accessibility**
- SQLite database content can be viewed using a wide variety of third-party tools.
- Content stored in an SQLite database is more likely to be recoverable decades in the future, long after all traces of the original application have been lost. Data lives longer than code.
- SQLite database files are [recommended by the US Library of Congress](locrsf.md) as a storage format for long-term preservation of digital content.
SQLite allows database files to have any desired filename extension, so an application can choose a custom filename extension for its own use, if desired. The [application_id pragma](pragma.md#pragma_application_id) can be used to set an "Application ID" integer in the database file so that tools like [file(1)](http://www.darwinsys.com/file/) can determine that the file is associated with your application and is not just a generic SQL database.
---
# Books About SQLite
*Sección: Guides | Origen: https://www.sqlite.org/books.html*
------------------------------------------------------------------------
## SQLite Forensics (2018)
Author: Paul Sanderson\
Publisher: [Amazon](https://www.amazon.com/product/dp/1980293074)
This text by noted digital forensics expert, Paul Sanderson, provides investigators with low-level technical details useful in analysing SQLite database files.
Every computer and phone uses hundreds of SQLite databases and there are over one trillion SQLite databases in active use. Hence, the importance of examining the data held in these databases in an investigation, including deleted data when possible, is paramount. This book fully explains the format of the SQLite database file. It shows how records are encoded, how to decode them manually and how to decode records that are partially overwritten. It also describe how the workings of SQLite, and in particular the journal and WAL, can be used to ascertain what has happened in a manner that cannot be determined from the data alone. The book covers basic SQL queries and how they can be used to create a custom report that includes data from different tables, and shows how one can use SQL queries to test hypotheses about the relationships of data in different tables.
This book is aimed mainly at forensic practitioners, and it is assumed that the reader has some basic knowledge of computer forensics; it will also be of interest to computer professionals in general particularly those who have an interest in the SQLite file format.
------------------------------------------------------------------------
## Learning SQLite for iOS (2016)
Author: Gene Da Rocha\
Publisher: [Packt Publishing](https://www.packtpub.com/application-development/learning-sqlite-ios)
This book starts with the architecture of SQLite database and introduces you to concepts in SQL. You will find yourself equipped to design your own database system, administer it, and maintain it. Further, you will learn how to operate your SQLite databases smoothly using SQL commands.
You will be able to extend the functionality of SQLite by using its vast arsenal of C API calls to build some interesting, exciting, new, and intelligent data-driven applications. Understand how Xcode, HTML5, and Phonegap can be used to build a cross-platform modern app which can benefit from all these technologies - all through creating a complete, customizable application skeleton that you can build on for your own apps. This book provides a comprehensive description of SQLite database system. It describes design principles, engineering trade-offs, implementation issues, and operations of SQLite.
------------------------------------------------------------------------
## SQLite Database System Design and Implementation (2015)
Author: Sibsankar Haldar\
Publisher: [https://books.google.com/](https://books.google.com/books?id=OEJ1CQAAQBAJ)\
This book provides a comprehensive description of SQLite database system. It describes design principles, engineering trade-offs, implementation issues, and operations of SQLite.
------------------------------------------------------------------------
## Android SQLite Essentials (2014)
Authors: Sunny Kumar Aditya and Vikash Kumar Karn\
Publisher: [Packt Publishing](https://www.packtpub.com/application-development/android-sqlite-essentials)\
Android SQLite Essentials focuses on the core concepts behind building database-driven applications. This book covers the basic and advanced topics with equivalent simplicity and detail, in order to enable readers to quickly grasp and implement the concepts to build an application database.
This book takes a hands-on, example-based approach to help readers understand the core topics of SQLite and Android database-driven applications. This book focuses on providing you with latent as well as widespread knowledge about practices and approaches towards development in an easily understandable manner.
------------------------------------------------------------------------
## SQLite for Mobile Apps Simplified (2014)
Author: Sribatsa Das\
Publisher: Amazon\
[Amazon](https://www.amazon.com/dp/product/B00M3OVSRK)
SQLite for Mobile Apps Simplified is devoted to presenting approach and implementation methodology for using SQLite database in mobile apps. It presents step-by-step examples to create schema, execute transactions and access data from Android, BlackBerry and iOS applications. In addition, it presents ADB Shell and SQLite command-line shell from ADB Shell to access the SQLite Database created by the Android apps. For BlackBerry and iOS application, the book presents ways to access the data using the command line shell.
------------------------------------------------------------------------
## The Definitive Guide to SQLite (2nd edition, 2010)
Authors: Mike Owens and Grant Allen\
Publisher: Apress\
[Amazon](http://www.amazon.com/gp/product/1430232250)
Outside of the world of enterprise computing, there is one database that enables a huge range of software and hardware to flex relational database capabilities, without the baggage and cost of traditional database management systems. That database is SQLite - an embeddable database with an amazingly small footprint, yet able to handle databases of enormous size. SQLite comes equipped with an array of powerful features available through a host of programming and development environments. It is supported by languages such as C, Java, Perl, PHP, Python, Ruby, TCL, and more.
*The Definitive Guide to SQLite, Second Edition* is devoted to complete coverage of the latest version of this powerful database. It offers a thorough overview of SQLite's capabilities and APIs. The book also uses SQLite as the basis for helping newcomers make their first foray into database development. In only a short time you can be writing programs as diverse as a server-side browser plug-in or the next great iPhone or Android application!
------------------------------------------------------------------------
## Using SQLite (2010)
Author: Jay A. Kreibich\
Publisher: O'Reilly Media\
[O'Reilly](http://oreilly.com/catalog/9780596521196/)
Developers, take note: databases aren't just for the IS group any more. You can build database-backed applications for the desktop, Web, embedded systems, or operating systems without linking to heavy-duty client-server databases such as Oracle and MySQL. This book shows how you to use SQLite, a small and lightweight database that you can build right into your application during development. Applications that handle data have an enormous advantage today, and with SQLite, you'll discover how to develop a database-backed application that remains manageable in size and complexity. This book guides you every step of the way. You'll get a crash course in data modeling, become familiar with SQLite's dialect of the SQL database language, and learn how you to work with SQLite using either a scripting language or a C-based language, such as C# or Objective C.Now, even relatively small and nimble applications can be a part of the data revolution. Using SQLite shows you how.
------------------------------------------------------------------------
## SQLite 3 - Einstieg in die Datenbankwelt (2010)
Author: Kay Droessler\
Publisher: Lulu.com\
[Amazon](https://www.amazon.com/product/dp/1445741075)
Die Datenbanksprache SQL ( Structured Query Language ) wird in Datenbanken zur Definition, Manipulation, Sicherung, aber hauptsaechlich zur Abfrage von Daten aus der Datenbank eingesetzt. Unabhaengig vom Betriebssystem oder aufwendigen, benutzerfreundlichen, graphischen Oberflaechen bleibt die Logik aber immer gleich.SQLite ist eine freie Desktop-Datenbank, sie kostet nichts, ist fuer viele Betriebssysteme verfuegbar, schnell heruntergeladen und installiert und auf das Notwendigste reduziert. Fuer den Einsteiger sind das die besten Voraussetzungen, ohne viel Aufwand schnell in die Welt der Datenbanken und Datenbanksprache reinzuschnuppern.Wer nach den Uebungen aber auf den Geschmack gekommen ist, hat schon den groessten Teil an Datenbanken und SQL gelernt, denn alles Besprochene ist Wissen, welches auch auf jedes andere der vielen Datenbanken grundlegend anwendbar ist. Nun koennen Sie auf die richtig Grossen zugehen, vom grossen Fachbuch bis zum riesigen Datenbanksystem.
------------------------------------------------------------------------
## Inside Symbian SQL (2010)
Authors: Ivan Litovski & Richard Maynard\
Publisher: Wiley\
[wiley.com](http://www.wiley.com/WileyCDA/WileyTitle/productCd-0470744022.html)
This is the definitive reference book on the Symbian SQL database which is based on SQLite. The authors (both members of the Symbian engineering team responsible for the implementation of the code) show you how to design code and ease migration from an internal and external point of view, plus they reveal the dos and don'ts of writing high-performance database applications. Packed with resources and sample code, this timely book reveals how to design and tune applications that use the Symbian SQL framework to ultimately improve performance.
With its sample code and insider expertise, this text has everything you need to keep you ahead of the curve.
------------------------------------------------------------------------
## The SQL Guide to SQLite (2009)
Author: Rick F. van der Lans\
Publisher: Lulu.com\
[Amazon](https://www.amazon.com/product/dp/0557076765)
SQLite is a small, fast, embeddable, SQL-based database server. It is easy to install, needs no management, and is open source. This book describes SQLite in detail. With hundreds of examples, plus a proven approach and structure, the book teaches you how to use SQLite efficiently and effectively. It contains a complete description of the SQL dialect as implemented in SQLite version 3.6. The book can be seen as a tutorial and a reference book. Source code for the numerous SQL examples and exercises included in this book can be downloaded from www.r20.nl.
------------------------------------------------------------------------
## An Introduction to SQLite - 2nd Edition (2009)
Author: Naoki Nishizawa\
Publisher: Shoeisha\
[Amazon.jp](https://www.amazon.co.jp/product/dp/479811944X)
This text is written in fluent Japanese specifically for a Japanese audience. This is the second edition of the book - the first edition was published in 2005.
------------------------------------------------------------------------
## Inside SQLite (2007)
Author: Sibsankar Haldar\
Publisher: O'Reilly Media\
[O'Reilly](http://oreilly.com/catalog/9780596550066)
SQLite is a small, zero-configuration, custom-tailored, embeddable, thread-safe, easily maintainable, transaction-oriented, SQL-based, relational database management system. There is no separate install or setup procedure to initialize SQLite before using it. There is no configuration file. SQLite is open source, and is available in the public domain (for more information on open source, visit http://opensource.org). You can download SQLite source code from its homepage https://sqlite.org, compile it using your favorite C compiler, and start using the compiled library. SQLite runs on Linux, Windows, Mac OS X, and a few other operating systems. It has been widely used in low-to-medium tier database applications. This Short Cut discusses design principles, engineering trade-offs, implementation issues, and operations of SQLite. It presents a comprehensive description of all important components of the SQLite engine.
------------------------------------------------------------------------
## SQLite (2004)
Author: Chris Newman\
Publisher: Sams\
[Amazon](https://www.amazon.com/product/dp/067232685X)
SQLite is a small, fast, embeddable database. What makes it popular is the combination of the database engine and interface into a single library as well as the ability to store all the data in a single file. Its functionality lies between MySQL and PostgreSQL, however it is faster than both databases.
In *SQLite*, author Chris Newman provides a thorough, practical guide to using, administering and programming this up-and-coming database. If you want to learn about SQLite or about its use in conjunction with PHP this is the book for you.
---
# Bridging Tcl and JSON with the SQLite Extension
*Sección: Guides | Origen: https://www.sqlite.org/tcljson.html*
# 1. Using SQLite to Bridge Tcl and JSON
[The Tcl SQLite extension](./tclsqlite.md) can act as a bridge to smooth over Tcl's impedance mismatch with JSON, shifting all of the parsing and escaping from Tcl to SQLite with very little effort. The sections below demonstrate techniques for consuming and emitting JSON via SQLite.
## 1.1. Consuming JSON
One of the simplest way to consume and break down a JSON payload is to feed it to SQLite and extract the results using Tcl's `lassign` function:
> \
> set json theJSON...\
> lassign \[db eval {\
> with payload(j) as (select jsonb(\$json)) select\
> -- A simple value:\
> j-\>\>'foo',\
> -- A sub-object or array:\
> CASE WHEN json_valid(j-\>\>'bar') THEN j-\>\>'bar' ELSE NULL END\
> -- Any other fields...\
> from payload\
> }\] foo bar\
Arrays can be injested using `json_each()`:
> \
> set json {\[1, "two", 3.0, {"nested": true}, null\]}\
> set myList \[db eval {\
> select value from json_each(\$json)\
> }\]\
> \
> \# Emits: 1 two 3.0 {{"nested":true}} {}\
Arrays of objects can be decomposed into a list of dict objects:
> \
> set json {\[{"id":1, "v":"A"}, {"id":2, "v":"B"}\]}\
> set myDictList \[db eval {\
> select json_object('id', value-\>\>'id', 'v', value-\>\>'v')\
> from json_each(\$json)\
> }\]\
> \
> \# Emits: {{"id":1,"v":"A"}} {{"id":2,"v":"B"}}\
Object entries in array objects can be decomposed using an approach like the first example shown above.
## 1.2. Emitting JSON: Db Table as a JSON Object
The approach described here uses an in-memory db to incrementally build up a JSON object, automatically smoothing over the edges between data types such as numbers and strings.
> \
> \#\
> \# Initialize, if needed, the sqlite3 connection for the JR temp db and\
> \# return its command name.\
> \#\
> \# JR = JSON Response (to an HTTP request)\
> \#\
> proc jr-db {} {\
> if {"" eq \[info command ::\_\_jrdb\]} {\
> sqlite3 ::\_\_jrdb ":memory:"\
> ::\_\_jrdb eval {\
> -- Holds a list of key/value pairs for a JSON response object\
> create table jr(k TEXT UNIQUE ON CONFLICT REPLACE,v ANY);\
> }\
> }\
> return ::\_\_jrdb\
> }\
> \
> \#\
> \# Remove all entries from the JR buffer.\
> \#\
> proc jr-reset {args} {\
> \[jr-db\] eval {delete from jr}\
> }\
> \
> \#\
> \# Set one or more key/value pairs in the JR object.\
> \#\
> proc jr-set {args} {\
> set db \[jr-db\]\
> foreach {k v} \$args {\
> \$db eval {insert into jr(k,v) values(\$k,\$v)}\
> }\
> }\
> \
> \#\
> \# Returns a JSON-format object representing the current JR state.\
> \#\
> proc jr-get {} {\
> \[jr-db\] onecolumn {\
> select json_group_object(k,CASE WHEN json_valid(v,1)\
> THEN json(v) ELSE v END) from jr\
> }\
> }\
Example usage:
> \
> jr-set message "This is a message."\
> jr-set aBool true isNull null anInt 37 aFloat 42.42\
> puts \[jr-get\]\
Results in:
> \
> {"message":"This is a message.","aBool":true,"isNull":null,"anInt":37,"aFloat":42.42}\
## 1.3. Emitting JSON: Incremental Build-up
The approach shown here uses a couple of routines to incrementally build up a nested object or array, faithfully navigating the type handling, such that integers, null, and boolean-looking values can be emitted as such instead of strings.
> \
> \#\
> \# Returns the command name of the shared SQLite3 instance used by the\
> \# X-to-JSON APIs, initializing it on demand.\
> \#\
> proc json-db {} {\
> if {"" eq \[info command ::\_\_jsonDb\]} {\
> sqlite3 ::\_\_jsonDb ":memory:"\
> }\
> return ::\_\_jsonDb\
> }\
> \
> \#\
> \# Given a dict-style object, this creates a JSON object representation.\
> \# It does not handle nested objects but each value may itself be the result\
> \# of its own call to this method, which has a similar effect.\
> \#\
> proc json-obj {kvps} {\
> set q "select json_object("\
> set n 0\
> set nn 1\
> foreach {k v} \$kvps {\
> set \$n \$k\
> set \$nn \$v\
> if {\$n} {append q ","}\
> append q "\\\$n, CASE WHEN json_valid(\\\$nn) THEN json(\\\$nn) ELSE \\\$nn END"\
> # This may look like an SQL injection opportunity, but it's\
> # injecting prepared statement placeholders, not values.\
> incr n 2\
> incr nn 2\
> }\
> append q ")"\
> \[json-db\] onecolumn \$q\
> }\
> \
> \#\
> \# Returns a JSON-format array of the given arguments. See json-object\
> \# for notes about nesting.\
> \#\
> proc json-array {args} {\
> set n 0\
> set q "select json_array("\
> foreach a \$args {\
> set \$n \$a\
> if {\$n} {append q ","}\
> append q "CASE WHEN json_valid(\\\$n) THEN json(\\\$n) ELSE \\\$n END"\
> incr n\
> }\
> append q ")"\
> \[json-db\] onecolumn \$q\
> }\
Example usage:
> \
> proc json-pretty {arg {space " "}} {\
> \[json-db\] onecolumn {select json_pretty(\$arg,\$space)}\
> }\
> set o {\
> hi world\
> number 17.3\
> truth true\
> lies false\
> nil null\
> nada "null"\
> notNull "Null"\
> }\
> lappend o list \[json-array hello there \[json-obj {nested true}\]\]\
> lappend o obj \[json-obj {name "Nested object"}\]\
> puts \[json-pretty \[json-obj \$o\]\]\
Results in:
> {\
> "hi": "world",\
> "number": 17.3,\
> "truth": true,\
> "lies": false,\
> "nil": null,\
> "nada": null,\
> "notNull": "Null",\
> "list": \[\
> "hello",\
> "there",\
> {\
> "nested": true\
> }\
> \],\
> "obj": {\
> "name": "Nested object"\
> }\
> }\
---
# C/C++ Interface For SQLite Version 3 (old)
*Sección: Guides | Origen: https://www.sqlite.org/capi3.html*
**Note:** This document was written in 2004 as a guide to helping programmers move from using SQLite version 2 to SQLite version 3. The information in this document is still essentially correct, however there have been many changes and enhancements over the years. We recommend that the following documents be used instead:
- [An Introduction To The SQLite C/C++ Interface](cintro.md)
- [SQLite C/C++ Reference Guide](c3ref/intro.md)
## C/C++ Interface For SQLite Version 3
### 1.0 Overview
SQLite version 3.0 is a new version of SQLite, derived from the SQLite 2.8.13 code base, but with an incompatible file format and API. SQLite version 3.0 was created to answer demand for the following features:
- Support for UTF-16.
- User-definable text collating sequences.
- The ability to store BLOBs in indexed columns.
It was necessary to move to version 3.0 to implement these features because each requires incompatible changes to the database file format. Other incompatible changes, such as a cleanup of the API, were introduced at the same time under the theory that it is best to get your incompatible changes out of the way all at once.
The API for version 3.0 is similar to the version 2.X API, but with some important changes. Most noticeably, the "`sqlite_`" prefix that occurs on the beginning of all API functions and data structures are changed to "`sqlite3_`". This avoids confusion between the two APIs and allows linking against both SQLite 2.X and SQLite 3.0 at the same time.
There is no agreement on what the C datatype for a UTF-16 string should be. Therefore, SQLite uses a generic type of void\* to refer to UTF-16 strings. Client software can cast the void\* to whatever datatype is appropriate for their system.
### 2.0 C/C++ Interface
The API for SQLite 3.0 includes 83 separate functions in addition to several data structures and \#defines. (A complete [API reference](c3ref/intro.md) is provided as a separate document.) Fortunately, the interface is not nearly as complex as its size implies. Simple programs can still make do with only 3 functions: [sqlite3_open()](c3ref/open.md), [sqlite3_exec()](c3ref/exec.md), and [sqlite3_close()](c3ref/close.md). More control over the execution of the database engine is provided using [sqlite3_prepare_v2()](c3ref/prepare.md) to compile an SQLite statement into byte code and [sqlite3_step()](c3ref/step.md) to execute that bytecode. A family of routines with names beginning with [sqlite3_column\_](c3ref/column_blob.md) is used to extract information about the result set of a query. Many interface functions come in pairs, with both a UTF-8 and UTF-16 version. And there is a collection of routines used to implement user-defined SQL functions and user-defined text collating sequences.
#### 2.1 Opening and closing a database
> \
> typedef struct sqlite3 sqlite3;\
> int sqlite3_open(const char\*, sqlite3\*\*);\
> int sqlite3_open16(const void\*, sqlite3\*\*);\
> int sqlite3_close(sqlite3\*);\
> const char \*sqlite3_errmsg(sqlite3\*);\
> const void \*sqlite3_errmsg16(sqlite3\*);\
> int sqlite3_errcode(sqlite3\*);\
The sqlite3_open() routine returns an integer error code rather than a pointer to the sqlite3 structure as the version 2 interface did. The difference between sqlite3_open() and sqlite3_open16() is that sqlite3_open16() takes UTF-16 (in host native byte order) for the name of the database file. If a new database file needs to be created, then sqlite3_open16() sets the internal text representation to UTF-16 whereas sqlite3_open() sets the text representation to UTF-8.
The opening and/or creating of the database file is deferred until the file is actually needed. This allows options and parameters, such as the native text representation and default page size, to be set using PRAGMA statements.
The sqlite3_errcode() routine returns a result code for the most recent major API call. sqlite3_errmsg() returns an English-language text error message for the most recent error. The error message is represented in UTF-8 and will be ephemeral - it could disappear on the next call to any SQLite API function. sqlite3_errmsg16() works like sqlite3_errmsg() except that it returns the error message represented as UTF-16 in host native byte order.
The error codes for SQLite version 3 are unchanged from version 2. They are as follows:
> \
> \#define SQLITE_OK 0 /\* Successful result \*/\
> \#define SQLITE_ERROR 1 /\* SQL error or missing database \*/\
> \#define SQLITE_INTERNAL 2 /\* An internal logic error in SQLite \*/\
> \#define SQLITE_PERM 3 /\* Access permission denied \*/\
> \#define SQLITE_ABORT 4 /\* Callback routine requested an abort \*/\
> \#define SQLITE_BUSY 5 /\* The database file is locked \*/\
> \#define SQLITE_LOCKED 6 /\* A table in the database is locked \*/\
> \#define SQLITE_NOMEM 7 /\* A malloc() failed \*/\
> \#define SQLITE_READONLY 8 /\* Attempt to write a readonly database \*/\
> \#define SQLITE_INTERRUPT 9 /\* Operation terminated by sqlite_interrupt() \*/\
> \#define SQLITE_IOERR 10 /\* Some kind of disk I/O error occurred \*/\
> \#define SQLITE_CORRUPT 11 /\* The database disk image is malformed \*/\
> \#define SQLITE_NOTFOUND 12 /\* (Internal Only) Table or record not found \*/\
> \#define SQLITE_FULL 13 /\* Insertion failed because database is full \*/\
> \#define SQLITE_CANTOPEN 14 /\* Unable to open the database file \*/\
> \#define SQLITE_PROTOCOL 15 /\* Database lock protocol error \*/\
> \#define SQLITE_EMPTY 16 /\* (Internal Only) Database table is empty \*/\
> \#define SQLITE_SCHEMA 17 /\* The database schema changed \*/\
> \#define SQLITE_TOOBIG 18 /\* Too much data for one row of a table \*/\
> \#define SQLITE_CONSTRAINT 19 /\* Abort due to contraint violation \*/\
> \#define SQLITE_MISMATCH 20 /\* Data type mismatch \*/\
> \#define SQLITE_MISUSE 21 /\* Library used incorrectly \*/\
> \#define SQLITE_NOLFS 22 /\* Uses OS features not supported on host \*/\
> \#define SQLITE_AUTH 23 /\* Authorization denied \*/\
> \#define SQLITE_ROW 100 /\* sqlite_step() has another row ready \*/\
> \#define SQLITE_DONE 101 /\* sqlite_step() has finished executing \*/\
#### 2.2 Executing SQL statements
> \
> typedef int (\*sqlite_callback)(void\*,int,char\*\*, char\*\*);\
> int sqlite3_exec(sqlite3\*, const char \*sql, sqlite_callback, void\*, char\*\*);\
The [sqlite3_exec()](c3ref/exec.md) function works much as it did in SQLite version 2. Zero or more SQL statements specified in the second parameter are compiled and executed. Query results are returned to a callback routine.
In SQLite version 3, the sqlite3_exec routine is just a wrapper around calls to the prepared statement interface.
> \
> typedef struct sqlite3_stmt sqlite3_stmt;\
> int sqlite3_prepare(sqlite3\*, const char\*, int, sqlite3_stmt\*\*, const char\*\*);\
> int sqlite3_prepare16(sqlite3\*, const void\*, int, sqlite3_stmt\*\*, const void\*\*);\
> int sqlite3_finalize(sqlite3_stmt\*);\
> int sqlite3_reset(sqlite3_stmt\*);\
The sqlite3_prepare interface compiles a single SQL statement into byte code for later execution. This interface is now the preferred way of accessing the database.
The SQL statement is a UTF-8 string for sqlite3_prepare(). The sqlite3_prepare16() works the same way except that it expects a UTF-16 string as SQL input. Only the first SQL statement in the input string is compiled. The fifth parameter is filled in with a pointer to the next (uncompiled) SQLite statement in the input string, if any. The sqlite3_finalize() routine deallocates a prepared SQL statement. All prepared statements must be finalized before the database can be closed. The sqlite3_reset() routine resets a prepared SQL statement so that it can be executed again.
The SQL statement may contain tokens of the form "?" or "?nnn" or ":aaa" where "nnn" is an integer and "aaa" is an identifier. Such tokens represent unspecified literal values (or "wildcards") to be filled in later by the [sqlite3_bind](c3ref/bind_blob.md) interface. Each wildcard has an associated number which is its sequence in the statement or the "nnn" in the case of a "?nnn" form. It is allowed for the same wildcard to occur more than once in the same SQL statement, in which case all instance of that wildcard will be filled in with the same value. Unbound wildcards have a value of NULL.
> \
> int sqlite3_bind_blob(sqlite3_stmt\*, int, const void\*, int n, void(\*)(void\*));\
> int sqlite3_bind_double(sqlite3_stmt\*, int, double);\
> int sqlite3_bind_int(sqlite3_stmt\*, int, int);\
> int sqlite3_bind_int64(sqlite3_stmt\*, int, long long int);\
> int sqlite3_bind_null(sqlite3_stmt\*, int);\
> int sqlite3_bind_text(sqlite3_stmt\*, int, const char\*, int n, void(\*)(void\*));\
> int sqlite3_bind_text16(sqlite3_stmt\*, int, const void\*, int n, void(\*)(void\*));\
> int sqlite3_bind_value(sqlite3_stmt\*, int, const sqlite3_value\*);\
There is an assortment of sqlite3_bind routines used to assign values to wildcards in a prepared SQL statement. Unbound wildcards are interpreted as NULLs. Bindings are not reset by sqlite3_reset(). But wildcards can be rebound to new values after an sqlite3_reset().
After an SQL statement has been prepared (and optionally bound), it is executed using:
> \
> int sqlite3_step(sqlite3_stmt\*);\
The sqlite3_step() routine returns SQLITE_ROW if it is returning a single row of the result set, or SQLITE_DONE if execution has completed, either normally or due to an error. It might also return SQLITE_BUSY if it is unable to open the database file. If the return value is SQLITE_ROW, then the following routines can be used to extract information about that row of the result set:
> \
> const void \*sqlite3_column_blob(sqlite3_stmt\*, int iCol);\
> int sqlite3_column_bytes(sqlite3_stmt\*, int iCol);\
> int sqlite3_column_bytes16(sqlite3_stmt\*, int iCol);\
> int sqlite3_column_count(sqlite3_stmt\*);\
> const char \*sqlite3_column_decltype(sqlite3_stmt \*, int iCol);\
> const void \*sqlite3_column_decltype16(sqlite3_stmt \*, int iCol);\
> double sqlite3_column_double(sqlite3_stmt\*, int iCol);\
> int sqlite3_column_int(sqlite3_stmt\*, int iCol);\
> long long int sqlite3_column_int64(sqlite3_stmt\*, int iCol);\
> const char \*sqlite3_column_name(sqlite3_stmt\*, int iCol);\
> const void \*sqlite3_column_name16(sqlite3_stmt\*, int iCol);\
> const unsigned char \*sqlite3_column_text(sqlite3_stmt\*, int iCol);\
> const void \*sqlite3_column_text16(sqlite3_stmt\*, int iCol);\
> int sqlite3_column_type(sqlite3_stmt\*, int iCol);\
The [sqlite3_column_count()](c3ref/column_count.md) function returns the number of columns in the results set. sqlite3_column_count() can be called at any time after [sqlite3_prepare_v2()](c3ref/prepare.md). [sqlite3_data_count()](c3ref/data_count.md) works similarly to [sqlite3_column_count()](c3ref/column_count.md) except that it only works following [sqlite3_step()](c3ref/step.md). If the previous call to [sqlite3_step()](c3ref/step.md) returned SQLITE_DONE or an error code, then [sqlite3_data_count()](c3ref/data_count.md) will return 0 whereas [sqlite3_column_count()](c3ref/column_count.md) will continue to return the number of columns in the result set.
Returned data is examined using the other [sqlite3_column\_\*\*\*()](c3ref/column_blob.md) functions, all of which take a column number as their second parameter. Columns are zero-indexed from left to right. Note that this is different to parameters, which are indexed starting at one.
The [sqlite3_column_type()](c3ref/column_blob.md) function returns the datatype for the value in the Nth column. The return value is one of these:
> \
> #define SQLITE_INTEGER 1\
> #define SQLITE_FLOAT 2\
> #define SQLITE_TEXT 3\
> #define SQLITE_BLOB 4\
> #define SQLITE_NULL 5\
The sqlite3_column_decltype() routine returns text which is the declared type of the column in the CREATE TABLE statement. For an expression, the return type is an empty string. sqlite3_column_name() returns the name of the Nth column. sqlite3_column_bytes() returns the number of bytes in a column that has type BLOB or the number of bytes in a TEXT string with UTF-8 encoding. sqlite3_column_bytes16() returns the same value for BLOBs but for TEXT strings returns the number of bytes in a UTF-16 encoding.
- sqlite3_column_blob() return BLOB data.
- sqlite3_column_text() return TEXT data as UTF-8.
- sqlite3_column_text16() return TEXT data as UTF-16.
- sqlite3_column_int() return INTEGER data in the host machines native integer format.
- sqlite3_column_int64() returns 64-bit INTEGER data.
- Finally, sqlite3_column_double() return floating point data.
It is not necessary to retrieve data in the format specified by sqlite3_column_type(). If a different format is requested, the data is converted automatically.
Data format conversions can invalidate the pointer returned by prior calls to sqlite3_column_blob(), sqlite3_column_text(), and/or sqlite3_column_text16(). Pointers might be invalided in the following cases:
- The initial content is a BLOB and sqlite3_column_text() or sqlite3_column_text16() is called. A zero-terminator might need to be added to the string.
- The initial content is UTF-8 text and sqlite3_column_bytes16() or sqlite3_column_text16() is called. The content must be converted to UTF-16.
- The initial content is UTF-16 text and sqlite3_column_bytes() or sqlite3_column_text() is called. The content must be converted to UTF-8.
Note that conversions between UTF-16be and UTF-16le are always done in place and do not invalidate a prior pointer, though of course the content of the buffer that the prior pointer points to will have been modified. Other kinds of conversion are done in place when it is possible, but sometime it is not possible and in those cases prior pointers are invalidated.
The safest and easiest to remember policy is this: assume that any result from
- sqlite3_column_blob(),
- sqlite3_column_text(), or
- sqlite3_column_text16()
is invalided by subsequent calls to
- sqlite3_column_bytes(),
- sqlite3_column_bytes16(),
- sqlite3_column_text(), or
- sqlite3_column_text16().
This means that you should always call sqlite3_column_bytes() or sqlite3_column_bytes16() before calling sqlite3_column_blob(), sqlite3_column_text(), or sqlite3_column_text16().
#### 2.3 User-defined functions
User defined functions can be created using the following routine:
> \
> typedef struct sqlite3_value sqlite3_value;\
> int sqlite3_create_function(\
> sqlite3 \*,\
> const char \*zFunctionName,\
> int nArg,\
> int eTextRep,\
> void\*,\
> void (\*xFunc)(sqlite3_context\*,int,sqlite3_value\*\*),\
> void (\*xStep)(sqlite3_context\*,int,sqlite3_value\*\*),\
> void (\*xFinal)(sqlite3_context\*)\
> );\
> int sqlite3_create_function16(\
> sqlite3\*,\
> const void \*zFunctionName,\
> int nArg,\
> int eTextRep,\
> void\*,\
> void (\*xFunc)(sqlite3_context\*,int,sqlite3_value\*\*),\
> void (\*xStep)(sqlite3_context\*,int,sqlite3_value\*\*),\
> void (\*xFinal)(sqlite3_context\*)\
> );\
> #define SQLITE_UTF8 1\
> #define SQLITE_UTF16 2\
> #define SQLITE_UTF16BE 3\
> #define SQLITE_UTF16LE 4\
> #define SQLITE_ANY 5\
The nArg parameter specifies the number of arguments to the function. A value of 0 indicates that any number of arguments is allowed. The eTextRep parameter specifies what representation text values are expected to be in for arguments to this function. The value of this parameter should be one of the parameters defined above. SQLite version 3 allows multiple implementations of the same function using different text representations. The database engine chooses the function that minimizes the number of text conversions required.
Normal functions specify only xFunc and leave xStep and xFinal set to NULL. Aggregate functions specify xStep and xFinal and leave xFunc set to NULL. There is no separate sqlite3_create_aggregate() API.
The function name is specified in UTF-8. A separate sqlite3_create_function16() API works the same as sqlite_create_function() except that the function name is specified in UTF-16 host byte order.
Notice that the parameters to functions are now pointers to sqlite3_value structures instead of pointers to strings as in SQLite version 2.X. The following routines are used to extract useful information from these "values":
> \
> const void \*sqlite3_value_blob(sqlite3_value\*);\
> int sqlite3_value_bytes(sqlite3_value\*);\
> int sqlite3_value_bytes16(sqlite3_value\*);\
> double sqlite3_value_double(sqlite3_value\*);\
> int sqlite3_value_int(sqlite3_value\*);\
> long long int sqlite3_value_int64(sqlite3_value\*);\
> const unsigned char \*sqlite3_value_text(sqlite3_value\*);\
> const void \*sqlite3_value_text16(sqlite3_value\*);\
> int sqlite3_value_type(sqlite3_value\*);\
Function implementations use the following APIs to acquire context and to report results:
> \
> void \*sqlite3_aggregate_context(sqlite3_context\*, int nbyte);\
> void \*sqlite3_user_data(sqlite3_context\*);\
> void sqlite3_result_blob(sqlite3_context\*, const void\*, int n, void(\*)(void\*));\
> void sqlite3_result_double(sqlite3_context\*, double);\
> void sqlite3_result_error(sqlite3_context\*, const char\*, int);\
> void sqlite3_result_error16(sqlite3_context\*, const void\*, int);\
> void sqlite3_result_int(sqlite3_context\*, int);\
> void sqlite3_result_int64(sqlite3_context\*, long long int);\
> void sqlite3_result_null(sqlite3_context\*);\
> void sqlite3_result_text(sqlite3_context\*, const char\*, int n, void(\*)(void\*));\
> void sqlite3_result_text16(sqlite3_context\*, const void\*, int n, void(\*)(void\*));\
> void sqlite3_result_value(sqlite3_context\*, sqlite3_value\*);\
> void \*sqlite3_get_auxdata(sqlite3_context\*, int);\
> void sqlite3_set_auxdata(sqlite3_context\*, int, void\*, void (\*)(void\*));\
#### 2.4 User-defined collating sequences
The following routines are used to implement user-defined collating sequences:
> \
> sqlite3_create_collation(sqlite3\*, const char \*zName, int eTextRep, void\*,\
> int(\*xCompare)(void\*,int,const void\*,int,const void\*));\
> sqlite3_create_collation16(sqlite3\*, const void \*zName, int eTextRep, void\*,\
> int(\*xCompare)(void\*,int,const void\*,int,const void\*));\
> sqlite3_collation_needed(sqlite3\*, void\*, \
> void(\*)(void\*,sqlite3\*,int eTextRep,const char\*));\
> sqlite3_collation_needed16(sqlite3\*, void\*,\
> void(\*)(void\*,sqlite3\*,int eTextRep,const void\*));\
The sqlite3_create_collation() function specifies a collating sequence name and a comparison function to implement that collating sequence. The comparison function is only used for comparing text values. The eTextRep parameter is one of SQLITE_UTF8, SQLITE_UTF16LE, SQLITE_UTF16BE, or SQLITE_ANY to specify which text representation the comparison function works with. Separate comparison functions can exist for the same collating sequence for each of the UTF-8, UTF-16LE and UTF-16BE text representations. The sqlite3_create_collation16() works like sqlite3_create_collation() except that the collation name is specified in UTF-16 host byte order instead of in UTF-8.
The sqlite3_collation_needed() routine registers a callback which the database engine will invoke if it encounters an unknown collating sequence. The callback can lookup an appropriate comparison function and invoke sqlite_3_create_collation() as needed. The fourth parameter to the callback is the name of the collating sequence in UTF-8. For sqlite3_collation_need16() the callback sends the collating sequence name in UTF-16 host byte order.
---
# Change in Default Page Size in SQLite Version 3.12.0
*Sección: Guides | Origen: https://www.sqlite.org/pgszchng2016.html*
# The Default Page Size Change of SQLite 3.12.0
## 1.0 Introduction
An SQLite database file consists of one or more "pages". For a single database file, all pages are the same size, though for different database files, the page size can be any power of two between 512 and 65536, inclusive.
Since the SQLite database file format was designed (in 2003) the default [page size](pragma.md#pragma_page_size) for new databases has been 1024 bytes. This was a reasonable choice in 2003. But on modern hardware, a 4096 byte page is a faster and better choice. So, beginning with SQLite [version 3.12.0](releaselog/3_12_0.md) (2016-03-29)) the default page size for new database files has been increased to 4096 bytes.
The upper bound on the database [cache size](pragma.md#pragma_cache_size) has traditionally defaulted to 2000 pages. SQLite [version 3.12.0](releaselog/3_12_0.md) also changes this default setting to be "-2000" which means 2000\*1024 bytes, regardless of page size. So, the upper bound on the amount of memory used for the page cache is unchanged.
## 2.0 Not a Compatibility Break
These changes in the default behavior of SQLite are not a compatibility break. All legacy database files continue to be readable and writable by newer versions of SQLite, and all newly created database files continue to be readable and writable by legacy versions of the SQLite library. The only thing that is changing is some default settings. This should result in a performance increase for many applications.
Though most applications should not notice any change (except that they run a little faster), if problems arise then the legacy behavior can be restored at compile-time by using the following options to the C-compiler:
> \
> -DSQLITE_DEFAULT_PAGE_SIZE=1024 \
> -DSQLITE_DEFAULT_CACHE_SIZE=2000\
The page size and cache size can also be set or changed at run-time using the [page_size pragma](pragma.md#pragma_page_size) and [cache_size pragma](pragma.md#pragma_cache_size), respectively.
## 3.0 Possible Negative Consequences Of This Change
The minimum size of an SQLite database is one page for each table and each index. With a larger page size, the size of an empty database for a given schema will grow by a factor of four, therefore. However, once the database begins to fill with content the size of the older 1024-byte page databases and the newer 4096-byte page databases will quickly converge. Due to relaxed bin-packing constraints, the 4096-byte page size might actually result in a smaller file, once substantial content is added.
---
# Changegroup Handle
*Sección: Guides | Origen: https://www.sqlite.org/session/changegroup.html*
[](../session/intro.md)
## Session Module C Interface
## Changegroup Handle
> typedef struct sqlite3_changegroup sqlite3_changegroup;\
A changegroup is an object used to combine two or more [changesets](../sessionintro.md#changeset) or [patchsets](../sessionintro.md#changeset)
Constructor: [sqlite3changegroup_new()](../session/sqlite3changegroup_new.md)
Destructor: [sqlite3changegroup_delete()](../session/sqlite3changegroup_delete.md)
Methods: [sqlite3changegroup_add()](../session/sqlite3changegroup_add.md), [sqlite3changegroup_add_change()](../session/sqlite3changegroup_add_change.md), [sqlite3changegroup_output()](../session/sqlite3changegroup_output.md)
See also lists of [Objects](../session/objlist.md), [Constants](../session/constlist.md), and [Functions](../session/funclist.md).
---
# Changeset Iterator Handle
*Sección: Guides | Origen: https://www.sqlite.org/session/changeset_iter.html*
[](../session/intro.md)
## Session Module C Interface
## Changeset Iterator Handle
> typedef struct sqlite3_changeset_iter sqlite3_changeset_iter;\
An instance of this object acts as a cursor for iterating over the elements of a [changeset](../sessionintro.md#changeset) or [patchset](../sessionintro.md#changeset).
Constructors: [sqlite3changeset_start()](../session/sqlite3changeset_start.md), [sqlite3changeset_start_v2()](../session/sqlite3changeset_start.md)
- [sqlite3changeset_conflict](../session/sqlite3changeset_conflict.md)
- [sqlite3changeset_finalize](../session/sqlite3changeset_finalize.md)
- [sqlite3changeset_fk_conflicts](../session/sqlite3changeset_fk_conflicts.md)
- [sqlite3changeset_new](../session/sqlite3changeset_new.md)
- [sqlite3changeset_next](../session/sqlite3changeset_next.md)
- [sqlite3changeset_old](../session/sqlite3changeset_old.md)
- [sqlite3changeset_op](../session/sqlite3changeset_op.md)
- [sqlite3changeset_pk](../session/sqlite3changeset_pk.md)
See also lists of [Objects](../session/objlist.md), [Constants](../session/constlist.md), and [Functions](../session/funclist.md).
---
# Clustered Indexes and the WITHOUT ROWID Optimization
*Sección: Guides | Origen: https://www.sqlite.org/withoutrowid.html*
# 1. Introduction
By default, every row in SQLite has a special column, usually called the "[rowid](lang_createtable.md#rowid)", that uniquely identifies that row within the table. However if the phrase "WITHOUT ROWID" is added to the end of a [CREATE TABLE](lang_createtable.md) statement, then the special "rowid" column is omitted. There are sometimes space and performance advantages to omitting the rowid.
A WITHOUT ROWID table is a table that uses a [Clustered Index](https://en.wikipedia.org/wiki/Database_index#Clustered) as the primary key.
## 1.1. Syntax
To create a WITHOUT ROWID table, simply add the keywords "WITHOUT ROWID" to the end of the [CREATE TABLE](lang_createtable.md) statement. For example:
> \
> CREATE TABLE IF NOT EXISTS wordcount(\
> word TEXT PRIMARY KEY,\
> cnt INTEGER\
> ) **WITHOUT ROWID**;\
As with all SQL syntax, the case of the keywords does not matter. One can write "WITHOUT rowid" or "without rowid" or "WiThOuT rOwId" and it will mean the same thing.
Every WITHOUT ROWID table must have a [PRIMARY KEY](lang_createtable.md#primkeyconst). An error is raised if a CREATE TABLE statement with the WITHOUT ROWID clause lacks a PRIMARY KEY.
In most contexts, the special "rowid" column of normal tables can also be called "oid" or "\_rowid\_". However, only "rowid" works as the keyword in the CREATE TABLE statement.
## 1.2. Compatibility
SQLite [version 3.8.2](releaselog/3_8_2.md) (2013-12-06) or later is necessary in order to use a WITHOUT ROWID table. An attempt to open a database that contains one or more WITHOUT ROWID tables using an earlier version of SQLite will result in a "malformed database schema" error.
## 1.3. Quirks
WITHOUT ROWID is found only in SQLite and is not compatible with any other SQL database engine, as far as we know. In an elegant system, all tables would behave as WITHOUT ROWID tables even without the WITHOUT ROWID keyword. However, when SQLite was first designed, it used only integer [rowids](lang_createtable.md#rowid) for row keys to simplify the implementation. This approach worked well for many years. But as the demands on SQLite grew, the need for tables in which the PRIMARY KEY really did correspond to the underlying row key grew more acute. The WITHOUT ROWID concept was added in order to meet that need without breaking backwards compatibility with the billions of SQLite databases already in use at the time (circa 2013).
# 2. Differences From Ordinary Rowid Tables
The WITHOUT ROWID syntax is an optimization. It provides no new capabilities. Anything that can be done using a WITHOUT ROWID table can also be done in exactly the same way, and exactly the same syntax, using an ordinary rowid table. The only advantage of a WITHOUT ROWID table is that it can sometimes use less disk space and/or perform a little faster than an ordinary rowid table.
For the most part, ordinary rowid tables and WITHOUT ROWID tables are interchangeable. But there are some additional restrictions on WITHOUT ROWID tables that do not apply to ordinary rowid tables:
1. **Every WITHOUT ROWID table must have a PRIMARY KEY.** An attempt to create a WITHOUT ROWID table without a PRIMARY KEY results in an error.
2. **The special behaviors associated with "[INTEGER PRIMARY KEY](lang_createtable.md#rowid)" do not apply on WITHOUT ROWID tables.** In an ordinary table, "INTEGER PRIMARY KEY" means that the column is an alias for the rowid. But since there is no rowid in a WITHOUT ROWID table, that special meaning no longer applies. An "INTEGER PRIMARY KEY" column in a WITHOUT ROWID table works like an "INT PRIMARY KEY" column in an ordinary table: It is a PRIMARY KEY that has integer [affinity](datatype3.md#affinity).
3. **[AUTOINCREMENT](autoinc.md) does not work on WITHOUT ROWID tables.** The [AUTOINCREMENT](autoinc.md) mechanism assumes the presence of a rowid and so it does not work on a WITHOUT ROWID table. An error is raised if the "AUTOINCREMENT" keyword is used in the CREATE TABLE statement for a WITHOUT ROWID table.
4. **NOT NULL is enforced on every column of the PRIMARY KEY in a WITHOUT ROWID table.** This is in accordance with the SQL standard. Each column of a PRIMARY KEY is supposed to be individually NOT NULL. However, NOT NULL was not enforced on PRIMARY KEY columns by early versions of SQLite due to a bug. By the time that this bug was discovered, so many SQLite databases were already in circulation that the decision was made not to fix this bug for fear of breaking compatibility. So, ordinary rowid tables in SQLite violate the SQL standard and allow NULL values in PRIMARY KEY fields. But WITHOUT ROWID tables do follow the standard and will throw an error on any attempt to insert a NULL into a PRIMARY KEY column.
5. **The [sqlite3_last_insert_rowid()](c3ref/last_insert_rowid.md) function does not work for WITHOUT ROWID tables.** Inserts into a WITHOUT ROWID do not change the value returned by the [sqlite3_last_insert_rowid()](c3ref/last_insert_rowid.md) function. The [last_insert_rowid()](lang_corefunc.md#last_insert_rowid) SQL function is also unaffected since it is just a wrapper around [sqlite3_last_insert_rowid()](c3ref/last_insert_rowid.md).
6. **The [incremental blob I/O](c3ref/blob_open.md) mechanism does not work for WITHOUT ROWID tables.** Incremental BLOB I/O uses the rowid to create an [sqlite3_blob](c3ref/blob.md) object for doing the direct I/O. However, WITHOUT ROWID tables do not have a rowid, and so there is no way to create an [sqlite3_blob](c3ref/blob.md) object for a WITHOUT ROWID table.
7. **The [sqlite3_update_hook()](c3ref/update_hook.md) interface does not fire callbacks for changes to a WITHOUT ROWID table.** Part of the callback from [sqlite3_update_hook()](c3ref/update_hook.md) is the rowid of the table row that has changed. However, WITHOUT ROWID tables do not have a rowid. Hence, the update hook is not invoked when a WITHOUT ROWID table changes.
# 3. Benefits Of WITHOUT ROWID Tables
A WITHOUT ROWID table is an optimization that can reduce storage and processing requirements.
In an ordinary SQLite table, the PRIMARY KEY is really just a [UNIQUE](lang_createtable.md#uniqueconst) index. The key used to look up records on disk is the [rowid](lang_createtable.md#rowid). The special "[INTEGER PRIMARY KEY](lang_createtable.md#rowid)" column type in ordinary SQLite tables causes the column to be an alias for the rowid, and so an INTEGER PRIMARY KEY is a true PRIMARY KEY. But any other kind of PRIMARY KEYs, including "INT PRIMARY KEY" are just unique indexes in an ordinary rowid table.
Consider a table (shown below) intended to store a vocabulary of words together with a count of the number of occurrences of each word in some text corpus:
> \
> CREATE TABLE IF NOT EXISTS wordcount(\
> word TEXT PRIMARY KEY,\
> cnt INTEGER\
> );\
As an ordinary SQLite table, "wordcount" is implemented as two separate B-Trees. The main table uses the hidden rowid value as the key and stores the "word" and "cnt" columns as data. The "TEXT PRIMARY KEY" phrase of the CREATE TABLE statement causes the creation of an [unique index](lang_createindex.md#uniqueidx) on the "word" column. This index is a separate B-Tree that uses "word" and the "rowid" as the key and stores no data at all. Note that the complete text of every "word" is stored twice: once in the main table and again in the index.
Consider querying this table to find the number of occurrences of the word "xsync":
> \
> SELECT cnt FROM wordcount WHERE word='xsync';\
This query first has to search the index B-Tree looking for any entry that contains the matching value for "word". When an entry is found in the index, the rowid is extracted and used to search the main table. Then the "cnt" value is read out of the main table and returned. Hence, two separate binary searches are required to fulfill the request.
A WITHOUT ROWID table uses a different data design for the equivalent table.
> \
> CREATE TABLE IF NOT EXISTS wordcount(\
> word TEXT PRIMARY KEY,\
> cnt INTEGER\
> ) WITHOUT ROWID;\
In this latter table, there is only a single B-Tree which uses the "word" column as its key and the "cnt" column as its data. (Technicality: the low-level implementation actually stores both "word" and "cnt" in the "key" area of the B-Tree. But unless you are looking at the low-level byte encoding of the database file, that fact is unimportant.) Because there is only a single B-Tree, the text of the "word" column is only stored once in the database. Furthermore, querying the "cnt" value for a specific "word" only involves a single binary search into the main B-Tree, since the "cnt" value can be retrieved directly from the record found by that first search and without the need to do a second binary search on the rowid.
Thus, in some cases, a WITHOUT ROWID table can use about half the amount of disk space and can operate nearly twice as fast. Of course, in a real-world schema, there will typically be secondary indices and/or UNIQUE constraints, and the situation is more complicated. But even then, there can often be space and performance advantages to using WITHOUT ROWID on tables that have non-integer or composite PRIMARY KEYs.
# 4. When To Use WITHOUT ROWID
The WITHOUT ROWID optimization is likely to be helpful for tables that have non-integer or composite (multi-column) PRIMARY KEYs and that do not store large strings or BLOBs.
WITHOUT ROWID tables will work correctly (that is to say, they provide the correct answer) for tables with a single INTEGER PRIMARY KEY. However, ordinary rowid tables will run faster in that case. Hence, it is good design to avoid creating WITHOUT ROWID tables with single-column PRIMARY KEYs of type INTEGER.
WITHOUT ROWID tables work best when individual rows are not too large. A good rule-of-thumb is that the average size of a single row in a WITHOUT ROWID table should be less than about 1/20th the size of a database page. That means that rows should not contain more than about 50 bytes each for a 1KiB page size or about 200 bytes each for 4KiB page size. WITHOUT ROWID tables will work (in the sense that they get the correct answer) for arbitrarily large rows - up to 2GB in size - but traditional rowid tables tend to work faster for large row sizes. This is because rowid tables are implemented as [B\*-Trees](fileformat2.md#btree) where all content is stored in the leaves of the tree, whereas WITHOUT ROWID tables are implemented using ordinary B-Trees with content stored on both leaves and intermediate nodes. Storing content in intermediate nodes causes each intermediate node entry to take up more space on the page and thus reduces the fan-out, increasing the search cost.
The "sqlite3_analyzer.exe" utility program, available as source code in the SQLite source tree or as a precompiled binary on the [SQLite Download page](https://sqlite.org/download.html), can be used to measure the average sizes of table rows in an existing SQLite database.
Note that except for a few corner-case differences detailed above, WITHOUT ROWID tables and rowid tables work the same. They both generate the same answers given the same SQL statements. So it is a simple matter to run experiments on an application, late in the development cycle, to test whether or not the use of WITHOUT ROWID tables will be helpful. A good strategy is to simply not worry about WITHOUT ROWID until near the end of product development, then go back and run tests to see if adding WITHOUT ROWID to tables with non-integer PRIMARY KEYs helps or hurts performance, and retaining the WITHOUT ROWID only in those cases where it helps.
# 5. Determining If An Existing Table Is WITHOUT ROWID
A WITHOUT ROWID table returns the same content for [PRAGMA table_info](pragma.md#pragma_table_info) and [PRAGMA table_xinfo](pragma.md#pragma_table_xinfo) as does an ordinary table. But unlike an ordinary table, a WITHOUT ROWID also responds to the [PRAGMA index_info](pragma.md#pragma_index_info) command. The [PRAGMA index_info](pragma.md#pragma_index_info) on a WITHOUT ROWID table returns information about the PRIMARY KEY for the table. In this way, the [PRAGMA index_info](pragma.md#pragma_index_info) command can be used to unambiguously determine whether a particular table is a WITHOUT ROWID table or an ordinary table - an ordinary table will always return no rows but a WITHOUT ROWID table will always return one or more rows.
---
# Code Of Conduct
*Sección: Guides | Origen: https://www.sqlite.org/codeofconduct.html*
# Code of Conduct
Due to concerns raised by readers, this document has been removed. The separate [Code of Ethics](codeofethics.md) document is similar to what this document used to be, but with a different name. The new name is an effort to more clearly communicate the purpose and scope of the document.
To be clear: The removal of this document does not represent a policy shift. Rather the change is merely an improvement in how the policy is communicated.
For historical reference, the complete history for the source code to this document is available in the SQLite Documentation source repository: | Offset | Size | Description |
|---|---|---|
| 0 | 1 | The one-byte flag at offset 0 indicating the b-tree page type.
|
| 1 | 2 | The two-byte integer at offset 1 gives the start of the first freeblock on the page, or is zero if there are no freeblocks. |
| 3 | 2 | The two-byte integer at offset 3 gives the number of cells on the page. |
| 5 | 2 | The two-byte integer at offset 5 designates the start of the cell content area. A zero value for this integer is interpreted as 65536. |
| 7 | 1 | The one-byte integer at offset 7 gives the number of fragmented free bytes within the cell content area. |
| 8 | 4 | The four-byte page number at offset 8 is the right-most pointer. This value appears in the header of interior b-tree pages only and is omitted from all other pages. |
| Datatype | Appears in... | Description | |||
|---|---|---|---|---|---|
| Table Leaf (0x0d) | Table Interior (0x05) | Index Leaf (0x0a) | Index Interior (0x02) | ||
| 4-byte integer | ✔ | ✔ | Page number of left child | ||
| varint | ✔ | ✔ | ✔ | Number of bytes of payload | |
| varint | ✔ | ✔ | Rowid | ||
| byte array | ✔ | ✔ | ✔ | Payload | |
| 4-byte integer | ✔ | ✔ | ✔ | Page number of first overflow page | |
| Offset | Size | Description |
|---|---|---|
| 0 | 1 | The one-byte flag at offset 0 indicating the b-tree page type.
|
| 1 | 2 | The two-byte integer at offset 1 gives the start of the first freeblock on the page, or is zero if there are no freeblocks. |
| 3 | 2 | The two-byte integer at offset 3 gives the number of cells on the page. |
| 5 | 2 | The two-byte integer at offset 5 designates the start of the cell content area. A zero value for this integer is interpreted as 65536. |
| 7 | 1 | The one-byte integer at offset 7 gives the number of fragmented free bytes within the cell content area. |
| 8 | 4 | The four-byte page number at offset 8 is the right-most pointer. This value appears in the header of interior b-tree pages only and is omitted from all other pages. |
| Datatype | Appears in... | Description | |||
|---|---|---|---|---|---|
| Table Leaf (0x0d) | Table Interior (0x05) | Index Leaf (0x0a) | Index Interior (0x02) | ||
| 4-byte integer | ✔ | ✔ | Page number of left child | ||
| varint | ✔ | ✔ | ✔ | Number of bytes of payload | |
| varint | ✔ | ✔ | Rowid | ||
| byte array | ✔ | ✔ | ✔ | Payload | |
| 4-byte integer | ✔ | ✔ | ✔ | Page number of first overflow page | |
| Example Typenames From The > CREATE TABLE Statement > or CAST Expression |
> Resulting Affinity | >Rule Used To Determine Affinity | >
|---|---|---|
| INT > INTEGER > TINYINT > SMALLINT > MEDIUMINT > BIGINT > UNSIGNED BIG INT > INT2 > INT8 |
> INTEGER | >1 | >
| CHARACTER(20) > VARCHAR(255) > VARYING CHARACTER(255) > NCHAR(55) > NATIVE CHARACTER(70) > NVARCHAR(100) > TEXT > CLOB |
> TEXT | >2 | >
| BLOB > no datatype specified |
> BLOB | >3 | >
| REAL > DOUBLE > DOUBLE PRECISION > FLOAT |
> REAL | >4 | >
| NUMERIC > DECIMAL(10,5) > BOOLEAN > DATE > DATETIME |
> NUMERIC | >5 | >
| 1152693165.1106291898 | >
| -1152693165.1106280772 | >
| 0.0000011126 | >
](https://www.loc.gov) |
SQLite is a [Recommended Storage Format](https://www.loc.gov/preservation/resources/rfs/) for datasets according to the [US Library of Congress](https://www.loc.gov/). Further information:
- 
# 2. The Basic Idea
We propose to use the [fossil software configuration management](http://www.fossil-scm.org) system to set up two branches. One branch (the "public branch" or "trunk") contains the published SQLite sources and the other branch is the private branch which contains the code that is customized for the project. Whenever a new public release of SQLite is made, that release is added to the public branch and then the changes are merged into the private branch.
This document proposes to use [fossil](http://www.fossil-scm.org/), but any other distributed software configuration management system such as [monotone](http://www.monotone.ca/) or [mercurial](http://www.selenic.com/mercurial/wiki/) (a.k.a. "hg"), or [git](http://www.git-scm.org/) could serve just as well. The concept will be the same, though the specifics of the procedure will vary.
The diagram at the right illustrates the concept. One begins with a standard SQLite release. For the sake of example, suppose that one intends to create a private branch off of SQLite version 3.6.15. In the diagram this is version (1). The maintainer makes an exact copy of the baseline SQLite into the branch space, shown as version (2). Note that (1) and (2) are exactly the same. Then the maintainer applies the private changes to version (2) resulting in version (3). In other words, version (3) is SQLite version 3.6.15 plus edits.
Later, SQLite version 3.6.16 is released, as shown by circle (4) in the diagram. At the point, the private branch maintainer does a merge which takes all of the changes going from (1) to (4) and applies those changes to (3). The result is version (5), which is SQLite 3.6.16 plus edits.
There might be merge conflicts. In other words, it might be that the changes from (2) to (3) are incompatible with the changes from (1) to (4). In that case, the maintainer will have to manually resolve the conflicts. Hopefully conflicts will not come up that often. Conflicts are less likely to occur when the private edits are kept to a minimum.
The cycle above can be repeated many times. The diagram shows a third SQLite release, 3.6.17 in circle (6). The private branch maintainer can do another merge in order to incorporate the changes moving from (4) to (6) into the private branch, resulting in version (7).
# 3. The Procedure
The remainder of this document will guide the reader through the steps needed to maintain a private branch. The general idea is the same as outlined above. This section merely provides more detail.
We emphasize again that these steps are not intended to be the only acceptable method for maintaining a private branch. This approach is one of many. Use this document as a baseline for preparing project-specific procedures. Do not be afraid to experiment.
## 3.1. Obtain The Software
[Fossil](http://www.fossil-scm.org/) is a computer program that must be installed on your machine before you use it. Fortunately, installing fossil is very easy. Fossil is a single "\*.exe" file that you simply download and run. To uninstall fossil, simply delete the exe file. [Detailed instructions](http://www.fossil-scm.org/index.html/doc/tip/www/quickstart.wiki) for installing and getting started with fossil are available on the [fossil website](http://www.fossil-scm.org).
## 3.2. Create A Project Repository
Create a fossil repository to host the private branch using the following command:
> \
> fossil new private-project.fossil\
You can call your project anything you like. The "`.fossil`" suffix is optional. For this document, we will continue to call the project "`private-project.fossil`". Note that `private-project.fossil` is an ordinary disk file (actually an SQLite database) that will contain your complete project history. You can make a backup of the project simply by making a copy of that one file.
If you want to configure the new project, type:
> \
> fossil ui private-project.fossil\
The "ui" command will cause fossil to run a miniature built-in webserver and to launch your web-browser pointing at that webserver. You can use your web-browser to configure your project in various ways. See the instructions on the fossil website for additional information.
Once the project repository is created, create an open checkout of the project by moving to the directory where you want to keep all of the project source code and typing:
> \
> fossil open private-project.fossil\
You can have multiple checkouts of the same project if you want. And you can "clone" the repository to different machines so that multiple developers can use it. See the fossil website for further information.
## 3.3. Installing The SQLite Baseline In Fossil
The repository created in the previous step is initially empty. The next step is to load the baseline SQLite release - circle (1) in the diagram above.
Begin by obtaining a copy of SQLite in whatever form you use it. The public SQLite you obtain should be as close to your private edited copy as possible. If your project uses the SQLite amalgamation, then get a copy of the amalgamation. If you use the preprocessed separate source files, get those instead. Put all the source files in the checkout directory created in the previous step.
The source code in public SQLite releases uses unix line endings (ASCII code 10: "newline" only, NL) and spaces instead of tabs. If you will be changing the line ending to windows-style line endings (ASCII codes 13, 10: "carriage-return" and "newline"; CR-NL) or if you will be changing space indents into tab indents, **make that change now** before you check in the baseline. The merging process will only work well if the differences between the public and the private branches are minimal. If every single line of the source file is changed in the private branch because you changed from NL to CR-NL line endings, then the merge steps will not work correctly.
Let us assume that you are using the amalgamation source code. Add the baseline to your project as follows:
> \
> fossil add sqlite3.c sqlite3.h\
If you are using separate source files, name all of the source files instead of just the two amalgamation source files. Once this is done, commit your changes as follows:
> \
> fossil commit\
You will be prompted for a check-in comment. Say whatever you like. After the commit completes, your baseline will be part of the repository. The following command, if you like, to see this on the "timeline":
> \
> fossil ui\
That last command is the same "ui" command that we ran before. It starts a mini-webserver running and points your web browser at it. But this time we didn't have to specify the repository file because we are located inside a checkout and so fossil can figure out the repository for itself. If you want to type in the repository filename as the second argument, you can. But it is optional.
If you do not want to use your web browser to view the new check-in, you can get some information from the command-line using commands like these:
> \
> fossil timeline\
> fossil info\
> fossil status\
## 3.4. Creating The Private Branch
The previous step created circle (1) in the diagram above. This step will create circle (2). Run the following command:
> \
> fossil branch new private trunk -bgcolor "#add8e8"\
This command will create a new branch named "private" (you can use a different name if you like) and assign it a background color of light blue ("#add8e8"). You can omit the background color if you want, though having a distinct background does make it easier to tell the branch from the "trunk" (the public branch) on timeline displays. You can change the background color of the private branch or of the public branch (the "trunk") using the web interface if you like.
The command above created the new branch. But your checkout is still on the trunk - a fact you can see by running the command:
> \
> fossil info\
To change your check-out to the private branch, type:
> \
> fossil update private\
You can run the "info" command again to verify that you are on the private branch. To go back to the public branch, type:
> \
> fossil update trunk\
Normally, fossil will modify all the files in your checkout when switching between the private and the public branches. But at this point, the files are identical in both branches so no modifications need to be made.
## 3.5. Adding Customizations To The Code In The Private Branch
Now it is time to make the private, custom modifications to SQLite which are the whole point of this exercise. Switch to the private branch (if you are not already there) using the "`fossil update private`" command, then bring up the source files in your text editor and make whatever changes you want to make. Once you have finished making changes, commit those changes using this command:
> \
> fossil commit\
You will be prompted once again to enter a commit describing your changes. Then the commit will occur. The commit creates a new checkin in the repository that corresponds to circle (3) in the diagram above.
Now that the public and private branches are different, you can run the "`fossil update trunk`" and "`fossil update private`" commands and see that fossil really does change the files in the checkout as you switch back and forth between branches.
Note that in the diagram above, we showed the private edits as a single commit. This was for clarity of presentation only. There is nothing to stop you from doing dozens or hundreds of separate tiny changes and committing each separately. In fact, making many small changes is the preferred way to work. The only reason for doing all the changes in a single commit is that it makes the diagram easier to draw.
## 3.6. Incorporating New Public SQLite Releases
Suppose that after a while (about a month, usually) a new version of SQLite is released: 3.6.16. You will want to incorporate this new public version of SQLite into your repository in the public branch (the trunk). To do this, first change your repository over to the trunk:
> \
> fossil update trunk\
Then download the new version of the SQLite sources and overwrite the files that are in the checkout.
If you made NL to CR-NL line ending changes or space to tab indentation changes in the original baseline, make the same changes to the new source file.
Once everything is ready, run the "`fossil commit`" command to check in the changes. This creates circle (4) in the diagram above.
## 3.7. Merging Public SQLite Updates Into The Private Branch
The next step is to move the changes in the public branch over into the private branch. In other words, we want to create circle (5) in the diagram above. Begin by changing to the private branch using "`fossil update private`". Then type this command:
> \
> fossil merge trunk\
The "merge" command attempts to apply all the changes between circles (1) and (4) to the files in the local checkout. Note that circle (5) has not been created yet. You will need to run the "commit" to create circle (5).
It might be that there are conflicts in the merge. Conflicts occur when the same line of code was changed in different ways between circles (1) and (4) versus circles (2) and (3). The merge command will announce any conflicts and will include both versions of the conflicting lines in the output. You will need to bring up the files that contain conflicts and manually resolve the conflicts.
After resolving conflicts, many users like to compile and test the new version before committing it to the repository. Or you can commit first and test later. Either way, run the "`fossil commit`" command to check-in the circle (5) version.
## 3.8. Further Updates
As new versions of SQLite are released, repeat steps 3.6 and 3.7 to add changes in the new release to the private branch. Additional private changes can be made on the private branch in between releases if desired.
# 4. Variations
Since this document was first written, the canonical SQLite source code has been moved from the venerable CVS system into a Fossil repository at | MySQL 3.23.41 |
MySQL 4.0.16 |
Firebird | SQL Anywhere |
Borland Interbase |
|
|---|---|---|---|---|---|
| Adding anything to null gives null | Yes | Yes | Yes | Yes | Yes |
| Multiplying null by zero gives null | Yes | Yes | Yes | Yes | Yes |
| nulls are distinct in a UNIQUE column | Yes | Yes | Yes | (Note 4) | (Note 4) |
| nulls are distinct in SELECT DISTINCT | No | No | No (Note 1) | No | No |
| nulls are distinct in a UNION | (Note 3) | No | No (Note 1) | No | No |
| "CASE WHEN null THEN 1 ELSE 0 END" is 0? | Yes | Yes | Yes | Yes | (Note 5) |
| "null OR true" is true | Yes | Yes | Yes | Yes | Yes |
| "not (null AND false)" is true | No | Yes | Yes | Yes | Yes |
| Notes: | 1. | Older versions of firebird omit all NULLs from SELECT DISTINCT and from UNION. |
| 2. | Test data unavailable. | |
| 3. | MySQL version 3.23.41 does not support UNION. | |
| 4. | DB2, SQL Anywhere, and Borland Interbase do not allow NULLs in a UNIQUE column. | |
| 5. | Borland Interbase does not support CASE expressions. |
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[indexed-column:](syntax/indexed-column.md)** show
Any index that includes the WHERE clause at the end is considered to be a partial index. Indexes that omit the WHERE clause (or indexes that are created by UNIQUE or PRIMARY KEY constraints inside of CREATE TABLE statements) are ordinary full indexes.
The expression following the WHERE clause may contain operators, literal values, and names of columns in the table being indexed. The WHERE clause may *not* contain subqueries, references to other tables, [non-deterministic functions](deterministic.md), or [bound parameters](lang_expr.md#varparam).
Only rows of the table for which the WHERE clause evaluates to true are included in the index. If the WHERE clause expression evaluates to NULL or to false for some rows of the table, then those rows are omitted from the index.
The columns referenced in the WHERE clause of a partial index can be any of the columns in the table, not just columns that happen to be indexed. However, it is very common for the WHERE clause expression of a partial index to be a simple expression on the column being indexed. The following is a typical example:
CREATE INDEX po_parent ON purchaseorder(parent_po) WHERE parent_po IS NOT NULL;\
In the example above, if most purchase orders do not have a "parent" purchase order, then most parent_po values will be NULL. That means only a small subset of the rows in the purchaseorder table will be indexed. Hence the index will take up much less space. And changes to the original purchaseorder table will run faster since the po_parent index only needs to be updated for those exceptional rows where parent_po is not NULL. But the index is still useful for querying. In particular, if one wants to know all "children" of a particular purchase order "?1", the query would be:
SELECT po_num FROM purchaseorder WHERE parent_po=?1;\
The query above will use the po_parent index to help find the answer, since the po_parent index contains entries for all rows of interest. Note that since po_parent is smaller than a full index, the query will likely run faster too.
## 2.1. Unique Partial Indexes
A partial index definition may include the UNIQUE keyword. If it does, then SQLite requires every entry *in the index* to be unique. This provides a mechanism for enforcing uniqueness across some subset of the rows in a table.
For example, suppose you have a database of the members of a large organization where each person is assigned to a particular "team". Each team has a "leader" who is also a member of that team. The table might look something like this:
CREATE TABLE person(\
person_id INTEGER PRIMARY KEY,\
team_id INTEGER REFERENCES team,\
is_team_leader BOOLEAN,\
-- other fields elided\
);\
The team_id field cannot be unique because there are usually multiple people on the same team. One cannot make the combination of team_id and is_team_leader unique since there are usually multiple non-leaders on each team. The solution to enforcing one leader per team is to create a unique index on team_id but restricted to those entries for which is_team_leader is true:
CREATE UNIQUE INDEX team_leader ON person(team_id) WHERE is_team_leader;\
Coincidentally, that same index is useful for locating the team leader of a particular team:
SELECT person_id FROM person WHERE is_team_leader AND team_id=?1;\
# 3. Queries Using Partial Indexes
Let X be the expression in the WHERE clause of a partial index, and let W be the WHERE clause of a query that uses the table that is indexed. Then, the query is permitted to use the partial index if W⇒X, where the ⇒ operator (usually pronounced "implies") is the logic operator equivalent to "X or not W". Hence, determining whether or not a partial index is usable in a particular query reduces to proving a theorem in first-order logic.
SQLite does not have a sophisticated theorem prover with which to determine W⇒X. Instead, SQLite uses two simple rules to find the common cases where W⇒X is true, and it assumes all the other cases are false. The rules used by SQLite are these:
1. If W is AND-connected terms and X is OR-connected terms and if any term of W appears as a term of X, then the partial index is usable.
For example, let the index be
CREATE INDEX ex1 ON tab1(a,b) WHERE a=5 OR b=6;\
And let the query be:
SELECT \* FROM tab1 WHERE b=6 AND a=7; *-- uses partial index*\
Then the index is usable by the query because the "b=6" term appears in both the index definition and in the query. Remember: terms in the index should be OR-connected and terms in the query should be AND-connected.
The terms in W and X must match exactly. SQLite does not do algebra to try to get them to look the same. The term "b=6" does not match "b=3+3" or "b-6=0" or "b BETWEEN 6 AND 6". "b=6" will match to "6=b" as long as "b=6" is on the index and "6=b" is in the query. If a term of the form "6=b" appears in the index, it will never match anything.
2. If a term in X is of the form "z IS NOT NULL" and if a term in W is a comparison operator on "z" other than "IS", then those terms match.
Example: Let the index be
CREATE INDEX ex2 ON tab2(b,c) WHERE c IS NOT NULL;\
Then any query that uses operators =, \<, \>, \<=, \>=, \<\>, IN, LIKE, or GLOB on column "c" would be usable with the partial index because those comparison operators are only true if "c" is not NULL. So the following query could use the partial index:
SELECT \* FROM tab2 WHERE b=456 AND c\<\>0; *-- uses partial index*\
But the next query can not use the partial index:
SELECT \* FROM tab2 WHERE b=456; *-- cannot use partial index*\
The latter query can not use the partial index because there might be rows in the table with b=456 and where c is NULL. But those rows would not be in the partial index.
These two rules describe how the query planner for SQLite works as of this writing (2013-08-01). And the rules above will always be honored. However, future versions of SQLite might incorporate a better theorem prover that can find other cases where W⇒X is true and thus may find more instances where partial indexes are useful.
# 4. Supported Versions
Partial indexes have been supported in SQLite since [version 3.8.0](releaselog/3_8_0.md) (2013-08-26).
Database files that contain partial indices are not readable or writable by versions of SQLite prior to 3.8.0. However, a database file created by SQLite 3.8.0 is still readable and writable by prior versions as long as its schema contains no partial indexes. A database that is unreadable by legacy versions of SQLite can be made readable simply by running [DROP INDEX](lang_dropindex.md) on the partial indexes.
---
# Pointer Passing Interfaces
*Sección: Guides | Origen: https://www.sqlite.org/bindptr.html*
# 1. Overview
Three new "\_pointer()" interfaces were added to SQLite 3.20.0 (2017-08-01):
- [sqlite3_bind_pointer()](c3ref/bind_blob.md),
- [sqlite3_result_pointer()](c3ref/result_blob.md), and
- [sqlite3_value_pointer()](c3ref/value_blob.md).
Questions and confusion quickly arose on the [mailing lists](support.md#mailinglists) about the purpose behind these new interfaces, why they were introduced, and what problem they solve. This essay attempts to answer those questions and clear up the confusion.
# 2. A Brief History Of Pointer Passing In SQLite
It is sometimes convenient for SQLite extensions to communicate non-SQL values between subcomponents or between the extension and the application. Some examples:
- In the [FTS3](fts3.md) extension, the [MATCH operator](fts3.md#full_text_index_queries) (which does the full-text search) needs to communicate details of matching entries to the [snippet()](fts3.md#snippet), [offsets()](fts3.md#offsets), and [matchinfo()](fts3.md#matchinfo) functions so that those functions can convert the details of the match into useful output.
- In order for an application to [add new extensions to FTS5](fts5.md#extending_fts5), such as new tokenizers, the application needs a pointer to the "fts5_api" object.
- In the [CARRAY extension](carray.md), the application needs to tell the extension the location of a C-language array that contains the data for the table-valued function that the extension implements.
The traditional way of communicating this information was to transform a C-language pointer into a BLOB or a 64-bit integer, then move that BLOB or integer through SQLite using the usual interfaces like [sqlite3_bind_blob()](c3ref/bind_blob.md), [sqlite3_result_blob()](c3ref/result_blob.md), [sqlite3_value_blob()](c3ref/value_blob.md) or the integer equivalents.
## 2.1. Upping The Threat Level
Passing around pointers as if they were integers or BLOBs is easy, effective, and works well in an environment where the application components are all friendly toward one another. However, passing pointers as integers and BLOBs allows hostile SQL text to forge invalid pointers that can carry out mischief.
For example, the first argument to the [snippet()](fts3.md#snippet) function is supposed to be a special column of the FTS3 table that contains a pointer to an fts3cursor object that contains information about the current full text search match. That pointer was formerly passed as a BLOB. For example, if the FTS3 table is named "t1" and has a column named "cx", one might write:
SELECT snippet(t1) FROM t1 WHERE cx MATCH \$pattern;\
But if a hacker is able to run arbitrary SQL, he might run a slightly different query, like this:
SELECT hex(t1) FROM t1 WHERE cx MATCH \$pattern;\
Because the pointer is passed in the t1 column of the t1 table as a BLOB (in older versions of SQLite), such a query would have shown the value of the pointer in hex. The attacker could then modify that pointer to try to get the snippet() function to modify memory in some other part of the application address space instead of the fts3cursor object it was supposed to be operating on:
SELECT snippet(x'6092310100000000') FROM t1 WHERE cx MATCH \$pattern;\
Historically, this was not considered a threat. The argument was that if a hostile agent is able to inject arbitrary SQL text into the application, then that agent is already in full control of the application, so letting the hostile agent forge a pointer does not give the agent any new capability.
For most cases, it is true that potential attackers have no way of injecting arbitrary SQL, and so most uses of SQLite are immune to the attack above. But there are some notable exceptions. To wit:
- The [WebSQL](https://en.wikipedia.org/wiki/Web_SQL_Database) interface to webkit allowed any webpage to run arbitrary SQL in the browser for Chrome and Safari. That arbitrary SQL was supposed to be run inside a sandbox where it could do no harm even if exploited, but that sandbox turned out to be less secure than people supposed. In the spring of 2017, one team of hackers was able to root an iMac using a long sequence of exploits, one of which involved corrupting the pointers passed as BLOB values to the snippet() FTS3 function of an SQLite database running via the WebSQL interface inside of Safari.
- On Android, we are told, there are many services that will blindly run arbitrary SQL that is passed to them by untrustworthy apps that have been downloaded from dodgy corners of the internet. Android services are suppose to be more guarded about running SQL from unvetted sources. This author does not have any specific examples to the contrary, but he has heard rumors that they exist. Even if all Android services are more careful and properly vet all the SQL they run, it would be difficult to audit them all in order to verify that they are safe. Hence, security-minded people are keen to ensure that no exploits are possible by passing arbitrary SQL text.
- The [Fossil](https://www.fossil-scm.org/) version control system (designed and written for the purpose of supporting SQLite development) allows mildly trusted users to enter arbitrary SQL for generating trouble-ticket reports. That SQL is sanitized using the [sqlite3_set_authorizer()](c3ref/set_authorizer.md) interface, and no exploits have ever been found. But this is an example of potentially hostile agents being able to inject arbitrary SQL into the system.
## 2.2. Preventing Forged Pointers
The first attempt at closing security gaps in pointer passing was to prevent pointer values from being forged. This was accomplished by having the sender attach a subtype to each pointer using [sqlite3_result_subtype()](c3ref/result_subtype.md) and having the receiver verify that subtype using [sqlite3_value_subtype()](c3ref/value_subtype.md) and reject pointers that had an incorrect subtype. Since there is no way to attach a subtype to a result using pure SQL, this prevents pointers from being forged using SQL. The only way to send a pointer is to use C code. If an attacker can set a subtype, then he is also able to forge a pointer without the help of SQLite.
Using subtypes to identify valid pointers prevented the WebSQL exploit. But it turned out to be an incomplete solution.
## 2.3. Pointer Leaks
The use of subtypes on pointers prevented pointer forgery using pure SQL. But subtypes do nothing to prevent an attacker from reading the values of pointers. In other words, subtypes on pointer values prevent attacks using SQL statements like this:
SELECT snippet(x'6092310100000000') FROM t1 WHERE cx MATCH \$pattern;\
The BLOB argument to snippet() does not have the correct subtype, so the snippet function ignores it, makes no changes to any data structures, and harmlessly returns NULL.
But the use of subtypes does nothing to prevent the value of a pointer from being read using SQL code like this:
SELECT hex(t1) FROM t1 WHERE cx MATCH \$pattern;\
What harm could come of that, you ask? The SQLite developers (including this author) wondered the same thing. But then security researchers pointed out that knowledge of pointers can help attackers to circumvent address-space randomization defenses. This is called a "pointer leak". A pointer leak is not itself a vulnerability, but it can aid an attacker in effectively exploiting other vulnerabilities.
# 3. The New Pointer-Passing Interfaces
Allowing extension components to pass private information to one another securely and without introducing pointer leaks requires new interfaces:
- **[sqlite3_bind_pointer](c3ref/bind_blob.md)(S,I,P,T,D)** → Bind pointer P of type T to the I-th parameter of prepared statement S. D is an optional destructor function for P.
- **[sqlite3_result_pointer](c3ref/result_blob.md)(C,P,T,D)** → Return pointer P of type T as the argument of function C. D is an optional destructor function for P.
- **[sqlite3_value_pointer](c3ref/value_blob.md)(V,T)** → Return the pointer of type T associated with value V, or if V has no associated pointer, or if the pointer on V is of a type different from T, then return NULL.
To SQL, the values created by [sqlite3_bind_pointer()](c3ref/bind_blob.md) and [sqlite3_result_pointer()](c3ref/result_blob.md) are indistinguishable from NULL. An SQL statement that tries to use the [hex()](lang_corefunc.md#hex) function to read the value of a pointer will get an SQL NULL answer. The only way to discover whether or not a value has an associated pointer is to use the [sqlite3_value_pointer()](c3ref/value_blob.md) interface with the appropriate type string T.
Pointer values read by [sqlite3_value_pointer()](c3ref/value_blob.md) cannot be generated by pure SQL. Hence, it is not possible for SQL to forge pointers.
Pointer values generated by [sqlite3_bind_pointer()](c3ref/bind_blob.md) and [sqlite3_result_pointer()](c3ref/result_blob.md) cannot be read by pure SQL. Hence, it is not possible for SQL to leak the value of pointers.
In this way the new pointer-passing interface seems to solve all of the security problems associated with passing pointer values from one extension to another in SQLite.
## 3.1. Pointer Types
The "pointer type" in the last parameter to [sqlite3_bind_pointer()](c3ref/bind_blob.md), [sqlite3_result_pointer()](c3ref/result_blob.md), and [sqlite3_value_pointer()](c3ref/value_blob.md) is used to prevent pointers intended for one extension from being redirected to a different extension. For example, without the use of pointer types, an attacker could still get access to pointer information in a system that included both the [FTS3](fts3.md) and the [CARRAY extension](carray.md) using SQL like this:
SELECT ca.value FROM t1, carray(t1,10) AS ca WHERE cx MATCH \$pattern\
In the statement above, the FTS3 cursor pointer generated by the MATCH operator is sent into the carray() table-valued function instead of its intended recipient snippet(). The carray() function treats the pointer as a pointer to an array of integers and returns each integer one by one, thus leaking the content of the FTS3 cursor object. Since the FTS3 cursor object contains pointers to other objects, the statement above would be a pointer leak.
Except, the statement above does not work, thanks to pointer types. The pointer generated by the MATCH operator has a type of "fts3cursor" but the carray() function expects to receives a pointer of type "carray". Because the pointer type on the [sqlite3_result_pointer()](c3ref/result_blob.md) does not match the pointer type on the [sqlite3_value_pointer()](c3ref/value_blob.md) call, [sqlite3_value_pointer()](c3ref/value_blob.md) returns NULL in carray() and thus signals the CARRAY extension that it has been passed an invalid pointer.
### 3.1.1. Pointer types are static strings
Pointer types are static strings, which ideally should be string literals embedded directly in the SQLite API call, not parameters passed in from other functions. Consideration was given to using integer values as the pointer type, but static strings provides a much larger name space which reduces the chance of accidental type-name collisions between unrelated extensions.
By "static string", we mean a zero-terminated array of bytes that is fixed and unchanging for the life of the program. In other words, the pointer type string should be a string constant. In contrast, a "dynamic string" is a zero-terminated array of bytes that is held in memory allocated from the heap, and which must be freed to avoid a memory leak. Do not use dynamic strings as the pointer type string.
Multiple commentators have expressed a desire to use dynamic strings for the pointer type, and to have SQLite take ownership of the type strings and to automatically free the type string when it has finished using it. That design is rejected for the following reasons:
1. The pointer type is not intended to be flexible and dynamic. The pointer type is intended to be a design-time constant. Applications should not synthesize pointer type strings at run-time. Providing support for dynamic pointer type strings would lead developers to misuse the pointer-passing interfaces by creating run-time synthesized pointer type strings. Requiring the pointer type strings to be static encourages developers to do the right thing by choosing fixed pointer type names at design-time and encoding those names as constant strings.
2. All string values at the SQL level in SQLite are dynamic strings. Requiring type strings to be static makes it difficult to create an application-defined SQL function that can synthesize a pointer of an arbitrary type. We do not want users to create such SQL functions, since such functions would compromise the security of the system. Thus, the requirement to use static strings helps to defend the integrity of the pointer-passing interfaces against ill-designed SQL functions. The static string requirement is not a perfect defense, since a sophisticated programmer can code around it, and a novice programmer can simply take the memory leak. But by stating that the pointer type string must be static, we hope to encourage developers who might otherwise use a dynamic string for the pointer type to think more carefully about the problem and avoid introducing security issues.
3. Having SQLite take ownership of the type strings would impose a performance cost on all applications, even applications that do not use the pointer-passing interfaces. SQLite passes values around as instances of the [sqlite3_value](c3ref/value.md) object. That object has a destructor, which because of the fact that sqlite3_value objects are used for nearly everything, is invoked frequently. If the destructor needs to check to see if there is a pointer type string that needs to be freed, that is a few extra CPU cycles that need to be burned on each call to the destructor. Those cycles add up. We would be willing to bear the cost of the extra CPU cycles if pointer-passing was a commonly used programming paradigm, but pointer-passing is rare, and so it seems unwise to impose a run-time cost on billions and billions of applications that do not use pointer passing just for convenience of a few applications that do.
If you feel that you need dynamic pointer type strings in your application, that is a strong indicator that you are misusing the pointer-passing interface. Your intended use may be unsafe. Please rethink your design. Determine if you really need to be passing pointers through SQL in the first place. Or perhaps find a different mechanism other than the pointer-passing interfaces described by this article.
## 3.2. Destructor Functions
The last parameter to the [sqlite3_bind_pointer()](c3ref/bind_blob.md) and [sqlite3_result_pointer()](c3ref/result_blob.md) routines is a pointer to a procedure used to dispose of the P pointer once SQLite has finished with it. This pointer can be NULL, in which case no destructor is called.
When the D parameter is not NULL, that means that ownership of the pointer is being transferred to SQLite. SQLite will take responsibility for freeing resources associated with the pointer when it has finished using the pointer. If the D parameter is NULL, that means that ownership of the pointer remains with the caller and the caller is responsible for disposing of the pointer.
Note that the destructor function D is for the pointer value P, not for the type string T. The type string T should be a static string with an infinite lifetime.
If ownership of the pointer is passed into SQLite by providing a non-NULL D parameter to [sqlite3_bind_pointer()](c3ref/bind_blob.md) or [sqlite3_result_pointer()](c3ref/result_blob.md) then the ownership remains with SQLite until the object is destroyed. There is no way to transfer ownership out of SQLite and back into the application again.
# 4. Restrictions On The Use of Pointer Values
The pointers that piggy-back on SQL NULL values using the [sqlite3_bind_pointer()](c3ref/bind_blob.md), [sqlite3_result_pointer()](c3ref/result_blob.md), and [sqlite3_value_pointer()](c3ref/value_blob.md) interface are transient and ephemeral. The pointers are never written into the database. The pointers will not survive sorting. The latter fact is why there is no sqlite3_column_pointer() interface, since it is impossible to predict whether or not the query planner will insert a sort operation prior to returning a value from a query, so it would be impossible to know if a pointer value inserted into a query by [sqlite3_bind_pointer()](c3ref/bind_blob.md) or [sqlite3_result_pointer()](c3ref/result_blob.md) would survive through to the result set.
Pointer values must flow directly from their producer into their consumer, with no intermediate operators or functions. Any transformation of a pointer value destroys the pointer and transforms the value into an ordinary SQL NULL.
# 5. Summary
Key take-aways from this essay:
1. The internet is an increasingly hostile place. These days, developers should assume that attackers will find a way to execute arbitrary SQL in an application. Applications should be designed to prevent the execution of arbitrary SQL from escalating into a more severe exploit.
2. A few SQLite extensions benefit from passing pointers:
- The [FTS3](fts3.md) MATCH operator passes pointers into [snippet()](fts3.md#snippet), [offsets()](fts3.md#offsets), and [matchinfo()](fts3.md#matchinfo).
- The [carray table-valued function](carray.md) needs to accept a pointer to an array of C-language values from the application.
- The [remember() extension](https://sqlite.org/src/file/ext/misc/remember.c) needs a pointer to a C-language integer variable in which to remember the value it passes.
- Applications need to receive a pointer to the "fts5_api" object in order to add extensions, such as custom tokenizers, to the [FTS5](fts5.md) extension.
3. Pointers should never be exchanged by encoding them as some other SQL datatype, such as integers or BLOBs. Instead, use the interfaces designed to facilitate secure pointer passing: [sqlite3_bind_pointer()](c3ref/bind_blob.md), [sqlite3_result_pointer()](c3ref/result_blob.md), and [sqlite3_value_pointer()](c3ref/value_blob.md).
4. The use of pointer-passing is an advanced technique that should be used infrequently and cautiously. Pointer-passing should not be used haphazardly or carelessly. Pointer-passing is a sharp tool that can leave deep scars if misused.
5. The "pointer type" string which is the last parameter to each of the pointer-passing interfaces should be a distinct, application-specific string literal that appears directly in the API call. The pointer type should not be a parameter passed in from a higher-level function.
---
# Powersafe Overwrite
*Sección: Guides | Origen: https://www.sqlite.org/psow.html*
"Powersafe overwrite" is a term used by the SQLite team to describe a behavior of some filesystems and disk-controllers related to data preservation during a power loss. Powersafe overwrite is a boolean property: either the storage system has it or it does not.
We say that a system has the powersafe overwrite property if the following statement is true:
> **When an application writes a range of bytes in a file, no bytes outside of that range will change, even if the write occurs just before a crash or power failure.**
The powersafe overwrite property says nothing about the state of the bytes that were written. Those bytes might contain their old values, their new values, random values, or some combination of these. The powersafe overwrite property merely states that writes cannot change bytes outside of the range of bytes written.
In other words, powersafe overwrite means that there is no "collateral damage" when a power loss occurs while writing. Only those bytes actually being written might be damaged.
In practical terms, what the powersafe write property means is that when the disk controller detects an impending power loss, it finishes writing whatever sector it is working on prior to parking the heads. It means that individual sector writes will complete once started, even if there is a power loss.
Consider what would happen if disk sector writes are interrupted by a power loss. If an application writes two or three bytes in the middle of some file, the operating system will implement this by first reading the entire sector containing those bytes, making the change to the sector in memory, then writing the entire sector back to the disk. If a power loss occurs during the writeback and the sector was not completely written, then on the next read after reboot, error correcting codes in the sector will probably detect irreparable damage and the disk controller will read out the sector as all zeros or all ones. Thus values will have changed outside of the range of the two or three bytes that were written at the application level - a violation of the powersafe overwrite property.
## SQLite Assumptions About Powersafe Overwrite
All versions of SQLite up to and including [version 3.7.9](releaselog/3_7_9.md) (2011-11-01) assume that the filesystem does not provide powersafe overwrite. SQLite has traditionally assumed that when any one byte of a file changes, all other bytes within the same sector of that byte have the potential of being corrupted on a power loss. When writing, SQLite has made sure to journal all bytes in the same sector of any modifications and it pads journal files out to the next sector boundary so that subsequent appends to that journal cannot damage prior records. SQLite understands the sector size to be the value returned by the xSectorSize method in the [VFS](vfs.md). The SQLite team has often referred to the value returned by xSectorSize as the "blast radius" of a write, since it expresses the range of bytes that might be damaged if a power loss occurs during the write. The default [VFSes](vfs.md) for unix and windows have always returned 512 as the sector size (or blast radius) for all versions of SQLite up to and including version 3.7.9.
Newer disk drives have begun using 4096 byte sectors however. Beginning with SQLite [version 3.7.10](releaselog/3_7_10.md) (2012-01-16), the SQLite development team experimented with changes to xSectorSize to report 4096 bytes as the blast radius. This had the effect of increasing write overhead on many databases. For a database with a [PRAGMA page_size](pragma.md#pragma_page_size) of 1024 (a very common choice) making a change to a single page in the database now requires SQLite to backup three other adjacent pages to the rollback journal, whereas formerly it only had to backup the one page that was changing. In [WAL mode](wal.md), each transaction had to be padded out to the next 4096-byte boundary in the WAL file, rather than the next 512-byte boundary, resulting in thousands of extra bytes being written per transaction.
The extra write overhead prompted a reexamination of assumptions about powersafe overwrite. With modern disk drives, the capacity has become so large and the data density so great that a single sector is very small and writing a single sector takes very little time. We know that disk drives can detect an impending power loss and continue to operate for some small amount of time on residual energy because those drives are able to park their heads before spinning down. And so if an impending power loss is detectable by the disk controller, it seems reasonable that the controller will finish writing whatever sector it is current working on when the imminent power loss is first detected, prior to parking the heads, as long as doing so does not take too long, which it should not with small and dense sectors. Hence it seems reasonable to assume powersafe overwrite for modern disks. Indeed, BerkeleyDB has made this assumption for decades, we are told. Caution is advised though. As Roger Binns noted on the SQLite developers mailing list: "'poorly written' should be the main assumption about drive firmware."
## Torn Pages
A torn page occurs when a database page is larger than a disk sector, the database page is written to disk, but a power loss occurs prior to all sectors of the database page being written. Then, upon recovery, part of the database page will have the old content while some other parts of the page will have the new content. Some database engines assume that page writes are atomic and hence a torn page is an unrecoverable error.
SQLite never assumes that database page writes are atomic, regardless of the PSOW setting.(1) And hence SQLite is always able to automatically recover from torn pages induced by a crash. Enabling PSOW does not decrease SQLite's ability to recover from a torn page.
## Changes In SQLite Version 3.7.10
The [VFS](vfs.md) for SQLite [version 3.7.10](releaselog/3_7_10.md) (2012-01-16) adds a new device characteristic named [SQLITE_IOCAP_POWERSAFE_OVERWRITE](c3ref/c_iocap_atomic.md). Database files that report this characteristic are assumed to reside on storage systems that have the powersafe overwrite property. The default unix and windows [VFSes](vfs.md) now report [SQLITE_IOCAP_POWERSAFE_OVERWRITE](c3ref/c_iocap_atomic.md) if SQLite is compiled with [-DSQLITE_POWERSAFE_OVERWRITE=1](compile.md#powersafe_overwrite) or they make the legacy assumption that storage does not have the powersafe overwrite property if compiled with [-DSQLITE_POWERSAFE_OVERWRITE=0](compile.md#powersafe_overwrite). For now, the default is for powersafe overwrite to be turned on, though we may revisit this in the future and default it off.
The powersafe overwrite property for individual databases can be specified as the database is opened using the "psow" query parameter with a [URI filename](uri.md). For example, to always assume powersafe overwrite for a file (perhaps to ensure maximum write performance), open it as
> file:somefile.db?psow=1
Or to be extra safe with a database and to force SQLite to assume the database lacks powersafe overwrite, open it using
> file:somefile.db?psow=0
There is also a new [SQLITE_FCNTL_POWERSAFE_OVERWRITE](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlpowersafeoverwrite) opcode for the [sqlite3_file_control()](c3ref/file_control.md) that allows an application to query the powersafe overwrite property for a database file.
------------------------------------------------------------------------
## Notes:
1. SQLite never assumes atomic page writes *in its default configurations*. But a custom [VFS](vfs.md) can set one of the [SQLITE_IOCAP_ATOMIC](c3ref/c_iocap_atomic.md) bits in the result of the xDeviceCharacteristic() method and then SQLite will assume that page writes are atomic. The application must supply a custom VFS to accomplish this, however, since none of the standard VFSes will ever set any of the atomic bits in the xDeviceCharacteristics() vector.
---
# Pressrelease 20071212
*Sección: Guides | Origen: https://www.sqlite.org/pressrelease-20071212.html*
FOR IMMEDIATE RELEASE:
## SQLite Consortium Launches With Mozilla And Symbian As Charter Members
### Ensures independent technical direction for world's most deployed SQL database engine
**Charlotte, North Carolina - December 12, 2007** - The SQLite Consortium, a new membership association dedicated to maintaining SQLite as a fully open and independent product, was formally announced today. Mozilla and Symbian Ltd. have joined the SQLite Consortium as charter members.
SQLite is a compact, high efficiency, high reliability, embeddable SQL database engine. The source code to SQLite is in the public domain and is available with no associated fees. SQLite is the most deployed SQL database engine in the world and is currently used in a wide range of commercial software products and electronic devices from leading manufacturers. SQLite is found today in many mobile phones, MP3 players, set-top boxes, and PCs.
The mission of the SQLite Consortium is to continue developing and enhancing SQLite as a product that anyone may use without paying royalties or licensing fees. Members of the SQLite Consortium provide funding to enable this mission and in return receive enterprise-level technical support. Technical control and direction of SQLite remains entirely with the SQLite developers.
Mozilla, developer of the popular open-source Firefox web browser, and Symbian, the market-leading open operating system for advanced data-enabled smartphones, both deploy the SQLite database engine in their products. As charter members of the Consortium, Mozilla and Symbian are ensuring the development and support of SQLite as a freely accessible and public domain software asset.
"SQLite has become a popular embedded database because it is lightweight, fast, and open source," said Michael Schroepfer, Vice President of Engineering, Mozilla. "As a charter member of the SQLite Consortium, Mozilla is excited to help ensure SQLite remains a vibrant and open technology, in line with our mission to promote choice and innovation on the Internet."
"The SQLite Consortium will help set the standards for database management which are essential in smartphone functionality and will also help create a pool of developers, highly-skilled in SQLite for future mobile phone development, " said Bruce Carney, Director, Developer Programmes & Services, Symbian. "Our involvement with the SQL Consortium not only demonstrates Symbian's commitment to open standards in the industry, but as mobile phones become increasingly powerful and smartphones become increasingly popular, we are focused on ensuring that desktop developers, who move to the mobile space, have the easiest and most productive experience possible."
SQLite is a winner of the 2005 Google/O'Reilly Open Source Award. Additional information regarding the SQLite Consortium is available at the SQLite website, http://www.sqlite.org/.
\# \# \#
**About SQLite**
SQLite is a software library that implements a self-contained, embeddable, serverless, zero-configuration, transactional SQL database engine. The code for SQLite is in the public domain and is free for any use, commercial or private. SQLite is currently found in countless software titles and electronic devices.
SQLite was originally developed and released 2000 by Dr. D. Richard Hipp. The code continues to be maintained and enhanced by an international team of developers under Hipp's direction.
CONTACT INFORMATION:\
SQLite Consortium\
Dr. D. Richard Hipp\
6200 Maple Cove Lane\
Charlotte, NC 28269\
Email: drh@sqlite.org\
http://www.sqlite.org/\
Tel: +1.704.948.4565
**About Mozilla**
Mozilla is a global community dedicated to building free, open source products and technologies that improve the online experience for people everywhere. Mozilla works in the open with a highly disciplined, transparent and cooperative development process, under the umbrella of the non-profit Mozilla Foundation. As a wholly owned subsidiary, the Mozilla Corporation organizes the development and marketing of Mozilla products. This unique structure has enabled Mozilla to financially support and cultivate competitive, viable community innovation. For more information, visit www.mozilla.com.
CONTACT INFORMATION:\
Mozilla Corporation\
Jessica Waight\
Tel: +1.415.345.4754\
Email: jwaight@outcastpr.com
**About Symbian Limited**
Symbian is a software licensing company that develops and licenses Symbian OS, the market-leading open operating system for advanced, data-enabled mobile phones known as smartphones.
Symbian licenses Symbian OS to the world's leading handset manufacturers and has built close co-operative business relationships with leading companies across the mobile industry. During Q3 2007, 20.4 million Symbian smartphones were sold worldwide to over 250 major network operators, bringing the total number of Symbian smartphones shipped up to 30 September 2007 to 165 million.
Symbian has its headquarters in London, United Kingdom, with offices in the United States, United Kingdom, Asia (India, P.R. China, and Korea) and Japan. For more information, please visit www.symbian.com.
CONTACT INFORMATION:\
Symbian Global Press Office\
Karen Hamblen\
+44 207 154 1707\
press@symbian.com
---
# Profiling SQL Queries
*Sección: Guides | Origen: https://www.sqlite.org/profile.html*
# 1. Overview
SQLite contains built-in support for profiling SQL queries, but it is not enabled by default. In order to enable support for query profiling, SQLite must be compiled with the [following option](compile.md#enable_stmt_scanstatus):
-DSQLITE_ENABLE_STMT_SCANSTATUS\
Building SQLite with this option enables the [sqlite3_stmt_scanstatus_v2()](c3ref/stmt_scanstatus.md) API, which provides access to the various profiling metrics. The remainder of this page discusses the profiling reports generated by the SQLite [command-line shell](cli.md) using these metrics, rather than the API directly.
The profiling reports generated by the shell are very similar to the query plan reports generated by the [EXPLAIN QUERY PLAN](eqp.md) command. This page assumes that the reader is familiar with this format.
Within a command-line shell compiled with the option above, query profiling is enabled using the ".scanstats on" command:
sqlite\> .scanstats on\
Once enabled, the shell automatically outputs a query profile after each SQL query executed. Query profiling can be disabled using ".scanstats off". For example:
sqlite\> .scanstats on\
sqlite\> SELECT a FROM t1, t2 WHERE a IN (1,2,3) AND a=d+e;\
Cycles Loops Rows \
---------- ----- -----\
QUERY PLAN 255M 100% 1 3\
\|--SEARCH t1 USING INTEGER PRIMARY KEY (rowid=?) 60.0M 23% 1 3\
\`--SCAN t2 134M 52% 3 150K\
# 2. Simple Cases - Rows, Loops and Cycles
Consider a database with the following schema:
CREATE VIRTUAL TABLE ft USING fts5(text);\
CREATE TABLE t1(a, b);\
CREATE TABLE t2(c INTEGER PRIMARY KEY, d);\
Then, after first executing ".scanstats on":
sqlite3\> SELECT \* FROM t1, t2 WHERE t2.c=t1.a;\
\<...query results...\>\
Cycles Loops Rows \
---------- ----- -----\
QUERY PLAN 1.14M 100%\
\|--SCAN t1 455K 40% 1 500\
\`--SEARCH t2 USING INTEGER PRIMARY KEY (rowid=?) 620K 54% 500 250\
The text in the example above following the snipped "\<...query results...\>" is the profile report for the join query just executed. The parts of the profile report that are similar to the [EXPLAIN QUERY PLAN](eqp.md) output indicate that the query is implemented by doing a full table-scan of table "t1", with a lookup by INTEGER PRIMARY KEY on table "t2" for each row visited.
The value of "1" in the "Loops" column to the right of the EXPLAIN QUERY PLAN output on the "SCAN t1" line indicates that this loop - the full-table scan of table "t1" - ran exactly once. The value of "500" under the "Rows column indicates that that single scan generates 500 rows.
The "SEARCH t2 USING ..." line contains "500" for "Loops" to indicate that this "loop" (really a lookup by INTEGER PRIMARY KEY) ran 500 times. Which makes sense - it ran once for each row visited by the full-table scan of "t1". The "250" under "Row" means that, altogether, those 500 loops generated 250 rows. In other words, only half of the INTEGER PRIMARY KEY lookups on table t2 were successful, for the other half of the lookups there was no row to find.
The loop-count for a SEARCH or SCAN entry is not necessarily the same as the number of rows output by the outer loop. For example, if the query above were modified as follows:
sqlite3\> SELECT \* FROM t1, t2 WHERE t1.b\<=100 AND t2.c=t1.a;\
\<...query results...\>\
Cycles Loops Rows \
---------- ----- -----\
QUERY PLAN 561K 100%\
\|--SCAN t1 345K 62% 1 500\
\`--SEARCH t2 USING INTEGER PRIMARY KEY (rowid=?) 129K 23% 100 50\
This time, even though the "SCAN t1" loop still visits 500 rows, the "SEARCH t2" lookup is only performed 100 times. This is because SQLite was able to discard rows from t1 that did not match the "t1.b\<=100" constraint.
The "cycles" measurements are based on the [CPU time-stamp counter](https://en.wikipedia.org/wiki/Time_Stamp_Counter) , and so are a good proxy for wall-clock time. For the query above, the total number of cycles was about 561,000. (All of the values displayed are rounded to three significant digits.) For each of the two loops ("SCAN t1..." and "SEARCH t2..."), the cycles count represents the time spent in operations that can be directly attributed to that loop only. Specifically, this is the time spent navigating and extracting data from the database b-trees for that loop. These values never quite add up to the total cycles for the query, as there are other internal operations performed by SQLite that are not directly attributable to either loop.
The cycles count for the "SCAN t1" loop was 345K - 62% of the total for the query. The 100 lookups peformed by the "SEARCH t1" loop took 129K cycles, 23% of the total.
When a virtual table is used, the "Rows" and "Loops" metrics have the same meaning as for loops on regular SQLite tables. The "Cycles" meaurement is the total cycles consumed within virtual table methods associated with the loop. For example:
sqlite3\> SELECT \* FROM ft('sqlite'), t2 WHERE t2.c=ft.rowid;\
\<...query results...\>\
Cycles Loops Rows \
---------- ----- -----\
QUERY PLAN 836K 100%\
\|--SCAN ft VIRTUAL TABLE INDEX 0:M1 740K 91% 1 48\
\`--SEARCH t2 USING INTEGER PRIMARY KEY (rowid=?) 62.9K 8% 48 25\
In this case the single query (Loops: 1) on fts5 table "ft" returned 48 rows (Rows: 48) and consumed about 740K cycles, which was roughly 88% of the total query time.
# 3. Complex Cases - Rows, Loops and Cycles
Using the same schema as in the previous section, consider this more complicated example:
sqlite3\> WITH cnt(i) AS (\
SELECT 1 UNION SELECT i+1 FROM cnt WHERE i\<100\
)\
SELECT\
\*, (SELECT d FROM t2 WHERE c=ft.rowid)\
FROM\
(SELECT count(\*), a FROM t1 GROUP BY a) AS v1 CROSS JOIN\
ft('sqlite'),\
cnt\
WHERE cnt.i=ft.rowid AND v1.a=ft.rowid;\
\<...query results...\>\
Cycles Loops Rows \
---------- ----- -----\
QUERY PLAN 178M 100%\
\|--CO-ROUTINE v1\
\| \|--SCAN t1 397K 0% 1 500\
\| \`--USE TEMP B-TREE FOR GROUP BY\
\|--MATERIALIZE cnt 1.28M 1%\
\| \|--SETUP\
\| \| \`--SCAN CONSTANT ROW\
\| \`--RECURSIVE STEP\
\| \`--SCAN cnt 129K 0% 100 100\
\|--SCAN v1 4.50M 3% 1 500\
\|--SCAN ft VIRTUAL TABLE INDEX 0:M1= 162M 91% 500 271\
\|--SCAN cnt 7.33M 4% 95 9500\
\`--CORRELATED SCALAR SUBQUERY 3 169K 0% 37\
\`--SEARCH t2 USING INTEGER PRIMARY KEY (rowid=?) 94.7K 0% 37 21\
The most complicated part of the example above is understanding the query plan - the portion of the report that would also be generated by an [EXPLAIN QUERY PLAN](eqp.md) command.
The following query uses an [automatic index](optoverview.md#autoindex) and an external sort:
sqlite\> SELECT \* FROM\
t2,\
(SELECT count(\*) AS cnt, d FROM t2 GROUP BY d) AS v2\
WHERE v2.d=t2.d AND t2.d\>100\
ORDER BY v2.cnt;\
\<...query results...\>\
Cycles Loops Rows \
---------- ----- -----\
QUERY PLAN 6.23M 100%\
\|--MATERIALIZE v2 2.35M 38%\
\| \|--SCAN t2 188K 3% 1 250\
\| \`--USE TEMP B-TREE FOR GROUP BY\
\|--SCAN t2 456K 7% 1 250\
\|--CREATE AUTOMATIC INDEX ON v2(d, cnt) 1.67M 27% 1 250\
\|--SEARCH v2 USING AUTOMATIC COVERING INDEX (d=?) 933K 15% 200 200\
\`--USE TEMP B-TREE FOR ORDER BY 662K 11% 1 200\
Points of interest are:
- This query materializes the sub-query into a temp table, then creates an automatic (i.e. transient) index on it, then uses that index to optimize the join. All three of these steps - "MATERIALIZE v2", "CREATE AUTOMATIC INDEX" and "SEARCH ... USING AUTOMATIC INDEX" have separate cycle counts. The "rows" associated with the "CREATE AUTOMATIC INDEX" line represents the total number of rows included in the index. The "loops" and "rows" associated with the "SEARCH ... USING AUTOMATIC INDEX" line represent the number of lookups the index was used for and the total number of rows found by those lookups.
- The external sort "USE TEMP B-TREE FOR ORDER BY" is also accounted for separately. The cycles count represents the extra cycles consumed by sorting the returned rows, above those that would have been used if the rows were returned in arbitrary order. The rows count represents the number of rows sorted.
# 4. Planner Estimates
As well as ".scanstats on" to enable profiling and ".scanstats off" to disable it, the shell also accepts ".scanstats est":
sqlite\> .scanstats est\
This enables a special kind of profiling report that includes two extra values associated with each "SCAN..." and "SEARCH..." element of a query profile. The "Loops" and "Rows" columns show the actual number of invocations of each step and the actual number of rows generated, but now both numbers are also followed by the estimated values for those quantities that the query planner used to pick the algorithm.
sqlite\> SELECT a FROM t1, t2 WHERE a IN (1,2,3) AND a=d+e ORDER BY a;\
\
Each SQL statement in the statement list is an instance of the following:
**[sql-stmt:](syntax/sql-stmt.md)**
---
# Query Planning
*Sección: Guides | Origen: https://www.sqlite.org/queryplanner.html*
## Overview
The best feature of SQL (in all its implementations, not just SQLite) is that it is a *declarative* language, not a *procedural* language. When programming in SQL you tell the system *what* you want to compute, not *how* to compute it. The task of figuring out the *how* is delegated to the *query planner* subsystem within the SQL database engine.
For any given SQL statement, there might be hundreds or thousands or even millions of different algorithms of performing the operation. All of these algorithms will get the correct answer, though some will run faster than others. The query planner is an [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) that tries to pick the fastest and most efficient algorithm for each SQL statement.
Most of the time, the query planner in SQLite does a good job. However, the query planner needs indices to work with. These indices must normally be added by programmers. Rarely, the query planner AI will make a suboptimal algorithm choice. In those cases, programmers may want to provide additional hints to help the query planner do a better job.
This document provides background information about how the SQLite query planner and query engine work. Programmers can use this information to help create better indexes, and provide hints to help the query planner when needed.
Additional information is provided in the [SQLite query planner](optoverview.md) and [next generation query planner](queryplanner-ng.md) documents.
# 1. Searching
## 1.1. Tables Without Indices
Most tables in SQLite consist of zero or more rows with a unique integer key (the [rowid](lang_createtable.md#rowid) or [INTEGER PRIMARY KEY](lang_createtable.md#rowid)) followed by content. (The exception is [WITHOUT ROWID](withoutrowid.md) tables.) The rows are logically stored in order of increasing rowid. As an example, this article uses a table named "FruitsForSale" which relates various fruits to the state where they are grown and their unit price at market. The schema is this:
\
CREATE TABLE FruitsForSale(\
Fruit TEXT,\
State TEXT,\
Price REAL\
);\
With some (arbitrary) data, such a table might be logically stored on disk as shown in figure 1:
\
Figure 1: Logical Layout Of Table "FruitsForSale"
In this example, the rowids are not consecutive but they are ordered. SQLite usually creates rowids beginning with one and increasing by one with each added row. But if rows are deleted, gaps can appear in the sequence. And the application can control the rowid assigned if desired, so that rows are not necessarily inserted at the bottom. But regardless of what happens, the rowids are always unique and in strictly ascending order.
Suppose you want to look up the price of peaches. The query would be as follows:
\
SELECT price FROM fruitsforsale WHERE fruit='Peach';\
To satisfy this query, SQLite reads every row out of the table, checks to see if the "fruit" column has the value of "Peach" and if so, outputs the "price" column from that row. The process is illustrated by [figure 2](#fig2) below. This algorithm is called a *full table scan* since the entire content of the table must be read and examined in order to find the one row of interest. With a table of only 7 rows, a full table scan is acceptable, but if the table contained 7 million rows, a full table scan might read megabytes of content in order to find a single 8-byte number. For that reason, one normally tries to avoid full table scans.
\
Figure 2: Full Table Scan
## 1.2. Lookup By Rowid
One technique for avoiding a full table scan is to do lookups by rowid (or by the equivalent [INTEGER PRIMARY KEY](lang_createtable.md#rowid)). To lookup the price of peaches, one would query for the entry with a rowid of 4:
\
SELECT price FROM fruitsforsale WHERE rowid=4;\
Since the information is stored in the table in rowid order, SQLite can find the correct row using a binary search. If the table contains N elements, the time required to look up the desired row is proportional to logN rather than being proportional to N as in a full table scan. If the table contains 10 million elements, that means the query will be on the order of N/logN or about 1 million times faster.
\
Figure 3: Lookup By Rowid
## 1.3. Lookup By Index
The problem with looking up information by rowid is that you probably do not care what the price of "item 4" is - you want to know the price of peaches. And so a rowid lookup is not helpful.
To make the original query more efficient, we can add an index on the "fruit" column of the "fruitsforsale" table like this:
\
CREATE INDEX Idx1 ON fruitsforsale(fruit);\
An index is another table similar to the original "fruitsforsale" table but with the content (the fruit column in this case) stored in front of the rowid and with all rows in content order. [Figure 4](#fig4) gives a logical view of the Idx1 index. The "fruit" column is the primary key used to order the elements of the table and the "rowid" is the secondary key used to break the tie when two or more rows have the same "fruit". In the example, the rowid has to be used as a tie-breaker for the "Orange" rows. Notice that since the rowid is always unique over all elements of the original table, the composite key of "fruit" followed by "rowid" will be unique over all elements of the index.
\
Figure 4: An Index On The Fruit Column
This new index can be used to implement a faster algorithm for the original "Price of Peaches" query.
\
SELECT price FROM fruitsforsale WHERE fruit='Peach';\
The query starts by doing a binary search on the Idx1 index for entries that have fruit='Peach'. SQLite can do this binary search on the Idx1 index but not on the original FruitsForSale table because the rows in Idx1 are sorted by the "fruit" column. Having found a row in the Idx1 index that has fruit='Peach', the database engine can extract the rowid for that row. Then the database engines does a second binary search on the original FruitsForSale table to find the original row that contains fruit='Peach'. From the row in the FruitsForSale table, SQLite can then extract the value of the price column. This procedure is illustrated by [figure 5](#fig5).
\
Figure 5: Indexed Lookup For The Price Of Peaches
SQLite has to do two binary searches to find the price of peaches using the method show above. But for a table with a large number of rows, this is still much faster than doing a full table scan.
## 1.4. Multiple Result Rows
In the previous query the fruit='Peach' constraint narrowed the result down to a single row. But the same technique works even if multiple rows are obtained. Suppose we looked up the price of Oranges instead of Peaches:
\
SELECT price FROM fruitsforsale WHERE fruit='Orange'\
\
Figure 6: Indexed Lookup For The Price Of Oranges
In this case, SQLite still does a single binary search to find the first entry of the index where fruit='Orange'. Then it extracts the rowid from the index and uses that rowid to lookup the original table entry via binary search and output the price from the original table. But instead of quitting, the database engine then advances to the next row of index to repeat the process for next fruit='Orange' entry. Advancing to the next row of an index (or table) is much less costly than doing a binary search since the next row is often located on the same database page as the current row. In fact, the cost of advancing to the next row is so cheap in comparison to a binary search that we usually ignore it. So our estimate for the total cost of this query is 3 binary searches. If the number of rows of output is K and the number of rows in the table is N, then in general the cost of doing the query is proportional to (K+1)\*logN.
## 1.5. Multiple AND-Connected WHERE-Clause Terms
Next, suppose that you want to look up the price of not just any orange, but specifically California-grown oranges. The appropriate query would be as follows:
\
SELECT price FROM fruitsforsale WHERE fruit='Orange' AND state='CA'\
\
Figure 7: Indexed Lookup Of California Oranges
One approach to this query is to use the fruit='Orange' term of the WHERE clause to find all rows dealing with oranges, then filter those rows by rejecting any that are from states other than California. This process is shown by [figure 7](#fig7) above. This is a perfectly reasonable approach in most cases. Yes, the database engine did have to do an extra binary search for the Florida orange row that was later rejected, so it was not as efficient as we might hope, though for many applications it is efficient enough.
Suppose that in addition to the index on "fruit" there was also an index on "state".
\
CREATE INDEX Idx2 ON fruitsforsale(state);\
\
Figure 8: Index On The State Column
The "state" index works just like the "fruit" index in that it is a new table with an extra column in front of the rowid and sorted by that extra column as the primary key. The only difference is that in Idx2, the first column is "state" instead of "fruit" as it is with Idx1. In our example data set, there is more redundancy in the "state" column and so there are more duplicate entries. The ties are still resolved using the rowid.
Using the new Idx2 index on "state", SQLite has another option for lookup up the price of California oranges: it can look up every row that contains fruit from California and filter out those rows that are not oranges.
\
Figure 9: Indexed Lookup Of California Oranges
Using Idx2 instead of Idx1 causes SQLite to examine a different set of rows, but it gets the same answer in the end (which is very important - remember that indices should never change the answer, only help SQLite to get to the answer more quickly) and it does the same amount of work. So the Idx2 index did not help performance in this case.
The last two queries take the same amount of time, in our example. So which index, Idx1 or Idx2, will SQLite choose? If the [ANALYZE](lang_analyze.md) command has been run on the database, so that SQLite has had an opportunity to gather statistics about the available indices, then SQLite will know that the Idx1 index usually narrows the search down to a single item (our example of fruit='Orange' is the exception to this rule) whereas the Idx2 index will normally only narrow the search down to two rows. So, if all else is equal, SQLite will choose Idx1 with the hope of narrowing the search to as small a number of rows as possible. This choice is only possible because of the statistics provided by [ANALYZE](lang_analyze.md). If [ANALYZE](lang_analyze.md) has not been run then the choice of which index to use is arbitrary.
## 1.6. Multi-Column Indices
To get the maximum performance out of a query with multiple AND-connected terms in the WHERE clause, you really want a multi-column index with columns for each of the AND terms. In this case we create a new index on the "fruit" and "state" columns of FruitsForSale:
\
CREATE INDEX Idx3 ON FruitsForSale(fruit, state);\
\
Figure 1: A Two-Column Index
A multi-column index follows the same pattern as a single-column index; the indexed columns are added in front of the rowid. The only difference is that now multiple columns are added. The left-most column is the primary key used for ordering the rows in the index. The second column is used to break ties in the left-most column. If there were a third column, it would be used to break ties for the first two columns. And so forth for all columns in the index. Because rowid is guaranteed to be unique, every row of the index will be unique even if all of the content columns for two rows are the same. That case does not happen in our sample data, but there is one case (fruit='Orange') where there is a tie on the first column which must be broken by the second column.
Given the new multi-column Idx3 index, it is now possible for SQLite to find the price of California oranges using only 2 binary searches:
\
SELECT price FROM fruitsforsale WHERE fruit='Orange' AND state='CA'\
\
Figure 11: Lookup Using A Two-Column Index
With the Idx3 index on both columns that are constrained by the WHERE clause, SQLite can do a single binary search against Idx3 to find the one rowid for California oranges, then do a single binary search to find the price for that item in the original table. There are no dead-ends and no wasted binary searches. This is a more efficient query.
Note that Idx3 contains all the same information as the original [Idx1](#fig3). And so if we have Idx3, we do not really need Idx1 any more. The "price of peaches" query can be satisfied using Idx3 by simply ignoring the "state" column of Idx3:
\
SELECT price FROM fruitsforsale WHERE fruit='Peach'\
\
Figure 12: Single-Column Lookup On A Multi-Column Index
Hence, a good rule of thumb is that your database schema should never contain two indices where one index is a prefix of the other. Drop the index with fewer columns. SQLite will still be able to do efficient lookups with the longer index.
## 1.7. Covering Indexes
The "price of California oranges" query was made more efficient through the use of a two-column index. But SQLite can do even better with a three-column index that also includes the "price" column:
\
CREATE INDEX Idx4 ON FruitsForSale(fruit, state, price);\
\
Figure 13: A Covering Index
This new index contains all the columns of the original FruitsForSale table that are used by the query - both the search terms and the output. We call this a "covering index". Because all of the information needed is in the covering index, SQLite never needs to consult the original table in order to find the price.
\
SELECT price FROM fruitsforsale WHERE fruit='Orange' AND state='CA';\
\
Figure 14: Query Using A Covering Index
Hence, by adding extra "output" columns onto the end of an index, one can avoid having to reference the original table and thereby cut the number of binary searches for a query in half. This is a constant-factor improvement in performance (roughly a doubling of the speed). But on the other hand, it is also just a refinement; A two-fold performance increase is not nearly as dramatic as the one-million-fold increase seen when the table was first indexed. And for most queries, the difference between 1 microsecond and 2 microseconds is unlikely to be noticed.
## 1.8. OR-Connected Terms In The WHERE Clause
Multi-column indices only work if the constraint terms in the WHERE clause of the query are connected by AND. So Idx3 and Idx4 are helpful when the search is for items that are both Oranges and grown in California, but neither index would be that useful if we wanted all items that were either oranges *or* are grown in California.
\
SELECT price FROM FruitsForSale WHERE fruit='Orange' OR state='CA';\
When confronted with OR-connected terms in a WHERE clause, SQLite examines each OR term separately and tries to use an index to find the rowids associated with each term. It then takes the union of the resulting rowid sets to find the end result. The following figure illustrates this process:
\
Figure 15: Query With OR Constraints
The diagram above implies that SQLite computes all of the rowids first and then combines them with a union operation before starting to do rowid lookups on the original table. In reality, the rowid lookups are interspersed with rowid computations. SQLite uses one index at a time to find rowids while remembering which rowids it has seen before so as to avoid duplicates. That is just an implementation detail, though. The diagram, while not 100% accurate, provides a good overview of what is happening.
In order for the OR-by-UNION technique shown above to be useful, there must be an index available that helps resolve every OR-connected term in the WHERE clause. If even a single OR-connected term is not indexed, then a full table scan would have to be done in order to find the rowids generated by the one term, and if SQLite has to do a full table scan, it might as well do it on the original table and get all of the results in a single pass without having to mess with union operations and follow-on binary searches.
One can see how the OR-by-UNION technique could also be leveraged to use multiple indices on queries where the WHERE clause has terms connected by AND, by using an intersect operator in place of union. Many SQL database engines will do just that. But the performance gain over using just a single index is slight and so SQLite does not implement that technique at this time. However, a future version SQLite might be enhanced to support AND-by-INTERSECT.
# 2. Sorting
SQLite (like all other SQL database engines) can also use indices to satisfy the ORDER BY clauses in a query, in addition to expediting lookup. In other words, indices can be used to speed up sorting as well as searching.
When no appropriate indices are available, a query with an ORDER BY clause must be sorted as a separate step. Consider this query:
\
SELECT \* FROM fruitsforsale ORDER BY fruit;\
SQLite processes this by gathering all the output of the query and then running that output through a sorter.
\
Figure 16: Sorting Without An Index
If the number of output rows is K, then the time needed to sort is proportional to KlogK. If K is small, the sorting time is usually not a factor, but in a query such as the above where K==N, the time needed to sort can be much greater than the time needed to do a full table scan. Furthermore, the entire output is accumulated in temporary storage (which might be either in main memory or on disk, depending on various compile-time and run-time settings) which can mean that a lot of temporary storage is required to complete the query.
## 2.1. Sorting By Rowid
Because sorting can be expensive, SQLite works hard to convert ORDER BY clauses into no-ops. If SQLite determines that output will naturally appear in the order specified, then no sorting is done. So, for example, if you request the output in rowid order, no sorting will be done:
\
SELECT \* FROM fruitsforsale ORDER BY rowid;\
\
Figure 17: Sorting By Rowid
You can also request a reverse-order sort like this:
\
SELECT \* FROM fruitsforsale ORDER BY rowid DESC;\
SQLite will still omit the sorting step. But in order for output to appear in the correct order, SQLite will do the table scan starting at the end and working toward the beginning, rather than starting at the beginning and working toward the end as shown in [figure 17](#fig17).
## 2.2. Sorting By Index
Of course, ordering the output of a query by rowid is seldom useful. Usually one wants to order the output by some other column.
If an index is available on the ORDER BY column, that index can be used for sorting. Consider the request for all items sorted by "fruit":
\
SELECT \* FROM fruitsforsale ORDER BY fruit;\
\
Figure 18: Sorting With An Index
The Idx1 index is scanned from top to bottom (or from bottom to top if "ORDER BY fruit DESC" is used) in order to find the rowids for each item in order by fruit. Then for each rowid, a binary search is done to lookup and output that row. In this way, the output appears in the requested order without the need to gather the entire output and sort it using a separate step.
But does this really save time? The number of steps in the [original indexless sort](#fig16) is proportional to NlogN since that is how much time it takes to sort N rows. But when we use Idx1 as shown here, we have to do N rowid lookups which take logN time each, so the total time of NlogN is the same!
SQLite uses a cost-based query planner. When there are two or more ways of solving the same query, SQLite tries to estimate the total amount of time needed to run the query using each plan, and then uses the plan with the lowest estimated cost. A cost is computed mostly from the estimated time, and so this case could go either way depending on the table size and what WHERE clause constraints were available, and so forth. But generally speaking, the indexed sort would probably be chosen, if for no other reason, because it does not need to accumulate the entire result set in temporary storage before sorting and thus uses much less temporary storage.
## 2.3. Sorting By Covering Index
If a covering index can be used for a query, then the multiple rowid lookups can be avoided and the cost of the query drops dramatically.
\
Figure 19: Sorting With A Covering Index
With a covering index, SQLite can simply walk the index from one end to the other and deliver the output in time proportional to N and without having to allocate a large buffer to hold the result set.
# 3. Searching And Sorting At The Same Time
The previous discussion has treated searching and sorting as separate topics. But in practice, it is often the case that one wants to search and sort at the same time. Fortunately, it is possible to do this using a single index.
## 3.1. Searching And Sorting With A Multi-Column Index
Suppose we want to find the prices of all kinds of oranges sorted in order of the state where they are grown. The query is this:
\
SELECT price FROM fruitforsale WHERE fruit='Orange' ORDER BY state\
The query contains both a search restriction in the WHERE clause and a sort order in the ORDER BY clause. Both the search and the sort can be accomplished at the same time using the two-column index Idx3.
\
Figure 20: Search And Sort By Multi-Column Index
The query does a binary search on the index to find the subset of rows that have fruit='Orange'. (Because the fruit column is the left-most column of the index and the rows of the index are in sorted order, all such rows will be adjacent.) Then it scans the matching index rows from top to bottom to get the rowids for the original table, and for each rowid does a binary search on the original table to find the price.
You will notice that there is no "sort" box anywhere in the above diagram. The ORDER BY clause of the query has become a no-op. No sorting has to be done here because the output order is by the state column and the state column also happens to be the first column after the fruit column in the index. So, if we scan entries of the index that have the same value for the fruit column from top to bottom, those index entries are guaranteed to be ordered by the state column.
## 3.2. Searching And Sorting With A Covering Index
A [covering index](queryplanner.md#covidx) can also be used to search and sort at the same time. Consider the following:
\
SELECT \* FROM fruitforsale WHERE fruit='Orange' ORDER BY state\
\
Figure 21: Search And Sort By Covering Index
As before, SQLite does a single binary search for the range of rows in the covering index that satisfy the WHERE clause, then scans that range from top to bottom to get the desired results. The rows that satisfy the WHERE clause are guaranteed to be adjacent since the WHERE clause is an equality constraint on the left-most column of the index. And by scanning the matching index rows from top to bottom, the output is guaranteed to be ordered by state since the state column is the very next column to the right of the fruit column. And so the resulting query is very efficient.
SQLite can pull a similar trick for a descending ORDER BY:
\
SELECT \* FROM fruitforsale WHERE fruit='Orange' ORDER BY state DESC\
The same basic algorithm is followed, except this time the matching rows of the index are scanned from bottom to top instead of from top to bottom, so that the states will appear in descending order.
## 3.3. Partial Sorting Using An Index (a.k.a. Block Sorting)
Sometimes only part of an ORDER BY clause can be satisfied using indexes. Consider, for example, the following query:
\
SELECT \* FROM fruitforsale ORDER BY fruit, price\
If the covering index is used for the scan, the "fruit" column will appear naturally in the correct order, but when there are two or more rows with the same fruit, the price might be out of order. When this occurs, SQLite does many small sorts, one sort for each distinct value of fruit, rather than one large sort. Figure 22 below illustrates the concept.
\
Figure 22: Partial Sort By Index
In the example, instead of a single sort of 7 elements, there are 5 sorts of one-element each and 1 sort of 2 elements for the case of fruit=='Orange'.
The advantages of doing many smaller sorts instead of a single large sort are:
1. Multiple small sorts collectively use fewer CPU cycles than a single large sort.
2. Each small sort is run independently, meaning that much less information needs to be kept in temporary storage at any one time.
3. Those columns of the ORDER BY that are already in the correct order due to indexes can be omitted from the sort key, further reducing storage requirements and CPU time.
4. Output rows can be returned to the application as each small sort completes, and well before the table scan is complete.
5. If a LIMIT clause is present, it might be possible to avoid scanning the entire table.
Because of these advantages, SQLite always tries to do a partial sort using an index even if a complete sort by index is not possible.
# 4. WITHOUT ROWID tables
The basic principles described above apply to both ordinary rowid tables and [WITHOUT ROWID](withoutrowid.md) tables. The only difference is that the rowid column that serves as the key for tables and that appears as the right-most term in indexes is replaced by the PRIMARY KEY.
---
# Query Result Formatting In The CLI
*Sección: Guides | Origen: https://www.sqlite.org/climode.html*
# 1. Introduction
In [Command Line Interface](cli.md) (or [CLI](cli.md)) for SQLite [version 3.52.0](releaselog/3_52_0.md) (2026-03-06), the "`.mode`" [dot-command](cli.md#dotcmd) was enhanced to provide more flexibility in rendering query results. But with flexibiliity comes complexity. For that reason, the operation of the ".mode" command is now broken out into this separate document.
## 1.1. Summary of enhancements
- The ".mode" command now takes many new options that control the output format. Some of these new options replace settings that were formerly handled by separate dot-commands. For example, the new ["--width" option](climode.md#opt-width) now replaces the legacy ".width" dot-command. (The legacy ".width" command is retained for compatibility but is no longer documented and is deprecated.)
- The default mode for interactive sessions is changed to "qbox" modified with additional options ["--quote relaxed"](climode.md#opt-quote), ["--limits 5,300,20"](climode.md#opt-limits), ["--textjsonb on"](climode.md#opt-textjsonb) and ["--sw auto"](climode.md#opt-sw). The legacy "list" mode is still the default for scripts, for backwards compatibility.
- New modes "`tty`" and "`batch`" set the display mode to the default for interactive sessions and for batch sessions, respectively.
- New mode "`psql`" makes the output look very similar to the output from PostgreSQL's "psql" command-line utility.
- There are many new formatting possibilities. See details below.
## 1.2. A few quick examples:
To see the current output mode, use ".mode" with no arguments.
sqlite\> **.mode**\
.mode qbox --limits on --quote relaxed --sw auto --textjsonb on \
sqlite\>\
Add "-v" for more detail:
sqlite\> **.mode -v**\
.mode qbox --align "" --border on --blob-quote auto --colsep "" --escape auto \
--limits on --null "NULL" --quote relaxed --rowsep "" --sw auto --tablename "" \
--textjsonb on --titles on --widths "" --wordwrap off\
sqlite\>\
Use ".mode --list" to see a list of all available output modes:
sqlite\> **.mode --list**\
available modes: ascii box c column count csv html insert jatom jobject json \
line list markdown off psql qbox quote table tabs tcl batch tty\
sqlite\>\
Change to "column" mode with no limits on the length of individual fields, but squeezing the width of all columns so that the table fits on the screen.
sqlite\> **.mode column -limits off -sw auto **\
Set up the display to be ASCII-art boxes (similar to MySQL) with text shown unquoted, with NULL value appearing as "NULL", with BLOB values appearing as hexadecimal, and with length limits set to show only the first 10 lines or first 1000 characters of any value.
sqlite\> **.mode table -quote off -null NULL -blob hex -limits 10,1000 **\
Use split-column mode ("split") but only for a single SQL input (due to the ["--once" option](climode.md#opt-once)).
sqlite\> **.mode --once split**\
sqlite\> **SELECT name FROM pragma_function_list**\
...\> **WHERE name GLOB 'json\_\*'**\
...\> **ORDER BY name;**\
json_array json_group_array json_patch json_replace json_valid \
json_array_length json_group_object json_pretty json_set\
json_array_length json_insert json_pretty json_type\
json_error_position json_object json_quote json_type\
json_extract json_parse json_remove json_valid\
sqlite3\>\
Show usage hints about the ".mode" command:
sqlite\> **.help mode **\
# 2. Default Output Formats
As of version 3.52.0 (2026-03-06) the default format is:
- Show query results in a table composed from Unicode box drawing symbols. ("box")
- Quote all output as SQL literals, except do not quote text literals when it is not necessary to disambiguate them. ("--quote relaxed")
- Attempt to automatically squeeze the output table so that it fits within the width of the display. ("--screenwidth auto")
- Truncate multi-line values to show only the first 5 lines. ("--linelimit 5")
- Truncate long values to show only the first 300 characters. ("--charlimit 300")
- Truncate column titles to 20 characters. (--titlelimit 20)
- When displaying a BLOB that is really JSONB, show the equivalent JSON text rather than the BLOB value. ("--textjsonb on")
The above is the default when the CLI is connected to a terminal or console window. When run as a batch script (when both standard input and standard output are connected to a file or pipe rather than a keyboard or terminal window) the default format is the same as it always has been for SQLite version 3.51.0 and earlier:
- Values appear as they are in the database, without quoting.
- All columns for each row appear on a single line separated by "\|".
- Rows are terminated by a newline (U+000a).
- There are no limits on the length of result values or output lines.
This "batch" mode is for legacy compatibility. You can force batch mode by launching the CLI with the "`--batch`" command-line option, or by issuing the "`.mode batch`" dot-command.
To see how the CLI is currently configured for result rendering, you can run the command "`.mode`" with no arguments, or run "`.mode -v`" for more detail.
# 3. Changing Output Formats
There are many different output "modes". The default for terminals, where individual values are quoted and the whole result is displayed in a matrix composed from Unicode box-drawing characters, is called "qbox". The default for batch mode is called "list". You can get a complete list of all available modes by running the command "`.mode --list`"
To change output modes, run a command like "`.mode `*NAME*" where *NAME* is one of the built-in modes named in the output of the "`.mode --list`" command. There are also many options available to fine-tune how results are displayed. You can probably discern many of those options by examining the output of the "`.mode -v`" command.
## 3.1. Output mode "list"
The default output mode for scripts (and for all instances of the CLI prior to 3.52.0) is "list". In list mode, each row of a query result is written on one line of output and each column within that row is separated by a specific separator string. The default separator is a pipe symbol ("\|"). List mode is especially useful when you are going to send the output of a query to another program (such as AWK) for additional processing.
sqlite\> **.mode list**\
sqlite\> **CREATE TABLE tbl1(one,two);**\
sqlite\> **INSERT INTO tbl1 VALUES('hello!',10),('goodbye',20);**\
sqlite\> **SELECT \* FROM tbl1;**\
hello!\|10\
goodbye\|20\
sqlite\>\
Use the "`--colsep` *STRING*" option on the "`.mode`" command to select a different column separator string. For example, to change the separator to a comma and a space, you could do this:
sqlite\> **.mode list --colsep ", "**\
sqlite\> **select \* from tbl1;**\
hello!, 10\
goodbye, 20\
sqlite\>\
Changing to a different mode might reset the column separator, or various other settings, back to a default value for the new mode. So you might need to repeat the "--colsep" option whenever you change modes if you want to continue using a non-standard separator.
## 3.2. Output mode "quote"
In "quote" mode, the output is formatted as SQL literals. Strings are enclosed in single-quotes and internal single-quotes are escaped by doubling. Blobs are displayed in hexadecimal blob literal notation (Ex: x'abcd'). Numbers are displayed as ASCII text and NULL values are shown as "NULL". All columns are separated from each other by a comma.
sqlite\> **.mode quote**\
sqlite\> **select \* from tbl1;**\
'hello!',10\
'goodbye',20\
sqlite\>\
Quote mode is really an alias for list mode with some setting changes. The following two .mode commands give the same end result:
sqlite\> **.mode quote**\
sqlite\> **.mode list -quote on -colsep ","**\
## 3.3. Other list-like output modes
Several output modes are convenience aliases for "list" with alternative values for the "`--quote`", "`--colsep`", "`--rowsep`", and "`--null`". Here is a complete list:
> | Mode | --quote | --colsep | --rowsep | --null |
> |--------|---------|----------|----------|--------|
> | ascii | csv | "\037" | "\036" | "" |
> | c | tcl | , | "\n" | NULL |
> | csv | csv | , | "\r\n" | "" |
> | jatom | json | , | "\n" | null |
> | list | off | \| | "\n" | "" |
> | quote | on | , | "\n" | NULL |
> | tables | csv | "\t" | "\n" | "" |
> | tcl | tcl | , | "\n" | "" |
## 3.4. Output mode "line"
In "line" mode, each column in a row of the database is shown on a line by itself. Each line consists of the column name, a colon, and the column data. Successive records are separated by a blank line. Here is an example of line mode output:
sqlite\> **.mode line**\
sqlite\> **select \* from tbl1;**\
one: hello!\
two: 10\
\
one: goodbye\
two: 20\
sqlite\>\
The "line" mode is particularly useful when displaying results that have a large number of columns, too many columns to fit on a single line of your display. Line mode avoids overflowing lines of your display and thus makes the output easier to read.
Before version 3.52.0, the separator was an equal sign rather than a colon. In other words, the first line of the example above used to say "one = hello!" instead of "one: hello!". You can restore the pre-3.52.0 formatting using the "--colsep *TEXT*" option to the ".mode" command, where *TEXT* is the desired separator. Hence, to get the legacy formatting, you say:
sqlite\> **.mode line --colsep " = "**\
## 3.5. Tabular output modes
In tabular modes, each record is shown on a separate line with the data aligned in columns. The "column" mode is an example:
sqlite\> **.mode column**\
sqlite\> **select \* from tbl1;**\
one two\
-------- ---\
hello! 10\
goodbye 20\
sqlite\>\
In "column" mode (and also in "box", "psql", "qbox", "table", and "markdown") the width of columns adjusts automatically. You can override this, providing a specified width for each column using the "--width" option to the ".mode" command. The argument to "--width" is a list of space- or comma-separated integers which are the number characters to devote to each column. Negative numbers mean right-justify. A value of 0 means the width of the column automatically adjusts to its content. The default value for "--width" is 0 and 0 is also the default for any column to the right of those that are specified using "--width". Thus:
sqlite\> **.mode --width 12,-6**\
sqlite\> **select \* from tbl1;**\
one two\
------------ ------\
hello! 10\
goodbye 20\
sqlite\>\
The command "`.mode --width 0`" resets all column widths back to zero and hence causes all column widths to be determined automatically.
Here are examples of other tabular modes:
sqlite\> **.mode box --widths 0**\
sqlite\> **select \* from tbl1;**\
╭─────────┬─────╮\
│ one │ two │\
╞═════════╪═════╡\
│ hello! │ 10 │\
│ goodbye │ 20 │\
╰─────────┴─────╯\
sqlite\> **.mode markdown**\
sqlite\> **select \* from tbl1;**\
\| one \| two \|\
\|---------\|-----\|\
\| hello! \| 10 \|\
\| goodbye \| 20 \|\
sqlite\> **.mode psql**\
sqlite\> **select \* from tbl1;**\
one \| two\
---------+-----\
hello! \| 10\
goodbye \| 20\
sqlite\> **.mode qbox**\
sqlite\> **select \* from tbl1;**\
╭───────────┬─────╮\
│ one │ two │\
╞═══════════╪═════╡\
│ 'hello!' │ 10 │\
│ 'goodbye' │ 20 │\
╰───────────┴─────╯\
sqlite\> **.mode table**\
sqlite\> **select \* from tbl1;**\
+---------+-----+\
\| one \| two \|\
+---------+-----+\
\| hello! \| 10 \|\
\| goodbye \| 20 \|\
+---------+-----+\
sqlite\>\
There "qbox" mode is really just a convenience variant of "box" that automatically enables ["--quote on"](climode.md#opt-quote). Similarly "psql" (so named because it formats results in a manner similar to the "psql" command line utility of PostgreSQL) is really just "table" mode with the addition of the ["--border off" option](climode.md#opt-border).
## 3.6. Line wrapping
The tabular modes accept some additional options to control formatting. The "--wrap *N*" option (where *N* is an integer) causes columns to wrap text that is longer than N characters. Wrapping is disabled if N is zero.
sqlite\> **insert into tbl1 values('The quick fox jumps over a lazy brown dog.',90);**\
sqlite\> **.mode box --wrap 30**\
sqlite\> **select \* from tbl1 where two\>50;**\
╭────────────────────────────────┬─────╮\
│ one │ two │\
╞════════════════════════════════╪═════╡\
│ The quick fox jumps over a laz │ 90 │\
│ y brown dog. │ │\
╰────────────────────────────────┴─────╯\
sqlite\>\
Wrapping happens after exactly *N* characters, which might be in the middle of a word. To wrap at a word boundary, add the "--wordwrap on" option (or just "-ww" for short):
sqlite\> **.mode box --wrap 30 -ww**\
sqlite\> **select \* from tbl1 where two\>50;**\
╭────────────────────────────────┬─────╮\
│ one │ two │\
╞════════════════════════════════╪═════╡\
│ The quick fox jumps over a │ 90 │\
│ lazy brown dog. │ │\
╰────────────────────────────────┴─────╯\
sqlite\>\
The command ".mode box --wrap 60 --quote on" is so useful for general-purpose database queries that it is given its own alias. Instead of typing out that whole 30-character command, you can just say ".mode qbox".
## 3.7. Output mode "insert"
Another useful output mode is "insert". In insert mode, the output is formatted to look like SQL INSERT statements. Use insert mode to generate text that can later be used to input data into a different database.
When specifying insert mode, you have to give an extra argument which is the name of the table to be inserted into. For example:
sqlite\> **.mode insert new_table**\
sqlite\> **select \* from tbl1 where two\<50;**\
INSERT INTO new_table VALUES('hello',10),\
('goodbye',20);\
sqlite\>\
Multiple rows will be added as additional tuples onto the end of the INSERT statement until the size of the INSERT statement (in bytes) exceeds the ["--multiinsert" setting](climode.md#opt-multiinsert) (default: 3000). To force every row to be on a separate INSERT statement set --multiinsert to 0.
If the `--titles on` option is included in the `.mode` command, then the INSERT output will include that list of column names:
sqlite\> **.mode insert mytable --titles on**\
sqlite\> **select 1 a, 2 b, 3 c;**\
INSERT INTO mytable(a,b,c) VALUES(1,2,3);\
sqlite\>\
## 3.8. Output mode "split"
The column-split output mode, called use "split" and invoked using "`.mode split`", is a special case of the tabular "column" mode. The "split" mode only works on queries that return a single column and when the ["--screenwidth" option](climode.md#opt-sw) is not "off". Instead of displaying the results in a single vertical column, the "split" mode tries to wrap that column vertically so that the final output is two or more columns. The CLI creates as many columns as will fit on the screen.
The following example demonstrates using the "split" mode to list all built-in SQL functions whose names begin with "c" on a screen that is 55 characters wide:
sqlite\> **.mode --once split --sw 55**\
sqlite\> **SELECT name FROM pragma_function_list**\
...\> **WHERE name GLOB 'c\*'**\
...\> **ORDER BY name;**\
ceil coalesce cosh current_date\
ceiling concat count current_time\
changes concat_ws count current_timestamp\
char cos cume_dist\
sqlite3\>\
The CLI uses "split" mode internally to help it implement dot-commands like [.tables](cli.md#dtables)
## 3.9. Output modes "count" and "off"
The output modes "count" and "off" do not show any actual query results. Instead they show just the number of rows of results, or nothing at all, respectively. These modes are useful for running timing tests on queries that generate a lot of output where you do not care what the output is but only how long it takes to compute.
## 3.10. Output modes "batch" and "tty"
Two aliases "batch" and "tty" mean the default output mode for when the CLI is started as a script ("batch") and when the CLI is started from a terminal or console ("tty").
## 3.11. User Defined Output Modes
The ["--tag" option](climode.md#opt-tag) allows new customized output modes to be defined and named. The argument to --tag is the name of a new mode. All settings defined before the --tag are captured in that name and can be restored at a later time using "`.mode `*TAGNAME*".
# 4. Escaping Control Characters
By default (since version 3.50.0), the CLI avoids displaying most control characters in the range of U+0001 through U+001f even when such characters are within content strings that the CLI is trying to output. This is done to avoid problems when the output is viewed on a device that interprets [ANSI escape codes](https://en.wikipedia.org/wiki/ANSI_escape_code). The CLI avoids showing *most* control characters, but makes the following exceptions: TAB (0x09), LF (0x0a) and CRLF (0x0d,0x0a). The exceptions are passed through into the output unchanged.
The default behavior is for the CLI to display most control characters the same way the "cat -A" command does in Linux: For control character X, display two characters "^Y" where Y is X+0x40. For example, the "ESC" character (0x1b) is rendered as "^\[" and the backspace character (0x08) is rendered as "^H".
The rendering of control characters is governed by the "--escape T" command-line option to the CLI, or to the ".mode" dot-command, where T is the control-character handling algorithm. The default T is "ascii". If you change it to "--escape symbol" then control characters are mapped into printable unicode values in the range of U+2401 through U+241f. For example, ESC is rendered as "␛" and backspace becomes "␈". Setting "--escape off" turns off all control character mapping so that the characters output by the CLI are exactly what are in the database.
# 5. Line Endings
The default line ending on Windows can be either "\r\n" (CRLF) or "\n" NL. Even though it is closely related to output formatting, the line ending choice is controlled by a completely separate subsystem of the CLI implementation and thus has its own ".crlf" dot-command, separate from ".mode".
Use ".crlf on" to set the CRLF line ending and ".crlf off" for NL. As is traditional for Windows, CRLF is the default. However, this causes some outputs to be different than on non-Windows platforms due to the added "\r" characters. To cause the CLI to output results on Windows that are identical to the results on all other systems, run ".crlf off".
On non-Windows platforms, the ".crlf" command is a no-op and the crlf mode is always "off". For [CSV output](cli.md#csvout), the line ending is always "\r\n" regardless of the .crlf setting, due to requirements of RFC-4180.
# 6. Details On .mode Syntax And Options
The mode command works by processing its arguments from left to right. Order can be important. For example, settings to the left of the ["--reset" option](climode.md#opt-reset) will likely be rolled back because the reset is processed after those settings. But settings to the right will survive because the settings are changed after the reset.
Use the ".help mode" to get a quick summary of the options available on the ".mode" command. Keep reading below for details.
## 6.1. `--align` *STRING*
The alignment value is a string composed of characters 'L', 'C', and 'R' that determine how text is justified in tabular modes. 'L' means left (the default), 'C' means centered, and 'R' means right. Each letter in the string corresponds to a single column in the tabular output. If the output has more columns than there are letters in the alignment string, then the remaining columns are all left-justified.
## 6.2. `--blob-quote `*`ARG`*
The --blob-quote option (which can be abbreviated as just "--blob") determines how BLOB values are displayed. The argument can be one of "auto", "text", "sql", "hex", "tcl", "json", or "size".
The default --blob-quote setting is "auto" which means that the system selects an appropriate method of displaying BLOB values based on the current mode and/or the current ["--quote" setting](climode.md#opt-quote). The default is "auto" and that works best in most circumstances.
If ARG is "text", that means that the bytes of the BLOB value are interpreted as UTF-8 text and displayed as text. "sql" means that the BLOB is rendered as an SQL BLOB literal. "hex" means the BLOB value is displayed as hexadecimal. "tcl" means that the BLOB value is rendered as a double-quoted string where each byte is represented by traditional C-language backslash octal notation. For example, a BLOB value of x'424c4f42' would be rendered as `"\102\114\117\102"`. The "json" encoding is similar except that the individual bytes use JSON escape: `"\u0042\u004c\u004f\u0042"`. The "size" encoding does not try to show the BLOB content at all, but instead just shows the size of the BLOB as text, like this: `(482-byte blob)`
## 6.3. `--charlimit` *N*
Limit the number of characters to display for a single value in the output. If the output text is longer than N characters, it is truncated and an ellipsis are added at the end. If N is zero, then the character limit is disabled.
The character limit works in all output modes.
See also the ["--linelimit" option](climode.md#opt-linelimit), the ["--limits" option](climode.md#opt-limits), and the ["--titlelimit" option](climode.md#opt-tlim).
## 6.4. `--border` auto\|off\|on
The --border setting control whether or not a box appears around the outside of the entire result, or if only the interior divider lines are shown. This setting only affects "box" and "table" modes. The value of this setting is "off" then the border is omitted. Otherwise the border is shown. The default behavior is to show the outer border. The "psql" mode is an alias for the "table" mode but with the --border setting changed to "off".
## 6.5. `--colsep` *STRING*
Set the column-separator to *STRING*. Use double-quotes and backslash-escapes to use spaces and special characters like tab (\t) as part of the column-separator.
## 6.6. `--escape` *ESC*
Control how control characters are escaped in all output. Possible values for *ESC* are "off", "ascii", and "symbol". The "ascii" value is the default and is recommended.
## 6.7. `--linelimit` *N*
Do not display more than the first *N* lines of text for any single value. Lines can be split due to the text containing newline characters (U+000a) or due to column wrapping. Either way, this option causes the first *N* lines to be shown and then shows ellipsis for the *N+1*-th line. Set N to zero to disable the line limiter.
The line limiter only works for tabular modes and for "line" mode. It is ignored in all other modes.
See also the ["--charlimit" option](climode.md#opt-charlimit), the ["--limits" option](climode.md#opt-limits), and the ["--titlelimit" option](climode.md#opt-tlim)
## 6.8. `--limits` *L,C,T*
This option is shorthand for "`--linelimit L --charlimit C --titlelimit T`". In other words, when the argument is three integers L, C, and T separate by commas, then the line limit, the character limit, and the title limit are set to L, C, and T, respectively. If the ",T" is omitted, then only the line limit and character limit are changed and the title limit is unchanged. The argument to --limits can also be "off" which is an alias for "0,0,0" or "on" which sets all limits to reasonable built-in defaults.
## 6.9. `--list`
The "--list" option takes no arguments. It causes the ".mode" command to print a list of all available modes, including user-defined modes created using the ["--tag" option](climode.md#opt-tag).
## 6.10. `--multiinsert` *N*
The `--multiinsert` setting influences the output when in "insert" mode. The argument N governs how many rows of result are included in each INSERT statement. When N is positive, multiple rows are added as extra tuples in an INSERT statement until the total size of the INSERT statement exceeds N bytes. Subsequent rows will go into a new INSERT statement.
Setting `--multiinsert` to two or three thousand can make ".mode insert" output easier to read, and also faster to parse when moving the content to a different database engine.
## 6.11. `--null` *STRING*
The STRING argument becomes the text that the CLI displays for NULL values. Common choices are an empty string (which must be quoted as `""`), "null", and "NULL".
## 6.12. `--once`
The "--once" option means all setting changes to the right are transient and will rollback after the next SQL statement is run.
In the previous sentence, "next SQL statement" means the all SQL statements up to and including the next complete line of SQL input that ends with a semicolon. If two or more SQL queries occur on the same input line, all of them will be run before the mode is rolled back. So if you do (for example) "`.mode --once split`" then enter two SELECT statements on the next line of input, both of those SELECTs will be processed using "split" mode.
## 6.13. `--quote` *ARG*
The --quote option determines how text values are quoted prior to rendered. Possible arguments are: "off", "on", "sql", "relaxed", "csv", "html", "tcl", or "json".
When --quote is "off" the text is displayed as it appears in the database with no escapes.
The --quote value of "sql" means to display text as SQL text literals within single-quotes. A value of "relaxed" is similar, except that "relaxed" tries to avoid adding extra quoting syntax in cases where it is not needed. A value of "csv" means to quote text according to the rules specified for CSV file in RFC-4180. A value of "html" means to escape text for display in HTML, so that "\<" characters are rendered as "\<", and so forth. "tcl" means to put the text inside double-quotes and use backslash escape, as if for TCL, C, Perl, and other common programming languages. "json" is similar to "tcl" except that it uses only backslash escapes that are valid JSON.
The value of "on" is similar to "sql" except that "on" also changes the ["--null" option](climode.md#opt-null) to be "NULL".
## 6.14. `--reset`
The --reset option leaves the current mode unchanged, but it sets all the other various settings (--colsep, --null, --rowsep, and so forth) back to whatever the default is for that particular mode.
## 6.15. `--rowsep` *STRING*
Use STRING as the row separator.
## 6.16. `--screenwidth` *N*
This setting tells the CLI that the display device is N characters wide. The CLI then attempts to squeeze tabular and "line" mode outputs to fit within that many characters. If the argument is 0 or "off", that means the screenwidth is ignored an no attempt is made to squeeze the results down to any particular width.
The default value is "auto" which causes the CLI interrogate the display device to determine its actual width before each query is run. With the "auto" value, if you are running the CLI in a terminal or console window and you drag the window wider, the screenwidth setting is adjusted automatically.
The "--sw N" setting is a shorthand for "--screenwidth N".
The screenwidth is only used by [tabular modes](climode.md#clmnr) and by the [line mode](climode.md#linemode). Screenwidth limiting is "best effort" in the sense that the CLI works hard to squeeze the output to fit tha specified width, but might exceed the specified screenwidth if there is no way around it. For example, if the --screenwidth is 40 and you attempt to display a result with 50 different columns, there is clearly no way that will fit, and the screenwidth will be exceeded in that case.
## 6.17. `--tablename` *NAME*
Use "NAME" as the name of the table to insert into for "insert" mode.
## 6.18. `--tag` *NAME*
This option creates a new mode called NAME. After using this tag, you can say ".mode NAME" and all mode settings that were in effect when the --tag option was first executed will be restored.
The order of options is important here. The new mode will consist of all mode settings that are in effect at the moment that the "--tag" option is countered. Hence changes to the left of "--tag" are part of the new mode, but changes to the right of "--tag" are not.
## 6.19. `--textjsonb` *BOOLEAN*
If --testjsonb is enabled, then when displaying a BLOB value, the CLI first checks to see if the value is really a [JSONB](json1.md#jsonbx) blob, and if it is, it displays the equivalent text for that JSONB using whatever quoting mechanism is specified by the ["--quote" option](climode.md#opt-quote). If the BLOB to be displayed is not JSONB, then it is rendered using the current ["--blob-quote" option](climode.md#opt-blob).
## 6.20. `--title` *ARG*
The --title option determines whether or not to render column headers, and if so what text encoding to use for column headers. Whether or not to show column headers, and if so how to encode them. ARG can be "off", "on", "sql", "csv", "html", "tcl", or "json".
## 6.21. `--titlelimit` *N*
The --titlelimit option specifies a maximum width for the column titles in tabular and "line" modes. (Other modes are not currently affected by --titlelimit, but that could change in future releases.) If a column title is longer than the specified number of characters, then the title is truncated. Also, newline and tab characters within the title or changed into ordinary spaces.
The --titlelimit feature is useful to prevent oversize column titles when entering queries that use subqueries or complex expressions as result columns. Without an AS clause, the titles for such columns default to the complete text of the subquery or expression. That can result in unweldy tabular and/or line-mode output. Setting --titlelimit to a positive number (usually between about 10 or 20) can ensure more reasonable looking output. If --titlelimit is zero, then no limits on the length of the title are imposed.
See also the ["--charlimit option](climode.md#opt-charlimit), the ["--linelimit" option](climode.md#opt-linelimit), and the ["--limits" option](climode.md#opt-limits).
## 6.22. `--verbose`
If enabled, then the display of the current mode and settings shows every possible setting, even settings that currently hold their default value.
The "-v" option is shorthand for "--verbose".
## 6.23. `--widths` *LIST*
Set the columns widths for tabular modes. The argument is a list of integers, one for each column. A "0" width means use a dynamic width based on the actual width of data. If there are fewer entries in LIST than columns, "0" is used for the unspecified widths.
## 6.24. `--wordwrap` *BOOLEAN*
When the ["--wrap" option](climode.md#opt-wrap) requires longer texts to be wrapped, this option determine whether wrapping occurs at a word boundary or in the middle of a word. A value of true means that the CLI attempts to find a suitable word boundary at which to wrap.
For really long words, it might not possible find a word boundry, in which case the wrapping might still occur mid-word.
## 6.25. `--wrap` *N*
In tabular modes, this setting prevents any column from growing wider than N characters. If the text to be displayed is wider than N character, then the text wraps. An N value of 0 means there is no limit and table columns can be as wide as necessary to accomodate the text.
## 6.26. `--ww`
The "--ww" option, which does not take an argument, is simply a shorthand notation for "--wordwrap on".
---
# Quirks, Caveats, and Gotchas In SQLite
*Sección: Guides | Origen: https://www.sqlite.org/quirks.html*
# 1. Overview
The SQL language is a "standard". Even so, no two SQL database engines work exactly alike. Every SQL implementation has its own peculiarities and oddities, and SQLite is no exception to this rule.
This document strives to highlight the principal differences between SQLite and other SQL implementations, as an aid to developers that are porting to or from SQLite or who are trying to build a system that works across multiple database engines.
If you are an SQLite user who has stumbled over some quirk of SQLite that is not mentioned here, please let the developers know by posting a brief message on the [SQLite Forum](https://sqlite.org/forum/forum).
# 2. SQLite Is Embedded, Not Client-Server
Whenever 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](serverless.md). There is no separate server process that manages the database. An application interacts with the database engine using function calls, not by sending messages to a separate process or thread.
The fact that SQLite is embedded and [serverless](serverless.md) instead of being client/server is a feature, not a bug.
Client/server databases like MySQL, PostgreSQL, SQL Server, Oracle, and others are an important component of modern systems. These systems solve an important problem. But SQLite solves a different problem. Both SQLite and client/server databases have their role. Developers who are comparing SQLite against other SQL database engines need to clearly understand this distinction.
See the [Appropriate Uses For SQLite](whentouse.md) document for additional information.
# 3. Flexible Typing
SQLite is flexible with regard to datatypes. Datatypes are advisory rather than mandatory.
Some commentators say that SQLite is "weakly typed" and that other SQL databases are "strongly typed". We consider these terms to be inaccurate and even pejorative. We prefer to say that SQLite is "flexibly typed" and that other SQL database engines are "rigidly typed".
See the [Datatypes in SQLite](datatype3.md) document for a detailed discussion of the type system in SQLite.
The key point is that SQLite is very forgiving of the type of data that you put into the database. For example, if a column has a datatype of "INTEGER" and the application inserts a text string into that column, SQLite will first try to convert the text string into an integer, just like every other SQL database engine. Thus, if one inserts **'1234'** into an INTEGER column, that value is converted into an integer 1234 and stored. But, if you insert a non-numeric string like **'wxyz'** into an INTEGER column, unlike other SQL databases, SQLite does not throw an error. Instead, SQLite stores the actual string value in the column.
Similarly, SQLite allows you to store a 2000-character string into a column of type VARCHAR(50). Other SQL implementations would either throw an error or truncate the string. SQLite stores the entire 2000-character string with no loss of information and without complaint.
Where this ends up causing problems is when developers do some initial coding work using SQLite and get their application working, but then try to convert to another database like PostgreSQL or SQL Server for deployment. If the application is initially taking advantage of SQLite's flexible typing, then it will fail when moved to another database that is more judgmental about data types.
[Flexible typing is a feature](flextypegood.md) of SQLite, not a bug. Flexible typing is about freedom. Nevertheless, we recognize that this feature does sometimes cause confusion for developers who are accustomed to working with other databases that are more strict with regard to data type rules. In retrospect, perhaps it would have been less confusing if SQLite had merely implemented an ANY datatype so that developers could explicitly state when they wanted to use flexible typing, rather than making flexible typing the default. As an accommodation for those who expect rigid typing, SQLite version 3.37.0 (2021-11-27) introduced the option of [STRICT tables](stricttables.md). These either impose the mandatory datatype constraints found in other SQL database engines, or allow the explicit ANY datatype to retain SQLite's flexible typing.
## 3.1. No Separate BOOLEAN Datatype
Unlike most other SQL implementations, SQLite does not have a separate BOOLEAN data type. Instead, TRUE and FALSE are (normally) represented as integers 1 and 0, respectively. This does not seem to cause many problems, as we seldom get complaints about it. But it is important to recognize.
Beginning with SQLite [version 3.23.0](releaselog/3_23_0.md) (2018-04-02), SQLite also recognizes TRUE and FALSE keywords as aliases for integer values 1 and 0, respectively. This provides better compatibility with other SQL implementations. But for backwards compatibility, if there are columns named TRUE or FALSE, then the keywords are treated as identifiers referencing those columns, rather than BOOLEAN literals.
## 3.2. No Separate DATETIME Datatype
SQLite has no DATETIME datatype. Instead, dates and times can be stored in any of these ways:
- As a TEXT string in the ISO-8601 format. Example: '2018-04-02 12:13:46'.
- As an INTEGER number of seconds since 1970 (also known as "unix time").
- As a REAL value that is the fractional [Julian day number](https://en.wikipedia.org/wiki/Julian_day).
The built-in [date and time functions](lang_datefunc.md) of SQLite understand date/times in all of the formats above, and can freely change between them. Which format you use, is entirely up to your application.
## 3.3. The datatype is optional
Because SQLite is flexible and forgiving with regard to datatypes, table columns can be created that have no specified datatype at all. For example:
CREATE TABLE t1(a,b,c,d);\
The table "t1" has four columns "a", "b", "c", and "d" that have no particular datatype assigned. You can store anything you want in any of those columns.
# 4. Foreign Key Enforcement Is Off By Default
SQLite has parsed foreign key constraints for time out of mind, but added the ability to actually enforce those constraints much later, with [version 3.6.19](releaselog/3_6_19.md) (2009-10-14). By the time foreign key constraint enforcement was added, there were already countless millions of databases in circulation that contained foreign key constraints, some of which were not correct. To avoid breaking those legacy databases, foreign key constraint enforcement is turned off by default in SQLite.
Applications can activate foreign key enforcement at run-time using the [PRAGMA foreign_keys](pragma.md#pragma_foreign_keys) statement. Or, foreign key enforcement can be activated at compile-time using the [-DSQLITE_DEFAULT_FOREIGN_KEYS=1](compile.md#default_foreign_keys) compile-time option.
# 5. PRIMARY KEYs Can Sometimes Contain NULLs
A PRIMARY KEY in an SQLite table is usually just a UNIQUE constraint. Due to an historical oversight, the column values of a PRIMARY KEY are allowed to be NULL. This is a bug, but by the time the problem was discovered there where so many databases in circulation that depended on the bug that the decision was made to support the buggy behavior moving forward. You can work around this problem by adding a NOT NULL constraint on each column of the PRIMARY KEY.
Exceptions:
- The value of an [INTEGER PRIMARY KEY](lang_createtable.md#rowid) column must always be a non-NULL integer because the INTEGER PRIMARY KEY is an alias for the [ROWID](lang_createtable.md#rowid). If you try to insert a NULL into an INTEGER PRIMARY KEY column, SQLite automatically converts the NULL into a unique integer.
- The [WITHOUT ROWID](withoutrowid.md) and [STRICT](stricttables.md) features was added after this bug was discovered, and so WITHOUT ROWID and STRICT tables work correctly: They disallow NULLs in the PRIMARY KEY.
# 6. Aggregate Queries Can Contain Non-Aggregate Result Columns That Are Not In The GROUP BY Clause
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).
SQLite does not enforce this restriction. The output columns from an aggregate query can be arbitrary expressions that include columns not found in the GROUP BY clause. This feature has two uses:
1. With SQLite (but not any other SQL implementation that we know of) if an aggregate query contains a single min() or max() function, then the values of columns used in the output are taken from the row where the min() or max() value was achieved. If two or more rows have the same min() or max() value, then the columns values will be chosen arbitrarily from one of those rows.
For example to find the highest paid employee:
SELECT max(salary), first_name, last_name FROM employee;\
In the query above, the values for the first_name and last_name columns will correspond to the row that satisfied the max(salary) condition.
2. If a query contains no aggregate functions at all, then a GROUP BY clause can be added as a substitute for the DISTINCT ON clause. In other words, output rows are filtered so that only one row is shown 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. (SQLite supports DISTINCT but not DISTINCT ON, whose functionality is provided instead by GROUP BY.)
# 7. SQLite Does Not Do Full Unicode Case Folding By Default
SQLite does not know about the upper-case/lower-case distinction for all unicode characters. SQL functions like upper() and lower() only work on ASCII characters. There are two reasons for this:
1. Though stable now, when SQLite was first designed, the rules for unicode case folding were still in flux. That means that the behavior might have changed with each new unicode release, disrupting applications and corrupting indexes in the process.
2. The tables necessary to do full and proper unicode case folding are larger than the whole SQLite library.
Full unicode case folding is supported in SQLite if it is compiled with the [-DSQLITE_ENABLE_ICU](compile.md#enable_icu) option and linked against the [International Components for Unicode](https://icu.unicode.org) library.
# 8. Double-quoted String Literals Are Accepted
The SQL standard requires double-quotes around identifiers and single-quotes around string literals. For example:
- `"this is a legal SQL column name"`
- `'this is an SQL string literal'`
SQLite accepts both of the above. But, in an effort to be compatible with MySQL 3.x (which was one of the most widely used RDBMSes 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.
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.
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 that capability to avoid breaking legacy.
As of SQLite 3.27.0 (2019-02-07) the use of a double-quoted string literal causes a warning message to be sent to the [error log](errlog.md).
As of SQLite 3.29.0 (2019-07-10) the use of double-quoted string literals can be disabled at run-time using the [SQLITE_DBCONFIG_DQS_DDL](c3ref/c_dbconfig_defensive.md#sqlitedbconfigdqsddl) and [SQLITE_DBCONFIG_DQS_DML](c3ref/c_dbconfig_defensive.md#sqlitedbconfigdqsdml) actions to [sqlite3_db_config()](c3ref/db_config.md). The default settings can be altered at compile-time using the [-DSQLITE_DQS=*N*](compile.md#dqs) compile-time option. Application developers are encouraged to compile using -DSQLITE_DQS=0 in order to disable the double-quoted string literal misfeature by default. If that is not possible, then disable double-quoted string literals for individual database connections using C-code like this:
> \
> sqlite3_db_config(db, SQLITE_DBCONFIG_DQS_DDL, 0, (void\*)0);\
> sqlite3_db_config(db, SQLITE_DBCONFIG_DQS_DML, 0, (void\*)0);\
Or, if double-quoted string literals are disabled by default, but need to be selectively enabled for some historical database connections, that can be done using the same C-code as shown above except with the third parameter changed from 0 to 1.
As of SQLite 3.41.0 (2023-02-21) SQLITE_DBCONFIG_DQS_DDL and SQLITE_DBCONFIG_DQS_DML are disabled by default in the [CLI](cli.md). Use the ".dbconfig" dot-command to reenable the legacy behavior if desired.
# 9. Keywords Can Often Be Used As Identifiers
The SQL language is rich in keywords. Most SQL implementations do not allow keywords to be used as identifiers (names of tables or columns) unless they are enclosed in double-quotes. But SQLite is more flexible. Many keywords can be used as identifiers without needing to be quoted, as long as those keywords are used in a context where it is clear that they are intended to be an identifier.
For example, the following statement is valid in SQLite:
CREATE TABLE union(true INT, with BOOLEAN);\
The same SQL statement will fail on every other SQL implementation that we know of due to the use of keywords "union", "true", and "with" as identifiers.
The ability to use keywords as identifiers promotes backwards compatibility. As new keywords are added, legacy schemas that just happen to use those keywords as table or column names continue to work. However, the ability to use a keyword as an identifier sometimes leads to surprising outcomes. For example:
CREATE TRIGGER AFTER INSERT ON tableX BEGIN\
INSERT INTO tableY(b) VALUES(new.a);\
END;\
The trigger created by the previous statement is named "AFTER" and it is a "BEFORE" trigger. The "AFTER" token is used as an identifier instead of as a keyword, as that is the only way to parse the statement. Another example:
CREATE TABLE tableZ(INTEGER PRIMARY KEY);\
The tableZ table has a single column named "INTEGER". That column has no datatype specified, but it is the PRIMARY KEY. The column is *not* the [INTEGER PRIMARY KEY](lang_createtable.md#rowid) for the table because it has no datatype. The "INTEGER" token is used as an identifier for the column name, not as a datatype keyword.
# 10. Dubious SQL Is Allowed Without Any Error Or Warning
The original implementation of SQLite sought to follow [Postel's Law](https://en.wikipedia.org/wiki/Robustness_principle) which states in part "Be liberal in what you accept". This used to be considered good design - that a system would accept dodgy inputs and try to do the best it could without complaining too much. More recently, people have come to prefer software that is strict in what it accepts, so as to more easily find errors.
There are now millions of applications that take advantage of SQLite's flexible and forgiving design choices. We cannot change SQLite to follow the current preference toward strict and dogmatic behavior without breaking those legacy applications.
# 11. AUTOINCREMENT Does Not Work The Same As MySQL
The [AUTOINCREMENT](autoinc.md) feature in SQLite works differently than it does in MySQL. This often causes confusion for people who initially learned SQL on MySQL and then start using SQLite, and expect the two systems to work identically.
See the [SQLite AUTOINCREMENT documentation](autoinc.md) for detailed instructions on what AUTOINCREMENT does and does not do in SQLite.
# 12. NUL Characters Are Allowed In Text Strings
NUL characters (ASCII code 0x00 and Unicode \u0000) may appear in the middle of strings in SQLite. This can lead to unexpected behavior. See the "[NUL characters in strings](nulinstr.md)" document for further information.
# 13. SQLite Distinguishes Between Integer And Text Literals
SQLite says that the following query returns false:
SELECT 1='1';\
It does this because an integer is not a string. Every other major SQL database engine says this is true, for reasons that the creator of SQLite does not understand.
# 14. SQLite Gets The Precedence Of Comma-Joins Wrong
SQLite gives all join operators equal precedence and processes them from left to right. But this is not quite correct. It should be that comma-joins have lower precedence than all others join operators. In other words, a FROM clause like this:
> ... FROM a, b RIGHT JOIN c, d ...
Should be parsed as follows:
But SQLite instead parses the FROM clause like this:
The problem can only make a difference in the result when using RIGHT OUTER JOIN or FULL OUTER JOIN in the same FROM clause with comma-joins, which rarely happens in practice. And the problem can be easily overcome using parentheses in the FROM clause:
> ... FROM a, (b RIGHT JOIN c), d ...
---
# Rebase a changeset
*Sección: Guides | Origen: https://www.sqlite.org/session/sqlite3rebaser_rebase.html*
[](../session/intro.md)
## Session Module C Interface
## Rebase a changeset
> int sqlite3rebaser_rebase(\
> sqlite3_rebaser\*,\
> int nIn, const void \*pIn, \
> int \*pnOut, void \*\*ppOut \
> );\
**Important:** This interface is [experimental](../c3ref/experimental.md) and is subject to change without notice.
Argument pIn must point to a buffer containing a changeset nIn bytes in size. This function allocates and populates a buffer with a copy of the changeset rebased according to the configuration of the rebaser object passed as the first argument. If successful, (\*ppOut) is set to point to the new buffer containing the rebased changeset and (\*pnOut) to its size in bytes and SQLITE_OK returned. It is the responsibility of the caller to eventually free the new buffer using sqlite3_free(). Otherwise, if an error occurs, (\*ppOut) and (\*pnOut) are set to zero and an SQLite error code returned.
See also lists of [Objects](../session/objlist.md), [Constants](../session/constlist.md), and [Functions](../session/funclist.md).
---
# Rebasing changesets
*Sección: Guides | Origen: https://www.sqlite.org/session/rebaser.html*
[](../session/intro.md)
## Session Module C Interface
## Rebasing changesets
> typedef struct sqlite3_rebaser sqlite3_rebaser;\
**Important:** This interface is [experimental](../c3ref/experimental.md) and is subject to change without notice.
Suppose there is a site hosting a database in state S0. And that modifications are made that move that database to state S1 and a changeset recorded (the "local" changeset). Then, a changeset based on S0 is received from another site (the "remote" changeset) and applied to the database. The database is then in state (S1+"remote"), where the exact state depends on any conflict resolution decisions (OMIT or REPLACE) made while applying "remote". Rebasing a changeset is to update it to take those conflict resolution decisions into account, so that the same conflicts do not have to be resolved elsewhere in the network.
For example, if both the local and remote changesets contain an INSERT of the same key on "CREATE TABLE t1(a PRIMARY KEY, b)":
local: INSERT INTO t1 VALUES(1, 'v1'); remote: INSERT INTO t1 VALUES(1, 'v2');
and the conflict resolution is REPLACE, then the INSERT change is removed from the local changeset (it was overridden). Or, if the conflict resolution was "OMIT", then the local changeset is modified to instead contain:
UPDATE t1 SET b = 'v2' WHERE a=1;
Changes within the local changeset are rebased as follows:
Local INSERT
This may only conflict with a remote INSERT. If the conflict resolution was OMIT, then add an UPDATE change to the rebased changeset. Or, if the conflict resolution was REPLACE, add nothing to the rebased changeset.
Local DELETE
This may conflict with a remote UPDATE or DELETE. In both cases the only possible resolution is OMIT. If the remote operation was a DELETE, then add no change to the rebased changeset. If the remote operation was an UPDATE, then the old.\* fields of change are updated to reflect the new.\* values in the UPDATE.
Local UPDATE
This may conflict with a remote UPDATE or DELETE. If it conflicts with a DELETE, and the conflict resolution was OMIT, then the update is changed into an INSERT. Any undefined values in the new.\* record from the update change are filled in using the old.\* values from the conflicting DELETE. Or, if the conflict resolution was REPLACE, the UPDATE change is simply omitted from the rebased changeset.
If conflict is with a remote UPDATE and the resolution is OMIT, then the old.\* values are rebased using the new.\* values in the remote change. Or, if the resolution is REPLACE, then the change is copied into the rebased changeset with updates to columns also updated by the conflicting remote UPDATE removed. If this means no columns would be updated, the change is omitted.
A local change may be rebased against multiple remote changes simultaneously. If a single key is modified by multiple remote changesets, they are combined as follows before the local changeset is rebased:
- If there has been one or more REPLACE resolutions on a key, it is rebased according to a REPLACE.
- If there have been no REPLACE resolutions on a key, then the local changeset is rebased according to the most recent of the OMIT resolutions.
Note that conflict resolutions from multiple remote changesets are combined on a per-field basis, not per-row. This means that in the case of multiple remote UPDATE operations, some fields of a single local change may be rebased for REPLACE while others are rebased for OMIT.
In order to rebase a local changeset, the remote changeset must first be applied to the local database using sqlite3changeset_apply_v2() and the buffer of rebase information captured. Then:
1. An sqlite3_rebaser object is created by calling sqlite3rebaser_create().
2. The new object is configured with the rebase buffer obtained from sqlite3changeset_apply_v2() by calling sqlite3rebaser_configure(). If the local changeset is to be rebased against multiple remote changesets, then sqlite3rebaser_configure() should be called multiple times, in the same order that the multiple sqlite3changeset_apply_v2() calls were made.
3. Each local changeset is rebased by calling sqlite3rebaser_rebase().
4. The sqlite3_rebaser object is deleted by calling sqlite3rebaser_delete().
See also lists of [Objects](../session/objlist.md), [Constants](../session/constlist.md), and [Functions](../session/funclist.md).
---
# Recent SQLite News
*Sección: Guides | Origen: https://www.sqlite.org/news.html*
## Recent News
### 2026-07-24 - [Version 3.53.4](releaselog/3_53_4.md)
> SQLite version 3.53.4 is a maintenance patch release for 3.53, with fixes for (mostly) AI-discovered bugs.
>
> There was a huge rush of AI-aided bug reporting shortly after the 3.53.0 release (2026-04-09), but lately the rate of bug reports has declined noticably, and the bugs that are being reported are increasingly insignificant. Could it be that the AI-bug avalanche is coming to an end, and that all of the bugs that AIs are able to find have now nearly all been found and fixed? Watch this news log for updates. Perhaps this will be the last patch release for 3.53 and that the next release will be 3.54.0, with enhancements and new features.
------------------------------------------------------------------------
### 2026-06-26 - [Version 3.53.3](releaselog/3_53_3.md)
> SQLite version 3.53.3 is a maintenance patch release for 3.53.
------------------------------------------------------------------------
### 2026-06-03 - [Version 3.53.2](releaselog/3_53_2.md)
> SQLite version 3.53.2 is a maintenance patch release for 3.53.
------------------------------------------------------------------------
### 2026-05-05 - [Version 3.53.1](releaselog/3_53_1.md)
> SQLite version 3.53.1 is a maintenance patch release for 3.53.
------------------------------------------------------------------------
### 2026-04-09 - [Version 3.53.0](releaselog/3_53_0.md)
> SQLite version 3.53.0 is a re-release of [version 3.52.0](releaselog/3_52_0.md) with additional enhancements to address the problem of [stale expression indexes](staleexpridx.md).
>
> The [WAL-reset bug](wal.md#walresetbug) is fixed in this release. This is the first major release (if you don't count 3.52.0) that contains a fix for that bug, so upgrading is recommended.
>
> See the [version 3.53.0 change log](releaselog/3_53_0.md) for a list of the many other enhancements included in 3.53.0.
------------------------------------------------------------------------
### 2026-03-13 - [Version 3.51.3](releaselog/3_51_3.md)
> SQLite version 3.52.0 has been withdrawn because some of the new features found in 3.52.0 are not 100% compatible with prior releases. Those new features and their associated APIs need to be reworked before 3.52 is made available.
>
> In place of 3.52.0, patch release 3.51.3 is now available. Patch release 3.51.3 fixes the [WAL-reset bug](wal.md#walresetbug) as well as other minor problems that have come to light since the 3.51.2 release.
>
> Version 3.52.0 works fine and is fully backwards compatible as long as the database does not contain [indexes on expressions](expridx.md) or indexes on [VIRTUAL computed columns](gencol.md) where the expression evaluates to a floating-point number that is derived from text or [JSONB](json1.md#jsonbx) inputs. If indexes of that type are present, then version 3.52.0 might not interoperate correct with prior releases, in rare cases.
------------------------------------------------------------------------
### 2026-03-06 - [Version 3.52.0](releaselog/3_52_0.md)
> SQLite version 3.52.0 is a major release with many important changes, the two most important of which (in my opinion) are:
>
> 1. A 15-year-old [database corruption bug](wal.md#walresetbug) was discovered just a few days ago, and is now fixed.
> 2. The [command-line interface](cli.md) utility has been significantly enhanced, especially in how it [formats query results](climode.md).
>
> See the [change log](releaselog/3_52_0.md) for a more complete list.
>
> The previous release was about four months ago. We are *striving* to slow the release cadence of SQLite to about once every six months. This is not a promise, only a goal. We'll see how it goes.
------------------------------------------------------------------------
### 2026-01-09 - [Version 3.51.2](releaselog/3_51_2.md)
> Patch release 3.51.2 fixes a potential (but unlikely) deadlock in the OS interface for unix that can arise due to changes in 3.51.0 that were designed to detect broken Posix Advisory Locks cause by the application mistakenly directly opening and closing a file descriptor to the database file and not going through the SQLite interface. The patch also fixes some other obscure bugs that are of little importance, but still ought to be addressed. Changes from 3.51.0 and 3.51.1 are minimal.
------------------------------------------------------------------------
### 2025-11-28 - [Version 3.51.1](releaselog/3_51_1.md)
> Patch release 3.51.1 fixes two cases of incorrect answers to corner-case queries caused by new optimizations in version 3.51.0.
------------------------------------------------------------------------
### 2025-11-04 - [Version 3.51.0](releaselog/3_51_0.md)
> Version 3.51.0 is the first major update to SQLite since the 25th anniversary release on 2025-05-29. Version 3.51.0 includes new features, new interfaces, and new optimizations. See the [3.51.0 change log](releaselog/3_51_0.md) for more detail.
------------------------------------------------------------------------
### 2025-07-30 - [Version 3.50.4](releaselog/3_50_4.md)
> Version 3.50.4 is a patch release to fix minor problems reported since the previous release.
------------------------------------------------------------------------
### 2025-07-17 - [Version 3.50.3](releaselog/3_50_3.md)
> Version 3.50.3 is a patch release to fix minor problems reported since the previous release.
------------------------------------------------------------------------
### 2025-06-28 - [Version 3.50.2](releaselog/3_50_2.md)
> Version 3.50.2 is a patch release to fix minor problems reported since the previous release.
------------------------------------------------------------------------
### 2025-06-06 - [Version 3.50.1](releaselog/3_50_1.md)
> Version 3.50.1 is a small patch to fix minor problems in the 3.50.0 release. Upgrading is recommended.
------------------------------------------------------------------------
### 2025-05-29 - [Version 3.50.0](releaselog/3_50_0.md)
> Version 3.50.0 is the twenty-fifth anniversary release of SQLite.
------------------------------------------------------------------------
### 2025-05-07 - [Version 3.49.2](releaselog/3_49_2.md)
> Patch release 3.49.2 fixes various bugs. The most important problem is a mistake in the NOT NULL optimization that was added to version 3.40.0 (see item 3c in the [version 3.40.0 change log](releaselog/3_40_0.md)) that if abused by an attacker with SQL injection capabilities can lead to read off the end of a static array, resulting in a segfault and possible denial of service. This patch release is mostly to address that one mistake. The other fixes could have waited for the next major release.
>
> The 3.50.0 release is still scheduled for 2025-05-29, which is only about three weeks away. All the same bug fixes will be in the 3.50.0 release, so you might want to wait for that release to come up before upgrading.
------------------------------------------------------------------------
### 2025-02-18 - [Version 3.49.1](releaselog/3_49_1.md)
> Patch release 3.49.1 fixes a problem in the [concat_ws() SQL function](lang_corefunc.md#concat_ws). The problem has existed since version 3.44.0 (2023-11-01) but was only discovered two days ago. The problem is a potential vulnerability. An attacker who can control the separator string and can make that string very large (hundreds of megabytes) could cause a memory error. Your system is not vulnerable if you are following the [recommended application security practices](security.md), especially recommendation number 2, or if your system does not use the concat_ws() function and is impervious to SQL injections. Regardless of whether or not your system is subject to this problem, you will do well to upgrade to version 3.49.1 or later.
>
> The 3.49.1 patch release also makes multiple improvements to the portability of configure scripts and makefiles. These improvements involve a lot of change, but only to makefiles and configuration scripts. The core SQLite library is unaffected by those enhancements.
------------------------------------------------------------------------
### 2025-02-06 - [Version 3.49.0](releaselog/3_49_0.md)
> There were a lot of minor patches and bug fixes that needed to be added to the 3.48.0 release. We were originally planning to do a patch release 3.48.1 to publish those changes. But we noticed that the patches formed a significant fraction of all changes on the main development trunk, and the trunk was stable, so we decided instead just to do an early release of version 3.49.0.
>
> Hence, the 3.49.0 release is being published less than one month after the 3.48.0 release. Version 3.49.0 contains both patches for minor issues in the 3.48.0 release and new enhancements. See the [change log](releaselog/3_49_0.md) for details.
>
> We expect that the next major release (3.50.0) will resume the usual 5-to-7 month cadence.
------------------------------------------------------------------------
### 2025-01-14 - [Version 3.48.0](releaselog/3_48_0.md)
> Version 3.48.0 refactors the "./configure" system of SQLite to fix bugs, simplify usage, improve performance, and make it easier to maintain moving forward. Though the internal changes are extensive, the user interface should remain the same. Unless you were doing something bizarre and undocumented with ./configure, you should not notice the difference.
>
> **NB:** This change applies to the configure system in the [canonical source code](amalg-v-canon.md#canon) only. The amalgamation tarball (the sqlite-autoconf-xxxxxx.tar.gz download) is unaffected.
>
> The ./configure implementation has changed to use [Autosetup](https://msteveb.github.io/autosetup/) instead of GNU Autoconf. One benefit of this is that TCL is no longer necessary to build SQLite from canonical sources, thus simplifying the build process. Just download the canonical source code, unpack it, and run "./configure && make". No third-party software packages (other than the C compiler and related tools like "make") are needed in most cases. The Windows makefile ("Makefile.msc") also now runs without TCL. Note, however, that TCL is still required to run tests or to build tools such as [sqlite3_analyzer](sqlanalyze.md) that link against libtcl.
>
> There are other minor enhancements in the 3.48.0 release, but the refactor of the ./configure system is by far the biggest and most important change. See the [change log](releaselog/3_48_0.md) for more detail.
------------------------------------------------------------------------
### 2024-12-07 - [Version 3.47.2](releaselog/3_47_2.md)
> Versions 3.47.0 and 3.47.1 contain a bug in the text-to-floating-point conversion routines such that numbers where the 16 most significant digits are "1844674407370955" might be converted to floating point incorrectly on x64 and i386 hardware. This is not an issue on ARM or PPC (the only other CPUs that the SQLite devs have access to), only x64/i386. Version 3.47.2 addresses the problems. You should upgrade to 3.47.2 or later if you are using any prior 3.47.x release.
------------------------------------------------------------------------
### 2024-11-25 - [Version 3.47.1](releaselog/3_47_1.md)
> Version 3.47.1 is a patch release with minimal changes from version 3.47.0. The purpose of the patch is to fix various issues in the 3.47.0 release.
------------------------------------------------------------------------
### 2024-10-21 - [Version 3.47.0](releaselog/3_47_0.md)
> Version 3.47.0 is an enhancement release with many feature improvements and performance enhancements. Of particular note:
>
> - The [sqlite3_rsync](rsync.md) command-line utility is now available for doing bandwidth-efficient live backups over SSH.
> - Integration with [TCL9](https://www.theregister.com/2024/10/02/tcltk_version_9/).
>
> See the [change log](releaselog/3_47_0.md) for details.
------------------------------------------------------------------------
### 2024-08-13 - [Version 3.46.1](releaselog/3_46_1.md)
> Version 3.46.1 is a patch release that fixes several minor problems in version 3.46.0. There are minimal changes from the previous release.
------------------------------------------------------------------------
### 2024-05-23 - [Version 3.46.0](releaselog/3_46_0.md)
> Version 3.46.0 is an enhancement release. Enhancements include:
>
> - Improvements to the [PRAGMA optimize](pragma.md#pragma_optimize) command
> - Enhancements to the [date and time functions](lang_datefunc.md)
> - The ability to put "\_" between digits in numeric literals for readability
> - Added the [json_pretty()](json1.md#jpretty) function
> - Improvements to the query planner, especially a new faster implementation for VALUES clauses with many terms.
>
> None of these enhancements are critical. Update at your convenience.
------------------------------------------------------------------------
### 2024-04-15 - [Version 3.45.3](releaselog/3_45_3.md)
> Version 3.45.3 is a patch release that fixes a few obscure problems, including:
>
> - The "old.\*" values in an [UPDATE trigger](lang_createtrigger.md) might be incorrect if the trigger fires in response to an [UPSERT](lang_upsert.md).
> - The [sum()](lang_aggfunc.md#sumunc) function might return NULL in some cases where Infinity would be a better answer.
>
> None of the problems are emergencies. Upgrade at your convenience.
------------------------------------------------------------------------
### 2024-03-12 - [Version 3.45.2](releaselog/3_45_2.md)
> Version 3.45.2 is a patch against SQLite versions 3.45.0 and 3.45.1.
>
> The primary reason for this patch is to fix two three-year-old bugs identified by Forum posts [919c6579c8](https://sqlite.org/forum/forumpost/919c6579c8) and [440f2a2f17](https://sqlite.org/forum/forumpost/440f2a2f17). These problems could result in incorrect query results or corrupt indexes. See the associated forum threads for details.
>
> Other trifling fixes are also included in the patch.
------------------------------------------------------------------------
### 2024-01-30 - [Version 3.45.1](releaselog/3_45_1.md)
> Version 3.45.1 is a patch against SQLite version 3.45.0.
>
> The main focus of this patch release is to restore certain undocumented legacy behavior in the [JSON SQL functions](json1.md) that the developers were unaware of but which some applications had come to depend on. This undocumented behavior was "fixed" in the 3.45.0, resulting in breakage for applications that were using it. So it has now been restored and documented.
>
> Other obscure issues that have come up since the 3.45.0 release, some related to the release itself and some going back years, are also fixed.
------------------------------------------------------------------------
### 2024-01-15 - [Version 3.45.0](releaselog/3_45_0.md)
> Version 3.45.0 is an enhancement release of SQLite.
>
> The most impactful change is likely enhancements to the [JSON SQL functions](json1.md) such that they are now able to store their internal JSON parse trees in the database as BLOB values. This can significantly increase the performance of applications that process large JSON strings as it omits the need to translate JSON text to and from the internal binary format used by SQLite.
>
> A second noteworthy change is that any [application-defined SQL functions](appfunc.md) that make use of the [sqlite3_result_subtype()](c3ref/result_subtype.md) interface must now include the [SQLITE_RESULT_SUBTYPE](c3ref/c_deterministic.md#sqliteresultsubtype) attribute when the function is registered using [sqlite3_create_function()](c3ref/create_function.md) or similar. Failure to include the SQLITE_RESULT_SUBTYPE attribute on functions that use [sqlite3_result_subtype()](c3ref/result_subtype.md) might result in incorrect answers.
>
> See the [change log](releaselog/3_45_0.md) for additional enhancements that are part of the 3.45.0 release.
------------------------------------------------------------------------
### 2023-11-24 - [Version 3.44.2](releaselog/3_44_2.md)
> The [CLI](cli.md) fix in version 3.44.1 introduced a new bug, which is fixed by patch release 3.44.2. Version 3.44.2 also fixes an FTS5 problem that was found by a fuzzer just minutes after the 3.44.1 release.
------------------------------------------------------------------------
### 2023-11-22 - [Version 3.44.1](releaselog/3_44_1.md)
> Version 3.44.1 is a patch release that fixes various obscure bugs. There is no need to upgrade, unless you are having problems with a prior release.
------------------------------------------------------------------------
### 2023-11-01 - [Version 3.44.0](releaselog/3_44_0.md)
> Version 3.44.0 is a new enhancement release of SQLite.
>
> It has only been 69 days since the previous major release (3.43.0). The original plan was for version 3.44.0 to occur at a spacing of approximately 120 days from the prior release. However, the code accumulated so many important enhancements that it seemed better to accelerate the release of 3.44.0, thus getting those enhancements into circulation. This means that some enhancements that were originally planned to be in 3.44.0 have been deferred until subsequent releases.
------------------------------------------------------------------------
### 2023-10-10 - [Version 3.43.2](releaselog/3_43_2.md)
> Version 3.43.2 is a patch release that fixes a few small inaccuracies in version 3.43.0 and 3.43.1.
------------------------------------------------------------------------
### 2023-09-11 - [Version 3.43.1](releaselog/3_43_1.md)
> Version 3.43.1 is a patch release that fixes a few small inaccuracies that were discovered in the the 3.43.0 and/or 3.42.0 releases after the 3.43.0 release was published.
------------------------------------------------------------------------
### 2023-08-24 - [Version 3.43.0](releaselog/3_43_0.md)
> Version 3.43.0 is a routine enhancement release of SQLite. Key enhancements in this release include added support for [Contentless-Delete FTS5 Indexes](fts5.md#clssdeltab), and performance improvements in [JSON processing](json1.md). See the [change log](releaselog/3_43_0.md) for details.
------------------------------------------------------------------------
### 2023-05-16 - [Version 3.42.0](releaselog/3_42_0.md)
> Version 3.42.0 is a routine enhancement release of SQLite. Key enhancements in this release are added support for [JSON5](json1.md#json5) and the [FTS5 secure-delete command](fts5.md#the_secure_delete_configuration_option). See the [change log](releaselog/3_42_0.md) for a summary of all enhancements in this release.
------------------------------------------------------------------------
### 2023-03-22 - [Version 3.41.2](releaselog/3_41_2.md)
> Version 3.41.2 is a patch release that fixes multiple fuzzer-found problems in prior releases. The worst problems include reads (not writes) past the end of a buffer. Upgrading is recommended.
------------------------------------------------------------------------
### 2023-03-10 - [Version 3.41.1](releaselog/3_41_1.md)
> Version 3.41.1 is a patch release that fixes various obscure problems found in 3.41.0 and reported by users. Upgrading is optional.
------------------------------------------------------------------------
### 2023-02-21 - [Version 3.41.0](releaselog/3_41_0.md)
> Version 3.41.0 is a routine enhancement release.
------------------------------------------------------------------------
### 2022-12-28 - [Version 3.40.1](releaselog/3_40_1.md)
> Version 3.40.1 is a patch release that fixes some obscure problems in version 3.40.0. The problems fixed have no impact on most applications. Upgrading is only necessary if you encounter problems.
>
> The two most important fixes are these:
>
> - Fix the [safe command-line option](cli.md#safemode) on the [CLI](cli.md) so that it correctly disallows functions with side-effects. This is a bug in the CLI — *not* a bug in the SQLite library — and it only affects the --safe command-line option, making that option less than fully "safe". As the number of systems that use the --safe command-line option in the CLI is approximately zero, this is not considered an important bug. However, a third-party wrote a CVE against it which caused considerable angst among maintainers, so it seems good to get the fix into circulation sooner rather than wait on the next major release.
>
> - The optional [memsys5](malloc.md#memsys5) memory allocator picked up a bug that might put it into an infinite loop for very large (500MiB) allocations. Almost all systems use their native memory allocator, not memsys5. Memsys5 is only used if SQLite is compiled using SQLITE_ENABLE_MEMSYS5 and then initialized using [sqlite3_config](c3ref/config.md)([SQLITE_CONFIG_HEAP](c3ref/c_config_covering_index_scan.md#sqliteconfigheap)). Very, very few systems do this, and so the problem is not considered to be serious.
>
> See the [branch-3.40 timeline](https://sqlite.org/src/timeline?r=branch-3.40) for a complete listing of changes that have gone into this patch release.
------------------------------------------------------------------------
### 2022-11-16 - [Version 3.40.0](releaselog/3_40_0.md)
> Version 3.40.0 is a new feature release of SQLite. See the [change log](releaselog/3_40_0.md) for details. Key enhancements in this release include:
>
> 1. Official support for compiling [SQLite to WASM](https://sqlite.org/wasm/doc/trunk/index.md) and running it in a web browser.
>
> 2. New and improved [recovery extension](recovery.md) for extracting data from corrupted database files.
>
> This release also includes performance enhancements and improvements to the query planner.
>
> A psychological milestone: The performance benchmark that the SQLite developers have used for many years has for the first time dropped below 1 billion CPU cycles (measured using cachegrind) when run in [WAL mode](wal.md). This is less than half the number of CPU cycles used as recently as 8 years ago. (The graph below shows SQLite using a [rollback journal](lockingv3.md#rollback) which uses fewer CPU cycles at the expense of extra I/O. The benchmark passed through the 1 billion cycle barrier for rollback journals for the previous release.)
>
> 
------------------------------------------------------------------------
### 2022-09-29 - [Version 3.39.4](releaselog/3_39_4.md)
> Version 3.39.4 is a security release that addresses a single long-standing problem in the [FTS3 extension](fts3.md). An attacker who is able to execute arbitrary SQL statements and who can create a corrupt database that is 2GB or larger in size might be able to trick FTS3 into overflowing an integer used to size a memory allocation, causing the allocation to be too small and ultimately resulting in a buffer overrun. The release also includes fixes for other obscure weaknesses, as described in the release notes.
------------------------------------------------------------------------
### 2022-09-05 - [Version 3.39.3](releaselog/3_39_3.md)
> Version 3.39.3 is a patch release that fixes a few obscure problems in the 3.39.0 release. See the release notes for details.
------------------------------------------------------------------------
### 2022-07-21 - [Version 3.39.2](releaselog/3_39_2.md)
> Version 3.39.2 is a security release that addresses multiple long-standing issues in SQLite. The most severe problem is identified by CVE-2022-35737. That issue is associated with the auxiliary C-language APIs of SQLite and cannot be reached using SQL or database inputs, and hence is unlikely to affect your application. Nevertheless, upgrading is recommended. The other issues are comparatively minor. This release also fixes a performance regression that appeared in version 3.39.0 that might affect some multi-way joins that use LEFT JOIN.
------------------------------------------------------------------------
### 2022-07-13 - [Version 3.39.1](releaselog/3_39_1.md)
> Version 3.39.1 is a patch release that fixes a few minor problems in version 3.39.0. Upgrading is optional.
------------------------------------------------------------------------
### 2022-06-25 - [Version 3.39.0](releaselog/3_39_0.md)
> Version 3.39.0 is a regular maintenance release of SQLite. The key enhancement in this release is added support for RIGHT and FULL JOIN. There are other language and performance enhancements as well — see the [release notes](releaselog/3_39_0.md) for details.
------------------------------------------------------------------------
### 2022-05-06 - [Version 3.38.5](releaselog/3_38_5.md)
> The 3.38.4 patch release included a minor change to the [CLI](cli.md) source code that did not work. The release manager only ran a subset of the normal release tests, and hence did not catch the problem. As a result, the CLI will segfault when using columnar output modes in version 3.38.4. This blunder did not affect the core SQLite library. It only affected the CLI.
>
> Take-away lesson: **Always** run **all** of your tests prior to a release - even a trival patch release. **Always**.
>
> The 3.38.5 patch release fixes the 3.38.4 blunder.
------------------------------------------------------------------------
### 2022-05-04 - [Version 3.38.4](releaselog/3_38_4.md)
> Another user-discovered problem in the new Bloom filter optimization is fixed in this patch release. Without the fix, it is possible for a multi-way join that uses Bloom filters for two or more tables in the join to enter an infinite loop if the key constraint on one of those tables contains a NULL value.
------------------------------------------------------------------------
### 2022-04-27 - [Version 3.38.3](releaselog/3_38_3.md)
> Version 3.38.3 fixes a bug in the automatic-index and Bloom filter construction logic that might cause SQLite to be overly aggressive in the use of ON clause constraints, resulting in an incorrect automatic-index or Bloom filter that excludes some valid rows from output. The bug was introduced in version 3.38.0. Other minor changes were tossed in to complete the patch.
------------------------------------------------------------------------
### 2022-03-26 - [Version 3.38.2](releaselog/3_38_2.md)
> Version 3.38.2 fixes another bug in the new Bloom filter optimization that might cause incorrect answers for a LEFT JOIN that has an IS NULL constraint on the right-hand table.
------------------------------------------------------------------------
### 2022-03-12 - [Version 3.38.1](releaselog/3_38_1.md)
> Version 3.38.1 fixes a pair of bugs in the Bloom filter optimization that was introduced in version 3.38.0. These bugs might cause incorrect answers for some obscure queries. Various other minor problems and documentation typos were fixed at the same time.
------------------------------------------------------------------------
### 2022-02-22 - [Version 3.38.0](releaselog/3_38_0.md)
> Version 3.38.0 is a routine maintenance release of SQLite. There are various minor enhancements and about a 0.5% reduction in the number of CPU cycles used. See the [release notes](releaselog/3_38_0.md) for more detail.
------------------------------------------------------------------------
### 2022-01-06 - [Version 3.37.2](releaselog/3_37_2.md)
> Version 3.37.2 fixes a [database corruption bug](howtocorrupt.md#svptbug). You are encouraged to upgrade, especially if you are using [SAVEPOINT](lang_savepoint.md).
>
> The problem first appeared in version 3.35.0 (2021-03-12) and affects all subsequent releases through 3.37.1. If temporary files are stored in memory (which is not the default behavior, but is sometimes selected by applications using either [-DSQLITE_TEMP_STORE](compile.md#temp_store) or [PRAGMA temp_store](pragma.md#pragma_temp_store)) and if a [SAVEPOINT](lang_savepoint.md) is rolled back and then subsequent changes within the same transaction are committed, the database file might (with low but non-zero probability) go corrupt.
------------------------------------------------------------------------
### 2021-12-30 - [Version 3.37.1](releaselog/3_37_1.md)
> Version 3.37.1 fixes a bug in the [UPSERT](lang_upsert.md) logic, introduced by the UPSERT enhancements of [version 3.35.0](releaselog/3_35_0.md), that can cause incorrect byte-code to be generated in some cases, resulting in an infinite loop in the byte code, or a NULL-pointer dereference. This patch release also fixes some other minor problems with assert() statements and in the [CLI](cli.md).
------------------------------------------------------------------------
### 2021-11-27 - [Version 3.37.0](releaselog/3_37_0.md)
> Version 3.37.0 is a routine maintenance release of SQLite. The biggest new feature in this release is support for [STRICT tables](stricttables.md). Other enhancements are described in the [release notes](releaselog/3_37_0.md).
------------------------------------------------------------------------
### 2021-06-18 - [Version 3.36.0](releaselog/3_36_0.md)
> Version 3.36.0 is a routine maintenance release of SQLite. There are no new major features, only incremental improvements to existing features and small performance improvements.
------------------------------------------------------------------------
### 2021-04-19 - Patch release 3.35.5
> The new ALTER TABLE DROP COLUMN capability that was added in the 3.35.0 release contained a bug that might cause the table content to go corrupt when the table was rewritten to remove the dropped column. Fixed by this patch.
------------------------------------------------------------------------
### 2021-04-02 - Patch release 3.35.4
> Version 3.35.4 is yet another patch release to fix obscure problems in features associated with the 3.35.0 release.
------------------------------------------------------------------------
### 2021-03-26 - Patch release 3.35.3
> Version 3.35.3 contains patches for a handful of minor problems discovered in prior releases.
------------------------------------------------------------------------
### 2021-03-17 - Patch release 3.35.2
> Version 3.35.2 is a small patch release to fix some minor problems that were discovered shortly after the 3.35.1 release.
------------------------------------------------------------------------
### 2021-03-15 - Patch release 3.35.1
> A user discovered an issue with the new DROP COLUMN capability in version 3.35.0, and so version 3.35.1 was created to fix it. No need to upgrade if you are not using DROP COLUMN.
------------------------------------------------------------------------
### 2021-03-12 - Release 3.35.0
> SQLite version 3.35.0 is a routine maintenance release. This release adds a number of new language features, including support for ALTER TABLE DROP COLUMN, built-in math functions, generalized UPSERT, and the MATERIALIZED hint on common table expressions. There are also query planner optimizations and incremental CLI improvements.
------------------------------------------------------------------------
### 2020-01-20 - Release 3.34.1
> SQLite version 3.34.1 is a patch release that fixes a possible use-after-free bug that can be provoked by malicious SQL. Other minor issues in extensions and documentation are also fixed.
------------------------------------------------------------------------
### 2020-12-01 - Release 3.34.0
> SQLite version 3.34.0 is a routine maintenance release. This release adds incremental improvements to performance and features, including enhancements to the query planner, multiple recursive SELECTS in recursive common table expressions, and better error messages from CHECK constraint failures. See the change log for details.
------------------------------------------------------------------------
### 2020-08-14 - Release 3.33.0
> SQLite version 3.33.0 is a routine maintenance release. This release features added support for "UPDATE FROM" following the PostgreSQL syntax, and a doubling of the maximum database size to 281 TB, as well as many other improvements. See the change log for details.
------------------------------------------------------------------------
### 2020-06-18 - Release 3.32.3
> The 3.32.3 release is a patch release that contains fixes for various issues discovered by fuzzers. None of the issues fixed are likely to be encountered by applications that use SQLite in ordinary ways, though upgrading never hurts.
>
> Map of all changes since the 3.32.0 release: 
\
Celebrating the SQLite "π release" with a home-baked pie.
2. Added support for [WITHOUT ROWID virtual tables](vtab.md#worid).
3. Improved the query planner so that the [OR optimization](optoverview.md#or_opt) can be used on [virtual tables](vtab.md) even if one or more of the disjuncts use the [LIKE](lang_expr.md#like), [GLOB](lang_expr.md#glob), [REGEXP](lang_expr.md#regexp), [MATCH](lang_expr.md#match) operators.
4. Added the [CSV virtual table](csv.md) for reading [RFC 4180](https://www.ietf.org/rfc/rfc4180.txt) formatted comma-separated value files.
5. Added the [carray() table-valued function](carray.md) extension.
6. Enabled [persistent loadable extensions](loadext.md#persist) using the new [SQLITE_OK_LOAD_PERMANENTLY](rescode.md#ok_load_permanently) return code from the extension entry point.
7. Added the [SQLITE_DBSTATUS_CACHE_USED_SHARED](c3ref/c_dbstatus_options.md#sqlitedbstatuscacheusedshared) option to [sqlite3_db_status()](c3ref/db_status.md).
8. Add the [vfsstat.c](https://sqlite.org/src/artifact?ci=trunk&filename=ext/misc/vfsstat.c) loadable extension - a VFS shim that measures I/O together with an [eponymous virtual table](vtab.md#epovtab) that provides access to the measurements.
9. Improved algorithm for running queries with both an ORDER BY and a LIMIT where only the inner-most loop naturally generates rows in the correct order.
10. Enhancements to [Lemon parser generator](lemon.md), so that it generates a faster parser.
11. The [PRAGMA compile_options](pragma.md#pragma_compile_options) command now attempts to show the version number of the compiler that generated the library.
12. Enhance [PRAGMA table_info](pragma.md#pragma_table_info) so that it provides information about [eponymous virtual tables](vtab.md#epovtab).
13. Added the "win32-none" VFS, analogous to the "unix-none" VFS, that works like the default "win32" VFS except that it ignores all file locks.
14. The query planner uses a full scan of a [partial index](partialindex.md) instead of a full scan of the main table, in cases where that makes sense.
15. Allow [table-valued functions](vtab.md#tabfunc2) to appear on the right-hand side of an [IN operator](lang_expr.md#in_op).
16. Created the [dbhash.exe](dbhash.md) command-line utility.
17. Added two new C-language interfaces: [sqlite3_expanded_sql()](c3ref/expanded_sql.md) and [sqlite3_trace_v2()](c3ref/trace_v2.md). These new interfaces subsume the functions of [sqlite3_trace()](c3ref/profile.md) and [sqlite3_profile()](c3ref/profile.md) which are now deprecated.
18. Added the [json_quote()](json1.md#jquote) SQL function to [the json1 extension](json1.md).
19. Disable the [authorizer callback](c3ref/set_authorizer.md) while reparsing the schema.
20. Added the [SQLITE_ENABLE_UNKNOWN_SQL_FUNCTION](compile.md#enable_unknown_sql_function) compile-time option and turned that option on by default when building the [command-line shell](cli.md).
**Bug Fixes:**
21. Fix the [ALTER TABLE](lang_altertable.md) command so that it does not corrupt [descending indexes](lang_createindex.md#descidx) when adding a column to a [legacy file format](pragma.md#pragma_legacy_file_format) database. Ticket [f68bf68513a1c15f](https://sqlite.org/src/info/f68bf68513a1c15f)
22. Fix a NULL-pointer dereference/crash that could occurs when a transitive WHERE clause references a non-existent collating sequence. Ticket [e8d439c77685eca6](https://sqlite.org/src/info/e8d439c77685eca6).
23. Improved the cost estimation for an index scan which includes a WHERE clause that can be partially or fully evaluated using columns in the index and without having to do a table lookup. This fixes a performance regression that occurred for some obscure queries following the ORDER BY LIMIT optimization introduced in [version 3.12.0](#version_3_12_0).
**Hashes:**
24. SQLITE_SOURCE_ID: "2016-08-08 13:40:27 d5e98057028abcf7217d0d2b2e29bbbcdf09d6de"
25. SHA1 for sqlite3.c: 234a3275d03a287434ace3ccdf1afb208e6b0e92
### 2016-05-18 (3.13.0)
1. Postpone I/O associated with TEMP files for as long as possible, with the hope that the I/O can ultimately be avoided completely.
2. Merged the [session](sessionintro.md) extension into trunk.
3. Added the ".auth ON\|OFF" command to the [command-line shell](cli.md).
4. Added the "--indent" option to the ".schema" and ".fullschema" commands of the [command-line shell](cli.md), to turn on pretty-printing.
5. Added the ".eqp full" option to the [command-line shell](cli.md), that does both [EXPLAIN](lang_explain.md) and [EXPLAIN QUERY PLAN](eqp.md) on each statement that is evaluated.
6. Improved unicode filename handling in the [command-line shell](cli.md) on Windows.
7. Improved resistance against goofy query planner decisions caused by incomplete or incorrect modifications to the [sqlite_stat1](fileformat2.md#stat1tab) table by the application.
8. Added the [sqlite3_db_config](c3ref/db_config.md)(db,[SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenableloadextension)) interface which allows the [sqlite3_load_extension()](c3ref/load_extension.md) C-API to be enabled while keeping the [load_extension()](lang_corefunc.md#load_extension) SQL function disabled for security.
9. Change the [temporary directory search algorithm](tempfiles.md#tempdir) on Unix to allow directories with write and execute permission, but without read permission, to serve as temporary directories. Apply this same standard to the "." fallback directory.
**Bug Fixes:**
10. Fix a problem with the multi-row one-pass DELETE optimization that was causing it to compute incorrect answers with a self-referential subquery in the WHERE clause. Fix for ticket [dc6ebeda9396087](https://sqlite.org/src/info/dc6ebeda9396087)
11. Fix a possible segfault with DELETE when table is a [rowid table](rowidtable.md) with an [INTEGER PRIMARY KEY](lang_createtable.md#rowid) and the WHERE clause contains a OR and the table has one or more indexes that are able to trigger the OR optimization, but none of the indexes reference any table columns other than the INTEGER PRIMARY KEY. Ticket [16c9801ceba49](https://sqlite.org/src/info/16c9801ceba49).
12. When checking for the [WHERE-clause push-down optimization](optoverview.md#pushdown), verify that all terms of the compound inner SELECT are non-aggregate, not just the last term. Fix for ticket [f7f8c97e97597](https://sqlite.org/src/info/f7f8c97e97597).
13. Fix a locking race condition in Windows that can occur when two or more processes attempt to recover the same [hot journal](fileformat2.md#hotjrnl) at the same time.
**Hashes:**
14. SQLITE_SOURCE_ID: "2016-05-18 10:57:30 fc49f556e48970561d7ab6a2f24fdd7d9eb81ff2"
15. SHA1 for sqlite3.c: 9b9171b1e6ce7a980e6b714e9c0d9112657ad552
**Bug fixes backported into patch release 3.12.2 (2016-04-18):**
16. Fix a backwards compatibility problem in version 3.12.0 and 3.12.1: Columns declared as `"INTEGER" PRIMARY KEY` (with quotes around the datatype keyword) were not being recognized as an [INTEGER PRIMARY KEY](lang_createtable.md#rowid), which resulted in an incompatible database file. Ticket [7d7525cb01b68](https://sqlite.org/src/info/7d7525cb01b68)
17. Fix a bug (present since [version 3.9.0](#version_3_9_0)) that can cause the [DELETE](lang_delete.md) operation to miss rows if [PRAGMA reverse_unordered_selects](pragma.md#pragma_reverse_unordered_selects) is turned on. Ticket [a306e56ff68b8fa5](https://sqlite.org/src/info/a306e56ff68b8fa5)
18. Fix a bug in the code generator that can cause incorrect results if two or more [virtual tables](vtab.md) are joined and the virtual table used in outer loop of the join has an [IN operator](lang_expr.md#in_op) constraint.
19. Correctly interpret negative "PRAGMA cache_size" values when determining the cache size used for sorting large amounts of data.
**Bug fixes backported into patch release 3.12.1 (2016-04-08):**
20. Fix a boundary condition error introduced by version 3.12.0 that can result in a crash during heavy [SAVEPOINT](lang_savepoint.md) usage. Ticket [7f7f8026eda38](https://sqlite.org/src/info/7f7f8026eda38).
21. Fix [views](lang_createview.md) so that they inherit column datatypes from the table that they are defined against, when possible.
22. Fix the query planner so that IS and IS NULL operators are able to drive an index on a LEFT OUTER JOIN.
### 2016-04-18 (3.12.2)
1. Fix a backwards compatibility problem in version 3.12.0 and 3.12.1: Columns declared as `"INTEGER" PRIMARY KEY` (with quotes around the datatype keyword) were not being recognized as an [INTEGER PRIMARY KEY](lang_createtable.md#rowid), which resulted in an incompatible database file. Ticket [7d7525cb01b68](https://sqlite.org/src/info/7d7525cb01b68)
2. Fix a bug (present since [version 3.9.0](#version_3_9_0)) that can cause the [DELETE](lang_delete.md) operation to miss rows if [PRAGMA reverse_unordered_selects](pragma.md#pragma_reverse_unordered_selects) is turned on. Ticket [a306e56ff68b8fa5](https://sqlite.org/src/info/a306e56ff68b8fa5)
3. Fix a bug in the code generator that can cause incorrect results if two or more [virtual tables](vtab.md) are joined and the virtual table used in outer loop of the join has an [IN operator](lang_expr.md#in_op) constraint.
4. Correctly interpret negative "PRAGMA cache_size" values when determining the cache size used for sorting large amounts of data.
**Hashes:**
5. SQLITE_SOURCE_ID: "2016-04-18 17:30:31 92dc59fd5ad66f646666042eb04195e3a61a9e8e"
6. SHA1 for sqlite3.c: de5a5898ebd3a3477d4652db143746d008b24c83
### 2016-04-08 (3.12.1)
1. Fix a boundary condition error introduced by version 3.12.0 that can result in a crash during heavy [SAVEPOINT](lang_savepoint.md) usage. Ticket [7f7f8026eda38](https://sqlite.org/src/info/7f7f8026eda38).
2. Fix [views](lang_createview.md) so that they inherit column datatypes from the table that they are defined against, when possible.
3. Fix the query planner so that IS and IS NULL operators are able to drive an index on a LEFT OUTER JOIN.
**Hashes:**
4. SQLITE_SOURCE_ID: "2016-04-08 15:09:49 fe7d3b75fe1bde41511b323925af8ae1b910bc4d"
5. SHA1 for sqlite3.c: ebb18593350779850e3e1a930eb84a70fca8c1d1
### 2016-04-01 (3.9.3)
1. Backport a [simple query planner optimization](https://sqlite.org/src/info/c648539b52ca28c0) that allows the IS operator to drive an index on a LEFT OUTER JOIN. No other changes from the [version 3.9.2](#version_3_9_2) baseline.
### 2016-03-29 (3.12.0)
1. **Potentially Disruptive Change:**
2. The [SQLITE_DEFAULT_PAGE_SIZE](compile.md#default_page_size) is increased from 1024 to 4096. The [SQLITE_DEFAULT_CACHE_SIZE](compile.md#default_cache_size) is changed from 2000 to -2000 so the same amount of cache memory is used by default. See the application note on the [version 3.12.0 page size change](pgszchng2016.md) for further information.
**Performance enhancements:**
3. Enhancements to the [Lemon parser generator](lemon.md) so that it creates a smaller and faster SQL parser.
4. Only create [master journal](tempfiles.md#superjrnl) files if two or more attached databases are all modified, do not have [PRAGMA synchronous](pragma.md#pragma_synchronous) set to OFF, and do not have the [journal_mode](pragma.md#pragma_journal_mode) set to OFF, MEMORY, or WAL.
5. Only create [statement journal](tempfiles.md#stmtjrnl) files when their size exceeds a threshold. Otherwise the journal is held in memory and no I/O occurs. The threshold can be configured at compile-time using [SQLITE_STMTJRNL_SPILL](compile.md#stmtjrnl_spill) or at start-time using [sqlite3_config](c3ref/config.md)([SQLITE_CONFIG_STMTJRNL_SPILL](c3ref/c_config_covering_index_scan.md#sqliteconfigstmtjrnlspill)).
6. The query planner is able to optimize IN operators on [virtual tables](vtab.md) even if the [xBestIndex](vtab.md#xbestindex) method does not set the sqlite3_index_constraint_usage.omit flag of the virtual table column to the left of the IN operator.
7. The query planner now does a better job of optimizing [virtual table](vtab.md) accesses in a 3-way or higher join where constraints on the virtual table are split across two or more other tables of the join.
8. More efficient handling of [application-defined SQL functions](appfunc.md), especially in cases where the application defines hundreds or thousands of custom functions.
9. The query planner considers the LIMIT clause when estimating the cost of ORDER BY.
10. The configure script (on unix) automatically detects pread() and pwrite() and sets compile-time options to use those OS interfaces if they are available.
11. Reduce the amount of memory needed to hold the schema.
12. Other miscellaneous micro-optimizations for improved performance and reduced memory usage.
**New Features:**
13. Added the [SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER](c3ref/c_dbconfig_defensive.md#sqlitedbconfigenablefts3tokenizer) option to [sqlite3_db_config()](c3ref/db_config.md) which allows the two-argument version of the [fts3_tokenizer()](fts3.md#f3tknzr) SQL function to be enabled or disabled at run-time.
14. Added the [sqlite3rbu_bp_progress()](https://sqlite.org/src/artifact/d7cc99350?ln=403-443) interface to the [RBU](rbu.md) extension.
15. The [PRAGMA defer_foreign_keys=ON](pragma.md#pragma_defer_foreign_keys) statement now also disables [RESTRICT actions](foreignkeys.md#fk_actions) on foreign key.
16. Added the [sqlite3_system_errno()](c3ref/system_errno.md) interface.
17. Added the [SQLITE_DEFAULT_SYNCHRONOUS](compile.md#default_synchronous) and [SQLITE_DEFAULT_WAL_SYNCHRONOUS](compile.md#default_wal_synchronous) compile-time options. The [SQLITE_DEFAULT_SYNCHRONOUS](compile.md#default_synchronous) compile-time option replaces the [SQLITE_EXTRA_DURABLE](compile.md#extra_durable) option, which is no longer supported.
18. Enhanced the ".stats" command in the [command-line shell](cli.md) to show more information about I/O performance obtained from /proc, when available.
**Bug fixes:**
19. Make sure the [sqlite3_set_auxdata()](c3ref/get_auxdata.md) values from multiple triggers within a single statement do not interfere with one another. Ticket [dc9b1c91](https://sqlite.org/src/info/dc9b1c91).
20. Fix the code generator for expressions of the form "x IN (SELECT...)" where the SELECT statement on the RHS is a correlated subquery. Ticket [5e3c886796e5512e](https://sqlite.org/src/info/5e3c886796e5512e).
21. Fix a harmless TSAN warning associated with the [sqlite3_db_readonly()](c3ref/db_readonly.md) interface.
**Hashes:**
22. SQLITE_SOURCE_ID: "2016-03-29 10:14:15 e9bb4cf40f4971974a74468ef922bdee481c988b"
23. SHA1 for sqlite3.c: cba2be96d27cb51978cd4a200397a4ad178986eb
### 2016-03-03 (3.11.1)
1. Improvements to the Makefiles and build scripts used by VisualStudio.
2. Fix an [FTS5](fts5.md) issue in which the 'optimize' command could cause index corruption.
3. Fix a buffer overread that might occur if [FTS5](fts5.md) is used to query a corrupt database file.
4. Increase the maximum "scope" value for the [spellfix1](spellfix1.md) extension from 6 to 30.
5. SQLITE_SOURCE_ID: "2016-03-03 16:17:53 f047920ce16971e573bc6ec9a48b118c9de2b3a7"
6. SHA1 for sqlite3.c: 3da832fd2af36eaedb05d61a8f4c2bb9f3d54265
### 2016-02-15 (3.11.0)
1. **General improvements:**
2. Enhanced [WAL mode](wal.md) so that it works efficiently with transactions that are larger than the [cache_size](pragma.md#pragma_cache_size).
3. Added the [FTS5 detail option](fts5.md#the_detail_option).
4. Added the "EXTRA" option to [PRAGMA synchronous](pragma.md#pragma_synchronous) that does a sync of the containing directory when a rollback journal is unlinked in DELETE mode, for better durability. The [SQLITE_EXTRA_DURABLE](compile.md#extra_durable) compile-time option enables [PRAGMA synchronous=EXTRA](pragma.md#pragma_synchronous) by default.
5. Enhanced the [query planner](optoverview.md) so that it is able to use a [covering index](queryplanner.md#covidx) as part of the [OR optimization](optoverview.md#or_opt).
6. Avoid recomputing [NOT NULL](lang_createtable.md#notnullconst) and [CHECK constraints](lang_createtable.md#ckconst) on unchanged columns in [UPDATE](lang_update.md) statement.
7. Many micro-optimizations, resulting in a library that is faster than the previous release.
**Enhancements to the [command-line shell](cli.md):**
8. By default, the shell is now in "auto-explain" mode. The output of [EXPLAIN](lang_explain.md) commands is automatically formatted.
9. Added the ".vfslist" [dot-command](cli.md#dotcmd).
10. The [SQLITE_ENABLE_EXPLAIN_COMMENTS](compile.md#enable_explain_comments) compile-time option is now turned on by default in the standard builds.
**Enhancements to the [TCL Interface](tclsqlite.md):**
11. If a database connection is opened with the "-uri 1" option, then [URI filenames](uri.md) are honored by the "backup" and "restore" commands.
12. Added the "-sourceid" option to the "sqlite3" command.
**Makefile improvements:**
13. Improved pthreads detection in configure scripts.
14. Add the ability to do MSVC Windows builds from the [amalgamation tarball](download.md).
**Bug fixes**
15. Fix an issue with incorrect sharing of VDBE temporary registers between co-routines that could cause incorrect query results in obscure cases. Ticket [d06a25c84454a](https://sqlite.org/src/info/d06a25c84454a).
16. Fix a problem in the [sqlite3_result_subtype()](c3ref/result_subtype.md) interface that could cause problems for the [json1](json1.md) extension under obscure circumstances. Fix for ticket [f45ac567eaa9f9](https://sqlite.org/src/info/f45ac567eaa9f9).
17. Escape control characters in JSON strings. Fix for ticket [ad2559db380abf8](https://sqlite.org/src/info/ad2559db380abf8).
18. Reenable the xCurrentTime and xGetLastError methods in the built-in unix [VFSes](vfs.md) as long as [SQLITE_OMIT_DEPRECATED](compile.md#omit_deprecated) is not defined.
**Backwards Compatibility:**
19. Because of continuing security concerns, the two-argument version of the seldom-used and little-known [fts3_tokenizer()](fts3.md#f3tknzr) function is disabled unless SQLite is compiled with the [SQLITE_ENABLE_FTS3_TOKENIZER](compile.md#enable_fts3_tokenizer).
**Hashes:**
20. SQLITE_SOURCE_ID: "2016-02-15 17:29:24 3d862f207e3adc00f78066799ac5a8c282430a5f"
21. SHA1 for sqlite3.c: df01436c5fcfe72d1a95bc172158219796e1a90b
### 2016-01-20 (3.10.2)
1. **Critical bug fix:**
2. Version 3.10.0 introduced a case-folding bug in the [LIKE](lang_expr.md#like) operator which is fixed by this patch release. Ticket [80369eddd5c94](https://sqlite.org/src/info/80369eddd5c94).
**Other miscellaneous bug fixes:**
3. Fix a use-after-free that can occur when SQLite is compiled with -DSQLITE_HAS_CODEC.
4. Fix the build so that it works with -DSQLITE_OMIT_WAL.
5. Fix the configure script for the amalgamation so that the --readline option works again on Raspberry PIs.
**Hashes:**
6. SQLITE_SOURCE_ID: "2016-01-20 15:27:19 17efb4209f97fb4971656086b138599a91a75ff9"
7. SHA1 for sqlite3.c: f7088b19d97cd7a1c805ee95c696abd54f01de4f
### 2016-01-14 (3.10.1)
1. **New feature:**
2. Add the [SQLITE_FCNTL_JOURNAL_POINTER](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntljournalpointer) file control.
**Bug fix:**
3. Fix a 16-month-old bug in the query planner that could generate incorrect results when a scalar subquery attempts to use the [block sorting](queryplanner.md#partialsort) optimization. Ticket [cb3aa0641d9a4](https://sqlite.org/src/info/cb3aa0641d9a4).
**Hashes:**
4. SQLITE_SOURCE_ID: "2016-01-13 21:41:56 254419c36766225ca542ae873ed38255e3fb8588"
5. SHA1 for sqlite3.c: 1398ba8e4043550a533cdd0834bfdad1c9eab0f4
### 2016-01-06 (3.10.0)
1. **General improvements:**
2. Added support for [LIKE](lang_expr.md#like), [GLOB](lang_expr.md#glob), and [REGEXP](lang_expr.md#regexp) operators on [virtual tables](vtab.md).
3. Added the [colUsed field](vtab.md#colUsed) to [sqlite3_index_info](c3ref/index_info.md) for use by the [sqlite3_module.xBestIndex](vtab.md#xbestindex) method.
4. Enhance the [PRAGMA cache_spill](pragma.md#pragma_cache_spill) statement to accept a 32-bit integer parameter which is the threshold below which cache spilling is prohibited.
5. On unix, if a symlink to a database file is opened, then the corresponding journal files are based on the actual filename, not the symlink name.
6. Added the "--transaction" option to [sqldiff](sqldiff.md).
7. Added the [sqlite3_db_cacheflush()](c3ref/db_cacheflush.md) interface.
8. Added the [sqlite3_strlike()](c3ref/strlike.md) interface.
9. When using [memory-mapped I/O](mmap.md) map the database file read-only so that stray pointers and/or array overruns in the application cannot accidentally modify the database file.
10. Added the *experimental* [sqlite3_snapshot_get()](c3ref/snapshot_get.md), [sqlite3_snapshot_open()](c3ref/snapshot_open.md), and [sqlite3_snapshot_free()](c3ref/snapshot_free.md) interfaces. These are subject to change or removal in a subsequent release.
11. Enhance the ['utc' modifier](lang_datefunc.md#localtime) in the [date and time functions](lang_datefunc.md) so that it is a no-op if the date/time is known to already be in UTC. (This is not a compatibility break since the behavior has long been documented as "undefined" in that case.)
12. Added the [json_group_array()](json1.md#jgrouparray) and [json_group_object()](json1.md#jgroupobject) SQL functions in the [json](json1.md#jmini) extension.
13. Added the [SQLITE_LIKE_DOESNT_MATCH_BLOBS](compile.md#like_doesnt_match_blobs) compile-time option.
14. Many small performance optimizations.
**Portability enhancements:**
15. Work around a sign-extension bug in the optimizer of the HP C compiler on HP/UX. [(details)](https://sqlite.org/src/fdiff?sbs=1&v1=869c95b0fc73026d&v2=232c242a0ccb3d67)
**Enhancements to the [command-line shell](cli.md):**
16. Added the ".changes ON\|OFF" and ".vfsinfo" [dot-commands](cli.md#dotcmd).
17. Translate between MBCS and UTF8 when running in [cmd.exe](https://en.wikipedia.org/wiki/Cmd.exe) on Windows.
**Enhancements to makefiles:**
18. Added the --enable-editline and --enable-static-shell options to the various autoconf-generated configure scripts.
19. Omit all use of "awk" in the makefiles, to make building easier for MSVC users.
**Important fixes:**
20. Fix inconsistent integer to floating-point comparison operations that could result in a corrupt index if the index is created on a table column that contains both large integers and floating point values of similar magnitude. Ticket [38a97a87a6](https://sqlite.org/src/tktview?name=38a97a87a6).
21. Fix an infinite-loop in the query planner that could occur on malformed [common table expressions](lang_with.md).
22. Various bug fixes in the [sqldiff](sqldiff.md) tool.
**Hashes:**
23. SQLITE_SOURCE_ID: "2016-01-06 11:01:07 fd0a50f0797d154fefff724624f00548b5320566"
24. SHA1 for sqlite3.c: b92ca988ebb6df02ac0c8f866dbf3256740408ac
### 2015-11-02 (3.9.2)
1. Fix the schema parser so that it interprets certain (obscure and ill-formed) CREATE TABLE statements the same as legacy. Fix for ticket [ac661962a2aeab3c331](https://sqlite.org/src/info/ac661962a2aeab3c331)
2. Fix a query planner problem that could result in an incorrect answer due to the use of [automatic indexing](optoverview.md#autoindex) in subqueries in the FROM clause of a correlated scalar subqueries. Fix for ticket [8a2adec1](https://sqlite.org/src/info/8a2adec1).
3. SQLITE_SOURCE_ID: "2015-11-02 18:31:45 bda77dda9697c463c3d0704014d51627fceee328"
4. SHA1 for sqlite3.c: 1c4013876f50bbaa3e6f0f98e0147c76287684c1
### 2015-10-16 (3.9.1)
1. Fix [the json1 extension](json1.md) so that it does not recognize ASCII form-feed as a whitespace character, in order to comply with RFC-7159. Fix for ticket [57eec374ae1d0a1d](https://sqlite.org/src/info/57eec374ae1d0a1d)
2. Add a few \#ifdef and build script changes to address compilation issues that appeared after the 3.9.0 release.
3. SQLITE_SOURCE_ID: ""2015-10-16 17:31:12 767c1727fec4ce11b83f25b3f1bfcfe68a2c8b02"
4. SHA1 for sqlite3.c: 5e6d1873a32d82c2cf8581f143649940cac8ae49
### 2015-10-14 (3.9.0)
1. **Policy Changes:**
2. The [version numbering conventions](versionnumbers.md) for SQLite are revised to use the emerging standard of [semantic versioning](http://semver.org/).
**New Features And Enhancements:**
3. Added [the json1 extension](json1.md) module in the source tree, and in the [amalgamation](amalgamation.md). Enable support using the [SQLITE_ENABLE_JSON1](compile.md#enable_json1) compile-time option.
4. Added [Full Text Search version 5 (FTS5)](fts5.md) to the [amalgamation](amalgamation.md), enabled using [SQLITE_ENABLE_FTS5](compile.md#enable_fts5). FTS5 will be considered "experimental" (subject to incompatible changes) for at least one more release cycle.
5. The [CREATE VIEW](lang_createview.md) statement now accepts an optional list of column names following the view name.
6. Added support for [indexes on expressions](expridx.md).
7. Added support for [table-valued functions](vtab.md#tabfunc2) in the FROM clause of a [SELECT](lang_select.md) statement.
8. Added support for [eponymous virtual tables](vtab.md#epovtab).
9. A [VIEW](lang_createview.md) may now reference undefined tables and functions when initially created. Missing tables and functions are reported when the VIEW is used in a query.
10. Added the [sqlite3_value_subtype()](c3ref/value_subtype.md) and [sqlite3_result_subtype()](c3ref/result_subtype.md) interfaced (used by [the json1 extension](json1.md)).
11. The query planner is now able to use [partial indexes](partialindex.md) that contain AND-connected terms in the WHERE clause.
12. The sqlite3_analyzer.exe utility is updated to report the depth of each btree and to show the average fanout for indexes and WITHOUT ROWID tables.
13. Enhanced the [dbstat virtual table](dbstat.md) so that it can be used as a [table-valued function](vtab.md#tabfunc2) where the argument is the schema to be analyzed.
**Other changes:**
14. The [sqlite3_memory_alarm()](c3ref/aggregate_count.md) interface, which has been deprecated and undocumented for 8 years, is changed into a no-op.
**Important fixes:**
15. Fixed a critical bug in the [SQLite Encryption Extension](https://sqlite.org/see/doc/trunk/www/readme.wiki) that could cause the database to become unreadable and unrecoverable if a [VACUUM](lang_vacuum.md) command changed the size of the encryption nonce.
16. Added a memory barrier in the implementation of [sqlite3_initialize()](c3ref/initialize.md) to help ensure that it is thread-safe.
17. Fix the [OR optimization](optoverview.md#or_opt) so that it always ignores subplans that do not use an index.
18. Do not apply the [WHERE-clause push-down optimization](optoverview.md#pushdown) on terms that originate in the ON or USING clause of a LEFT JOIN. Fix for ticket [c2a19d81652f40568c](https://sqlite.org/src/info/c2a19d81652f40568c).
19. SQLITE_SOURCE_ID: "2015-10-14 12:29:53 a721fc0d89495518fe5612e2e3bbc60befd2e90d"
20. SHA1 for sqlite3.c: c03e47e152ddb9c342b84ffb39448bf4a2bd4288
### 2015-07-29 (3.8.11.1)
1. Restore an undocumented side-effect of [PRAGMA cache_size](pragma.md#pragma_cache_size): force the database schema to be parsed if the database has not been previously accessed.
2. Fix a long-standing problem in [sqlite3_changes()](c3ref/changes.md) for [WITHOUT ROWID](withoutrowid.md) tables that was reported a few hours after the 3.8.11 release.
3. SQLITE_SOURCE_ID: "2015-07-29 20:00:57 cf538e2783e468bbc25e7cb2a9ee64d3e0e80b2f"
4. SHA1 for sqlite3.c: 3be71d99121fe5b17f057011025bcf84e7cc6c84
### 2015-07-27 (3.8.11)
1. Added the experimental [RBU](rbu.md) extension. Note that this extension is experimental and subject to change in incompatible ways.
2. Added the experimental [FTS5](fts5.md) extension. Note that this extension is experimental and subject to change in incompatible ways.
3. Added the [sqlite3_value_dup()](c3ref/value_dup.md) and [sqlite3_value_free()](c3ref/value_dup.md) interfaces.
4. Enhance the [spellfix1](spellfix1.md) extension to support [ON CONFLICT](lang_conflict.md) clauses.
5. The [IS operator](lang_expr.md#isisnot) is now able to drive indexes.
6. Enhance the query planner to permit [automatic indexing](optoverview.md#autoindex) on FROM-clause subqueries that are implemented by co-routine.
7. Disallow the use of "rowid" in [common table expressions](lang_with.md).
8. Added the [PRAGMA cell_size_check](pragma.md#pragma_cell_size_check) command for better and earlier detection of database file corruption.
9. Added the [matchinfo 'b' flag](fts3.md#matchinfo-b) to the [matchinfo()](fts3.md#matchinfo) function in [FTS3](fts3.md).
10. Improved fuzz-testing of database files, with fixes for problems found.
11. Add the fuzzcheck test program and automatically run this program using both SQL and database test cases on "make test".
12. Added the [SQLITE_MUTEX_STATIC_VFS1](c3ref/c_mutex_fast.md) static mutex and use it in the Windows [VFS](vfs.md).
13. The [sqlite3_profile()](c3ref/profile.md) callback is invoked (by [sqlite3_reset()](c3ref/reset.md) or [sqlite3_finalize()](c3ref/finalize.md)) for statements that did not run to completion.
14. Enhance the page cache so that it can preallocate a block of memory to use for the initial set page cache lines. Set the default preallocation to 100 pages. Yields about a 5% performance increase on common workloads.
15. Miscellaneous micro-optimizations result in 22.3% more work for the same number of CPU cycles relative to the previous release. SQLite now runs twice as fast as [version 3.8.0](#version_3_8_0) and three times as fast as [version 3.3.9](#version_3_3_9). (Measured using [cachegrind](http://valgrind.org/docs/manual/cg-manual.html) on the [speedtest1.c](https://sqlite.org/src/artifact/83f6b3318f7ee) workload on Ubuntu 14.04 x64 with gcc 4.8.2 and -Os. Your performance may vary.)
16. Added the [sqlite3_result_zeroblob64()](c3ref/result_blob.md) and [sqlite3_bind_zeroblob64()](c3ref/bind_blob.md) interfaces.
**Important bug fixes:**
17. Fix [CREATE TABLE AS](lang_createtable.md#createtabas) so that columns of type TEXT never end up holding an INT value. Ticket [f2ad7de056ab1dc9200](https://sqlite.org/src/info/f2ad7de056ab1dc9200)
18. Fix [CREATE TABLE AS](lang_createtable.md#createtabas) so that it does not leave NULL entries in the [sqlite_master table](schematab.md) if the SELECT statement on the right-hand side aborts with an error. Ticket [873cae2b6e25b](https://sqlite.org/src/info/873cae2b6e25b)
19. Fix the [skip-scan optimization](optoverview.md#skipscan) so that it works correctly when the [OR optimization](optoverview.md#or_opt) is used on [WITHOUT ROWID](withoutrowid.md) tables. Ticket [8fd39115d8f46](https://sqlite.org/src/info/8fd39115d8f46)
20. Fix the [sqlite3_memory_used()](c3ref/memory_highwater.md) and [sqlite3_memory_highwater()](c3ref/memory_highwater.md) interfaces so that they actually do provide a 64-bit answer.
**Hashes:**
21. SQLITE_SOURCE_ID: "2015-07-27 13:49:41 b8e92227a469de677a66da62e4361f099c0b79d0"
22. SHA1 for sqlite3.c: 719f6891abcd9c459b5460b191d731cd12a3643e
### 2015-05-20 (3.8.10.2)
1. Fix an index corruption issue introduced by [version 3.8.7](#version_3_8_7). An index with a TEXT key can be corrupted by an [INSERT](lang_insert.md) into the corresponding table if the table has two nested triggers that convert the key value to INTEGER and back to TEXT again. Ticket [34cd55d68e0](https://sqlite.org/src/info/34cd55d68e0e6e7c9a0711aab81a2ee3c354b4c0)
2. SQLITE_SOURCE_ID: "2015-05-20 18:17:19 2ef4f3a5b1d1d0c4338f8243d40a2452cc1f7fe4"
3. SHA1 for sqlite3.c: 638abb77965332c956dbbd2c8e4248e84da4eb63
### 2015-05-09 (3.8.10.1)
1. Make [sqlite3_compileoption_used()](c3ref/compileoption_get.md) responsive to the [SQLITE_ENABLE_DBSTAT_VTAB](compile.md#enable_dbstat_vtab) compile-time option.
2. Fix a harmless warning in the [command-line shell](cli.md) on some versions of MSVC.
3. Fix minor issues with the [dbstat virtual table](dbstat.md).
4. SQLITE_SOURCE_ID: "2015-05-09 12:14:55 05b4b1f2a937c06c90db70c09890038f6c98ec40"
5. SHA1 for sqlite3.c: 85e4e1c08c7df28ef61bb9759a0d466e0eefbaa2
### 2015-05-07 (3.8.10)
1. Added the [sqldiff.exe](sqldiff.md) utility program for computing the differences between two SQLite database files.
2. Added the [matchinfo y flag](fts3.md#matchinfo-y) to the [matchinfo()](fts3.md#matchinfo) function of [FTS3](fts3.md).
3. Performance improvements for [ORDER BY](lang_select.md#orderby), [VACUUM](lang_vacuum.md), [CREATE INDEX](lang_createindex.md), [PRAGMA integrity_check](pragma.md#pragma_integrity_check), and [PRAGMA quick_check](pragma.md#pragma_quick_check).
4. Fix many obscure problems discovered while [SQL fuzzing](testing.md#fuzztesting).
5. Identify all methods for important objects in the interface documentation. ([example](c3ref/context.md))
6. Made the [American Fuzzy Lop fuzzer](testing.md#aflfuzz) a standard part of SQLite's [testing strategy](testing.md).
7. Add the ".binary" and ".limits" commands to the [command-line shell](cli.md).
8. Make the [dbstat virtual table](dbstat.md) part of standard builds when compiled with the [SQLITE_ENABLE_DBSTAT_VTAB](compile.md#enable_dbstat_vtab) option.
9. SQLITE_SOURCE_ID: "2015-05-07 11:53:08 cf975957b9ae671f34bb65f049acf351e650d437"
10. SHA1 for sqlite3.c: 0b34f0de356a3f21b9dfc761f3b7821b6353c570
### 2015-04-08 (3.8.9)
1. Add VxWorks-7 as an officially supported and tested platform.
2. Added the [sqlite3_status64()](c3ref/status.md) interface.
3. Fix memory size tracking so that it works even if SQLite uses more than 2GiB of memory.
4. Added the [PRAGMA index_xinfo](pragma.md#pragma_index_xinfo) command.
5. Fix a potential 32-bit integer overflow problem in the [sqlite3_blob_read()](c3ref/blob_read.md) and [sqlite3_blob_write()](c3ref/blob_write.md) interfaces.
6. Ensure that prepared statements automatically reset on extended error codes of SQLITE_BUSY and SQLITE_LOCKED even when compiled using [SQLITE_OMIT_AUTORESET](compile.md#omit_autoreset).
7. Correct miscounts in the sqlite3_analyzer.exe utility related to WITHOUT ROWID tables.
8. Added the ".dbinfo" command to the [command-line shell](cli.md).
9. Improve the performance of fts3/4 queries that use the OR operator and at least one auxiliary fts function.
10. Fix a bug in the fts3 snippet() function causing it to omit leading separator characters from snippets that begin with the first token in a column.
11. SQLITE_SOURCE_ID: "2015-04-08 12:16:33 8a8ffc862e96f57aa698f93de10dee28e69f6e09"
12. SHA1 for sqlite3.c: 49f1c3ae347e1327b5aaa6c7f76126bdf09c6f42
### 2015-02-25 (3.8.8.3)
1. Fix a bug (ticket [2326c258d02ead33](https://sqlite.org/src/info/2326c258d02ead33)) that can lead to incorrect results if the qualifying constraint of a [partial index](partialindex.md) appears in the ON clause of a LEFT JOIN.
2. Added the ability to link against the "[linenoise](https://github.com/antirez/linenoise)" command-line editing library in unix builds of the [command-line shell](cli.md).
3. SQLITE_SOURCE_ID: "2015-02-25 13:29:11 9d6c1880fb75660bbabd693175579529785f8a6b"
4. SHA1 for sqlite3.c: 74ee38c8c6fd175ec85a47276dfcefe8a262827a
### 2015-01-30 (3.8.8.2)
1. Enhance [sqlite3_wal_checkpoint_v2(TRUNCATE)](c3ref/wal_checkpoint_v2.md) interface so that it truncates the WAL file even if there is no checkpoint work to be done.
2. SQLITE_SOURCE_ID: "2015-01-30 14:30:45 7757fc721220e136620a89c9d28247f28bbbc098"
3. SHA1 for sqlite3.c: 85ce79948116aa9a087ec345c9d2ce2c1d3cd8af
### 2015-01-20 (3.8.8.1)
1. Fix a bug in the sorting logic, present since version 3.8.4, that can cause output to appear in the wrong order on queries that contains an ORDER BY clause, a LIMIT clause, and that have approximately 60 or more columns in the result set. Ticket [f97c4637102a3ae72b79](https://sqlite.org/src/tktview?name=f97c4637102a3ae72b79).
2. SQLITE_SOURCE_ID: "2015-01-20 16:51:25 f73337e3e289915a76ca96e7a05a1a8d4e890d55"
3. SHA1 for sqlite3.c: 33987fb50dcc09f1429a653d6b47672f5a96f19e
### 2015-01-16 (3.8.8)
1. **New Features:**
2. Added the [PRAGMA data_version](pragma.md#pragma_data_version) command that can be used to determine if a database file has been modified by another process.
3. Added the [SQLITE_CHECKPOINT_TRUNCATE](c3ref/c_checkpoint_full.md) option to the [sqlite3_wal_checkpoint_v2()](c3ref/wal_checkpoint_v2.md) interface, with corresponding enhancements to [PRAGMA wal_checkpoint](pragma.md#pragma_wal_checkpoint).
4. Added the [sqlite3_stmt_scanstatus()](c3ref/stmt_scanstatus.md) interface, available only when compiled with [SQLITE_ENABLE_STMT_SCANSTATUS](compile.md#enable_stmt_scanstatus).
5. The [sqlite3_table_column_metadata()](c3ref/table_column_metadata.md) is enhanced to work correctly on [WITHOUT ROWID](withoutrowid.md) tables and to check for the existence of a a table if the column name parameter is NULL. The interface is now also included in the build by default, without requiring the [SQLITE_ENABLE_COLUMN_METADATA](compile.md#enable_column_metadata) compile-time option.
6. Added the [SQLITE_ENABLE_API_ARMOR](compile.md#enable_api_armor) compile-time option.
7. Added the [SQLITE_REVERSE_UNORDERED_SELECTS](compile.md#reverse_unordered_selects) compile-time option.
8. Added the [SQLITE_SORTER_PMASZ](compile.md#sorter_pmasz) compile-time option and [SQLITE_CONFIG_PMASZ](c3ref/c_config_covering_index_scan.md#sqliteconfigpmasz) start-time option.
9. Added the [SQLITE_CONFIG_PCACHE_HDRSZ](c3ref/c_config_covering_index_scan.md#sqliteconfigpcachehdrsz) option to [sqlite3_config()](c3ref/config.md) which makes it easier for applications to determine the appropriate amount of memory for use with [SQLITE_CONFIG_PAGECACHE](c3ref/c_config_covering_index_scan.md#sqliteconfigpagecache).
10. The number of rows in a [VALUES clause](lang_select.md#values) is no longer limited by [SQLITE_LIMIT_COMPOUND_SELECT](c3ref/c_limit_attached.md#sqlitelimitcompoundselect).
11. Added the [eval.c](https://sqlite.org/src/artifact/f971962e92ebb8b0) [loadable extension](loadext.md) that implements an eval() SQL function that will recursively evaluate SQL.
**Performance Enhancements:**
12. Reduce the number of memcpy() operations involved in balancing a b-tree, for 3.2% overall performance boost.
13. Improvements to cost estimates for the [skip-scan optimization](optoverview.md#skipscan).
14. The [automatic indexing](optoverview.md#autoindex) optimization is now capable of generating a [partial index](partialindex.md) if that is appropriate.
**Bug fixes:**
15. Ensure durability following a power loss with "PRAGMA journal_mode=TRUNCATE" by calling fsync() right after truncating the journal file.
16. The query planner now recognizes that any column in the right-hand table of a LEFT JOIN can be NULL, even if that column has a NOT NULL constraint. Avoid trying to optimize out NULL tests in those cases. Fix for ticket [6f2222d550f5b0ee7ed](https://sqlite.org/src/info/6f2222d550f5b0ee7ed).
17. Make sure ORDER BY puts rows in ascending order even if the DISTINCT operator is implemented using a descending index. Fix for ticket [c5ea805691bfc4204b1cb9e](https://sqlite.org/src/info/c5ea805691bfc4204b1cb9e).
18. Fix data races that might occur under stress when running with many threads in [shared cache mode](sharedcache.md) where some of the threads are opening and closing connections.
19. Fix obscure crash bugs found by [american fuzzy lop](http://lcamtuf.coredump.cx/afl/). Ticket [a59ae93ee990a55](https://sqlite.org/src/info/a59ae93ee990a55).
20. Work around a GCC optimizer bug (for gcc 4.2.1 on MacOS 10.7) that caused the [R-Tree extension](rtree.md) to compute incorrect results when compiled with -O3.
**Other changes:**
21. Disable the use of the strchrnul() C-library routine unless it is specifically enabled using the -DHAVE_STRCHRNULL compile-time option.
22. Improvements to the effectiveness and accuracy of the [likelihood()](lang_corefunc.md#likelihood), [likely()](lang_corefunc.md#likely), and [unlikely()](lang_corefunc.md#unlikely) SQL hint functions.
23. SQLITE_SOURCE_ID: "2015-01-16 12:08:06 7d68a42face3ab14ed88407d4331872f5b243fdf"
24. SHA1 for sqlite3.c: 91aea4cc722371d58aae3d22e94d2a4165276905
### 2014-12-09 (3.8.7.4)
1. Bug fix: Add in a mutex that was omitted from the previous release.
2. SQLITE_SOURCE_ID: "2014-12-09 01:34:36 f66f7a17b78ba617acde90fc810107f34f1a1f2e"
3. SHA1 for sqlite3.c: 0a56693a3c24aa3217098afab1b6fecccdedfd23
### 2014-12-05 (3.8.7.3)
1. Bug fix: Ensure the cached KeyInfo objects (an internal abstraction not visible to the application) do not go stale when operating in [shared cache mode](sharedcache.md) and frequently closing and reopening some database connections while leaving other database connections on the same shared cache open continuously. Ticket [e4a18565a36884b00edf](https://sqlite.org/src/info/e4a18565a36884b00edf).
2. Bug fix: Recognize that any column in the right-hand table of a LEFT JOIN can be NULL even if the column has a NOT NULL constraint. Do not apply optimizations that assume the column is never NULL. Ticket [6f2222d550f5b0ee7ed](https://sqlite.org/src/info/6f2222d550f5b0ee7ed).
3. SQLITE_SOURCE_ID: "2014-12-05 22:29:24 647e77e853e81a5effeb4c33477910400a67ba86"
4. SHA1 for sqlite3.c: 3ad2f5ba3a4a3e3e51a1dac9fda9224b359f0261
### 2014-11-18 (3.8.7.2)
1. Enhance the [ROLLBACK](lang_transaction.md) command so that pending queries are allowed to continue as long as the schema is unchanged. Formerly, a ROLLBACK would cause all pending queries to fail with an [SQLITE_ABORT](rescode.md#abort) or [SQLITE_ABORT_ROLLBACK](rescode.md#abort_rollback) error. That error is still returned if the ROLLBACK modifies the schema.
2. Bug fix: Make sure that NULL results from OP_Column are fully and completely NULL and do not have the MEM_Ephem bit set. Ticket [094d39a4c95ee4](https://sqlite.org/src/info/094d39a4c95ee4).
3. Bug fix: The %c format in sqlite3_mprintf() is able to handle precisions greater than 70.
4. Bug fix: Do not automatically remove the DISTINCT keyword from a SELECT that forms the right-hand side of an IN operator since it is necessary if the SELECT also contains a LIMIT. Ticket [db87229497](https://sqlite.org/src/info/db87229497).
5. SQLITE_SOURCE_ID: "2014-11-18 20:57:56 2ab564bf9655b7c7b97ab85cafc8a48329b27f93"
6. SHA1 for sqlite3.c: b2a68d5783f48dba6a8cb50d8bf69b238c5ec53a
### 2014-10-29 (3.8.7.1)
1. In [PRAGMA journal_mode=TRUNCATE](pragma.md#pragma_journal_mode) mode, call fsync() immediately after truncating the journal file to ensure that the transaction is durable across a power loss.
2. Fix an assertion fault that can occur when updating the NULL value of a field at the end of a table that was added using [ALTER TABLE ADD COLUMN](lang_altertable.md).
3. Do not attempt to use the strchrnul() function from the standard C library unless the HAVE_STRCHRNULL compile-time option is set.
4. Fix a couple of problems associated with running an UPDATE or DELETE on a [VIEW](lang_createview.md) with a [rowid](lang_createtable.md#rowid) in the WHERE clause.
5. SQLITE_SOURCE_ID: "2014-10-29 13:59:56 3b7b72c4685aa5cf5e675c2c47ebec10d9704221"
6. SHA1 for sqlite3.c: 2d25bd1a73dc40f538f3a81c28e6efa5999bdf0c
### 2014-10-17 (3.8.7)
1. **Performance Enhancements:**
2. Many micro-optimizations result in 20.3% more work for the same number of CPU cycles relative to the previous release. The cumulative performance increase since [version 3.8.0](#version_3_8_0) is 61%. (Measured using [cachegrind](http://valgrind.org/docs/manual/cg-manual.html) on the [speedtest1.c](https://sqlite.org/src/artifact/83f6b3318f7ee) workload on Ubuntu 13.10 x64 with gcc 4.8.1 and -Os. Your performance may vary.)
3. The sorter can use auxiliary helper threads to increase real-time response. This feature is off by default and may be enabled using the [PRAGMA threads](pragma.md#pragma_threads) command or the [SQLITE_DEFAULT_WORKER_THREADS](compile.md#default_worker_threads) compile-time option.
4. Enhance the [skip-scan](optoverview.md#skipscan) optimization so that it is able to skip index terms that occur in the middle of the index, not just as the left-hand side of the index.
5. Improved optimization of [CAST](lang_expr.md#castexpr) operators.
6. Various improvements in how the query planner uses [sqlite_stat4](fileformat2.md#stat4tab) information to estimate plan costs.
**New Features:**
7. Added new interfaces with 64-bit length parameters: [sqlite3_malloc64()](c3ref/free.md), [sqlite3_realloc64()](c3ref/free.md), [sqlite3_bind_blob64()](c3ref/bind_blob.md), [sqlite3_result_blob64()](c3ref/result_blob.md), [sqlite3_bind_text64()](c3ref/bind_blob.md), and [sqlite3_result_text64()](c3ref/result_blob.md).
8. Added the new interface [sqlite3_msize()](c3ref/free.md) that returns the size of a memory allocation obtained from [sqlite3_malloc64()](c3ref/free.md) and its variants.
9. Added the [SQLITE_LIMIT_WORKER_THREADS](c3ref/c_limit_attached.md#sqlitelimitworkerthreads) option to [sqlite3_limit()](c3ref/limit.md) and [PRAGMA threads](pragma.md#pragma_threads) command for configuring the number of available worker threads.
10. The [spellfix1](spellfix1.md) extension allows the application to optionally specify the rowid for each INSERT.
11. Added the [User Authentication](https://sqlite.org/src/doc/trunk/ext/userauth/user-auth.txt) extension.
**Bug Fixes:**
12. Fix a bug in the [partial index](partialindex.md) implementation that might result in an incorrect answer if a partial index is used in a subquery or in a [view](lang_createview.md). Ticket [98d973b8f5](https://sqlite.org/src/info/98d973b8f5).
13. Fix a query planner bug that might cause a table to be scanned in the wrong direction (thus reversing the order of output) when a DESC index is used to implement the ORDER BY clause on a query that has an identical GROUP BY clause. Ticket [ba7cbfaedc7e6](https://sqlite.org/src/info/ba7cbfaedc7e6).
14. Fix a bug in [sqlite3_trace()](c3ref/profile.md) that was causing it to sometimes fail to print an SQL statement if that statement needed to be re-prepared. Ticket [11d5aa455e0d98f3c1e6a08](https://sqlite.org/src/info/11d5aa455e0d98f3c1e6a08)
15. Fix a faulty assert() statement. Ticket [369d57fb8e5ccdff06f1](https://sqlite.org/src/info/369d57fb8e5ccdff06f1)
**Test, Debug, and Analysis Changes:**
16. Show ASCII-art abstract syntax tree diagrams using the ".selecttrace" and ".wheretrace" commands in the [command-line shell](cli.md) when compiled with [SQLITE_DEBUG](compile.md#debug), SQLITE_ENABLE_SELECTTRACE, and SQLITE_ENABLE_WHERETRACE. Also provide the sqlite3TreeViewExpr() and sqlite3TreeViewSelect() entry points that can be invoked from with the debugger to show the parse tree when stopped at a breakpoint.
17. Drop support for SQLITE_ENABLE_TREE_EXPLAIN. The SELECTTRACE mechanism provides more useful diagnostics information.
18. New options to the [command-line shell](cli.md) for configuring auxiliary memory usage: --pagecache, --lookaside, and --scratch.
19. SQLITE_SOURCE_ID: "2014-10-17 11:24:17 e4ab094f8afce0817f4074e823fabe59fc29ebb4"
20. SHA1 for sqlite3.c: 56dcf5e931a9e1fa12fc2d600cd91d3bf9b639cd
### 2014-08-15 (3.8.6)
1. Added support for [hexadecimal integer literals](lang_expr.md#hexint) in the SQL parser. (Ex: 0x123abc)
2. Enhanced the [PRAGMA integrity_check](pragma.md#pragma_integrity_check) command to detect [UNIQUE](lang_createtable.md#uniqueconst) and [NOT NULL](lang_createtable.md#notnullconst) constraint violations.
3. Increase the maximum value of [SQLITE_MAX_ATTACHED](limits.md#max_attached) from 62 to 125.
4. Increase the timeout in [WAL mode](wal.md) before issuing an [SQLITE_PROTOCOL](rescode.md#protocol) error from 1 second to 10 seconds.
5. Added the [likely(X)](lang_corefunc.md#likely) SQL function.
6. The [unicode61](fts3.md#unicode61) tokenizer is now included in [FTS4](fts3.md#fts4) by default.
7. Trigger automatic reprepares on all prepared statements when [ANALYZE](lang_analyze.md) is run.
8. Added a new [loadable extension](loadext.md) source code file to the source tree: [fileio.c](https://sqlite.org/src/finfo?name=ext/misc/fileio.c)
9. Add extension functions [readfile(X) and writefile(X,Y)](cli.md#fileio) (using code copy/pasted from fileio.c in the previous bullet) to the [command-line shell](cli.md).
10. Added the [.fullschema](cli.md#fullschema) dot-command to the [command-line shell](cli.md).
**Performance Enhancements:**
11. Deactivate the [DISTINCT](lang_select.md#distinct) keyword on subqueries on the right-hand side of the [IN operator](lang_expr.md#in_op).
12. Add the capability of evaluating an [IN operator](lang_expr.md#in_op) as a sequence of comparisons as an alternative to using a table lookup. Use the sequence of comparisons implementation in circumstances where it is likely to be faster, such as when the right-hand side of the IN operator is small and/or changes frequently.
13. The query planner now uses [sqlite_stat4](fileformat2.md#stat4tab) information (created by [ANALYZE](lang_analyze.md)) to help determine if the [skip-scan optimization](optoverview.md#skipscan) is appropriate.
14. Ensure that the query planner never tries to use a self-made transient index in place of a schema-defined index.
15. Other minor tweaks to improve the quality of [VDBE](opcode.md) code.
**Bug Fixes:**
16. Fix a bug in [CREATE UNIQUE INDEX](lang_createindex.md), introduced when [WITHOUT ROWID](withoutrowid.md) support added in version 3.8.2, that allows a non-unique NOT NULL column to be given a UNIQUE index. Ticket [9a6daf340df99ba93c](https://sqlite.org/src/info/9a6daf340df99ba93c)
17. Fix a bug in [R-Tree extension](rtree.md), introduced in the previous release, that can cause an incorrect results for queries that use the rowid of the R-Tree on the left-hand side of an [IN operator](lang_expr.md#in_op). Ticket [d2889096e7bdeac6](https://sqlite.org/src/info/d2889096e7bdeac6).
18. Fix the [sqlite3_stmt_busy()](c3ref/stmt_busy.md) interface so that it gives the correct answer for [ROLLBACK](lang_transaction.md) statements that have been stepped but never reset.
19. Fix a bug in that would cause a null pointer to be dereferenced if a column with a DEFAULT that is an aggregate function tried to usee its DEFAULT. Ticket [3a88d85f36704eebe1](https://sqlite.org/src/info/3a88d85f36704eebe1)
20. CSV output from the [command-line shell](cli.md) now always uses CRLF for the row separator and avoids inserting CR in front of NLs contained in data.
21. Fix a [column affinity](datatype3.md#affinity) problem with the [IN operator](lang_expr.md#in_op). Ticket [9a8b09f8e6](https://sqlite.org/src/info/9a8b09f8e6).
22. Fix the [ANALYZE](lang_analyze.md) command so that it adds correct samples for [WITHOUT ROWID](withoutrowid.md) tables in the [sqlite_stat4](fileformat2.md#stat4tab) table. Ticket [b2fa5424e6fcb15](https://sqlite.org/src/info/b2fa5424e6fcb15).
23. SQLITE_SOURCE_ID: "2014-08-15 11:46:33 9491ba7d738528f168657adb43a198238abde19e"
24. SHA1 for sqlite3.c: 72c64f05cd9babb9c0f9b3c82536d83be7804b1c
### 2014-06-04 (3.8.5)
1. Added support for [partial sorting by index](queryplanner.md#partialsort).
2. Enhance the query planner so that it always prefers an index that uses a superset of WHERE clause terms relative to some other index.
3. Improvements to the [automerge command](fts3.md#*fts4automergecmd) of [FTS4](fts3.md#fts4) to better control the index size for a full-text index that is subject to a large number of updates.
4. Added the [sqlite3_rtree_query_callback()](rtree.md#xquery) interface to [R-Tree extension](rtree.md)
5. Added new [URI query parameters](uri.md#coreqp) "nolock" and "immutable".
6. Use less memory by not remembering CHECK constraints on read-only database connections.
7. Enable the [OR optimization](queryplanner.md#or_in_where) for [WITHOUT ROWID](withoutrowid.md) tables.
8. Render expressions of the form "x IN (?)" (with a single value in the list on the right-hand side of the IN operator) as if they where "x==?", Similarly optimize "x NOT IN (?)"
9. Add the ".system" and ".once" commands to the [command-line shell](cli.md).
10. Added the [SQLITE_IOCAP_IMMUTABLE](c3ref/c_iocap_atomic.md) bit to the set of bits that can be returned by the xDeviceCharacteristics method of a [VFS](vfs.md).
11. Added the [SQLITE_TESTCTRL_BYTEORDER](c3ref/c_testctrl_always.md) test control.
**Bug Fixes:**
12. OFFSET clause ignored on queries without a FROM clause. Ticket [07d6a0453d](https://sqlite.org/src/info/07d6a0453d)
13. Assertion fault on queries involving expressions of the form "x IN (?)". Ticket [e39d032577](https://sqlite.org/src/info/e39d032577).
14. Incorrect column datatype reported. Ticket [a8a0d2996a](https://sqlite.org/src/info/a8a0d2996a)
15. Duplicate row returned on a query against a table with more than 16 indices, each on a separate column, and all used via OR-connected constraints. Ticket [10fb063b11](https://sqlite.org/src/info/10fb063b11)
16. Partial index causes assertion fault on UPDATE OR REPLACE. Ticket [2ea3e9fe63](https://sqlite.org/src/info/2ea3e9fe63)
17. Crash when calling undocumented SQL function sqlite_rename_parent() with NULL parameters. Ticket [264b970c43](https://sqlite.org/src/info/264b970c4379fd)
18. ORDER BY ignored if the query has an identical GROUP BY. Ticket [b75a9ca6b0](https://sqlite.org/src/info/b75a9ca6b0499)
19. The group_concat(x,'') SQL function returns NULL instead of an empty string when all inputs are empty strings. Ticket [55746f9e65](https://sqlite.org/src/info/55746f9e65f85)
20. Fix a bug in the VDBE code generator that caused crashes when doing an INSERT INTO ... SELECT statement where the number of columns being inserted is larger than the number of columns in the destination table. Ticket [e9654505cfd](https://sqlite.org/src/info/e9654505cfda9)
21. Fix a problem in CSV import in the [command-line shell](cli.md) where if the leftmost field of the first row in the CSV file was both zero bytes in size and unquoted no data would be imported.
22. Fix a problem in FTS4 where the left-most column that contained the [notindexed column](fts3.md#fts4notindexed) name as a prefix was not indexed rather than the column whose name matched exactly.
23. Fix the [sqlite3_db_readonly()](c3ref/db_readonly.md) interface so that it returns true if the database is read-only due to the file format write version number being too large.
24. SQLITE_SOURCE_ID: "2014-06-04 14:06:34 b1ed4f2a34ba66c29b130f8d13e9092758019212"
25. SHA1 for sqlite3.c: 7bc194957238c61b1a47f301270286be5bc5208c
### 2014-04-03 (3.8.4.3)
1. Add a [one-character fix](https://sqlite.org/src/fdiff?sbs=1&v1=7d539cedb1c&v2=ebad891b7494d&smhdr) for a problem that might cause incorrect query results on a query that mixes DISTINCT, GROUP BY in a subquery, and ORDER BY. [Ticket 98825a79ce14](https://sqlite.org/src/info/98825a79ce1456863).
2. SQLITE_SOURCE_ID: "2014-04-03 16:53:12 a611fa96c4a848614efe899130359c9f6fb889c3"
3. SHA1 for sqlite3.c: 310a1faeb9332a3cd8d1f53b4a2e055abf537bdc
### 2014-03-26 (3.8.4.2)
1. Fix a potential buffer overread that could result when trying to search a corrupt database file.
2. SQLITE_SOURCE_ID: "2014-03-26 18:51:19 02ea166372bdb2ef9d8dfbb05e78a97609673a8e"
3. SHA1 for sqlite3.c: 4685ca86c2ea0649ed9f59a500013e90b3fe6d03
### 2014-03-11 (3.8.4.1)
1. Work around a C-preprocessor macro conflict that breaks the build for some configurations with Microsoft Visual Studio.
2. When computing the cost of the [skip-scan optimization](optoverview.md#skipscan), take into account the fact that multiple seeks are required.
3. SQLITE_SOURCE_ID: "2014-03-11 15:27:36 018d317b1257ce68a92908b05c9c7cf1494050d0"
4. SHA1 for sqlite3.c: d5cd1535053a50aa8633725e3595740b33709ac5
### 2014-03-10 (3.8.4)
1. Code optimization and refactoring for improved performance.
2. Add the ".clone" and ".save" commands to the command-line shell.
3. Update the banner on the command-line shell to alert novice users when they are using an ephemeral in-memory database.
4. Fix editline support in the command-line shell.
5. Add support for coverage testing of VDBE programs using the [SQLITE_TESTCTRL_VDBE_COVERAGE](c3ref/c_testctrl_always.md) verb of [sqlite3_test_control()](c3ref/test_control.md).
6. Update the \_FILE_OFFSET_BITS macro so that builds work again on QNX.
7. Change the datatype of SrcList.nSrc from type u8 to type int to work around an issue in the C compiler on AIX.
8. Get extension loading working on Cygwin.
9. Bug fix: Fix the [char()](lang_corefunc.md#char) SQL function so that it returns an empty string rather than an "out of memory" error when called with zero arguments.
10. Bug fix: DISTINCT now recognizes that a [zeroblob](lang_corefunc.md#zeroblob) and a blob of all 0x00 bytes are the same thing. [Ticket \[fccbde530a\]](https://sqlite.org/src/info/fccbde530a)
11. Bug fix: Compute the correct answer for queries that contain an IS NOT NULL term in the WHERE clause and also contain an OR term in the WHERE clause and are compiled with [SQLITE_ENABLE_STAT4](compile.md#enable_stat4). [Ticket \[4c86b126f2\]](https://sqlite.org/src/info/4c86b126f2)
12. Bug fix: Make sure "rowid" columns are correctly resolved in joins between normal tables and WITHOUT ROWID tables. [Ticket \[c34d0557f7\]](https://sqlite.org/src/info/c34d0557f7)
13. Bug fix: Make sure the same temporary registers are not used in concurrent co-routines used to implement compound SELECT statements containing ORDER BY clauses, as such use can lead to incorrect answers. [Ticket \[8c63ff0eca\]](https://sqlite.org/src/info/8c63ff0eca)
14. Bug fix: Ensure that "ORDER BY random()" clauses do not get optimized out. [Ticket \[65bdeb9739\]](https://sqlite.org/src/info/65bdeb9739)
15. Bug fix: Repair a name-resolution error that can occur in sub-select statements contained within a TRIGGER. [Ticket \[4ef7e3cfca\]](https://sqlite.org/src/info/4ef7e3cfca)
16. Bug fix: Fix column default values expressions of the form "DEFAULT(-(-9223372036854775808))" so that they work correctly, initializing the column to a floating point value approximately equal to +9223372036854775808.0.
17. SQLITE_SOURCE_ID: "2014-03-10 12:20:37 530a1ee7dc2435f80960ce4710a3c2d2bfaaccc5"
18. SHA1 for sqlite3.c: b0c22e5f15f5ba2afd017ecd990ea507918afe1c
### 2014-02-11 (3.8.3.1)
1. Fix a bug (ticket [4c86b126f2](https://sqlite.org/src/info/4c86b126f2)) that causes rows to go missing on some queries with OR clauses and IS NOT NULL operators in the WHERE clause, when the [SQLITE_ENABLE_STAT3](compile.md#enable_stat3) or [SQLITE_ENABLE_STAT4](compile.md#enable_stat4) compile-time options are used.
2. Fix a harmless compiler warning that was causing problems for VS2013.
3. SQLITE_SOURCE_ID: "2014-02-11 14:52:19 ea3317a4803d71d88183b29f1d3086f46d68a00e"
4. SHA1 for sqlite3.c: 990004ef2d0eec6a339e4caa562423897fe02bf0
### 2014-02-03 (3.8.3)
1. Added support for [common table expressions](lang_with.md) and the [WITH clause](lang_with.md).
2. Added the [printf()](lang_corefunc.md#printf) SQL function.
3. Added [SQLITE_DETERMINISTIC](c3ref/c_deterministic.md#sqlitedeterministic) as an optional bit in the 4th argument to the [sqlite3_create_function()](c3ref/create_function.md) and related interfaces, providing applications with the ability to create new functions that can be factored out of inner loops when they have constant arguments.
4. Add [SQLITE_READONLY_DBMOVED](rescode.md#readonly_dbmoved) error code, returned at the beginning of a transaction, to indicate that the underlying database file has been renamed or moved out from under SQLite.
5. Allow arbitrary expressions, including function calls and subqueries, in the filename argument to [ATTACH](lang_attach.md).
6. Allow a [VALUES clause](lang_select.md#values) to be used anywhere a [SELECT](lang_select.md) statement is valid.
7. Reseed the PRNG used by [sqlite3_randomness(N,P)](c3ref/randomness.md) when invoked with N==0. Automatically reseed after a fork() on unix.
8. Enhance the [spellfix1](spellfix1.md) virtual table so that it can search efficiently by rowid.
9. Performance enhancements.
10. Improvements to the comments in the VDBE byte-code display when running [EXPLAIN](lang_explain.md).
11. Add the "%token_class" directive to [Lemon parser generator](lemon.md) and use it to simplify the grammar.
12. Change the [Lemon](lemon.md) source code to avoid calling C-library functions that OpenBSD considers dangerous. (Ex: sprintf).
13. Bug fix: In the [command-line shell](cli.md) CSV import feature, do not end a field when an escaped double-quote occurs at the end of a CRLN line.
14. SQLITE_SOURCE_ID: "2014-02-03 13:52:03 e816dd924619db5f766de6df74ea2194f3e3b538"
15. SHA1 for sqlite3.c: 98a07da78f71b0275e8d9c510486877adc31dbee
### 2013-12-06 (3.8.2)
1. Changed the defined behavior for the [CAST expression](lang_expr.md#castexpr) when floating point values greater than +9223372036854775807 are cast into integers so that the result is the largest possible integer, +9223372036854775807, instead of the smallest possible integer, -9223372036854775808. After this change, CAST(9223372036854775809.0 as INT) yields +9223372036854775807 instead of -9223372036854775808. **← Potentially Incompatible Change!**
2. Added support for [WITHOUT ROWID](withoutrowid.md) tables.
3. Added the [skip-scan optimization](optoverview.md#skipscan) to the query planner.
4. Extended the [virtual table](vtab.md) interface, and in particular the [sqlite3_index_info](c3ref/index_info.md) object to allow a virtual table to report its estimate on the number of rows that will be returned by a query.
5. Update the [R-Tree extension](rtree.md) to make use of the enhanced virtual table interface.
6. Add the [SQLITE_ENABLE_EXPLAIN_COMMENTS](compile.md#enable_explain_comments) compile-time option.
7. Enhanced the comments that are inserted into [EXPLAIN](lang_explain.md) output when the [SQLITE_ENABLE_EXPLAIN_COMMENTS](compile.md#enable_explain_comments) compile-time option is enabled.
8. Performance enhancements in the VDBE, especially to the OP_Column opcode.
9. Factor constant subexpressions in inner loops out to the initialization code in prepared statements.
10. Enhanced the ".explain" output formatting of the [command-line shell](cli.md) so that loops are indented to better show the structure of the program.
11. Enhanced the ".timer" feature of the [command-line shell](cli.md) so that it shows wall-clock time in addition to system and user times.
12. SQLITE_SOURCE_ID: "2013-12-06 14:53:30 27392118af4c38c5203a04b8013e1afdb1cebd0d"
13. SHA1 for sqlite3.c: 6422c7d69866f5ea3db0968f67ee596e7114544e
### 2013-10-17 (3.8.1)
1. Added the [unlikely()](lang_corefunc.md#unlikely) and [likelihood()](lang_corefunc.md#likelihood) SQL functions to be used as hints to the query planner.
2. Enhancements to the query planner:
1. Take into account the fact WHERE clause terms that cannot be used with indices still probably reduce the number of output rows.
2. Estimate the sizes of table and index rows and use the smallest applicable B-Tree for full scans and "count(\*)" operations.
3. Added the [soft_heap_limit pragma](pragma.md#pragma_soft_heap_limit).
4. Added support for [SQLITE_ENABLE_STAT4](compile.md#enable_stat4)
5. Added support for "sz=NNN" parameters at the end of [sqlite_stat1.stat](fileformat2.md#stat1tab) fields used to specify the average length in bytes for table and index rows.
6. Avoid running foreign-key constraint checks on an UPDATE if none of the modified columns are associated with foreign keys.
7. Added the [SQLITE_MINIMUM_FILE_DESCRIPTOR](compile.md#minimum_file_descriptor) compile-time option
8. Added the win32-longpath VFS on windows, permitting filenames up to 32K characters in length.
9. The [Date And Time Functions](lang_datefunc.md) are enhanced so that the current time (ex: julianday('now')) is always the same for multiple function invocations within the same [sqlite3_step()](c3ref/step.md) call.
10. Add the "totype.c" extension, implementing the tointeger() and toreal() SQL functions.
11. [FTS4](fts3.md#fts4) queries are better able to make use of docid\<\$limit constraints to limit the amount of I/O required.
12. Added the hidden [fts4aux languageid column](fts3.md#f4alid) to the [fts4aux](fts3.md#fts4aux) virtual table.
13. The [VACUUM](lang_vacuum.md) command packs the database about 1% tighter.
14. The sqlite3_analyzer utility program is updated to provide better descriptions and to compute a more accurate estimate for "Non-sequential pages"
15. Refactor the implementation of PRAGMA statements to improve parsing performance.
16. The directory used to hold temporary files on unix can now be set using the SQLITE_TMPDIR environment variable, which takes precedence over the TMPDIR environment variable. The [sqlite3_temp_directory](c3ref/temp_directory.md) global variable still has higher precedence than both environment variables, however.
17. Added the [PRAGMA stats](pragma.md#pragma_stats) statement.
18. **Bug fix:** Return the correct answer for "SELECT count(\*) FROM table" even if there is a [partial index](partialindex.md) on the table. Ticket [a5c8ed66ca](https://sqlite.org/src/info/a5c8ed66ca).
19. SQLITE_SOURCE_ID: "2013-10-17 12:57:35 c78be6d786c19073b3a6730dfe3fb1be54f5657a"
20. SHA1 for sqlite3.c: 0a54d76566728c2ba96292a49b138e4f69a7c391
### 2013-09-03 (3.8.0.2)
1. Fix a bug in the optimization that attempts to omit unused LEFT JOINs
2. SQLITE_SOURCE_ID: "2013-09-03 17:11:13 7dd4968f235d6e1ca9547cda9cf3bd570e1609ef"
3. SHA1 for sqlite3.c: 6cf0c7b46975a87a0dc3fba69c229a7de61b0c21
### 2013-08-29 (3.8.0.1)
1. Fix an off-by-one error that caused quoted empty string at the end of a CRLF-terminated line of CSV input to be misread by the command-line shell.
2. Fix a query planner bug involving a LEFT JOIN with a BETWEEN or LIKE/GLOB constraint and then another INNER JOIN to the right that involves an OR constraint.
3. Fix a query planner bug that could result in a segfault when querying tables with a UNIQUE or PRIMARY KEY constraint with more than four columns.
4. SQLITE_SOURCE_ID: "2013-08-29 17:35:01 352362bc01660edfbda08179d60f09e2038a2f49"
5. SHA1 for sqlite3.c: 99906bf63e6cef63d6f3d7f8526ac4a70e76559e
### 2013-08-26 (3.8.0)
1. Add support for [partial indexes](partialindex.md)
2. Cut-over to the [next generation query planner](queryplanner-ng.md) for faster and better query plans.
3. The [EXPLAIN QUERY PLAN](eqp.md) output no longer shows an estimate of the number of rows generated by each loop in a join.
4. Added the [FTS4 notindexed option](fts3.md#fts4notindexed), allowing non-indexed columns in an FTS4 table.
5. Added the [SQLITE_STMTSTATUS_VM_STEP](c3ref/c_stmtstatus_counter.md#sqlitestmtstatusvmstep) option to [sqlite3_stmt_status()](c3ref/stmt_status.md).
6. Added the [cache_spill pragma](pragma.md#pragma_cache_spill).
7. Added the [query_only pragma](pragma.md#pragma_query_only).
8. Added the [defer_foreign_keys pragma](pragma.md#pragma_defer_foreign_keys) and the [sqlite3_db_status](c3ref/db_status.md)(db, [SQLITE_DBSTATUS_DEFERRED_FKS](c3ref/c_dbstatus_options.md#sqlitedbstatusdeferredfks),...) C-language interface.
9. Added the "percentile()" function as a [loadable extension](loadext.md) in the ext/misc subdirectory of the source tree.
10. Added the [SQLITE_ALLOW_URI_AUTHORITY](compile.md#allow_uri_authority) compile-time option.
11. Add the [sqlite3_cancel_auto_extension(X)](c3ref/cancel_auto_extension.md) interface.
12. A running SELECT statement that lacks a FROM clause (or any other statement that never reads or writes from any database file) will not prevent a read transaction from closing.
13. Add the [SQLITE_DEFAULT_AUTOMATIC_INDEX](compile.md#default_automatic_index) compile-time option. Setting this option to 0 disables automatic indices by default.
14. Issue an [SQLITE_WARNING_AUTOINDEX](rescode.md#warning_autoindex) warning on the [SQLITE_CONFIG_LOG](c3ref/c_config_covering_index_scan.md#sqliteconfiglog) whenever the query planner uses an automatic index.
15. Added the [SQLITE_FTS3_MAX_EXPR_DEPTH](compile.md#fts3_max_expr_depth) compile-time option.
16. Added an optional 5th parameter defining the collating sequence to the next_char() extension SQL function.
17. The [SQLITE_BUSY_SNAPSHOT](rescode.md#busy_snapshot) extended error code is returned in WAL mode when a read transaction cannot be upgraded to a write transaction because the read is on an older snapshot.
18. Enhancements to the sqlite3_analyzer utility program to provide size information separately for each individual index of a table, in addition to the aggregate size.
19. Allow read transactions to be freely opened and closed by SQL statements run from within the implementation of [application-defined SQL functions](appfunc.md) if the function is called by a SELECT statement that does not access any database table.
20. Disable the use of posix_fallocate() on all (unix) systems unless the HAVE_POSIX_FALLOCATE compile-time option is used.
21. Update the ".import" command in the [command-line shell](cli.md) to support multi-line fields and correct RFC-4180 quoting and to issue warning and/or error messages if the input text is not strictly RFC-4180 compliant.
22. Bug fix: In the [unicode61](fts3.md#unicode61) tokenizer of [FTS4](fts3.md#fts4), treat all private code points as identifier symbols.
23. Bug fix: Bare identifiers in ORDER BY clauses bind more tightly to output column names, but identifiers in expressions bind more tightly to input column names. Identifiers in GROUP BY clauses always prefer output column names, however.
24. Bug fixes: Multiple problems in the legacy query optimizer were fixed by the move to [NGQP](queryplanner-ng.md).
25. SQLITE_SOURCE_ID: "2013-08-26 04:50:08 f64cd21e2e23ed7cff48f7dafa5e76adde9321c2"
26. SHA1 for sqlite3.c: b7347f4b4c2a840e6ba12040093d606bd16ea21e
### 2013-05-20 (3.7.17)
1. Add support for [memory-mapped I/O](mmap.md).
2. Add the [sqlite3_strglob()](c3ref/strglob.md) convenience interface.
3. Assigned the integer at offset 68 in the [database header](fileformat2.md#database_header) as the [Application ID](fileformat2.md#appid) for when SQLite is used as an [application file-format](appfileformat.md). Added the [PRAGMA application_id](pragma.md#pragma_application_id) command to query and set the Application ID.
4. Report rollback recovery in the [error log](errlog.md) as SQLITE_NOTICE_RECOVER_ROLLBACK. Change the error log code for WAL recover from SQLITE_OK to SQLITE_NOTICE_RECOVER_WAL.
5. Report the risky uses of [unlinked database files](howtocorrupt.md#unlink) and [database filename aliasing](howtocorrupt.md#alias) as SQLITE_WARNING messages in the [error log](errlog.md).
6. Added the [SQLITE_TRACE_SIZE_LIMIT](compile.md#trace_size_limit) compile-time option.
7. Increase the default value of [SQLITE_MAX_SCHEMA_RETRY](compile.md#max_schema_retry) to 50 and make sure that it is honored in every place that a schema change might force a statement retry.
8. Add a new test harness called "mptester" used to verify correct operation when multiple processes are using the same database file at the same time.
9. Enhance the [extension loading](loadext.md) mechanism to be more flexible (while still maintaining backwards compatibility) in two ways:
1. If the default entry point "sqlite3_extension_init" is not present in the loadable extension, also try an entry point "sqlite3_X_init" where "X" is based on the shared library filename. This allows every extension to have a different entry point, which allows them to be statically linked with no code changes.
2. The shared library filename passed to [sqlite3_load_extension()](c3ref/load_extension.md) may omit the filename suffix, and an appropriate architecture-dependent suffix (".so", ".dylib", or ".dll") will be added automatically.
10. Added many new loadable extensions to the source tree, including amatch, closure, fuzzer, ieee754, nextchar, regexp, spellfix, and wholenumber. See header comments on each extension source file for further information about what that extension does.
11. Enhance [FTS3](fts3.md) to avoid using excess stack space when there are a huge number of terms on the right-hand side of the MATCH operator. A side-effect of this change is that the MATCH operator can only accommodate 12 NEAR operators at a time.
12. Enhance the [fts4aux](fts3.md#fts4aux) virtual table so that it can be a TEMP table.
13. Added the [fts3tokenize virtual table](fts3.md#fts3tok) to the [full-text search](fts3.md) logic.
14. Query planner enhancement: Use the transitive property of constraints to move constraints into the outer loops of a join whenever possible, thereby reducing the amount of work that needs to occur in inner loops.
15. Discontinue the use of posix_fallocate() on unix, as it does not work on all filesystems.
16. Improved tracing and debugging facilities in the Windows [VFS](vfs.md).
17. Bug fix: Fix a potential **database corruption bug** in [shared cache mode](sharedcache.md) when one [database connection](c3ref/sqlite3.md) is closed while another is in the middle of a write transaction. Ticket [e636a050b7](https://sqlite.org/src/info/e636a050b7)
18. Bug fix: Only consider AS names from the result set as candidates for resolving identifiers in the WHERE clause if there are no other matches. In the ORDER BY clause, AS names take priority over any column names. Ticket [2500cdb9be05](https://sqlite.org/src/info/2500cdb9be05)
19. Bug fix: Do not allow a virtual table to cancel the ORDER BY clause unless all outer loops are guaranteed to return no more than one row result. Ticket [ba82a4a41eac1](https://sqlite.org/src/info/ba82a4a41eac1).
20. Bug fix: Do not suppress the ORDER BY clause on a virtual table query if an IN constraint is used. Ticket [f69b96e3076e](https://sqlite.org/src/info/f69b96e3076e).
21. Bug fix: The [command-line shell](cli.md) gives an exit code of 0 when terminated using the ".quit" command.
22. Bug fix: Make sure [PRAGMA](pragma.md#syntax) statements appear in [sqlite3_trace()](c3ref/profile.md) output.
23. Bug fix: When a [compound query](lang_select.md#compound) that uses an ORDER BY clause with a [COLLATE operator](lang_expr.md#collateop), make sure that the sorting occurs according to the specified collation and that the comparisons associate with the compound query use the native collation. Ticket [6709574d2a8d8](https://sqlite.org/src/info/6709574d2a8d8).
24. Bug fix: Makes sure the [authorizer](c3ref/set_authorizer.md) callback gets a valid pointer to the string "ROWID" for the column-name parameter when doing an [UPDATE](lang_update.md) that changes the rowid. Ticket [0eb70d77cb05bb2272](https://sqlite.org/src/info/0eb70d77cb05bb2272)
25. Bug fix: Do not move WHERE clause terms inside OR expressions that are contained within an ON clause of a LEFT JOIN. Ticket [f2369304e4](https://sqlite.org/src/info/f2369304e4)
26. Bug fix: Make sure an error is always reported when attempting to preform an operation that requires a [collating sequence](datatype3.md#collation) that is missing. Ticket [0fc59f908b](https://sqlite.org/src/info/0fc59f908b)
27. SQLITE_SOURCE_ID: "2013-05-20 00:56:22 118a3b35693b134d56ebd780123b7fd6f1497668"
28. SHA1 for sqlite3.c: 246987605d0503c700a08b9ee99a6b5d67454aab
### 2013-04-12 (3.7.16.2)
1. Fix a bug (present since version 3.7.13) that could result in database corruption on windows if two or more processes try to access the same database file at the same time and immediately after third process crashed in the middle of committing to that same file. See ticket [7ff3120e4f](https://sqlite.org/src/info/7ff3120e4f) for further information.
2. SQLITE_SOURCE_ID: "2013-04-12 11:52:43 cbea02d93865ce0e06789db95fd9168ebac970c7"
3. SHA1 for sqlite3.c: d466b54789dff4fb0238b9232e74896deaefab94
### 2013-03-29 (3.7.16.1)
1. Fix for a bug in the ORDER BY optimizer that was introduced in [version 3.7.15](#version_3_7_15) which would sometimes optimize out the sorting step when in fact the sort was required. Ticket [a179fe7465](https://sqlite.org/src/info/a179fe7465)
2. Fix a long-standing bug in the [CAST expression](lang_expr.md#castexpr) that would recognize UTF16 characters as digits even if their most-significant-byte was not zero. Ticket [689137afb6da41](https://sqlite.org/src/info/689137afb6da41).
3. Fix a bug in the NEAR operator of [FTS3](fts3.md) when applied to subfields. Ticket [38b1ae018f](https://sqlite.org/src/info/38b1ae018f).
4. Fix a long-standing bug in the storage engine that would (very rarely) cause a spurious report of an SQLITE_CORRUPT error but which was otherwise harmless. Ticket [6bfb98dfc0c](https://sqlite.org/src/info/6bfb98dfc0c).
5. The SQLITE_OMIT_MERGE_SORT option has been removed. The merge sorter is now a required component of SQLite.
6. Fixed lots of spelling errors in the source-code comments
7. SQLITE_SOURCE_ID: "2013-03-29 13:44:34 527231bc67285f01fb18d4451b28f61da3c4e39d"
8. SHA1 for sqlite3.c: 7a91ceceac9bcf47ceb8219126276e5518f7ff5a
### 2013-03-18 (3.7.16)
1. Added the [PRAGMA foreign_key_check](pragma.md#pragma_foreign_key_check) command.
2. Added new extended error codes for all SQLITE_CONSTRAINT errors
3. Added the SQLITE_READONLY_ROLLBACK extended error code for when a database cannot be opened because it needs rollback recovery but is read-only.
4. Added SQL functions [unicode(A)](lang_corefunc.md#unicode) and [char(X1,...,XN)](lang_corefunc.md#char).
5. Performance improvements for [PRAGMA incremental_vacuum](pragma.md#pragma_incremental_vacuum), especially in cases where the number of free pages is greater than what will fit on a single trunk page of the freelist.
6. Improved optimization of queries containing aggregate min() or max().
7. Enhance virtual tables so that they can potentially use an index when the WHERE clause contains the IN operator.
8. Allow indices to be used for sorting even if prior terms of the index are constrained by IN operators in the WHERE clause.
9. Enhance the [PRAGMA table_info](pragma.md#pragma_table_info) command so that the "pk" column is an increasing integer to show the order of columns in the primary key.
10. Enhance the query optimizer to exploit transitive join constraints.
11. Performance improvements in the query optimizer.
12. Allow the error message from [PRAGMA integrity_check](pragma.md#pragma_integrity_check) to be longer than 20000 bytes.
13. Improved name resolution for deeply nested queries.
14. Added the test_regexp.c module as a demonstration of how to implement the REGEXP operator.
15. Improved error messages in the [RTREE](rtree.md) extension.
16. Enhance the [command-line shell](cli.md) so that a non-zero argument to the ".exit" command causes the shell to exit immediately without cleanly shutting down the database connection.
17. Improved error messages for invalid boolean arguments to dot-commands in the [command-line shell](cli.md).
18. Improved error messages for "foreign key mismatch" showing the names of the two tables involved.
19. Remove all uses of umask() in the unix VFS.
20. Added the [PRAGMA vdbe_addoptrace](pragma.md#pragma_vdbe_addoptrace) and [PRAGMA vdbe_debug](pragma.md#pragma_vdbe_debug) commands.
21. Change to use strncmp() or the equivalent instead of memcmp() when comparing non-zero-terminated strings.
22. Update cygwin interfaces to omit deprecated API calls.
23. Enhance the [spellfix1](spellfix1.md) extension so that the edit distance cost table can be changed at runtime by inserting a string like 'edit_cost_table=TABLE' into the "command" field.
24. Bug fix: repair a long-standing problem that could cause incorrect query results in a 3-way or larger join that compared INTEGER fields against TEXT fields in two or more places. Ticket [fc7bd6358f](https://sqlite.org/src/info/fc7bd6358f)
25. Bug fix: Issue an error message if the 16-bit reference counter on a view overflows due to an overly complex query.
26. Bug fix: Avoid leaking memory on LIMIT and OFFSET clauses in deeply nested UNION ALL queries.
27. Bug fix: Make sure the schema is up-to-date prior to running pragmas table_info, index_list, index_info, and foreign_key_list.
28. SQLITE_SOURCE_ID: "2013-03-18 11:39:23 66d5f2b76750f3520eb7a495f6247206758f5b90"
29. SHA1 for sqlite3.c: 7308ab891ca1b2ebc596025cfe4dc36f1ee89cf6
### 2013-01-09 (3.7.15.2)
1. Fix a bug, introduced in [version 3.7.15](#version_3_7_15), that causes an ORDER BY clause to be optimized out of a three-way join when the ORDER BY is actually required. Ticket [598f5f7596b055](https://sqlite.org/src/info/598f5f7596b055)
2. SQLITE_SOURCE_ID: "2013-01-09 11:53:05 c0e09560d26f0a6456be9dd3447f5311eb4f238f"
3. SHA1 for sqlite3.c: 5741f47d1bc38aa0a8c38f09e60a5fe0031f272d
### 2012-12-19 (3.7.15.1)
1. Fix a bug, introduced in [version 3.7.15](#version_3_7_15), that causes a segfault if the AS name of a result column of a SELECT statement is used as a logical term in the WHERE clause. Ticket [a7b7803e8d1e869](https://sqlite.org/src/info/a7b7803e8d1e869).
2. SQLITE_SOURCE_ID: "2012-12-19 20:39:10 6b85b767d0ff7975146156a99ad673f2c1a23318"
3. SHA1 for sqlite3.c: bbbaa68061e925bd4d7d18d7e1270935c5f7e39a
### 2012-12-12 (3.7.15)
1. Added the [sqlite3_errstr()](c3ref/errcode.md) interface.
2. Avoid invoking the [sqlite3_trace()](c3ref/profile.md) callback multiple times when a statement is automatically reprepared due to [SQLITE_SCHEMA](rescode.md#schema) errors.
3. Added support for Windows Phone 8 platforms
4. Enhance IN operator processing to make use of indices with numeric affinities.
5. Do full-table scans using covering indices when possible, under the theory that an index will be smaller and hence can be scanned with less I/O.
6. Enhance the query optimizer so that ORDER BY clauses are more aggressively optimized, especially in joins where various terms of the ORDER BY clause come from separate tables of the join.
7. Add the ability to implement FROM clause subqueries as coroutines rather that manifesting the subquery into a temporary table.
8. Enhancements the command-line shell:
1. Added the ".print" command
2. Negative numbers in the ".width" command cause right-alignment
3. Add the ".wheretrace" command when compiled with SQLITE_DEBUG
9. Added the [busy_timeout pragma](pragma.md#pragma_busy_timeout).
10. Added the [instr()](lang_corefunc.md#instr) SQL function.
11. Added the [SQLITE_FCNTL_BUSYHANDLER](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlbusyhandler) file control, used to allow VFS implementations to get access to the busy handler callback.
12. The xDelete method in the built-in [VFSes](vfs.md) now return SQLITE_IOERR_DELETE_NOENT if the file to be deleted does not exist.
13. Enhanced support for QNX.
14. Work around an optimizer bug in the MSVC compiler when targeting ARM.
15. Bug fix: Avoid various concurrency problems in [shared cache mode](sharedcache.md).
16. Bug fix: Avoid a deadlock or crash if the [backup API](backup.md), [shared cache](sharedcache.md), and the SQLite Encryption Extension are all used at once.
17. Bug fix: SQL functions created using the TCL interface honor the "nullvalue" setting.
18. Bug fix: Fix a 32-bit overflow problem on CREATE INDEX for databases larger than 16GB.
19. Bug fix: Avoid segfault when using the [COLLATE operator](lang_expr.md#collateop) inside of a [CHECK constraint](lang_createtable.md#ckconst) or [view](lang_createview.md) in [shared cache mode](sharedcache.md).
20. SQLITE_SOURCE_ID: "2012-12-12 13:36:53 cd0b37c52658bfdf992b1e3dc467bae1835a94ae"
21. SHA1 for sqlite3.c: 2b413611f5e3e3b6ef5f618f2a9209cdf25cbcff"
### 2012-10-04 (3.7.14.1)
1. Fix a bug (ticket [\[d02e1406a58ea02d\]\]](https://sqlite.org/src/tktview/d02e1406a58ea02d)) that causes a segfault on a LEFT JOIN that includes an OR in the ON clause.
2. Work around a bug in the optimizer in the VisualStudio-2012 compiler that causes invalid code to be generated when compiling SQLite on ARM.
3. Fix the TCL interface so that the "nullvalue" setting is honored for TCL implementations of SQL functions.
4. SQLITE_SOURCE_ID: "2012-10-04 19:37:12 091570e46d04e84b67228e0bdbcd6e1fb60c6bdb"
5. SHA1 for sqlite3.c: 62aaecaacab3a4bf4a8fe4aec1cfdc1571fe9a44
### 2012-09-03 (3.7.14)
1. Drop built-in support for OS/2. If you need to upgrade an OS/2 application to use this or a later version of SQLite, then add an application-defined [VFS](vfs.md) using the [sqlite3_vfs_register()](c3ref/vfs_find.md) interface. The code removed in this release can serve as a baseline for the application-defined VFS.
2. Ensure that floating point values are preserved exactly when reconstructing a database from the output of the ".dump" command of the [command-line shell](cli.md).
3. Added the [sqlite3_close_v2()](c3ref/close.md) interface.
4. Updated the [command-line shell](cli.md) so that it can be built using [SQLITE_OMIT_FLOATING_POINT](compile.md#omit_floating_point) and [SQLITE_OMIT_AUTOINIT](compile.md#omit_autoinit).
5. Improvements to the windows makefiles and build processes.
6. Enhancements to [PRAGMA integrity_check](pragma.md#pragma_integrity_check) and [PRAGMA quick_check](pragma.md#pragma_quick_check) so that they can optionally check just a single attached database instead of all attached databases.
7. Enhancements to [WAL mode](wal.md) processing that ensure that at least one valid read-mark is available at all times, so that read-only processes can always read the database.
8. Performance enhancements in the sorter used by ORDER BY and CREATE INDEX.
9. Added the [SQLITE_DISABLE_FTS4_DEFERRED](compile.md#disable_fts4_deferred) compile-time option.
10. Better handling of aggregate queries where the aggregate functions are contained within subqueries.
11. Enhance the query planner so that it will try to use a [covering index](queryplanner.md#covidx) on queries that make use of [or optimization](optoverview.md#or_opt).
12. SQLITE_SOURCE_ID: "2012-09-03 15:42:36 c0d89d4a9752922f9e367362366efde4f1b06f2a"
13. SHA1 for sqlite3.c: 5fdf596b29bb426001f28b488ff356ae14d5a5a6
### 2012-06-11 (3.7.13)
1. [In-memory databases](inmemorydb.md) that are specified using [URI filenames](uri.md) are allowed to use [shared cache](sharedcache.md#inmemsharedcache), so that the same in-memory database can be accessed from multiple database connections.
2. Recognize and use the [mode=memory](uri.md#coreqp) query parameter in [URI filenames](uri.md).
3. Avoid resetting the schema of [shared cache](sharedcache.md) connections when any one connection closes. Instead, wait for the last connection to close before resetting the schema.
4. In the [RTREE](rtree.md) extension, when rounding 64-bit floating point numbers to 32-bit for storage, always round in a direction that causes the bounding box to get larger.
5. Adjust the unix driver to avoid unnecessary calls to fchown().
6. Add interfaces sqlite3_quota_ferror() and sqlite3_quota_file_available() to the test_quota.c module.
7. The [sqlite3_create_module()](c3ref/create_module.md) and [sqlite3_create_module_v2()](c3ref/create_module.md) interfaces return SQLITE_MISUSE on any attempt to overload or replace a [virtual table](vtab.md) module. The destructor is always called in this case, in accordance with historical and current documentation.
8. SQLITE_SOURCE_ID: "2012-06-11 02:05:22 f5b5a13f7394dc143aa136f1d4faba6839eaa6dc"
9. SHA1 for sqlite3.c: ff0a771d6252545740ba9685e312b0e3bb6a641b
### 2012-05-22 (3.7.12.1)
1. Fix a bug [(ticket c2ad16f997)](https://sqlite.org/src/info/c2ad16f997ee9c) in the 3.7.12 release that can cause a segfault for certain obscure nested aggregate queries.
2. Fix various other minor test script problems.
3. SQLITE_SOURCE_ID: "2012-05-22 02:45:53 6d326d44fd1d626aae0e8456e5fa2049f1ce0789"
4. SHA1 for sqlite3.c: d494e8d81607f0515d4f386156fb0fd86d5ba7df
### 2012-05-14 (3.7.12)
1. Add the [SQLITE_DBSTATUS_CACHE_WRITE](c3ref/c_dbstatus_options.md#sqlitedbstatuscachewrite) option for [sqlite3_db_status()](c3ref/db_status.md).
2. Optimize the [typeof()](lang_corefunc.md#typeof) and [length()](lang_corefunc.md#length) SQL functions so that they avoid unnecessary reading of database content from disk.
3. Add the [FTS4 "merge" command](fts3.md#*fts4mergecmd), the [FTS4 "automerge" command](fts3.md#*fts4automergecmd), and the [FTS4 "integrity-check" command](fts3.md#*fts4ickcmd).
4. Report the name of specific [CHECK](lang_createtable.md#ckconst) constraints that fail.
5. In the command-line shell, use popen() instead of fopen() if the first character of the argument to the ".output" command is "\|".
6. Make use of OVERLAPPED in the windows [VFS](vfs.md) to avoid some system calls and thereby obtain a performance improvement.
7. More aggressive optimization of the AND operator when one side or the other is always false.
8. Improved performance of queries with many OR-connected terms in the WHERE clause that can all be indexed.
9. Add the [SQLITE_RTREE_INT_ONLY](compile.md#rtree_int_only) compile-time option to force the [R\*Tree Extension Module](rtree.md) to use integer instead of floating point values for both storage and computation.
10. Enhance the [PRAGMA integrity_check](pragma.md#pragma_integrity_check) command to use much less memory when processing multi-gigabyte databases.
11. New interfaces added to the test_quota.c add-on module.
12. Added the ".trace" dot-command to the command-line shell.
13. Allow virtual table constructors to be invoked recursively.
14. Improved optimization of ORDER BY clauses on compound queries.
15. Improved optimization of aggregate subqueries contained within an aggregate query.
16. Bug fix: Fix the [RELEASE](lang_savepoint.md) command so that it does not cancel pending queries. This repairs a problem introduced in 3.7.11.
17. Bug fix: Do not discard the DISTINCT as superfluous unless a subset of the result set is subject to a UNIQUE constraint *and* it none of the columns in that subset can be NULL. Ticket [385a5b56b9](https://sqlite.org/src/info/385a5b56b9).
18. Bug fix: Do not optimize away an ORDER BY clause that has the same terms as a UNIQUE index unless those terms are also NOT NULL. Ticket [2a5629202f](https://sqlite.org/src/info/2a5629202f).
19. SQLITE_SOURCE_ID: "2012-05-14 01:41:23 8654aa9540fe9fd210899d83d17f3f407096c004"
20. SHA1 for sqlite3.c: 57e2104a0f7b3f528e7f6b7a8e553e2357ccd2e1
### 2012-03-20 (3.7.11)
1. Enhance the [INSERT](lang_insert.md) syntax to allow multiple rows to be inserted via the VALUES clause.
2. Enhance the [CREATE VIRTUAL TABLE](lang_createvtab.md) command to support the IF NOT EXISTS clause.
3. Added the [sqlite3_stricmp()](c3ref/stricmp.md) interface as a counterpart to [sqlite3_strnicmp()](c3ref/stricmp.md).
4. Added the [sqlite3_db_readonly()](c3ref/db_readonly.md) interface.
5. Added the [SQLITE_FCNTL_PRAGMA](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlpragma) file control, giving [VFS](vfs.md) implementations the ability to add new [PRAGMA](pragma.md#syntax) statements or to override built-in PRAGMAs.
6. Queries of the form: "SELECT max(x), y FROM table" returns the value of y on the same row that contains the maximum x value.
7. Added support for the [FTS4 languageid option](fts3.md#*fts4languageid).
8. Documented support for the [FTS4 content option](fts3.md#*fts4content). This feature has actually been in the code since [version 3.7.9](#version_3_7_9) but is only now considered to be officially supported.
9. Pending statements no longer block [ROLLBACK](lang_transaction.md). Instead, the pending statement will return SQLITE_ABORT upon next access after the ROLLBACK.
10. Improvements to the handling of CSV inputs in the [command-line shell](cli.md)
11. Fix a [bug](https://sqlite.org/src/info/b7c8682cc1) introduced in [version 3.7.10](#version_3_7_10) that might cause a LEFT JOIN to be incorrectly converted into an INNER JOIN if the WHERE clause indexable terms connected by OR.
12. SQLITE_SOURCE_ID: "2012-03-20 11:35:50 00bb9c9ce4f465e6ac321ced2a9d0062dc364669"
13. SHA1 for sqlite3.c: d460d7eda3a9dccd291aed2a9fda868b9b120a10
### 2012-01-16 (3.7.10)
1. The default [schema format number](fileformat2.md#schemaformat) is changed from 1 to 4. This means that, unless the [PRAGMA legacy_file_format=ON](pragma.md#pragma_legacy_file_format) statement is run, newly created database files will be unreadable by version of SQLite prior to 3.3.0 (2006-01-10). It also means that the [descending indices](lang_createindex.md#descidx) are enabled by default.
2. The sqlite3_pcache_methods structure and the [SQLITE_CONFIG_PCACHE](c3ref/c_config_covering_index_scan.md#sqliteconfigpcache) and [SQLITE_CONFIG_GETPCACHE](c3ref/c_config_covering_index_scan.md#sqliteconfiggetpcache) configuration parameters are deprecated. They are replaced by a new [sqlite3_pcache_methods2](c3ref/pcache_methods2.md) structure and [SQLITE_CONFIG_PCACHE2](c3ref/c_config_covering_index_scan.md#sqliteconfigpcache2) and [SQLITE_CONFIG_GETPCACHE2](c3ref/c_config_covering_index_scan.md#sqliteconfiggetpcache2) configuration parameters.
3. Added the [powersafe overwrite](psow.md) property to the VFS interface. Provide the [SQLITE_IOCAP_POWERSAFE_OVERWRITE](c3ref/c_iocap_atomic.md) I/O capability, the [SQLITE_POWERSAFE_OVERWRITE](compile.md#powersafe_overwrite) compile-time option, and the "psow=BOOLEAN" query parameter for [URI filenames](uri.md).
4. Added the [sqlite3_db_release_memory()](c3ref/db_release_memory.md) interface and the [shrink_memory pragma](pragma.md#pragma_shrink_memory).
5. Added the [sqlite3_db_filename()](c3ref/db_filename.md) interface.
6. Added the [sqlite3_stmt_busy()](c3ref/stmt_busy.md) interface.
7. Added the [sqlite3_uri_boolean()](c3ref/uri_boolean.md) and [sqlite3_uri_int64()](c3ref/uri_boolean.md) interfaces.
8. If the argument to [PRAGMA cache_size](pragma.md#pragma_cache_size) is negative N, that means to use approximately -1024\*N bytes of memory for the page cache regardless of the page size.
9. Enhanced the default memory allocator to make use of \_msize() on windows, malloc_size() on Mac, and malloc_usable_size() on Linux.
10. Enhanced the query planner to support index queries with range constraints on the rowid.
11. Enhanced the query planner flattening logic to allow UNION ALL compounds to be promoted upwards to replace a simple wrapper SELECT even if the compounds are joins.
12. Enhanced the query planner so that the xfer optimization can be used with INTEGER PRIMARY KEY ON CONFLICT as long as the destination table is initially empty.
13. Enhanced the windows [VFS](vfs.md) so that all system calls can be overridden using the xSetSystemCall interface.
14. Updated the "unix-dotfile" [VFS](vfs.md) to use locking directories with mkdir() and rmdir() instead of locking files with open() and unlink().
15. Enhancements to the test_quota.c extension to support stdio-like interfaces with quotas.
16. Change the unix [VFS](vfs.md) to be tolerant of read() system calls that return less then the full number of requested bytes.
17. Change both unix and windows [VFSes](vfs.md) to report a sector size of 4096 instead of the old default of 512.
18. In the [TCL Interface](tclsqlite.md), add the -uri option to the "sqlite3" TCL command used for creating new database connection objects.
19. Added the [SQLITE_TESTCTRL_EXPLAIN_STMT](c3ref/c_testctrl_always.md) test-control option with the [SQLITE_ENABLE_TREE_EXPLAIN](compile.md#enable_tree_explain) compile-time option to enable the [command-line shell](cli.md) to display ASCII-art parse trees of SQL statements that it processes, for debugging and analysis.
20. **Bug fix:** Add an additional xSync when restarting a WAL in order to prevent an exceedingly unlikely but theoretically possible database corruption following power-loss. Ticket [ff5be73dee](https://sqlite.org/src/info/ff5be73dee).
21. **Bug fix:** Change the VDBE so that all registers are initialized to Invalid instead of NULL. Ticket [7bbfb7d442](https://sqlite.org/src/info/7bbfb7d442)
22. **Bug fix:** Fix problems that can result from 32-bit integer overflow. Ticket [ac00f496b7e2](https://sqlite.org/src/info/ac0ff496b7e2)
23. SQLITE_SOURCE_ID: "2012-01-16 13:28:40 ebd01a8deffb5024a5d7494eef800d2366d97204"
24. SHA1 for sqlite3.c: 6497cbbaad47220bd41e2e4216c54706e7ae95d4
### 2011-11-01 (3.7.9)
1. If a search token (on the right-hand side of the MATCH operator) in [FTS4](fts3.md#fts4) begins with "^" then that token must be the first in its field of the document. **\*\* Potentially Incompatible Change \*\***
2. Added options [SQLITE_DBSTATUS_CACHE_HIT](c3ref/c_dbstatus_options.md#sqlitedbstatuscachehit) and [SQLITE_DBSTATUS_CACHE_MISS](c3ref/c_dbstatus_options.md#sqlitedbstatuscachemiss) to the [sqlite3_db_status()](c3ref/db_status.md) interface.
3. Removed support for [SQLITE_ENABLE_STAT2](compile.md#enable_stat2), replacing it with the much more capable [SQLITE_ENABLE_STAT3](compile.md#enable_stat3) option.
4. Enhancements to the sqlite3_analyzer utility program, including the --pageinfo and --stats options and support for multiplexed databases.
5. Enhance the [sqlite3_data_count()](c3ref/data_count.md) interface so that it can be used to determine if SQLITE_DONE has been seen on the prepared statement.
6. Added the [SQLITE_FCNTL_OVERWRITE](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntloverwrite) file-control by which the SQLite core indicates to the VFS that the current transaction will overwrite the entire database file.
7. Increase the default [lookaside memory allocator](malloc.md#lookaside) allocation size from 100 to 128 bytes.
8. Enhanced the query planner so that it can factor terms in and out of OR expressions in the WHERE clause in an effort to find better indices.
9. Added the [SQLITE_DIRECT_OVERFLOW_READ](compile.md#direct_overflow_read) compile-time option, causing [overflow pages](fileformat2.md#ovflpgs) to be read directly from the database file, bypassing the [page cache](c3ref/pcache_methods2.md).
10. Remove limits on the magnitude of precision and width value in the format specifiers of the [sqlite3_mprintf()](c3ref/mprintf.md) family of string rendering routines.
11. Fix a bug that prevent [ALTER TABLE ... RENAME](lang_altertable.md) from working on some virtual tables in a database with a UTF16 encoding.
12. Fix a bug in ASCII-to-float conversion that causes slow performance and incorrect results when converting numbers with ridiculously large exponents.
13. Fix a bug that causes incorrect results in aggregate queries that use multiple aggregate functions whose arguments contain complicated expressions that differ only in the case of string literals contained within those expressions.
14. Fix a bug that prevented the [page_count](pragma.md#pragma_page_count) and [quick_check](pragma.md#pragma_quick_check) pragmas from working correctly if their names were capitalized.
15. Fix a bug that caused [VACUUM](lang_vacuum.md) to fail if the [count_changes pragma](pragma.md#pragma_count_changes) was engaged.
16. Fix a bug in [virtual table](vtab.md) implementation that causes a crash if an [FTS4](fts3.md#fts4) table is [dropped](lang_droptable.md) inside a transaction and a [SAVEPOINT](lang_savepoint.md) occurs afterwards.
17. SQLITE_SOURCE_ID: "2011-11-01 00:52:41 c7c6050ef060877ebe77b41d959e9df13f8c9b5e"
18. SHA1 for sqlite3.c: becd16877f4f9b281b91c97e106089497d71bb47
### 2011-09-19 (3.7.8)
1. Orders of magnitude performance improvement for [CREATE INDEX](lang_createindex.md) on very large tables.
2. Improved the windows VFS to better defend against interference from anti-virus software.
3. Improved query plan optimization when the DISTINCT keyword is present.
4. Allow more system calls to be overridden in the unix VFS - to provide better support for chromium sandboxes.
5. Increase the default size of a lookahead cache line from 100 to 128 bytes.
6. Enhancements to the test_quota.c module so that it can track preexisting files.
7. Bug fix: Virtual tables now handle IS NOT NULL constraints correctly.
8. Bug fixes: Correctly handle nested correlated subqueries used with indices in a WHERE clause.
9. SQLITE_SOURCE_ID: "2011-09-19 14:49:19 3e0da808d2f5b4d12046e05980ca04578f581177"
10. SHA1 for sqlite3.c: bfcd74a655636b592c5dba6d0d5729c0f8e3b4de
### 2011-06-28 (3.7.7.1)
1. Fix [a bug](https://sqlite.org/src/info/25ee812710) causing [PRAGMA case_sensitive_like](pragma.md#pragma_case_sensitive_like) statements compiled using sqlite3_prepare() to fail with an [SQLITE_SCHEMA](rescode.md#schema) error.
2. SQLITE_SOURCE_ID: "2011-06-28 17:39:05 af0d91adf497f5f36ec3813f04235a6e195a605f"
3. SHA1 for sqlite3.c: d47594b8a02f6cf58e91fb673e96cb1b397aace0
### 2011-06-23 (3.7.7)
1. Add support for [URI filenames](uri.md)
2. Add the [sqlite3_vtab_config()](c3ref/vtab_config.md) interface in support of [ON CONFLICT](lang_conflict.md) clauses with [virtual tables](vtab.md).
3. Add the [xSavepoint](vtab.md#xsavepoint), [xRelease](vtab.md#xsavepoint) and [xRollbackTo](vtab.md#xsavepoint) methods in [virtual tables](vtab.md) in support of [SAVEPOINT](lang_savepoint.md) for virtual tables.
4. Update the built-in [FTS3/FTS4](fts3.md) and [RTREE](rtree.md) virtual tables to support [ON CONFLICT](lang_conflict.md) clauses and [REPLACE](lang_replace.md).
5. Avoid unnecessary reparsing of the database schema.
6. Added support for the [FTS4 prefix option](fts3.md#fts4prefix) and the [FTS4 order option](fts3.md#fts4order).
7. Allow [WAL-mode](wal.md) databases to be opened read-only as long as there is an existing read/write connection.
8. Added support for [short filenames](shortnames.md).
9. SQLITE_SOURCE_ID: "2011-06-23 19:49:22 4374b7e83ea0a3fbc3691f9c0c936272862f32f2"
10. SHA1 for sqlite3.c: 5bbe79e206ae5ffeeca760dbd0d66862228db551
### 2011-05-19 (3.7.6.3)
1. Fix a problem with [WAL mode](wal.md) which could cause transactions to silently rollback if the [cache_size](pragma.md#pragma_cache_size) is set very small (less than 10) and SQLite comes under memory pressure.
### 2011-04-17 (3.7.6.2)
1. Fix the function prototype for the open(2) system call to agree with POSIX. Without this fix, pthreads does not work correctly on NetBSD.
2. SQLITE_SOURCE_ID: "2011-04-17 17:25:17 154ddbc17120be2915eb03edc52af1225eb7cb5e"
3. SHA1 for sqlite3.c: 806577fd524dd5f3bfd8d4d27392ed2752bc9701
### 2011-04-13 (3.7.6.1)
1. Fix a bug in 3.7.6 that only appears if the [SQLITE_FCNTL_SIZE_HINT](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlsizehint) file control is used with a build of SQLite that makes use of the HAVE_POSIX_FALLOCATE compile-time option and which has SQLITE_ENABLE_LOCKING_MODE turned off.
2. SQLITE_SOURCE_ID: "2011-04-13 14:40:25 a35e83eac7b185f4d363d7fa51677f2fdfa27695"
3. SHA1 for sqlite3.c: b81bfa27d3e09caf3251475863b1ce6dd9f6ab66
### 2011-04-12 (3.7.6)
1. Added the [sqlite3_wal_checkpoint_v2()](c3ref/wal_checkpoint_v2.md) interface and enhanced the [wal_checkpoint pragma](pragma.md#pragma_wal_checkpoint) to support blocking checkpoints.
2. Improvements to the query planner so that it makes better estimates of plan costs and hence does a better job of choosing the right plan, especially when [SQLITE_ENABLE_STAT2](compile.md#enable_stat2) is used.
3. Fix a bug which prevented deferred foreign key constraints from being enforced when [sqlite3_finalize()](c3ref/finalize.md) was not called by one statement with a failed foreign key constraint prior to another statement with foreign key constraints running.
4. Integer arithmetic operations that would have resulted in overflow are now performed using floating-point instead.
5. Increased the version number on the [VFS object](c3ref/vfs.md) to 3 and added new methods xSetSysCall, xGetSysCall, and xNextSysCall used for doing full-coverage testing.
6. Increase the maximum value of [SQLITE_MAX_ATTACHED](limits.md#max_attached) from 30 to 62 (though the default value remains at 10).
7. Enhancements to FTS4:
1. Added the [fts4aux](fts3.md#fts4aux) table
2. Added support for [compressed FTS4 content](fts3.md#*fts4compression)
8. Enhance the [ANALYZE](lang_analyze.md) command to support the name of an index as its argument, in order to analyze just that one index.
9. Added the "unix-excl" built-in VFS on unix and unix-like platforms.
10. SQLITE_SOURCE_ID: "2011-04-12 01:58:40 f9d43fa363d54beab6f45db005abac0a7c0c47a7"
11. SHA1 for sqlite3.c: f38df08547efae0ff4343da607b723f588bbd66b
### 2011-02-01 (3.7.5)
1. Added the [sqlite3_vsnprintf()](c3ref/mprintf.md) interface.
2. Added the [SQLITE_DBSTATUS_LOOKASIDE_HIT](c3ref/c_dbstatus_options.md#sqlitedbstatuslookasidehit), [SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE](c3ref/c_dbstatus_options.md#sqlitedbstatuslookasidemisssize), and [SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL](c3ref/c_dbstatus_options.md#sqlitedbstatuslookasidemissfull) options for the [sqlite3_db_status()](c3ref/db_status.md) interface.
3. Added the [SQLITE_OMIT_AUTORESET](compile.md#omit_autoreset) compile-time option.
4. Added the [SQLITE_DEFAULT_FOREIGN_KEYS](compile.md#default_foreign_keys) compile-time option.
5. Updates to [sqlite3_stmt_readonly()](c3ref/stmt_readonly.md) so that its result is well-defined for all prepared statements and so that it works with [VACUUM](lang_vacuum.md).
6. Added the "-heap" option to the [command-line shell](cli.md)
7. Fix [a bug](https://sqlite.org/src/info/5d863f876e) involving frequent changes in and out of WAL mode and VACUUM that could (in theory) cause database corruption.
8. Enhance the [sqlite3_trace()](c3ref/profile.md) mechanism so that nested SQL statements such as might be generated by virtual tables are shown but are shown in comments and without parameter expansion. This greatly improves tracing output when using the FTS3/4 and/or RTREE virtual tables.
9. Change the xFileControl() methods on all built-in VFSes to return [SQLITE_NOTFOUND](rescode.md#notfound) instead of [SQLITE_ERROR](rescode.md#error) for an unrecognized operation code.
10. The SQLite core invokes the [SQLITE_FCNTL_SYNC_OMITTED](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlsyncomitted) [file control](c3ref/file_control.md) to the VFS in place of a call to xSync if the database has [PRAGMA synchronous](pragma.md#pragma_synchronous) set to OFF.
### 2010-12-07 (3.7.4)
1. Added the [sqlite3_blob_reopen()](c3ref/blob_reopen.md) interface to allow an existing [sqlite3_blob](c3ref/blob.md) object to be rebound to a new row.
2. Use the new [sqlite3_blob_reopen()](c3ref/blob_reopen.md) interface to improve the performance of FTS.
3. [VFSes](c3ref/vfs.md) that do not support shared memory are allowed to access [WAL](wal.md) databases if [PRAGMA locking_mode](pragma.md#pragma_locking_mode) is set to EXCLUSIVE.
4. Enhancements to [EXPLAIN QUERY PLAN](eqp.md).
5. Added the [sqlite3_stmt_readonly()](c3ref/stmt_readonly.md) interface.
6. Added [PRAGMA checkpoint_fullfsync](pragma.md#pragma_checkpoint_fullfsync).
7. Added the [SQLITE_FCNTL_FILE_POINTER](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlfilepointer) option to [sqlite3_file_control()](c3ref/file_control.md).
8. Added support for [FTS4](fts3.md#fts4) and enhancements to the FTS [matchinfo()](fts3.md#matchinfo) function.
9. Added the test_superlock.c module which provides example code for obtaining an exclusive lock to a rollback or WAL database.
10. Added the test_multiplex.c module which provides an example VFS that provides multiplexing (sharding) of a DB, splitting it over multiple files of fixed size.
11. A [very obscure bug](https://sqlite.org/src/info/80ba201079) associated with the [or optimization](optoverview.md#or_opt) was fixed.
### 2010-10-08 (3.7.3)
1. Added the [sqlite3_create_function_v2()](c3ref/create_function.md) interface that includes a destructor callback.
2. Added support for [custom r-tree queries](rtree.md#customquery) using application-supplied callback routines to define the boundary of the query region.
3. The default page cache strives more diligently to avoid using memory beyond what is allocated to it by [SQLITE_CONFIG_PAGECACHE](c3ref/c_config_covering_index_scan.md#sqliteconfigpagecache). Or if using page cache is allocating from the heap, it strives to avoid going over the [sqlite3_soft_heap_limit64()](c3ref/hard_heap_limit64.md), even if [SQLITE_ENABLE_MEMORY_MANAGEMENT](compile.md#enable_memory_management) is not set.
4. Added the [sqlite3_soft_heap_limit64()](c3ref/hard_heap_limit64.md) interface as a replacement for [sqlite3_soft_heap_limit()](c3ref/soft_heap_limit.md).
5. The [ANALYZE](lang_analyze.md) command now gathers statistics on tables even if they have no indices.
6. Tweaks to the query planner to help it do a better job of finding the most efficient query plan for each query.
7. Enhanced the internal text-to-numeric conversion routines so that they work with UTF8 or UTF16, thereby avoiding some UTF16-to-UTF8 text conversions.
8. Fix a problem that was causing excess memory usage with large [WAL](wal.md) transactions in win32 systems.
9. The interface between the VDBE and B-Tree layer is enhanced such that the VDBE provides hints to the B-Tree layer letting the B-Tree layer know when it is safe to use hashing instead of B-Trees for transient tables.
10. Miscellaneous documentation enhancements.
### 2010-08-24 (3.7.2)
1. Fix an [old and very obscure bug](https://sqlite.org/src/info/5e10420e8d) that can lead to corruption of the database [free-page list](fileformat2.md#freelist) when [incremental_vacuum](pragma.md#pragma_incremental_vacuum) is used.
### 2010-08-23 (3.7.1)
1. Added new commands [SQLITE_DBSTATUS_SCHEMA_USED](c3ref/c_dbstatus_options.md#sqlitedbstatusschemaused) and [SQLITE_DBSTATUS_STMT_USED](c3ref/c_dbstatus_options.md#sqlitedbstatusstmtused) to the [sqlite3_db_status()](c3ref/db_status.md) interface, in order to report out the amount of memory used to hold the schema and prepared statements of a connection.
2. Increase the maximum size of a database pages from 32KiB to 64KiB.
3. Use the [LIKE optimization](optoverview.md#like_opt) even if the right-hand side string contains no wildcards.
4. Added the [SQLITE_FCNTL_CHUNK_SIZE](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlchunksize) verb to the [sqlite3_file_control()](c3ref/file_control.md) interface for both unix and windows, to cause database files to grow in large chunks in order to reduce disk fragmentation.
5. Fixed a bug in the query planner that caused performance regressions relative to 3.6.23.1 on some complex joins.
6. Fixed a typo in the OS/2 backend.
7. Refactored the pager module.
8. The SQLITE_MAX_PAGE_SIZE compile-time option is now silently ignored. The maximum page size is hard-coded at 65536 bytes.
### 2010-08-04 (3.7.0.1)
1. Fix a potential database corruption bug that can occur if version 3.7.0 and version 3.6.23.1 alternately write to the same database file. [Ticket \[51ae9cad317a1\]](https://sqlite.org/src/info/51ae9cad317a1)
2. Fix a performance regression related to the query planner enhancements of version 3.7.0.
### 2010-07-21 (3.7.0)
1. Added support for [write-ahead logging](wal.md).
2. Query planner enhancement - automatic transient indices are created when doing so reduces the estimated query time.
3. Query planner enhancement - the ORDER BY becomes a no-op if the query also contains a GROUP BY clause that forces the correct output order.
4. Add the [SQLITE_DBSTATUS_CACHE_USED](c3ref/c_dbstatus_options.md#sqlitedbstatuscacheused) verb for [sqlite3_db_status()](c3ref/db_status.md).
5. The logical database size is now stored in the database header so that bytes can be appended to the end of the database file without corrupting it and so that SQLite will work correctly on systems that lack support for ftruncate().
### 2010-03-26 (3.6.23.1)
1. Fix a bug in the offsets() function of [FTS3](fts3.md)
2. Fix a missing "sync" that when omitted could lead to database corruption if a power failure or OS crash occurred just as a ROLLBACK operation was finishing.
### 2010-03-09 (3.6.23)
1. Added the [secure_delete pragma](pragma.md#pragma_secure_delete).
2. Added the [sqlite3_compileoption_used()](c3ref/compileoption_get.md) and [sqlite3_compileoption_get()](c3ref/compileoption_get.md) interfaces as well as the [compile_options pragma](pragma.md#pragma_compile_options) and the [sqlite_compileoption_used()](lang_corefunc.md#sqlite_compileoption_used) and [sqlite_compileoption_get()](lang_corefunc.md#sqlite_compileoption_get) SQL functions.
3. Added the [sqlite3_log()](c3ref/log.md) interface together with the [SQLITE_CONFIG_LOG](c3ref/c_config_covering_index_scan.md#sqliteconfiglog) verb to [sqlite3_config()](c3ref/config.md). The ".log" command is added to the [Command Line Interface](cli.md).
4. Improvements to [FTS3](fts3.md).
5. Improvements and bug-fixes in support for [SQLITE_OMIT_FLOATING_POINT](compile.md#omit_floating_point).
6. The [integrity_check pragma](pragma.md#pragma_integrity_check) is enhanced to detect out-of-order rowids.
7. The ".genfkey" operator has been removed from the [Command Line Interface](cli.md).
8. Updates to the co-hosted [Lemon LALR(1) parser generator](lemon.md). (These updates did not affect SQLite.)
9. Various minor bug fixes and performance enhancements.
### 2010-01-06 (3.6.22)
1. Fix bugs that can (rarely) lead to incorrect query results when the CAST or OR operators are used in the WHERE clause of a query.
2. Continuing enhancements and improvements to [FTS3](fts3.md).
3. Other miscellaneous bug fixes.
### 2009-12-07 (3.6.21)
1. The SQL output resulting from [sqlite3_trace()](c3ref/profile.md) is now modified to include the values of [bound parameters](lang_expr.md#varparam).
2. Performance optimizations targeting a specific use case from a single high-profile user of SQLite. A 12% reduction in the number of CPU operations is achieved (as measured by Valgrind). Actual performance improvements in practice may vary depending on workload. Changes include:
1. The [ifnull()](lang_corefunc.md#ifnull) and [coalesce()](lang_corefunc.md#coalesce) SQL functions are now implemented using in-line VDBE code rather than calling external functions, so that unused arguments need never be evaluated.
2. The [substr()](lang_corefunc.md#substr) SQL function does not bother to measure the length its entire input string if it is only computing a prefix
3. Unnecessary OP_IsNull, OP_Affinity, and OP_MustBeInt VDBE opcodes are suppressed
4. Various code refactorizations for performance
3. The FTS3 extension has undergone a major rework and cleanup. New [FTS3 documentation](fts3.md) is now available.
4. The [SQLITE_SECURE_DELETE](compile.md#secure_delete) compile-time option fixed to make sure that content is deleted even when the [truncate optimization](lang_delete.md#truncateopt) applies.
5. Improvements to "dot-command" handling in the [Command Line Interface](cli.md).
6. Other minor bug fixes and documentation enhancements.
### 2009-11-04 (3.6.20)
1. Optimizer enhancement: [prepared statements](c3ref/stmt.md) are automatically re-compiled when a binding on the RHS of a LIKE operator changes or when any range constraint changes under [SQLITE_ENABLE_STAT2](compile.md#enable_stat2).
2. Various minor bug fixes and documentation enhancements.
### 2009-10-30 (3.6.16.1)
1. A small patch to version 3.6.16 to fix [the OP_If bug](https://sqlite.org/src/info/6b00e0a34c).
### 2009-10-14 (3.6.19)
1. Added support for [foreign key constraints](foreignkeys.md). Foreign key constraints are disabled by default. Use the [foreign_keys pragma](pragma.md#pragma_foreign_keys) to turn them on.
2. Generalized the IS and IS NOT operators to take arbitrary expressions on their right-hand side.
3. The [TCL Interface](tclsqlite.md) has been enhanced to use the [Non-Recursive Engine (NRE)](http://www.tcl-lang.org/cgi-bin/tct/tip/322.html) interface to the TCL interpreter when linked against TCL 8.6 or later.
4. Fix a bug introduced in 3.6.18 that can lead to a segfault when an attempt is made to write on a read-only database.
### 2009-09-11 (3.6.18)
1. Versioning of the SQLite source code has transitioned from CVS to [Fossil](http://www.fossil-scm.org/).
2. Query planner enhancements.
3. The [SQLITE_ENABLE_STAT2](compile.md#enable_stat2) compile-time option causes the [ANALYZE](lang_analyze.md) command to collect a small histogram of each index, to help SQLite better select among competing range query indices.
4. Recursive triggers can be enabled using the [PRAGMA recursive_triggers](pragma.md#pragma_recursive_triggers) statement.
5. Delete triggers fire when rows are removed due to a [REPLACE conflict resolution](lang_conflict.md). This feature is only enabled when recursive triggers are enabled.
6. Added the [SQLITE_OPEN_SHAREDCACHE](c3ref/c_open_autoproxy.md) and [SQLITE_OPEN_PRIVATECACHE](c3ref/c_open_autoproxy.md) flags for [sqlite3_open_v2()](c3ref/open.md) used to override the global [shared cache mode](sharedcache.md) settings for individual database connections.
7. Added improved version identification features: C-Preprocessor macro [SQLITE_SOURCE_ID](c3ref/c_scm_branch.md), C/C++ interface [sqlite3_sourceid()](c3ref/libversion.md), and SQL function [sqlite_source_id()](lang_corefunc.md#sqlite_source_id).
8. Obscure bug fix on triggers ([\[efc02f9779\]](https://sqlite.org/src/info/efc02f9779)).
### 2009-08-10 (3.6.17)
1. Expose the [sqlite3_strnicmp()](c3ref/stricmp.md) interface for use by extensions and applications.
2. Remove the restriction on [virtual tables](vtab.md) and [shared cache mode](sharedcache.md). Virtual tables and shared cache can now be used at the same time.
3. Many code simplifications and obscure bug fixes in support of providing [100% branch test coverage](testing.md#coverage).
### 2009-06-27 (3.6.16)
1. Fix a bug (ticket \#3929) that occasionally causes INSERT or UPDATE operations to fail on an indexed table that has a self-modifying trigger.
2. Other minor bug fixes and performance optimizations.
### 2009-06-15 (3.6.15)
1. Refactor the internal representation of SQL expressions so that they use less memory on embedded platforms.
2. Reduce the amount of stack space used
3. Fix an 64-bit alignment bug on HP/UX and Sparc
4. The [sqlite3_create_function()](c3ref/create_function.md) family of interfaces now return [SQLITE_MISUSE](rescode.md#misuse) instead of [SQLITE_ERROR](rescode.md#error) when passed invalid parameter combinations.
5. When new tables are created using CREATE TABLE ... AS SELECT ... the datatype of the columns is the simplified SQLite datatype (TEXT, INT, REAL, NUMERIC, or BLOB) instead of a copy of the original datatype from the source table.
6. Resolve race conditions when checking for a hot rollback journal.
7. The [sqlite3_shutdown()](c3ref/initialize.md) interface frees all mutexes under windows.
8. Enhanced robustness against corrupt database files
9. Continuing improvements to the test suite and fixes to obscure bugs and inconsistencies that the test suite improvements are uncovering.
### 2009-05-25 (3.6.14.2)
1. Fix a code generator bug introduced in [version 3.6.14](#version_3_6_14). This bug can cause incorrect query results under obscure circumstances. Ticket \#3879.
### 2009-05-19 (3.6.14.1)
1. Fix a bug in [group_concat()](lang_aggfunc.md#group_concat), ticket \#3841
2. Fix a performance bug in the pager cache, ticket \#3844
3. Fix a bug in the [sqlite3_backup](c3ref/backup.md) implementation that can lead to a corrupt backup database. Ticket \#3858.
### 2009-05-07 (3.6.14)
1. Added the optional asynchronous VFS module.
2. Enhanced the query optimizer so that [virtual tables](vtab.md) are able to make use of OR and IN operators in the WHERE clause.
3. Speed improvements in the btree and pager layers.
4. Added the [SQLITE_HAVE_ISNAN](compile.md#have_isnan) compile-time option which will cause the isnan() function from the standard math library to be used instead of SQLite's own home-brew NaN checker.
5. Countless minor bug fixes, documentation improvements, new and improved test cases, and code simplifications and cleanups.
### 2009-04-13 (3.6.13)
1. Fix a bug in [version 3.6.12](#version_3_6_12) that causes a segfault when running a count(\*) on the sqlite_master table of an empty database. Ticket \#3774.
2. Fix a bug in [version 3.6.12](#version_3_6_12) that causes a segfault that when inserting into a table using a DEFAULT value where there is a function as part of the DEFAULT value expression. Ticket \#3791.
3. Fix data structure alignment issues on Sparc. Ticket \#3777.
4. Other minor bug fixes.
### 2009-03-31 (3.6.12)
1. Fixed a bug that caused database corruption when an [incremental_vacuum](pragma.md#pragma_incremental_vacuum) is rolled back in an in-memory database. Ticket \#3761.
2. Added the [sqlite3_unlock_notify()](c3ref/unlock_notify.md) interface.
3. Added the [reverse_unordered_selects pragma](pragma.md#pragma_reverse_unordered_selects).
4. The default page size on windows is automatically adjusted to match the capabilities of the underlying filesystem.
5. Add the new ".genfkey" command in the [CLI](cli.md) for generating triggers to implement foreign key constraints.
6. Performance improvements for "count(\*)" queries.
7. Reduce the amount of heap memory used, especially by TRIGGERs.
8.
### 2009-02-18 (3.6.11)
1. Added the [hot-backup interface](c3ref/backup_finish.md#sqlite3backupinit).
2. Added new commands ".backup" and ".restore" to the [CLI](cli.md).
3. Added new methods [backup](tclsqlite.md#backup) and [restore](tclsqlite.md#restore) to the TCL interface.
4. Improvements to the [syntax bubble diagrams](syntaxdiagrams.md)
5. Various minor bug fixes
### 2009-01-15 (3.6.10)
1. Fix a cache coherency problem that could lead to database corruption. Ticket \#3584.
### 2009-01-14 (3.6.9)
1. Fix two bugs, which when combined might result in incorrect query results. Both bugs were harmless by themselves; only when they team up do they cause problems. Ticket \#3581.
### 2009-01-12 (3.6.8)
1. Added support for [nested transactions](lang_savepoint.md)
2. Enhanced the query optimizer so that it is able to use multiple indices to efficiently process [OR-connected constraints](optoverview.md#or_opt) in a WHERE clause.
3. Added support for parentheses in FTS3 query patterns using the [SQLITE_ENABLE_FTS3_PARENTHESIS](compile.md#enable_fts3_parenthesis) compile-time option.
### 2008-12-16 (3.6.7)
1. Reorganize the Unix interface in os_unix.c
2. Added support for "Proxy Locking" on Mac OS X.
3. Changed the prototype of the [sqlite3_auto_extension()](c3ref/auto_extension.md) interface in a way that is backwards compatible but which might cause warnings in new builds of applications that use that interface.
4. Changed the signature of the xDlSym method of the [sqlite3_vfs](c3ref/vfs.md) object in a way that is backwards compatible but which might cause compiler warnings.
5. Added superfluous casts and variable initializations in order to suppress nuisance compiler warnings.
6. Fixes for various minor bugs.
### 2008-11-26 (3.6.6.2)
1. Fix a bug in the b-tree delete algorithm that seems like it might be able to cause database corruption. The bug was first introduced in [version 3.6.6](#version_3_6_6) by check-in \[5899\] on 2008-11-13.
2. Fix a memory leak that can occur following a disk I/O error.
### 2008-11-22 (3.6.6.1)
1. Fix a bug in the page cache that can lead database corruption following a rollback. This bug was first introduced in [version 3.6.4](#version_3_6_4).
2. Two other very minor bug fixes
### 2008-11-19 (3.6.6)
1. Fix a \#define that prevented [memsys5](malloc.md#memsys5) from compiling
2. Fix a problem in the virtual table commit mechanism that was causing a crash in FTS3. Ticket \#3497.
3. Add the [application-defined page cache](c3ref/pcache_methods2.md)
4. Added built-in support for VxWorks
### 2008-11-12 (3.6.5)
1. Add the MEMORY option to the [journal_mode pragma](pragma.md#pragma_journal_mode).
2. Added the [sqlite3_db_mutex()](c3ref/db_mutex.md) interface.
3. Added the [SQLITE_OMIT_TRUNCATE_OPTIMIZATION](compile.md#omit_truncate_optimization) compile-time option.
4. Fixed the [truncate optimization](lang_delete.md#truncateopt) so that [sqlite3_changes()](c3ref/changes.md) and [sqlite3_total_changes()](c3ref/total_changes.md) interfaces and the [count_changes pragma](pragma.md#pragma_count_changes) return the correct values.
5. Added the [sqlite3_extended_errcode()](c3ref/errcode.md) interface.
6. The [COMMIT](lang_transaction.md) command now succeeds even if there are pending queries. It returns [SQLITE_BUSY](rescode.md#busy) if there are pending incremental BLOB I/O requests.
7. The error code is changed to [SQLITE_BUSY](rescode.md#busy) (instead of [SQLITE_ERROR](rescode.md#error)) when an attempt is made to [ROLLBACK](lang_transaction.md) while one or more queries are still pending.
8. Drop all support for the [experimental memory allocators](malloc.md#memsysx) memsys4 and memsys6.
9. Added the [SQLITE_ZERO_MALLOC](compile.md#zero_malloc) compile-time option.
### 2008-10-15 (3.6.4)
1. Add option support for LIMIT and ORDER BY clauses on [DELETE](lang_delete.md) and [UPDATE](lang_update.md) statements. Only works if SQLite is compiled with [SQLITE_ENABLE_UPDATE_DELETE_LIMIT](compile.md#enable_update_delete_limit).
2. Added the [sqlite3_stmt_status()](c3ref/stmt_status.md) interface for performance monitoring.
3. Add the [INDEXED BY](lang_indexedby.md) clause.
4. The LOCKING_STYLE extension is now enabled by default on Mac OS X
5. Added the TRUNCATE option to [PRAGMA journal_mode](pragma.md#pragma_journal_mode)
6. Performance enhancements to tree balancing logic in the B-Tree layer.
7. Added the [source code](https://sqlite.org/src/finfo?name=tool/genfkey.c) and [documentation](https://sqlite.org/src/finfo?name=tool/genfkey.README) for the **genfkey** program for automatically generating triggers to enforce foreign key constraints.
8. Added the [SQLITE_OMIT_TRUNCATE_OPTIMIZATION](compile.md#omit_truncate_optimization) compile-time option.
9. The [SQL language documentation](lang.md) is converted to use [syntax diagrams](syntaxdiagrams.md) instead of BNF.
10. Other minor bug fixes
### 2008-09-22 (3.6.3)
1. Fix for a bug in the SELECT DISTINCT logic that was introduced by the prior version.
2. Other minor bug fixes
### 2008-08-30 (3.6.2)
1. Split the pager subsystem into separate pager and pcache subsystems.
2. Factor out identifier resolution procedures into separate files.
3. Bug fixes
### 2008-08-06 (3.6.1)
1. Added the [lookaside memory allocator](malloc.md#lookaside) for a speed improvement in excess of 15% on some workloads. (Your mileage may vary.)
2. Added the [SQLITE_CONFIG_LOOKASIDE](c3ref/c_config_covering_index_scan.md#sqliteconfiglookaside) verb to [sqlite3_config()](c3ref/config.md) to control the default lookaside configuration.
3. Added verbs [SQLITE_STATUS_PAGECACHE_SIZE](c3ref/c_status_malloc_count.md#sqlitestatuspagecachesize) and [SQLITE_STATUS_SCRATCH_SIZE](c3ref/c_status_malloc_count.md#sqlitestatusscratchsize) to the [sqlite3_status()](c3ref/status.md) interface.
4. Modified [SQLITE_CONFIG_PAGECACHE](c3ref/c_config_covering_index_scan.md#sqliteconfigpagecache) and [SQLITE_CONFIG_SCRATCH](c3ref/c_config_covering_index_scan.md#sqliteconfigscratch) to remove the "+4" magic number in the buffer size computation.
5. Added the [sqlite3_db_config()](c3ref/db_config.md) and [sqlite3_db_status()](c3ref/db_status.md) interfaces for controlling and monitoring the lookaside allocator separately on each [database connection](c3ref/sqlite3.md).
6. Numerous other performance enhancements
7. Miscellaneous minor bug fixes
### 2008-07-16 (3.6.0 beta)
1. Modifications to the [virtual file system](c3ref/vfs.md) interface to support a wider range of embedded systems. See [35to36.html](35to36.md) for additional information. \*\*\* Potentially incompatible change \*\*\*
2. All C-preprocessor macros used to control compile-time options now begin with the prefix "SQLITE\_". This may require changes to applications that compile SQLite using their own makefiles and with custom compile-time options, hence we mark this as a \*\*\* Potentially incompatible change \*\*\*
3. The SQLITE_MUTEX_APPDEF compile-time option is no longer supported. Alternative mutex implementations can now be added at run-time using the [sqlite3_config()](c3ref/config.md) interface with the [SQLITE_CONFIG_MUTEX](c3ref/c_config_covering_index_scan.md#sqliteconfigmutex) verb. \*\*\* Potentially incompatible change \*\*\*
4. The handling of IN and NOT IN operators that contain a NULL on their right-hand side expression is brought into compliance with the SQL standard and with other SQL database engines. This is a bug fix, but as it has the potential to break legacy applications that depend on the older buggy behavior, we mark that as a \*\*\* Potentially incompatible change \*\*\*
5. The result column names generated for compound subqueries have been simplified to show only the name of the column of the original table and omit the table name. This makes SQLite operate more like other SQL database engines.
6. Added the [sqlite3_config()](c3ref/config.md) interface for doing run-time configuration of the entire SQLite library.
7. Added the [sqlite3_status()](c3ref/status.md) interface used for querying run-time status information about the overall SQLite library and its subsystems.
8. Added the [sqlite3_initialize()](c3ref/initialize.md) and [sqlite3_shutdown()](c3ref/initialize.md) interfaces.
9. The [SQLITE_OPEN_NOMUTEX](c3ref/c_open_autoproxy.md) option was added to [sqlite3_open_v2()](c3ref/open.md).
10. Added the [PRAGMA page_count](pragma.md#pragma_page_count) command.
11. Added the [sqlite3_next_stmt()](c3ref/next_stmt.md) interface.
12. Added a new [R\*Tree virtual table](rtree.md)
### 2008-05-14 (3.5.9)
1. Added *experimental* support for the [journal_mode](pragma.md#pragma_journal_mode) PRAGMA and persistent journal.
2. [Journal mode PERSIST](pragma.md#pragma_journal_mode) is the default behavior in [exclusive locking mode](pragma.md#pragma_locking_mode).
3. Fix a performance regression on LEFT JOIN (see ticket \#3015) that was mistakenly introduced in [version 3.5.8](#version_3_5_8).
4. Performance enhancement: Reengineer the internal routines used to interpret and render variable-length integers.
5. Fix a buffer-overrun problem in [sqlite3_mprintf()](c3ref/mprintf.md) which occurs when a string without a zero-terminator is passed to "%.\*s".
6. Always convert IEEE floating point NaN values into NULL during processing. (Ticket \#3060)
7. Make sure that when a connection blocks on a RESERVED lock that it is able to continue after the lock is released. (Ticket \#3093)
8. The "configure" scripts should now automatically configure Unix systems for large file support. Improved error messages for when large files are encountered and large file support is disabled.
9. Avoid cache pages leaks following disk-full or I/O errors
10. And, many more minor bug fixes and performance enhancements....
### 2008-04-16 (3.5.8)
1. Expose SQLite's internal pseudo-random number generator (PRNG) via the [sqlite3_randomness()](c3ref/randomness.md) interface
2. New interface [sqlite3_context_db_handle()](c3ref/context_db_handle.md) that returns the [database connection](c3ref/sqlite3.md) handle that has invoked an application-defined SQL function.
3. New interface [sqlite3_limit()](c3ref/limit.md) allows size and length limits to be set on a per-connection basis and at run-time.
4. Improved crash-robustness: write the database page size into the rollback journal header.
5. Allow the [VACUUM](lang_vacuum.md) command to change the page size of a database file.
6. The xAccess() method of the VFS is allowed to return -1 to signal a memory allocation error.
7. Performance improvement: The OP_IdxDelete opcode uses unpacked records, obviating the need for one OP_MakeRecord opcode call for each index record deleted.
8. Performance improvement: Constant subexpressions are factored out of loops.
9. Performance improvement: Results of OP_Column are reused rather than issuing multiple OP_Column opcodes.
10. Fix a bug in the RTRIM collating sequence.
11. Fix a bug in the SQLITE_SECURE_DELETE option that was causing Firefox crashes. Make arrangements to always test SQLITE_SECURE_DELETE prior to each release.
12. Other miscellaneous performance enhancements.
13. Other miscellaneous minor bug fixes.
### 2008-03-17 (3.5.7)
1. Fix a bug (ticket \#2927) in the register allocation for compound selects - introduced by the new VM code in version 3.5.5.
2. ALTER TABLE uses double-quotes instead of single-quotes for quoting filenames.
3. Use the WHERE clause to reduce the size of a materialized VIEW in an UPDATE or DELETE statement. (Optimization)
4. Do not apply the flattening optimization if the outer query is an aggregate and the inner query contains ORDER BY. (Ticket \#2943)
5. Additional OS/2 updates
6. Added an experimental power-of-two, first-fit memory allocator.
7. Remove all instances of sprintf() from the code
8. Accept "Z" as the zulu timezone at the end of date strings
9. Fix a bug in the LIKE optimizer that occurs when the last character before the first wildcard is an upper-case "Z"
10. Added the "bitvec" object for keeping track of which pages have been journalled. Improves speed and reduces memory consumption, especially for large database files.
11. Get the SQLITE_ENABLE_LOCKING_STYLE macro working again on Mac OS X.
12. Store the statement journal in the temporary file directory instead of collocated with the database file.
13. Many improvements and cleanups to the configure script
### 2008-02-06 (3.5.6)
1. Fix a bug (ticket \#2913) that prevented virtual tables from working in a LEFT JOIN. The problem was introduced into shortly before the 3.5.5 release.
2. Bring the OS/2 porting layer up-to-date.
3. Add the new [sqlite3_result_error_code()](c3ref/result_blob.md) API and use it in the implementation of [ATTACH](lang_attach.md) so that proper error codes are returned when an [ATTACH](lang_attach.md) fails.
### 2008-01-31 (3.5.5)
1. Convert the underlying virtual machine to be a register-based machine rather than a stack-based machine. The only user-visible change is in the output of EXPLAIN.
2. Add the build-in RTRIM collating sequence.
### 2007-12-14 (3.5.4)
1. Fix a critical bug in UPDATE or DELETE that occurs when an OR REPLACE clause or a trigger causes rows in the same table to be deleted as side effects. (See ticket \#2832.) The most likely result of this bug is a segmentation fault, though database corruption is a possibility.
2. Bring the processing of ORDER BY into compliance with the SQL standard for case where a result alias and a table column name are in conflict. Correct behavior is to prefer the result alias. Older versions of SQLite incorrectly picked the table column. (See ticket \#2822.)
3. The [VACUUM](lang_vacuum.md) command preserves the setting of the [legacy_file_format pragma](pragma.md#pragma_legacy_file_format). (Ticket \#2804.)
4. Productize and officially support the group_concat() SQL function.
5. Better optimization of some IN operator expressions.
6. Add the ability to change the [auto_vacuum](pragma.md#pragma_auto_vacuum) status of a database by setting the auto_vaccum pragma and VACUUMing the database.
7. Prefix search in FTS3 is much more efficient.
8. Relax the SQL statement length restriction in the CLI so that the ".dump" output of databases with very large BLOBs and strings can be played back to recreate the database.
9. Other small bug fixes and optimizations.
### 2007-11-27 (3.5.3)
1. Move website and documentation files out of the source tree into a [separate CM system](https://sqlite.org/docsrc/).
2. Fix a long-standing bug in INSERT INTO ... SELECT ... statements where the SELECT is compound.
3. Fix a long-standing bug in RAISE(IGNORE) as used in BEFORE triggers.
4. Fixed the operator precedence for the ~ operator.
5. On Win32, do not return an error when attempting to delete a file that does not exist.
6. Allow collating sequence names to be quoted.
7. Modify the TCL interface to use [sqlite3_prepare_v2()](c3ref/prepare.md).
8. Fix multiple bugs that can occur following a malloc() failure.
9. [sqlite3_step()](c3ref/step.md) returns [SQLITE_MISUSE](rescode.md#misuse) instead of crashing when called with a NULL parameter.
10. FTS3 now uses the SQLite memory allocator exclusively. The FTS3 amalgamation can now be appended to the SQLite amalgamation to generate a super-amalgamation containing both.
11. The DISTINCT keyword now will sometimes use an INDEX if an appropriate index is available and the optimizer thinks its use might be advantageous.
### 2007-11-05 (3.5.2)
1. Dropped support for the [SQLITE_OMIT_MEMORY_ALLOCATION](compile.md#omitfeatures) compile-time option.
2. Always open files using FILE_FLAG_RANDOM_ACCESS under Windows.
3. The 3rd parameter of the built-in SUBSTR() function is now optional.
4. Bug fix: do not invoke the authorizer when reparsing the schema after a schema change.
5. Added the experimental malloc-free memory allocator in mem3.c.
6. Virtual machine stores 64-bit integer and floating point constants in binary instead of text for a performance boost.
7. Fix a race condition in test_async.c.
8. Added the ".timer" command to the CLI
### 2007-10-04 (3.5.1)
1. ***Nota Bene:** We are not using terms "alpha" or "beta" on this release because the code is stable and because if we use those terms, nobody will upgrade. However, we still reserve the right to make incompatible changes to the new VFS interface in future releases.*
2. Fix a bug in the handling of [SQLITE_FULL](rescode.md#full) errors that could lead to database corruption. Ticket \#2686.
3. The test_async.c drive now does full file locking and works correctly when used simultaneously by multiple processes on the same database.
4. The CLI ignores whitespace (including comments) at the end of lines
5. Make sure the query optimizer checks dependencies on all terms of a compound SELECT statement. Ticket \#2640.
6. Add demonstration code showing how to build a VFS for a raw mass storage without a filesystem.
7. Added an output buffer size parameter to the xGetTempname() method of the VFS layer.
8. Sticky [SQLITE_FULL](rescode.md#full) or [SQLITE_IOERR](rescode.md#ioerr) errors in the pager are reset when a new transaction is started.
### 2007-09-04 (3.5.0) alpha
1. Redesign the OS interface layer. See [34to35.html](34to35.md) for details. \*\*\* Potentially incompatible change \*\*\*
2. The [sqlite3_release_memory()](c3ref/release_memory.md), [sqlite3_soft_heap_limit()](c3ref/soft_heap_limit.md), and [sqlite3_enable_shared_cache()](c3ref/enable_shared_cache.md) interfaces now work cross all threads in the process, not just the single thread in which they are invoked. \*\*\* Potentially incompatible change \*\*\*
3. Added the [sqlite3_open_v2()](c3ref/open.md) interface.
4. Reimplemented the memory allocation subsystem and made it replaceable at compile-time.
5. Created a new mutex subsystem and made it replicable at compile-time.
6. The same database connection may now be used simultaneously by separate threads.
### 2007-08-13 (3.4.2)
1. Fix a database corruption bug that might occur if a ROLLBACK command is executed in [auto-vacuum mode](pragma.md#pragma_auto_vacuum) and a very small [sqlite3_soft_heap_limit](c3ref/soft_heap_limit.md) is set. Ticket \#2565.
2. Add the ability to run a full regression test with a small [sqlite3_soft_heap_limit](c3ref/soft_heap_limit.md).
3. Fix other minor problems with using small soft heap limits.
4. Work-around for [GCC bug 32575](http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32575).
5. Improved error detection of misused aggregate functions.
6. Improvements to the amalgamation generator script so that all symbols are prefixed with either SQLITE_PRIVATE or SQLITE_API.
### 2007-07-20 (3.4.1)
1. Fix a bug in [VACUUM](lang_vacuum.md) that can lead to database corruptio if two processes are connected to the database at the same time and one VACUUMs then the other then modifies the database.
2. The expression "+column" is now considered the same as "column" when computing the collating sequence to use on the expression.
3. In the [TCL language interface](tclsqlite.md), "@variable" instead of "\$variable" always binds as a blob.
4. Added [PRAGMA freelist_count](pragma.md#pragma_freelist_count) for determining the current size of the freelist.
5. The [PRAGMA auto_vacuum=incremental](pragma.md#pragma_auto_vacuum) setting is now persistent.
6. Add FD_CLOEXEC to all open files under Unix.
7. Fix a bug in the [min()/max() optimization](optoverview.md#minmax) when applied to descending indices.
8. Make sure the TCL language interface works correctly with 64-bit integers on 64-bit machines.
9. Allow the value -9223372036854775808 as an integer literal in SQL statements.
10. Add the capability of "hidden" columns in virtual tables.
11. Use the macro SQLITE_PRIVATE (defaulting to "static") on all internal functions in the amalgamation.
12. Add pluggable tokenizers and [ICU](https://icu.unicode.org) tokenization support to FTS2
13. Other minor bug fixes and documentation enhancements
### 2007-06-18 (3.4.0)
1. Fix a bug that can lead to database corruption if an [SQLITE_BUSY](rescode.md#busy) error occurs in the middle of an explicit transaction and that transaction is later committed. Ticket \#2409.
2. Fix a bug that can lead to database corruption if autovacuum mode is on and a malloc() failure follows a CREATE TABLE or CREATE INDEX statement which itself follows a cache overflow inside a transaction. See ticket \#2418.
3. Added explicit [upper bounds](limits.md) on the sizes and quantities of things SQLite can process. This change might cause compatibility problems for applications that use SQLite in the extreme, which is why the current release is 3.4.0 instead of 3.3.18.
4. Added support for [Incremental BLOB I/O](c3ref/blob_open.md).
5. Added the [sqlite3_bind_zeroblob()](c3ref/bind_blob.md) API and the [zeroblob()](lang_corefunc.md#zeroblob) SQL function.
6. Added support for [Incremental Vacuum](pragma.md#pragma_incremental_vacuum).
7. Added the SQLITE_MIXED_ENDIAN_64BIT_FLOAT compile-time option to support ARM7 processors with goofy endianness.
8. Removed all instances of sprintf() and strcpy() from the core library.
9. Added support for [International Components for Unicode (ICU)](https://icu.unicode.org) to the full-text search extensions.
10. In the Windows OS driver, reacquire a SHARED lock if an attempt to acquire an EXCLUSIVE lock fails. Ticket \#2354
11. Fix the REPLACE() function so that it returns NULL if the second argument is an empty string. Ticket \#2324.
12. Document the hazards of type conversions in [sqlite3_column_blob()](c3ref/column_blob.md) and related APIs. Fix unnecessary type conversions. Ticket \#2321.
13. Internationalization of the TRIM() function. Ticket \#2323
14. Use memmove() instead of memcpy() when moving between memory regions that might overlap. Ticket \#2334
15. Fix an optimizer bug involving subqueries in a compound SELECT that has both an ORDER BY and a LIMIT clause. Ticket \#2339.
16. Make sure the [sqlite3_snprintf()](c3ref/mprintf.md) interface does not zero-terminate the buffer if the buffer size is less than 1. Ticket \#2341
17. Fix the built-in printf logic so that it prints "NaN" not "Inf" for floating-point NaNs. Ticket \#2345
18. When converting BLOB to TEXT, use the text encoding of the main database. Ticket \#2349
19. Keep the full precision of integers (if possible) when casting to NUMERIC. Ticket \#2364
20. Fix a bug in the handling of UTF16 codepoint 0xE000
21. Consider explicit collate clauses when matching WHERE constraints to indices in the query optimizer. Ticket \#2391
22. Fix the query optimizer to correctly handle constant expressions in the ON clause of a LEFT JOIN. Ticket \#2403
23. Fix the query optimizer to handle rowid comparisons to NULL correctly. Ticket \#2404
24. Fix many potential segfaults that could be caused by malicious SQL statements.
### 2007-04-25 (3.3.17)
1. When the "write_version" value of the database header is larger than what the library understands, make the database read-only instead of unreadable.
2. Other minor bug fixes
### 2007-04-18 (3.3.16)
1. Fix a bug that caused VACUUM to fail if NULLs appeared in a UNIQUE column.
2. Reinstate performance improvements that were added in [Version 3.3.14](#version_3_3_14) but regressed in [Version 3.3.15](#version_3_3_15).
3. Fix problems with the handling of ORDER BY expressions on compound SELECT statements in subqueries.
4. Fix a potential segfault when destroying locks on WinCE in a multi-threaded environment.
5. Documentation updates.
### 2007-04-09 (3.3.15)
1. Fix a bug introduced in 3.3.14 that caused a rollback of CREATE TEMP TABLE to leave the database connection wedged.
2. Fix a bug that caused an extra NULL row to be returned when a descending query was interrupted by a change to the database.
3. The FOR EACH STATEMENT clause on a trigger now causes a syntax error. It used to be silently ignored.
4. Fix an obscure and relatively harmless problem that might have caused a resource leak following an I/O error.
5. Many improvements to the test suite. Test coverage now exceeded 98%
### 2007-04-02 (3.3.14)
1. Fix a bug (ticket \#2273) that could cause a segfault when the IN operator is used one term of a two-column index and the right-hand side of the IN operator contains a NULL.
2. Added a new OS interface method for determining the sector size of underlying media: sqlite3OsSectorSize().
3. A new algorithm for statements of the form INSERT INTO *table1* SELECT \* FROM *table2* is faster and reduces fragmentation. VACUUM uses statements of this form and thus runs faster and defragments better.
4. Performance enhancements through reductions in disk I/O:
1. Do not read the last page of an overflow chain when deleting the row - just add that page to the freelist.
2. Do not store pages being deleted in the rollback journal.
3. Do not read in the (meaningless) content of pages extracted from the freelist.
4. Do not flush the page cache (and thus avoiding a cache refill) unless another process changes the underlying database file.
5. Truncate rather than delete the rollback journal when committing a transaction in exclusive access mode, or when committing the TEMP database.
5. Added support for exclusive access mode using ["PRAGMA locking_mode=EXCLUSIVE"](pragma.md#pragma_locking_mode)
6. Use heap space instead of stack space for large buffers in the pager - useful on embedded platforms with stack-space limitations.
7. Add a makefile target "sqlite3.c" that builds an amalgamation containing the core SQLite library C code in a single file.
8. Get the library working correctly when compiled with GCC option "-fstrict-aliasing".
9. Removed the vestigal SQLITE_PROTOCOL error.
10. Improvements to test coverage, other minor bugs fixed, memory leaks plugged, code refactored and/or recommended in places for easier reading.
### 2007-02-13 (3.3.13)
1. Add a "fragmentation" measurement in the output of sqlite3_analyzer.
2. Add the COLLATE operator used to explicitly set the collating sequence used by an expression. This feature is considered experimental pending additional testing.
3. Allow up to 64 tables in a join - the old limit was 32.
4. Added two new experimental functions: [randomblob()](lang_corefunc.md#randomblob) and [hex()](lang_corefunc.md#hex). Their intended use is to facilitate generating [UUIDs](http://en.wikipedia.org/wiki/UUID).
5. Fix a problem where [PRAGMA count_changes](pragma.md#pragma_count_changes) was causing incorrect results for updates on tables with triggers
6. Fix a bug in the ORDER BY clause optimizer for joins where the left-most table in the join is constrained by a UNIQUE index.
7. Fixed a bug in the "copy" method of the TCL interface.
8. Bug fixes in fts1 and fts2 modules.
### 2007-01-27 (3.3.12)
1. Fix another bug in the IS NULL optimization that was added in version 3.3.9.
2. Fix an assertion fault that occurred on deeply nested views.
3. Limit the amount of output that [PRAGMA integrity_check](pragma.md#pragma_integrity_check) generates.
4. Minor syntactic changes to support a wider variety of compilers.
### 2007-01-22 (3.3.11)
1. Fix another bug in the implementation of the new [sqlite3_prepare_v2()](c3ref/prepare.md) API. We'll get it right eventually...
2. Fix a bug in the IS NULL optimization that was added in version 3.3.9 - the bug was causing incorrect results on certain LEFT JOINs that included in the WHERE clause an IS NULL constraint for the right table of the LEFT JOIN.
3. Make AreFileApisANSI() a no-op macro in WinCE since WinCE does not support this function.
### 2007-01-09 (3.3.10)
1. Fix bugs in the implementation of the new [sqlite3_prepare_v2()](c3ref/prepare.md) API that can lead to segfaults.
2. Fix 1-second round-off errors in the strftime() function
3. Enhance the Windows OS layer to provide detailed error codes
4. Work around a win2k problem so that SQLite can use single-character database file names
5. The [user_version](pragma.md#pragma_user_version) and [schema_version](pragma.md#pragma_schema_version) pragmas correctly set their column names in the result set
6. Documentation updates
### 2007-01-04 (3.3.9)
1. Fix bugs in pager.c that could lead to database corruption if two processes both try to recover a hot journal at the same instant
2. Added the [sqlite3_prepare_v2()](c3ref/prepare.md) API.
3. Fixed the ".dump" command in the command-line shell to show indices, triggers and views again.
4. Change the table_info pragma so that it returns NULL for the default value if there is no default value
5. Support for non-ASCII characters in win95 filenames
6. Query optimizer enhancements:
1. Optimizer does a better job of using indices to satisfy ORDER BY clauses that sort on the integer primary key
2. Use an index to satisfy an IS NULL operator in the WHERE clause
3. Fix a bug that was causing the optimizer to miss an OR optimization opportunity
4. The optimizer has more freedom to reorder tables in the FROM clause even in there are LEFT joins.
7. Extension loading supported added to WinCE
8. Allow constraint names on the DEFAULT clause in a table definition
9. Added the ".bail" command to the command-line shell
10. Make CSV (comma separate value) output from the command-line shell more closely aligned to accepted practice
11. Experimental FTS2 module added
12. Use sqlite3_mprintf() instead of strdup() to avoid libc dependencies
13. VACUUM uses a temporary file in the official TEMP folder, not in the same directory as the original database
14. The prefix on temporary filenames on Windows is changed from "sqlite" to "etilqs".
### 2006-10-09 (3.3.8)
1. Support for full text search using the FTS1 module (beta)
2. Added Mac OS X locking patches (beta - disabled by default)
3. Introduce extended error codes and add error codes for various kinds of I/O errors.
4. Added support for IF EXISTS on CREATE/DROP TRIGGER/VIEW
5. Fix the regression test suite so that it works with Tcl8.5
6. Enhance sqlite3_set_authorizer() to provide notification of calls to SQL functions.
7. Added experimental API: sqlite3_auto_extension()
8. Various minor bug fixes
### 2006-08-12 (3.3.7)
1. Added support for virtual tables (beta)
2. Added support for dynamically loaded extensions (beta)
3. The [sqlite3_interrupt()](c3ref/interrupt.md) routine can be called for a different thread
4. Added the [MATCH](lang_expr.md#match) operator.
5. The default file format is now 1.
### 2006-06-06 (3.3.6)
1. Plays better with virus scanners on Windows
2. Faster :memory: databases
3. Fix an obscure segfault in UTF-8 to UTF-16 conversions
4. Added driver for OS/2
5. Correct column meta-information returned for aggregate queries
6. Enhanced output from EXPLAIN QUERY PLAN
7. LIMIT 0 now works on subqueries
8. Bug fixes and performance enhancements in the query optimizer
9. Correctly handle NULL filenames in ATTACH and DETACH
10. Improved syntax error messages in the parser
11. Fix type coercion rules for the IN operator
### 2006-04-05 (3.3.5)
1. CHECK constraints use conflict resolution algorithms correctly.
2. The SUM() function throws an error on integer overflow.
3. Choose the column names in a compound query from the left-most SELECT instead of the right-most.
4. The sqlite3_create_collation() function honors the SQLITE_UTF16_ALIGNED flag.
5. SQLITE_SECURE_DELETE compile-time option causes deletes to overwrite old data with zeros.
6. Detect integer overflow in abs().
7. The random() function provides 64 bits of randomness instead of only 32 bits.
8. Parser detects and reports automaton stack overflow.
9. Change the round() function to return REAL instead of TEXT.
10. Allow WHERE clause terms on the left table of a LEFT OUTER JOIN to contain aggregate subqueries.
11. Skip over leading spaces in text to numeric conversions.
12. Various minor bug and documentation typo fixes and performance enhancements.
### 2006-02-11 (3.3.4)
1. Fix a blunder in the Unix mutex implementation that can lead to deadlock on multithreaded systems.
2. Fix an alignment problem on 64-bit machines
3. Added the fullfsync pragma.
4. Fix an optimizer bug that could have caused some unusual LEFT OUTER JOINs to give incorrect results.
5. The SUM function detects integer overflow and converts to accumulating an approximate result using floating point numbers
6. Host parameter names can begin with '@' for compatibility with SQL Server.
7. Other miscellaneous bug fixes
### 2006-01-31 (3.3.3)
1. Removed support for an ON CONFLICT clause on CREATE INDEX - it never worked correctly so this should not present any backward compatibility problems.
2. Authorizer callback now notified of ALTER TABLE ADD COLUMN commands
3. After any changes to the TEMP database schema, all prepared statements are invalidated and must be recreated using a new call to sqlite3_prepare()
4. Other minor bug fixes in preparation for the first stable release of version 3.3
### 2006-01-24 (3.3.2 beta)
1. Bug fixes and speed improvements. Improved test coverage.
2. Changes to the OS-layer interface: mutexes must now be recursive.
3. Discontinue the use of thread-specific data for out-of-memory exception handling
### 2006-01-16 (3.3.1 alpha)
1. Countless bug fixes
2. Speed improvements
3. Database connections can now be used by multiple threads, not just the thread in which they were created.
### 2006-01-11 (3.3.0 alpha)
1. CHECK constraints
2. IF EXISTS and IF NOT EXISTS clauses on CREATE/DROP TABLE/INDEX.
3. DESC indices
4. More efficient encoding of boolean values resulting in smaller database files
5. More aggressive [SQLITE_OMIT_FLOATING_POINT](compile.md#omit_floating_point)
6. Separate INTEGER and REAL affinity
7. Added a virtual function layer for the OS interface
8. "exists" method added to the TCL interface
9. Improved response to out-of-memory errors
10. Database cache can be optionally shared between connections in the same thread
11. Optional READ UNCOMMITTED isolation (instead of the default isolation level of SERIALIZABLE) and table level locking when database connections share a common cache.
### 2005-12-19 (3.2.8)
1. Fix an obscure bug that can cause database corruption under the following unusual circumstances: A large INSERT or UPDATE statement which is part of an even larger transaction fails due to a uniqueness constraint but the containing transaction commits.
### 2005-12-19 (2.8.17)
1. Fix an obscure bug that can cause database corruption under the following unusual circumstances: A large INSERT or UPDATE statement which is part of an even larger transaction fails due to a uniqueness contraint but the containing transaction commits.
### 2005-09-24 (3.2.7)
1. GROUP BY now considers NULLs to be equal again, as it should
2. Now compiles on Solaris and OpenBSD and other Unix variants that lack the fdatasync() function
3. Now compiles on MSVC++6 again
4. Fix uninitialized variables causing malfunctions for various obscure queries
5. Correctly compute a LEFT OUTER JOINs that is constrained on the left table only
### 2005-09-17 (3.2.6)
1. Fix a bug that can cause database corruption if a VACUUM (or autovacuum) fails and is rolled back on a database that is larger than 1GiB
2. LIKE optimization now works for columns with COLLATE NOCASE
3. ORDER BY and GROUP BY now use bounded memory
4. Added support for COUNT(DISTINCT expr)
5. Change the way SUM() handles NULL values in order to comply with the SQL standard
6. Use fdatasync() instead of fsync() where possible in order to speed up commits slightly
7. Use of the CROSS keyword in a join turns off the table reordering optimization
8. Added the experimental and undocumented EXPLAIN QUERY PLAN capability
9. Use the unicode API in Windows
### 2005-08-27 (3.2.5)
1. Fix a bug effecting DELETE and UPDATE statements that changed more than 40960 rows.
2. Change the makefile so that it no longer requires GNUmake extensions
3. Fix the --enable-threadsafe option on the configure script
4. Fix a code generator bug that occurs when the left-hand side of an IN operator is constant and the right-hand side is a SELECT statement
5. The PRAGMA synchronous=off statement now disables syncing of the master journal file in addition to the normal rollback journals
### 2005-08-24 (3.2.4)
1. Fix a bug introduced in the previous release that can cause a segfault while generating code for complex WHERE clauses.
2. Allow floating point literals to begin or end with a decimal point.
### 2005-08-21 (3.2.3)
1. Added support for the CAST operator
2. Tcl interface allows BLOB values to be transferred to user-defined functions
3. Added the "transaction" method to the Tcl interface
4. Allow the DEFAULT value of a column to call functions that have constant operands
5. Added the ANALYZE command for gathering statistics on indices and using those statistics when picking an index in the optimizer
6. Remove the limit (formerly 100) on the number of terms in the WHERE clause
7. The right-hand side of the IN operator can now be a list of expressions instead of just a list of constants
8. Rework the optimizer so that it is able to make better use of indices
9. The order of tables in a join is adjusted automatically to make better use of indices
10. The IN operator is now a candidate for optimization even if the left-hand side is not the left-most term of the index. Multiple IN operators can be used with the same index.
11. WHERE clause expressions using BETWEEN and OR are now candidates for optimization
12. Added the "case_sensitive_like" pragma and the SQLITE_CASE_SENSITIVE_LIKE compile-time option to set its default value to "on".
13. Use indices to help with GLOB expressions and LIKE expressions too when the case_sensitive_like pragma is enabled
14. Added support for grave-accent quoting for compatibility with MySQL
15. Improved test coverage
16. Dozens of minor bug fixes
### 2005-06-12 (3.2.2)
1. Added the sqlite3_db_handle() API
2. Added the sqlite3_get_autocommit() API
3. Added a REGEXP operator to the parser. There is no function to back up this operator in the standard build but users can add their own using sqlite3_create_function()
4. Speed improvements and library footprint reductions.
5. Fix byte alignment problems on 64-bit architectures.
6. Many, many minor bug fixes and documentation updates.
### 2005-03-29 (3.2.1)
1. Fix a memory allocation error in the new ADD COLUMN comment.
2. Documentation updates
### 2005-03-21 (3.2.0)
1. Added support for ALTER TABLE ADD COLUMN.
2. Added support for the "T" separator in ISO-8601 date/time strings.
3. Improved support for Cygwin.
4. Numerous bug fixes and documentation updates.
### 2005-03-17 (3.1.6)
1. Fix a bug that could cause database corruption when inserting record into tables with around 125 columns.
2. sqlite3_step() is now much more likely to invoke the busy handler and less likely to return SQLITE_BUSY.
3. Fix memory leaks that used to occur after a malloc() failure.
### 2005-03-11 (3.1.5)
1. The ioctl on Mac OS X to control syncing to disk is F_FULLFSYNC, not F_FULLSYNC. The previous release had it wrong.
### 2005-03-11 (3.1.4)
1. Fix a bug in autovacuum that could cause database corruption if a CREATE UNIQUE INDEX fails because of a constraint violation. This problem only occurs if the new autovacuum feature introduced in version 3.1 is turned on.
2. The F_FULLSYNC ioctl (currently only supported on Mac OS X) is disabled if the synchronous pragma is set to something other than "full".
3. Add additional forward compatibility to the future version 3.2 database file format.
4. Fix a bug in WHERE clauses of the form (rowid\<'2')
5. New [SQLITE_OMIT\_...](compile.md#omitfeatures) compile-time options added
6. Updates to the man page
7. Remove the use of strcasecmp() from the shell
8. Windows DLL exports symbols Tclsqlite_Init and Sqlite_Init
### 2005-02-19 (3.1.3)
1. Fix a problem with VACUUM on databases from which tables containing AUTOINCREMENT have been dropped.
2. Add forward compatibility to the future version 3.2 database file format.
3. Documentation updates
### 2005-02-15 (3.1.2)
1. Fix a bug that can lead to database corruption if there are two open connections to the same database and one connection does a VACUUM and the second makes some change to the database.
2. Allow "?" parameters in the LIMIT clause.
3. Fix VACUUM so that it works with AUTOINCREMENT.
4. Fix a race condition in AUTOVACUUM that can lead to corrupt databases
5. Add a numeric version number to the sqlite3.h include file.
6. Other minor bug fixes and performance enhancements.
### 2005-02-15 (2.8.16)
1. Fix a bug that can lead to database corruption if there are two open connections to the same database and one connection does a VACUUM and the second makes some change to the database.
2. Correctly handle quoted names in CREATE INDEX statements.
3. Fix a naming conflict between sqlite.h and sqlite3.h.
4. Avoid excess heap usage when copying expressions.
5. Other minor bug fixes.
### 2005-02-01 (3.1.1 BETA)
1. Automatic caching of prepared statements in the TCL interface
2. ATTACH and DETACH as well as some other operations cause existing prepared statements to expire.
3. Numerous minor bug fixes
### 2005-01-21 (3.1.0 ALPHA)
1. Autovacuum support added
2. CURRENT_TIME, CURRENT_DATE, and CURRENT_TIMESTAMP added
3. Support for the EXISTS clause added.
4. Support for correlated subqueries added.
5. Added the ESCAPE clause on the LIKE operator.
6. Support for ALTER TABLE ... RENAME TABLE ... added
7. AUTOINCREMENT keyword supported on INTEGER PRIMARY KEY
8. Many SQLITE_OMIT\_ macros inserts to omit features at compile-time and reduce the library footprint.
9. The REINDEX command was added.
10. The engine no longer consults the main table if it can get all the information it needs from an index.
11. Many nuisance bugs fixed.
### 2004-10-12 (3.0.8)
1. Add support for DEFERRED, IMMEDIATE, and EXCLUSIVE transactions.
2. Allow new user-defined functions to be created when there are already one or more precompiled SQL statements.
3.
4. Fix portability problems for MinGW/MSYS.
5. Fix a byte alignment problem on 64-bit Sparc machines.
6. Fix the ".import" command of the shell so that it ignores \r characters at the end of lines.
7. The "csv" mode option in the shell puts strings inside double-quotes.
8. Fix typos in documentation.
9. Convert array constants in the code to have type "const".
10. Numerous code optimizations, specially optimizations designed to make the code footprint smaller.
### 2004-09-18 (3.0.7)
1. The BTree module allocates large buffers using malloc() instead of off of the stack, in order to play better on machines with limited stack space.
2. Fixed naming conflicts so that versions 2.8 and 3.0 can be linked and used together in the same ANSI-C source file.
3. New interface: sqlite3_bind_parameter_index()
4. Add support for wildcard parameters of the form: "?nnn"
5. Fix problems found on 64-bit systems.
6. Removed encode.c file (containing unused routines) from the version 3.0 source tree.
7. The sqlite3_trace() callbacks occur before each statement is executed, not when the statement is compiled.
8. Makefile updates and miscellaneous bug fixes.
### 2004-09-02 (3.0.6 beta)
1. Better detection and handling of corrupt database files.
2. The sqlite3_step() interface returns SQLITE_BUSY if it is unable to commit a change because of a lock
3. Combine the implementations of LIKE and GLOB into a single pattern-matching subroutine.
4. Miscellaneous code size optimizations and bug fixes
### 2004-08-29 (3.0.5 beta)
1. Support for ":AAA" style bind parameter names.
2. Added the new sqlite3_bind_parameter_name() interface.
3. Support for TCL variable names embedded in SQL statements in the TCL bindings.
4. The TCL bindings transfer data without necessarily doing a conversion to a string.
5. The database for TEMP tables is not created until it is needed.
6. Add the ability to specify an alternative temporary file directory using the "sqlite_temp_directory" global variable.
7. A compile-time option (SQLITE_BUSY_RESERVED_LOCK) causes the busy handler to be called when there is contention for a RESERVED lock.
8. Various bug fixes and optimizations
### 2004-08-09 (3.0.4 beta)
1. CREATE TABLE and DROP TABLE now work correctly as prepared statements.
2. Fix a bug in VACUUM and UNIQUE indices.
3. Add the ".import" command to the command-line shell.
4. Fix a bug that could cause index corruption when an attempt to delete rows of a table is blocked by a pending query.
5. Library size optimizations.
6. Other minor bug fixes.
### 2004-07-22 (2.8.15)
1. This is a maintenance release only. Various minor bugs have been fixed and some portability enhancements are added.
### 2004-07-22 (3.0.3 beta)
1. The second beta release for SQLite 3.0.
2. Add support for "PRAGMA page_size" to adjust the page size of the database.
3. Various bug fixes and documentation updates.
### 2004-06-30 (3.0.2 beta)
1. The first beta release for SQLite 3.0.
### 2004-06-22 (3.0.1 alpha)
1. **\*\*\* Alpha Release - Research And Testing Use Only \*\*\***
2. Lots of bug fixes.
### 2004-06-18 (3.0.0 alpha)
1. **\*\*\* Alpha Release - Research And Testing Use Only \*\*\***
2. Support for internationalization including UTF-8, UTF-16, and user defined collating sequences.
3. New file format that is 25% to 35% smaller for typical use.
4. Improved concurrency.
5. Atomic commits for ATTACHed databases.
6. Remove cruft from the APIs.
7. BLOB support.
8. 64-bit rowids.
9. [More information](version3.md).
### 2004-06-09 (2.8.14)
1. Fix the min() and max() optimizer so that it works when the FROM clause consists of a subquery.
2. Ignore extra whitespace at the end of "." commands in the shell.
3. Bundle sqlite_encode_binary() and sqlite_decode_binary() with the library.
4. The TEMP_STORE and DEFAULT_TEMP_STORE pragmas now work.
5. Code changes to compile cleanly using OpenWatcom.
6. Fix VDBE stack overflow problems with INSTEAD OF triggers and NULLs in IN operators.
7. Add the global variable sqlite_temp_directory which if set defines the directory in which temporary files are stored.
8. sqlite_interrupt() plays well with VACUUM.
9. Other minor bug fixes.
### 2004-03-08 (2.8.13)
1. Refactor parts of the code in order to make the code footprint smaller. The code is now also a little bit faster.
2. sqlite_exec() is now implemented as a wrapper around sqlite_compile() and sqlite_step().
3. The built-in min() and max() functions now honor the difference between NUMERIC and TEXT datatypes. Formerly, min() and max() always assumed their arguments were of type NUMERIC.
4. New HH:MM:SS modifier to the built-in date/time functions.
5. Experimental sqlite_last_statement_changes() API added. Fixed the last_insert_rowid() function so that it works correctly with triggers.
6. Add functions prototypes for the database encryption API.
7. Fix several nuisance bugs.
### 2004-02-08 (2.8.12)
1. Fix a bug that will might corrupt the rollback journal if a power failure or external program halt occurs in the middle of a COMMIT. The corrupt journal can lead to database corruption when it is rolled back.
2. Reduce the size and increase the speed of various modules, especially the virtual machine.
3. Allow "\| HWACI By: Print Name: Title:
|
COMPANY By: Print Name: Title:
|
The issues arise from the properties and utilization of the two data/control channels between the above three blocks.
## Channel Traffic Volume
The "API Call" channel carries less information than the "File I/O" channel. API calls to submit queries or specify data modification normally require substantially fewer bits to be passed back and forth than are transferred to/from the database file to store or find the data. Query result retrieval will normally require much more file traffic than API traffic because the data to be returned is rarely to be found without reading unrequested data.
## Channel Bandwidth
The API Call channel operates at processor main memory speeds (Giga-words/second), with data often passed by reference (and so not copied.) In contrast, even the fastest File I/O channels are slower. They require the data to be copied, usually over a medium requiring bit-serialization. For spinning magnetic media, transfers await platter rotation and head movement, then are limited by spin velocity.
When the File I/O channel includes a network connection, (in addition to some genuine File I/O at its far end), additional slowness is imposed. Even where raw transfer rate does not limit bandwidth, the traffic must still be packetized and buffered at both ends. Additional layers of I/O handlers add scheduling delays. However, slowed transfers are the least significant issue with network filesystems.
## Channel Reliability
The "API Call" channel is highly reliable, to the extent that error rates are unstated and ignored as negligible. The channel fails only when the system loses power (excepting meteorites, etc.)
The "File I/O" channel, when it directly reaches a local storage device, is also highly reliable. (Spinning storage MTBF exceeds 1 million hours, and NVRAM lasts longer.) Local devices also have a characteristic which is critical for enabling database management software to be designed to ensure [ACID](transactional.md) behavior: When all process writes to the device have completed, (when POSIX fsync() or Windows FlushFileBuffers() calls return), the filesystem then either has stored the "written" data or will do so before storing any subsequently written data.
When network filesystem apparatus and software layers are interposed between filesystem clients and a filesystem over an actual storage device, significant sources of failure and misbehavior are introduced. While network data transfers are error-checked well, transfer packets do not all reliably arrive at their destination once sent. Some packets are clobbered by other packets and must be resent. Under packet clobbering conditions, repeated retries can impose delays exceeding what is needed for similar data to reach local storage. Some portions of what a client writes can end up stored out of time order relative to other portions written.
Because of the disordering and outright data loss which occur in network filesystem writes, it is critical that sets of file writes can be accurately known to be done before a subsequent set of file writes begins. This assurance is obtained by use of robustly designed and correctly implemented fsync() (or equivalent) OS functions. Unfortunately for some applications, network filesystem sync operation can be less robust than local filesystem sync. Attaining robust sync in the face of network packet transport errors is hard, and safeguards are sometimes relaxed in favor of performance.
A similar hazard arises with file locking in network filesystems. SQLite relies on exclusive locks for write operations, and those have been known to operate incorrectly for some network filesystems. This has led to database corruption. That may happen again as the designers of such change their implementation to suit more common use cases.
The bottom line is that network filesystem sync and locking reliability vary among implementations and installations. The design assumptions upon which it relies may hold more true where an application is tested than where it is relied upon. **Rely upon it at your (and your customers') peril.** See [How To Corrupt Your Database Files](lockingv3.md#how_to_corrupt).
# Performance and Reliability Issues
From the above diagram and discussion, it is obvious that performance (aka "speed") is degraded by insertion of a network link into one of the two channels. Consideration of relative traffic volumes between the API Call channel and the File I/O channel reveals that such insertion will have less performance impact at the API Call channel.
Consideration of reliability impact is easier, with a clearer outcome: Inserting a network link into the API Call channel may also result in call failures at times. But if the Client Application has bothered to use SQL/SQLite transactions properly, such failures will only cause a transaction to fail and be rolled back, without compromising the integrity of the data. In contrast, if the network link is inserted into the File I/O channel, transactions may fail (as for the API Call insertion) but with the additional effect that the remote database is corrupted.
These network unreliability issues can be mitigated, completely or to an acceptable degree, by using SQLite in rollback mode. However, the SQLite library is not tested in across-a-network scenarios, nor is that reasonably possible. Hence, use of a remote database is done **at the user's risk**.
# Recommendations
Generally, if your data is separated from the application by a network, you want to use a client/server database. This is due to the fact that the database engine acts as a bandwidth-reducing filter on the database traffic.
If your data is separated from the application by a network, you want the low-traffic link to be across the network, not the high-traffic link. This means that the database engine needs to be on the same machine as the database itself. Such is the case with a client/server database like PostgreSQL. SQLite is different in that the database engine runs on the same machine as the application, which forces the higher-traffic link to traverse the network in remote database scenarios. That normally results in lower performance.
Network filesystems do not support the ability to do simultaneous reads and writes while at the same time keeping the database consistent. So if you have multiple clients on multiple different machines which need to do simultaneous database reads and writes, you have these choices:
1\. Use a client/server database engine. [PostgreSQL](https://postgresql.org/) is an excellent choice. A variation of this is:
2\. Host an SQLite database in [WAL mode](wal.md), but do all reads and writes from processes on the same machine that stores the database file. Implement a proxy that runs on the database machine that relays read/write requests from remote machines.
3\. Use SQLite in [rollback mode](isolation.md). This means you can have multiple simultaneous readers or one writer, but not simultaneous readers and writers.
Application programmers should be cognizant of the possibility that their application's users will elect to use a remote database if they can do so. Unless one of the above choices has been effected, or one at a time, exclusive access is used, a programmer should consider blocking that election unless reliability is of little importance.
# Summary
Choose the technology that is right for you and your customers. If your data lives on a different machine from your application, then you should consider a client/server database. SQLite is designed for situations where the data and application coexist on the same machine. SQLite can still be made to work in many remote database situations, but a client/server solution will usually work better in that scenario.
---
# SQLite Pro Support
*Sección: Guides | Origen: https://www.sqlite.org/prosupport.html*
# Professional Support & Extension Products
## Support ([details below](#detail))
| 1. | Public Forum. Help and advice from a world-wide community of experts. | Free | More Info Recent Posts |
| 2. | Annual Maintenance Subscription. Private, expert email advice from the developers of SQLite. | $1500/year | More Info Purchase |
| 3. | Technical Support. High-priority email and phone support directly from the SQLite developers. Guaranteed response time available as an option. | $8K-85K/year | More Info Request A Quote |
| 4. | SQLite Consortium Membership. Premium enterprise support including on-site visits and access to all proprietary extensions and test suites. | $150K/year | More Info Request A Quote |
| 5. | SQLite License. Warranty of title and perpetual right-to-use for the SQLite source code. | $6000 one time fee | More Info Purchase |
| 6. | SQLite Encryption Extension (SEE) source code. A drop-in replacement for public-domain SQLite C source code that has the added ability to read/write AES-encrypted databases. | $2000 one time fee | More Info Purchase |
| 7. | Compressed And Encrypted Read-Only Database (CEROD). A drop-in replacement for public-domain SQLite source code that has the added ability to read database that has been both compressed and encrypted. | $2000 one time fee | More Info Buy Now! |
| 8. | The ZIPVFS Read/Write Compressed Database Extension. The ZIPVFS extension automatically compresses and encrypts your data as it is written to disk, and decompressed and decrypts it while reading. | $4000 one time fee | More Info Buy Now! |
| 9. | TH3 Testing Support. The TH3 test harness is an aviation-grade test suite for SQLite. SQLite developers can run TH3 on specialized hardware and/or using specialized compile-time options, according to customer specification, either remotely or on customer premises. Pricing for this services is on a case-by-case basis depending on requirements. | call | More Info Request A Quote |
\
Celebrating the SQLite "π release" with a home-baked pie.
2. Added support for [WITHOUT ROWID virtual tables](../vtab.md#worid).
3. Improved the query planner so that the [OR optimization](../optoverview.md#or_opt) can be used on [virtual tables](../vtab.md) even if one or more of the disjuncts use the [LIKE](../lang_expr.md#like), [GLOB](../lang_expr.md#glob), [REGEXP](../lang_expr.md#regexp), [MATCH](../lang_expr.md#match) operators.
4. Added the [CSV virtual table](../csv.md) for reading [RFC 4180](https://www.ietf.org/rfc/rfc4180.txt) formatted comma-separated value files.
5. Added the [carray() table-valued function](../carray.md) extension.
6. Enabled [persistent loadable extensions](../loadext.md#persist) using the new [SQLITE_OK_LOAD_PERMANENTLY](../rescode.md#ok_load_permanently) return code from the extension entry point.
7. Added the [SQLITE_DBSTATUS_CACHE_USED_SHARED](../c3ref/c_dbstatus_options.md#sqlitedbstatuscacheusedshared) option to [sqlite3_db_status()](../c3ref/db_status.md).
8. Add the [vfsstat.c](https://sqlite.org/src/artifact?ci=trunk&filename=ext/misc/vfsstat.c) loadable extension - a VFS shim that measures I/O together with an [eponymous virtual table](../vtab.md#epovtab) that provides access to the measurements.
9. Improved algorithm for running queries with both an ORDER BY and a LIMIT where only the inner-most loop naturally generates rows in the correct order.
10. Enhancements to [Lemon parser generator](../lemon.md), so that it generates a faster parser.
11. The [PRAGMA compile_options](../pragma.md#pragma_compile_options) command now attempts to show the version number of the compiler that generated the library.
12. Enhance [PRAGMA table_info](../pragma.md#pragma_table_info) so that it provides information about [eponymous virtual tables](../vtab.md#epovtab).
13. Added the "win32-none" VFS, analogous to the "unix-none" VFS, that works like the default "win32" VFS except that it ignores all file locks.
14. The query planner uses a full scan of a [partial index](../partialindex.md) instead of a full scan of the main table, in cases where that makes sense.
15. Allow [table-valued functions](../vtab.md#tabfunc2) to appear on the right-hand side of an [IN operator](../lang_expr.md#in_op).
16. Created the [dbhash.exe](../dbhash.md) command-line utility.
17. Added two new C-language interfaces: [sqlite3_expanded_sql()](../c3ref/expanded_sql.md) and [sqlite3_trace_v2()](../c3ref/trace_v2.md). These new interfaces subsume the functions of [sqlite3_trace()](../c3ref/profile.md) and [sqlite3_profile()](../c3ref/profile.md) which are now deprecated.
18. Added the [json_quote()](../json1.md#jquote) SQL function to [the json1 extension](../json1.md).
19. Disable the [authorizer callback](../c3ref/set_authorizer.md) while reparsing the schema.
20. Added the [SQLITE_ENABLE_UNKNOWN_SQL_FUNCTION](../compile.md#enable_unknown_sql_function) compile-time option and turned that option on by default when building the [command-line shell](../cli.md).
**Bug Fixes:**
21. Fix the [ALTER TABLE](../lang_altertable.md) command so that it does not corrupt [descending indexes](../lang_createindex.md#descidx) when adding a column to a [legacy file format](../pragma.md#pragma_legacy_file_format) database. Ticket [f68bf68513a1c15f](https://sqlite.org/src/info/f68bf68513a1c15f)
22. Fix a NULL-pointer dereference/crash that could occurs when a transitive WHERE clause references a non-existent collating sequence. Ticket [e8d439c77685eca6](https://sqlite.org/src/info/e8d439c77685eca6).
23. Improved the cost estimation for an index scan which includes a WHERE clause that can be partially or fully evaluated using columns in the index and without having to do a table lookup. This fixes a performance regression that occurred for some obscure queries following the ORDER BY LIMIT optimization introduced in [version 3.12.0](../releaselog/3_12_0.md).
**Hashes:**
24. SQLITE_SOURCE_ID: "2016-08-08 13:40:27 d5e98057028abcf7217d0d2b2e29bbbcdf09d6de"
25. SHA1 for sqlite3.c: 234a3275d03a287434ace3ccdf1afb208e6b0e92
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.14.1 On 2016-08-11
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_14_1.html*
## SQLite Release 3.14.1 On 2016-08-11
**Prior changes from version 3.14 (2016-08-08):**
1. \
Celebrating the SQLite "π release" with a home-baked pie.
2. Added support for [WITHOUT ROWID virtual tables](../vtab.md#worid).
3. Improved the query planner so that the [OR optimization](../optoverview.md#or_opt) can be used on [virtual tables](../vtab.md) even if one or more of the disjuncts use the [LIKE](../lang_expr.md#like), [GLOB](../lang_expr.md#glob), [REGEXP](../lang_expr.md#regexp), [MATCH](../lang_expr.md#match) operators.
4. Added the [CSV virtual table](../csv.md) for reading [RFC 4180](https://www.ietf.org/rfc/rfc4180.txt) formatted comma-separated value files.
5. Added the [carray() table-valued function](../carray.md) extension.
6. Enabled [persistent loadable extensions](../loadext.md#persist) using the new [SQLITE_OK_LOAD_PERMANENTLY](../rescode.md#ok_load_permanently) return code from the extension entry point.
7. Added the [SQLITE_DBSTATUS_CACHE_USED_SHARED](../c3ref/c_dbstatus_options.md#sqlitedbstatuscacheusedshared) option to [sqlite3_db_status()](../c3ref/db_status.md).
8. Add the [vfsstat.c](https://sqlite.org/src/artifact?ci=trunk&filename=ext/misc/vfsstat.c) loadable extension - a VFS shim that measures I/O together with an [eponymous virtual table](../vtab.md#epovtab) that provides access to the measurements.
9. Improved algorithm for running queries with both an ORDER BY and a LIMIT where only the inner-most loop naturally generates rows in the correct order.
10. Enhancements to [Lemon parser generator](../lemon.md), so that it generates a faster parser.
11. The [PRAGMA compile_options](../pragma.md#pragma_compile_options) command now attempts to show the version number of the compiler that generated the library.
12. Enhance [PRAGMA table_info](../pragma.md#pragma_table_info) so that it provides information about [eponymous virtual tables](../vtab.md#epovtab).
13. Added the "win32-none" VFS, analogous to the "unix-none" VFS, that works like the default "win32" VFS except that it ignores all file locks.
14. The query planner uses a full scan of a [partial index](../partialindex.md) instead of a full scan of the main table, in cases where that makes sense.
15. Allow [table-valued functions](../vtab.md#tabfunc2) to appear on the right-hand side of an [IN operator](../lang_expr.md#in_op).
16. Created the [dbhash.exe](../dbhash.md) command-line utility.
17. Added two new C-language interfaces: [sqlite3_expanded_sql()](../c3ref/expanded_sql.md) and [sqlite3_trace_v2()](../c3ref/trace_v2.md). These new interfaces subsume the functions of [sqlite3_trace()](../c3ref/profile.md) and [sqlite3_profile()](../c3ref/profile.md) which are now deprecated.
18. Added the [json_quote()](../json1.md#jquote) SQL function to [the json1 extension](../json1.md).
19. Disable the [authorizer callback](../c3ref/set_authorizer.md) while reparsing the schema.
20. Added the [SQLITE_ENABLE_UNKNOWN_SQL_FUNCTION](../compile.md#enable_unknown_sql_function) compile-time option and turned that option on by default when building the [command-line shell](../cli.md).
**Bug Fixes:**
21. Fix the [ALTER TABLE](../lang_altertable.md) command so that it does not corrupt [descending indexes](../lang_createindex.md#descidx) when adding a column to a [legacy file format](../pragma.md#pragma_legacy_file_format) database. Ticket [f68bf68513a1c15f](https://sqlite.org/src/info/f68bf68513a1c15f)
22. Fix a NULL-pointer dereference/crash that could occurs when a transitive WHERE clause references a non-existent collating sequence. Ticket [e8d439c77685eca6](https://sqlite.org/src/info/e8d439c77685eca6).
23. Improved the cost estimation for an index scan which includes a WHERE clause that can be partially or fully evaluated using columns in the index and without having to do a table lookup. This fixes a performance regression that occurred for some obscure queries following the ORDER BY LIMIT optimization introduced in [version 3.12.0](../releaselog/3_12_0.md).
**Changes in this specific patch release, version 3.14.1 (2016-08-11):**
1. A performance enhancement to the page-cache "truncate" operation reduces [COMMIT](../lang_transaction.md) time by dozens of milliseconds on systems with a large [page cache](../pragma.md#pragma_cache_size).
2. Fix to the --rbu option of [sqldiff](../sqldiff.md).
**Hashes:**
3. SQLITE_SOURCE_ID: "2016-08-11 18:53:32 a12d8059770df4bca59e321c266410344242bf7b"
4. SHA1 for sqlite3.c: d545b24892278272ce4e40e0567d69c8babf12ea
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.14.2 On 2016-09-12
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_14_2.html*
## SQLite Release 3.14.2 On 2016-09-12
**Prior changes from version 3.14 (2016-08-08):**
1. \
Celebrating the SQLite "π release" with a home-baked pie.
2. Added support for [WITHOUT ROWID virtual tables](../vtab.md#worid).
3. Improved the query planner so that the [OR optimization](../optoverview.md#or_opt) can be used on [virtual tables](../vtab.md) even if one or more of the disjuncts use the [LIKE](../lang_expr.md#like), [GLOB](../lang_expr.md#glob), [REGEXP](../lang_expr.md#regexp), [MATCH](../lang_expr.md#match) operators.
4. Added the [CSV virtual table](../csv.md) for reading [RFC 4180](https://www.ietf.org/rfc/rfc4180.txt) formatted comma-separated value files.
5. Added the [carray() table-valued function](../carray.md) extension.
6. Enabled [persistent loadable extensions](../loadext.md#persist) using the new [SQLITE_OK_LOAD_PERMANENTLY](../rescode.md#ok_load_permanently) return code from the extension entry point.
7. Added the [SQLITE_DBSTATUS_CACHE_USED_SHARED](../c3ref/c_dbstatus_options.md#sqlitedbstatuscacheusedshared) option to [sqlite3_db_status()](../c3ref/db_status.md).
8. Add the [vfsstat.c](https://sqlite.org/src/artifact?ci=trunk&filename=ext/misc/vfsstat.c) loadable extension - a VFS shim that measures I/O together with an [eponymous virtual table](../vtab.md#epovtab) that provides access to the measurements.
9. Improved algorithm for running queries with both an ORDER BY and a LIMIT where only the inner-most loop naturally generates rows in the correct order.
10. Enhancements to [Lemon parser generator](../lemon.md), so that it generates a faster parser.
11. The [PRAGMA compile_options](../pragma.md#pragma_compile_options) command now attempts to show the version number of the compiler that generated the library.
12. Enhance [PRAGMA table_info](../pragma.md#pragma_table_info) so that it provides information about [eponymous virtual tables](../vtab.md#epovtab).
13. Added the "win32-none" VFS, analogous to the "unix-none" VFS, that works like the default "win32" VFS except that it ignores all file locks.
14. The query planner uses a full scan of a [partial index](../partialindex.md) instead of a full scan of the main table, in cases where that makes sense.
15. Allow [table-valued functions](../vtab.md#tabfunc2) to appear on the right-hand side of an [IN operator](../lang_expr.md#in_op).
16. Created the [dbhash.exe](../dbhash.md) command-line utility.
17. Added two new C-language interfaces: [sqlite3_expanded_sql()](../c3ref/expanded_sql.md) and [sqlite3_trace_v2()](../c3ref/trace_v2.md). These new interfaces subsume the functions of [sqlite3_trace()](../c3ref/profile.md) and [sqlite3_profile()](../c3ref/profile.md) which are now deprecated.
18. Added the [json_quote()](../json1.md#jquote) SQL function to [the json1 extension](../json1.md).
19. Disable the [authorizer callback](../c3ref/set_authorizer.md) while reparsing the schema.
20. Added the [SQLITE_ENABLE_UNKNOWN_SQL_FUNCTION](../compile.md#enable_unknown_sql_function) compile-time option and turned that option on by default when building the [command-line shell](../cli.md).
**Bug Fixes:**
21. Fix the [ALTER TABLE](../lang_altertable.md) command so that it does not corrupt [descending indexes](../lang_createindex.md#descidx) when adding a column to a [legacy file format](../pragma.md#pragma_legacy_file_format) database. Ticket [f68bf68513a1c15f](https://sqlite.org/src/info/f68bf68513a1c15f)
22. Fix a NULL-pointer dereference/crash that could occurs when a transitive WHERE clause references a non-existent collating sequence. Ticket [e8d439c77685eca6](https://sqlite.org/src/info/e8d439c77685eca6).
23. Improved the cost estimation for an index scan which includes a WHERE clause that can be partially or fully evaluated using columns in the index and without having to do a table lookup. This fixes a performance regression that occurred for some obscure queries following the ORDER BY LIMIT optimization introduced in [version 3.12.0](../releaselog/3_12_0.md).
**Prior changes from version 3.14.1 (2016-08-11):**
1. A performance enhancement to the page-cache "truncate" operation reduces [COMMIT](../lang_transaction.md) time by dozens of milliseconds on systems with a large [page cache](../pragma.md#pragma_cache_size).
2. Fix to the --rbu option of [sqldiff](../sqldiff.md).
**Changes in this specific patch release, version 3.14.2 (2016-09-12):**
1. Improved support for using the STDCALL calling convention in winsqlite3.dll.
2. Fix the [sqlite3_trace_v2()](../c3ref/trace_v2.md) interface so that it is disabled if either the callback or the mask arguments are zero, in accordance with the documentation.
3. Fix commenting errors and improve the comments generated on [EXPLAIN](../lang_explain.md) listings when the [-DSQLITE_ENABLE_EXPLAIN_COMMENTS](../compile.md#enable_explain_comments) compile-time option is used.
4. Fix the ".read" command in the [command-line shell](../cli.md) so that it understands that its input is not interactive.
5. Correct affinity computations for a SELECT on the RHS of an IN operator. Fix for ticket [199df4168c](https://sqlite.org/src/info/199df4168c).
6. The ORDER BY LIMIT optimization is not valid unless the inner-most IN operator loop is actually used by the query plan. Fix for ticket [0c4df46116e90f92](https://sqlite.org/src/info/0c4df46116e90f92).
7. Fix an internal code generator problem that was causing some [DELETE](../lang_delete.md) operations to no-op. Ticket [ef360601](https://sqlite.org/src/info/ef360601)
**Hashes:**
8. SQLITE_SOURCE_ID: "2016-09-12 18:50:49 29dbef4b8585f753861a36d6dd102ca634197bd6"
9. SHA1 for sqlite3.c: bcc4a1989db45e7f223191f2d0f66c1c28946383
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.15.0 On 2016-10-14
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_15_0.html*
## SQLite Release 3.15.0 On 2016-10-14
1. Added support for [row values](../rowvalue.md).
2. Allow [deterministic SQL functions](../deterministic.md) in the WHERE clause of a [partial index](../partialindex.md).
3. Added the "[modeof=*filename*](../uri.md#urimodeof)" URI parameter on the unix VFS
4. Added support for [SQLITE_DBCONFIG_MAINDBNAME](../c3ref/c_dbconfig_defensive.md#sqlitedbconfigmaindbname).
5. Added the ability to [VACUUM](../lang_vacuum.md) an [ATTACH-ed](../lang_attach.md) database.
6. Enhancements to the [command-line shell](../cli.md):
1. Add the ".testcase" and ".check" [dot-commands](../cli.md#dotcmd).
2. Added the --new option to the ".open" dot-command, causing any prior content in the database to be purged prior to opening.
7. Enhance the [fts5vocab](../fts5.md#the_fts5vocab_virtual_table_module) virtual table to handle "ORDER BY term" efficiently.
8. Miscellaneous micro-optimizations reduce CPU usage by more than 7% on common workloads. Most optimization in this release has been on the front-end ([sqlite3_prepare_v2()](../c3ref/prepare.md)).
**Bug Fixes:**
9. The multiply operator now correctly detects 64-bit integer overflow and promotes to floating point in all corner-cases. Fix for ticket [1ec41379c9c1e400](https://sqlite.org/src/info/1ec41379c9c1e400).
10. Correct handling of columns with redundant unique indexes when those columns are used on the LHS of an [IN operator](../lang_expr.md#in_op). Fix for ticket [0eab1ac759](https://sqlite.org/src/info/0eab1ac759).
11. Skip NULL entries on range queries in [indexes on expressions](../expridx.md). Fix for ticket [4baa46491212947](https://sqlite.org/src/tktview/4baa46491212947).
12. Ensure that the [AUTOINCREMENT](../autoinc.md) counters in the sqlite_sequence table are initialized doing "Xfer Optimization" on "INSERT ... SELECT" statements. Fix for ticket [7b3328086a5c116c](https://sqlite.org/src/info/7b3328086a5c116c).
13. Make sure the ORDER BY LIMIT optimization (from check-in [559733b09e](https://sqlite.org/src/info/559733b09e9630fa)) works with IN operators on INTEGER PRIMARY KEYs. Fix for ticket [96c1454c](https://sqlite.org/src/info/96c1454cbfd9509)
**Hashes:**
14. SQLITE_SOURCE_ID: "2016-10-14 10:20:30 707875582fcba352b4906a595ad89198d84711d8"
15. SHA1 for sqlite3.c: fba106f8f6493c66eeed08a2dfff0907de54ae76
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.15.1 On 2016-11-04
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_15_1.html*
## SQLite Release 3.15.1 On 2016-11-04
**Prior changes from version 3.15.0 (2016-10-14):**
1. Added support for [row values](../rowvalue.md).
2. Allow [deterministic SQL functions](../deterministic.md) in the WHERE clause of a [partial index](../partialindex.md).
3. Added the "[modeof=*filename*](../uri.md#urimodeof)" URI parameter on the unix VFS
4. Added support for [SQLITE_DBCONFIG_MAINDBNAME](../c3ref/c_dbconfig_defensive.md#sqlitedbconfigmaindbname).
5. Added the ability to [VACUUM](../lang_vacuum.md) an [ATTACH-ed](../lang_attach.md) database.
6. Enhancements to the [command-line shell](../cli.md):
1. Add the ".testcase" and ".check" [dot-commands](../cli.md#dotcmd).
2. Added the --new option to the ".open" dot-command, causing any prior content in the database to be purged prior to opening.
7. Enhance the [fts5vocab](../fts5.md#the_fts5vocab_virtual_table_module) virtual table to handle "ORDER BY term" efficiently.
8. Miscellaneous micro-optimizations reduce CPU usage by more than 7% on common workloads. Most optimization in this release has been on the front-end ([sqlite3_prepare_v2()](../c3ref/prepare.md)).
**Bug Fixes:**
9. The multiply operator now correctly detects 64-bit integer overflow and promotes to floating point in all corner-cases. Fix for ticket [1ec41379c9c1e400](https://sqlite.org/src/info/1ec41379c9c1e400).
10. Correct handling of columns with redundant unique indexes when those columns are used on the LHS of an [IN operator](../lang_expr.md#in_op). Fix for ticket [0eab1ac759](https://sqlite.org/src/info/0eab1ac759).
11. Skip NULL entries on range queries in [indexes on expressions](../expridx.md). Fix for ticket [4baa46491212947](https://sqlite.org/src/tktview/4baa46491212947).
12. Ensure that the [AUTOINCREMENT](../autoinc.md) counters in the sqlite_sequence table are initialized doing "Xfer Optimization" on "INSERT ... SELECT" statements. Fix for ticket [7b3328086a5c116c](https://sqlite.org/src/info/7b3328086a5c116c).
13. Make sure the ORDER BY LIMIT optimization (from check-in [559733b09e](https://sqlite.org/src/info/559733b09e9630fa)) works with IN operators on INTEGER PRIMARY KEYs. Fix for ticket [96c1454c](https://sqlite.org/src/info/96c1454cbfd9509)
**Changes in this specific patch release, version 3.15.1 (2016-11-04):**
1. Added [SQLITE_FCNTL_WIN32_GET_HANDLE](../c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlwin32gethandle) file control opcode.
2. Fix the [VACUUM](../lang_vacuum.md) command so that it spills excess content to disk rather than holding everything in memory, and possible causing an out-of-memory error for larger database files. This fixes an issue introduced by version 3.15.0.
3. Fix a case (present since 3.8.0 - 2013-08-26) where OR-connected terms in the ON clause of a LEFT JOIN might cause incorrect results. Ticket [34a579141b2c5ac](https://sqlite.org/src/info/34a579141b2c5ac).
4. Fix a case where the use of [row values](../rowvalue.md) in the ON clause of a LEFT JOIN might cause incorrect results. Ticket [fef4bb4bd9185ec8f](https://sqlite.org/src/info/fef4bb4bd9185ec8f).
**Hashes:**
5. SQLITE_SOURCE_ID: "2016-11-04 12:08:49 1136863c76576110e710dd5d69ab6bf347c65e36"
6. SHA1 for sqlite3.c: e7c26a7be3e431dd06898f8d262c4ef240c07366
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.15.2 On 2016-11-28
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_15_2.html*
## SQLite Release 3.15.2 On 2016-11-28
**Prior changes from version 3.15.0 (2016-10-14):**
1. Added support for [row values](../rowvalue.md).
2. Allow [deterministic SQL functions](../deterministic.md) in the WHERE clause of a [partial index](../partialindex.md).
3. Added the "[modeof=*filename*](../uri.md#urimodeof)" URI parameter on the unix VFS
4. Added support for [SQLITE_DBCONFIG_MAINDBNAME](../c3ref/c_dbconfig_defensive.md#sqlitedbconfigmaindbname).
5. Added the ability to [VACUUM](../lang_vacuum.md) an [ATTACH-ed](../lang_attach.md) database.
6. Enhancements to the [command-line shell](../cli.md):
1. Add the ".testcase" and ".check" [dot-commands](../cli.md#dotcmd).
2. Added the --new option to the ".open" dot-command, causing any prior content in the database to be purged prior to opening.
7. Enhance the [fts5vocab](../fts5.md#the_fts5vocab_virtual_table_module) virtual table to handle "ORDER BY term" efficiently.
8. Miscellaneous micro-optimizations reduce CPU usage by more than 7% on common workloads. Most optimization in this release has been on the front-end ([sqlite3_prepare_v2()](../c3ref/prepare.md)).
**Bug Fixes:**
9. The multiply operator now correctly detects 64-bit integer overflow and promotes to floating point in all corner-cases. Fix for ticket [1ec41379c9c1e400](https://sqlite.org/src/info/1ec41379c9c1e400).
10. Correct handling of columns with redundant unique indexes when those columns are used on the LHS of an [IN operator](../lang_expr.md#in_op). Fix for ticket [0eab1ac759](https://sqlite.org/src/info/0eab1ac759).
11. Skip NULL entries on range queries in [indexes on expressions](../expridx.md). Fix for ticket [4baa46491212947](https://sqlite.org/src/tktview/4baa46491212947).
12. Ensure that the [AUTOINCREMENT](../autoinc.md) counters in the sqlite_sequence table are initialized doing "Xfer Optimization" on "INSERT ... SELECT" statements. Fix for ticket [7b3328086a5c116c](https://sqlite.org/src/info/7b3328086a5c116c).
13. Make sure the ORDER BY LIMIT optimization (from check-in [559733b09e](https://sqlite.org/src/info/559733b09e9630fa)) works with IN operators on INTEGER PRIMARY KEYs. Fix for ticket [96c1454c](https://sqlite.org/src/info/96c1454cbfd9509)
**Prior changes from version 3.15.1 (2016-11-04):**
1. Added [SQLITE_FCNTL_WIN32_GET_HANDLE](../c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlwin32gethandle) file control opcode.
2. Fix the [VACUUM](../lang_vacuum.md) command so that it spills excess content to disk rather than holding everything in memory, and possible causing an out-of-memory error for larger database files. This fixes an issue introduced by version 3.15.0.
3. Fix a case (present since 3.8.0 - 2013-08-26) where OR-connected terms in the ON clause of a LEFT JOIN might cause incorrect results. Ticket [34a579141b2c5ac](https://sqlite.org/src/info/34a579141b2c5ac).
4. Fix a case where the use of [row values](../rowvalue.md) in the ON clause of a LEFT JOIN might cause incorrect results. Ticket [fef4bb4bd9185ec8f](https://sqlite.org/src/info/fef4bb4bd9185ec8f).
**Changes in this specific patch release, version 3.15.2 (2016-11-28):**
1. Multiple bug fixes to the [row value](../rowvalue.md) logic that was introduced in version 3.15.0.
2. Fix a NULL pointer dereference in ATTACH/DETACH following a maliciously constructed syntax error. Ticket [2f1b168ab4d4844](https://sqlite.org/src/info/2f1b168ab4d4844).
3. Fix a crash that can occur following an out-of-memory condition in the built-in [instr()](../lang_corefunc.md#instr) function.
4. In the [JSON extension](../json1.md), fix the JSON validator so that it correctly rejects invalid backslash escapes within strings.
**Hashes:**
5. SQLITE_SOURCE_ID: "2016-11-28 19:13:37 bbd85d235f7037c6a033a9690534391ffeacecc8"
6. SHA1 for sqlite3.c: 06d77b42a3e70609f8d4bbb97caf53652f1082cb
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.16.0 On 2017-01-02
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_16_0.html*
## SQLite Release 3.16.0 On 2017-01-02
1. Uses 9% fewer CPU cycles. (See the [CPU performance measurement](../cpu.md) report for details on how this performance increase was computed.)
2. Added experimental support for [PRAGMA functions](../pragma.md#pragfunc).
3. Added the [SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE](../c3ref/c_dbconfig_defensive.md#sqlitedbconfignockptonclose) option to [sqlite3_db_config()](../c3ref/db_config.md).
4. Enhance the [date and time functions](../lang_datefunc.md) so that the 'unixepoch' modifier works for the full span of supported dates.
5. Changed the default configuration of the [lookaside memory allocator](../malloc.md#lookaside) from 500 slots of 128 bytes each into 125 slots of 512 bytes each.
6. Enhanced "WHERE x NOT NULL" [partial indexes](../partialindex.md) so that they are usable if the "x" column appears in a LIKE or GLOB operator.
7. Enhanced [sqlite3_interrupt()](../c3ref/interrupt.md) so that it interrupts [checkpoint](../wal.md#ckpt) operations that are in process.
8. Enhanced the [LIKE](../lang_expr.md#like) and [GLOB](../lang_expr.md#glob) matching algorithm to be faster for cases when the pattern contains multiple wildcards.
9. Added the [SQLITE_FCNTL_WIN32_GET_HANDLE](../c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlwin32gethandle) file control opcode.
10. Added ".mode quote" to the [command-line shell](../cli.md).
11. Added ".lint fkey-indexes" to the [command-line shell](../cli.md).
12. Added the [.imposter dot-command](../imposter.md#dotimposter) to the [command-line shell](../cli.md).
13. Added the [remember(V,PTR)](https://sqlite.org/src/file/ext/misc/remember.c) SQL function as a [loadable extension](../loadext.md).
14. Rename the [SQLITE_OMIT_BUILTIN_TEST](../compile.md#omit_builtin_test) compile-time option to [SQLITE_UNTESTABLE](../compile.md#untestable) to better reflect the implications of using it.
**Bug Fixes:**
15. Fix a long-standing bug in the query planner that caused incorrect results on a LEFT JOIN where the left-hand table is a subquery and the join constraint is a bare column name coming from the left-hand subquery. Ticket [2df0107b](https://sqlite.org/src/info/2df0107b).
16. Correctly handle the integer literal -0x8000000000000000 in the query planner.
**Hashes:**
17. SQLITE_SOURCE_ID: "2017-01-02 11:57:58 04ac0b75b1716541b2b97704f4809cb7ef19cccf"
18. SHA1 for sqlite3.c: e2920fb885569d14197c9b7958e6f1db573ee669
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.16.1 On 2017-01-03
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_16_1.html*
## SQLite Release 3.16.1 On 2017-01-03
**Prior changes from version 3.16.0 (2017-01-02):**
1. Uses 9% fewer CPU cycles. (See the [CPU performance measurement](../cpu.md) report for details on how this performance increase was computed.)
2. Added experimental support for [PRAGMA functions](../pragma.md#pragfunc).
3. Added the [SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE](../c3ref/c_dbconfig_defensive.md#sqlitedbconfignockptonclose) option to [sqlite3_db_config()](../c3ref/db_config.md).
4. Enhance the [date and time functions](../lang_datefunc.md) so that the 'unixepoch' modifier works for the full span of supported dates.
5. Changed the default configuration of the [lookaside memory allocator](../malloc.md#lookaside) from 500 slots of 128 bytes each into 125 slots of 512 bytes each.
6. Enhanced "WHERE x NOT NULL" [partial indexes](../partialindex.md) so that they are usable if the "x" column appears in a LIKE or GLOB operator.
7. Enhanced [sqlite3_interrupt()](../c3ref/interrupt.md) so that it interrupts [checkpoint](../wal.md#ckpt) operations that are in process.
8. Enhanced the [LIKE](../lang_expr.md#like) and [GLOB](../lang_expr.md#glob) matching algorithm to be faster for cases when the pattern contains multiple wildcards.
9. Added the [SQLITE_FCNTL_WIN32_GET_HANDLE](../c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlwin32gethandle) file control opcode.
10. Added ".mode quote" to the [command-line shell](../cli.md).
11. Added ".lint fkey-indexes" to the [command-line shell](../cli.md).
12. Added the [.imposter dot-command](../imposter.md#dotimposter) to the [command-line shell](../cli.md).
13. Added the [remember(V,PTR)](https://sqlite.org/src/file/ext/misc/remember.c) SQL function as a [loadable extension](../loadext.md).
14. Rename the [SQLITE_OMIT_BUILTIN_TEST](../compile.md#omit_builtin_test) compile-time option to [SQLITE_UNTESTABLE](../compile.md#untestable) to better reflect the implications of using it.
**Bug Fixes:**
15. Fix a long-standing bug in the query planner that caused incorrect results on a LEFT JOIN where the left-hand table is a subquery and the join constraint is a bare column name coming from the left-hand subquery. Ticket [2df0107b](https://sqlite.org/src/info/2df0107b).
16. Correctly handle the integer literal -0x8000000000000000 in the query planner.
**Changes in this specific patch release, version 3.16.1 (2017-01-03):**
1. Fix a bug concerning the use of [row values](../rowvalue.md) within [triggers](../lang_createtrigger.md) (see ticket [8c9458e7](https://sqlite.org/src/info/8c9458e7)) that was in version 3.15.0 but was not reported until moments after the 3.16.0 release was published.
**Hashes:**
2. SQLITE_SOURCE_ID: "2017-01-03 18:27:03 979f04392853b8053817a3eea2fc679947b437fd"
3. SHA1 for sqlite3.c: 354f6223490b30fd5320b4066b1535e4ce33988d
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.16.2 On 2017-01-06
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_16_2.html*
## SQLite Release 3.16.2 On 2017-01-06
**Prior changes from version 3.16.0 (2017-01-02):**
1. Uses 9% fewer CPU cycles. (See the [CPU performance measurement](../cpu.md) report for details on how this performance increase was computed.)
2. Added experimental support for [PRAGMA functions](../pragma.md#pragfunc).
3. Added the [SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE](../c3ref/c_dbconfig_defensive.md#sqlitedbconfignockptonclose) option to [sqlite3_db_config()](../c3ref/db_config.md).
4. Enhance the [date and time functions](../lang_datefunc.md) so that the 'unixepoch' modifier works for the full span of supported dates.
5. Changed the default configuration of the [lookaside memory allocator](../malloc.md#lookaside) from 500 slots of 128 bytes each into 125 slots of 512 bytes each.
6. Enhanced "WHERE x NOT NULL" [partial indexes](../partialindex.md) so that they are usable if the "x" column appears in a LIKE or GLOB operator.
7. Enhanced [sqlite3_interrupt()](../c3ref/interrupt.md) so that it interrupts [checkpoint](../wal.md#ckpt) operations that are in process.
8. Enhanced the [LIKE](../lang_expr.md#like) and [GLOB](../lang_expr.md#glob) matching algorithm to be faster for cases when the pattern contains multiple wildcards.
9. Added the [SQLITE_FCNTL_WIN32_GET_HANDLE](../c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlwin32gethandle) file control opcode.
10. Added ".mode quote" to the [command-line shell](../cli.md).
11. Added ".lint fkey-indexes" to the [command-line shell](../cli.md).
12. Added the [.imposter dot-command](../imposter.md#dotimposter) to the [command-line shell](../cli.md).
13. Added the [remember(V,PTR)](https://sqlite.org/src/file/ext/misc/remember.c) SQL function as a [loadable extension](../loadext.md).
14. Rename the [SQLITE_OMIT_BUILTIN_TEST](../compile.md#omit_builtin_test) compile-time option to [SQLITE_UNTESTABLE](../compile.md#untestable) to better reflect the implications of using it.
**Bug Fixes:**
15. Fix a long-standing bug in the query planner that caused incorrect results on a LEFT JOIN where the left-hand table is a subquery and the join constraint is a bare column name coming from the left-hand subquery. Ticket [2df0107b](https://sqlite.org/src/info/2df0107b).
16. Correctly handle the integer literal -0x8000000000000000 in the query planner.
**Prior changes from version 3.16.1 (2017-01-03):**
1. Fix a bug concerning the use of [row values](../rowvalue.md) within [triggers](../lang_createtrigger.md) (see ticket [8c9458e7](https://sqlite.org/src/info/8c9458e7)) that was in version 3.15.0 but was not reported until moments after the 3.16.0 release was published.
**Changes in this specific patch release, version 3.16.2 (2017-01-06):**
1. Fix the [REPLACE](../lang_replace.md) statement for [WITHOUT ROWID](../withoutrowid.md) tables that lack secondary indexes so that it works correctly with triggers and foreign keys. This was a new bug caused by performance optimizations added in version 3.16.0. Ticket [30027b613b4](https://sqlite.org/src/info/30027b613b4)
2. Fix the [sqlite3_value_text()](../c3ref/value_blob.md) interface so that it correctly translates content generated by [zeroblob()](../lang_corefunc.md#zeroblob) into a string of all 0x00 characters. This is a long-standing issue discovered after the 3.16.1 release by [OSS-Fuzz](https://github.com/google/oss-fuzz)
3. Fix the bytecode generator to deal with a subquery in the FROM clause that is itself a UNION ALL where one side of the UNION ALL is a view that contains an ORDER BY. This is a long-standing issue that was discovered after the release of 3.16.1. See ticket [190c2507](https://sqlite.org/src/info/190c2507).
4. Adjust the [sqlite3_column_count()](../c3ref/column_count.md) API so it more often returns the same values for [PRAGMA](../pragma.md#syntax) statements as it did in prior releases, to minimize disruption to applications that might be using that interface in unexpected ways.
**Hashes:**
5. SQLITE_SOURCE_ID: "2017-01-06 16:32:41 a65a62893ca8319e89e48b8a38cf8a59c69a8209"
6. SHA1 for sqlite3.c: 2bebdc3f24911c0d12b6d6c0123c3f84d6946b08
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.17.0 On 2017-02-13
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_17_0.html*
## SQLite Release 3.17.0 On 2017-02-13
1. Approximately 25% better performance from the [R-Tree extension](../rtree.md).
1. Uses compiler built-ins (ex: \_\_builtin_bswap32() or \_byteswap_ulong()) for byteswapping when available.
2. Uses the [sqlite3_blob](../c3ref/blob.md) key/value access object instead of SQL for pulling content out of R-Tree nodes
3. Other miscellaneous enhancements such as loop unrolling.
2. Add the [SQLITE_DEFAULT_LOOKASIDE](../compile.md#default_lookaside) compile-time option.
3. Increase the default [lookaside](../malloc.md#lookaside) size from 512,125 to 1200,100 as this provides better performance while only adding 56KB of extra memory per connection. Memory-sensitive applications can restore the old default at compile-time, start-time, or run-time.
4. Use compiler built-ins \_\_builtin_sub_overflow(), \_\_builtin_add_overflow(), and \_\_builtin_mul_overflow() when available. (All compiler built-ins can be omitted with the [SQLITE_DISABLE_INTRINSIC](../compile.md#disable_intrinsic) compile-time option.)
5. Added the [SQLITE_ENABLE_NULL_TRIM](../compile.md#enable_null_trim) compile-time option, which can result in significantly smaller database files for some applications, at the risk of being incompatible with older versions of SQLite.
6. Change [SQLITE_DEFAULT_PCACHE_INITSZ](../compile.md#default_pcache_initsz) from 100 to 20, for improved performance.
7. Added the SQLITE_UINT64_TYPE compile-time option as an analog to SQLITE_INT64_TYPE.
8. Perform some [UPDATE](../lang_update.md) operations in a single pass instead of in two passes.
9. Enhance the [session extension](../sessionintro.md) to support [WITHOUT ROWID](../withoutrowid.md) tables.
10. Fixed performance problems and potential stack overflows when creating [views](../lang_createview.md) from multi-row VALUES clauses with hundreds of thousands of rows.
11. Added the [sha1.c](https://sqlite.org/src/file/ext/misc/sha1.c) extension.
12. In the [command-line shell](../cli.md), enhance the ".mode" command so that it restores the default column and row separators for modes "line", "list", "column", and "tcl".
13. Enhance the [SQLITE_DIRECT_OVERFLOW_READ](../compile.md#direct_overflow_read) option so that it works in [WAL mode](../wal.md) as long as the pages being read are not in the WAL file.
14. Enhance the [Lemon parser generator](../lemon.md) so that it can store the parser object as a stack variable rather than allocating space from the heap and make use of that enhancement in the [amalgamation](../amalgamation.md).
15. Other performance improvements. Uses about [6.5% fewer CPU cycles](../cpu.md).
**Bug Fixes:**
16. Throw an error if the ON clause of a LEFT JOIN references tables to the right of the ON clause. This is the same behavior as PostgreSQL. Formerly, SQLite silently converted the LEFT JOIN into an INNER JOIN. Fix for ticket [25e335f802dd](https://sqlite.org/src/info/25e335f802dd).
17. Use the correct affinity for columns of automatic indexes. Ticket [7ffd1ca1d2ad4ec](https://sqlite.org/src/info/7ffd1ca1d2ad4ec).
18. Ensure that the [sqlite3_blob_reopen()](../c3ref/blob_reopen.md) interface can correctly handle short rows. Fix for ticket [e6e962d6b0f06f46e](https://sqlite.org/src/info/e6e962d6b0f06f46e).
**Hashes:**
19. SQLITE_SOURCE_ID: "2017-02-13 16:02:40 ada05cfa86ad7f5645450ac7a2a21c9aa6e57d2c"
20. SHA1 for sqlite3.c: cc7d708bb073c44102a59ed63ce6142da1f174d1
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.18.0 On 2017-03-30
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_18_0.html*
## SQLite Release 3.18.0 On 2017-03-30
1. Added the [PRAGMA optimize](../pragma.md#pragma_optimize) command
2. The SQLite version identifier returned by the [sqlite_source_id()](../lang_corefunc.md#sqlite_source_id) SQL function and the [sqlite3_sourceid()](../c3ref/libversion.md) C API and found in the [SQLITE_SOURCE_ID](../c3ref/c_scm_branch.md) macro is now a 64-digit SHA3-256 hash instead of a 40-digit SHA1 hash.
3. Added the [json_patch()](../json1.md#jpatch) SQL function to the [JSON1 extension](../json1.md).
4. Enhance the [LIKE optimization](../optoverview.md#like_opt) so that it works for arbitrary expressions on the left-hand side as long as the LIKE pattern on the right-hand side does not begin with a digit or minus sign.
5. Added the [sqlite3_set_last_insert_rowid()](../c3ref/set_last_insert_rowid.md) interface and use the new interface in the [FTS3](../fts3.md), [FTS4](../fts3.md#fts4), and [FTS5](../fts5.md) extensions to ensure that the [sqlite3_last_insert_rowid()](../c3ref/last_insert_rowid.md) interface always returns reasonable values.
6. Enhance [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) and [PRAGMA quick_check](../pragma.md#pragma_quick_check) so that they verify [CHECK constraints](../lang_createtable.md#ckconst).
7. Enhance the query plans for joins to detect empty tables early and halt without doing unnecessary work.
8. Enhance the [sqlite3_mprintf()](../c3ref/mprintf.md) family of interfaces and the [printf SQL function](../lang_corefunc.md#printf) to put comma separators at the thousands marks for integers, if the "," format modifier is used in between the "%" and the "d" (example: "%,d").
9. Added the -D[SQLITE_MAX_MEMORY](../compile.md#max_memory)=*N* compile-time option.
10. Added the [.sha3sum dot-command](../cli.md#sha3sum) and the [.selftest dot-command](../cli.md#selftest) to the [command-line shell](../cli.md)
11. Begin enforcing [SQLITE_LIMIT_VDBE_OP](../c3ref/c_limit_attached.md#sqlitelimitvdbeop). This can be used, for example, to prevent excessively large prepared statements in systems that accept SQL queries from untrusted users.
12. Various performance improvements.
**Bug Fixes:**
13. Ensure that indexed expressions with collating sequences are handled correctly. Fix for ticket [eb703ba7b50c1a5](https://sqlite.org/src/info/eb703ba7b50c1a5).
14. Fix a bug in the 'start of ...' modifiers for the [date and time functions](../lang_datefunc.md). Ticket [6097cb92745327a1](https://sqlite.org/src/info/6097cb92745327a1)
15. Fix a potential segfault in complex recursive triggers, resulting from a bug in the OP_Once opcode introduced as part of a performance optimization in version 3.15.0. Ticket [06796225f59c057c](https://sqlite.org/src/info/06796225f59c057c)
16. In the [RBU extension](../rbu.md), add extra sync operations to avoid the possibility of corruption following a power failure.
17. The [sqlite3_trace_v2()](../c3ref/trace_v2.md) output for nested SQL statements should always begin with a "--" comment marker.
**Hashes:**
18. SQLITE_SOURCE_ID: "2017-03-28 18:48:43 424a0d380332858ee55bdebc4af3789f74e70a2b3ba1cf29d84b9b4bcf3e2e37"
19. SHA3-256 for sqlite3.c: cbf322df1f76be57fb3be84f3da1fc71d1d3dfdb7e7c2757fb0ff630b3bc2e5d
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.18.1 On 2017-06-16
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_18_1.html*
## SQLite Release 3.18.1 On 2017-06-16
**Prior changes from version 3.18.0 (2017-03-30):**
1. Added the [PRAGMA optimize](../pragma.md#pragma_optimize) command
2. The SQLite version identifier returned by the [sqlite_source_id()](../lang_corefunc.md#sqlite_source_id) SQL function and the [sqlite3_sourceid()](../c3ref/libversion.md) C API and found in the [SQLITE_SOURCE_ID](../c3ref/c_scm_branch.md) macro is now a 64-digit SHA3-256 hash instead of a 40-digit SHA1 hash.
3. Added the [json_patch()](../json1.md#jpatch) SQL function to the [JSON1 extension](../json1.md).
4. Enhance the [LIKE optimization](../optoverview.md#like_opt) so that it works for arbitrary expressions on the left-hand side as long as the LIKE pattern on the right-hand side does not begin with a digit or minus sign.
5. Added the [sqlite3_set_last_insert_rowid()](../c3ref/set_last_insert_rowid.md) interface and use the new interface in the [FTS3](../fts3.md), [FTS4](../fts3.md#fts4), and [FTS5](../fts5.md) extensions to ensure that the [sqlite3_last_insert_rowid()](../c3ref/last_insert_rowid.md) interface always returns reasonable values.
6. Enhance [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) and [PRAGMA quick_check](../pragma.md#pragma_quick_check) so that they verify [CHECK constraints](../lang_createtable.md#ckconst).
7. Enhance the query plans for joins to detect empty tables early and halt without doing unnecessary work.
8. Enhance the [sqlite3_mprintf()](../c3ref/mprintf.md) family of interfaces and the [printf SQL function](../lang_corefunc.md#printf) to put comma separators at the thousands marks for integers, if the "," format modifier is used in between the "%" and the "d" (example: "%,d").
9. Added the -D[SQLITE_MAX_MEMORY](../compile.md#max_memory)=*N* compile-time option.
10. Added the [.sha3sum dot-command](../cli.md#sha3sum) and the [.selftest dot-command](../cli.md#selftest) to the [command-line shell](../cli.md)
11. Begin enforcing [SQLITE_LIMIT_VDBE_OP](../c3ref/c_limit_attached.md#sqlitelimitvdbeop). This can be used, for example, to prevent excessively large prepared statements in systems that accept SQL queries from untrusted users.
12. Various performance improvements.
**Bug Fixes:**
13. Ensure that indexed expressions with collating sequences are handled correctly. Fix for ticket [eb703ba7b50c1a5](https://sqlite.org/src/info/eb703ba7b50c1a5).
14. Fix a bug in the 'start of ...' modifiers for the [date and time functions](../lang_datefunc.md). Ticket [6097cb92745327a1](https://sqlite.org/src/info/6097cb92745327a1)
15. Fix a potential segfault in complex recursive triggers, resulting from a bug in the OP_Once opcode introduced as part of a performance optimization in version 3.15.0. Ticket [06796225f59c057c](https://sqlite.org/src/info/06796225f59c057c)
16. In the [RBU extension](../rbu.md), add extra sync operations to avoid the possibility of corruption following a power failure.
17. The [sqlite3_trace_v2()](../c3ref/trace_v2.md) output for nested SQL statements should always begin with a "--" comment marker.
**Changes in this specific patch release, version 3.18.1 (2017-06-16):**
1. Fix a bug associated with [auto_vacuum](../pragma.md#pragma_auto_vacuum) that can lead to database corruption. The bug was introduced in [version 3.16.0](../releaselog/3_16_0.md) (2017-01-02). Ticket [fda22108](https://sqlite.org/src/info/fda22108).
**Hashes:**
2. SQLITE_SOURCE_ID: "2017-06-16 13:41:15 77bb46233db03a3338bacf7e56f439be3dfd1926ea0c44d252eeafa7a7b31c06"
3. SHA3-256 for sqlite3.c: 334eaf776db9d09a4e69d6012c266bc837107edc2c981739ef82081cb11c5723
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.18.2 On 2017-06-17
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_18_2.html*
## SQLite Release 3.18.2 On 2017-06-17
**Prior changes from version 3.18.0 (2017-03-30):**
1. Added the [PRAGMA optimize](../pragma.md#pragma_optimize) command
2. The SQLite version identifier returned by the [sqlite_source_id()](../lang_corefunc.md#sqlite_source_id) SQL function and the [sqlite3_sourceid()](../c3ref/libversion.md) C API and found in the [SQLITE_SOURCE_ID](../c3ref/c_scm_branch.md) macro is now a 64-digit SHA3-256 hash instead of a 40-digit SHA1 hash.
3. Added the [json_patch()](../json1.md#jpatch) SQL function to the [JSON1 extension](../json1.md).
4. Enhance the [LIKE optimization](../optoverview.md#like_opt) so that it works for arbitrary expressions on the left-hand side as long as the LIKE pattern on the right-hand side does not begin with a digit or minus sign.
5. Added the [sqlite3_set_last_insert_rowid()](../c3ref/set_last_insert_rowid.md) interface and use the new interface in the [FTS3](../fts3.md), [FTS4](../fts3.md#fts4), and [FTS5](../fts5.md) extensions to ensure that the [sqlite3_last_insert_rowid()](../c3ref/last_insert_rowid.md) interface always returns reasonable values.
6. Enhance [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) and [PRAGMA quick_check](../pragma.md#pragma_quick_check) so that they verify [CHECK constraints](../lang_createtable.md#ckconst).
7. Enhance the query plans for joins to detect empty tables early and halt without doing unnecessary work.
8. Enhance the [sqlite3_mprintf()](../c3ref/mprintf.md) family of interfaces and the [printf SQL function](../lang_corefunc.md#printf) to put comma separators at the thousands marks for integers, if the "," format modifier is used in between the "%" and the "d" (example: "%,d").
9. Added the -D[SQLITE_MAX_MEMORY](../compile.md#max_memory)=*N* compile-time option.
10. Added the [.sha3sum dot-command](../cli.md#sha3sum) and the [.selftest dot-command](../cli.md#selftest) to the [command-line shell](../cli.md)
11. Begin enforcing [SQLITE_LIMIT_VDBE_OP](../c3ref/c_limit_attached.md#sqlitelimitvdbeop). This can be used, for example, to prevent excessively large prepared statements in systems that accept SQL queries from untrusted users.
12. Various performance improvements.
**Bug Fixes:**
13. Ensure that indexed expressions with collating sequences are handled correctly. Fix for ticket [eb703ba7b50c1a5](https://sqlite.org/src/info/eb703ba7b50c1a5).
14. Fix a bug in the 'start of ...' modifiers for the [date and time functions](../lang_datefunc.md). Ticket [6097cb92745327a1](https://sqlite.org/src/info/6097cb92745327a1)
15. Fix a potential segfault in complex recursive triggers, resulting from a bug in the OP_Once opcode introduced as part of a performance optimization in version 3.15.0. Ticket [06796225f59c057c](https://sqlite.org/src/info/06796225f59c057c)
16. In the [RBU extension](../rbu.md), add extra sync operations to avoid the possibility of corruption following a power failure.
17. The [sqlite3_trace_v2()](../c3ref/trace_v2.md) output for nested SQL statements should always begin with a "--" comment marker.
**Prior changes from version 3.18.1 (2017-06-16):**
1. Fix a bug associated with [auto_vacuum](../pragma.md#pragma_auto_vacuum) that can lead to database corruption. The bug was introduced in [version 3.16.0](../releaselog/3_16_0.md) (2017-01-02). Ticket [fda22108](https://sqlite.org/src/info/fda22108).
**Changes in this specific patch release, version 3.18.2 (2017-06-17):**
1. Fix a bug that might cause duplicate output rows when an IN operator is used in the WHERE clause. Ticket [61fe9745](https://sqlite.org/src/info/61fe9745).
**Hashes:**
2. SQLITE_SOURCE_ID: "2017-06-17 09:59:36 036ebf729e4b21035d7f4f8e35a6f705e6bf99887889e2dc14ebf2242e7930dd"
3. SHA3-256 for sqlite3.c: b0bd014f2776b9f9508a3fc6432f70e2436bf54475369f88f0aeef75b0eec93e
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.19.0 On 2017-05-22
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_19_0.html*
## SQLite Release 3.19.0 On 2017-05-22
1. The [SQLITE_READ](../c3ref/c_alter_table.md) [authorizer callback](../c3ref/set_authorizer.md) is invoked once with a column name that is an empty string for every table referenced in a query from which no columns are extracted.
2. When using an index on an expression, try to use expression values already available in the index, rather than loading the original columns and recomputing the expression.
3. Enhance the [flattening optimization](../optoverview.md#flattening) so that it is able to flatten views on the right-hand side of a LEFT JOIN.
4. Use [replace()](../lang_corefunc.md#replace) instead of [char()](../lang_corefunc.md#char) for escaping newline and carriage-return characters embedded in strings in the .dump output from the [command-line shell](../cli.md).
5. Avoid unnecessary foreign key processing in UPDATE statements that do not touch the columns that are constrained by the foreign keys.
6. On a DISTINCT query that uses an index, try to skip ahead to the next distinct entry using the index rather than stepping through rows, when an appropriate index is available.
7. Avoid unnecessary invalidation of [sqlite3_blob](../c3ref/blob.md) handles when making changes to unrelated tables.
8. Transfer any terms of the HAVING clause that use only columns mentioned in the GROUP BY clause over to the WHERE clause for faster processing.
9. Reuse the same materialization of a VIEW if that VIEW appears more than once in the same query.
10. Enhance [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) so that it identifies tables that have two or more rows with the same [rowid](../lang_createtable.md#rowid).
11. Enhance the [FTS5](../fts5.md) query syntax so that [column filters](../fts5.md#fts5_column_filters) may be applied to arbitrary expressions.
12. Enhance the [json_extract()](../json1.md#jex) function to cache and reuse parses of JSON input text.
13. Added the [anycollseq.c](https://sqlite.org/src/file/ext/misc/anycollseq.c) [loadable extension](../loadext.md) that allows a generic SQLite database connection to read a schema that contains unknown and/or application-specific [collating sequences](../datatype3.md#collation).
**Bug Fixes:**
14. Fix a problem in [REPLACE](../lang_replace.md) that can result in a corrupt database containing two or more rows with the same [rowid](../lang_createtable.md#rowid). Fix for ticket [f68dc596c4e6018d](https://sqlite.org/src/info/f68dc596c4e6018d).
15. Fix a problem in [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) that was causing a subsequent [VACUUM](../lang_vacuum.md) to behave suboptimally.
16. Fix the [PRAGMA foreign_key_check](../pragma.md#pragma_foreign_key_check) command so that it works correctly with foreign keys on [WITHOUT ROWID](../withoutrowid.md) tables.
17. Fix a bug in the b-tree logic that can result in incorrect duplicate answers for IN operator queries. Ticket [61fe9745](https://sqlite.org/src/info/61fe9745)
18. Disallow leading zeros in numeric constants in JSON. Fix for ticket [b93be8729a895a528e2](https://sqlite.org/src/info/b93be8729a895a528e2).
19. Disallow control characters inside of strings in JSON. Fix for ticket [6c9b5514077fed34551](https://sqlite.org/src/info/6c9b5514077fed34551).
20. Limit the depth of recursion for JSON objects and arrays in order to avoid excess stack usage in the recursive descent parser. Fix for ticket [981329adeef51011052](https://sqlite.org/src/info/981329adeef51011052).
**Hashes:**
21. SQLITE_SOURCE_ID: "2017-05-22 13:58:13 28a94eb282822cad1d1420f2dad6bf65e4b8b9062eda4a0b9ee8270b2c608e40"
22. SHA3-256 for sqlite3.c: c30326aa1a9cc342061b755725eac9270109acf878bc59200dd4b1cea6bc2908
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.19.1 On 2017-05-24
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_19_1.html*
## SQLite Release 3.19.1 On 2017-05-24
**Prior changes from version 3.19.0 (2017-05-22):**
1. The [SQLITE_READ](../c3ref/c_alter_table.md) [authorizer callback](../c3ref/set_authorizer.md) is invoked once with a column name that is an empty string for every table referenced in a query from which no columns are extracted.
2. When using an index on an expression, try to use expression values already available in the index, rather than loading the original columns and recomputing the expression.
3. Enhance the [flattening optimization](../optoverview.md#flattening) so that it is able to flatten views on the right-hand side of a LEFT JOIN.
4. Use [replace()](../lang_corefunc.md#replace) instead of [char()](../lang_corefunc.md#char) for escaping newline and carriage-return characters embedded in strings in the .dump output from the [command-line shell](../cli.md).
5. Avoid unnecessary foreign key processing in UPDATE statements that do not touch the columns that are constrained by the foreign keys.
6. On a DISTINCT query that uses an index, try to skip ahead to the next distinct entry using the index rather than stepping through rows, when an appropriate index is available.
7. Avoid unnecessary invalidation of [sqlite3_blob](../c3ref/blob.md) handles when making changes to unrelated tables.
8. Transfer any terms of the HAVING clause that use only columns mentioned in the GROUP BY clause over to the WHERE clause for faster processing.
9. Reuse the same materialization of a VIEW if that VIEW appears more than once in the same query.
10. Enhance [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) so that it identifies tables that have two or more rows with the same [rowid](../lang_createtable.md#rowid).
11. Enhance the [FTS5](../fts5.md) query syntax so that [column filters](../fts5.md#fts5_column_filters) may be applied to arbitrary expressions.
12. Enhance the [json_extract()](../json1.md#jex) function to cache and reuse parses of JSON input text.
13. Added the [anycollseq.c](https://sqlite.org/src/file/ext/misc/anycollseq.c) [loadable extension](../loadext.md) that allows a generic SQLite database connection to read a schema that contains unknown and/or application-specific [collating sequences](../datatype3.md#collation).
**Bug Fixes:**
14. Fix a problem in [REPLACE](../lang_replace.md) that can result in a corrupt database containing two or more rows with the same [rowid](../lang_createtable.md#rowid). Fix for ticket [f68dc596c4e6018d](https://sqlite.org/src/info/f68dc596c4e6018d).
15. Fix a problem in [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) that was causing a subsequent [VACUUM](../lang_vacuum.md) to behave suboptimally.
16. Fix the [PRAGMA foreign_key_check](../pragma.md#pragma_foreign_key_check) command so that it works correctly with foreign keys on [WITHOUT ROWID](../withoutrowid.md) tables.
17. Fix a bug in the b-tree logic that can result in incorrect duplicate answers for IN operator queries. Ticket [61fe9745](https://sqlite.org/src/info/61fe9745)
18. Disallow leading zeros in numeric constants in JSON. Fix for ticket [b93be8729a895a528e2](https://sqlite.org/src/info/b93be8729a895a528e2).
19. Disallow control characters inside of strings in JSON. Fix for ticket [6c9b5514077fed34551](https://sqlite.org/src/info/6c9b5514077fed34551).
20. Limit the depth of recursion for JSON objects and arrays in order to avoid excess stack usage in the recursive descent parser. Fix for ticket [981329adeef51011052](https://sqlite.org/src/info/981329adeef51011052).
**Changes in this specific patch release, version 3.19.1 (2017-05-24):**
1. Fix a bug in the LEFT JOIN [flattening optimization](../optoverview.md#flattening). Ticket [cad1ab4cb7b0fc](https://sqlite.org/src/info/cad1ab4cb7b0fc).
2. Remove a surplus semicolon that was causing problems for older versions of MSVC.
**Hashes:**
3. SQLITE_SOURCE_ID: "2017-05-24 13:08:33 f6d7b988f40217821a382bc298180e9e6794f3ed79a83c6ef5cae048989b3f86"
4. SHA3-256 for sqlite3.c: 996b2aff37b6e0c6663d0312cd921bbdf6826c989cbbb07dadde5e9672889bca
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.19.2 On 2017-05-25
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_19_2.html*
## SQLite Release 3.19.2 On 2017-05-25
**Prior changes from version 3.19.0 (2017-05-22):**
1. The [SQLITE_READ](../c3ref/c_alter_table.md) [authorizer callback](../c3ref/set_authorizer.md) is invoked once with a column name that is an empty string for every table referenced in a query from which no columns are extracted.
2. When using an index on an expression, try to use expression values already available in the index, rather than loading the original columns and recomputing the expression.
3. Enhance the [flattening optimization](../optoverview.md#flattening) so that it is able to flatten views on the right-hand side of a LEFT JOIN.
4. Use [replace()](../lang_corefunc.md#replace) instead of [char()](../lang_corefunc.md#char) for escaping newline and carriage-return characters embedded in strings in the .dump output from the [command-line shell](../cli.md).
5. Avoid unnecessary foreign key processing in UPDATE statements that do not touch the columns that are constrained by the foreign keys.
6. On a DISTINCT query that uses an index, try to skip ahead to the next distinct entry using the index rather than stepping through rows, when an appropriate index is available.
7. Avoid unnecessary invalidation of [sqlite3_blob](../c3ref/blob.md) handles when making changes to unrelated tables.
8. Transfer any terms of the HAVING clause that use only columns mentioned in the GROUP BY clause over to the WHERE clause for faster processing.
9. Reuse the same materialization of a VIEW if that VIEW appears more than once in the same query.
10. Enhance [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) so that it identifies tables that have two or more rows with the same [rowid](../lang_createtable.md#rowid).
11. Enhance the [FTS5](../fts5.md) query syntax so that [column filters](../fts5.md#fts5_column_filters) may be applied to arbitrary expressions.
12. Enhance the [json_extract()](../json1.md#jex) function to cache and reuse parses of JSON input text.
13. Added the [anycollseq.c](https://sqlite.org/src/file/ext/misc/anycollseq.c) [loadable extension](../loadext.md) that allows a generic SQLite database connection to read a schema that contains unknown and/or application-specific [collating sequences](../datatype3.md#collation).
**Bug Fixes:**
14. Fix a problem in [REPLACE](../lang_replace.md) that can result in a corrupt database containing two or more rows with the same [rowid](../lang_createtable.md#rowid). Fix for ticket [f68dc596c4e6018d](https://sqlite.org/src/info/f68dc596c4e6018d).
15. Fix a problem in [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) that was causing a subsequent [VACUUM](../lang_vacuum.md) to behave suboptimally.
16. Fix the [PRAGMA foreign_key_check](../pragma.md#pragma_foreign_key_check) command so that it works correctly with foreign keys on [WITHOUT ROWID](../withoutrowid.md) tables.
17. Fix a bug in the b-tree logic that can result in incorrect duplicate answers for IN operator queries. Ticket [61fe9745](https://sqlite.org/src/info/61fe9745)
18. Disallow leading zeros in numeric constants in JSON. Fix for ticket [b93be8729a895a528e2](https://sqlite.org/src/info/b93be8729a895a528e2).
19. Disallow control characters inside of strings in JSON. Fix for ticket [6c9b5514077fed34551](https://sqlite.org/src/info/6c9b5514077fed34551).
20. Limit the depth of recursion for JSON objects and arrays in order to avoid excess stack usage in the recursive descent parser. Fix for ticket [981329adeef51011052](https://sqlite.org/src/info/981329adeef51011052).
**Prior changes from version 3.19.1 (2017-05-24):**
1. Fix a bug in the LEFT JOIN [flattening optimization](../optoverview.md#flattening). Ticket [cad1ab4cb7b0fc](https://sqlite.org/src/info/cad1ab4cb7b0fc).
2. Remove a surplus semicolon that was causing problems for older versions of MSVC.
**Changes in this specific patch release, version 3.19.2 (2017-05-25):**
1. Fix more bugs in the LEFT JOIN [flattening optimization](../optoverview.md#flattening). Ticket [7fde638e94287d2c](https://sqlite.org/src/info/7fde638e94287d2c).
**Hashes:**
2. SQLITE_SOURCE_ID: "2017-05-25 16:50:27 edb4e819b0c058c7d74d27ebd14cc5ceb2bad6a6144a486a970182b7afe3f8b9"
3. SHA3-256 for sqlite3.c: 1be0c457869c1f7eba58c3b5097b9ec307a15be338308bee8e5be8570bcf5d1e
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.19.3 On 2017-06-08
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_19_3.html*
## SQLite Release 3.19.3 On 2017-06-08
**Prior changes from version 3.19.0 (2017-05-22):**
1. The [SQLITE_READ](../c3ref/c_alter_table.md) [authorizer callback](../c3ref/set_authorizer.md) is invoked once with a column name that is an empty string for every table referenced in a query from which no columns are extracted.
2. When using an index on an expression, try to use expression values already available in the index, rather than loading the original columns and recomputing the expression.
3. Enhance the [flattening optimization](../optoverview.md#flattening) so that it is able to flatten views on the right-hand side of a LEFT JOIN.
4. Use [replace()](../lang_corefunc.md#replace) instead of [char()](../lang_corefunc.md#char) for escaping newline and carriage-return characters embedded in strings in the .dump output from the [command-line shell](../cli.md).
5. Avoid unnecessary foreign key processing in UPDATE statements that do not touch the columns that are constrained by the foreign keys.
6. On a DISTINCT query that uses an index, try to skip ahead to the next distinct entry using the index rather than stepping through rows, when an appropriate index is available.
7. Avoid unnecessary invalidation of [sqlite3_blob](../c3ref/blob.md) handles when making changes to unrelated tables.
8. Transfer any terms of the HAVING clause that use only columns mentioned in the GROUP BY clause over to the WHERE clause for faster processing.
9. Reuse the same materialization of a VIEW if that VIEW appears more than once in the same query.
10. Enhance [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) so that it identifies tables that have two or more rows with the same [rowid](../lang_createtable.md#rowid).
11. Enhance the [FTS5](../fts5.md) query syntax so that [column filters](../fts5.md#fts5_column_filters) may be applied to arbitrary expressions.
12. Enhance the [json_extract()](../json1.md#jex) function to cache and reuse parses of JSON input text.
13. Added the [anycollseq.c](https://sqlite.org/src/file/ext/misc/anycollseq.c) [loadable extension](../loadext.md) that allows a generic SQLite database connection to read a schema that contains unknown and/or application-specific [collating sequences](../datatype3.md#collation).
**Bug Fixes:**
14. Fix a problem in [REPLACE](../lang_replace.md) that can result in a corrupt database containing two or more rows with the same [rowid](../lang_createtable.md#rowid). Fix for ticket [f68dc596c4e6018d](https://sqlite.org/src/info/f68dc596c4e6018d).
15. Fix a problem in [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) that was causing a subsequent [VACUUM](../lang_vacuum.md) to behave suboptimally.
16. Fix the [PRAGMA foreign_key_check](../pragma.md#pragma_foreign_key_check) command so that it works correctly with foreign keys on [WITHOUT ROWID](../withoutrowid.md) tables.
17. Fix a bug in the b-tree logic that can result in incorrect duplicate answers for IN operator queries. Ticket [61fe9745](https://sqlite.org/src/info/61fe9745)
18. Disallow leading zeros in numeric constants in JSON. Fix for ticket [b93be8729a895a528e2](https://sqlite.org/src/info/b93be8729a895a528e2).
19. Disallow control characters inside of strings in JSON. Fix for ticket [6c9b5514077fed34551](https://sqlite.org/src/info/6c9b5514077fed34551).
20. Limit the depth of recursion for JSON objects and arrays in order to avoid excess stack usage in the recursive descent parser. Fix for ticket [981329adeef51011052](https://sqlite.org/src/info/981329adeef51011052).
**Prior changes from version 3.19.1 (2017-05-24):**
1. Fix a bug in the LEFT JOIN [flattening optimization](../optoverview.md#flattening). Ticket [cad1ab4cb7b0fc](https://sqlite.org/src/info/cad1ab4cb7b0fc).
2. Remove a surplus semicolon that was causing problems for older versions of MSVC.
**Prior changes from version 3.19.2 (2017-05-25):**
1. Fix more bugs in the LEFT JOIN [flattening optimization](../optoverview.md#flattening). Ticket [7fde638e94287d2c](https://sqlite.org/src/info/7fde638e94287d2c).
**Changes in this specific patch release, version 3.19.3 (2017-06-08):**
1. Fix a bug associated with [auto_vacuum](../pragma.md#pragma_auto_vacuum) that can lead to database corruption. The bug was introduced in [version 3.16.0](../releaselog/3_16_0.md) (2017-01-02). Ticket [fda22108](https://sqlite.org/src/info/fda22108).
**Hashes:**
2. SQLITE_SOURCE_ID: "2017-06-08 14:26:16 0ee482a1e0eae22e08edc8978c9733a96603d4509645f348ebf55b579e89636b"
3. SHA3-256 for sqlite3.c: 368f1d31272b1739f804bcfa5485e5de62678015c4adbe575003ded85c164bb8
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.2.0 On 2005-03-21
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_2_0.html*
## SQLite Release 3.2.0 On 2005-03-21
1. Added support for ALTER TABLE ADD COLUMN.
2. Added support for the "T" separator in ISO-8601 date/time strings.
3. Improved support for Cygwin.
4. Numerous bug fixes and documentation updates.
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.2.1 On 2005-03-29
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_2_1.html*
## SQLite Release 3.2.1 On 2005-03-29
1. Fix a memory allocation error in the new ADD COLUMN comment.
2. Documentation updates
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.2.2 On 2005-06-12
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_2_2.html*
## SQLite Release 3.2.2 On 2005-06-12
1. Added the sqlite3_db_handle() API
2. Added the sqlite3_get_autocommit() API
3. Added a REGEXP operator to the parser. There is no function to back up this operator in the standard build but users can add their own using sqlite3_create_function()
4. Speed improvements and library footprint reductions.
5. Fix byte alignment problems on 64-bit architectures.
6. Many, many minor bug fixes and documentation updates.
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.2.3 On 2005-08-21
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_2_3.html*
## SQLite Release 3.2.3 On 2005-08-21
1. Added support for the CAST operator
2. Tcl interface allows BLOB values to be transferred to user-defined functions
3. Added the "transaction" method to the Tcl interface
4. Allow the DEFAULT value of a column to call functions that have constant operands
5. Added the ANALYZE command for gathering statistics on indices and using those statistics when picking an index in the optimizer
6. Remove the limit (formerly 100) on the number of terms in the WHERE clause
7. The right-hand side of the IN operator can now be a list of expressions instead of just a list of constants
8. Rework the optimizer so that it is able to make better use of indices
9. The order of tables in a join is adjusted automatically to make better use of indices
10. The IN operator is now a candidate for optimization even if the left-hand side is not the left-most term of the index. Multiple IN operators can be used with the same index.
11. WHERE clause expressions using BETWEEN and OR are now candidates for optimization
12. Added the "case_sensitive_like" pragma and the SQLITE_CASE_SENSITIVE_LIKE compile-time option to set its default value to "on".
13. Use indices to help with GLOB expressions and LIKE expressions too when the case_sensitive_like pragma is enabled
14. Added support for grave-accent quoting for compatibility with MySQL
15. Improved test coverage
16. Dozens of minor bug fixes
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.2.4 On 2005-08-24
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_2_4.html*
## SQLite Release 3.2.4 On 2005-08-24
1. Fix a bug introduced in the previous release that can cause a segfault while generating code for complex WHERE clauses.
2. Allow floating point literals to begin or end with a decimal point.
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.2.5 On 2005-08-27
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_2_5.html*
## SQLite Release 3.2.5 On 2005-08-27
1. Fix a bug effecting DELETE and UPDATE statements that changed more than 40960 rows.
2. Change the makefile so that it no longer requires GNUmake extensions
3. Fix the --enable-threadsafe option on the configure script
4. Fix a code generator bug that occurs when the left-hand side of an IN operator is constant and the right-hand side is a SELECT statement
5. The PRAGMA synchronous=off statement now disables syncing of the master journal file in addition to the normal rollback journals
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.2.6 On 2005-09-17
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_2_6.html*
## SQLite Release 3.2.6 On 2005-09-17
1. Fix a bug that can cause database corruption if a VACUUM (or autovacuum) fails and is rolled back on a database that is larger than 1GiB
2. LIKE optimization now works for columns with COLLATE NOCASE
3. ORDER BY and GROUP BY now use bounded memory
4. Added support for COUNT(DISTINCT expr)
5. Change the way SUM() handles NULL values in order to comply with the SQL standard
6. Use fdatasync() instead of fsync() where possible in order to speed up commits slightly
7. Use of the CROSS keyword in a join turns off the table reordering optimization
8. Added the experimental and undocumented EXPLAIN QUERY PLAN capability
9. Use the unicode API in Windows
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.2.7 On 2005-09-24
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_2_7.html*
## SQLite Release 3.2.7 On 2005-09-24
1. GROUP BY now considers NULLs to be equal again, as it should
2. Now compiles on Solaris and OpenBSD and other Unix variants that lack the fdatasync() function
3. Now compiles on MSVC++6 again
4. Fix uninitialized variables causing malfunctions for various obscure queries
5. Correctly compute a LEFT OUTER JOINs that is constrained on the left table only
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.2.8 On 2005-12-19
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_2_8.html*
## SQLite Release 3.2.8 On 2005-12-19
1. Fix an obscure bug that can cause database corruption under the following unusual circumstances: A large INSERT or UPDATE statement which is part of an even larger transaction fails due to a uniqueness constraint but the containing transaction commits.
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.20.0 On 2017-08-01
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_20_0.html*
## SQLite Release 3.20.0 On 2017-08-01
1. Update the text of error messages returned by [sqlite3_errmsg()](../c3ref/errcode.md) for some error codes.
2. Add new [pointer passing interfaces](../bindptr.md).
3. Backwards-incompatible changes to some extensions in order to take advantage of the improved security offered by the new [pointer passing interfaces](../bindptr.md):
1. [Extending FTS5](../fts5.md#extending_fts5) → requires [sqlite3_bind_pointer()](../c3ref/bind_blob.md) to find the fts5_api pointer.
2. [carray(PTR,N)](../carray.md) → requires [sqlite3_bind_pointer()](../c3ref/bind_blob.md) to set the PTR parameter.
3. [remember(V,PTR)](https://sqlite.org/src/file/ext/misc/remember.c) → requires [sqlite3_bind_pointer()](../c3ref/bind_blob.md) to set the PTR parameter.
4. Added the [SQLITE_STMT virtual table](../stmt.md) extension.
5. Added the [COMPLETION extension](../completion.md) - designed to suggest tab-completions for interactive user interfaces. This is a work in progress. Expect further enhancements in future releases.
6. Added the [UNION virtual table](../unionvtab.md) extension.
7. The built-in [date and time functions](../lang_datefunc.md) have been enhanced so that they can be used in [CHECK constraints](../lang_createtable.md#ckconst), in [indexes on expressions](../expridx.md), and in the WHERE clauses of [partial indexes](../partialindex.md), provided that they do not use the 'now', 'localtime', or 'utc' keywords. [More information](../deterministic.md#dtexception).
8. Added the [sqlite3_prepare_v3()](../c3ref/prepare.md) and [sqlite3_prepare16_v3()](../c3ref/prepare.md) interfaces with the extra "prepFlags" parameters.
9. Provide the [SQLITE_PREPARE_PERSISTENT](../c3ref/c_prepare_dont_log.md#sqlitepreparepersistent) flag for [sqlite3_prepare_v3()](../c3ref/prepare.md) and use it to limit [lookaside memory](../malloc.md#lookaside) misuse by [FTS3](../fts3.md), [FTS5](../fts5.md), and the [R-Tree extension](../rtree.md).
10. Added the [PRAGMA secure_delete=FAST](../pragma.md#pragma_secure_delete) command. When secure_delete is set to FAST, old content is overwritten with zeros as long as that does not increase the amount of I/O. Deleted content might still persist on the [free-page list](../fileformat2.md#freelist) but will be purged from all b-tree pages.
11. Enhancements to the [command-line shell](../cli.md):
1. Add support for tab-completion using the [COMPLETION extension](../completion.md), for both readline and linenoise.
2. Add the ".cd" command.
3. Enhance the "[.schema](../cli.md#dschema)" command to show the schema of all attached databases.
4. Enhance "[.tables](../cli.md#dtables)" so that it shows the schema names for all attached if the name is anything other than "main".
5. The "[.import](../cli.md#csv)" command ignores an initial UTF-8 BOM.
6. Added the "--newlines" option to the "[.dump](../cli.md#dump)" command to cause U+000a and U+000d characters to be output literally rather than escaped using the [replace()](../lang_corefunc.md#replace) function.
12. Query planner enhancements:
1. When generating individual loops for each ORed term of an OR scan, move any constant WHERE expressions outside of the loop, as is done for top-level loops.
2. The query planner examines the values of bound parameters to help determine if a partial index is usable.
3. When deciding between two plans with the same estimated cost, bias the selection toward the one that does not use the sorter.
4. Evaluate WHERE clause constraints involving correlated subqueries last, in the hope that they never have be evaluated at all.
5. Do not use the [flattening optimization](../optoverview.md#flattening) for a sub-query on the RHS of a LEFT JOIN if that subquery reads data from a [virtual table](../vtab.md) as doing so prevents the query planner from creating [automatic indexes](../optoverview.md#autoindex) on the results of the sub-query, which can slow down the query.
13. Add [SQLITE_STMTSTATUS_REPREPARE](../c3ref/c_stmtstatus_counter.md#sqlitestmtstatusreprepare), [SQLITE_STMTSTATUS_RUN](../c3ref/c_stmtstatus_counter.md#sqlitestmtstatusrun), and [SQLITE_STMTSTATUS_MEMUSED](../c3ref/c_stmtstatus_counter.md#sqlitestmtstatusmemused) options for the [sqlite3_stmt_status()](../c3ref/stmt_status.md) interface.
14. Provide [PRAGMA functions](../pragma.md#pragfunc) for [PRAGMA integrity_check](../pragma.md#pragma_integrity_check), [PRAGMA quick_check](../pragma.md#pragma_quick_check), and [PRAGMA foreign_key_check](../pragma.md#pragma_foreign_key_check).
15. Add the -withoutnulls option to the [TCL interface eval method](../tclsqlite.md#eval).
16. Enhance the [sqlite3_analyzer.exe](../sqlanalyze.md) utility program so that it shows the number of bytes of metadata on btree pages.
17. The [SQLITE_DBCONFIG_ENABLE_QPSG](../c3ref/c_dbconfig_defensive.md#sqlitedbconfigenableqpsg) run-time option and the [SQLITE_ENABLE_QPSG](../compile.md#enable_qpsg) compile-time option enable the [query planner stability guarantee](../queryplanner-ng.md#qpstab). See also ticket [892fc34f173e99d8](https://sqlite.org/src/info/892fc34f173e99d8)
18. Miscellaneous optimizations result in a 2% reduction in [CPU cycles used](../cpu.md).
**Bug Fixes:**
19. Fix the behavior of [sqlite3_column_name()](../c3ref/column_name.md) for queries that use the [flattening optimization](../optoverview.md#flattening) so that the result is consistent with other queries that do not use that optimization, and with PostgreSQL, MySQL, and SQLServer. Ticket [de3403bf5ae](https://sqlite.org/src/info/de3403bf5ae).
20. Fix the query planner so that it knows not to use [automatic indexes](../optoverview.md#autoindex) on the right table of LEFT JOIN if the WHERE clause uses the [IS operator](../lang_expr.md#isisnot). Fix for [ce68383bf6aba](https://sqlite.org/src/info/ce68383bf6aba).
21. Ensure that the query planner knows that any column of a [flattened](../optoverview.md#flattening) LEFT JOIN can be NULL even if that column is labeled with "NOT NULL". Fix for ticket [892fc34f173e99d8](https://sqlite.org/src/info/892fc34f173e99d8).
22. Fix rare false-positives in [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) when run on a database connection with [attached databases](../lang_attach.md). Ticket [a4e06e75a9ab61a12](https://sqlite.org/src/info/a4e06e75a9ab61a12)
23. Fix a bug (discovered by OSSFuzz) that causes an assertion fault if certain dodgy CREATE TABLE declarations are used. Ticket [bc115541132dad136](https://sqlite.org/src/info/bc115541132dad136)
**Hashes:**
24. SQLITE_SOURCE_ID: "2017-08-01 13:24:15 9501e22dfeebdcefa783575e47c60b514d7c2e0cad73b2a496c0bc4b680900a8"
25. SHA3-256 for sqlite3.c: 79b7f3b977360456350219cba0ba0e5eb55910565eab68ea83edda2f968ebe95
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.20.1 On 2017-08-24
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_20_1.html*
## SQLite Release 3.20.1 On 2017-08-24
**Prior changes from version 3.20.0 (2017-08-01):**
1. Update the text of error messages returned by [sqlite3_errmsg()](../c3ref/errcode.md) for some error codes.
2. Add new [pointer passing interfaces](../bindptr.md).
3. Backwards-incompatible changes to some extensions in order to take advantage of the improved security offered by the new [pointer passing interfaces](../bindptr.md):
1. [Extending FTS5](../fts5.md#extending_fts5) → requires [sqlite3_bind_pointer()](../c3ref/bind_blob.md) to find the fts5_api pointer.
2. [carray(PTR,N)](../carray.md) → requires [sqlite3_bind_pointer()](../c3ref/bind_blob.md) to set the PTR parameter.
3. [remember(V,PTR)](https://sqlite.org/src/file/ext/misc/remember.c) → requires [sqlite3_bind_pointer()](../c3ref/bind_blob.md) to set the PTR parameter.
4. Added the [SQLITE_STMT virtual table](../stmt.md) extension.
5. Added the [COMPLETION extension](../completion.md) - designed to suggest tab-completions for interactive user interfaces. This is a work in progress. Expect further enhancements in future releases.
6. Added the [UNION virtual table](../unionvtab.md) extension.
7. The built-in [date and time functions](../lang_datefunc.md) have been enhanced so that they can be used in [CHECK constraints](../lang_createtable.md#ckconst), in [indexes on expressions](../expridx.md), and in the WHERE clauses of [partial indexes](../partialindex.md), provided that they do not use the 'now', 'localtime', or 'utc' keywords. [More information](../deterministic.md#dtexception).
8. Added the [sqlite3_prepare_v3()](../c3ref/prepare.md) and [sqlite3_prepare16_v3()](../c3ref/prepare.md) interfaces with the extra "prepFlags" parameters.
9. Provide the [SQLITE_PREPARE_PERSISTENT](../c3ref/c_prepare_dont_log.md#sqlitepreparepersistent) flag for [sqlite3_prepare_v3()](../c3ref/prepare.md) and use it to limit [lookaside memory](../malloc.md#lookaside) misuse by [FTS3](../fts3.md), [FTS5](../fts5.md), and the [R-Tree extension](../rtree.md).
10. Added the [PRAGMA secure_delete=FAST](../pragma.md#pragma_secure_delete) command. When secure_delete is set to FAST, old content is overwritten with zeros as long as that does not increase the amount of I/O. Deleted content might still persist on the [free-page list](../fileformat2.md#freelist) but will be purged from all b-tree pages.
11. Enhancements to the [command-line shell](../cli.md):
1. Add support for tab-completion using the [COMPLETION extension](../completion.md), for both readline and linenoise.
2. Add the ".cd" command.
3. Enhance the "[.schema](../cli.md#dschema)" command to show the schema of all attached databases.
4. Enhance "[.tables](../cli.md#dtables)" so that it shows the schema names for all attached if the name is anything other than "main".
5. The "[.import](../cli.md#csv)" command ignores an initial UTF-8 BOM.
6. Added the "--newlines" option to the "[.dump](../cli.md#dump)" command to cause U+000a and U+000d characters to be output literally rather than escaped using the [replace()](../lang_corefunc.md#replace) function.
12. Query planner enhancements:
1. When generating individual loops for each ORed term of an OR scan, move any constant WHERE expressions outside of the loop, as is done for top-level loops.
2. The query planner examines the values of bound parameters to help determine if a partial index is usable.
3. When deciding between two plans with the same estimated cost, bias the selection toward the one that does not use the sorter.
4. Evaluate WHERE clause constraints involving correlated subqueries last, in the hope that they never have be evaluated at all.
5. Do not use the [flattening optimization](../optoverview.md#flattening) for a sub-query on the RHS of a LEFT JOIN if that subquery reads data from a [virtual table](../vtab.md) as doing so prevents the query planner from creating [automatic indexes](../optoverview.md#autoindex) on the results of the sub-query, which can slow down the query.
13. Add [SQLITE_STMTSTATUS_REPREPARE](../c3ref/c_stmtstatus_counter.md#sqlitestmtstatusreprepare), [SQLITE_STMTSTATUS_RUN](../c3ref/c_stmtstatus_counter.md#sqlitestmtstatusrun), and [SQLITE_STMTSTATUS_MEMUSED](../c3ref/c_stmtstatus_counter.md#sqlitestmtstatusmemused) options for the [sqlite3_stmt_status()](../c3ref/stmt_status.md) interface.
14. Provide [PRAGMA functions](../pragma.md#pragfunc) for [PRAGMA integrity_check](../pragma.md#pragma_integrity_check), [PRAGMA quick_check](../pragma.md#pragma_quick_check), and [PRAGMA foreign_key_check](../pragma.md#pragma_foreign_key_check).
15. Add the -withoutnulls option to the [TCL interface eval method](../tclsqlite.md#eval).
16. Enhance the [sqlite3_analyzer.exe](../sqlanalyze.md) utility program so that it shows the number of bytes of metadata on btree pages.
17. The [SQLITE_DBCONFIG_ENABLE_QPSG](../c3ref/c_dbconfig_defensive.md#sqlitedbconfigenableqpsg) run-time option and the [SQLITE_ENABLE_QPSG](../compile.md#enable_qpsg) compile-time option enable the [query planner stability guarantee](../queryplanner-ng.md#qpstab). See also ticket [892fc34f173e99d8](https://sqlite.org/src/info/892fc34f173e99d8)
18. Miscellaneous optimizations result in a 2% reduction in [CPU cycles used](../cpu.md).
**Bug Fixes:**
19. Fix the behavior of [sqlite3_column_name()](../c3ref/column_name.md) for queries that use the [flattening optimization](../optoverview.md#flattening) so that the result is consistent with other queries that do not use that optimization, and with PostgreSQL, MySQL, and SQLServer. Ticket [de3403bf5ae](https://sqlite.org/src/info/de3403bf5ae).
20. Fix the query planner so that it knows not to use [automatic indexes](../optoverview.md#autoindex) on the right table of LEFT JOIN if the WHERE clause uses the [IS operator](../lang_expr.md#isisnot). Fix for [ce68383bf6aba](https://sqlite.org/src/info/ce68383bf6aba).
21. Ensure that the query planner knows that any column of a [flattened](../optoverview.md#flattening) LEFT JOIN can be NULL even if that column is labeled with "NOT NULL". Fix for ticket [892fc34f173e99d8](https://sqlite.org/src/info/892fc34f173e99d8).
22. Fix rare false-positives in [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) when run on a database connection with [attached databases](../lang_attach.md). Ticket [a4e06e75a9ab61a12](https://sqlite.org/src/info/a4e06e75a9ab61a12)
23. Fix a bug (discovered by OSSFuzz) that causes an assertion fault if certain dodgy CREATE TABLE declarations are used. Ticket [bc115541132dad136](https://sqlite.org/src/info/bc115541132dad136)
**Changes in this specific patch release, version 3.20.1 (2017-08-24):**
1. Fix a potential memory leak in the new [sqlite3_result_pointer()](../c3ref/result_blob.md) interface. Ticket [7486aa54b968e9b5](https://sqlite.org/src/info/7486aa54b968e9b5).
**Hashes:**
2. SQLITE_SOURCE_ID: "2017-08-24 16:21:36 8d3a7ea6c5690d6b7c3767558f4f01b511c55463e3f9e64506801fe9b74dce34"
3. SHA3-256 for sqlite3.c: 93b1a6d69b48dc39697d1d3a1e4c30b55da0bdd2cad0c054462f91081832954a
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.21.0 On 2017-10-24
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_21_0.html*
## SQLite Release 3.21.0 On 2017-10-24
1. Take advantage of the atomic-write capabilities in the [F2FS filesystem](https://en.wikipedia.org/wiki/F2FS) when available, for greatly reduced transaction overhead. This currently requires the [SQLITE_ENABLE_BATCH_ATOMIC_WRITE](../compile.md#enable_batch_atomic_write) compile-time option.
2. Allow [ATTACH](../lang_attach.md) and [DETACH](../lang_detach.md) commands to work inside of a transaction.
3. Allow [WITHOUT ROWID virtual tables](../vtab.md#worid) to be writable if the PRIMARY KEY contains exactly one column.
4. The "fsync()" that occurs after the header is written in a WAL reset now uses the sync settings for checkpoints. This means it will use a "fullfsync" on macs if [PRAGMA checkpoint_fullfsync](../pragma.md#pragma_checkpoint_fullfsync) set on.
5. The [sqlite3_sourceid()](../c3ref/libversion.md) function tries to detect if the source code has been modified from what is checked into version control and if there are modifications, the last four characters of the version hash are shown as "alt1" or "alt2". The objective is to detect accidental and/or careless edits. A forger can subvert this feature.
6. Improved de-quoting of column names for [CREATE TABLE AS](../lang_createtable.md#createtabas) statements with an aggregate query on the right-hand side.
7. Fewer "stat()" system calls issued by the unix VFS.
8. Enhanced the [LIKE optimization](../optoverview.md#like_opt) so that it works with an [ESCAPE](../lang_expr.md#like) clause.
9. Enhanced [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) and [PRAGMA quick_check](../pragma.md#pragma_quick_check) to detect obscure row corruption that they were formerly missing. Also update both pragmas so that they return error text rather than SQLITE_CORRUPT when encountering corruption in [records](../fileformat2.md#record_format).
10. The query planner now prefers to implement FROM-clause subqueries using [co-routines](../optoverview.md#coroutines) rather using the [query flattener](../optoverview.md#flattening) optimization. Support for the use of co-routines for subqueries may no longer be disabled.
11. Pass information about !=, IS, IS NOT, NOT NULL, and IS NULL constraints into the [xBestIndex](../vtab.md#xbestindex) method of virtual tables.
12. Enhanced the [CSV virtual table](../csv.md) so that it accepts the last row of input if the final new-line character is missing.
13. Remove the rarely-used "scratch" memory allocator. Replace it with the [SQLITE_CONFIG_SMALL_MALLOC](../c3ref/c_config_covering_index_scan.md#sqliteconfigsmallmalloc) configuration setting that gives SQLite a hint that large memory allocations should be avoided when possible.
14. Added the [swarm virtual table](https://sqlite.org/src/file/ext/misc/unionvtab.c) to the existing union virtual table extension.
15. Added the [sqlite_dbpage virtual table](https://sqlite.org/src/file/src/dbpage.c) for providing direct access to pages of the database file. The source code is built into the [amalgamation](../amalgamation.md) and is activated using the [-DSQLITE_ENABLE_DBPAGE_VTAB](../compile.md#enable_dbpage_vtab) compile-time option.
16. Add a new type of fts5vocab virtual table - "instance" - that provides direct access to an FTS5 full-text index at the lowest possible level.
17. Remove a call to rand_s() in the Windows VFS since it was causing problems in Firefox on some older laptops.
18. The [src/shell.c](https://sqlite.org/src/finfo?name=src/shell.c) source code to the [command-line shell](../cli.md) is no longer under version control. That file is now generated as part of the build process.
19. Miscellaneous [microoptimizations](../cpu.md#microopt) reduce CPU usage by about 2.1%.
20. Bug fixes:
1. Fix a faulty assert() statement discovered by OSSFuzz. Ticket [cb91bf4290c211d](https://sqlite.org/src/info/cb91bf4290c211d)
2. Fix an obscure memory leak in [sqlite3_result_pointer()](../c3ref/result_blob.md). Ticket [7486aa54b968e9b](https://sqlite.org/src/info/7486aa54b968e9b)
3. Avoid a possible use-after-free error by deferring schema resets until after the query planner has finished running. Ticket [be436a7f4587ce5](https://sqlite.org/src/info/be436a7f4587ce5)
4. Only use indexes-on-expressions to optimize ORDER BY or GROUP BY if the COLLATE is correct. Ticket [e20dd54ab0e4383](https://sqlite.org/src/info/e20dd54ab0e4383)
5. Fix an assertion fault that was coming up when the expression in an index-on-expressions is really a constant. Ticket [aa98619ad08ddca](https://sqlite.org/src/info/aa98619ad08ddca)
6. Fix an assertion fault that could occur following [PRAGMA reverse_unordered_selects](../pragma.md#pragma_reverse_unordered_selects). Ticket [cb91bf4290c211d](https://sqlite.org/src/info/cb91bf4290c211d)
7. Fix a segfault that can occur for queries that use table-valued functions in an IN or EXISTS subquery. Ticket [b899b6042f97f5](https://sqlite.org/src/info/b899b6042f97f5)
8. Fix a potential integer overflow problem when compiling a particular horrendous common table expression. This was another problem discovered by OSSFuzz. Check-in [6ee8cb6ae5](https://sqlite.org/src/info/6ee8cb6ae5).
9. Fix a potential out-of-bound read when querying a corrupt database file, a problem detected by Natalie Silvanovich of Google Project Zero. Check-in [04925dee41a21f](https://sqlite.org/src/info/04925dee41a21f).
**Hashes:**
21. SQLITE_SOURCE_ID: "2017-10-24 18:55:49 1a584e499906b5c87ec7d43d4abce641fdf017c42125b083109bc77c4de48827"
22. SHA3-256 for sqlite3.c: 84c181c0283d0320f488357fc8aab51898370c157601459ebee49d779036fe03
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.22.0 On 2018-01-22
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_22_0.html*
## SQLite Release 3.22.0 On 2018-01-22
1. The output of [sqlite3_trace_v2()](../c3ref/trace_v2.md) now shows each individual SQL statement run within a trigger.
2. Add the ability to read from [WAL mode](../wal.md) databases even if the application lacks write permission on the database and its containing directory, as long as the -shm and -wal files exist in that directory.
3. Added the [rtreecheck()](../rtree.md#rtreecheck) scalar SQL function to the [R-Tree extension](../rtree.md).
4. Added the [sqlite3_vtab_nochange()](../c3ref/vtab_nochange.md) and [sqlite3_value_nochange()](../c3ref/value_blob.md) interfaces to help virtual table implementations optimize UPDATE operations.
5. Added the [sqlite3_vtab_collation()](../c3ref/vtab_collation.md) interface.
6. Added support for the ["^" initial token syntax](../fts5.md#carrotq) in FTS5.
7. New extensions:
1. The [Zipfile virtual table](../zipfile.md) can read and write a [ZIP Archive](https://en.wikipedia.org/wiki/Zip_(file_format)).
2. Added the fsdir(PATH) [table-valued function](../vtab.md#tabfunc2) to the [fileio.c](https://sqlite.org/src/file/ext/misc/fileio.c) extension, for listing the files in a directory.
3. The [sqlite_btreeinfo](https://sqlite.org/src/file/ext/misc/btreeinfo.c) eponymous virtual table for introspecting and estimating the sizes of the btrees in a database.
4. The [Append VFS](https://sqlite.org/src/file/ext/misc/appendvfs.c) is a [VFS shim](../vfs.md#shim) that allows an SQLite database to be appended to some other file. This allows (for example) a database to be appended to an executable that then opens and reads the database.
8. Query planner enhancements:
1. The optimization that uses an index to quickly compute an aggregate min() or max() is extended to work with [indexes on expressions](../expridx.md).
2. The decision of whether to implement a FROM-clause subquery as a co-routine or using [query flattening](../optoverview.md#flattening) now considers whether the result set of the outer query is "complex" (if it contains functions or expression subqueries). A complex result set biases the decision toward the use of co-routines.
3. The planner avoids query plans that use indexes with unknown collating functions.
4. The planner omits unused LEFT JOINs even if they are not the right-most joins of a query.
9. Other performance optimizations:
1. A smaller and faster implementation of text to floating-point conversion subroutine: sqlite3AtoF().
2. The [Lemon parser generator](../lemon.md) creates a faster parser.
3. Use the strcspn() C-library routine to speed up the LIKE and GLOB operators.
10. Improvements to the [command-line shell](../cli.md):
1. The ".schema" command shows the structure of virtual tables.
2. Added support for reading and writing [SQLite Archive](../sqlar.md) files using the [.archive command](../cli.md#sqlar).
3. Added the experimental [.expert command](../cli.md#expert)
4. Added the ".eqp trigger" variant of the ".eqp" command
5. Enhance the ".lint fkey-indexes" command so that it works with [WITHOUT ROWID](../withoutrowid.md) tables.
6. If the filename argument to the shell is a ZIP archive rather than an SQLite database, then the shell automatically opens that ZIP archive using the [Zipfile virtual table](../zipfile.md).
7. Added the [edit() SQL function](../cli.md#editfunc).
8. Added the [.excel command](../cli.md#exexcel*) to simplify exporting database content to a spreadsheet.
9. Databases are opened using [Append VFS](https://sqlite.org/src/file/ext/misc/appendvfs.c) when the --append flag is used on the command line or with the .open command.
11. Enhance the [SQLITE_ENABLE_UPDATE_DELETE_LIMIT](../compile.md#enable_update_delete_limit) compile-time option so that it works for [WITHOUT ROWID](../withoutrowid.md) tables.
12. Provide the [sqlite_offset(X)](../lang_corefunc.md#sqlite_offset) SQL function that returns the byte offset into the database file to the beginning of the record holding value X, when compiling with [-DSQLITE_ENABLE_OFFSET_SQL_FUNC](../compile.md#enable_offset_sql_func).
13. Bug fixes:
1. Infinite loop on an UPDATE that uses an OR operator in the WHERE clause. Problem introduced with 3.17.0 and reported on the mailing list about one year later. Ticket [47b2581aa9bfecec](https://sqlite.org/src/info/47b2581aa9bfecec).
2. Incorrect query results when the skip-ahead-distinct optimization is used. Ticket [ef9318757b152e3a](https://sqlite.org/src/info/ef9318757b152e3a).
3. Incorrect query results on a join with a ORDER BY DESC. Ticket [123c9ba32130a6c9](https://sqlite.org/src/info/123c9ba32130a6c9).
4. Inconsistent result set column names between CREATE TABLE AS and a simple SELECT. Ticket [3b4450072511e621](https://sqlite.org/src/info/3b4450072511e621)
5. Assertion fault when doing REPLACE on an index on an expression. Ticket [dc3f932f5a147771](https://sqlite.org/src/info/dc3f932f5a147771)
6. Assertion fault when doing an IN operator on a constant index. Ticket [aa98619ad08ddcab](https://sqlite.org/src/info/aa98619ad08ddcab)
**Hashes:**
14. SQLITE_SOURCE_ID: "2018-01-22 18:45:57 0c55d179733b46d8d0ba4d88e01a25e10677046ee3da1d5b1581e86726f2171d"
15. SHA3-256 for sqlite3.c: 206df47ebc49cd1710ac0dd716ce5de5854826536993f4feab7a49d136b85069
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.23.0 On 2018-04-02
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_23_0.html*
## SQLite Release 3.23.0 On 2018-04-02
1. Add the [sqlite3_serialize()](../c3ref/serialize.md) and [sqlite3_deserialize()](../c3ref/deserialize.md) interfaces when the [SQLITE_ENABLE_DESERIALIZE](../compile.md#enable_deserialize) compile-time option is used.
2. Recognize TRUE and FALSE as constants. (For compatibility, if there exist columns named "true" or "false", then the identifiers refer to the columns rather than Boolean constants.)
3. Support operators IS TRUE, IS FALSE, IS NOT TRUE, and IS NOT FALSE.
4. Added the [SQLITE_DBSTATUS_CACHE_SPILL](../c3ref/c_dbstatus_options.md#sqlitedbstatuscachespill) option to [sqlite3_db_status()](../c3ref/db_status.md) for reporting the number of cache spills that have occurred.
5. The "alternate-form-2" flag ("!") on the [built-in printf](../printf.md) implementation now causes string substitutions to measure the width and precision in characters instead of bytes.
6. If the [xColumn](../vtab.md#xcolumn) method in a [virtual table](../vtab.md) implementation returns an error message using [sqlite3_result_error()](../c3ref/result_blob.md) then give that error message preference over internally-generated messages.
7. Added the -A command-line option to the [CLI](../cli.md) to make it easier to manage [SQLite Archive files](../sqlar.md).
8. Add support for INSERT OR REPLACE, INSERT OR IGNORE, and UPDATE OR REPLACE in the [Zipfile virtual table](../zipfile.md).
9. Enhance the [sqlite3changeset_apply()](../session/sqlite3changeset_apply.md) interface so that it is hardened against attacks from deliberately corrupted [changeset](../sessionintro.md#changeset) objects.
10. Added the [sqlite3_normalize()](https://sqlite.org/src/file/ext/misc/normalize.c) extension function.
11. Query optimizer enhancements:
1. Improve the [omit-left-join optimization](../optoverview.md#omitnoopjoin) so that it works in cases where the right-hand table is UNIQUE but not necessarily NOT NULL.
2. Improve the [push-down optimization](../optoverview.md#pushdown) so that it works for many LEFT JOINs.
3. Add the [LEFT JOIN strength reduction optimization](../optoverview.md#leftjoinreduction) that converts a LEFT JOIN into an ordinary JOIN if there exist terms in the WHERE clause that would prevent the extra all-NULL row of the LEFT JOIN from appearing in the output set.
4. Avoid unnecessary writes to the sqlite_sequence table when an [AUTOINCREMENT](../autoinc.md) table is updated with an rowid that is less than the maximum.
12. Bug fixes:
1. Fix the parser to accept valid [row value](../rowvalue.md) syntax. Ticket [7310e2fb3d046a5](https://sqlite.org/src/info/7310e2fb3d046a5)
2. Fix the query planner so that it takes into account dependencies in the arguments to table-valued functions in subexpressions in the WHERE clause. Ticket [80177f0c226ff54](https://sqlite.org/src/info/80177f0c226ff54)
3. Fix incorrect result with complex OR-connected WHERE and STAT4. Ticket [ec32177c99ccac2](https://sqlite.org/src/info/ec32177c99ccac2)
4. Fix potential corruption in [indexes on expressions](../expridx.md) due to automatic datatype conversions. Ticket [343634942dd54ab](https://sqlite.org/src/info/343634942dd54ab)
5. Assertion fault in FTS4. Ticket [d6ec09eccf68cfc](https://sqlite.org/src/info/d6ec09eccf68cfc)
6. Incorrect result on the less-than operator in [row values](../rowvalue.md). Ticket [f484b65f3d62305](https://sqlite.org/src/info/f484b65f3d62305)
7. Always interpret non-zero floating-point values as TRUE, even if the integer part is zero. Ticket [36fae083b450e3a](https://sqlite.org/src/info/36fae083b450e3a)
8. Fix an issue in the fsdir(PATH) [table-valued function](../vtab.md#tabfunc2) to the [fileio.c](https://sqlite.org/src/file/ext/misc/fileio.c) extension, that caused a segfault if the fsdir() table was used as the inner table of a join. Problem reported on the mailing list and fixed by check-in [7ce4e71c1b7251be](https://sqlite.org/src/info/7ce4e71c1b7251be)
9. Issue an error rather instead of an assertion-fault or null-pointer dereference when the sqlite_master table is corrupted so that the sqlite_sequence table root page is really a btree-index page. Check-in [525deb7a67fbd647](https://sqlite.org/src/info/525deb7a67fbd647)
10. Fix the [ANALYZE](../lang_analyze.md) command so that it computes statistics on tables whose names begin with "sqlite". Check-in [0249d9aecf69948d](https://sqlite.org/src/info/0249d9aecf69948d)
13. Additional fixes for issues detected by [OSSFuzz](https://github.com/google/oss-fuzz):
1. Fix a possible infinite loop on VACUUM for corrupt database files. Check-in [27754b74ddf64](https://sqlite.org/src/info/27754b74ddf64)
2. Disallow [parameters](../lang_expr.md#varparam) in the [WITH clause](../lang_with.md) of triggers and views. Check-in [b918d4b4e546d](https://sqlite.org/src/info/b918d4b4e546d)
3. Fix a potential memory leak in [row value](../rowvalue.md) processing. Check-in [2df6bbf1b8ca8](https://sqlite.org/src/info/2df6bbf1b8ca8)
4. Improve the performance of the [replace() SQL function](../lang_corefunc.md#replace) for cases where there are many substitutions on megabyte-sized strings, in an attempt to avoid OSSFuzz timeouts during testing. Check-in [fab2c2b07b5d3](https://sqlite.org/src/info/fab2c2b07b5d3)
5. Provide an appropriate error message when the sqlite_master table contains a CREATE TABLE AS statement. Formerly this caused either an assertion fault or null pointer dereference. Problem found by OSSFuzz on the GDAL project. Check-in [d75e67654aa96](https://sqlite.org/src/info/d75e67654aa96)
6. Incorrect assert() statement removed. Check-in [823779d31eb09cda](https://sqlite.org/src/info/823779d31eb09cda).
7. Fix a problem with using the [LIKE optimization](../optoverview.md#like_opt) on an [INTEGER PRIMARY KEY](../lang_createtable.md#rowid). Check-in [b850dd159918af56](https://sqlite.org/src/info/b850dd159918af56).
**Hashes:**
14. SQLITE_SOURCE_ID: "2018-04-02 11:04:16 736b53f57f70b23172c30880186dce7ad9baa3b74e3838cae5847cffb98f5cd2"
15. SHA3-256 for sqlite3.c: 4bed3dc2dc905ff55e2c21fd2725551fc0ca50912a9c96c6af712a4289cb24fa
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.23.1 On 2018-04-10
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_23_1.html*
## SQLite Release 3.23.1 On 2018-04-10
**Prior changes from version 3.23.0 (2018-04-02):**
1. Add the [sqlite3_serialize()](../c3ref/serialize.md) and [sqlite3_deserialize()](../c3ref/deserialize.md) interfaces when the [SQLITE_ENABLE_DESERIALIZE](../compile.md#enable_deserialize) compile-time option is used.
2. Recognize TRUE and FALSE as constants. (For compatibility, if there exist columns named "true" or "false", then the identifiers refer to the columns rather than Boolean constants.)
3. Support operators IS TRUE, IS FALSE, IS NOT TRUE, and IS NOT FALSE.
4. Added the [SQLITE_DBSTATUS_CACHE_SPILL](../c3ref/c_dbstatus_options.md#sqlitedbstatuscachespill) option to [sqlite3_db_status()](../c3ref/db_status.md) for reporting the number of cache spills that have occurred.
5. The "alternate-form-2" flag ("!") on the [built-in printf](../printf.md) implementation now causes string substitutions to measure the width and precision in characters instead of bytes.
6. If the [xColumn](../vtab.md#xcolumn) method in a [virtual table](../vtab.md) implementation returns an error message using [sqlite3_result_error()](../c3ref/result_blob.md) then give that error message preference over internally-generated messages.
7. Added the -A command-line option to the [CLI](../cli.md) to make it easier to manage [SQLite Archive files](../sqlar.md).
8. Add support for INSERT OR REPLACE, INSERT OR IGNORE, and UPDATE OR REPLACE in the [Zipfile virtual table](../zipfile.md).
9. Enhance the [sqlite3changeset_apply()](../session/sqlite3changeset_apply.md) interface so that it is hardened against attacks from deliberately corrupted [changeset](../sessionintro.md#changeset) objects.
10. Added the [sqlite3_normalize()](https://sqlite.org/src/file/ext/misc/normalize.c) extension function.
11. Query optimizer enhancements:
1. Improve the [omit-left-join optimization](../optoverview.md#omitnoopjoin) so that it works in cases where the right-hand table is UNIQUE but not necessarily NOT NULL.
2. Improve the [push-down optimization](../optoverview.md#pushdown) so that it works for many LEFT JOINs.
3. Add the [LEFT JOIN strength reduction optimization](../optoverview.md#leftjoinreduction) that converts a LEFT JOIN into an ordinary JOIN if there exist terms in the WHERE clause that would prevent the extra all-NULL row of the LEFT JOIN from appearing in the output set.
4. Avoid unnecessary writes to the sqlite_sequence table when an [AUTOINCREMENT](../autoinc.md) table is updated with an rowid that is less than the maximum.
12. Bug fixes:
1. Fix the parser to accept valid [row value](../rowvalue.md) syntax. Ticket [7310e2fb3d046a5](https://sqlite.org/src/info/7310e2fb3d046a5)
2. Fix the query planner so that it takes into account dependencies in the arguments to table-valued functions in subexpressions in the WHERE clause. Ticket [80177f0c226ff54](https://sqlite.org/src/info/80177f0c226ff54)
3. Fix incorrect result with complex OR-connected WHERE and STAT4. Ticket [ec32177c99ccac2](https://sqlite.org/src/info/ec32177c99ccac2)
4. Fix potential corruption in [indexes on expressions](../expridx.md) due to automatic datatype conversions. Ticket [343634942dd54ab](https://sqlite.org/src/info/343634942dd54ab)
5. Assertion fault in FTS4. Ticket [d6ec09eccf68cfc](https://sqlite.org/src/info/d6ec09eccf68cfc)
6. Incorrect result on the less-than operator in [row values](../rowvalue.md). Ticket [f484b65f3d62305](https://sqlite.org/src/info/f484b65f3d62305)
7. Always interpret non-zero floating-point values as TRUE, even if the integer part is zero. Ticket [36fae083b450e3a](https://sqlite.org/src/info/36fae083b450e3a)
8. Fix an issue in the fsdir(PATH) [table-valued function](../vtab.md#tabfunc2) to the [fileio.c](https://sqlite.org/src/file/ext/misc/fileio.c) extension, that caused a segfault if the fsdir() table was used as the inner table of a join. Problem reported on the mailing list and fixed by check-in [7ce4e71c1b7251be](https://sqlite.org/src/info/7ce4e71c1b7251be)
9. Issue an error rather instead of an assertion-fault or null-pointer dereference when the sqlite_master table is corrupted so that the sqlite_sequence table root page is really a btree-index page. Check-in [525deb7a67fbd647](https://sqlite.org/src/info/525deb7a67fbd647)
10. Fix the [ANALYZE](../lang_analyze.md) command so that it computes statistics on tables whose names begin with "sqlite". Check-in [0249d9aecf69948d](https://sqlite.org/src/info/0249d9aecf69948d)
13. Additional fixes for issues detected by [OSSFuzz](https://github.com/google/oss-fuzz):
1. Fix a possible infinite loop on VACUUM for corrupt database files. Check-in [27754b74ddf64](https://sqlite.org/src/info/27754b74ddf64)
2. Disallow [parameters](../lang_expr.md#varparam) in the [WITH clause](../lang_with.md) of triggers and views. Check-in [b918d4b4e546d](https://sqlite.org/src/info/b918d4b4e546d)
3. Fix a potential memory leak in [row value](../rowvalue.md) processing. Check-in [2df6bbf1b8ca8](https://sqlite.org/src/info/2df6bbf1b8ca8)
4. Improve the performance of the [replace() SQL function](../lang_corefunc.md#replace) for cases where there are many substitutions on megabyte-sized strings, in an attempt to avoid OSSFuzz timeouts during testing. Check-in [fab2c2b07b5d3](https://sqlite.org/src/info/fab2c2b07b5d3)
5. Provide an appropriate error message when the sqlite_master table contains a CREATE TABLE AS statement. Formerly this caused either an assertion fault or null pointer dereference. Problem found by OSSFuzz on the GDAL project. Check-in [d75e67654aa96](https://sqlite.org/src/info/d75e67654aa96)
6. Incorrect assert() statement removed. Check-in [823779d31eb09cda](https://sqlite.org/src/info/823779d31eb09cda).
7. Fix a problem with using the [LIKE optimization](../optoverview.md#like_opt) on an [INTEGER PRIMARY KEY](../lang_createtable.md#rowid). Check-in [b850dd159918af56](https://sqlite.org/src/info/b850dd159918af56).
**Changes in this specific patch release, version 3.23.1 (2018-04-10):**
1. Fix two problems in the new [LEFT JOIN strength reduction optimization](../optoverview.md#leftjoinreduction). Tickets [1e39b966ae9ee739](https://sqlite.org/src/info/1e39b966ae9ee739) and [fac496b61722daf2](https://sqlite.org/src/info/fac496b61722daf2).
2. Fix misbehavior of the FTS5 xBestIndex method. Ticket [2b8aed9f7c9e61e8](https://sqlite.org/src/info/2b8aed9f7c9e61e8).
3. Fix a harmless reference to an uninitialized virtual machine register. Ticket [093420fc0eb7cba7](https://sqlite.org/src/info/093420fc0eb7cba7).
4. Fix the [CLI](../cli.md) so that it builds with -DSQLITE_UNTESTABLE
5. Fix the [eval.c](https://sqlite.org/src/file/ext/misc/eval.c) extension so that it works with [PRAGMA empty_result_callbacks=ON](../pragma.md#pragma_empty_result_callbacks).
6. Fix the [generate_series](../series.md) virtual table so that it correctly returns no rows if any of its constraints are NULL.
7. Performance enhancements in the parser.
**Hashes:**
8. SQLITE_SOURCE_ID: "2018-04-10 17:39:29 4bb2294022060e61de7da5c227a69ccd846ba330e31626ebcd59a94efd148b3b"
9. SHA3-256 for sqlite3.c: 65750d1e506f416a0b0b9dd22d171379679c733e3460549754dc68c92705b5dc
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.24.0 On 2018-06-04
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_24_0.html*
## SQLite Release 3.24.0 On 2018-06-04
1. Add support for PostgreSQL-style [UPSERT](../lang_upsert.md).
2. Add support for [auxiliary columns in r-tree tables](../rtree.md#auxcol).
3. Add C-language APIs for discovering SQL keywords used by SQLite: [sqlite3_keyword_count()](../c3ref/keyword_check.md), [sqlite3_keyword_name()](../c3ref/keyword_check.md), and [sqlite3_keyword_check()](../c3ref/keyword_check.md).
4. Add C-language APIs for dynamic strings based on the [sqlite3_str](../c3ref/str.md) object.
5. Enhance [ALTER TABLE](../lang_altertable.md) so that it recognizes "true" and "false" as valid arguments to DEFAULT.
6. Add the sorter-reference optimization as a compile-time option. Only available if compiled with SQLITE_ENABLE_SORTER_REFERENCES.
7. Improve the format of the [EXPLAIN QUERY PLAN](../eqp.md) raw output, so that it gives better information about the query plan and about the relationships between the various components of the plan.
8. Added the [SQLITE_DBCONFIG_RESET_DATABASE](../c3ref/c_dbconfig_defensive.md#sqlitedbconfigresetdatabase) option to the [sqlite3_db_config()](../c3ref/db_config.md) API.
**[CLI](../cli.md) Enhancements:**
9. Automatically intercepts the raw [EXPLAIN QUERY PLAN](../eqp.md) output and reformats it into an ASCII-art graph.
10. Lines that begin with "#" and that are not in the middle of an SQL statement are interpreted as comments.
11. Added the --append option to the ".backup" command.
12. Added the ".dbconfig" command.
**Performance:**
13. [UPDATE](../lang_update.md) avoids unnecessary low-level disk writes when the contents of the database file do not actually change. For example, "UPDATE t1 SET x=25 WHERE y=?" generates no extra disk I/O if the value in column x is already 25. Similarly, when doing [UPDATE](../lang_update.md) on records that span multiple pages, only the subset of pages that actually change are written to disk. This is a low-level performance optimization only and does not affect the behavior of TRIGGERs or other higher level SQL structures.
14. Queries that use ORDER BY and LIMIT now try to avoid computing rows that cannot possibly come in under the LIMIT. This can greatly improve performance of ORDER BY LIMIT queries, especially when the LIMIT is small relative to the number of unrestricted output rows.
15. The [OR optimization](../optoverview.md#or_opt) is allowed to proceed even if the OR expression has also been converted into an IN expression. Uses of the OR optimization are now also [more clearly shown](../eqp.md#or-opt) in the [EXPLAIN QUERY PLAN](../eqp.md) output.
16. The query planner is more aggressive about using [automatic indexes](../optoverview.md#autoindex) for views and subqueries for which it is not possible to create a persistent index.
17. Make use of the one-pass UPDATE and DELETE query plans in the [R-Tree extension](../rtree.md) where appropriate.
18. Performance improvements in the LEMON-generated parser.
**Bug fixes:**
19. For the right-hand table of a LEFT JOIN, compute the values of expressions directly rather than loading precomputed values out of an [expression index](../expridx.md) as the expression index might not contain the correct value. Ticket [7fa8049685b50b5aeb0c2](https://sqlite.org/src/info/7fa8049685b50b5aeb0c2)
20. Do not attempt to use terms from the WHERE clause to enable indexed lookup of the right-hand table of a LEFT JOIN. Ticket [4ba5abf65c5b0f9a96a7a](https://sqlite.org/src/info/4ba5abf65c5b0f9a96a7a)
21. Fix a memory leak that can occur following a failure to open error in the [CSV virtual table](../csv.md)
22. Fix a long-standing problem wherein a corrupt schema on the [sqlite_sequence](../fileformat2.md#seqtab) table used by [AUTOINCREMENT](../autoinc.md) can lead to a crash. Ticket [d8dc2b3a58cd5dc2918a1](https://sqlite.org/src/info/d8dc2b3a58cd5dc29)
23. Fix the [json_each()](../json1.md#jeach) function so that it returns valid results on its "fullkey" column when the input is a simple value rather than an array or object.
**Hashes:**
24. SQLITE_SOURCE_ID: "2018-06-04 19:24:41 c7ee0833225bfd8c5ec2f9bf62b97c4e04d03bd9566366d5221ac8fb199a87ca"
25. SHA3-256 for sqlite3.c: 0d384704e1c66026228336d1e91771d295bf688c9c44c7a44f25a4c16c26ab3c
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.25.0 On 2018-09-15
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_25_0.html*
## SQLite Release 3.25.0 On 2018-09-15
1. Add support for [window functions](../windowfunctions.md)
2. Enhancements the [ALTER TABLE](../lang_altertable.md) command:
1. Add support for renaming columns within a table using ALTER TABLE *table* RENAME COLUMN *oldname* TO *newname*.
2. Fix table rename feature so that it also updates references to the renamed table in [triggers](../lang_createtrigger.md) and [views](../lang_createview.md).
3. Query optimizer improvements:
1. Avoid unnecessary loads of columns in an aggregate query that are not within an aggregate function and that are not part of the GROUP BY clause.
2. The IN-early-out optimization: When doing a look-up on a multi-column index and an IN operator is used on a column other than the left-most column, then if no rows match against the first IN value, check to make sure there exist rows that match the columns to the right before continuing with the next IN value.
3. Use the transitive property to try to propagate constant values within the WHERE clause. For example, convert "a=99 AND b=a" into "a=99 AND b=99".
4. Use a separate mutex on every inode in the unix [VFS](../vfs.md), rather than a single mutex shared among them all, for slightly better concurrency in multi-threaded environments.
5. Enhance the [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) command for improved detection of problems on the page freelist.
6. Output infinity as 1e999 in the ".dump" command of the [command-line shell](../cli.md).
7. Added the [SQLITE_FCNTL_DATA_VERSION](../c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntldataversion) file-control.
8. Added the [Geopoly module](../geopoly.md)
**Bug fixes:**
9. The ORDER BY LIMIT optimization might have caused an infinite loop in the byte code of the prepared statement under very obscure circumstances, due to a confluence of minor defects in the query optimizer. Fix for ticket [9936b2fa443fec03ff25](https://sqlite.org/src/info/9936b2fa443fec03ff25)
10. On an UPSERT when the order of constraint checks is rearranged, ensure that the affinity transformations on the inserted content occur before any of the constraint checks. Fix for ticket [79cad5e4b2e219dd197242e9e](https://sqlite.org/src/info/79cad5e4b2e219dd197242e9e).
11. Avoid using a prepared statement for ".stats on" command of the [CLI](../cli.md) after it has been closed by the ".eqp full" logicc. Fix for ticket [7be932dfa60a8a6b3b26bcf76](https://sqlite.org/src/info/7be932dfa60a8a6b3b26bcf76).
12. The LIKE optimization was generating incorrect byte-code and hence getting the wrong answer if the left-hand operand has numeric affinity and the right-hand-side pattern is '/%' or if the pattern begins with the ESCAPE character. Fix for ticket [c94369cae9b561b1f996d0054b](https://sqlite.org/src/info/c94369cae9b561b1f996d0054b)
**Hashes:**
13. SQLITE_SOURCE_ID: "2018-09-15 04:01:47 b63af6c3bd33152742648d5d2e8dc5d5fcbcdd27df409272b6aea00a6f761760"
14. SHA3-256 for sqlite3.c: 989e3ff37f2b5eea8e42205f808ccf0ba86c6ea6aa928ad2c011f33a108ac45d
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.25.1 On 2018-09-18
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_25_1.html*
## SQLite Release 3.25.1 On 2018-09-18
**Prior changes from version 3.25.0 (2018-09-15):**
1. Add support for [window functions](../windowfunctions.md)
2. Enhancements the [ALTER TABLE](../lang_altertable.md) command:
1. Add support for renaming columns within a table using ALTER TABLE *table* RENAME COLUMN *oldname* TO *newname*.
2. Fix table rename feature so that it also updates references to the renamed table in [triggers](../lang_createtrigger.md) and [views](../lang_createview.md).
3. Query optimizer improvements:
1. Avoid unnecessary loads of columns in an aggregate query that are not within an aggregate function and that are not part of the GROUP BY clause.
2. The IN-early-out optimization: When doing a look-up on a multi-column index and an IN operator is used on a column other than the left-most column, then if no rows match against the first IN value, check to make sure there exist rows that match the columns to the right before continuing with the next IN value.
3. Use the transitive property to try to propagate constant values within the WHERE clause. For example, convert "a=99 AND b=a" into "a=99 AND b=99".
4. Use a separate mutex on every inode in the unix [VFS](../vfs.md), rather than a single mutex shared among them all, for slightly better concurrency in multi-threaded environments.
5. Enhance the [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) command for improved detection of problems on the page freelist.
6. Output infinity as 1e999 in the ".dump" command of the [command-line shell](../cli.md).
7. Added the [SQLITE_FCNTL_DATA_VERSION](../c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntldataversion) file-control.
8. Added the [Geopoly module](../geopoly.md)
**Bug fixes:**
9. The ORDER BY LIMIT optimization might have caused an infinite loop in the byte code of the prepared statement under very obscure circumstances, due to a confluence of minor defects in the query optimizer. Fix for ticket [9936b2fa443fec03ff25](https://sqlite.org/src/info/9936b2fa443fec03ff25)
10. On an UPSERT when the order of constraint checks is rearranged, ensure that the affinity transformations on the inserted content occur before any of the constraint checks. Fix for ticket [79cad5e4b2e219dd197242e9e](https://sqlite.org/src/info/79cad5e4b2e219dd197242e9e).
11. Avoid using a prepared statement for ".stats on" command of the [CLI](../cli.md) after it has been closed by the ".eqp full" logicc. Fix for ticket [7be932dfa60a8a6b3b26bcf76](https://sqlite.org/src/info/7be932dfa60a8a6b3b26bcf76).
12. The LIKE optimization was generating incorrect byte-code and hence getting the wrong answer if the left-hand operand has numeric affinity and the right-hand-side pattern is '/%' or if the pattern begins with the ESCAPE character. Fix for ticket [c94369cae9b561b1f996d0054b](https://sqlite.org/src/info/c94369cae9b561b1f996d0054b)
**Changes in this specific patch release, version 3.25.1 (2018-09-18):**
1. Extra sanity checking added to ALTER TABLE in the 3.25.0 release sometimes raises a false-positive when the table being modified has a trigger that updates a virtual table. The false-positive caused the ALTER TABLE to rollback, thus leaving the schema unchanged. Ticket [b41031ea2b537237](https://sqlite.org/src/info/b41031ea2b537237).
2. The fix in the 3.25.0 release for the endless-loop in the byte-code associated with the ORDER BY LIMIT optimization did not work for some queries involving window functions. An additional correction is required. Ticket [510cde277783b5fb](https://sqlite.org/src/info/510cde277783b5fb)
**Hashes:**
3. SQLITE_SOURCE_ID: "2018-09-18 20:20:44 2ac9003de44da7dafa3fbb1915ac5725a9275c86bf2f3b7aa19321bf1460b386"
4. SHA3-256 for sqlite3.c: 1b2302e7a54cc99c84ff699a299f61f069a28e1ed090b89e4430ca80ae2aab06
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.25.2 On 2018-09-25
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_25_2.html*
## SQLite Release 3.25.2 On 2018-09-25
**Prior changes from version 3.25.0 (2018-09-15):**
1. Add support for [window functions](../windowfunctions.md)
2. Enhancements the [ALTER TABLE](../lang_altertable.md) command:
1. Add support for renaming columns within a table using ALTER TABLE *table* RENAME COLUMN *oldname* TO *newname*.
2. Fix table rename feature so that it also updates references to the renamed table in [triggers](../lang_createtrigger.md) and [views](../lang_createview.md).
3. Query optimizer improvements:
1. Avoid unnecessary loads of columns in an aggregate query that are not within an aggregate function and that are not part of the GROUP BY clause.
2. The IN-early-out optimization: When doing a look-up on a multi-column index and an IN operator is used on a column other than the left-most column, then if no rows match against the first IN value, check to make sure there exist rows that match the columns to the right before continuing with the next IN value.
3. Use the transitive property to try to propagate constant values within the WHERE clause. For example, convert "a=99 AND b=a" into "a=99 AND b=99".
4. Use a separate mutex on every inode in the unix [VFS](../vfs.md), rather than a single mutex shared among them all, for slightly better concurrency in multi-threaded environments.
5. Enhance the [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) command for improved detection of problems on the page freelist.
6. Output infinity as 1e999 in the ".dump" command of the [command-line shell](../cli.md).
7. Added the [SQLITE_FCNTL_DATA_VERSION](../c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntldataversion) file-control.
8. Added the [Geopoly module](../geopoly.md)
**Bug fixes:**
9. The ORDER BY LIMIT optimization might have caused an infinite loop in the byte code of the prepared statement under very obscure circumstances, due to a confluence of minor defects in the query optimizer. Fix for ticket [9936b2fa443fec03ff25](https://sqlite.org/src/info/9936b2fa443fec03ff25)
10. On an UPSERT when the order of constraint checks is rearranged, ensure that the affinity transformations on the inserted content occur before any of the constraint checks. Fix for ticket [79cad5e4b2e219dd197242e9e](https://sqlite.org/src/info/79cad5e4b2e219dd197242e9e).
11. Avoid using a prepared statement for ".stats on" command of the [CLI](../cli.md) after it has been closed by the ".eqp full" logicc. Fix for ticket [7be932dfa60a8a6b3b26bcf76](https://sqlite.org/src/info/7be932dfa60a8a6b3b26bcf76).
12. The LIKE optimization was generating incorrect byte-code and hence getting the wrong answer if the left-hand operand has numeric affinity and the right-hand-side pattern is '/%' or if the pattern begins with the ESCAPE character. Fix for ticket [c94369cae9b561b1f996d0054b](https://sqlite.org/src/info/c94369cae9b561b1f996d0054b)
**Prior changes from version 3.25.1 (2018-09-18):**
1. Extra sanity checking added to ALTER TABLE in the 3.25.0 release sometimes raises a false-positive when the table being modified has a trigger that updates a virtual table. The false-positive caused the ALTER TABLE to rollback, thus leaving the schema unchanged. Ticket [b41031ea2b537237](https://sqlite.org/src/info/b41031ea2b537237).
2. The fix in the 3.25.0 release for the endless-loop in the byte-code associated with the ORDER BY LIMIT optimization did not work for some queries involving window functions. An additional correction is required. Ticket [510cde277783b5fb](https://sqlite.org/src/info/510cde277783b5fb)
**Changes in this specific patch release, version 3.25.2 (2018-09-25):**
1. Add the [PRAGMA legacy_alter_table=ON](../pragma.md#pragma_legacy_alter_table) command that causes the "ALTER TABLE RENAME" command to behave as it did in SQLite versions 3.24.0 and earlier: references to the renamed table inside the bodies of triggers and views are not updated. This new pragma provides a compatibility work around for older programs that expected the older, wonky behavior of ALTER TABLE RENAME.
2. Fix a problem with the new [window functions](../windowfunctions.md) implementation that caused a malfunction when complicated expressions involving window functions were used inside of a view.
3. Fixes for various other compiler warnings and minor problems associated with obscure configurations.
**Hashes:**
4. SQLITE_SOURCE_ID: "2018-09-25 19:08:10 fb90e7189ae6d62e77ba3a308ca5d683f90bbe633cf681865365b8e92792d1c7"
5. SHA3-256 for sqlite3.c: 34c23ff91631ae10354f8c9d62fd7d65732b3d7f3acfd0bbae31ff4a62fe28af
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.25.3 On 2018-11-05
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_25_3.html*
## SQLite Release 3.25.3 On 2018-11-05
**Prior changes from version 3.25.0 (2018-09-15):**
1. Add support for [window functions](../windowfunctions.md)
2. Enhancements the [ALTER TABLE](../lang_altertable.md) command:
1. Add support for renaming columns within a table using ALTER TABLE *table* RENAME COLUMN *oldname* TO *newname*.
2. Fix table rename feature so that it also updates references to the renamed table in [triggers](../lang_createtrigger.md) and [views](../lang_createview.md).
3. Query optimizer improvements:
1. Avoid unnecessary loads of columns in an aggregate query that are not within an aggregate function and that are not part of the GROUP BY clause.
2. The IN-early-out optimization: When doing a look-up on a multi-column index and an IN operator is used on a column other than the left-most column, then if no rows match against the first IN value, check to make sure there exist rows that match the columns to the right before continuing with the next IN value.
3. Use the transitive property to try to propagate constant values within the WHERE clause. For example, convert "a=99 AND b=a" into "a=99 AND b=99".
4. Use a separate mutex on every inode in the unix [VFS](../vfs.md), rather than a single mutex shared among them all, for slightly better concurrency in multi-threaded environments.
5. Enhance the [PRAGMA integrity_check](../pragma.md#pragma_integrity_check) command for improved detection of problems on the page freelist.
6. Output infinity as 1e999 in the ".dump" command of the [command-line shell](../cli.md).
7. Added the [SQLITE_FCNTL_DATA_VERSION](../c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntldataversion) file-control.
8. Added the [Geopoly module](../geopoly.md)
**Bug fixes:**
9. The ORDER BY LIMIT optimization might have caused an infinite loop in the byte code of the prepared statement under very obscure circumstances, due to a confluence of minor defects in the query optimizer. Fix for ticket [9936b2fa443fec03ff25](https://sqlite.org/src/info/9936b2fa443fec03ff25)
10. On an UPSERT when the order of constraint checks is rearranged, ensure that the affinity transformations on the inserted content occur before any of the constraint checks. Fix for ticket [79cad5e4b2e219dd197242e9e](https://sqlite.org/src/info/79cad5e4b2e219dd197242e9e).
11. Avoid using a prepared statement for ".stats on" command of the [CLI](../cli.md) after it has been closed by the ".eqp full" logicc. Fix for ticket [7be932dfa60a8a6b3b26bcf76](https://sqlite.org/src/info/7be932dfa60a8a6b3b26bcf76).
12. The LIKE optimization was generating incorrect byte-code and hence getting the wrong answer if the left-hand operand has numeric affinity and the right-hand-side pattern is '/%' or if the pattern begins with the ESCAPE character. Fix for ticket [c94369cae9b561b1f996d0054b](https://sqlite.org/src/info/c94369cae9b561b1f996d0054b)
**Prior changes from version 3.25.1 (2018-09-18):**
1. Extra sanity checking added to ALTER TABLE in the 3.25.0 release sometimes raises a false-positive when the table being modified has a trigger that updates a virtual table. The false-positive caused the ALTER TABLE to rollback, thus leaving the schema unchanged. Ticket [b41031ea2b537237](https://sqlite.org/src/info/b41031ea2b537237).
2. The fix in the 3.25.0 release for the endless-loop in the byte-code associated with the ORDER BY LIMIT optimization did not work for some queries involving window functions. An additional correction is required. Ticket [510cde277783b5fb](https://sqlite.org/src/info/510cde277783b5fb)
**Prior changes from version 3.25.2 (2018-09-25):**
1. Add the [PRAGMA legacy_alter_table=ON](../pragma.md#pragma_legacy_alter_table) command that causes the "ALTER TABLE RENAME" command to behave as it did in SQLite versions 3.24.0 and earlier: references to the renamed table inside the bodies of triggers and views are not updated. This new pragma provides a compatibility work around for older programs that expected the older, wonky behavior of ALTER TABLE RENAME.
2. Fix a problem with the new [window functions](../windowfunctions.md) implementation that caused a malfunction when complicated expressions involving window functions were used inside of a view.
3. Fixes for various other compiler warnings and minor problems associated with obscure configurations.
**Changes in this specific patch release, version 3.25.3 (2018-11-05):**
1. Disallow the use of [window functions](../windowfunctions.md) in the recursive part of a CTE. Ticket [e8275b415a2f03bee](https://sqlite.org/src/info/e8275b415a2f03bee)
2. Fix the behavior of typeof() and length() on virtual tables. Ticket [69d642332d25aa3b7315a6d385](https://sqlite.org/src/info/69d642332d25aa3b7315a6d385)
3. Strengthen defenses against deliberately corrupted database files.
4. Fix a problem in the query planner that results when a row-value expression is used with a PRIMARY KEY with redundant columns. Ticket [1a84668dcfdebaf12415d](https://sqlite.org/src/info/1a84668dcfdebaf12415d)
5. Fix the query planner so that it works correctly for IS NOT NULL operators in the ON clause of a LEFT JOIN with the SQLITE_ENABLE_STAT4 compile-time option. [65eb38f6e46de8c75e188a17ec](https://sqlite.org/src/info/65eb38f6e46de8c75e188a17ec)
**Hashes:**
6. SQLITE_SOURCE_ID: "2018-11-05 20:37:38 89e099fbe5e13c33e683bef07361231ca525b88f7907be7092058007b75036f2"
7. SHA3-256 for sqlite3.c: 45586e4df74de3a43f3a1f8c7a78c3c3f02edce01af7d10cafe68bb94476a5c5
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.26.0 On 2018-12-01
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_26_0.html*
## SQLite Release 3.26.0 On 2018-12-01
1. Optimization: When doing an [UPDATE](../lang_update.md) on a table with [indexes on expressions](../expridx.md), do not update the expression indexes if they do not refer to any of the columns of the table being updated.
2. Allow the [xBestIndex()](../vtab.md#xbestindex) method of [virtual table](../vtab.md) implementations to return [SQLITE_CONSTRAINT](../rescode.md#constraint) to indicate that the proposed query plan is unusable and should not be given further consideration.
3. Added the [SQLITE_DBCONFIG_DEFENSIVE](../c3ref/c_dbconfig_defensive.md#sqlitedbconfigdefensive) option which disables the ability to create corrupt database files using ordinary SQL.
4. Added support for read-only [shadow tables](../vtab.md#xshadowname) when the [SQLITE_DBCONFIG_DEFENSIVE](../c3ref/c_dbconfig_defensive.md#sqlitedbconfigdefensive) option is enabled.
5. Added the [PRAGMA legacy_alter_table](../pragma.md#pragma_legacy_alter_table) command, which if enabled causes the [ALTER TABLE](../lang_altertable.md) command to behave like older version of SQLite (prior to version 3.25.0) for compatibility.
6. Added [PRAGMA table_xinfo](../pragma.md#pragma_table_xinfo) that works just like [PRAGMA table_info](../pragma.md#pragma_table_info) except that it also shows [hidden columns](../vtab.md#hiddencol) in virtual tables.
7. Added the [explain virtual table](https://sqlite.org/src/file/ext/misc/explain.c) as a run-time loadable extension.
8. Add a limit counter to the query planner to prevent excessive [sqlite3_prepare()](../c3ref/prepare.md) times for certain pathological SQL inputs.
9. Added support for the [sqlite3_normalized_sql()](../c3ref/expanded_sql.md) interface, when compiling with SQLITE_ENABLE_NORMALIZE.
10. Enhanced triggers so that they can use [table-valued functions](../vtab.md#tabfunc2) that exist in schemas other than the schema where the trigger is defined.
11. Enhancements to the [CLI](../cli.md):
1. Improvements to the ".help" command.
2. The SQLITE_HISTORY environment variable, if it exists, specifies the name of the command-line editing history file
3. The --deserialize option associated with opening a new database cause the database file to be read into memory and accessed using the [sqlite3_deserialize()](../c3ref/deserialize.md) API. This simplifies running tests on a database without modifying the file on disk.
12. Enhancements to the [geopoly](../geopoly.md) extension:
1. Always stores polygons using the binary format, which is faster and uses less space.
2. Added the [geopoly_regular()](../geopoly.md#regpoly) function.
3. Added the [geopoly_ccw()](../geopoly.md#ccw) function.
13. Enhancements to the [session](../sessionintro.md) extension:
1. Added the [SQLITE_CHANGESETAPPLY_INVERT](../session/c_changesetapply_fknoaction.md) flag
2. Added the [sqlite3changeset_start_v2()](../session/sqlite3changeset_start.md) interface and the [SQLITE_CHANGESETSTART_INVERT](../session/c_changesetstart_invert.md) flag.
3. Added the [changesetfuzz.c](https://sqlite.org/src/file/ext/session/changesetfuzz.c) test-case generator utility.
**Hashes:**
14. SQLITE_SOURCE_ID: "2018-12-01 12:34:55 bf8c1b2b7a5960c282e543b9c293686dccff272512d08865f4600fb58238b4f9"
15. SHA3-256 for sqlite3.c: 72c08830da9b5d1cb397c612c0e870d7f5eb41a323b41aa3d8aa5ae9ccedb2c4
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.27.0 On 2019-02-07
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_27_0.html*
## SQLite Release 3.27.0 On 2019-02-07
1. Added the [VACUUM INTO](../lang_vacuum.md#vacuuminto) command
2. Issue an SQLITE_WARNING message on the [error log](../errlog.md) if a [double-quoted string literal](../quirks.md#dblquote) is used.
3. The [sqlite3_normalized_sql()](../c3ref/expanded_sql.md) interface works on any prepared statement created using [sqlite3_prepare_v2()](../c3ref/prepare.md) or [sqlite3_prepare_v3()](../c3ref/prepare.md). It is no longer necessary to use [sqlite3_prepare_v3()](../c3ref/prepare.md) with [SQLITE_PREPARE_NORMALIZE](../c3ref/c_prepare_dont_log.md#sqlitepreparenormalize) in order to use [sqlite3_normalized_sql()](../c3ref/expanded_sql.md).
4. Added the remove_diacritics=2 option to [FTS3](../fts3.md) and [FTS5](../fts5.md).
5. Added the [SQLITE_PREPARE_NO_VTAB](../c3ref/c_prepare_dont_log.md#sqlitepreparenovtab) option to [sqlite3_prepare_v3()](../c3ref/prepare.md). Use that option to prevent circular references to [shadow tables](../vtab.md#xshadowname) from causing resource leaks.
6. Enhancements to the [sqlite3_deserialize()](../c3ref/deserialize.md) interface:
1. Add the [SQLITE_FCNTL_SIZE_LIMIT](../c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlsizelimit) [file-control](../c3ref/file_control.md) for setting an upper bound on the size of the in-memory database created by sqlite3_deserialize. The default upper bound is 1GiB, or whatever alternative value is specified by [sqlite3_config](../c3ref/config.md)([SQLITE_CONFIG_MEMDB_MAXSIZE](../c3ref/c_config_covering_index_scan.md#sqliteconfigmemdbmaxsize)) and/or [SQLITE_MEMDB_DEFAULT_MAXSIZE](../compile.md#memdb_default_maxsize).
2. Honor the [SQLITE_DESERIALIZE_READONLY](../c3ref/c_deserialize_freeonclose.md) flag, which was previously described in the documentation, but was previously a no-op.
3. Enhance the "deserialize" command of the [TCL Interface](../tclsqlite.md) to give it new "--maxsize N" and "--readonly BOOLEAN" options.
7. Enhancements to the [CLI](../cli.md), mostly to support testing and debugging of the SQLite library itself:
1. Add support for ".open --hexdb". The "[dbtotxt](https://sqlite.org/src/doc/trunk/tool/dbtotxt.md)" utility program used to generate the text for the "hexdb" is added to the source tree.
2. Add support for the "--maxsize N" option on ".open --deserialize".
3. Add the "--memtrace" command-line option, to show all memory allocations and deallocations.
4. Add the ".eqp trace" option on builds with SQLITE_DEBUG, to enable bytecode program listing with indentation and [PRAGMA vdbe_trace](../pragma.md#pragma_vdbe_trace) all in one step.
5. Add the ".progress" command for accessing the [sqlite3_progress_handler()](../c3ref/progress_handler.md) interface.
6. Add the "--async" option to the ".backup" command.
7. Add options "--expanded", "--normalized", "--plain", "--profile", "--row", "--stmt", and "--close" to the ".trace" command.
8. Increased robustness against malicious SQL that is run against a maliciously corrupted database.
**Bug fixes:**
9. Do not use a partial index to do a table scan on an IN operator. Ticket [1d958d90596593a774](https://sqlite.org/src/info/1d958d90596593a774).
10. Fix the [query flattener](../optoverview.md#flattening) so that it works on queries that contain subqueries that use [window functions](../windowfunctions.md). Ticket [709fcd17810f65f717](https://sqlite.org/src/info/f09fcd17810f65f717)
11. Ensure that ALTER TABLE modifies table and column names embedded in WITH clauses that are part of views and triggers.
12. Fix a parser bug that prevented the use of parentheses around table-valued functions.
13. Fix a problem with the [OR optimization](../optoverview.md#or_opt) on [indexes on expressions](../expridx.md). Ticket [d96eba87698a428c1d](https://sqlite.org/src/info/d96eba87698a428c1d).
14. Fix a problem with the [LEFT JOIN strength reduction optimization](../optoverview.md#leftjoinreduction) in which the optimization was being applied inappropriately due to an IS NOT NULL operator. Ticket [5948e09b8c415bc45d](https://sqlite.org/src/info/5948e09b8c415bc45d).
15. Fix the [REPLACE](../lang_replace.md) command so that it is no longer able to sneak a NULL value into a NOT NULL column even if the NOT NULL column has a default value of NULL. Ticket [e6f1f2e34dceeb1ed6](https://sqlite.org/src/info/e6f1f2e34dceeb1ed6)
16. Fix a problem with the use of [window functions](../windowfunctions.md) used within [correlated subqueries](../lang_expr.md#cosub). Ticket [d0866b26f83e9c55e3](https://sqlite.org/src/info/d0866b26f83e9c55e3)
17. Fix the [ALTER TABLE RENAME COLUMN](../lang_altertable.md#altertabmvcol) command so that it works for tables that have redundant UNIQUE constraints. Ticket [bc8d94f0fbd633fd9a](https://sqlite.org/src/info/bc8d94f0fbd633fd9a)
18. Fix a bug that caused [zeroblob](../lang_corefunc.md#zeroblob) values to be truncated when inserted into a table that uses an [expression index](../expridx.md). Ticket [bb4bdb9f7f654b0bb9](https://sqlite.org/src/info/bb4bdb9f7f654b0bb9)
**Hashes:**
19. SQLITE_SOURCE_ID: "2019-02-07 17:02:52 97744701c3bd414e6c9d7182639d8c2ce7cf124c4fce625071ae65658ac61713 "
20. SHA3-256 for sqlite3.c: ca011a10ee8515b33e5643444b98ee3d74dc45d3ac766c3700320def52bc6aba
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.27.1 On 2019-02-08
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_27_1.html*
## SQLite Release 3.27.1 On 2019-02-08
**Prior changes from version 3.27.0 (2019-02-07):**
1. Added the [VACUUM INTO](../lang_vacuum.md#vacuuminto) command
2. Issue an SQLITE_WARNING message on the [error log](../errlog.md) if a [double-quoted string literal](../quirks.md#dblquote) is used.
3. The [sqlite3_normalized_sql()](../c3ref/expanded_sql.md) interface works on any prepared statement created using [sqlite3_prepare_v2()](../c3ref/prepare.md) or [sqlite3_prepare_v3()](../c3ref/prepare.md). It is no longer necessary to use [sqlite3_prepare_v3()](../c3ref/prepare.md) with [SQLITE_PREPARE_NORMALIZE](../c3ref/c_prepare_dont_log.md#sqlitepreparenormalize) in order to use [sqlite3_normalized_sql()](../c3ref/expanded_sql.md).
4. Added the remove_diacritics=2 option to [FTS3](../fts3.md) and [FTS5](../fts5.md).
5. Added the [SQLITE_PREPARE_NO_VTAB](../c3ref/c_prepare_dont_log.md#sqlitepreparenovtab) option to [sqlite3_prepare_v3()](../c3ref/prepare.md). Use that option to prevent circular references to [shadow tables](../vtab.md#xshadowname) from causing resource leaks.
6. Enhancements to the [sqlite3_deserialize()](../c3ref/deserialize.md) interface:
1. Add the [SQLITE_FCNTL_SIZE_LIMIT](../c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlsizelimit) [file-control](../c3ref/file_control.md) for setting an upper bound on the size of the in-memory database created by sqlite3_deserialize. The default upper bound is 1GiB, or whatever alternative value is specified by [sqlite3_config](../c3ref/config.md)([SQLITE_CONFIG_MEMDB_MAXSIZE](../c3ref/c_config_covering_index_scan.md#sqliteconfigmemdbmaxsize)) and/or [SQLITE_MEMDB_DEFAULT_MAXSIZE](../compile.md#memdb_default_maxsize).
2. Honor the [SQLITE_DESERIALIZE_READONLY](../c3ref/c_deserialize_freeonclose.md) flag, which was previously described in the documentation, but was previously a no-op.
3. Enhance the "deserialize" command of the [TCL Interface](../tclsqlite.md) to give it new "--maxsize N" and "--readonly BOOLEAN" options.
7. Enhancements to the [CLI](../cli.md), mostly to support testing and debugging of the SQLite library itself:
1. Add support for ".open --hexdb". The "[dbtotxt](https://sqlite.org/src/doc/trunk/tool/dbtotxt.md)" utility program used to generate the text for the "hexdb" is added to the source tree.
2. Add support for the "--maxsize N" option on ".open --deserialize".
3. Add the "--memtrace" command-line option, to show all memory allocations and deallocations.
4. Add the ".eqp trace" option on builds with SQLITE_DEBUG, to enable bytecode program listing with indentation and [PRAGMA vdbe_trace](../pragma.md#pragma_vdbe_trace) all in one step.
5. Add the ".progress" command for accessing the [sqlite3_progress_handler()](../c3ref/progress_handler.md) interface.
6. Add the "--async" option to the ".backup" command.
7. Add options "--expanded", "--normalized", "--plain", "--profile", "--row", "--stmt", and "--close" to the ".trace" command.
8. Increased robustness against malicious SQL that is run against a maliciously corrupted database.
**Bug fixes:**
9. Do not use a partial index to do a table scan on an IN operator. Ticket [1d958d90596593a774](https://sqlite.org/src/info/1d958d90596593a774).
10. Fix the [query flattener](../optoverview.md#flattening) so that it works on queries that contain subqueries that use [window functions](../windowfunctions.md). Ticket [709fcd17810f65f717](https://sqlite.org/src/info/f09fcd17810f65f717)
11. Ensure that ALTER TABLE modifies table and column names embedded in WITH clauses that are part of views and triggers.
12. Fix a parser bug that prevented the use of parentheses around table-valued functions.
13. Fix a problem with the [OR optimization](../optoverview.md#or_opt) on [indexes on expressions](../expridx.md). Ticket [d96eba87698a428c1d](https://sqlite.org/src/info/d96eba87698a428c1d).
14. Fix a problem with the [LEFT JOIN strength reduction optimization](../optoverview.md#leftjoinreduction) in which the optimization was being applied inappropriately due to an IS NOT NULL operator. Ticket [5948e09b8c415bc45d](https://sqlite.org/src/info/5948e09b8c415bc45d).
15. Fix the [REPLACE](../lang_replace.md) command so that it is no longer able to sneak a NULL value into a NOT NULL column even if the NOT NULL column has a default value of NULL. Ticket [e6f1f2e34dceeb1ed6](https://sqlite.org/src/info/e6f1f2e34dceeb1ed6)
16. Fix a problem with the use of [window functions](../windowfunctions.md) used within [correlated subqueries](../lang_expr.md#cosub). Ticket [d0866b26f83e9c55e3](https://sqlite.org/src/info/d0866b26f83e9c55e3)
17. Fix the [ALTER TABLE RENAME COLUMN](../lang_altertable.md#altertabmvcol) command so that it works for tables that have redundant UNIQUE constraints. Ticket [bc8d94f0fbd633fd9a](https://sqlite.org/src/info/bc8d94f0fbd633fd9a)
18. Fix a bug that caused [zeroblob](../lang_corefunc.md#zeroblob) values to be truncated when inserted into a table that uses an [expression index](../expridx.md). Ticket [bb4bdb9f7f654b0bb9](https://sqlite.org/src/info/bb4bdb9f7f654b0bb9)
**Changes in this specific patch release, version 3.27.1 (2019-02-08):**
1. Fix a bug in the query optimizer: an adverse interaction between the [OR optimization](../optoverview.md#or_opt) and the optimization that tries to use values read directly from an [expression index](../expridx.md) instead of recomputing the expression. Ticket [4e8e4857d32d401f](https://sqlite.org/src/info/4e8e4857d32d401f)
**Hashes:**
2. SQLITE_SOURCE_ID: 2019-02-08 13:17:39 0eca3dd3d38b31c92b49ca2d311128b74584714d9e7de895b1a6286ef959a1dd
3. SHA3-256 for sqlite3.c: 11c14992660d5ac713ea8bea48dc5e6123f26bc8d3075fe5585d1a217d090233
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.27.2 On 2019-02-25
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_27_2.html*
## SQLite Release 3.27.2 On 2019-02-25
**Prior changes from version 3.27.0 (2019-02-07):**
1. Added the [VACUUM INTO](../lang_vacuum.md#vacuuminto) command
2. Issue an SQLITE_WARNING message on the [error log](../errlog.md) if a [double-quoted string literal](../quirks.md#dblquote) is used.
3. The [sqlite3_normalized_sql()](../c3ref/expanded_sql.md) interface works on any prepared statement created using [sqlite3_prepare_v2()](../c3ref/prepare.md) or [sqlite3_prepare_v3()](../c3ref/prepare.md). It is no longer necessary to use [sqlite3_prepare_v3()](../c3ref/prepare.md) with [SQLITE_PREPARE_NORMALIZE](../c3ref/c_prepare_dont_log.md#sqlitepreparenormalize) in order to use [sqlite3_normalized_sql()](../c3ref/expanded_sql.md).
4. Added the remove_diacritics=2 option to [FTS3](../fts3.md) and [FTS5](../fts5.md).
5. Added the [SQLITE_PREPARE_NO_VTAB](../c3ref/c_prepare_dont_log.md#sqlitepreparenovtab) option to [sqlite3_prepare_v3()](../c3ref/prepare.md). Use that option to prevent circular references to [shadow tables](../vtab.md#xshadowname) from causing resource leaks.
6. Enhancements to the [sqlite3_deserialize()](../c3ref/deserialize.md) interface:
1. Add the [SQLITE_FCNTL_SIZE_LIMIT](../c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlsizelimit) [file-control](../c3ref/file_control.md) for setting an upper bound on the size of the in-memory database created by sqlite3_deserialize. The default upper bound is 1GiB, or whatever alternative value is specified by [sqlite3_config](../c3ref/config.md)([SQLITE_CONFIG_MEMDB_MAXSIZE](../c3ref/c_config_covering_index_scan.md#sqliteconfigmemdbmaxsize)) and/or [SQLITE_MEMDB_DEFAULT_MAXSIZE](../compile.md#memdb_default_maxsize).
2. Honor the [SQLITE_DESERIALIZE_READONLY](../c3ref/c_deserialize_freeonclose.md) flag, which was previously described in the documentation, but was previously a no-op.
3. Enhance the "deserialize" command of the [TCL Interface](../tclsqlite.md) to give it new "--maxsize N" and "--readonly BOOLEAN" options.
7. Enhancements to the [CLI](../cli.md), mostly to support testing and debugging of the SQLite library itself:
1. Add support for ".open --hexdb". The "[dbtotxt](https://sqlite.org/src/doc/trunk/tool/dbtotxt.md)" utility program used to generate the text for the "hexdb" is added to the source tree.
2. Add support for the "--maxsize N" option on ".open --deserialize".
3. Add the "--memtrace" command-line option, to show all memory allocations and deallocations.
4. Add the ".eqp trace" option on builds with SQLITE_DEBUG, to enable bytecode program listing with indentation and [PRAGMA vdbe_trace](../pragma.md#pragma_vdbe_trace) all in one step.
5. Add the ".progress" command for accessing the [sqlite3_progress_handler()](../c3ref/progress_handler.md) interface.
6. Add the "--async" option to the ".backup" command.
7. Add options "--expanded", "--normalized", "--plain", "--profile", "--row", "--stmt", and "--close" to the ".trace" command.
8. Increased robustness against malicious SQL that is run against a maliciously corrupted database.
**Bug fixes:**
9. Do not use a partial index to do a table scan on an IN operator. Ticket [1d958d90596593a774](https://sqlite.org/src/info/1d958d90596593a774).
10. Fix the [query flattener](../optoverview.md#flattening) so that it works on queries that contain subqueries that use [window functions](../windowfunctions.md). Ticket [709fcd17810f65f717](https://sqlite.org/src/info/f09fcd17810f65f717)
11. Ensure that ALTER TABLE modifies table and column names embedded in WITH clauses that are part of views and triggers.
12. Fix a parser bug that prevented the use of parentheses around table-valued functions.
13. Fix a problem with the [OR optimization](../optoverview.md#or_opt) on [indexes on expressions](../expridx.md). Ticket [d96eba87698a428c1d](https://sqlite.org/src/info/d96eba87698a428c1d).
14. Fix a problem with the [LEFT JOIN strength reduction optimization](../optoverview.md#leftjoinreduction) in which the optimization was being applied inappropriately due to an IS NOT NULL operator. Ticket [5948e09b8c415bc45d](https://sqlite.org/src/info/5948e09b8c415bc45d).
15. Fix the [REPLACE](../lang_replace.md) command so that it is no longer able to sneak a NULL value into a NOT NULL column even if the NOT NULL column has a default value of NULL. Ticket [e6f1f2e34dceeb1ed6](https://sqlite.org/src/info/e6f1f2e34dceeb1ed6)
16. Fix a problem with the use of [window functions](../windowfunctions.md) used within [correlated subqueries](../lang_expr.md#cosub). Ticket [d0866b26f83e9c55e3](https://sqlite.org/src/info/d0866b26f83e9c55e3)
17. Fix the [ALTER TABLE RENAME COLUMN](../lang_altertable.md#altertabmvcol) command so that it works for tables that have redundant UNIQUE constraints. Ticket [bc8d94f0fbd633fd9a](https://sqlite.org/src/info/bc8d94f0fbd633fd9a)
18. Fix a bug that caused [zeroblob](../lang_corefunc.md#zeroblob) values to be truncated when inserted into a table that uses an [expression index](../expridx.md). Ticket [bb4bdb9f7f654b0bb9](https://sqlite.org/src/info/bb4bdb9f7f654b0bb9)
**Prior changes from version 3.27.1 (2019-02-08):**
1. Fix a bug in the query optimizer: an adverse interaction between the [OR optimization](../optoverview.md#or_opt) and the optimization that tries to use values read directly from an [expression index](../expridx.md) instead of recomputing the expression. Ticket [4e8e4857d32d401f](https://sqlite.org/src/info/4e8e4857d32d401f)
**Changes in this specific patch release, version 3.27.2 (2019-02-25):**
1. Fix a bug in the IN operator that was introduced by an attempted optimization in version 3.27.0. Ticket [df46dfb631f75694](https://sqlite.org/src/info/df46dfb631f75694)
2. Fix a bug causing a crash when a [window function](../windowfunctions.md) is misused. Ticket [4feb3159c6bc3f7e33959](https://sqlite.org/src/info/4feb3159c6bc3f7e33959).
3. Fix various documentation typos
**Hashes:**
4. SQLITE_SOURCE_ID: bd49a8271d650fa89e446b42e513b595a717b9212c91dd384aab871fc1d0f6d7
5. SHA3-256 for sqlite3.c: 1dbae33bff261f979d0042338f72c9e734b11a80720fb32498bae9150cc576e7
A [complete list of SQLite releases](../changes.md) in a single page and a [chronology](../chronology.md) are both also available. A detailed history of every check-in is available at [SQLite version control site](https://sqlite.org/src/timeline).
---
# SQLite Release 3.28.0 On 2019-04-16
*Sección: Guides | Origen: https://www.sqlite.org/releaselog/3_28_0.html*
## SQLite Release 3.28.0 On 2019-04-16
1. Enhanced [window functions](../windowfunctions.md):
1. Add support the [EXCLUDE clause](../windowfunctions.md#wexcls).
2. Add support for [window chaining](../windowfunctions.md#wchaining).
3. Add support for [GROUPS frames](../windowfunctions.md#grouptype).
4. Add support for "[\
\
\
References: [expr](./expr.md) [filter-clause](./filter-clause.md) [ordering-term](./ordering-term.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_expr.html](../lang_expr.md)
---
# SQLite Syntax: alter-table-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/alter-table-stmt.html*
# alter-table-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
References: [column-def](./column-def.md) [conflict-clause](./conflict-clause.md) [expr](./expr.md)\
See also: [lang_altertable.html](../lang_altertable.md)
---
# SQLite Syntax: analyze-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/analyze-stmt.html*
# analyze-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
See also: [lang_analyze.html](../lang_analyze.md)
---
# SQLite Syntax: attach-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/attach-stmt.html*
# attach-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
References: [expr](./expr.md)\
See also: [lang_attach.html](../lang_attach.md)
---
# SQLite Syntax: begin-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/begin-stmt.html*
# begin-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
See also: [lang_transaction.html](../lang_transaction.md)
---
# SQLite Syntax: column-constraint
*Sección: Guides | Origen: https://www.sqlite.org/syntax/column-constraint.html*
# column-constraint
\
Used by: [column-def](./column-def.md)\
References: [conflict-clause](./conflict-clause.md) [expr](./expr.md) [foreign-key-clause](./foreign-key-clause.md) [literal-value](./literal-value.md) [signed-number](./signed-number.md)\
See also: [gencol.html](../gencol.md) [lang_altertable.html](../lang_altertable.md) [lang_createtable.html](../lang_createtable.md)
---
# SQLite Syntax: column-def
*Sección: Guides | Origen: https://www.sqlite.org/syntax/column-def.html*
# column-def
\
Used by: [alter-table-stmt](./alter-table-stmt.md) [create-table-stmt](./create-table-stmt.md)\
References: [column-constraint](./column-constraint.md) [type-name](./type-name.md)\
See also: [lang_altertable.html](../lang_altertable.md) [lang_createtable.html](../lang_createtable.md)
---
# SQLite Syntax: column-name-list
*Sección: Guides | Origen: https://www.sqlite.org/syntax/column-name-list.html*
# column-name-list
\
Used by: [update-stmt](./update-stmt.md) [update-stmt-limited](./update-stmt-limited.md) [upsert-clause](./upsert-clause.md)\
See also: [lang_createtrigger.html](../lang_createtrigger.md) [lang_insert.html](../lang_insert.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md)
---
# SQLite Syntax: comment-syntax
*Sección: Guides | Origen: https://www.sqlite.org/syntax/comment-syntax.html*
# comment-syntax
\
\
See also: [lang_comment.html](../lang_comment.md)
---
# SQLite Syntax: commit-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/commit-stmt.html*
# commit-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
See also: [lang_transaction.html](../lang_transaction.md)
---
# SQLite Syntax: common-table-expression
*Sección: Guides | Origen: https://www.sqlite.org/syntax/common-table-expression.html*
# common-table-expression
\
Used by: [compound-select-stmt](./compound-select-stmt.md) [delete-stmt](./delete-stmt.md) [delete-stmt-limited](./delete-stmt-limited.md) [factored-select-stmt](./factored-select-stmt.md) [insert-stmt](./insert-stmt.md) [select-stmt](./select-stmt.md) [simple-select-stmt](./simple-select-stmt.md) [update-stmt](./update-stmt.md) [update-stmt-limited](./update-stmt-limited.md)\
References: [select-stmt](./select-stmt.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: compound-operator
*Sección: Guides | Origen: https://www.sqlite.org/syntax/compound-operator.html*
# compound-operator
\
Used by: [factored-select-stmt](./factored-select-stmt.md) [select-stmt](./select-stmt.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: compound-select-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/compound-select-stmt.html*
# compound-select-stmt
\
\
References: [common-table-expression](./common-table-expression.md) [expr](./expr.md) [ordering-term](./ordering-term.md) [select-core](./select-core.md)\
See also: [lang_select.html](../lang_select.md)
---
# SQLite Syntax: conflict-clause
*Sección: Guides | Origen: https://www.sqlite.org/syntax/conflict-clause.html*
# conflict-clause
\
Used by: [alter-table-stmt](./alter-table-stmt.md) [column-constraint](./column-constraint.md) [table-constraint](./table-constraint.md)\
See also: [lang_altertable.html](../lang_altertable.md) [lang_conflict.html](../lang_conflict.md) [lang_createtable.html](../lang_createtable.md)
---
# SQLite Syntax: create-index-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/create-index-stmt.html*
# create-index-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
References: [expr](./expr.md) [indexed-column](./indexed-column.md)\
See also: [lang_createindex.html](../lang_createindex.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: create-table-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/create-table-stmt.html*
# create-table-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
References: [column-def](./column-def.md) [select-stmt](./select-stmt.md) [table-constraint](./table-constraint.md) [table-options](./table-options.md)\
See also: [lang_createtable.html](../lang_createtable.md)
---
# SQLite Syntax: create-trigger-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/create-trigger-stmt.html*
# create-trigger-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
References: [delete-stmt](./delete-stmt.md) [expr](./expr.md) [insert-stmt](./insert-stmt.md) [select-stmt](./select-stmt.md) [update-stmt](./update-stmt.md)\
See also: [lang_createtrigger.html](../lang_createtrigger.md)
---
# SQLite Syntax: create-view-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/create-view-stmt.html*
# create-view-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
References: [select-stmt](./select-stmt.md)\
See also: [lang_createview.html](../lang_createview.md)
---
# SQLite Syntax: create-virtual-table-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/create-virtual-table-stmt.html*
# create-virtual-table-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
See also: [lang_createvtab.html](../lang_createvtab.md)
---
# SQLite Syntax: cte-table-name
*Sección: Guides | Origen: https://www.sqlite.org/syntax/cte-table-name.html*
# cte-table-name
\
Used by: [recursive-cte](./recursive-cte.md) [with-clause](./with-clause.md)\
See also: [lang_with.html](../lang_with.md)
---
# SQLite Syntax: delete-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/delete-stmt.html*
# delete-stmt
\
Used by: [create-trigger-stmt](./create-trigger-stmt.md) [sql-stmt](./sql-stmt.md)\
References: [common-table-expression](./common-table-expression.md) [expr](./expr.md) [qualified-table-name](./qualified-table-name.md) [returning-clause](./returning-clause.md)\
See also: [lang_createtrigger.html](../lang_createtrigger.md) [lang_delete.html](../lang_delete.md)
---
# SQLite Syntax: delete-stmt-limited
*Sección: Guides | Origen: https://www.sqlite.org/syntax/delete-stmt-limited.html*
# delete-stmt-limited
\
Used by: [sql-stmt](./sql-stmt.md)\
References: [common-table-expression](./common-table-expression.md) [expr](./expr.md) [ordering-term](./ordering-term.md) [qualified-table-name](./qualified-table-name.md) [returning-clause](./returning-clause.md)\
See also: [lang_delete.html](../lang_delete.md)
---
# SQLite Syntax: detach-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/detach-stmt.html*
# detach-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
See also: [lang_detach.html](../lang_detach.md)
---
# SQLite Syntax: drop-index-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/drop-index-stmt.html*
# drop-index-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
See also: [lang_dropindex.html](../lang_dropindex.md)
---
# SQLite Syntax: drop-table-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/drop-table-stmt.html*
# drop-table-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
See also: [lang_droptable.html](../lang_droptable.md)
---
# SQLite Syntax: drop-trigger-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/drop-trigger-stmt.html*
# drop-trigger-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
See also: [lang_droptrigger.html](../lang_droptrigger.md)
---
# SQLite Syntax: drop-view-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/drop-view-stmt.html*
# drop-view-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
See also: [lang_dropview.html](../lang_dropview.md)
---
# SQLite Syntax: expr
*Sección: Guides | Origen: https://www.sqlite.org/syntax/expr.html*
# expr
\
Used by: [aggregate-function-invocation](./aggregate-function-invocation.md) [alter-table-stmt](./alter-table-stmt.md) [attach-stmt](./attach-stmt.md) [column-constraint](./column-constraint.md) [compound-select-stmt](./compound-select-stmt.md) [create-index-stmt](./create-index-stmt.md) [create-trigger-stmt](./create-trigger-stmt.md) [delete-stmt](./delete-stmt.md) [delete-stmt-limited](./delete-stmt-limited.md) [factored-select-stmt](./factored-select-stmt.md) [filter-clause](./filter-clause.md) [frame-spec](./frame-spec.md) [function-arguments](./function-arguments.md) [indexed-column](./indexed-column.md) [insert-stmt](./insert-stmt.md) [join-constraint](./join-constraint.md) [ordering-term](./ordering-term.md) [over-clause](./over-clause.md) [raise-function](./raise-function.md) [result-column](./result-column.md) [returning-clause](./returning-clause.md) [select-core](./select-core.md) [select-stmt](./select-stmt.md) [simple-function-invocation](./simple-function-invocation.md) [simple-select-stmt](./simple-select-stmt.md) [table-constraint](./table-constraint.md) [table-or-subquery](./table-or-subquery.md) [update-stmt](./update-stmt.md) [update-stmt-limited](./update-stmt-limited.md) [upsert-clause](./upsert-clause.md) [window-defn](./window-defn.md) [window-function-invocation](./window-function-invocation.md)\
References: [filter-clause](./filter-clause.md) [function-arguments](./function-arguments.md) [literal-value](./literal-value.md) [over-clause](./over-clause.md) [raise-function](./raise-function.md) [select-stmt](./select-stmt.md) [type-name](./type-name.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: factored-select-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/factored-select-stmt.html*
# factored-select-stmt
\
\
References: [common-table-expression](./common-table-expression.md) [compound-operator](./compound-operator.md) [expr](./expr.md) [ordering-term](./ordering-term.md) [select-core](./select-core.md)\
See also: [lang_select.html](../lang_select.md)
---
# SQLite Syntax: filter-clause
*Sección: Guides | Origen: https://www.sqlite.org/syntax/filter-clause.html*
# filter-clause
\
Used by: [aggregate-function-invocation](./aggregate-function-invocation.md) [expr](./expr.md) [window-function-invocation](./window-function-invocation.md)\
References: [expr](./expr.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: foreign-key-clause
*Sección: Guides | Origen: https://www.sqlite.org/syntax/foreign-key-clause.html*
# foreign-key-clause
\
Used by: [column-constraint](./column-constraint.md) [table-constraint](./table-constraint.md)\
See also: [lang_altertable.html](../lang_altertable.md) [lang_createtable.html](../lang_createtable.md)
---
# SQLite Syntax: frame-spec
*Sección: Guides | Origen: https://www.sqlite.org/syntax/frame-spec.html*
# frame-spec
\
Used by: [over-clause](./over-clause.md) [window-defn](./window-defn.md)\
References: [expr](./expr.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: function-arguments
*Sección: Guides | Origen: https://www.sqlite.org/syntax/function-arguments.html*
# function-arguments
\
Used by: [expr](./expr.md)\
References: [expr](./expr.md) [ordering-term](./ordering-term.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: indexed-column
*Sección: Guides | Origen: https://www.sqlite.org/syntax/indexed-column.html*
# indexed-column
\
Used by: [create-index-stmt](./create-index-stmt.md) [table-constraint](./table-constraint.md) [upsert-clause](./upsert-clause.md)\
References: [expr](./expr.md)\
See also: [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_insert.html](../lang_insert.md) [lang_upsert.html](../lang_upsert.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: insert-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/insert-stmt.html*
# insert-stmt
\
Used by: [create-trigger-stmt](./create-trigger-stmt.md) [sql-stmt](./sql-stmt.md)\
References: [common-table-expression](./common-table-expression.md) [expr](./expr.md) [returning-clause](./returning-clause.md) [select-stmt](./select-stmt.md) [upsert-clause](./upsert-clause.md)\
See also: [lang_createtrigger.html](../lang_createtrigger.md) [lang_insert.html](../lang_insert.md)
---
# SQLite Syntax: join-clause
*Sección: Guides | Origen: https://www.sqlite.org/syntax/join-clause.html*
# join-clause
\
Used by: [select-core](./select-core.md) [select-stmt](./select-stmt.md) [table-or-subquery](./table-or-subquery.md) [update-stmt](./update-stmt.md) [update-stmt-limited](./update-stmt-limited.md)\
References: [join-constraint](./join-constraint.md) [join-operator](./join-operator.md) [table-or-subquery](./table-or-subquery.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: join-constraint
*Sección: Guides | Origen: https://www.sqlite.org/syntax/join-constraint.html*
# join-constraint
\
Used by: [join-clause](./join-clause.md)\
References: [expr](./expr.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: join-operator
*Sección: Guides | Origen: https://www.sqlite.org/syntax/join-operator.html*
# join-operator
\
Used by: [join-clause](./join-clause.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: literal-value
*Sección: Guides | Origen: https://www.sqlite.org/syntax/literal-value.html*
# literal-value
\
Used by: [column-constraint](./column-constraint.md) [expr](./expr.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: numeric-literal
*Sección: Guides | Origen: https://www.sqlite.org/syntax/numeric-literal.html*
# numeric-literal
\
\
See also: [lang_expr.html](../lang_expr.md)
---
# SQLite Syntax: ordering-term
*Sección: Guides | Origen: https://www.sqlite.org/syntax/ordering-term.html*
# ordering-term
\
Used by: [aggregate-function-invocation](./aggregate-function-invocation.md) [compound-select-stmt](./compound-select-stmt.md) [delete-stmt-limited](./delete-stmt-limited.md) [factored-select-stmt](./factored-select-stmt.md) [function-arguments](./function-arguments.md) [over-clause](./over-clause.md) [select-stmt](./select-stmt.md) [simple-select-stmt](./simple-select-stmt.md) [update-stmt-limited](./update-stmt-limited.md) [window-defn](./window-defn.md)\
References: [expr](./expr.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: over-clause
*Sección: Guides | Origen: https://www.sqlite.org/syntax/over-clause.html*
# over-clause
\
Used by: [expr](./expr.md)\
References: [expr](./expr.md) [frame-spec](./frame-spec.md) [ordering-term](./ordering-term.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: pragma-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/pragma-stmt.html*
# pragma-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
References: [pragma-value](./pragma-value.md)\
See also: [pragma.html](../pragma.md)
---
# SQLite Syntax: pragma-value
*Sección: Guides | Origen: https://www.sqlite.org/syntax/pragma-value.html*
# pragma-value
\
Used by: [pragma-stmt](./pragma-stmt.md)\
References: [signed-number](./signed-number.md)\
See also: [pragma.html](../pragma.md)
---
# SQLite Syntax: qualified-table-name
*Sección: Guides | Origen: https://www.sqlite.org/syntax/qualified-table-name.html*
# qualified-table-name
\
Used by: [delete-stmt](./delete-stmt.md) [delete-stmt-limited](./delete-stmt-limited.md) [update-stmt](./update-stmt.md) [update-stmt-limited](./update-stmt-limited.md)\
See also: [lang_createtrigger.html](../lang_createtrigger.md) [lang_delete.html](../lang_delete.md) [lang_indexedby.html](../lang_indexedby.md) [lang_update.html](../lang_update.md)
---
# SQLite Syntax: raise-function
*Sección: Guides | Origen: https://www.sqlite.org/syntax/raise-function.html*
# raise-function
\
Used by: [expr](./expr.md)\
References: [expr](./expr.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: recursive-cte
*Sección: Guides | Origen: https://www.sqlite.org/syntax/recursive-cte.html*
# recursive-cte
\
\
References: [cte-table-name](./cte-table-name.md)\
See also: [lang_with.html](../lang_with.md)
---
# SQLite Syntax: reindex-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/reindex-stmt.html*
# reindex-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
See also: [lang_reindex.html](../lang_reindex.md)
---
# SQLite Syntax: release-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/release-stmt.html*
# release-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
See also: [lang_savepoint.html](../lang_savepoint.md)
---
# SQLite Syntax: result-column
*Sección: Guides | Origen: https://www.sqlite.org/syntax/result-column.html*
# result-column
\
Used by: [select-core](./select-core.md) [select-stmt](./select-stmt.md)\
References: [expr](./expr.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: returning-clause
*Sección: Guides | Origen: https://www.sqlite.org/syntax/returning-clause.html*
# returning-clause
\
Used by: [delete-stmt](./delete-stmt.md) [delete-stmt-limited](./delete-stmt-limited.md) [insert-stmt](./insert-stmt.md) [update-stmt](./update-stmt.md) [update-stmt-limited](./update-stmt-limited.md)\
References: [expr](./expr.md)\
See also: [lang_createtrigger.html](../lang_createtrigger.md) [lang_delete.html](../lang_delete.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_update.html](../lang_update.md)
---
# SQLite Syntax: rollback-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/rollback-stmt.html*
# rollback-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
See also: [lang_savepoint.html](../lang_savepoint.md) [lang_transaction.html](../lang_transaction.md)
---
# SQLite Syntax: savepoint-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/savepoint-stmt.html*
# savepoint-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
See also: [lang_savepoint.html](../lang_savepoint.md)
---
# SQLite Syntax: select-core
*Sección: Guides | Origen: https://www.sqlite.org/syntax/select-core.html*
# select-core
\
Used by: [compound-select-stmt](./compound-select-stmt.md) [factored-select-stmt](./factored-select-stmt.md) [simple-select-stmt](./simple-select-stmt.md)\
References: [expr](./expr.md) [join-clause](./join-clause.md) [result-column](./result-column.md) [table-or-subquery](./table-or-subquery.md) [window-defn](./window-defn.md)\
See also: [lang_select.html](../lang_select.md)
---
# SQLite Syntax: select-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/select-stmt.html*
# select-stmt
\
Used by: [common-table-expression](./common-table-expression.md) [create-table-stmt](./create-table-stmt.md) [create-trigger-stmt](./create-trigger-stmt.md) [create-view-stmt](./create-view-stmt.md) [expr](./expr.md) [insert-stmt](./insert-stmt.md) [sql-stmt](./sql-stmt.md) [table-or-subquery](./table-or-subquery.md) [with-clause](./with-clause.md)\
References: [common-table-expression](./common-table-expression.md) [compound-operator](./compound-operator.md) [expr](./expr.md) [join-clause](./join-clause.md) [ordering-term](./ordering-term.md) [result-column](./result-column.md) [table-or-subquery](./table-or-subquery.md) [window-defn](./window-defn.md)\
See also: [changes.html](../changes.md) [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md) [releaselog/3_35_3.html](../releaselog/3_35_3.md) [releaselog/3_35_4.html](../releaselog/3_35_4.md) [releaselog/3_35_5.html](../releaselog/3_35_5.md)
---
# SQLite Syntax: signed-number
*Sección: Guides | Origen: https://www.sqlite.org/syntax/signed-number.html*
# signed-number
\
Used by: [column-constraint](./column-constraint.md) [pragma-value](./pragma-value.md) [type-name](./type-name.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md) [pragma.html](../pragma.md)
---
# SQLite Syntax: simple-function-invocation
*Sección: Guides | Origen: https://www.sqlite.org/syntax/simple-function-invocation.html*
# simple-function-invocation
\
\
References: [expr](./expr.md)\
See also: [lang_corefunc.html](../lang_corefunc.md) [lang_expr.html](../lang_expr.md)
---
# SQLite Syntax: simple-select-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/simple-select-stmt.html*
# simple-select-stmt
\
\
References: [common-table-expression](./common-table-expression.md) [expr](./expr.md) [ordering-term](./ordering-term.md) [select-core](./select-core.md)\
See also: [lang_select.html](../lang_select.md)
---
# SQLite Syntax: sql-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/sql-stmt.html*
# sql-stmt
\
Used by: [sql-stmt-list](./sql-stmt-list.md)\
References: [alter-table-stmt](./alter-table-stmt.md) [analyze-stmt](./analyze-stmt.md) [attach-stmt](./attach-stmt.md) [begin-stmt](./begin-stmt.md) [commit-stmt](./commit-stmt.md) [create-index-stmt](./create-index-stmt.md) [create-table-stmt](./create-table-stmt.md) [create-trigger-stmt](./create-trigger-stmt.md) [create-view-stmt](./create-view-stmt.md) [create-virtual-table-stmt](./create-virtual-table-stmt.md) [delete-stmt](./delete-stmt.md) [delete-stmt-limited](./delete-stmt-limited.md) [detach-stmt](./detach-stmt.md) [drop-index-stmt](./drop-index-stmt.md) [drop-table-stmt](./drop-table-stmt.md) [drop-trigger-stmt](./drop-trigger-stmt.md) [drop-view-stmt](./drop-view-stmt.md) [insert-stmt](./insert-stmt.md) [pragma-stmt](./pragma-stmt.md) [reindex-stmt](./reindex-stmt.md) [release-stmt](./release-stmt.md) [rollback-stmt](./rollback-stmt.md) [savepoint-stmt](./savepoint-stmt.md) [select-stmt](./select-stmt.md) [update-stmt](./update-stmt.md) [update-stmt-limited](./update-stmt-limited.md) [vacuum-stmt](./vacuum-stmt.md)\
See also: [lang.html](../lang.md) [lang_explain.html](../lang_explain.md)
---
# SQLite Syntax: sql-stmt-list
*Sección: Guides | Origen: https://www.sqlite.org/syntax/sql-stmt-list.html*
# sql-stmt-list
\
\
References: [sql-stmt](./sql-stmt.md)\
See also: [lang.html](../lang.md)
---
# SQLite Syntax: table-constraint
*Sección: Guides | Origen: https://www.sqlite.org/syntax/table-constraint.html*
# table-constraint
\
Used by: [create-table-stmt](./create-table-stmt.md)\
References: [conflict-clause](./conflict-clause.md) [expr](./expr.md) [foreign-key-clause](./foreign-key-clause.md) [indexed-column](./indexed-column.md)\
See also: [lang_createtable.html](../lang_createtable.md)
---
# SQLite Syntax: table-options
*Sección: Guides | Origen: https://www.sqlite.org/syntax/table-options.html*
# table-options
\
Used by: [create-table-stmt](./create-table-stmt.md)\
See also: [lang_createtable.html](../lang_createtable.md)
---
# SQLite Syntax: table-or-subquery
*Sección: Guides | Origen: https://www.sqlite.org/syntax/table-or-subquery.html*
# table-or-subquery
\
Used by: [join-clause](./join-clause.md) [select-core](./select-core.md) [select-stmt](./select-stmt.md) [update-stmt](./update-stmt.md) [update-stmt-limited](./update-stmt-limited.md)\
References: [expr](./expr.md) [join-clause](./join-clause.md) [select-stmt](./select-stmt.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: type-name
*Sección: Guides | Origen: https://www.sqlite.org/syntax/type-name.html*
# type-name
\
Used by: [column-def](./column-def.md) [expr](./expr.md)\
References: [signed-number](./signed-number.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: update-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/update-stmt.html*
# update-stmt
\
Used by: [create-trigger-stmt](./create-trigger-stmt.md) [sql-stmt](./sql-stmt.md)\
References: [column-name-list](./column-name-list.md) [common-table-expression](./common-table-expression.md) [expr](./expr.md) [join-clause](./join-clause.md) [qualified-table-name](./qualified-table-name.md) [returning-clause](./returning-clause.md) [table-or-subquery](./table-or-subquery.md)\
See also: [lang_createtrigger.html](../lang_createtrigger.md) [lang_update.html](../lang_update.md)
---
# SQLite Syntax: update-stmt-limited
*Sección: Guides | Origen: https://www.sqlite.org/syntax/update-stmt-limited.html*
# update-stmt-limited
\
Used by: [sql-stmt](./sql-stmt.md)\
References: [column-name-list](./column-name-list.md) [common-table-expression](./common-table-expression.md) [expr](./expr.md) [join-clause](./join-clause.md) [ordering-term](./ordering-term.md) [qualified-table-name](./qualified-table-name.md) [returning-clause](./returning-clause.md) [table-or-subquery](./table-or-subquery.md)\
See also: [lang_update.html](../lang_update.md)
---
# SQLite Syntax: upsert-clause
*Sección: Guides | Origen: https://www.sqlite.org/syntax/upsert-clause.html*
# upsert-clause
\
Used by: [insert-stmt](./insert-stmt.md)\
References: [column-name-list](./column-name-list.md) [expr](./expr.md) [indexed-column](./indexed-column.md)\
See also: [lang_createtrigger.html](../lang_createtrigger.md) [lang_insert.html](../lang_insert.md) [lang_upsert.html](../lang_upsert.md)
---
# SQLite Syntax: vacuum-stmt
*Sección: Guides | Origen: https://www.sqlite.org/syntax/vacuum-stmt.html*
# vacuum-stmt
\
Used by: [sql-stmt](./sql-stmt.md)\
See also: [lang_vacuum.html](../lang_vacuum.md)
---
# SQLite Syntax: window-defn
*Sección: Guides | Origen: https://www.sqlite.org/syntax/window-defn.html*
# window-defn
\
Used by: [select-core](./select-core.md) [select-stmt](./select-stmt.md) [window-function-invocation](./window-function-invocation.md)\
References: [expr](./expr.md) [frame-spec](./frame-spec.md) [ordering-term](./ordering-term.md)\
See also: [lang_aggfunc.html](../lang_aggfunc.md) [lang_altertable.html](../lang_altertable.md) [lang_attach.html](../lang_attach.md) [lang_createindex.html](../lang_createindex.md) [lang_createtable.html](../lang_createtable.md) [lang_createtrigger.html](../lang_createtrigger.md) [lang_createview.html](../lang_createview.md) [lang_delete.html](../lang_delete.md) [lang_expr.html](../lang_expr.md) [lang_insert.html](../lang_insert.md) [lang_returning.html](../lang_returning.md) [lang_select.html](../lang_select.md) [lang_update.html](../lang_update.md) [lang_upsert.html](../lang_upsert.md) [lang_with.html](../lang_with.md) [partialindex.html](../partialindex.md)
---
# SQLite Syntax: window-function-invocation
*Sección: Guides | Origen: https://www.sqlite.org/syntax/window-function-invocation.html*
# window-function-invocation
\
\
References: [expr](./expr.md) [filter-clause](./filter-clause.md) [window-defn](./window-defn.md)\
See also: [lang_expr.html](../lang_expr.md)
---
# SQLite Syntax: with-clause
*Sección: Guides | Origen: https://www.sqlite.org/syntax/with-clause.html*
# with-clause
\
\
References: [cte-table-name](./cte-table-name.md) [select-stmt](./select-stmt.md)\
See also: [lang_with.html](../lang_with.md)
---
# SQLite Unlock-Notify API
*Sección: Guides | Origen: https://www.sqlite.org/unlock_notify.html*
# Using the sqlite3_unlock_notify() API
\
/\* This example uses the pthreads API \*/\
\#include \| Substitution Type | Meaning |
|---|---|
| % | Two "%" characters in a row are translated into a single "%" in the output, without substituting any values. |
| d, i | The argument is a signed integer which is displayed in decimal. |
| u | The argument is an unsigned integer which is displayed in decimal. |
| f | The argument is a double which is displayed in decimal. |
| e, E | The argument is a double which is displayed in exponential notation. The exponent character is 'e' or 'E' depending on the type. |
| g, G | The argument is a double which is displayed in either normal decimal notation or if the exponent is not close to zero, in exponential notation. |
| x, X | The argument is an integer which is displayed in hexadecimal. Lower-case hexadecimal is used for %x and upper-case is used for %X |
| o | The argument is an integer which is displayed in octal. |
| s, z | The argument is either a zero-terminated string that is displayed, or a null pointer which is treated as an empty string. For the %z type in C-language interfaces, sqlite3_free() is invoked on the string after it has been copied into the output. The %s and %z substitutions are identical for the SQL printf() function, with a NULL argument treated as an empty string. The %s substitution is universal among printf functions, but the %z substitution and safe treatment of null pointers are SQLite enhancements, not found in other printf() implementations. Caution: Recent versions of GNU printf use %z to render size_t integer values. This is incompatible with SQLite's use of %z. |
| c | For the C-language interfaces, the argument is an integer which is interpreted as a character. For the format() SQL function the argument is a string from which the first character is extracted and displayed. |
| p | The argument is a pointer which is displayed as a hexadecimal address. Since the SQL language has no concept of a pointer, the %p substitution for the format() SQL function works like %x. |
| n | The argument is a pointer to an integer. Nothing is displayed for this substitution type. Instead, the integer to which the argument points is overwritten with the number of characters in the generated string that result from all format symbols to the left of the %n. |
| q, Q | The argument is a zero-terminated string. The string is printed with all single quote (') characters doubled so that the string can safely appear inside an SQL string literal. The %Q substitution type also puts single-quotes on both ends of the substituted string. If the argument to %Q is a null pointer then the output is an unquoted "NULL". In other words, a null pointer generates an SQL NULL, and a non-null pointer generates a valid SQL string literal. If the argument to %q is a null pointer then no output is generated. Thus a null-pointer to %q is the same as an empty string. If the alternate-form-1 flag ("#") is added to %Q (ex: "%#Q") then control codes in the range of U+0001 through U+001f are escaped using JSON-style backslash escapes and the entire output is enclosed in " unistr('...')". The resulting output is thus safe for display on devices that interpret ANSI escape sequences. The "%#q" conversion escapes control characters likewise but does not add the unistr() function wrapper.For these substitutions, the precision is the number of bytes or characters taken from the argument, not the number of bytes or characters that are written into the output. The %q and %Q substitutions are SQLite enhancements, not found in most other printf() implementations. |
| w | This substitution works like %q except that it doubles all double-quote characters (") instead of single-quotes, making the result suitable for using with a double-quoted identifier name in an SQL statement. The %w substitution is an SQLite enhancements, not found in most other printf() implementations. |
| STRICT | ordinary non-strict |
|---|---|
| CREATE TABLE t1(a ANY) STRICT; INSERT INTO t1 VALUES('000123'); SELECT typeof(a), quote(a) FROM t1; -- result: text '000123' |
CREATE TABLE t1(a ANY); INSERT INTO t1 VALUES('000123'); SELECT typeof(a), quote(a) FROM t1; -- result: integer 123 |
The complete build process starts with the canonical source code files on the left side of the diagram. There are between 100 and 200 separate canonical source files (depending on the SQLite version). Some of those canonical source files get transformed by preprocessor programs to generate "intermediate source files". One example of a preprocessor is the [Lemon](lemon.md) parser generator program. One of the canonical source code files is [parse.y](https://sqlite.org/src/file/src/parse.y) which is an LALR(1) grammar for the SQL dialect understood by SQLite. Lemon converts that grammar into C-code that implements a [pushdown automaton](https://en.wikipedia.org/wiki/Pushdown_automaton) that will parse SQL text into an [abstract syntax tree](https://en.wikipedia.org/wiki/Abstract_syntax_tree). There are many other examples of programs and scripts in SQLite that transform the code that the SQLite developers edit into code that can be understood by C compilers. Not all canonical source code files are preprocessed, but a fair number of them are.
After preprocessing, there are some scripts that gather together the many intermediate source files and the remaining canonical source files and concatenates them together to generate the "[amalgamation](amalgamation.md)". Often when we say "the amalgamation" we mean just the file "sqlite3.c" which contains the bulk of the SQLite source code. But the corresponding header file "sqlite3.h" is also constructed from other files. And the source code to the SQLite [command-line shell](cli.md) is an amalgamation contained in "shell.c".
The amalgamation files can then be processed by any ordinary C compiler to render the final build products, shown on the right side of the diagram. (The diagram shows build product filenames as they might appear on Windows. Substitute whatever alternative names are appropriate for your system.)
# 3. How To Compile From Canonical Sources
To compile SQLite from canonical sources, you download a tarball or ZIP archive of the canonical source tree, unpack that archive, then run either "`./configure && make`" on unix or "`nmake /f Makefile.msc`" on Windows. More details available at the following:
- [How To Compile On Unix](https://sqlite.org/src/file/doc/compile-for-unix.md)
- [How To Compile On Windows](https://sqlite.org/src/file/doc/compile-for-windows.md)
# 4. How To Compile From The Amalgamation
With each release of SQLite, the developers make available pre-built copies of the SQLite amalgamation files that you can get from the [Download Page](https://sqlite.org/download.html). Look for files named "`sqlite-amalgamation-`*NNNNNNN*`.zip`" and "`sqlite-autoconf-`*NNNNNNN*`.tar.gz`". The first is just the amalgamation source files. The second also includes a "configure" script and Makefile.
# 5. Advantages Of Building From The Amalgamation
1. **Fewer Files To Worry With**
You can embed the amalgamation files you need in your own source tree, and compile them using your own Makefile. You don't really need a separate "configure" script or Makefile. Add the "sqlite3.c" and "sqlite3.h" files into your own source tree, and then they will always be there without creating a new dependency. When you want to upgrade, just download the latest version and replace the ones in your own source tree.
2. **Less To Download**
The amalgamation archives are less than 1/4th the size of the complete SQLite source tree. So there is less to download.
3. **You Will End Up Using The Amalgamation Regardless**
If you build from canonical sources, the Makefile first builds the amalgamation and then compiles the amalgamation into binary machine code. Why not just skip that first step and go right to compiling the amalgamation directly?
4. **You Know That The Amalgamation You Are Using Has Been Testing And Vetted By The SQLite Developers**
If you pull down the pre-build amalgamation files, you can have confidence that those exact source files have been run through the SQLite developers [rigorous testing process](testing.md). You don't have to worry that you somehow broke something as you were compiling the canonical sources into the amalgamation.
# 6. Advantages Of Building From Canonical Sources
1. **Access To More Compile-Time Options**
SQLite supports [many, many compile-time options](compile.md), some of which work with the amalgamation, but some of which do not. Depending on what compile-time options you want to use, you may need to build from canonical sources.
2. **Access To Historical And Unreleased Versions Of SQLite**
The amalgamation source code is normally only available for the latest released version of SQLite. If you want an historical version of SQLite, or if you want to try out the latest unreleased trunk version of SQLite because it has some new feature that you like or because you just want to contribute back by helping with pre-release testing, then you must compile from canonical source.
3. **Easier To Customize The Code**
If you are making your own custom enhancements or modifications to SQLite, then you should probably work with the canonical sources. The amalgamation is designed to be friendly to C-compilers, not human programmers. You can, in theory, make custom modifications directly to the amalgamation source code, but you will have an easier time of it if you use the canonical source files.
# 7. Summary: Which Should You Choose
The decision of whether to build SQLite from the amalgamation or from canonical sources depends on your specific circumstances. Review the advantages and disadvantages to each approach outlined in the paragraphs above and decide for yourself.
---
# The Base64() SQL Function
*Sección: Guides | Origen: https://www.sqlite.org/base64.html*
# 1. Overview
The base64() function is an SQL function implemented as a [loadable extension](loadext.md) for SQLite. The function converts a binary BLOB into equivalent [RFC 4648](https://datatracker.ietf.org/doc/html/rfc4648) text or converts RFC 4648 text into the equivalent BLOB.
The base64() function is not a standard part of SQLite. It must be loaded as a separate extension. The source code to base64() is in the [base64.c source file](https://sqlite.org/src/file/ext/misc/base64.c) in the [ext/misc/ folder](https://sqlite.org/src/file/ext/misc) of the SQLite source tree.
The base64() function is not included in standard builds of the SQLite library, but it is loaded by default in the [CLI](cli.md). This is typical of the [CLI](cli.md) which loads various extensions above and beyond what are available in the standard SQLite library.
# 2. Features
1. The base64() function always takes a single argument.
2. If the argument to base64() is a BLOB, then the return value is TEXT that is the [RFC 4648](https://datatracker.ietf.org/doc/html/rfc4648) encoding of that BLOB.
3. If the argument to base64() is base64 TEXT then the return value is a BLOB that is the binary data corresponding to that base64 TEXT.
4. If the argument to base64() is NULL, then NULL is returned.
5. An error is raised if the argument to base64() is something other than TEXT, BLOB, or NULL.
6. If the argument is TEXT, leading and trailing whitespace is ignored.
7. If the argument is TEXT that has a prefix that looks like base64 but contains non-base64 characters, then as much of the input as possible is translated into a BLOB and that BLOB is returned.
8. The base64() function uses the standard [RFC 4648](https://datatracker.ietf.org/doc/html/rfc4648) alphabet: "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/".
# 3. See Also
- Build-in SQL functions [hex()](lang_corefunc.md#hex) and [unhex()](lang_corefunc.md#unhex).
- Extension function [base85()](base85.md).
---
# The Base85() SQL Function
*Sección: Guides | Origen: https://www.sqlite.org/base85.html*
# 1. Overview
The base85() function is an SQL function implemented as a [loadable extension](loadext.md) for SQLite. The function converts a binary BLOB into an equivalent base-85 text encoding or converts that same base-85 text encoding back into a BLOB.
The base85() function is not a standard part of SQLite. It must be loaded as a separate extension. The source code to base85() is in the [base85.c source file](https://sqlite.org/src/file/ext/misc/base85.c) in the [ext/misc/ folder](https://sqlite.org/src/file/ext/misc) of the SQLite source tree.
The base85() function is not included in standard builds of the SQLite library, but it is loaded by default in the [CLI](cli.md). This is typical of the [CLI](cli.md) which loads various extensions above and beyond what are available in the standard SQLite library.
Like [base64()](base64.md) representations, the base85() function can be used to format binary content through any sane ASCII channel unmolested. It also plays nicely in CSV or written as TCL brace-enclosed literals or SQL string literals. It is not suited for unmodified use in XML-like documents.
# 2. Encoding
The encoding used resembles Ascii85, but was devised by the author (Larry Brasfield) before Mozilla, Adobe, ZMODEM or other Ascii85 variant sources existed, in the 1984 timeframe on a VAX mainframe. Further, this is an independent implementation of a base85 system. Hence, the author has rightfully put this into the public domain.
Base85 numerals are taken from the set of 7-bit USASCII codes, excluding control characters and Space ! " ' ( ) { \| } ~ Del in code order representing digit values 0 to 84 (base 10.)
Groups of 4 bytes, interpreted as big-endian 32-bit values, are represented as 5-digit base85 numbers with MS to LS digit order. Groups of 1-3 bytes are represented with 2-4 digits, still big-endian but 8-24 bit values. (Using big-endian yields the simplest transition to byte groups smaller than 4 bytes. These byte groups can also be considered base-256 numbers.) Groups of 0 bytes are represented with 0 digits and vice-versa. No pad characters are used; encoded base85 numeral sequence (aka "group") length maps 1-to-1 to the decoded binary length.
Any character not in the base85 numeral set delimits groups. When base85 is streamed or stored in containers of indefinite size, newline is used to separate it into sub-sequences of no more than 80 digits so that fgets() can be used to read it.
# 3. Features
1. The base85() function always takes a single argument that must be TEXT (for base85-to-binary conversion) or a BLOB (for binary-to-base85 conversion).
2. If the argument to base85() is a BLOB, then the return value is TEXT according to the encoding described above.
3. If the argument to base85() is TEXT as described above then the return value is a BLOB that is the binary data corresponding to that base85 text.
4. An error is raised if the argument to base85() is something other than TEXT or BLOB.
# 4. See Also
- Build-in SQL function [hex()](lang_corefunc.md#hex).
- Extension function [base64()](base64.md).
---
# The Bytecode() And Tables_Used() Table-Valued Functions
*Sección: Guides | Origen: https://www.sqlite.org/bytecodevtab.html*
# 1. Overview
Bytecode and tables_used are [virtual tables](vtab.md) built into SQLite that access information about [prepared statements](c3ref/stmt.md). Both bytecode and tables_used operate as [table-valued functions](vtab.md#tabfunc2). They take a single required argument which is either the text of an SQL statement, or a pointer to an existing prepared statement. The bytecode function returns one row of result for each [bytecode](opcode.md) operation in the prepared statement. The tables_used function returns one row for each persistent btree (either a table or an index) accessed by the prepared statement.
# 2. Usage
The bytecode and tables_used tables are only available if SQLite has been compiled with the [-DSQLITE_ENABLE_BYTECODE_VTAB](compile.md#enable_bytecode_vtab) compile-time option. The [CLI](cli.md) has been compiled that way, and so you can use the standard [CLI](cli.md) as a test platform to experiment.
Both virtual tables are read-only [eponymous-only virtual tables](vtab.md#epoonlyvtab). You use them by mentioning them directly in the FROM clause of a SELECT statement. They both require a single argument which is the SQL statement to be analyzed. For example:
SELECT \* FROM bytecode('SELECT \* FROM bytecode(?1)');\
The argument can be either the text of an SQL statement, in which case the bytecode (or tables_used) for that statement is returned, or the argument can be a parameter such as ?1 or \$stmt that is later bound to a [prepared statement](c3ref/stmt.md) object using the [sqlite3_bind_pointer()](c3ref/bind_blob.md) interface. Use a pointer type of "stmt-pointer" for the [sqlite3_bind_pointer()](c3ref/bind_blob.md) interface.
## 2.1. Schema For bytecode
The schema of the bytecode virtual table is:
CREATE TABLE bytecode(\
addr INT,\
opcode TEXT,\
p1 INT,\
p2 INT,\
p3 INT,\
p4 TEXT,\
p5 INT,\
comment TEXT,\
subprog TEXT,\
nexec INT,\
ncycle INT,\
stmt HIDDEN\
);\
The first eight columns are the address, opcode, and operands for a single [bytecode](opcode.md) in the virtual machine that implements the statement. These columns are the same columns output when using EXPLAIN.
The bytecode virtual tables shows all operations in the prepared statement, both the main body of the prepared statement and in subprograms used to implement triggers or foreign key actions. The "subprog" field is NULL for the main body of the prepared statement, or is the trigger name or the string "(FK)" for triggers and foreign key actions, respectively.
The "nexec" and "ncycle" columns show the number of times each opcode has been executed, and the total number of CPU cycles used by that opcode, respectively. These fields always have a value of 0 unless SQLite has been compiled with [SQLITE_ENABLE_STMT_SCANSTATUS](compile.md#enable_stmt_scanstatus) compile-time options and scan-status statistics are enabled using the [sqlite3_db_config](c3ref/db_config.md)(db,[SQLITE_DBCONFIG_STMT_SCANSTATUS](c3ref/c_dbconfig_defensive.md#sqlitedbconfigstmtscanstatus),...) interface. The values for nexec and ncycle are cumulative, until reset using [sqlite3_stmt_scanstatus_reset()](c3ref/stmt_scanstatus_reset.md).
The "ncycle" column currently always returns 0 unless SQLite is compiled for X86_64 or AARCH64 processors using GCC, Clang, or MSVC, or compiled for PPC processors using GCC or Clang.
## 2.2. Schema For tables_used
The schema for the tables_used table is:
CREATE TABLE tables_used(\
type TEXT,\
schema TEXT,\
name TEXT,\
wr INT,\
subprog TEXT,\
stmt HIDDEN\
);\
The tables_used table is intended to show which btrees of the database file are read or written by a prepared statement, both by the main statement itself but also by related triggers and foreign key actions. The columns are as follows:
- **type** → Either "table" or "index", depending on what role the btree is serving.
- **schema** → Which database file the btree is located in. This will be "main" for the main database (the usual case), or "temp" for TEMP tables and indexes, or the name assigned to [attached](lang_attach.md) databases by the [ATTACH](lang_attach.md) statement.
- **name** → The name of the table or index
- **wr** → 0 if the object is read, 1 if the object is written
- **subprog** → The sub-program in which the object is accessed. NULL means the main body of the prepared statement. Otherwise this field is the name of a trigger or "(FK)" for a foreign key action.
---
# The Checksum VFS Shim
*Sección: Guides | Origen: https://www.sqlite.org/cksumvfs.html*
# 1. Overview
The checksum VFS extension is a [VFS shim](vfs.md#shim) that adds an 8-byte checksum to the end of every page in an SQLite database. The checksum is added as each page is written and verified as each page is read. The checksum is intended to help detect database corruption caused by random bit-flips in the mass storage device.
The checksum VFS extension requires SQLite version 3.32.0 (2020-05-22) or later. It will not work with earlier versions of SQLite.
# 2. Compiling
The checksum VFS module is a [loadable extension](loadext.md). It is not included in the [amalgamation](amalgamation.md). It must be added to SQLite either at compile-time or at run-time. The source code to the checksum VFS module is in the [ext/misc/cksumvfs.c](https://sqlite.org/src/file/ext/misc/cksumvfs.c) source file in the [SQLite source tree](https://sqlite.org/src).
To build the checksum VFS module into a run-time loadable extension, use commands similar to the following:
- (linux) → `gcc -fPIC -shared cksumvfs.c -o cksumvfs.so`
- (mac) → `clang -fPIC -dynamiclib cksumvfs.c -o cksumvfs.dylib`
- (windows) → `cl cksumvfs.c -link -dll -out:cksumvfs.dll`
You may want to add additional compiler options, of course, according to the needs of your project.
To statically link this extension with your product, compile it like any other C-language module but add the "-DSQLITE_CKSUMVFS_STATIC" option so that this module knows that it is being statically linked rather than dynamically linked.
# 3. Loading
To load this extension as a shared library, you first have to bring up a dummy SQLite database connection to use as the argument to the [sqlite3_load_extension()](c3ref/load_extension.md) API call. Then you invoke the [sqlite3_load_extension()](c3ref/load_extension.md) API and shutdown the dummy database connection. All subsequent database connections that are opened will include this extension. For example:
sqlite3 \*db;\
sqlite3_open(":memory:", &db);\
sqlite3_load_extension(db, "./cksumvfs");\
sqlite3_close(db);\
If this extension is compiled with -DSQLITE_CKSUMVFS_STATIC and statically linked against the application, initialize it using a single API call as follows:
sqlite3_cksumvfs_init();\
Cksumvfs is a [VFS shim](vfs.md#shim). When loaded, "cksmvfs" becomes the new default VFS, and it uses the prior default VFS as the next VFS down in the stack. This is normally what you want. However, in complex situations where multiple VFS shims are being loaded, it might be important to ensure that cksumvfs is loaded in the correct order so that it sequences itself into the default VFS Shim stack in the right order.
# 4. Usage
Open database connections using the [sqlite3_open()](c3ref/open.md) or [sqlite3_open_v2()](c3ref/open.md) interfaces, as normal. Ordinary database files (without a checksum) will operate normally. Databases with checksums will return an SQLITE_IOERR_DATA error if a page is encountered that contains an invalid checksum.
Checksumming only works on databases that have a [reserve bytes](fileformat2.md#resbyte) value of exactly 8. The default value for reserve-bytes is 0. Hence, newly created database files will omit the checksum by default. To create a database that includes a checksum, change the reserve-bytes value to 8 by running code similar to this:
int n = 8;\
sqlite3_file_control(db, 0, SQLITE_FCNTL_RESERVE_BYTES, &n);\
If you do this immediately after creating a new database file, before anything else has been written into the file, then that might be all that you need to do. Otherwise, the API call above should be followed by:
sqlite3_exec(db, "VACUUM", 0, 0, 0);\
It never hurts to run the VACUUM, even if you don't need it. If the database is in WAL mode, you should shutdown and reopen all database connections before continuing.
From the CLI, use the ".filectrl reserve_bytes 8" command, followed by "VACUUM;".
Note that SQLite allows the number of reserve-bytes to be increased but not decreased. So if a database file already has a reserve-bytes value greater than 8, there is no way to activate checksumming on that database, other than to dump and restore the database file. Note also that other extensions might also make use of the reserve-bytes. Checksumming will be incompatible with those other extensions.
# 5. Verification Of Checksums
If any checksum is incorrect, the "PRAGMA quick_check" command will find it. To verify that checksums are actually enabled and running, use SQL like the following:
SELECT count(\*), verify_checksum(data)\
FROM sqlite_dbpage\
GROUP BY 2;\
There are three possible outputs from the verify_checksum() function: 1, 0, and NULL. 1 is returned if the checksum is correct. 0 is returned if the checksum is incorrect. NULL is returned if the page is unreadable. If checksumming is enabled, the read will fail if the checksum is wrong, so the usual result from verify_checksum() on a bad checksum is NULL.
If everything is OK, the query above should return a single row where the second column is 1. Any other result indicates either that there is a checksum error, or checksum validation is disabled.
# 6. Controlling Checksum Verification
The cksumvfs extension implements a new PRAGMA statement that can be used to disable, re-enable, or query the status of checksum verification:
PRAGMA checksum_verification; -- query status\
PRAGMA checksum_verification=OFF; -- disable verification\
PRAGMA checksum_verification=ON; -- re-enable verification\
The "checksum_verification" pragma will return "1" (true) or "0" (false) if checksum verification is enabled or disabled, respectively. "Verification" in this context means the feature that causes SQLITE_IOERR_DATA errors if a checksum mismatch is detected while reading. Checksums are always kept up-to-date as long as the [reserve bytes](fileformat2.md#resbyte) value of the database is 8, regardless of the setting of this pragma. Checksum verification can be disabled (for example) to do forensic analysis of a database that has previously reported a checksum error.
The "checksum_verification" pragma will always respond with "0" if the database file does not have a [reserve bytes](fileformat2.md#resbyte) value of 8. The pragma will return no rows at all if the cksumvfs extension is not loaded.
---
# The COMPLETION() Table-Valued Function
*Sección: Guides | Origen: https://www.sqlite.org/completion.html*
# 1. Overview
The COMPLETION extension implements a [table-valued function](vtab.md#tabfunc2) named "completion" that can be used to suggest completions of partially entered words during interactive SQL input. The completion table can be used to help implement tab-completion, for example.
# 2. Details
The designed query interface is:
SELECT DISTINCT candidate COLLATE nocase\
FROM completion(\$prefix, \$wholeline)\
ORDER BY 1;\
The query above will return suggestions for the whole input word that begins with \$prefix. The \$wholeline parameter is all text from the beginning of the line up to the insertion point. The \$wholeline parameter is used for context.
The \$prefix parameter may be NULL, in which case the prefix is deduced from \$wholeline. Or, the \$wholeline parameter may be NULL or omitted if context information is unavailable or if context-aware completion is not desired.
The completion table might return the same candidate more than once, and it will return candidates in an arbitrary order. The DISTINCT keyword and the ORDER BY in the sample query above are added to make the answers unique and in lexicographical order.
## 2.1. Example Usage
The completion table is used to implement tab-completion in the [command-line shell](cli.md) in conjunction with either the readline or linenoise input line editing packages for unix. See the | Column | >Normal meaning | >Aggregate-mode meaning | >
|---|---|---|
| name | >The name of the table or index that is implemented by the btree of the current row | >|
| path | >See description above | >Always NULL | >
| pageno | >The page number of the database page for the current row | >The total number of pages in the btree for the current row | >
| pagetype | >'leaf' or 'interior' | >Always NULL | >
| ncell | >Number of cells on the current page or btree | >|
| payload | >Bytes of useful payload on the current page or btree | >|
| unused | >Unused bytes of on the current page or btree | >|
| mx_payload | >The largest payload found anywhere in the current page or btree. | >|
| pgoffset | >Byte offset to the start of the page | >Always NULL | >
| pgsize | >Total storage space used by the current page or btree. | >|
In the diagram, each of the 8 tables in the FROM clause of the query is identified by a large circle with the label of the FROM-clause term: N2, S, L, P, O, C, N1 and R. The arcs in the graph represent the estimated cost of computing each term assuming that the origin of the arc is in an outer loop. For example, the cost of running the S loop as an inner loop to L is 2.30 whereas the cost of running the S loop as an outer loop to L is 9.17.
The "cost" here is logarithmic. With nested loops, the work is multiplied, not added. But it is customary to think of graphs with additive weights and so the graph shows the logarithm of the various costs. The graph shows a cost advantage of S being inside of L of about 6.87, but this translates into the query running about 963 times faster when S loop is inside of the L loop rather than being outside of it.
The arrows from the small circles labeled with "\*" indicate the cost of running each loop with no dependencies. The outermost loop must use this \*-cost. Inner loops have the option of using the \*-cost or a cost assuming one of the other terms is in an outer loop, whichever gives the best result. One can think of the \*-costs as a short-hand notation indicating multiple arcs, one from each of the other nodes in the graph. The graph is therefore "complete", meaning that there are arcs (some explicit and some implied) in both directions between every pair of nodes in the graph.
The problem of finding the best query plan is equivalent to finding a minimum-cost path through the graph that visits each node exactly once.
(Side note: The cost estimates in the TPC-H Q8 graph above were computed by the query planner in SQLite 3.7.16 and converted using a natural logarithm.)
## 3.2. Complications
The presentation of the query planner problem above is a simplification. The costs are estimates. We cannot know what the true cost of running a loop is until we actually run the loop. SQLite makes guesses for the cost of running a loop based on the availability of indexes and constraints found in the WHERE clause. These guesses are usually pretty good, but they can sometimes be off. Using the [ANALYZE](lang_analyze.md) command to collect additional statistical information about the database can sometimes enable SQLite to make better guesses about the cost.
The costs are comprised of multiple numbers, not a single number as shown in the graph. SQLite computes several different estimated costs for each loop that apply at different times. For example, there is a "setup" cost that is incurred just once when the query starts. The setup cost is the cost of computing a [query-time index](optoverview.md#autoindex) for a table that does not already have an index. Then there is the cost of running each step of the loop. Finally, there is an estimate of the number of rows generated by the loop, which is information needed in estimating the costs of inner loops. Sorting costs may come into play if the query has an ORDER BY clause.
In a general query, dependencies need not be on a single loop, and hence the matrix of dependencies might not be representable as a graph. For example, one of the WHERE clause constraints might be S.a=L.b+P.c, implying that the S loop must be an inner loop of both L and P. Such dependencies cannot be drawn as a graph since there is no way for an arc to originate at two or more nodes at once.
If the query contains an ORDER BY clause or a GROUP BY clause or if the query uses the DISTINCT keyword then it is advantageous to select a path through the graph that causes rows to naturally appear in sorted order, so that no separate sorting step is required. Automatic elimination of ORDER BY clauses can make a large performance difference, so this is another factor that needs to be considered in a complete implementation.
In the TPC-H Q8 query, the setup costs are all negligible, all dependencies are between individual nodes, and there is no ORDER BY, GROUP BY, or DISTINCT clause. So for TPC-H Q8, the graph above is a reasonable representation of what needs to be computed. The general case involves a lot of extra complication, which for clarity is neglected in the remainder of this article.
## 3.3. Finding The Best Query Plan
Prior to [version 3.8.0](releaselog/3_8_0.md) (2013-08-26), SQLite always used the "Nearest Neighbor" or "NN" heuristic when searching for the best query plan. The NN heuristic makes a single traversal of the graph, always choosing the lowest-cost arc as the next step. The NN heuristic works surprisingly well in most cases. And NN is fast, so that SQLite is able to quickly find good plans for even large 64-way joins. In contrast, other SQL database engines that do more extensive searching tend to bog down when the number of tables in a join goes above 10 or 15.
Unfortunately, the query plan computed by NN for TPC-H Q8 is not optimal. The plan computed using NN is R-N1-N2-S-C-O-L-P with a cost of 36.92. The notation in the previous sentence means that the R table is run in the outer loop, N1 is in the next inner loop, N2 is in the third loop, and so forth down to P which is in the inner-most loop. The shortest path through the graph (as found via exhaustive search) is P-L-O-C-N1-R-S-N2 with a cost of 27.38. The difference might not seem like much, but remember that the costs are logarithmic, so the shortest path is nearly 750 times faster than that path found using the NN heuristic.
One solution to this problem is to change SQLite to do an exhaustive search for the best path. But an exhaustive search requires time proportional to K! (where K is the number of tables in the join) and so when you get beyond a 10-way join, the time to run [sqlite3_prepare()](c3ref/prepare.md) becomes very large.
## 3.4. The N Nearest Neighbors or "N3" Algorithm
The NGQP uses a new algorithm for seeking the best path through the graph: "N Nearest Neighbors" (hereafter "N3"). With N3, instead of choosing just one nearest neighbor for each step, the algorithm keeps track of the N bests paths at each step for some small integer N.
Suppose N=4. Then for the TPC-H Q8 graph, the first step finds the four shortest paths to visit any single node in the graph:
> R (cost: 3.56)\
> N1 (cost: 5.52)\
> N2 (cost: 5.52)\
> P (cost: 7.71)\
The second step finds the four shortest paths to visit two nodes beginning with one of the four paths from the previous step. In the case where two or more paths are equivalent (they have the same set of visited nodes, though possibly in a different order) only the first and lowest-cost path is retained. We have:
> R-N1 (cost: 7.03)\
> R-N2 (cost: 9.08)\
> N2-N1 (cost: 11.04)\
> R-P {cost: 11.27}\
The third step starts with the four shortest two-node paths and finds the four shortest three-node paths:
> R-N1-N2 (cost: 12.55)\
> R-N1-C (cost: 13.43)\
> R-N1-P (cost: 14.74)\
> R-N2-S (cost: 15.08)\
And so forth. There are 8 nodes in the TPC-H Q8 query, so this process repeats a total of 8 times. In the general case of a K-way join, the storage requirement is O(N) and the computation time is O(K\*N), which is significantly faster than the O(2K) exact solution.
But what value to choose for N? One might try N=K. This makes the algorithm O(K2) which is actually still quite efficient, since the maximum value of K is 64 and K rarely exceeds 10. But that is not enough for the TPC-H Q8 problem. With N=8 on TPC-H Q8 the N3 algorithm finds the solution R-N1-C-O-L-S-N2-P with a cost of 29.78. That is a big improvement over NN, but it is still not optimal. N3 finds the optimal solution for TPC-H Q8 when N is 10 or greater.
The initial implementation of NGQP chooses N=1 for simple queries, N=5 for two-way joins and N=10 for all joins with three or more tables. Later, the N value for joins with three or more tables was raised to 12 or to 18 if the join is against a star-schema. Further refinements are likely in the future.
# 4. The Star-Query Heuristic
The [N3 algorithm](queryplanner-ng.md#n3) works well for most queries. But there are a few cases where it generates a bad plan. Specifically, for some queries against a [star-schema](https://en.wikipedia.org/wiki/Star_schema) where there is a large fact table and six or more small dimension tables and where there exist indexes going in both directions, the N3 algorithm misses the best query plan unless the N parameter is very large - exponential in the number of dimension tables. Call these kinds of queries "star-queries". More recent versions of SQLite (circa 2024 or 2025 and later) implement a heuristic to work around this, so that efficient query plans are chosen for star-queries, without requiring hints from the programmer.
## 4.1. Background: What Is A Star-Query
A star-schema is a common relational database design in which there is a large "fact-table" surrounding by smaller "dimension-tables". The dimension-tables are typically keyed by integer ID values and hold a variety of other attributes that are accessed using that ID. The fact-table contains ID values referencing the various dimension tables.
For example, suppose you have dimension tables, all with integer ID values as their PRIMARY KEY, like this:
- A PRODUCT table holds information about each product.
- A SELLER table holds information about each sales staff member.
- A CUSTOMER table holds information about each customer.
- A CARRIER table holds information about each shipping provider.
- A WAREHOUSE table holds information about all warehouses.
Each of the dimension tables is relatively small. How many warehouses does your business operate? Maybe PRODUCT and CUSTOMER are somewhat larger, but the number of entries might be still measured in thousands, not millions.
The dimension tables are bound together by a single SALES table that records each sale. The SALES table contains things like:
- The time and value of the sale.
- The PRODUCT-id, SELLER-id, CUSTOMER-id, CARRIER-id, and WAREHOUSE-id.
The SALES table is our fact-table. The number of entries in SALES is orders of magnitude larger than any of the dimension tables. And each SALES table row references a single entry in the various dimension tables. A dimension table row might reference many thousands of SALES table rows, on the other hand.
This is a classic example of a star-schema. Data representations like this come up all the time, and in diverse fields. We call queries against this schema a "star-query". For example, asking for a complete report of all sales between the hours of 12:00 and 14:00 on 2024-01-04 would be a star-query. The SALES table would be consulted to find all entries between the specified hours, then the various dimension tables would be consulted to look up information about each individual sale.
## 4.2. Query Planning Problems With High-Dimensionality Star-Queries
The [N3 query planning algorithm](queryplanner-ng.md#n3) described above works fine and generates a optimal solution for star-queries with less than five or six dimension tables. However, if the number of dimension tables grows larger, then depending on how indexes are defined and on the relative sizes of the fact and dimension tables, the N3 algorithm will sometimes find a suboptimal plan.
That happens because N3 is still a greedy algorithm. Even though it is keeping track of up to N different solutions at each step, it only follows the N best solutions. That leads to problems as follows:
The step of finding all relevant entries in the fact table can be slow, because the fact table is so big. Finding relevant values of the fact table might be slower than doing a full table scan of the relatively small dimension tables. The best plan is usually to spend time finding the relevant rows of the fact table first and then do primary-key lookups of corresponding dimension table rows. But because N3 is a greedy algorithm, it tends to accumulate a bunch of full-table scans of dimension tables in its N-best plan set early in the search. If there enough dimension tables, they can fill up all N available slots and push out the best plan which starts with the more expensive search of the fact table.
N3 will still always find the best plan in the end, given a large enough value for N. The trouble is that a sufficiently large N might be exponential in the number of dimension tables. That means that overall query planning algorithm would require exponential time. N3 works great with three or four dimension tables. With a larger number of dimension tables, however, it starts to generate query plans that include full-table scans of the smaller dimension tables, which severely degrades performance.
## 4.3. A Large Test Case
The [test/starschema1.test](https://sqlite.org/src/file/test/starschema1.test) test script in the SQLite source tree shows a star-query with one fact table and 63 dimension tables. This test case is contrived, but it does demonstrate how the N3 algorithm can fail unless it is amended, as described in the next section.
## 4.4. Tweaks To N3 To Support Star Queries
To help the SQLite query planner come up with better query plans for star-queries, heuristics are used to adjust cost estimates for searching the various tables.
The current heuristic, as of version 3.49.0 (2025-02-06), is to artificially raise the estimated full-table scan cost for dimension tables so that the cost is slightly greater than the cost of finding the relevant rows of the fact table. This prevents a bunch of pointless full-table scans of dimension tables from pushing the search of the fact table out of the set of N-best solutions early in the algorithm, so that doing the fact table search wins in the end. Only the full-table scan costs of dimension tables are modified. The estimated costs for all other access methods is unchanged, and no costs are changed for tables of the query that are not clearly dimension tables, or for which the evaluation order is already constrained by OUTER JOINs. So the disruption to the algorithm is minimal, but sufficient to always find a good solution for star-queries even with a large number of dimensions.
A different heuristic was used in SQLite versions 3.47.0 and 3.48.0. The earlier heuristic was to lower the cost of all fact-table access methods so that they were able to out-compete full-table scans of the dimension tables, and thus avoid being eliminated from consideration early in the algorithm. However, this artificial lowering of the fact-table cost created other distortions that lead to performance regressions for other complex joins.
# 5. Hazards Of Upgrading To NGQP
*→ **This section is obsolete and retained for historical reference only.** ← This section was important when the NGQP was new. But a decade has elapsed, the NGQP has been deployed successfully to billions of devices, and everyone has upgraded, and no performance regressions were ever reported back to the SQLite developers. The upgrade hazard has vanished. **Skip ahead to the [query planner checklist](queryplanner-ng.md#howtofix)**.*
For most applications, upgrading from the legacy query planner to the NGQP requires little thought or effort. Simply replace the older SQLite version with the newer version of SQLite and recompile and the application will run faster. There are no API changes nor modifications to compilation procedures.
But as with any query planner change, upgrading to the NGQP does carry a small risk of introducing performance regressions. The problem here is not that the NGQP is incorrect or buggy or inferior to the legacy query planner. Given reliable information about the selectivity of indexes, the NGQP should always pick a plan that is as good as before, or better. The problem is that some applications may be using low-quality and low-selectivity indexes without having run [ANALYZE](lang_analyze.md). The older query planners look at many fewer possible implementations for each query and so they may have stumbled over a good plan by stupid luck. The NGQP, on the other hand, looks at many more query plan possibilities, and it may choose a different query plan that works better in theory, assuming good indexes, but which gives a performance regression in practice, because of the shape of the data.
Key points:
- The NGQP will always find an equal or better query plan, compared to prior query planners, as long as it has access to accurate [ANALYZE](lang_analyze.md) data in the [SQLITE_STAT1](fileformat2.md#stat1tab) file.
- The NGQP will always find a good query plan as long as the schema does not contain indexes that have more than about 10 or 20 rows with the same value in the left-most column of the index.
Not all applications meet these conditions. Fortunately, the NGQP will still usually find good query plans, even without these conditions. However, cases do arise (rarely) where performance regressions can occur.
## 5.1. Case Study: Upgrading Fossil to the NGQP
The [Fossil DVCS](http://www.fossil-scm.org/) is the version control system used to track all of the SQLite source code. A Fossil repository is an SQLite database file. (Readers are invited to ponder this recursion as an independent exercise.) Fossil is both the version-control system for SQLite and a test platform for SQLite. Whenever enhancements are made to SQLite, Fossil is one of the first applications to test and evaluate those enhancements. So Fossil was an early adopter of the NGQP.
Unfortunately, the NGQP caused a performance regression in Fossil.
One of the many reports that Fossil makes available is a timeline of changes to a single branch showing all merges in and out of that branch. See 
In the "without ANALYZE" case on the left, the NN algorithm chooses loop P (PLINK) as the outer loop because 4.9 is less than 5.2, resulting in path P-T which is algorithm-1. NN only looks at the single best choice at each step so it completely misses the fact that 5.2+4.4 makes a slightly cheaper plan than 4.9+4.8. But the N3 algorithm keeps track of the 5 best paths for a 2-way join, so it ends up selecting path T-P because of its slightly lower overall cost. Path T-P is algorithm-2.
Note that with ANALYZE the cost estimates are better aligned with reality and algorithm-1 is selected by both NN and N3.
(Side note: The costs estimates in the two most recent graphs were computed by the NGQP using a base-2 logarithm and slightly different cost assumptions compared to the legacy query planner. Hence, the cost estimates in these latter two graphs are not directly comparable to the cost estimates in the TPC-H Q8 graph.)
## 5.2. Fixing The Problem
Running [ANALYZE](lang_analyze.md) on the repository database immediately fixed the performance problem. However, we want Fossil to be robust and to always work quickly regardless of whether or not its repository has been analyzed. For this reason, the query was modified to use the CROSS JOIN operator instead of the plain JOIN operator. SQLite will not reorder the tables of a CROSS JOIN. This is a long-standing feature of SQLite that is specifically designed to allow knowledgeable programmers to enforce a particular loop nesting order. Once the join was changed to CROSS JOIN (the addition of a single keyword) the NGQP was forced to choose the faster algorithm-1 regardless of whether or not statistical information had been gathered using ANALYZE.
We say that algorithm-1 is "faster", but this is not strictly true. Algorithm-1 is faster in common repositories, but it is possible to construct a repository in which every check-in is on a different uniquely-named branch and all check-ins are children of the root check-in. In that case, TAGXREF_I1 would become more selective than PLINK_I1 and algorithm-2 really would be the faster choice. However such repositories are very unlikely to appear in practice and so hard-coding the loop nested order using the CROSS JOIN syntax is a reasonable solution to the problem in this case.
## 5.3. Update 2017: A Better Fix
The prior text was written in early 2013, before the first release of SQLite version 3.8.0. This paragraph was added in mid 2021. While all of the previous discussion remains true, a lot of improvements have been made to the query planner, making this whole section largely moot.
In 2017, Fossil was enhanced to make use of the new [PRAGMA optimize](pragma.md#pragma_optimize) statement. Whenever Fossil is about to close the database connection to its repository, it first runs "PRAGMA optimize", which will in turn cause ANALYZE to be run if it is needed. Usually an ANALYZE is not needed, and so there is no measurable performance penalty for doing this. But every now and then ANALYZE might be run on a few of the tables in the repository database. Because of this, query planning issues such as the one described here no longer come up in Fossil. The fact that ANALYZE is run periodically to keep the [sqlite_stat1](fileformat2.md#stat1tab) table up-to-date means that hand-tuning of queries is no longer required. We have not had to tweak a query in Fossil in ages.
Therefore, the current recommendation for avoiding problems such as this one is to simply run "PRAGMA optimize" just prior to closing each database connection. Or, if your application is long-running and never closes any database connections, then run "PRAGMA optimize" once per day or so. Also consider running "PRAGMA optimize" after any schema change.
# 6. Checklist For Avoiding Or Fixing Query Planner Problems
1. **Don't panic!** Cases where the query planner picks an inferior plan are actually quite rare. You are unlikely to run across any problems in your application. If you are not having performance issues, you do not need to worry about any of this.
2. **Create appropriate indexes.** Most SQL performance problems arise not because of query planner issues but rather due to lack of appropriate indexes. Make sure indexes are available to assist all large queries. Most performance issues can be resolved by one or two CREATE INDEX commands and with no changes to application code.
3. **Avoid creating low-quality indexes.**. A low-quality index (for the purpose of this checklist) is one where there are more than 10 or 20 rows in the table that have the same value for the left-most column of the index. In particular, avoid using boolean or "enum" columns as the left-most columns of your indexes.
The Fossil performance problem described in the previous section of this document arose because there were over ten-thousand entries in the TAGXREF table with the same value for the left-most column (the TAGID column) of the TAGXREF_I1 index.
4. **If you must use a low-quality index, be sure to run [ANALYZE](lang_analyze.md).** Low-quality indexes will not confuse the query planner as long as the query planner knows that the indexes are of low quality. And the way the query planner knows this is by the content of the [SQLITE_STAT1](fileformat2.md#stat1tab) table, which is computed by the ANALYZE command.
Of course, ANALYZE only works effectively if you have a significant amount of content in your database in the first place. When creating a new database that you expect to accumulate a lot of data, you can run the command "ANALYZE sqlite_schema" to create the SQLITE_STAT1 table, then prepopulate the [sqlite_stat1](fileformat2.md#stat1tab) table (using ordinary INSERT statements) with content that describes a typical database for your application - perhaps content that you extracted after running ANALYZE on a well-populated template database in the lab. Or, you could just run "[PRAGMA optimize](pragma.md#pragma_optimize)" before shutting down database connections so that ANALYZE will be run automatically as needed to keep the [sqlite_stat1](fileformat2.md#stat1tab) table current.
5. **Instrument your code.** Add logic that lets you know quickly and easily which queries are taking too much time. Then work on just those specific queries.
------------------------------------------------------------------------
*Update 2024: The query planner has been improved so much over the years that you should never need to use any of the hacks described below. The capabilities described below are still available, for backwards compatibility. But you shouldn't use them. If you do find a case where you are getting a suboptimal query plan, please report it to the SQLite developers on the [SQLite Forum](https://sqlite.org/forum) so that they can try to fix the problem. In other words:*
**Stop Reading Here!**
To help encourage you to stop reading, the remainder of this checklist is now grayed out.
------------------------------------------------------------------------
6. Use [unlikely()](lang_corefunc.md#unlikely) and [likelihood()](lang_corefunc.md#likelihood) SQL functions. SQLite normally assumes that terms in the WHERE clause that cannot be used by indexes have a strong probability of being true. If this assumption is incorrect, it could lead to a suboptimal query plan. The [unlikely()](lang_corefunc.md#unlikely) and [likelihood()](lang_corefunc.md#likelihood) SQL functions can be used to provide hints to the query planner about WHERE clause terms that are probably not true, and thus aid the query planner in selecting the best possible plan.
7. Use the [CROSS JOIN](optoverview.md#crossjoin) syntax to enforce a particular loop nesting order on queries that might use low-quality indexes in an unanalyzed database. SQLite [treats the CROSS JOIN operator specially](lang_select.md#crossjoin), forcing the table to the left to be an outer loop relative to the table on the right.
8. Use unary "+" operators to disqualify WHERE clause terms. If the query planner insists on selecting a poor-quality index for a particular query when a much higher-quality index is available, then [careful use of unary "+" operators](optoverview.md#uplus) in the WHERE clause can force the query planner away from the poor-quality index. Avoid using this trick if at all possible, and especially avoid it early in the application development cycle. Beware that adding a unary "+" operator to an equality expression might change the result of that expression if [type affinity](datatype3.md#affinity) is involved.
9. Use the [INDEXED BY](lang_indexedby.md) syntax to enforce the selection of particular indexes on problem queries. As with the previous two bullets, avoid this step if possible, and especially avoid doing this early in development as it is clearly a premature optimization.
# 7. Summary
The query planner in SQLite normally does a terrific job of selecting fast algorithms for running your SQL statements. This is true of the legacy query planner and even more true of the new NGQP. There may be an occasional situation where, due to incomplete information, the query planner selects a suboptimal plan. This will happen less often with the NGQP than with the legacy query planner, but it might still happen. Only in those rare cases do application developers need to get involved and help the query planner to do the right thing. In the common case, the NGQP is just a new enhancement to SQLite that makes the application run a little faster and which requires no new developer thought or action.
---
# The Percentile Extension
*Sección: Guides | Origen: https://www.sqlite.org/percentile.html*
# 1. Overview
The percentile extension provides four aggregate functions that compute a percentile score and/or the median value for a distribution.
## 1.1. Availability
The percentile extension has been part of [the amalgamation](amalgamation.md) since SQLite version 3.51.0 (2025-11-04). However, the percentile extension is disabled by default and must be activated at compile-time using the [-DSQLITE_ENABLE_PERCENTILE](compile.md#enable_percentile) compile-time option.
Prior to SQLite 3.51.0, the percentile extension was in a separate source code file that needed to be compiled independently and treated as a [loadable extension](loadext.md).
# 2. Aggregate Functions Implemented By Percentile
The percentile extension implements the aggregate SQL functions described below. The algorithms used by all of these functions use O(N) space and O(NlogN) time, where N is the number of non-NULL inputs.
## 2.1. The median(Y) aggregate function
The median(Y) function is an aggregate that computes the median value of all non-NULL inputs Y. If any Y input to median() is not NULL and is not a numeric value, an error is raised. If there are no non-NULL, numeric inputs, then the result of median() is NULL.
The median is the value of the center element when all the inputs are sorted and the number of inputs is odd. If the number of inputs is even, then the median is the average of the two center inputs.
The median(Y) function is equivalent to [percentile(Y,50)](lang_aggfunc.md#percentile).
## 2.2. The percentile(Y,P) aggregate function
The percentile(Y,P) aggregate function computes an answer X which is a value that is greater than or equal to P percent of the non-NULL inputs and which is less than or equal to 100-P percent of the inputs. The parameter P must be a number between 0.0 and 100.0. The value of P must be the same for all terms of the aggregate and may not be NULL. Y inputs must be either NULL or numeric. NULL values for Y are ignored. Any non-NULL Y input that is not numeric causes an error to be raised.
The percentile() function works by sorting the non-NULL inputs and then computing the input or inputs that are closest to P percent from the first to the last. The return value is the weighted average of the two closest inputs.
## 2.3. The percentile_cont(Y,P) aggregate function
The percentile_cont(Y,P) function works like [percentile(Y,P)](lang_aggfunc.md#percentile) except that the P value spans the range of 0.0 to 1.0 instead of 0.0 to 100.0. Thus the result of percentile_cont(Y,P) is the same as [percentile(Y,P\*100)](lang_aggfunc.md#percentile).
The percentile_cont() function is defined by SQL standards. However, instead of being a simple function call "percentile_cont(Y,P)", the SQL-standard syntax goes like this:
SELECT percentile_cont(P) WITHIN GROUP (ORDER BY Y) FROM tab;\
That is a lot of syntax to mean exactly the same thing as:
SELECT percentile_cont(Y,P) FROM tab;\
SQLite will support the SQL-standard syntax, but only if it is compiled (from canonical sources, not from the [amalgamation](amalgamation.md)) using the [-DSQLITE_ENABLE_ORDERED_SET_AGGREGATES=1](compile.md#enable_ordered_set_aggregates) compile-time option. Without that compile-time option, only the simpler "percentile_cont(Y,P)" form is supported. Since there are no advantages to the prolix SQL-standard format, and dramatic readability disadvantages, and because the [SQLITE_ENABLE_ORDERED_SET_AGGREGATES](compile.md#enable_ordered_set_aggregates) compile-time option causes the SQLite library to be larger, that option is omitted from most builds.
This author believes that the "\_cont" suffix on this function name is an abbreviation for "continuous" and reflects the fact that the return value is a weighted average of the two closest input values to the actual percentile rank. The name is an SQL standard, not something chosen by the SQLite developers.
## 2.4. The percentile_disc(Y,P) aggregate function
The percentile_disc(Y,P) function works like [percentile_cont(Y,P)](lang_aggfunc.md#percentile_cont) except that instead of doing a weighted average of the closest available inputs, it always returns a value that is one of the input values - the smaller of the two possible choices. The percentile_disc(Y,P) function is defined by SQL standards. As with percentile_cont(), the prolix ordered-set aggregate syntax is required, but that syntax is only supported by SQLite when SQLite is compiled using the [SQLITE_ENABLE_ORDERED_SET_AGGREGATES](compile.md#enable_ordered_set_aggregates) compile-time option.
This author believes that the "\_disc" suffix on this function name is an abbreviation for "discrete". The name is an SQL standard, not something chosen by the SQLite developers.
# 3. Design Requirements
The following requirements define the percentile extension.
1. The percentile(Y,P) function is an aggregate function taking exactly two arguments.
2. If the P argument to percentile(Y,P) is not the same for every row in the aggregate then an error is thrown. The word "same" in the previous sentence means that the value differs by less than 0.001.
3. If the P argument to percentile(Y,P) evaluates to anything other than a number in the range of 0.0 to 100.0 inclusive then an error is thrown.
4. If any Y argument to percentile(Y,P) evaluates to a value that is not NULL and is not numeric then an error is thrown.
5. If any Y argument to percentile(Y,P) evaluates to plus or minus infinity then an error is thrown. (SQLite always interprets NaN values as NULL.)
6. Both Y and P in percentile(Y,P) can be arbitrary expressions, including CASE WHEN expressions.
7. The percentile(Y,P) aggregate is able to handle inputs of at least one million (1,000,000) rows.
8. If there are no non-NULL values for Y, then percentile(Y,P) returns NULL.
9. If there is exactly one non-NULL value for Y, the percentile(Y,P) returns the one Y value.
10. If there are N non-NULL values of Y where N is two or more and the Y values are ordered from least to greatest and a graph is drawn from 0 to N-1 such that the height of the graph at J is the J-th Y value and such that straight lines are drawn between adjacent Y values, then the percentile(Y,P) function returns the height of the graph at P\*(N-1)/100.
11. The percentile(Y,P) function always returns either a floating point number or NULL.
12. The percentile(Y,P) is implemented as a single C99 source-code file that compiles into a shared-library or DLL that can be loaded into SQLite using the sqlite3_load_extension() interface.
13. A separate median(Y) function is the equivalent of percentile(Y,50).
14. A separate percentile_cont(Y,P) function returns the same result as percentile(Y,P\*100.0). In other words, the fraction value in the second argument to percentile_cont() should be in the range of 0 to 1 instead of 0 to 100 as it is for percentile().
15. A separate percentile_disc(Y,P) function is like percentile_cont(Y,P) except that instead of returning the weighted average of the nearest two input values, it returns the next lower value. So the percentile_disc(Y,P) will always return a value that was one of the inputs.
16. All of median(), percentile(Y,P), percentile_cont(Y,P) and percentile_disc(Y,P) can be used as window functions.
---
# The RBU Extension
*Sección: Guides | Origen: https://www.sqlite.org/rbu.html*
# 1. The RBU Extension
The RBU extension is an add-on for SQLite designed for use with large SQLite database files on low-power devices at the edge of a network. RBU may be used for two separate tasks:
- **RBU Update operations**. An [RBU Update](rbu.md#rbu_updates) is a bulk update of a database file that may include many insert, update and delete operations on one or more tables.
- **RBU Vacuum operations**. An [RBU Vacuum](rbu.md#rbu_vacuum) optimizes and rebuilds an entire database file, with results similar to SQLite's native VACUUM command.
The acronym RBU stands for "Resumable Bulk Update".
Both of the RBU functions may be accomplished using SQLite's built-in SQL commands - RBU update via a series of [INSERT](lang_insert.md), [DELETE](lang_delete.md) and [UPDATE](lang_update.md) commands within a single transaction, and RBU vacuum by a single [VACUUM](lang_vacuum.md) command. The RBU module provides the following advantages over these simpler approaches:
1. **RBU may be more efficient**
The most efficient way to apply changes to a B-Tree (the data structure that SQLite uses to store each table and index on disk) is to make the changes in key order. But if an SQL table has one or more indexes, the key order for each index may be different from the main table and the other auxiliary indexes. As a result, when executing a series of [INSERT](lang_insert.md), [UPDATE](lang_update.md) and [DELETE](lang_delete.md) statements it is not generally possible to order the operations so that all b-trees are updated in key order. The RBU update process works around this by applying all changes to the main table in one pass, then applying changes to each index in separate passes, ensuring each B-Tree is updated optimally. For a large database file (one that does not fit in the OS disk cache) this procedure can result in two orders of magnitude faster updates.
An RBU Vacuum operation requires less temporary disk space and writes less data to disk than an SQLite VACUUM. An SQLite VACUUM requires roughly twice the size of the final database file in temporary disk space to run. The total amount of data written is around three times the size of the final database file. By contrast, an RBU Vacuum requires roughly the size of the final database file in temporary disk space and writes a total of twice that to disk.
On the other hand, an RBU Vacuum uses more CPU than a regular SQLite VACUUM - in one test as much as five times as much. For this reason, an RBU Vacuum is often significantly slower than an SQLite VACUUM under the same conditions.
2. **RBU runs in the background**
An ongoing RBU operation (either an update or a vacuum) does not interfere with read access to the database file.
3. **RBU runs incrementally**
RBU operations may be suspended and then later resumed, perhaps with intervening power outages and/or system resets. For an RBU update, the original database content remains visible to all database readers until the entire update has been applied - even if the update is suspended and then later resumed.
The RBU extension is not enabled by default. To enable it, compile the [amalgamation](amalgamation.md) with the [SQLITE_ENABLE_RBU](compile.md#enable_rbu) compile-time option.
# 2. RBU Updates
## 2.1. RBU Update Limitations
The following limitations apply to RBU updates:
- The changes must consist of [INSERT](lang_insert.md), [UPDATE](lang_update.md), and [DELETE](lang_delete.md) operations only. CREATE and DROP operations are not supported.
- [INSERT](lang_insert.md) statements may not use default values.
- [UPDATE](lang_update.md) and [DELETE](lang_delete.md) statements must identify the target rows by rowid or by non-NULL PRIMARY KEY values.
- [UPDATE](lang_update.md) statements may not modify PRIMARY KEY or rowid values.
- RBU updates cannot be applied to any tables that contain a column named "rbu_control".
- The RBU update will not fire any triggers.
- The RBU update will not detect or prevent foreign key or CHECK constraint violations.
- All RBU updates use the "OR ROLLBACK" constraint handling mechanism.
- The target database may not be in [WAL mode](wal.md).
- ~~The target database may not contain [indexes on expressions](expridx.md).~~ Indexes on expressions are supported beginning with SQLite 3.30.0 (2019-10-04).
- No other writes may occur on the target database while the RBU update is being applied. A read-lock is held on the target database to prevent this.
## 2.2. Preparing an RBU Update File
All changes to be applied by RBU are stored in a separate SQLite database called the "RBU database". The database that is to be modified is called the "target database".
For each table in the target database that will be modified by the update, a corresponding table is created within the RBU database. The RBU database table schema is not the same as that of the target database, but is derived from it as [described below](rbu.md#database_tables).
The RBU database table contains a single row for each target database row inserted, updated or deleted by the update. Populating the RBU database tables is described in [the following section](rbu.md#database_contents).
### 2.2.1. The RBU Database Schema
For each table in the target database, the RBU database should contain a table named "data\<*integer*\>\_\<*target-table-name*\>" where \<*target-table-name*\> is the name of the table in the target database and \<*integer*\> is any sequence of zero or more numeric characters (0-9). Tables within the RBU database are processed in order by name (from smallest to largest according to the BINARY collation sequence), so the order in which target tables are updated is influenced by the selection of the \<*integer*\> portion of the data\_% table name. While this can be useful when using RBU to update [certain types of virtual tables](rbu.md#fts4_tables), there is normally no reason to use anything other than an empty string in place of \<*integer*\>.
The data\_% table must have all the same columns as the target table, plus one additional column named "rbu_control". The data\_% table should have no PRIMARY KEY or UNIQUE constraints, but each column should have the same type as the corresponding column in the target database. The rbu_control column should have no type at all. For example, if the target database contains:
CREATE TABLE t1(a INTEGER PRIMARY KEY, b TEXT, c UNIQUE);\
Then the RBU database should contain:
CREATE TABLE data_t1(a INTEGER, b TEXT, c, rbu_control);\
The order of the columns in the data\_% table does not matter.
If the target database table is a virtual table or a table that has no PRIMARY KEY declaration, the data\_% table must also contain a column named "rbu_rowid". The rbu_rowid column is mapped to the tables [ROWID](lang_createtable.md#rowid). For example, if the target database contains either of the following:
CREATE VIRTUAL TABLE x1 USING fts3(a, b);\
CREATE TABLE x1(a, b);\
then the RBU database should contain:
CREATE TABLE data_x1(a, b, rbu_rowid, rbu_control);\
Virtual tables for which the "rowid" column does not function like a primary key value cannot be updated using RBU.
All non-hidden columns (i.e. all columns matched by "SELECT \*") of the target table must be present in the input table. For virtual tables, hidden columns are optional - they are updated by RBU if present in the input table, or not otherwise. For example, to write to an fts4 table with a hidden languageid column such as:
CREATE VIRTUAL TABLE ft1 USING fts4(a, b, languageid='langid');\
Either of the following input table schemas may be used:
CREATE TABLE data_ft1(a, b, langid, rbu_rowid, rbu_control);\
CREATE TABLE data_ft1(a, b, rbu_rowid, rbu_control);\
### 2.2.2. RBU Database Contents
For each row to INSERT into the target database as part of the RBU update, the corresponding data\_% table should contain a single record with the "rbu_control" column set to contain integer value 0. The other columns should be set to the values that make up the new record to insert.
The "rbu_control" column may also be set to integer value 2 for an INSERT. In this case, the new row silently replaces any existing row that has the same primary key values. This is equivalent to a DELETE followed by an INSERT with the same primary key values. It is not the same as an SQL REPLACE command, as in that case the new row may replace any conflicting rows (i.e. those that conflict due to UNIQUE constraints or indexes), not just those with conflicting primary keys.
If the target database table has an INTEGER PRIMARY KEY, it is not possible to insert a NULL value into the IPK column. Attempting to do so results in an SQLITE_MISMATCH error.
For each row to DELETE from the target database as part of the RBU update, the corresponding data\_% table should contain a single record with the "rbu_control" column set to contain integer value 1. The real primary key values of the row to delete should be stored in the corresponding columns of the data\_% table. The values stored in the other columns are not used.
For each row to UPDATE from the target database as part of the RBU update, the corresponding data\_% table should contain a single record with the "rbu_control" column set to contain a value of type text. The real primary key values identifying the row to update should be stored in the corresponding columns of the data\_% table row, as should the new values of all columns being updated. The text value in the "rbu_control" column must contain the same number of characters as there are columns in the target database table, and must consist entirely of 'x' and '.' characters (or in some special cases 'd' - see below). For each column that is being updated, the corresponding character is set to 'x'. For those that remain as they are, the corresponding character of the rbu_control value should be set to '.'. For example, given the tables above, the update statement:
UPDATE t1 SET c = 'usa' WHERE a = 4;\
is represented by the data_t1 row created by:
INSERT INTO data_t1(a, b, c, rbu_control) VALUES(4, NULL, 'usa', '..x');\
If RBU is used to update a large BLOB value within a target database, it may be more efficient to store a patch or delta that can be used to modify the existing BLOB instead of an entirely new value within the RBU database. RBU allows deltas to be specified in two ways:
- In the "fossil delta" format - the format used for blob deltas by the [Fossil source-code management system](http://fossil-scm.org), or
- In a custom format defined by the RBU application.
The fossil delta format may only be used to update BLOB values. Instead of storing the new BLOB within the data\_% table, the fossil delta is stored instead. And instead of specifying an 'x' as part of the rbu_control string for the column to be updated, an 'f' character is stored. When processing an 'f' update, RBU loads the original BLOB data from disk, applies the fossil delta to it and stores the results back into the database file. The RBU databases generated by [sqldiff --rbu](rbu.md#sqldiff) make use of fossil deltas wherever doing so would save space in the RBU database.
To use a custom delta format, the RBU application must register a user-defined SQL function named "rbu_delta" before beginning to process the update. rbu_delta() will be invoked with two arguments - the original value stored in the target table column and the delta value provided as part of the RBU update. It should return the result of applying the delta to the original value. To use the custom delta function, the character of the rbu_control value corresponding to the target column to update must be set to 'd' instead of 'x'. Then, instead of updating the target table with the value stored in the corresponding data\_% column, RBU invokes the user-defined SQL function "rbu_delta()" and the store in the target table column.
For example, this row:
INSERT INTO data_t1(a, b, c, rbu_control) VALUES(4, NULL, 'usa', '..d');\
causes RBU to update the target database table in a way similar to:
UPDATE t1 SET c = rbu_delta(c, 'usa') WHERE a = 4;\
If the target database table is a virtual table or a table with no PRIMARY KEY, the rbu_control value should not include a character corresponding to the rbu_rowid value. For example, this:
INSERT INTO data_ft1(a, b, rbu_rowid, rbu_control) \
VALUES(NULL, 'usa', 12, '.x');\
causes a result similar to:
UPDATE ft1 SET b = 'usa' WHERE rowid = 12;\
The data\_% tables themselves should have no PRIMARY KEY declarations. However, RBU is more efficient if reading the rows in from each data\_% table in "rowid" order is roughly the same as reading them sorted by the PRIMARY KEY of the corresponding target database table. In other words, rows should be sorted using the destination table PRIMARY KEY fields before they are inserted into the data\_% tables.
### 2.2.3. Using RBU with FTS3/4 Tables
Usually, an [FTS3 or FTS4](fts3.md) table is an example of a virtual table with a rowid that works like a PRIMARY KEY. So, for the following FTS4 tables:
CREATE VIRTUAL TABLE ft1 USING fts4(addr, text);\
CREATE VIRTUAL TABLE ft2 USING fts4; -- implicit "content" column\
The data\_% tables may be created as follows:
CREATE TABLE data_ft1 USING fts4(addr, text, rbu_rowid, rbu_control);\
CREATE TABLE data_ft2 USING fts4(content, rbu_rowid, rbu_control);\
And populated as if the target table were an ordinary SQLite table with no explicit PRIMARY KEY columns.
[Contentless FTS4 tables](fts3.md#_contentless_fts4_tables_) are handled similarly, except that any attempt to update or delete rows will cause an error when applying the update.
[External content FTS4 tables](fts3.md#_external_content_fts4_tables_) may also be updated using RBU. In this case the user is required to configure the RBU database so that the same set of UPDATE, DELETE and INSERT operations are applied to the FTS4 index as to the underlying content table. As for all updates of external content FTS4 tables, the user is also required to ensure that any UPDATE or DELETE operations are applied to the FTS4 index before they are applied to the underlying content table (refer to FTS4 documentation for a detailed explanation). In RBU, this is done by ensuring that the name of the data\_% table used to write to the FTS4 table sorts before the name of the data\_% table used to update the underlying content table using the [BINARY](datatype3.md#collation) collation sequence. In order to avoid duplicating data within the RBU database, an SQL view may be used in place of one of the data\_% tables. For example, for the target database schema:
CREATE TABLE ccc(addr, text);\
CREATE VIRTUAL TABLE ccc_fts USING fts4(addr, text, content=ccc);\
The following RBU database schema may be used:
CREATE TABLE data_ccc(addr, text, rbu_rowid, rbu_control);\
CREATE VIEW data0_ccc_fts AS SELECT \* FROM data_ccc;\
The data_ccc table may then be populated as normal with the updates intended for target database table ccc. The same updates will be read by RBU from the data0_ccc_fts view and applied to FTS table ccc_fts. Because "data0_ccc_fts" is smaller than "data_ccc", the FTS table will be updated first, as required.
Cases in which the underlying content table has an explicit INTEGER PRIMARY KEY column are slightly more difficult, as the text values stored in the rbu_control column are slightly different for the FTS index and its underlying content table. For the underlying content table, a character must be included in any rbu_control text values for the explicit IPK, but for the FTS table itself, which has an implicit rowid, it should not. This is inconvenient, but can be solved using a more complicated view, as follows:
-- Target database schema\
CREATE TABLE ddd(i INTEGER PRIMARY KEY, k TEXT);\
CREATE VIRTUAL TABLE ddd_fts USING fts4(k, content=ddd);\
\
-- RBU database schema\
CREATE TABLE data_ccc(i, k, rbu_control);\
CREATE VIEW data0_ccc_fts AS SELECT i AS rbu_rowid, k, CASE \
WHEN rbu_control IN (0,1) THEN rbu_control ELSE substr(rbu_control, 2) END\
FROM data_ccc;\
The substr() function in the SQL view above returns the text of the rbu_control argument with the first character (the one corresponding to column "i", which is not required by the FTS table) removed.
### 2.2.4. Automatically Generating RBU Updates with sqldiff
As of SQLite [version 3.9.0](releaselog/3_9_0.md) (2015-10-14), the [sqldiff](sqldiff.md) utility is able to generate RBU databases representing the difference between two databases with identical schemas. For example, the following command:
sqldiff --rbu t1.db t2.db\
Outputs an SQL script to create an RBU database which, if used to update database t1.db, patches it so that its contents are identical to that of database t2.db.
By default, sqldiff attempts to process all non-virtual tables within the two databases provided to it. If any table appears in one database but not the other, or if any table has a slightly different schema in one database it is an error. The "--table" option may be useful if this causes a problem
Virtual tables are ignored by default by sqldiff. However, it is possible to explicitly create an RBU data\_% table for a virtual table that features a rowid that functions like a primary key using a command such as:
sqldiff --rbu --table \<*virtual-table-name*\> t1.db t2.db\
Unfortunately, even though virtual tables are ignored by default, any [underlying database tables](fts3.md#*shadowtab) that they create in order to store data within the database are not, and [sqldiff](sqldiff.md) will add these to any RBU database. For this reason, users attempting to use sqldiff to create RBU updates to apply to target databases with one or more virtual tables will likely have to run sqldiff using the --table option separately for each table to update in the target database.
## 2.3. RBU Update C/C++ Programming
The RBU extension interface allows an application to apply an RBU update stored in an RBU database to an existing target database. The procedure is as follows:
1. Open an RBU handle using the sqlite3rbu_open(T,A,S) function.
The T argument is the name of the target database file. The A argument is the name of the RBU database file. The S argument is the name of a "state database" used to store state information needed to resume the update after an interruption. The S argument can be NULL in which case the state information is stored in the RBU database in various tables whose names all begin with "rbu\_".
The sqlite3rbu_open(T,A,S) function returns a pointer to an "sqlite3rbu" object, which is then passed into the subsequent interfaces.
2. Register any required virtual table modules with the database handle returned by sqlite3rbu_db(X) (where argument X is the sqlite3rbu pointer returned from sqlite3rbu_open()). Also, if required, register the rbu_delta() SQL function using [sqlite3_create_function_v2()](c3ref/create_function.md).
3. Invoke the sqlite3rbu_step(X) function one or more times on the sqlite3rbu object pointer X. Each call to sqlite3rbu_step() performs a single b-tree operation, so thousands of calls may be required to apply a complete update. The sqlite3rbu_step() interface will return SQLITE_DONE when the update has been completely applied.
4. Call sqlite3rbu_close(X) to destroy the sqlite3rbu object pointer. If sqlite3rbu_step(X) has been called enough times to completely apply the update to the target database, then the RBU database is marked as fully applied. Otherwise, the state of the RBU update application is saved in the state database (or in the RBU database if the name of the state database file in sqlite3rbu_open() is NULL) for later resumption of the update.
If an update is only partially applied to the target database by the time sqlite3rbu_close() is called, state information is saved within the state database if it exists, or otherwise in the RBU database. This allows subsequent processes to automatically resume the RBU update from where it left off. If state information is stored in the RBU database, it can be removed by dropping all tables whose names begin with "rbu\_".
For more details, refer to the comments in [header file sqlite3rbu.h](http://sqlite.org/src/doc/trunk/ext/rbu/sqlite3rbu.h).
# 3. RBU Vacuum
## 3.1. RBU Vacuum Limitations
When compared with SQLite's built-in VACUUM command, RBU Vacuum has the following limitations:
- It may not be used on a database that contains [indexes on expressions](expridx.md).
- The database being vacuumed may not be in [WAL mode](wal.md).
## 3.2. RBU Vacuum C/C++ Programming
This section provides an overview of and example code demonstrating the integration of RBU Vacuum into an application program. For full details, refer to the comments in [header file sqlite3rbu.h](http://sqlite.org/src/doc/trunk/ext/rbu/sqlite3rbu.h).
RBU Vacuum applications all implement some variation of the following procedure:
1. An RBU handle is created by calling sqlite3rbu_vacuum(T, S).
Argument T is the name of the database file to vacuum. Argument S is the name of a database in which the RBU module will save its state if the vacuum operation is suspended.
If state database S does not exist when sqlite3rbu_vacuum() is invoked, it is automatically created and populated with the single table used to store the state of an RBU vacuum - "rbu_state". If an ongoing RBU vacuum is suspended, this table is populated with state data. The next time sqlite3rbu_vacuum() is called with the same S parameter, it detects this data and attempts to resume the suspended vacuum operation. When an RBU vacuum operation is completed or encounters an error, RBU automatically deletes the contents of the rbu_state table. In this case, the next call to sqlite3rbu_vacuum() starts an entirely new vacuum operation from scratch.
It is a good idea to establish a convention for determining the RBU vacuum state database name based on the target database name. The example code below uses "\| Opcode Name | >Description | >
|---|---|
| Abortable | >Verify that an Abort can happen. Assert if an Abort at this point might cause database corruption. This opcode only appears in debugging builds.
> An Abort is safe if either there have been no writes, or if there is an active statement journal. |
>
| Add | >Add the value in register P1 to the value in register P2 and store the result in register P3. If either input is NULL, the result is NULL. | >
| AddImm | >Add the constant P2 to the value in register P1. The result is always an integer.
> To force any register to be an integer, just add 0. |
>
| Affinity | >Apply affinities to a range of P2 registers starting with P1.
> P4 is a string that is P2 characters long. The N-th character of the string indicates the column affinity that should be used for the N-th memory cell in the range. |
>
| AggFinal | >P1 is the memory location that is the accumulator for an aggregate or window function. Execute the finalizer function for an aggregate and store the result in P1.
> P2 is the number of arguments that the step function takes and P4 is a pointer to the FuncDef for this function. The P2 argument is not used by this opcode. It is only there to disambiguate functions that can take varying numbers of arguments. The P4 argument is only needed for the case where the step function was not previously called. |
>
| AggInverse | >Execute the xInverse function for an aggregate. The function has P5 arguments. P4 is a pointer to the FuncDef structure that specifies the function. Register P3 is the accumulator.
> The P5 arguments are taken from register P2 and its successors. |
>
| AggStep | >Execute the xStep function for an aggregate. The function has P5 arguments. P4 is a pointer to the FuncDef structure that specifies the function. Register P3 is the accumulator.
> The P5 arguments are taken from register P2 and its successors. |
>
| AggStep1 | >Execute the xStep (if P1==0) or xInverse (if P1!=0) function for an aggregate. The function has P5 arguments. P4 is a pointer to the FuncDef structure that specifies the function. Register P3 is the accumulator.
> The P5 arguments are taken from register P2 and its successors. >This opcode is initially coded as OP_AggStep0. On first evaluation, the FuncDef stored in P4 is converted into an sqlite3_context and the opcode is changed. In this way, the initialization of the sqlite3_context only happens once, instead of on each call to the step function. |
>
| AggValue | >Invoke the xValue() function and store the result in register P3.
> P2 is the number of arguments that the step function takes and P4 is a pointer to the FuncDef for this function. The P2 argument is not used by this opcode. It is only there to disambiguate functions that can take varying numbers of arguments. The P4 argument is only needed for the case where the step function was not previously called. |
>
| And | >Take the logical AND of the values in registers P1 and P2 and write the result into register P3.
> If either P1 or P2 is 0 (false) then the result is 0 even if the other input is NULL. A NULL and true or two NULLs give a NULL output. |
>
| AutoCommit | >Set the database auto-commit flag to P1 (1 or 0). If P2 is true, roll back any currently active btree transactions. If there are any active VMs (apart from this one), then a ROLLBACK fails. A COMMIT fails if there are active writing VMs or active VMs that use shared cache.
> This instruction causes the VM to halt. |
>
| BeginSubrtn | >Mark the beginning of a subroutine that can be entered in-line or that can be called using Gosub. The subroutine should be terminated by an Return instruction that has a P1 operand that is the same as the P2 operand to this opcode and that has P3 set to 1. If the subroutine is entered in-line, then the Return will simply fall through. But if the subroutine is entered using Gosub, then the Return will jump back to the first instruction after the Gosub.
> This routine works by loading a NULL into the P2 register. When the return address register contains a NULL, the Return instruction is a no-op that simply falls through to the next instruction (assuming that the Return opcode has a P3 value of 1). Thus if the subroutine is entered in-line, then the Return will cause in-line execution to continue. But if the subroutine is entered via Gosub, then the Return will cause a return to the address following the Gosub. >This opcode is identical to Null. It has a different name only to make the byte code easier to read and verify. |
>
| BitAnd | >Take the bit-wise AND of the values in register P1 and P2 and store the result in register P3. If either input is NULL, the result is NULL. | >
| BitNot | >Interpret the content of register P1 as an integer. Store the ones-complement of the P1 value into register P2. If P1 holds a NULL then store a NULL in P2. | >
| BitOr | >Take the bit-wise OR of the values in register P1 and P2 and store the result in register P3. If either input is NULL, the result is NULL. | >
| Blob | >P4 points to a blob of data P1 bytes long. Store this blob in register P2. If P4 is a NULL pointer, then construct a zero-filled blob that is P1 bytes long in P2. | >
| Cast | >Force the value in register P1 to be the type defined by P2.
>
A NULL value is not changed by this routine. It remains NULL. |
>
| Checkpoint | >Checkpoint database P1. This is a no-op if P1 is not currently in WAL mode. Parameter P2 is one of SQLITE_CHECKPOINT_PASSIVE, FULL, RESTART, or TRUNCATE. Write 1 or 0 into mem[P3] if the checkpoint returns SQLITE_BUSY or not, respectively. Write the number of pages in the WAL after the checkpoint into mem[P3+1] and the number of pages in the WAL that have been checkpointed after the checkpoint completes into mem[P3+2]. However on an error, mem[P3+1] and mem[P3+2] are initialized to -1. | >
| Clear | >Delete all contents of the database table or index whose root page in the database file is given by P1. But, unlike Destroy, do not remove the table or index from the database file.
> The table being cleared is in the main database file if P2==0. If P2==1 then the table to be cleared is in the auxiliary database file that is used to store tables create using CREATE TEMPORARY TABLE. >If the P3 value is non-zero, then the row change count is incremented by the number of rows in the table being cleared. If P3 is greater than zero, then the value stored in register P3 is also incremented by the number of rows in the table being cleared. >See also: Destroy |
>
| Close | >Close a cursor previously opened as P1. If P1 is not currently open, this instruction is a no-op. | >
| ClrSubtype | >Clear the subtype from register P1. | >
| CollSeq | >P4 is a pointer to a CollSeq object. If the next call to a user function or aggregate calls sqlite3GetFuncCollSeq(), this collation sequence will be returned. This is used by the built-in min(), max() and nullif() functions.
> If P1 is not zero, then it is a register that a subsequent min() or max() aggregate will set to 1 if the current row is not the minimum or maximum. The P1 register is initialized to 0 by this instruction. >The interface used by the implementation of the aforementioned functions to retrieve the collation sequence set by this opcode is not available publicly. Only built-in functions have access to this feature. |
>
| Column | >Interpret the data that cursor P1 points to as a structure built using the MakeRecord instruction. (See the MakeRecord opcode for additional information about the format of the data.) Extract the P2-th column from this record. If there are less than (P2+1) values in the record, extract a NULL.
> The value extracted is stored in register P3. >If the record contains fewer than P2 fields, then extract a NULL. Or, if the P4 argument is a P4_MEM use the value of the P4 argument as the result. >If the OPFLAG_LENGTHARG bit is set in P5 then the result is guaranteed to only be used by the length() function or the equivalent. The content of large blobs is not loaded, thus saving CPU cycles. If the OPFLAG_TYPEOFARG bit is set then the result will only be used by the typeof() function or the IS NULL or IS NOT NULL operators or the equivalent. In this case, all content loading can be omitted. |
>
| ColumnsUsed | >This opcode (which only exists if SQLite was compiled with SQLITE_ENABLE_COLUMN_USED_MASK) identifies which columns of the table or index for cursor P1 are used. P4 is a 64-bit integer (P4_INT64) in which the first 63 bits are one for each of the first 63 columns of the table or index that are actually used by the cursor. The high-order bit is set if any column after the 64th is used. | >
| Compare | >Compare two vectors of registers in reg(P1)..reg(P1+P3-1) (call this vector "A") and in reg(P2)..reg(P2+P3-1) ("B"). Save the result of the comparison for use by the next Jump instruct.
> If P5 has the OPFLAG_PERMUTE bit set, then the order of comparison is determined by the most recent Permutation operator. If the OPFLAG_PERMUTE bit is clear, then register are compared in sequential order. >P4 is a KeyInfo structure that defines collating sequences and sort orders for the comparison. The permutation applies to registers only. The KeyInfo elements are used sequentially. >The comparison is a sort comparison, so NULLs compare equal, NULLs are less than numbers, numbers are less than strings, and strings are less than blobs. >This opcode must be immediately followed by an Jump opcode. |
>
| Concat | >Add the text in register P1 onto the end of the text in register P2 and store the result in register P3. If either the P1 or P2 text are NULL then store NULL in P3.
> P3 = P2 || P1 >It is illegal for P1 and P3 to be the same register. Sometimes, if P3 is the same register as P2, the implementation is able to avoid a memcpy(). |
>
| Copy | >Make a copy of registers P1..P1+P3 into registers P2..P2+P3.
> If the 0x0002 bit of P5 is set then also clear the MEM_Subtype flag in the destination. The 0x0001 bit of P5 indicates that this Copy opcode cannot be merged. The 0x0001 bit is used by the query planner and does not come into play during query execution. >This instruction makes a deep copy of the value. A duplicate is made of any string or blob constant. See also SCopy. |
>
| Count | >Store the number of entries (an integer value) in the table or index opened by cursor P1 in register P2.
> If P3==0, then an exact count is obtained, which involves visiting every btree page of the table. But if P3 is non-zero, an estimate is returned based on the current cursor position. |
>
| CreateBtree | >Allocate a new b-tree in the main database file if P1==0 or in the TEMP database file if P1==1 or in an attached database if P1>1. The P3 argument must be 1 (BTREE_INTKEY) for a rowid table it must be 2 (BTREE_BLOBKEY) for an index or WITHOUT ROWID table. The root page number of the new b-tree is stored in register P2. | >
| CursorHint | >Provide a hint to cursor P1 that it only needs to return rows that satisfy the Expr in P4. TK_REGISTER terms in the P4 expression refer to values currently held in registers. TK_COLUMN terms in the P4 expression refer to columns in the b-tree to which cursor P1 is pointing. | >
| CursorLock | >Lock the btree to which cursor P1 is pointing so that the btree cannot be written by an other cursor. | >
| CursorUnlock | >Unlock the btree to which cursor P1 is pointing so that it can be written by other cursors. | >
| DecrJumpZero | >Register P1 must hold an integer. Decrement the value in P1 and jump to P2 if the new value is exactly zero. | >
| DeferredSeek | >P1 is an open index cursor and P3 is a cursor on the corresponding table. This opcode does a deferred seek of the P3 table cursor to the row that corresponds to the current row of P1.
> This is a deferred seek. Nothing actually happens until the cursor is used to read a record. That way, if no reads occur, no unnecessary I/O happens. >P4 may be an array of integers (type P4_INTARRAY) containing one entry for each column in the P3 table. If array entry a(i) is non-zero, then reading column a(i)-1 from cursor P3 is equivalent to performing the deferred seek and then reading column i from P1. This information is stored in P3 and used to redirect reads against P3 over to P1, thus possibly avoiding the need to seek and read cursor P3. |
>
| Delete | >Delete the record at which the P1 cursor is currently pointing.
> If the OPFLAG_SAVEPOSITION bit of the P5 parameter is set, then the cursor will be left pointing at either the next or the previous record in the table. If it is left pointing at the next record, then the next Next instruction will be a no-op. As a result, in this case it is ok to delete a record from within a Next loop. If OPFLAG_SAVEPOSITION bit of P5 is clear, then the cursor will be left in an undefined state. >If the OPFLAG_AUXDELETE bit is set on P5, that indicates that this delete is one of several associated with deleting a table row and all its associated index entries. Exactly one of those deletes is the "primary" delete. The others are all on OPFLAG_FORDELETE cursors or else are marked with the AUXDELETE flag. >If the OPFLAG_NCHANGE (0x01) flag of P2 (NB: P2 not P5) is set, then the row change count is incremented (otherwise not). >If the OPFLAG_ISNOOP (0x40) flag of P2 (not P5!) is set, then the pre-update-hook for deletes is run, but the btree is otherwise unchanged. This happens when the Delete is to be shortly followed by an Insert with the same key, causing the btree entry to be overwritten. >P1 must not be pseudo-table. It has to be a real table with multiple rows. >If P4 is not NULL then it points to a Table object. In this case either the update or pre-update hook, or both, may be invoked. The P1 cursor must have been positioned using NotFound prior to invoking this opcode in this case. Specifically, if one is configured, the pre-update hook is invoked if P4 is not NULL. The update-hook is invoked if one is configured, P4 is not NULL, and the OPFLAG_NCHANGE flag is set in P2. >If the OPFLAG_ISUPDATE flag is set in P2, then P3 contains the address of the memory cell that contains the value that the rowid of the row will be set to by the update. |
>
| Destroy | >Delete an entire database table or index whose root page in the database file is given by P1.
> The table being destroyed is in the main database file if P3==0. If P3==1 then the table to be destroyed is in the auxiliary database file that is used to store tables create using CREATE TEMPORARY TABLE. >If AUTOVACUUM is enabled then it is possible that another root page might be moved into the newly deleted root page in order to keep all root pages contiguous at the beginning of the database. The former value of the root page that moved - its value before the move occurred - is stored in register P2. If no page movement was required (because the table being dropped was already the last one in the database) then a zero is stored in register P2. If AUTOVACUUM is disabled then a zero is stored in register P2. >This opcode throws an error if there are any active reader VMs when it is invoked. This is done to avoid the difficulty associated with updating existing cursors when a root page is moved in an AUTOVACUUM database. This error is thrown even if the database is not an AUTOVACUUM db in order to avoid introducing an incompatibility between autovacuum and non-autovacuum modes. >See also: Clear |
>
| Divide | >Divide the value in register P1 by the value in register P2 and store the result in register P3 (P3=P2/P1). If the value in register P1 is zero, then the result is NULL. If either input is NULL, the result is NULL. | >
| DropIndex | >Remove the internal (in-memory) data structures that describe the index named P4 in database P1. This is called after an index is dropped from disk (using the Destroy opcode) in order to keep the internal representation of the schema consistent with what is on disk. | >
| DropTable | >Remove the internal (in-memory) data structures that describe the table named P4 in database P1. This is called after a table is dropped from disk (using the Destroy opcode) in order to keep the internal representation of the schema consistent with what is on disk. | >
| DropTrigger | >Remove the internal (in-memory) data structures that describe the trigger named P4 in database P1. This is called after a trigger is dropped from disk (using the Destroy opcode) in order to keep the internal representation of the schema consistent with what is on disk. | >
| ElseEq | >This opcode must follow an Lt or Gt comparison operator. There can be zero or more OP_ReleaseReg opcodes intervening, but no other opcodes are allowed to occur between this instruction and the previous Lt or Gt.
> If the result of an Eq comparison on the same two operands as the prior Lt or Gt would have been true, then jump to P2. If the result of an Eq comparison on the two previous operands would have been false or NULL, then fall through. |
>
| EndCoroutine | >The instruction at the address in register P1 is a Yield. Jump to the P2 parameter of that Yield. After the jump, the value register P1 is left with a value such that subsequent OP_Yields go back to the this same EndCoroutine instruction.
> See also: InitCoroutine |
>
| Eq | >Compare the values in register P1 and P3. If reg(P3)==reg(P1) then jump to address P2.
> The SQLITE_AFF_MASK portion of P5 must be an affinity character - SQLITE_AFF_TEXT, SQLITE_AFF_INTEGER, and so forth. An attempt is made to coerce both inputs according to this affinity before the comparison is made. If the SQLITE_AFF_MASK is 0x00, then numeric affinity is used. Note that the affinity conversions are stored back into the input registers P1 and P3. So this opcode can cause persistent changes to registers P1 and P3. >Once any conversions have taken place, and neither value is NULL, the values are compared. If both values are blobs then memcmp() is used to determine the results of the comparison. If both values are text, then the appropriate collating function specified in P4 is used to do the comparison. If P4 is not specified then memcmp() is used to compare text string. If both values are numeric, then a numeric comparison is used. If the two values are of different types, then numbers are considered less than strings and strings are considered less than blobs. >If SQLITE_NULLEQ is set in P5 then the result of comparison is always either true or false and is never NULL. If both operands are NULL then the result of comparison is true. If either operand is NULL then the result is false. If neither operand is NULL the result is the same as it would be if the SQLITE_NULLEQ flag were omitted from P5. >This opcode saves the result of comparison for use by the new Jump opcode. |
>
| Expire | >Cause precompiled statements to expire. When an expired statement is executed using sqlite3_step() it will either automatically reprepare itself (if it was originally created using sqlite3_prepare_v2()) or it will fail with SQLITE_SCHEMA.
> If P1 is 0, then all SQL statements become expired. If P1 is non-zero, then only the currently executing statement is expired. >If P2 is 0, then SQL statements are expired immediately. If P2 is 1, then running SQL statements are allowed to continue to run to completion. The P2==1 case occurs when a CREATE INDEX or similar schema change happens that might help the statement run faster but which does not affect the correctness of operation. |
>
| Explain | >This is the same as Noop during normal query execution. The purpose of this opcode is to hold information about the query plan for the purpose of EXPLAIN QUERY PLAN output.
> The P4 value is human-readable text that describes the query plan element. Something like "SCAN t1" or "SEARCH t2 USING INDEX t2x1". >The P1 value is the ID of the current element and P2 is the parent element for the case of nested query plan elements. If P2 is zero then this element is a top-level element. >For loop elements, P3 is the estimated code of each invocation of this element. >As with all opcodes, the meanings of the parameters for Explain are subject to change from one release to the next. Applications should not attempt to interpret or use any of the information contained in the Explain opcode. The information provided by this opcode is intended for testing and debugging use only. |
>
| Filter | >Compute a hash on the key contained in the P4 registers starting with r[P3]. Check to see if that hash is found in the bloom filter hosted by register P1. If it is not present then maybe jump to P2. Otherwise fall through.
> False negatives are harmless. It is always safe to fall through, even if the value is in the bloom filter. A false negative causes more CPU cycles to be used, but it should still yield the correct answer. However, an incorrect answer may well arise from a false positive - if the jump is taken when it should fall through. |
>
| FilterAdd | >Compute a hash on the P4 registers starting with r[P3] and add that hash to the bloom filter contained in r[P1]. | >
| FinishSeek | >If cursor P1 was previously moved via DeferredSeek, complete that seek operation now, without further delay. If the cursor seek has already occurred, this instruction is a no-op. | >
| FkCheck | >Halt with an SQLITE_CONSTRAINT error if there are any unresolved foreign key constraint violations. If there are no foreign key constraint violations, this is a no-op.
> FK constraint violations are also checked when the prepared statement exits. This opcode is used to raise foreign key constraint errors prior to returning results such as a row change count or the result of a RETURNING clause. |
>
| FkCounter | >Increment a "constraint counter" by P2 (P2 may be negative or positive). If P1 is non-zero, the database constraint counter is incremented (deferred foreign key constraints). Otherwise, if P1 is zero, the statement counter is incremented (immediate foreign key constraints). | >
| FkIfZero | >This opcode tests if a foreign key constraint-counter is currently zero. If so, jump to instruction P2. Otherwise, fall through to the next instruction.
> If P1 is non-zero, then the jump is taken if the database constraint-counter is zero (the one that counts deferred constraint violations). If P1 is zero, the jump is taken if the statement constraint-counter is zero (immediate foreign key constraint violations). |
>
| Found | >If P4==0 then register P3 holds a blob constructed by MakeRecord. If P4>0 then register P3 is the first of P4 registers that form an unpacked record.
> Cursor P1 is on an index btree. If the record identified by P3 and P4 is a prefix of any entry in P1 then a jump is made to P2 and P1 is left pointing at the matching entry. >This operation leaves the cursor in a state where it can be advanced in the forward direction. The Next instruction will work, but not the Prev instruction. >See also: NotFound, NoConflict, NotExists. SeekGe |
>
| Function | >Invoke a user function (P4 is a pointer to an sqlite3_context object that contains a pointer to the function to be run) with arguments taken from register P2 and successors. The number of arguments is in the sqlite3_context object that P4 points to. The result of the function is stored in register P3. Register P3 must not be one of the function inputs.
> P1 is a 32-bit bitmask indicating whether or not each argument to the function was determined to be constant at compile time. If the first argument was constant then bit 0 of P1 is set. This is used to determine whether meta data associated with a user function argument using the sqlite3_set_auxdata() API may be safely retained until the next invocation of this opcode. > |
>
| Ge | >This works just like the Lt opcode except that the jump is taken if the content of register P3 is greater than or equal to the content of register P1. See the Lt opcode for additional information. | >
| GetSubtype | >Extract the subtype value from register P1 and write that subtype into register P2. If P1 has no subtype, then P1 gets a NULL. | >
| Gosub | >Write the current address onto register P1 and then jump to address P2. | >
| Goto | >An unconditional jump to address P2. The next instruction executed will be the one at index P2 from the beginning of the program.
> The P1 parameter is not actually used by this opcode. However, it is sometimes set to 1 instead of 0 as a hint to the command-line shell that this Goto is the bottom of a loop and that the lines from P2 down to the current line should be indented for EXPLAIN output. |
>
| Gt | >This works just like the Lt opcode except that the jump is taken if the content of register P3 is greater than the content of register P1. See the Lt opcode for additional information. | >
| Halt | >Exit immediately. All open cursors, etc are closed automatically.
> P1 is the result code returned by sqlite3_exec(), sqlite3_reset(), or sqlite3_finalize(). For a normal halt, this should be SQLITE_OK (0). For errors, it can be some other value. If P1!=0 then P2 will determine whether or not to rollback the current transaction. Do not rollback if P2==OE_Fail. Do the rollback if P2==OE_Rollback. If P2==OE_Abort, then back out all changes that have occurred during this execution of the VDBE, but do not rollback the transaction. >If P3 is not zero and P4 is NULL, then P3 is a register that holds the text of an error message. >If P3 is zero and P4 is not null then the error message string is held in P4. >P5 is a value between 1 and 4, inclusive, then the P4 error message string is modified as follows: >1: NOT NULL constraint failed: P4 2: UNIQUE constraint failed: P4 3: CHECK constraint failed: P4 4: FOREIGN KEY constraint failed: P4 >If P3 is zero and P5 is not zero and P4 is NULL, then everything after the ":" is omitted. >There is an implied "Halt 0 0 0" instruction inserted at the very end of every program. So a jump past the last instruction of the program is the same as executing Halt. |
>
| HaltIfNull | >Check the value in register P3. If it is NULL then Halt using parameter P1, P2, and P4 as if this were a Halt instruction. If the value in register P3 is not NULL, then this routine is a no-op. The P5 parameter should be 1. | >
| IdxDelete | >The content of P3 registers starting at register P2 form an unpacked index key. This opcode removes that entry from the index opened by cursor P1.
> P4 is a pointer to an Index structure. >Raise an SQLITE_CORRUPT_INDEX error if no matching index entry is found and not in writable_schema mode. |
>
| IdxGE | >The P4 register values beginning with P3 form an unpacked index key that omits the PRIMARY KEY. Compare this key value against the index that P1 is currently pointing to, ignoring the PRIMARY KEY or ROWID fields at the end.
> If the P1 index entry is greater than or equal to the key value then jump to P2. Otherwise fall through to the next instruction. |
>
| IdxGT | >The P4 register values beginning with P3 form an unpacked index key that omits the PRIMARY KEY. Compare this key value against the index that P1 is currently pointing to, ignoring the PRIMARY KEY or ROWID fields at the end.
> If the P1 index entry is greater than the key value then jump to P2. Otherwise fall through to the next instruction. |
>
| IdxInsert | >Register P2 holds an SQL index key made using the MakeRecord instructions. This opcode writes that key into the index P1. Data for the entry is nil.
> If P4 is not zero, then it is the number of values in the unpacked key of reg(P2). In that case, P3 is the index of the first register for the unpacked key. The availability of the unpacked key can sometimes be an optimization. >If P5 has the OPFLAG_APPEND bit set, that is a hint to the b-tree layer that this insert is likely to be an append. >If P5 has the OPFLAG_NCHANGE bit set, then the change counter is incremented by this instruction. If the OPFLAG_NCHANGE bit is clear, then the change counter is unchanged. >If the OPFLAG_USESEEKRESULT flag of P5 is set, the implementation might run faster by avoiding an unnecessary seek on cursor P1. However, the OPFLAG_USESEEKRESULT flag must only be set if there have been no prior seeks on the cursor or if the most recent seek used a key equivalent to P2. >This instruction only works for indices. The equivalent instruction for tables is Insert. |
>
| IdxLE | >The P4 register values beginning with P3 form an unpacked index key that omits the PRIMARY KEY or ROWID. Compare this key value against the index that P1 is currently pointing to, ignoring the PRIMARY KEY or ROWID on the P1 index.
> If the P1 index entry is less than or equal to the key value then jump to P2. Otherwise fall through to the next instruction. |
>
| IdxLT | >The P4 register values beginning with P3 form an unpacked index key that omits the PRIMARY KEY or ROWID. Compare this key value against the index that P1 is currently pointing to, ignoring the PRIMARY KEY or ROWID on the P1 index.
> If the P1 index entry is less than the key value then jump to P2. Otherwise fall through to the next instruction. |
>
| IdxRowid | >Write into register P2 an integer which is the last entry in the record at the end of the index key pointed to by cursor P1. This integer should be the rowid of the table entry to which this index entry points.
> See also: Rowid, MakeRecord. |
>
| If | >Jump to P2 if the value in register P1 is true. The value is considered true if it is numeric and non-zero. If the value in P1 is NULL then take the jump if and only if P3 is non-zero. | >
| IfEmpty | >Check to see if the b-tree table that cursor P1 references is empty and jump to P2 if it is. | >
| IFindKey | >This instruction always follows an Found with the same P1, P2 and P3 values as this instruction and a non-zero P4 value. The P4 value to this opcode is of type P4_INDEX and contains a pointer to the Index object of for the index being searched.
> This opcode uses sqlite3VdbeFindIndexKey() to search around the current cursor location for an index key that exactly matches all fields that are not indexed expressions or references to VIRTUAL generated columns, and either exactly match or are real numbers that are within 2 ULPs of each other if the don't match. >To put it another way, this opcode looks for nearby index entries that are very close to the search key, but which might have small differences in floating-point values that come via an expression. >If no nearby alternative entry is found in cursor P1, then jump to P2. But if a close match is found, fall through. >This opcode is used by PRAGMA integrity_check to help distinguish between truely corrupt indexes and expression indexes that are holding floating-point values that are off by one or two ULPs. |
>
| IfNoHope | >Register P3 is the first of P4 registers that form an unpacked record. Cursor P1 is an index btree. P2 is a jump destination. In other words, the operands to this opcode are the same as the operands to NotFound and IdxGT.
> This opcode is an optimization attempt only. If this opcode always falls through, the correct answer is still obtained, but extra work is performed. >A value of N in the seekHit flag of cursor P1 means that there exists a key P3:N that will match some record in the index. We want to know if it is possible for a record P3:P4 to match some record in the index. If it is not possible, we can skip some work. So if seekHit is less than P4, attempt to find out if a match is possible by running NotFound. >This opcode is used in IN clause processing for a multi-column key. If an IN clause is attached to an element of the key other than the left-most element, and if there are no matches on the most recent seek over the whole key, then it might be that one of the key element to the left is prohibiting a match, and hence there is "no hope" of any match regardless of how many IN clause elements are checked. In such a case, we abandon the IN clause search early, using this opcode. The opcode name comes from the fact that the jump is taken if there is "no hope" of achieving a match. > |
>
| IfNot | >Jump to P2 if the value in register P1 is False. The value is considered false if it has a numeric value of zero. If the value in P1 is NULL then take the jump if and only if P3 is non-zero. | >
| IfNotOpen | >If cursor P1 is not open or if P1 is set to a NULL row using the NullRow opcode, then jump to instruction P2. Otherwise, fall through. | >
| IfNotZero | >Register P1 must contain an integer. If the content of register P1 is initially greater than zero, then decrement the value in register P1. If it is non-zero (negative or positive) and then also jump to P2. If register P1 is initially zero, leave it unchanged and fall through. | >
| IfNullRow | >Check the cursor P1 to see if it is currently pointing at a NULL row. If it is, then set register P3 to NULL and jump immediately to P2. If P1 is not on a NULL row, then fall through without making any changes.
> If P1 is not an open cursor, then this opcode is a no-op. |
>
| IfPos | >Register P1 must contain an integer. If the value of register P1 is 1 or greater, subtract P3 from the value in P1 and jump to P2.
> If the initial value of register P1 is less than 1, then the value is unchanged and control passes through to the next instruction. |
>
| IfSizeBetween | >Let N be the approximate number of rows in the table or index with cursor P1 and let X be 10*log2(N) if N is positive or -1 if N is zero.
> Jump to P2 if X is in between P3 and P4, inclusive. |
>
| IncrVacuum | >Perform a single step of the incremental vacuum procedure on the P1 database. If the vacuum has finished, jump to instruction P2. Otherwise, fall through to the next instruction. | >
| Init | >Programs contain a single instance of this opcode as the very first opcode.
> If tracing is enabled (by the sqlite3_trace()) interface, then the UTF-8 string contained in P4 is emitted on the trace callback. Or if P4 is blank, use the string returned by sqlite3_sql(). >If P2 is not zero, jump to instruction P2. >Increment the value of P1 so that Once opcodes will jump the first time they are evaluated for this run. >If P3 is not zero, then it is an address to jump to if an SQLITE_CORRUPT error is encountered. |
>
| InitCoroutine | >Set up register P1 so that it will Yield to the coroutine located at address P3.
> If P2!=0 then the coroutine implementation immediately follows this opcode. So jump over the coroutine implementation to address P2. >See also: EndCoroutine |
>
| Insert | >Write an entry into the table of cursor P1. A new entry is created if it doesn't already exist or the data for an existing entry is overwritten. The data is the value MEM_Blob stored in register number P2. The key is stored in register P3. The key must be a MEM_Int.
> If the OPFLAG_NCHANGE flag of P5 is set, then the row change count is incremented (otherwise not). If the OPFLAG_LASTROWID flag of P5 is set, then rowid is stored for subsequent return by the sqlite3_last_insert_rowid() function (otherwise it is unmodified). >If the OPFLAG_USESEEKRESULT flag of P5 is set, the implementation might run faster by avoiding an unnecessary seek on cursor P1. However, the OPFLAG_USESEEKRESULT flag must only be set if there have been no prior seeks on the cursor or if the most recent seek used a key equal to P3. >If the OPFLAG_ISUPDATE flag is set, then this opcode is part of an UPDATE operation. Otherwise (if the flag is clear) then this opcode is part of an INSERT operation. The difference is only important to the update hook. >Parameter P4 may point to a Table structure, or may be NULL. If it is not NULL, then the update-hook (sqlite3.xUpdateCallback) is invoked following a successful insert. >(WARNING/TODO: If P1 is a pseudo-cursor and P2 is dynamically allocated, then ownership of P2 is transferred to the pseudo-cursor and register P2 becomes ephemeral. If the cursor is changed, the value of register P2 will then change. Make sure this does not cause any problems.) >This instruction only works on tables. The equivalent instruction for indices is IdxInsert. |
>
| Int64 | >P4 is a pointer to a 64-bit integer value. Write that value into register P2. | >
| IntCopy | >Transfer the integer value held in register P1 into register P2.
> This is an optimized version of SCopy that works only for integer values. |
>
| Integer | >The 32-bit integer value P1 is written into register P2. | >
| IntegrityCk | >Do an analysis of the currently open database. Store in register (P1+1) the text of an error message describing any problems. If no problems are found, store a NULL in register (P1+1).
> The register (P1) contains one less than the maximum number of allowed errors. At most reg(P1) errors will be reported. In other words, the analysis stops as soon as reg(P1) errors are seen. Reg(P1) is updated with the number of errors remaining. >The root page numbers of all tables in the database are integers stored in P4_INTARRAY argument. >If P5 is not zero, the check is done on the auxiliary database file, not the main database file. >This opcode is used to implement the integrity_check pragma. |
>
| IsNull | >Jump to P2 if the value in register P1 is NULL. | >
| IsTrue | >This opcode implements the IS TRUE, IS FALSE, IS NOT TRUE, and IS NOT FALSE operators.
> Interpret the value in register P1 as a boolean value. Store that boolean (a 0 or 1) in register P2. Or if the value in register P1 is NULL, then the P3 is stored in register P2. Invert the answer if P4 is 1. >The logic is summarized like this: >
|
>
| IsType | >Jump to P2 if the type of a column in a btree is one of the types specified by the P5 bitmask.
> P1 is normally a cursor on a btree for which the row decode cache is valid through at least column P3. In other words, there should have been a prior Column for column P3 or greater. If the cursor is not valid, then this opcode might give spurious results. The the btree row has fewer than P3 columns, then use P4 as the datatype. >If P1 is -1, then P3 is a register number and the datatype is taken from the value in that register. >P5 is a bitmask of data types. SQLITE_INTEGER is the least significant (0x01) bit. SQLITE_FLOAT is the 0x02 bit. SQLITE_TEXT is 0x04. SQLITE_BLOB is 0x08. SQLITE_NULL is 0x10. >WARNING: This opcode does not reliably distinguish between NULL and REAL when P1>=0. If the database contains a NaN value, this opcode will think that the datatype is REAL when it should be NULL. When P1<0 and the value is already stored in register P3, then this opcode does reliably distinguish between NULL and REAL. The problem only arises then P1>=0. >Take the jump to address P2 if and only if the datatype of the value determined by P1 and P3 corresponds to one of the bits in the P5 bitmask. |
>
| JournalMode | >Change the journal mode of database P1 to P3. P3 must be one of the PAGER_JOURNALMODE_XXX values. If changing between the various rollback modes (delete, truncate, persist, off and memory), this is a simple operation. No IO is required.
> If changing into or out of WAL mode the procedure is more complicated. >Write a string containing the final journal-mode to register P2. |
>
| Jump | >Jump to the instruction at address P1, P2, or P3 depending on whether in the most recent Compare instruction the P1 vector was less than, equal to, or greater than the P2 vector, respectively.
> This opcode must immediately follow an Compare opcode. |
>
| Last | >The next use of the Rowid or Column or Prev instruction for P1 will refer to the last entry in the database table or index. If the table or index is empty and P2>0, then jump immediately to P2. If P2 is 0 or if the table or index is not empty, fall through to the following instruction.
> This opcode leaves the cursor configured to move in reverse order, from the end toward the beginning. In other words, the cursor is configured to use Prev, not Next. |
>
| Le | >This works just like the Lt opcode except that the jump is taken if the content of register P3 is less than or equal to the content of register P1. See the Lt opcode for additional information. | >
| LoadAnalysis | >Read the sqlite_stat1 table for database P1 and load the content of that table into the internal index hash table. This will cause the analysis to be used when preparing all subsequent queries. | >
| Lt | >Compare the values in register P1 and P3. If reg(P3)<reg(P1) then jump to address P2.
> If the SQLITE_JUMPIFNULL bit of P5 is set and either reg(P1) or reg(P3) is NULL then the take the jump. If the SQLITE_JUMPIFNULL bit is clear then fall through if either operand is NULL. >The SQLITE_AFF_MASK portion of P5 must be an affinity character - SQLITE_AFF_TEXT, SQLITE_AFF_INTEGER, and so forth. An attempt is made to coerce both inputs according to this affinity before the comparison is made. If the SQLITE_AFF_MASK is 0x00, then numeric affinity is used. Note that the affinity conversions are stored back into the input registers P1 and P3. So this opcode can cause persistent changes to registers P1 and P3. >Once any conversions have taken place, and neither value is NULL, the values are compared. If both values are blobs then memcmp() is used to determine the results of the comparison. If both values are text, then the appropriate collating function specified in P4 is used to do the comparison. If P4 is not specified then memcmp() is used to compare text string. If both values are numeric, then a numeric comparison is used. If the two values are of different types, then numbers are considered less than strings and strings are considered less than blobs. >This opcode saves the result of comparison for use by the new Jump opcode. |
>
| MakeRecord | >Convert P2 registers beginning with P1 into the record format use as a data record in a database table or as a key in an index. The Column opcode can decode the record later.
> P4 may be a string that is P2 characters long. The N-th character of the string indicates the column affinity that should be used for the N-th field of the index key. >The mapping from character to affinity is given by the SQLITE_AFF_ macros defined in sqliteInt.h. >If P4 is NULL then all index fields have the affinity BLOB. >The meaning of P5 depends on whether or not the SQLITE_ENABLE_NULL_TRIM compile-time option is enabled: >* If SQLITE_ENABLE_NULL_TRIM is enabled, then the P5 is the index of the right-most table that can be null-trimmed. >* If SQLITE_ENABLE_NULL_TRIM is omitted, then P5 has the value OPFLAG_NOCHNG_MAGIC if the MakeRecord opcode is allowed to accept no-change records with serial_type 10. This value is only used inside an assert() and does not affect the end result. |
>
| MaxPgcnt | >Try to set the maximum page count for database P1 to the value in P3. Do not let the maximum page count fall below the current page count and do not change the maximum page count value if P3==0.
> Store the maximum page count after the change in register P2. |
>
| MemMax | >P1 is a register in the root frame of this VM (the root frame is different from the current frame if this instruction is being executed within a sub-program). Set the value of register P1 to the maximum of its current value and the value in register P2.
> This instruction throws an error if the memory cell is not initially an integer. |
>
| Move | >Move the P3 values in register P1..P1+P3-1 over into registers P2..P2+P3-1. Registers P1..P1+P3-1 are left holding a NULL. It is an error for register ranges P1..P1+P3-1 and P2..P2+P3-1 to overlap. It is an error for P3 to be less than 1. | >
| Multiply | >Multiply the value in register P1 by the value in register P2 and store the result in register P3. If either input is NULL, the result is NULL. | >
| MustBeInt | >Force the value in register P1 to be an integer. If the value in P1 is not an integer and cannot be converted into an integer without data loss, then jump immediately to P2, or if P2==0 raise an SQLITE_MISMATCH exception. | >
| Ne | >This works just like the Eq opcode except that the jump is taken if the operands in registers P1 and P3 are not equal. See the Eq opcode for additional information. | >
| NewRowid | >Get a new integer record number (a.k.a "rowid") used as the key to a table. The record number is not previously used as a key in the database table that cursor P1 points to. The new record number is written written to register P2.
> If P3>0 then P3 is a register in the root frame of this VDBE that holds the largest previously generated record number. No new record numbers are allowed to be less than this value. When this value reaches its maximum, an SQLITE_FULL error is generated. The P3 register is updated with the ' generated record number. This P3 mechanism is used to help implement the AUTOINCREMENT feature. |
>
| Next | >Advance cursor P1 so that it points to the next key/data pair in its table or index. If there are no more key/value pairs then fall through to the following instruction. But if the cursor advance was successful, jump immediately to P2.
> The Next opcode is only valid following an SeekGT, SeekGE, or Rewind opcode used to position the cursor. Next is not allowed to follow SeekLT, SeekLE, or Last. >The P1 cursor must be for a real table, not a pseudo-table. P1 must have been opened prior to this opcode or the program will segfault. >The P3 value is a hint to the btree implementation. If P3==1, that means P1 is an SQL index and that this instruction could have been omitted if that index had been unique. P3 is usually 0. P3 is always either 0 or 1. >If P5 is positive and the jump is taken, then event counter number P5-1 in the prepared statement is incremented. >See also: Prev |
>
| NoConflict | >If P4==0 then register P3 holds a blob constructed by MakeRecord. If P4>0 then register P3 is the first of P4 registers that form an unpacked record.
> Cursor P1 is on an index btree. If the record identified by P3 and P4 contains any NULL value, jump immediately to P2. If all terms of the record are not-NULL then a check is done to determine if any row in the P1 index btree has a matching key prefix. If there are no matches, jump immediately to P2. If there is a match, fall through and leave the P1 cursor pointing to the matching row. >This opcode is similar to NotFound with the exceptions that the branch is always taken if any part of the search key input is NULL. >This operation leaves the cursor in a state where it cannot be advanced in either direction. In other words, the Next and Prev opcodes do not work after this operation. > |
>
| Noop | >Do nothing. Continue downward to the next opcode. | >
| Not | >Interpret the value in register P1 as a boolean value. Store the boolean complement in register P2. If the value in register P1 is NULL, then a NULL is stored in P2. | >
| NotExists | >P1 is the index of a cursor open on an SQL table btree (with integer keys). P3 is an integer rowid. If P1 does not contain a record with rowid P3 then jump immediately to P2. Or, if P2 is 0, raise an SQLITE_CORRUPT error. If P1 does contain a record with rowid P3 then leave the cursor pointing at that record and fall through to the next instruction.
> The SeekRowid opcode performs the same operation but also allows the P3 register to contain a non-integer value, in which case the jump is always taken. This opcode requires that P3 always contain an integer. >The NotFound opcode performs the same operation on index btrees (with arbitrary multi-value keys). >This opcode leaves the cursor in a state where it cannot be advanced in either direction. In other words, the Next and Prev opcodes will not work following this opcode. >See also: Found, NotFound, NoConflict, SeekRowid |
>
| NotFound | >If P4==0 then register P3 holds a blob constructed by MakeRecord. If P4>0 then register P3 is the first of P4 registers that form an unpacked record.
> Cursor P1 is on an index btree. If the record identified by P3 and P4 is not the prefix of any entry in P1 then a jump is made to P2. If P1 does contain an entry whose prefix matches the P3/P4 record then control falls through to the next instruction and P1 is left pointing at the matching entry. >This operation leaves the cursor in a state where it cannot be advanced in either direction. In other words, the Next and Prev opcodes do not work after this operation. >See also: Found, NotExists, NoConflict, IfNoHope |
>
| NotNull | >Jump to P2 if the value in register P1 is not NULL. | >
| Null | >Write a NULL into registers P2. If P3 greater than P2, then also write NULL into register P3 and every register in between P2 and P3. If P3 is less than P2 (typically P3 is zero) then only register P2 is set to NULL.
> If the P1 value is non-zero, then also set the MEM_Cleared flag so that NULL values will not compare equal even if SQLITE_NULLEQ is set on Ne or Eq. |
>
| NullRow | >Move the cursor P1 to a null row. Any Column operations that occur while the cursor is on the null row will always write a NULL.
> If cursor P1 is not previously opened, open it now to a special pseudo-cursor that always returns NULL for every column. |
>
| Offset | >Store in register r[P3] the byte offset into the database file that is the start of the payload for the record at which that cursor P1 is currently pointing.
> P2 is the column number for the argument to the sqlite_offset() function. This opcode does not use P2 itself, but the P2 value is used by the code generator. The P1, P2, and P3 operands to this opcode are the same as for Column. >This opcode is only available if SQLite is compiled with the -DSQLITE_ENABLE_OFFSET_SQL_FUNC option. |
>
| OffsetLimit | >This opcode performs a commonly used computation associated with LIMIT and OFFSET processing. r[P1] holds the limit counter. r[P3] holds the offset counter. The opcode computes the combined value of the LIMIT and OFFSET and stores that value in r[P2]. The r[P2] value computed is the total number of rows that will need to be visited in order to complete the query.
> If r[P3] is zero or negative, that means there is no OFFSET and r[P2] is set to be the value of the LIMIT, r[P1]. >if r[P1] is zero or negative, that means there is no LIMIT and r[P2] is set to -1. >Otherwise, r[P2] is set to the sum of r[P1] and r[P3]. |
>
| Once | >Fall through to the next instruction the first time this opcode is encountered on each invocation of the byte-code program. Jump to P2 on the second and all subsequent encounters during the same invocation.
> Top-level programs determine first invocation by comparing the P1 operand against the P1 operand on the Init opcode at the beginning of the program. If the P1 values differ, then fall through and make the P1 of this opcode equal to the P1 of Init. If P1 values are the same then take the jump. >For subprograms, there is a bitmask in the VdbeFrame that determines whether or not the jump should be taken. The bitmask is necessary because the self-altering code trick does not work for recursive triggers. >The P3 operand is not used directly by this opcode. However P3 is used by the code generator as follows: If this opcode is the start of a subroutine and that subroutine uses a Bloom filter, then P3 will be the register that holds that Bloom filter. See tag-202407032019 in the source code for implementation details. |
>
| OpenAutoindex | >This opcode works the same as OpenEphemeral. It has a different name to distinguish its use. Tables created using by this opcode will be used for automatically created transient indices in joins. | >
| OpenDup | >Open a new cursor P1 that points to the same ephemeral table as cursor P2. The P2 cursor must have been opened by a prior OpenEphemeral opcode. Only ephemeral cursors may be duplicated.
> Duplicate ephemeral cursors are used for self-joins of materialized views. |
>
| OpenEphemeral | >Open a new cursor P1 to a transient table. The cursor is always opened read/write even if the main database is read-only. The ephemeral table is deleted automatically when the cursor is closed.
> If the cursor P1 is already opened on an ephemeral table, the table is cleared (all content is erased). >P2 is the number of columns in the ephemeral table. The cursor points to a BTree table if P4==0 and to a BTree index if P4 is not 0. If P4 is not NULL, it points to a KeyInfo structure that defines the format of keys in the index. >The P5 parameter can be a mask of the BTREE_* flags defined in btree.h. These flags control aspects of the operation of the btree. The BTREE_OMIT_JOURNAL and BTREE_SINGLE flags are added automatically. >If P3 is positive, then reg[P3] is modified slightly so that it can be used as zero-length data for Insert. This is an optimization that avoids an extra Blob opcode to initialize that register. |
>
| OpenPseudo | >Open a new cursor that points to a fake table that contains a single row of data. The content of that one row is the content of memory register P2. In other words, cursor P1 becomes an alias for the MEM_Blob content contained in register P2.
> A pseudo-table created by this opcode is used to hold a single row output from the sorter so that the row can be decomposed into individual columns using the Column opcode. The Column opcode is the only cursor opcode that works with a pseudo-table. >P3 is the number of fields in the records that will be stored by the pseudo-table. If P2 is 0 or negative then the pseudo-cursor will return NULL for every column. |
>
| OpenRead | >Open a read-only cursor for the database table whose root page is P2 in a database file. The database file is determined by P3. P3==0 means the main database, P3==1 means the database used for temporary tables, and P3>1 means used the corresponding attached database. Give the new cursor an identifier of P1. The P1 values need not be contiguous but all P1 values should be small integers. It is an error for P1 to be negative.
> Allowed P5 bits: >
The P4 value may be either an integer (P4_INT32) or a pointer to a KeyInfo structure (P4_KEYINFO). If it is a pointer to a KeyInfo object, then table being opened must be an index b-tree where the KeyInfo object defines the content and collating sequence of that index b-tree. Otherwise, if P4 is an integer value, then the table being opened must be a table b-tree with a number of columns no less than the value of P4. > |
>
| OpenWrite | >Open a read/write cursor named P1 on the table or index whose root page is P2 (or whose root page is held in register P2 if the OPFLAG_P2ISREG bit is set in P5 - see below).
> The P4 value may be either an integer (P4_INT32) or a pointer to a KeyInfo structure (P4_KEYINFO). If it is a pointer to a KeyInfo object, then table being opened must be an index b-tree where the KeyInfo object defines the content and collating sequence of that index b-tree. Otherwise, if P4 is an integer value, then the table being opened must be a table b-tree with a number of columns no less than the value of P4. >Allowed P5 bits: >
This instruction works like OpenRead except that it opens the cursor in read/write mode. > |
>
| Or | >Take the logical OR of the values in register P1 and P2 and store the answer in register P3.
> If either P1 or P2 is nonzero (true) then the result is 1 (true) even if the other input is NULL. A NULL and false or two NULLs give a NULL output. |
>
| Pagecount | >Write the current number of pages in database P1 to memory cell P2. | >
| Param | >This opcode is only ever present in sub-programs called via the Program instruction. Copy a value currently stored in a memory cell of the calling (parent) frame to cell P2 in the current frames address space. This is used by trigger programs to access the new.* and old.* values.
> The address of the cell in the parent frame is determined by adding the value of the P1 argument to the value of the P1 argument to the calling Program instruction. |
>
| ParseSchema | >Read and parse all entries from the schema table of database P1 that match the WHERE clause P4. If P4 is a NULL pointer, then the entire schema for P1 is reparsed.
> This opcode invokes the parser to create a new virtual machine, then runs the new virtual machine. It is thus a re-entrant opcode. |
>
| Permutation | >Set the permutation used by the Compare operator in the next instruction. The permutation is stored in the P4 operand.
> The permutation is only valid for the next opcode which must be an Compare that has the OPFLAG_PERMUTE bit set in P5. >The first integer in the P4 integer array is the length of the array and does not become part of the permutation. |
>
| Prev | >Back up cursor P1 so that it points to the previous key/data pair in its table or index. If there is no previous key/value pairs then fall through to the following instruction. But if the cursor backup was successful, jump immediately to P2.
> The Prev opcode is only valid following an SeekLT, SeekLE, or Last opcode used to position the cursor. Prev is not allowed to follow SeekGT, SeekGE, or Rewind. >The P1 cursor must be for a real table, not a pseudo-table. If P1 is not open then the behavior is undefined. >The P3 value is a hint to the btree implementation. If P3==1, that means P1 is an SQL index and that this instruction could have been omitted if that index had been unique. P3 is usually 0. P3 is always either 0 or 1. >If P5 is positive and the jump is taken, then event counter number P5-1 in the prepared statement is incremented. |
>
| Program | >Execute the trigger program passed as P4 (type P4_SUBPROGRAM).
> P1 contains the address of the memory cell that contains the first memory cell in an array of values used as arguments to the sub-program. P2 contains the address to jump to if the sub-program throws an IGNORE exception using the RAISE() function. P2 might be zero, if there is no possibility that an IGNORE exception will be raised. Register P3 contains the address of a memory cell in this (the parent) VM that is used to allocate the memory required by the sub-vdbe at runtime. >P4 is a pointer to the VM containing the trigger program. >If P5 is non-zero, then recursive program invocation is enabled. |
>
| PureFunc | >Invoke a user function (P4 is a pointer to an sqlite3_context object that contains a pointer to the function to be run) with arguments taken from register P2 and successors. The number of arguments is in the sqlite3_context object that P4 points to. The result of the function is stored in register P3. Register P3 must not be one of the function inputs.
> P1 is a 32-bit bitmask indicating whether or not each argument to the function was determined to be constant at compile time. If the first argument was constant then bit 0 of P1 is set. This is used to determine whether meta data associated with a user function argument using the sqlite3_set_auxdata() API may be safely retained until the next invocation of this opcode. >This opcode works exactly like Function. The only difference is in its name. This opcode is used in places where the function must be purely non-deterministic. Some built-in date/time functions can be either deterministic of non-deterministic, depending on their arguments. When those function are used in a non-deterministic way, they will check to see if they were called using PureFunc instead of Function, and if they were, they throw an error. > |
>
| ReadCookie | >Read cookie number P3 from database P1 and write it into register P2. P3==1 is the schema version. P3==2 is the database format. P3==3 is the recommended pager cache size, and so forth. P1==0 is the main database file and P1==1 is the database file used to store temporary tables.
> There must be a read-lock on the database (either a transaction must be started or there must be an open cursor) before executing this instruction. |
>
| Real | >P4 is a pointer to a 64-bit floating point value. Write that value into register P2. | >
| RealAffinity | >If register P1 holds an integer convert it to a real value.
> This opcode is used when extracting information from a column that has REAL affinity. Such column values may still be stored as integers, for space efficiency, but after extraction we want them to have only a real value. |
>
| ReleaseReg | >Release registers from service. Any content that was in the the registers is unreliable after this opcode completes.
> The registers released will be the P2 registers starting at P1, except if bit ii of P3 set, then do not release register P1+ii. In other words, P3 is a mask of registers to preserve. >Releasing a register clears the Mem.pScopyFrom pointer. That means that if the content of the released register was set using SCopy, a change to the value of the source register for the SCopy will no longer generate an assertion fault in sqlite3VdbeMemAboutToChange(). >If P5 is set, then all released registers have their type set to MEM_Undefined so that any subsequent attempt to read the released register (before it is reinitialized) will generate an assertion fault. >P5 ought to be set on every call to this opcode. However, there are places in the code generator will release registers before their are used, under the (valid) assumption that the registers will not be reallocated for some other purpose before they are used and hence are safe to release. >This opcode is only available in testing and debugging builds. It is not generated for release builds. The purpose of this opcode is to help validate the generated bytecode. This opcode does not actually contribute to computing an answer. |
>
| Remainder | >Compute the remainder after integer register P2 is divided by register P1 and store the result in register P3. If the value in register P1 is zero the result is NULL. If either operand is NULL, the result is NULL. | >
| ReopenIdx | >The ReopenIdx opcode works like OpenRead except that it first checks to see if the cursor on P1 is already open on the same b-tree and if it is this opcode becomes a no-op. In other words, if the cursor is already open, do not reopen it.
> The ReopenIdx opcode may only be used with P5==0 or P5==OPFLAG_SEEKEQ and with P4 being a P4_KEYINFO object. Furthermore, the P3 value must be the same as every other ReopenIdx or OpenRead for the same cursor number. >Allowed P5 bits: > > |
>
| ResetCount | >The value of the change counter is copied to the database handle change counter (returned by subsequent calls to sqlite3_changes()). Then the VMs internal change counter resets to 0. This is used by trigger programs. | >
| ResetSorter | >Delete all contents from the ephemeral table or sorter that is open on cursor P1.
> This opcode only works for cursors used for sorting and opened with OpenEphemeral or SorterOpen. |
>
| ResultRow | >The registers P1 through P1+P2-1 contain a single row of results. This opcode causes the sqlite3_step() call to terminate with an SQLITE_ROW return code and it sets up the sqlite3_stmt structure to provide access to the r(P1)..r(P1+P2-1) values as the result row. | >
| Return | >Jump to the address stored in register P1. If P1 is a return address register, then this accomplishes a return from a subroutine.
> If P3 is 1, then the jump is only taken if register P1 holds an integer values, otherwise execution falls through to the next opcode, and the Return becomes a no-op. If P3 is 0, then register P1 must hold an integer or else an assert() is raised. P3 should be set to 1 when this opcode is used in combination with BeginSubrtn, and set to 0 otherwise. >The value in register P1 is unchanged by this opcode. >P2 is not used by the byte-code engine. However, if P2 is positive and also less than the current address, then the "EXPLAIN" output formatter in the CLI will indent all opcodes from the P2 opcode up to be not including the current Return. P2 should be the first opcode in the subroutine from which this opcode is returning. Thus the P2 value is a byte-code indentation hint. See tag-20220407a in wherecode.c and shell.c. |
>
| Rewind | >The next use of the Rowid or Column or Next instruction for P1 will refer to the first entry in the database table or index. If the table or index is empty, jump immediately to P2. If the table or index is not empty, fall through to the following instruction.
> If P2 is zero, that is an assertion that the P1 table is never empty and hence the jump will never be taken. >This opcode leaves the cursor configured to move in forward order, from the beginning toward the end. In other words, the cursor is configured to use Next, not Prev. |
>
| RowCell | >P1 and P2 are both open cursors. Both must be opened on the same type of table - intkey or index. This opcode is used as part of copying the current row from P2 into P1. If the cursors are opened on intkey tables, register P3 contains the rowid to use with the new record in P1. If they are opened on index tables, P3 is not used.
> This opcode must be followed by either an Insert or InsertIdx opcode with the OPFLAG_PREFORMAT flag set to complete the insert operation. |
>
| RowData | >Write into register P2 the complete row content for the row at which cursor P1 is currently pointing. There is no interpretation of the data. It is just copied onto the P2 register exactly as it is found in the database file.
> If cursor P1 is an index, then the content is the key of the row. If cursor P2 is a table, then the content extracted is the data. >If the P1 cursor must be pointing to a valid row (not a NULL row) of a real table, not a pseudo-table. >If P3!=0 then this opcode is allowed to make an ephemeral pointer into the database page. That means that the content of the output register will be invalidated as soon as the cursor moves - including moves caused by other cursors that "save" the current cursors position in order that they can write to the same table. If P3==0 then a copy of the data is made into memory. P3!=0 is faster, but P3==0 is safer. >If P3!=0 then the content of the P2 register is unsuitable for use in OP_Result and any OP_Result will invalidate the P2 register content. The P2 register content is invalidated by opcodes like Function or by any use of another cursor pointing to the same table. |
>
| Rowid | >Store in register P2 an integer which is the key of the table entry that P1 is currently point to.
> P1 can be either an ordinary table or a virtual table. There used to be a separate OP_VRowid opcode for use with virtual tables, but this one opcode now works for both table types. |
>
| RowSetAdd | >Insert the integer value held by register P2 into a RowSet object held in register P1.
> An assertion fails if P2 is not an integer. |
>
| RowSetRead | >Extract the smallest value from the RowSet object in P1 and put that value into register P3. Or, if RowSet object P1 is initially empty, leave P3 unchanged and jump to instruction P2. | >
| RowSetTest | >Register P3 is assumed to hold a 64-bit integer value. If register P1 contains a RowSet object and that RowSet object contains the value held in P3, jump to register P2. Otherwise, insert the integer in P3 into the RowSet and continue on to the next opcode.
> The RowSet object is optimized for the case where sets of integers are inserted in distinct phases, which each set contains no duplicates. Each set is identified by a unique P4 value. The first set must have P4==0, the final set must have P4==-1, and for all other sets must have P4>0. >This allows optimizations: (a) when P4==0 there is no need to test the RowSet object for P3, as it is guaranteed not to contain it, (b) when P4==-1 there is no need to insert the value, as it will never be tested for, and (c) when a value that is part of set X is inserted, there is no need to search to see if the same value was previously inserted as part of set X (only if it was previously inserted as part of some other set). |
>
| Savepoint | >Open, release or rollback the savepoint named by parameter P4, depending on the value of P1. To open a new savepoint set P1==0 (SAVEPOINT_BEGIN). To release (commit) an existing savepoint set P1==1 (SAVEPOINT_RELEASE). To rollback an existing savepoint set P1==2 (SAVEPOINT_ROLLBACK). | >
| SCopy | >Make a shallow copy of register P1 into register P2.
> This instruction makes a shallow copy of the value. If the value is a string or blob, then the copy is only a pointer to the original and hence if the original changes so will the copy. Worse, if the original is deallocated, the copy becomes invalid. Thus the program must guarantee that the original will not change during the lifetime of the copy. Use Copy to make a complete copy. |
>
| SeekEnd | >Position cursor P1 at the end of the btree for the purpose of appending a new entry onto the btree.
> It is assumed that the cursor is used only for appending and so if the cursor is valid, then the cursor must already be pointing at the end of the btree and so no changes are made to the cursor. |
>
| SeekGE | >If cursor P1 refers to an SQL table (B-Tree that uses integer keys), use the value in register P3 as the key. If cursor P1 refers to an SQL index, then P3 is the first in an array of P4 registers that are used as an unpacked index key.
> Reposition cursor P1 so that it points to the smallest entry that is greater than or equal to the key value. If there are no records greater than or equal to the key and P2 is not zero, then jump to P2. >If the cursor P1 was opened using the OPFLAG_SEEKEQ flag, then this opcode will either land on a record that exactly matches the key, or else it will cause a jump to P2. When the cursor is OPFLAG_SEEKEQ, this opcode must be followed by an IdxLE opcode with the same arguments. The IdxGT opcode will be skipped if this opcode succeeds, but the IdxGT opcode will be used on subsequent loop iterations. The OPFLAG_SEEKEQ flags is a hint to the btree layer to say that this is an equality search. >This opcode leaves the cursor configured to move in forward order, from the beginning toward the end. In other words, the cursor is configured to use Next, not Prev. > |
>
| SeekGT | >If cursor P1 refers to an SQL table (B-Tree that uses integer keys), use the value in register P3 as a key. If cursor P1 refers to an SQL index, then P3 is the first in an array of P4 registers that are used as an unpacked index key.
> Reposition cursor P1 so that it points to the smallest entry that is greater than the key value. If there are no records greater than the key and P2 is not zero, then jump to P2. >This opcode leaves the cursor configured to move in forward order, from the beginning toward the end. In other words, the cursor is configured to use Next, not Prev. > |
>
| SeekHit | >Increase or decrease the seekHit value for cursor P1, if necessary, so that it is no less than P2 and no greater than P3.
> The seekHit integer represents the maximum of terms in an index for which there is known to be at least one match. If the seekHit value is smaller than the total number of equality terms in an index lookup, then the IfNoHope opcode might run to see if the IN loop can be abandoned early, thus saving work. This is part of the IN-early-out optimization. >P1 must be a valid b-tree cursor. |
>
| SeekLE | >If cursor P1 refers to an SQL table (B-Tree that uses integer keys), use the value in register P3 as a key. If cursor P1 refers to an SQL index, then P3 is the first in an array of P4 registers that are used as an unpacked index key.
> Reposition cursor P1 so that it points to the largest entry that is less than or equal to the key value. If there are no records less than or equal to the key and P2 is not zero, then jump to P2. >This opcode leaves the cursor configured to move in reverse order, from the end toward the beginning. In other words, the cursor is configured to use Prev, not Next. >If the cursor P1 was opened using the OPFLAG_SEEKEQ flag, then this opcode will either land on a record that exactly matches the key, or else it will cause a jump to P2. When the cursor is OPFLAG_SEEKEQ, this opcode must be followed by an IdxLE opcode with the same arguments. The IdxGE opcode will be skipped if this opcode succeeds, but the IdxGE opcode will be used on subsequent loop iterations. The OPFLAG_SEEKEQ flags is a hint to the btree layer to say that this is an equality search. > |
>
| SeekLT | >If cursor P1 refers to an SQL table (B-Tree that uses integer keys), use the value in register P3 as a key. If cursor P1 refers to an SQL index, then P3 is the first in an array of P4 registers that are used as an unpacked index key.
> Reposition cursor P1 so that it points to the largest entry that is less than the key value. If there are no records less than the key and P2 is not zero, then jump to P2. >This opcode leaves the cursor configured to move in reverse order, from the end toward the beginning. In other words, the cursor is configured to use Prev, not Next. > |
>
| SeekRowid | >P1 is the index of a cursor open on an SQL table btree (with integer keys). If register P3 does not contain an integer or if P1 does not contain a record with rowid P3 then jump immediately to P2. Or, if P2 is 0, raise an SQLITE_CORRUPT error. If P1 does contain a record with rowid P3 then leave the cursor pointing at that record and fall through to the next instruction.
> The NotExists opcode performs the same operation, but with NotExists the P3 register must be guaranteed to contain an integer value. With this opcode, register P3 might not contain an integer. >The NotFound opcode performs the same operation on index btrees (with arbitrary multi-value keys). >This opcode leaves the cursor in a state where it cannot be advanced in either direction. In other words, the Next and Prev opcodes will not work following this opcode. >See also: Found, NotFound, NoConflict, SeekRowid |
>
| SeekScan | >This opcode is a prefix opcode to SeekGE. In other words, this opcode must be immediately followed by SeekGE. This constraint is checked by assert() statements.
> This opcode uses the P1 through P4 operands of the subsequent SeekGE. In the text that follows, the operands of the subsequent SeekGE opcode are denoted as SeekOP.P1 through SeekOP.P4. Only the P1, P2 and P5 operands of this opcode are also used, and are called This.P1, This.P2 and This.P5. >This opcode helps to optimize IN operators on a multi-column index where the IN operator is on the later terms of the index by avoiding unnecessary seeks on the btree, substituting steps to the next row of the b-tree instead. A correct answer is obtained if this opcode is omitted or is a no-op. >The SeekGE.P3 and SeekGE.P4 operands identify an unpacked key which is the desired entry that we want the cursor SeekGE.P1 to be pointing to. Call this SeekGE.P3/P4 row the "target". >If the SeekGE.P1 cursor is not currently pointing to a valid row, then this opcode is a no-op and control passes through into the SeekGE. >If the SeekGE.P1 cursor is pointing to a valid row, then that row might be the target row, or it might be near and slightly before the target row, or it might be after the target row. If the cursor is currently before the target row, then this opcode attempts to position the cursor on or after the target row by invoking sqlite3BtreeStep() on the cursor between 1 and This.P1 times. >The This.P5 parameter is a flag that indicates what to do if the cursor ends up pointing at a valid row that is past the target row. If This.P5 is false (0) then a jump is made to SeekGE.P2. If This.P5 is true (non-zero) then a jump is made to This.P2. The P5==0 case occurs when there are no inequality constraints to the right of the IN constraint. The jump to SeekGE.P2 ends the loop. The P5!=0 case occurs when there are inequality constraints to the right of the IN operator. In that case, the This.P2 will point either directly to or to setup code prior to the IdxGT or IdxGE opcode that checks for loop terminate. >Possible outcomes from this opcode: > If the cursor is initially not pointed to any valid row, then fall through into the subsequent SeekGE opcode. > If the cursor is left pointing to a row that is before the target row, even after making as many as This.P1 calls to sqlite3BtreeNext(), then also fall through into SeekGE. > If the cursor is left pointing at the target row, either because it was at the target row to begin with or because one or more sqlite3BtreeNext() calls moved the cursor to the target row, then jump to This.P2.., > If the cursor started out before the target row and a call to to sqlite3BtreeNext() moved the cursor off the end of the index (indicating that the target row definitely does not exist in the btree) then jump to SeekGE.P2, ending the loop. > If the cursor ends up on a valid row that is past the target row (indicating that the target row does not exist in the btree) then jump to SeekOP.P2 if This.P5==0 or to This.P2 if This.P5>0. |
>
| Sequence | >Find the next available sequence number for cursor P1. Write the sequence number into register P2. The sequence number on the cursor is incremented after this instruction. | >
| SequenceTest | >P1 is a sorter cursor. If the sequence counter is currently zero, jump to P2. Regardless of whether or not the jump is taken, increment the the sequence value. | >
| SetCookie | >Write the integer value P3 into cookie number P2 of database P1. P2==1 is the schema version. P2==2 is the database format. P2==3 is the recommended pager cache size, and so forth. P1==0 is the main database file and P1==1 is the database file used to store temporary tables.
> A transaction must be started before executing this opcode. >If P2 is the SCHEMA_VERSION cookie (cookie number 1) then the internal schema version is set to P3-P5. The "PRAGMA schema_version=N" statement has P5 set to 1, so that the internal schema version will be different from the database schema version, resulting in a schema reset. |
>
| SetSubtype | >Set the subtype value of register P2 to the integer from register P1. If P1 is NULL, clear the subtype from p2. | >
| ShiftLeft | >Shift the integer value in register P2 to the left by the number of bits specified by the integer in register P1. Store the result in register P3. If either input is NULL, the result is NULL. | >
| ShiftRight | >Shift the integer value in register P2 to the right by the number of bits specified by the integer in register P1. Store the result in register P3. If either input is NULL, the result is NULL. | >
| SoftNull | >Set register P1 to have the value NULL as seen by the MakeRecord instruction, but do not free any string or blob memory associated with the register, so that if the value was a string or blob that was previously copied using SCopy, the copies will continue to be valid. | >
| Sort | >This opcode does exactly the same thing as Rewind except that it increments an undocumented global variable used for testing.
> Sorting is accomplished by writing records into a sorting index, then rewinding that index and playing it back from beginning to end. We use the Sort opcode instead of Rewind to do the rewinding so that the global variable will be incremented and regression tests can determine whether or not the optimizer is correctly optimizing out sorts. |
>
| SorterCompare | >P1 is a sorter cursor. This instruction compares a prefix of the record blob in register P3 against a prefix of the entry that the sorter cursor currently points to. Only the first P4 fields of r[P3] and the sorter record are compared.
> If either P3 or the sorter contains a NULL in one of their significant fields (not counting the P4 fields at the end which are ignored) then the comparison is assumed to be equal. >Fall through to next instruction if the two records compare equal to each other. Jump to P2 if they are different. |
>
| SorterData | >Write into register P2 the current sorter data for sorter cursor P1. Then clear the column header cache on cursor P3.
> This opcode is normally used to move a record out of the sorter and into a register that is the source for a pseudo-table cursor created using OpenPseudo. That pseudo-table cursor is the one that is identified by parameter P3. Clearing the P3 column cache as part of this opcode saves us from having to issue a separate NullRow instruction to clear that cache. |
>
| SorterInsert | >Register P2 holds an SQL index key made using the MakeRecord instructions. This opcode writes that key into the sorter P1. Data for the entry is nil. | >
| SorterNext | >This opcode works just like Next except that P1 must be a sorter object for which the SorterSort opcode has been invoked. This opcode advances the cursor to the next sorted record, or jumps to P2 if there are no more sorted records. | >
| SorterOpen | >This opcode works like OpenEphemeral except that it opens a transient index that is specifically designed to sort large tables using an external merge-sort algorithm.
> If argument P3 is non-zero, then it indicates that the sorter may assume that a stable sort considering the first P3 fields of each key is sufficient to produce the required results. |
>
| SorterSort | >After all records have been inserted into the Sorter object identified by P1, invoke this opcode to actually do the sorting. Jump to P2 if there are no records to be sorted.
> This opcode is an alias for Sort and Rewind that is used for Sorter objects. |
>
| SqlExec | >Run the SQL statement or statements specified in the P4 string.
> The P1 parameter is a bitmask of options: >0x0001 Disable Auth and Trace callbacks while the statements in P4 are running. >0x0002 Set db->nAnalysisLimit to P2 while the statements in P4 are running. |
>
| String | >The string value P4 of length P1 (bytes) is stored in register P2.
> If P3 is not zero and the content of register P3 is equal to P5, then the datatype of the register P2 is converted to BLOB. The content is the same sequence of bytes, it is merely interpreted as a BLOB instead of a string, as if it had been CAST. In other words: >if( P3!=0 and reg[P3]==P5 ) reg[P2] := CAST(reg[P2] as BLOB) |
>
| String8 | >P4 points to a nul terminated UTF-8 string. This opcode is transformed into a String opcode before it is executed for the first time. During this transformation, the length of string P4 is computed and stored as the P1 parameter. | >
| Subtract | >Subtract the value in register P1 from the value in register P2 and store the result in register P3. If either input is NULL, the result is NULL. | >
| TableLock | >Obtain a lock on a particular table. This instruction is only used when the shared-cache feature is enabled.
> P1 is the index of the database in sqlite3.aDb[] of the database on which the lock is acquired. A readlock is obtained if P3==0 or a write lock if P3==1. >P2 contains the root-page of the table to lock. >P4 contains a pointer to the name of the table being locked. This is only used to generate an error message if the lock cannot be obtained. |
>
| Trace | >Write P4 on the statement trace output if statement tracing is enabled.
> Operand P1 must be 0x7fffffff and P2 must positive. |
>
| Transaction | >Begin a transaction on database P1 if a transaction is not already active. If P2 is non-zero, then a write-transaction is started, or if a read-transaction is already active, it is upgraded to a write-transaction. If P2 is zero, then a read-transaction is started. If P2 is 2 or more then an exclusive transaction is started.
> P1 is the index of the database file on which the transaction is started. Index 0 is the main database file and index 1 is the file used for temporary tables. Indices of 2 or more are used for attached databases. >If a write-transaction is started and the Vdbe.usesStmtJournal flag is true (this flag is set if the Vdbe may modify more than one row and may throw an ABORT exception), a statement transaction may also be opened. More specifically, a statement transaction is opened iff the database connection is currently not in autocommit mode, or if there are other active statements. A statement transaction allows the changes made by this VDBE to be rolled back after an error without having to roll back the entire transaction. If no error is encountered, the statement transaction will automatically commit when the VDBE halts. >If P5!=0 then this opcode also checks the schema cookie against P3 and the schema generation counter against P4. The cookie changes its value whenever the database schema changes. This operation is used to detect when that the cookie has changed and that the current process needs to reread the schema. If the schema cookie in P3 differs from the schema cookie in the database header or if the schema generation counter in P4 differs from the current generation counter, then an SQLITE_SCHEMA error is raised and execution halts. The sqlite3_step() wrapper function might then reprepare the statement and rerun it from the beginning. |
>
| TypeCheck | >Apply affinities to the range of P2 registers beginning with P1. Take the affinities from the Table object in P4. If any value cannot be coerced into the correct type, then raise an error.
> If P3==0, then omit checking of VIRTUAL columns. >If P3==1, then omit checking of all generated column, both VIRTUAL and STORED. >If P3>=2, then only check column number P3-2 in the table (which will be a VIRTUAL column) against the value in reg[P1]. In this case, P2 will be 1. >This opcode is similar to Affinity except that this opcode forces the register type to the Table column type. This is used to implement "strict affinity". >GENERATED ALWAYS AS ... STATIC columns are only checked if P3 is zero. When P3 is non-zero, no type checking occurs for static generated columns. Virtual columns are computed at query time and so they are never checked. >Preconditions: >
If any precondition is false, an assertion fault occurs. |
>
| Vacuum | >Vacuum the entire database P1. P1 is 0 for "main", and 2 or more for an attached database. The "temp" database may not be vacuumed.
> If P2 is not zero, then it is a register holding a string which is the file into which the result of vacuum should be written. When P2 is zero, the vacuum overwrites the original database. |
>
| Variable | >Transfer the values of bound parameter P1 into register P2 | >
| VBegin | >P4 may be a pointer to an sqlite3_vtab structure. If so, call the xBegin method for that table.
> Also, whether or not P4 is set, check that this is not being called from within a callback to a virtual table xSync() method. If it is, the error code will be set to SQLITE_LOCKED. |
>
| VCheck | >P4 is a pointer to a Table object that is a virtual table in schema P1 that supports the xIntegrity() method. This opcode runs the xIntegrity() method for that virtual table, using P3 as the integer argument. If an error is reported back, the table name is prepended to the error message and that message is stored in P2. If no errors are seen, register P2 is set to NULL. | >
| VColumn | >Store in register P3 the value of the P2-th column of the current row of the virtual-table of cursor P1.
> If the VColumn opcode is being used to fetch the value of an unchanging column during an UPDATE operation, then the P5 value is OPFLAG_NOCHNG. This will cause the sqlite3_vtab_nochange() function to return true inside the xColumn method of the virtual table implementation. The P5 column might also contain other bits (OPFLAG_LENGTHARG or OPFLAG_TYPEOFARG) but those bits are unused by VColumn. |
>
| VCreate | >P2 is a register that holds the name of a virtual table in database P1. Call the xCreate method for that table. | >
| VDestroy | >P4 is the name of a virtual table in database P1. Call the xDestroy method of that table. | >
| VFilter | >P1 is a cursor opened using VOpen. P2 is an address to jump to if the filtered result set is empty.
> P4 is either NULL or a string that was generated by the xBestIndex method of the module. The interpretation of the P4 string is left to the module implementation. >This opcode invokes the xFilter method on the virtual table specified by P1. The integer query plan parameter to xFilter is stored in register P3. Register P3+1 stores the argc parameter to be passed to the xFilter method. Registers P3+2..P3+1+argc are the argc additional parameters which are passed to xFilter as argv. Register P3+2 becomes argv[0] when passed to xFilter. >A jump is made to P2 if the result set after filtering would be empty. |
>
| VInitIn | >Set register P2 to be a pointer to a ValueList object for cursor P1 with cache register P3 and output register P3+1. This ValueList object can be used as the first argument to sqlite3_vtab_in_first() and sqlite3_vtab_in_next() to extract all of the values stored in the P1 cursor. Register P3 is used to hold the values returned by sqlite3_vtab_in_first() and sqlite3_vtab_in_next(). | >
| VNext | >Advance virtual table P1 to the next row in its result set and jump to instruction P2. Or, if the virtual table has reached the end of its result set, then fall through to the next instruction. | >
| VOpen | >P4 is a pointer to a virtual table object, an sqlite3_vtab structure. P1 is a cursor number. This opcode opens a cursor to the virtual table and stores that cursor in P1. | >
| VRename | >P4 is a pointer to a virtual table object, an sqlite3_vtab structure. This opcode invokes the corresponding xRename method. The value in register P1 is passed as the zName argument to the xRename method. | >
| VUpdate | >P4 is a pointer to a virtual table object, an sqlite3_vtab structure. This opcode invokes the corresponding xUpdate method. P2 values are contiguous memory cells starting at P3 to pass to the xUpdate invocation. The value in register (P3+P2-1) corresponds to the p2th element of the argv array passed to xUpdate.
> The xUpdate method will do a DELETE or an INSERT or both. The argv[0] element (which corresponds to memory cell P3) is the rowid of a row to delete. If argv[0] is NULL then no deletion occurs. The argv[1] element is the rowid of the new row. This can be NULL to have the virtual table select the new rowid for itself. The subsequent elements in the array are the values of columns in the new row. >If P2==1 then no insert is performed. argv[0] is the rowid of a row to delete. >P1 is a boolean flag. If it is set to true and the xUpdate call is successful, then the value returned by sqlite3_last_insert_rowid() is set to the value of the rowid for the row just inserted. >P5 is the error actions (OE_Replace, OE_Fail, OE_Ignore, etc) to apply in the case of a constraint failure on an insert or update. |
>
| Yield | >Swap the program counter with the value in register P1. This has the effect of yielding to a coroutine.
> If the coroutine that is launched by this instruction ends with Yield or Return then continue to the next instruction. But if the coroutine launched by this instruction ends with EndCoroutine, then jump to P2 rather than continuing with the next instruction. >See also: InitCoroutine |
>
| ZeroOrNull | >If both registers P1 and P3 are NOT NULL, then store a zero in register P2. If either registers P1 or P3 are NULL then put a NULL in register P2. | >
The internal organization of the SQLite library can be viewed as the stack of modules shown to the right. The Tokenizer, Parser, and Code Generator components are used to process SQL statements and convert them into executable programs in a virtual machine language or byte code. Roughly speaking, these top three layers implement [sqlite3_prepare_v2()](c3ref/prepare.md). The byte code generated by the top three layers is a [prepared statement](c3ref/stmt.md). The Virtual Machine module is responsible for running the SQL statement byte code. The B-Tree module organizes a database file into multiple key/value stores with ordered keys and logarithmic performance. The Pager module is responsible for loading pages of the database file into memory, for implementing and controlling transactions, and for creating and maintaining the journal files that prevent database corruption following a crash or power failure. The OS Interface is a thin abstraction that provides a common set of routines for adapting SQLite to run on different operating systems. Roughly speaking, the bottom four layers implement [sqlite3_step()](c3ref/step.md).
This article is about the bottom layer.
The OS Interface - also called the "VFS" - is what makes SQLite portable across operating systems. Whenever any of the other modules in SQLite needs to communicate with the operating system, they invoke methods in the VFS. The VFS then invokes the operating-specific code needed to satisfy the request. Hence, porting SQLite to a new operating system is simply a matter of writing a new OS interface layer or "VFS".
# 3. Multiple VFSes
The standard SQLite source tree contains built-in VFSes for unix and windows. Alternative VFSes can be added at start-time or run-time using the [sqlite3_vfs_register()](c3ref/vfs_find.md) interface.
Multiple VFSes can be registered at the same time. Each VFS has a unique name. Separate [database connections](c3ref/sqlite3.md) within the same process can be using different VFSes at the same time. For that matter, if a single database connection has multiple database files open using the [ATTACH](lang_attach.md) command, then each attached database might be using a different VFS.
## 3.1. Standard Unix VFSes
Unix builds come with multiple built-in VFSes. The default VFS for unix is called "unix" and is used in most applications. Other VFSes that might be found in unix (depending on compile-time options) include:
1. **unix-dotfile** - uses dot-file locking rather than POSIX advisory locks.
2. **unix-excl** - obtains and holds an exclusive lock on database files, preventing other processes from accessing the database. Also keeps the [wal-index](walformat.md#shm) in heap rather than in shared memory.
3. **unix-none** - all file locking operations are no-ops.
4. **unix-namedsem** - uses named semaphores for file locking. VXWorks only.
The various unix VFSes differ only in the way they handle file locking - they share most of their implementation in common with one another and are all located in the same SQLite source file: [os_unix.c](https://sqlite.org/src/doc/trunk/src/os_unix.c). Note that except for "unix" and "unix-excl", the various unix VFSes all use incompatible locking implementations. If two processes are accessing the same SQLite database using different unix VFSes, they may not see each others locks and may end up interfering with one another, resulting in database corruption. The "unix-none" VFS in particular does no locking at all and will easily result in database corruption if used by two or more database connections at the same time. Programmers are encouraged to use only "unix" or "unix-excl" unless there is a compelling reason to do otherwise.
## 3.2. Standard Windows VFSes
Windows builds also come with multiple built-in VFSes. The default Windows VFS is called "win32" and is used in most applications. Other VFSes that might be found on windows builds include:
1. **win32-longpath** - like "win32" except that pathnames can be up to 65534 bytes in length, whereas pathnames max out at 1040 bytes in "win32".
2. **win32-none** - all file locking operations are no-ops.
3. **win32-longpath-none** - combination of "win32-longpath" and "win32-none" - long pathnames are supported and all lock operations are no-ops.
As with unix, most of the code for the various Windows VFSes is shared.
## 3.3. Specifying Which VFS To Use
There is always one VFS which is the default VFS. On unix systems, the "unix" VFS comes up as the default and on windows it is "win32". If no other actions are taken, new database connections will make use of the default VFS.
The default VFS can be changed by registering or re-registering the VFS using the [sqlite3_vfs_register()](c3ref/vfs_find.md) interface with a second parameter of 1. Hence, if a (unix) process wants to always use the "unix-nolock" VFS in place of "unix", the following code would work:
> \
> sqlite3_vfs_register(sqlite3_vfs_find("unix-nolock"), 1);\
An alternate VFS can also be specified as the 4th parameter to the [sqlite3_open_v2()](c3ref/open.md) function. For example:
> \
> int rc = sqlite3_open_v2("demo.db", &db, SQLITE_OPEN_READWRITE, "unix-nolock");\
Finally, if [URI filenames](uri.md) have been enabled, then the alternative VFS can be specified using the "vfs=" parameter on the URI. This technique works with [sqlite3_open()](c3ref/open.md), [sqlite3_open16()](c3ref/open.md), [sqlite3_open_v2()](c3ref/open.md), and when a new database is [ATTACH](lang_attach.md)-ed to an existing database connection. For example:
> \
> ATTACH 'file:demo2.db?vfs=unix-none' AS demo2;\
The VFS specified by a URI has the highest priority. After that comes a VFS specified as the fourth argument to [sqlite3_open_v2()](c3ref/open.md). The default VFS is used if no VFS is specified otherwise.
## 3.4. VFS Shims
From the point of view of the upper layers of the SQLite stack, each open database file uses exactly one VFS. But in practice, a particular VFS might just be a thin wrapper around another VFS that does the real work. We call a wrapper VFS a "shim".
A simple example of a shim is the "vfstrace" VFS. This is a VFS (implemented in the [vfstrace.c](https://sqlite.org/src/doc/trunk/ext/misc/vfstrace.c) source file) that writes a message associated with each VFS method call into a log file, then passes control off to another VFS to do the actual work.
## 3.5. Other Example VFSes
The following are other VFS implementations available in the public SQLite source tree:
- [appendvfs.c](https://sqlite.org/src/file/ext/misc/appendvfs.c) - This VFS allows an SQLite database to be appended to the end of some other file. This can be used, for example, to append an SQLite database onto the end of an executable such that, when run, it can easily locate the appended database. The [command-line shell](cli.md) will use this VFS if launched with the --append option, and its .archive command will use it given the --append flag.
- [test_demovfs.c](https://sqlite.org/src/doc/trunk/src/test_demovfs.c) - This file implements a very simple VFS named "demo" that uses POSIX functions such as open(), read(), write(), fsync(), close(), fsync(), sleep(), time(), and so forth. This VFS only works on unix systems. But it is not intended as a replacement for the standard "unix" VFS used by default on unix platforms. The "demo" VFS is deliberately kept very simple so that it can be used as a learning aid or as template for building other VFSes or for porting SQLite to new operating systems.
- [test_quota.c](https://sqlite.org/src/doc/trunk/src/test_quota.c) - This file implements a shim called "quota" that enforces cumulative file size limits on a collection of database files. An auxiliary interface is used to define "quota groups". A quota group is a set of files (database files, journals, and temporary files) whose names all match a [GLOB](lang_expr.md#glob) pattern. The sum of the sizes of all files in each quota group is tracked, and if that sum exceeds a threshold defined for the quota group, a callback function is invoked. That callback can either increase the threshold or cause the operation that would have exceeded the quota to fail with an [SQLITE_FULL](rescode.md#full) error. One of the uses of this shim is used to enforce resource limits on application databases in Firefox.
- [test_multiplex.c](https://sqlite.org/src/doc/trunk/src/test_multiplex.c) - This file implements a shim that allows database files to exceed the maximum file size of the underlying filesystem. This shim presents an interface to the upper six layers of SQLite that makes it look like very large files are being used, when in reality each such large file is split up into many smaller files on the underlying system. This shim has been used, for example, to allow databases to grow larger than 2 gibibytes on FAT16 filesystems.
- [test_onefile.c](https://sqlite.org/src/doc/trunk/src/test_onefile.c) - This file implements a demonstration VFS named "fs" that shows how SQLite can be used on an embedded device that lacks a filesystem. Content is written directly to the underlying media. A VFS derived from this demonstration code could be used by a gadget with a limited amount of flash memory to make SQLite behave as the filesystem for the flash memory on the device.
- [test_journal.c](https://sqlite.org/src/doc/trunk/src/test_journal.c) - This file implements a shim used during SQLite testing that verifies that the database and rollback journal are written in the correct order and are "synced" at appropriate times in order to guarantee that the database can recover from a power loss or hard reset at any time. The shim checks several invariants on the operation of databases and rollback journals and raises exceptions if any of those invariants are violated. These invariants, in turn, assure that the database is always recoverable. Running a large suite of test cases using this shim provides added assurance that SQLite databases will not be damaged by unexpected power failures or device resets.
- [test_vfs.c](https://sqlite.org/src/doc/trunk/src/test_vfs.c) - This file implements a shim that can be used to simulate filesystem faults. This shim is used during testing to verify that SQLite responds sanely to hardware malfunctions or to other error conditions such as running out of filesystem space that are difficult to test on a real system.
There are other VFS implementations both in the core SQLite source code library and in available extensions. The list above is not meant to be exhaustive but merely representative of the kinds of features that can be realized using the VFS interface.
# 4. VFS Implementations
A new VFS is implemented by subclassing three objects:
- [sqlite3_vfs](c3ref/vfs.md)
- [sqlite3_io_methods](c3ref/io_methods.md)
- [sqlite3_file](c3ref/file.md)
An [sqlite3_vfs](c3ref/vfs.md) object defines the name of the VFS and the core methods that implement the interface to the operating system, such as checking for existence of files, deleting files, creating files and opening and for reading and/or writing, converting filenames into their canonical form. The [sqlite3_vfs](c3ref/vfs.md) object also contains methods for obtaining randomness from the operating system, for suspending a process (sleeping) and for finding the current date and time.
The [sqlite3_file](c3ref/file.md) object represents an open file. The xOpen method of [sqlite3_vfs](c3ref/vfs.md) constructs an [sqlite3_file](c3ref/file.md) object when the file is opened. The [sqlite3_file](c3ref/file.md) keeps track of the state of the file while it is opened.
The [sqlite3_io_methods](c3ref/io_methods.md) object holds the methods used to interact with an open file. Each [sqlite3_file](c3ref/file.md) contains a pointer to an [sqlite3_io_methods](c3ref/io_methods.md) object that is appropriate for the file it represents. The [sqlite3_io_methods](c3ref/io_methods.md) object contains methods to do things such as read and write from the file, to truncate the file, to flush any changes to persistent storage, to find the size of the file, to lock and unlock the file, and to close file and destroy the [sqlite3_file](c3ref/file.md) object.
Writing the code for a new VFS involves constructing a subclass for the [sqlite3_vfs](c3ref/vfs.md) object and then registering that VFS object using a call to [sqlite3_vfs_register()](c3ref/vfs_find.md). The VFS implementation also provides subclasses for [sqlite3_file](c3ref/file.md) and [sqlite3_io_methods](c3ref/io_methods.md) but those objects are not registered directly with SQLite. Instead, the [sqlite3_file](c3ref/file.md) object is returned from the xOpen method of [sqlite3_vfs](c3ref/vfs.md) and the [sqlite3_file](c3ref/file.md) object points to an instance of the [sqlite3_io_methods](c3ref/io_methods.md) object.
---
# The SQLite Query Optimizer Overview
*Sección: Guides | Origen: https://www.sqlite.org/optoverview.html*
# 1. Introduction
This document provides an overview of how the query planner and optimizer for SQLite works.
Given a single SQL statement, there might be dozens, hundreds, or even thousands of ways to implement that statement, depending on the complexity of the statement itself and of the underlying database schema. The task of the query planner is to select the algorithm that minimizes disk I/O and CPU overhead.
Additional background information is available in the [indexing tutorial](queryplanner.md) document. The [Next Generation Query Planner](queryplanner-ng.md) document provides more detail on how the [join order](optoverview.md#joins) is chosen.
# 2. WHERE Clause Analysis
Prior to analysis, the following transformations are made to shift all join constraints into the WHERE clause:
- All NATURAL joins are converted into joins with a USING clause.
- All USING clauses (including ones created by the previous step) are converted into equivalent ON clauses.
- All ON clauses (include ones created by the previous step) are added as new conjuncts (AND-connected terms) in the WHERE clause.
SQLite makes no distinction between join constraints that occur in the WHERE clause and constraints in the ON clause of an inner join, since that distinction does not affect the outcome. However, there is a difference between ON clause constraints and WHERE clause constraints for outer joins. Therefore, when SQLite moves an ON clause constraint from an outer join over to the WHERE clause it adds special tags to the Abstract Syntax Tree (AST) to indicate that the constraint came from an outer join and from which outer join it came. There is no way to add those tags in pure SQL text. Hence, the SQL input must use ON clauses on outer joins. But in the internal AST, all constraints are part of the WHERE clause, because having everything in one place simplifies processing.
After all constraints have been shifted into the WHERE clause, The WHERE clause is broken up into conjuncts (hereafter called "terms"). In other words, the WHERE clause is broken up into pieces separated from the others by an AND operator. If the WHERE clause is composed of constraints separated by the OR operator (disjuncts) then the entire clause is considered to be a single "term" to which the [OR-clause optimization](#or_opt) is applied.
All terms of the WHERE clause are analyzed to see if they can be satisfied using indexes. To be usable by an index a term must usually be of one of the following forms:
> **\
> ***column*** = ***expression***\
> ***column*** IS ***expression***\
> ***column*** \> ***expression***\
> ***column*** \>= ***expression***\
> ***column*** \< ***expression***\
> ***column*** \<= ***expression***\
> ***expression*** = ***column***\
> ***expression*** IS ***column***\
> ***expression*** \> ***column***\
> ***expression*** \>= ***column***\
> ***expression*** \< ***column***\
> ***expression*** \<= ***column***\
> ***column*** IN (***expression-list***)\
> ***column*** IN (***subquery***)\
> ***column*** IS NULL\
> ***column*** LIKE ***pattern***\
> ***column*** GLOB ***pattern***\**
If an index is created using a statement like this:
CREATE INDEX idx_ex1 ON ex1(a,b,c,d,e,...,y,z);\
Then the index might be used if the initial columns of the index (columns a, b, and so forth) appear in WHERE clause terms. The initial columns of the index must be used with the **=** or **IN** or **IS** operators. The right-most column that is used can employ inequalities. For the right-most column of an index that is used, there can be up to two inequalities that must sandwich the allowed values of the column between two extremes.
It is not necessary for every column of an index to appear in a WHERE clause term in order for that index to be used. However, there cannot be gaps in the columns of the index that are used. Thus for the example index above, if there is no WHERE clause term that constrains column c, then terms that constrain columns a and b can be used with the index but not terms that constrain columns d through z. Similarly, index columns will not normally be used (for indexing purposes) if they are to the right of a column that is constrained only by inequalities. (See the [skip-scan optimization](optoverview.md#skipscan) below for the exception.)
In the case of [indexes on expressions](expridx.md), whenever the word "column" is used in the foregoing text, one can substitute "indexed expression" (meaning a copy of the expression that appears in the [CREATE INDEX](lang_createindex.md) statement) and everything will work the same.
## 2.1. Index Term Usage Examples
For the index above and WHERE clause like this:
... WHERE a=5 AND b IN (1,2,3) AND c IS NULL AND d='hello'\
The first four columns a, b, c, and d of the index would be usable since those four columns form a prefix of the index and are all bound by equality constraints.
For the index above and WHERE clause like this:
... WHERE a=5 AND b IN (1,2,3) AND c\>12 AND d='hello'\
Only columns a, b, and c of the index would be usable. The d column would not be usable because it occurs to the right of c and c is constrained only by inequalities.
For the index above and WHERE clause like this:
... WHERE a=5 AND b IN (1,2,3) AND d='hello'\
Only columns a and b of the index would be usable. The d column would not be usable because column c is not constrained and there can be no gaps in the set of columns that usable by the index.
For the index above and WHERE clause like this:
... WHERE b IN (1,2,3) AND c NOT NULL AND d='hello'\
The index is not usable at all because the left-most column of the index (column "a") is not constrained. Assuming there are no other indexes, the query above would result in a full table scan.
For the index above and WHERE clause like this:
... WHERE a=5 OR b IN (1,2,3) OR c NOT NULL OR d='hello'\
The index is not usable because the WHERE clause terms are connected by OR instead of AND. This query would result in a full table scan. However, if three additional indexes are added that contain columns b, c, and d as their left-most columns, then the [OR-clause optimization](#or_opt) might apply.
# 3. The BETWEEN Optimization
If a term of the WHERE clause is of the following form:
> **\
> ***expr1*** BETWEEN ***expr2*** AND ***expr3***\**
Then two "virtual" terms are added as follows:
> **\
> ***expr1*** \>= ***expr2*** AND ***expr1*** \<= ***expr3***\**
Virtual terms are used for analysis only and do not cause any byte-code to be generated. If both virtual terms end up being used as constraints on an index, then the original BETWEEN term is omitted and the corresponding test is not performed on input rows. Thus if the BETWEEN term ends up being used as an index constraint no tests are ever performed on that term. On the other hand, the virtual terms themselves never causes tests to be performed on input rows. Thus if the BETWEEN term is not used as an index constraint and instead must be used to test input rows, the *expr1* expression is only evaluated once.
# 4. OR Optimizations
WHERE clause constraints that are connected by OR instead of AND can be handled in two different ways.
## 4.1. Converting OR-connected constraint into an IN operator
If a term consists of multiple subterms containing a common column name and separated by OR, like this:
> **\
> ***column*** = ***expr1*** OR ***column*** = ***expr2*** OR ***column*** = ***expr3*** OR ...\**
Then that term is rewritten as follows:
> **\
> ***column*** IN (***expr1***,***expr2***,***expr3***,...)\**
The rewritten term then might go on to constrain an index using the normal rules for **IN** operators. Note that *column* must be the same column in every OR-connected subterm, although the column can occur on either the left or the right side of the **=** operator.
## 4.2. Evaluating OR constraints separately and taking the UNION of the result
If and only if the previously described conversion of OR to an IN operator does not work, the second OR-clause optimization is attempted. Suppose the OR clause consists of multiple subterms as follows:
> **\
> ***expr1*** OR ***expr2*** OR ***expr3***\**
Individual subterms might be a single comparison expression like **a=5** or **x\>y** or they can be LIKE or BETWEEN expressions, or a subterm can be a parenthesized list of AND-connected sub-subterms. Each subterm is analyzed as if it were itself the entire WHERE clause in order to see if the subterm is indexable by itself. If every subterm of an OR clause is separately indexable then the OR clause might be coded such that a separate index is used to evaluate each term of the OR clause. One way to think about how SQLite uses separate indexes for each OR clause term is to imagine that the WHERE clause where rewritten as follows:
> **\
> rowid IN (SELECT rowid FROM ***table*** WHERE ***expr1***\
> UNION SELECT rowid FROM ***table*** WHERE ***expr2***\
> UNION SELECT rowid FROM ***table*** WHERE ***expr3***)\**
The rewritten expression above is conceptual; WHERE clauses containing OR are not really rewritten this way. The actual implementation of the OR clause uses a mechanism that is more efficient and that works even for [WITHOUT ROWID](withoutrowid.md) tables or tables in which the "rowid" is inaccessible. Nevertheless, the essence of the implementation is captured by the statement above: Separate indexes are used to find candidate result rows from each OR clause term and the final result is the union of those rows.
Note that in most cases, SQLite will only use a single index for each table in the FROM clause of a query. The second OR-clause optimization described here is the exception to that rule. With an OR-clause, a different index might be used for each subterm in the OR-clause.
For any given query, the fact that the OR-clause optimization described here can be used does not guarantee that it will be used. SQLite uses a cost-based query planner that estimates the CPU and disk I/O costs of various competing query plans and chooses the plan that it thinks will be the fastest. If there are many OR terms in the WHERE clause or if some of the indexes on individual OR-clause subterms are not very selective, then SQLite might decide that it is faster to use a different query algorithm, or even a full-table scan. Application developers can use the [EXPLAIN QUERY PLAN](lang_explain.md) prefix on a statement to get a high-level overview of the chosen query strategy.
# 5. The LIKE Optimization
A WHERE-clause term that uses the [LIKE](lang_expr.md#like) or [GLOB](lang_expr.md#glob) operator can sometimes be used with an index to do a range search, almost as if the LIKE or GLOB were an alternative to a [BETWEEN](lang_expr.md#between) operator. There are many conditions on this optimization:
1. The right-hand side of the LIKE or GLOB must be either a string literal or a [parameter](lang_expr.md#varparam) bound to a string literal that does not begin with a wildcard character.
2. It must not be possible to make the LIKE or GLOB operator true by having a numeric value (instead of a string or blob) on the left-hand side. This means that either:
1. the left-hand side of the LIKE or GLOB operator is the name of an indexed column with [TEXT affinity](datatype3.md#affinity), or
2. the right-hand side pattern argument does not begin with a minus sign ("-") or a digit.
This constraint arises from the fact that numbers do not sort in lexicographical order. For example: 9\<10 but '9'\>'10'.
3. The built-in functions used to implement LIKE and GLOB must not have been overloaded using the [sqlite3_create_function()](c3ref/create_function.md) API.
4. For the GLOB operator, the column must be indexed using the built-in BINARY collating sequence.
5. For the LIKE operator, if [case_sensitive_like](pragma.md#pragma_case_sensitive_like) mode is enabled then the column must be indexed using the built-in BINARY collating sequence, or if [case_sensitive_like](pragma.md#pragma_case_sensitive_like) mode is disabled then the column must be indexed using the built-in NOCASE collating sequence.
6. If the ESCAPE option is used, the ESCAPE character must be ASCII, or a single-byte character in UTF-8.
The LIKE operator has two modes that can be set by a [pragma](pragma.md#pragma_case_sensitive_like). The default mode is for LIKE comparisons to be insensitive to differences of case for latin1 characters. Thus, by default, the following expression is true:
'a' LIKE 'A'\
If the case_sensitive_like pragma is enabled as follows:
PRAGMA case_sensitive_like=ON;\
Then the LIKE operator pays attention to case and the example above would evaluate to false. Note that case insensitivity only applies to latin1 characters - basically the upper and lower case letters of English in the lower 127 byte codes of ASCII. International character sets are case sensitive in SQLite unless an application-defined [collating sequence](datatype3.md#collation) and [like() SQL function](lang_corefunc.md#like) are provided that take non-ASCII characters into account. If an application-defined collating sequence and/or like() SQL function are provided, the LIKE optimization described here will never be taken.
The LIKE operator is case insensitive by default because this is what the SQL standard requires. You can change the default behavior at compile time by using the [SQLITE_CASE_SENSITIVE_LIKE](compile.md#case_sensitive_like) command-line option to the compiler.
The LIKE optimization might occur if the column named on the left of the operator is indexed using the built-in BINARY collating sequence and case_sensitive_like is turned on. Or the optimization might occur if the column is indexed using the built-in NOCASE collating sequence and the case_sensitive_like mode is off. These are the only two combinations under which LIKE operators will be optimized.
The GLOB operator is always case sensitive. The column on the left side of the GLOB operator must always use the built-in BINARY collating sequence or no attempt will be made to optimize that operator with indexes.
The LIKE optimization will only be attempted if the right-hand side of the GLOB or LIKE operator is either a literal string or a [parameter](lang_expr.md#varparam) that has been [bound](c3ref/bind_blob.md) to a string literal. The string literal must not begin with a wildcard; if the right-hand side begins with a wildcard character then this optimization is not attempted. If the right-hand side is a [parameter](lang_expr.md#varparam) that is bound to a string, then this optimization is only attempted if the [prepared statement](c3ref/stmt.md) containing the expression was compiled with [sqlite3_prepare_v2()](c3ref/prepare.md) or [sqlite3_prepare16_v2()](c3ref/prepare.md). The LIKE optimization is not attempted if the right-hand side is a [parameter](lang_expr.md#varparam) and the statement was prepared using [sqlite3_prepare()](c3ref/prepare.md) or [sqlite3_prepare16()](c3ref/prepare.md).
Suppose the initial sequence of non-wildcard characters on the right-hand side of the LIKE or GLOB operator is *x*. We are using a single character to denote this non-wildcard prefix but the reader should understand that the prefix can consist of more than 1 character. Let *y* be the smallest string that is the same length as /x/ but which compares greater than *x*. For example, if *x* is `'hello'` then *y* would be `'hellp'`. The LIKE and GLOB optimizations consist of adding two virtual terms like this:
> **\
> ***column*** \>= ***x*** AND ***column*** \< ***y***\**
Under most circumstances, the original LIKE or GLOB operator is still tested against each input row even if the virtual terms are used to constrain an index. This is because we do not know what additional constraints may be imposed by characters to the right of the *x* prefix. However, if there is only a single global wildcard to the right of *x*, then the original LIKE or GLOB test is disabled. In other words, if the pattern is like this:
> **\
> ***column*** LIKE ***x***%\
> ***column*** GLOB ***x***\*\**
then the original LIKE or GLOB tests are disabled when the virtual terms constrain an index because in that case we know that all of the rows selected by the index will pass the LIKE or GLOB test.
Note that when the right-hand side of a LIKE or GLOB operator is a [parameter](lang_expr.md#varparam) and the statement is prepared using [sqlite3_prepare_v2()](c3ref/prepare.md) or [sqlite3_prepare16_v2()](c3ref/prepare.md) then the statement is automatically reparsed and recompiled on the first [sqlite3_step()](c3ref/step.md) call of each run if the binding to the right-hand side parameter has changed since the previous run. This reparse and recompile is essentially the same action that occurs following a schema change. The recompile is necessary so that the query planner can examine the new value bound to the right-hand side of the LIKE or GLOB operator and determine whether or not to employ the optimization described above.
# 6. The Skip-Scan Optimization
The general rule is that indexes are only useful if there are WHERE-clause constraints on the left-most columns of the index. However, in some cases, SQLite is able to use an index even if the first few columns of the index are omitted from the WHERE clause but later columns are included.
Consider a table such as the following:
CREATE TABLE people(\
name TEXT PRIMARY KEY,\
role TEXT NOT NULL,\
height INT NOT NULL, -- in cm\
CHECK( role IN ('student','teacher') )\
);\
CREATE INDEX people_idx1 ON people(role, height);\
The people table has one entry for each person in a large organization. Each person is either a "student" or a "teacher", as determined by the "role" field. The table also records the height in centimeters of each person. The role and height are indexed. Notice that the left-most column of the index is not very selective - it only contains two possible values.
Now consider a query to find the names of everyone in the organization that is 180cm tall or taller:
SELECT name FROM people WHERE height\>=180;\
Because the left-most column of the index does not appear in the WHERE clause of the query, one is tempted to conclude that the index is not usable here. However, SQLite is able to use the index. Conceptually, SQLite uses the index as if the query were more like the following:
SELECT name FROM people\
WHERE role IN (SELECT DISTINCT role FROM people)\
AND height\>=180;\
Or this:
SELECT name FROM people WHERE role='teacher' AND height\>=180\
UNION ALL\
SELECT name FROM people WHERE role='student' AND height\>=180;\
The alternative query formulations shown above are conceptual only. SQLite does not really transform the query. The actual query plan is like this: SQLite locates the first possible value for "role", which it can do by rewinding the "people_idx1" index to the beginning and reading the first record. SQLite stores this first "role" value in an internal variable that we will here call "\$role". Then SQLite runs a query like: "SELECT name FROM people WHERE role=\$role AND height\>=180". This query has an equality constraint on the left-most column of the index and so the index can be used to resolve that query. Once that query is finished, SQLite then uses the "people_idx1" index to locate the next value of the "role" column, using code that is logically similar to "SELECT role FROM people WHERE role\>\$role LIMIT 1". This new "role" value overwrites the \$role variable, and the process repeats until all possible values for "role" have been examined.
We call this kind of index usage a "skip-scan" because the database engine is basically doing a full scan of the index but it optimizes the scan (making it less than "full") by occasionally skipping ahead to the next candidate value.
SQLite might use a skip-scan on an index if it knows that the first one or more columns contain many duplication values. If there are too few duplicates in the left-most columns of the index, then it would be faster to simply step ahead to the next value, and thus do a full table scan, than to do a binary search on an index to locate the next left-column value.
The only way that SQLite can know that there are many duplicates in the left-most columns of an index is if the [ANALYZE](lang_analyze.md) command has been run on the database. Without the results of ANALYZE, SQLite has to guess at the "shape" of the data in the table, and the default guess is that there are an average of 10 duplicates for every value in the left-most column of the index. Skip-scan only becomes profitable (it only gets to be faster than a full table scan) when the number of duplicates is about 18 or more. Hence, a skip-scan is never used on a database that has not been analyzed.
# 7. Joins
SQLite implements joins as nested loops. The default order of the nested loops in a join is for the left-most table in the FROM clause to form the outer loop and the right-most table to form the inner loop. However, SQLite will nest the loops in a different order if doing so will help it to select better indexes.
Inner joins can be freely reordered. However outer joins are neither commutative nor associative and hence will not be reordered. Inner joins to the left and right of an outer join might be reordered if the optimizer thinks that is advantageous but outer joins are always evaluated in the order in which they occur.
SQLite [treats the CROSS JOIN operator specially](lang_select.md#crossjoin). The CROSS JOIN operator is commutative, in theory. However, SQLite chooses to never reorder tables in a CROSS JOIN. This provides a mechanism by which the programmer can force SQLite to choose a particular loop nesting order.
When selecting the order of tables in a join, SQLite uses an efficient polynomial-time algorithm graph algorithm described in the [Next Generation Query Planner](queryplanner-ng.md) document. Because of this, SQLite is able to plan queries with 50- or 60-way joins in a matter of microseconds
Join reordering is automatic and usually works well enough that programmers do not have to think about it, especially if [ANALYZE](lang_analyze.md) has been used to gather statistics about the available indexes, though occasionally some hints from the programmer are needed. Consider, for example, the following schema:
CREATE TABLE node(\
id INTEGER PRIMARY KEY,\
name TEXT\
);\
CREATE INDEX node_idx ON node(name);\
CREATE TABLE edge(\
orig INTEGER REFERENCES node,\
dest INTEGER REFERENCES node,\
PRIMARY KEY(orig, dest)\
);\
CREATE INDEX edge_idx ON edge(dest,orig);\
The schema above defines a directed graph with the ability to store a name at each node. Now consider a query against this schema:
SELECT \*\
FROM edge AS e,\
node AS n1,\
node AS n2\
WHERE n1.name = 'alice'\
AND n2.name = 'bob'\
AND e.orig = n1.id\
AND e.dest = n2.id;\
This query asks for is all information about edges that go from nodes labeled "alice" to nodes labeled "bob". The query optimizer in SQLite has basically two choices on how to implement this query. (There are actually six different choices, but we will only consider two of them here.) Pseudocode below demonstrating these two choices.
Option 1:
foreach n1 where n1.name='alice' do:\
foreach n2 where n2.name='bob' do:\
foreach e where e.orig=n1.id and e.dest=n2.id\
return n1.\*, n2.\*, e.\*\
end\
end\
end\
Option 2:
foreach n1 where n1.name='alice' do:\
foreach e where e.orig=n1.id do:\
foreach n2 where n2.id=e.dest and n2.name='bob' do:\
return n1.\*, n2.\*, e.\*\
end\
end\
end\
The same indexes are used to speed up every loop in both implementation options. The only difference in these two query plans is the order in which the loops are nested.
So which query plan is better? It turns out that the answer depends on what kind of data is found in the node and edge tables.
Let the number of alice nodes be M and the number of bob nodes be N. Consider two scenarios. In the first scenario, M and N are both 2 but there are thousands of edges on each node. In this case, option 1 is preferred. With option 1, the inner loop checks for the existence of an edge between a pair of nodes and outputs the result if found. Because there are only 2 alice and bob nodes each, the inner loop only has to run four times and the query is very quick. Option 2 would take much longer here. The outer loop of option 2 only executes twice, but because there are a large number of edges leaving each alice node, the middle loop has to iterate many thousands of times. It will be much slower. So in the first scenario, we prefer to use option 1.
Now consider the case where M and N are both 3500. Alice nodes are abundant. This time suppose each of these nodes is connected by only one or two edges. Now option 2 is preferred. With option 2, the outer loop still has to run 3500 times, but the middle loop only runs once or twice for each outer loop and the inner loop will only run once for each middle loop, if at all. So the total number of iterations of the inner loop is around 7000. Option 1, on the other hand, has to run both its outer loop and its middle loop 3500 times each, resulting in 12 million iterations of the middle loop. Thus in the second scenario, option 2 is nearly 2000 times faster than option 1.
So you can see that depending on how the data is structured in the table, either query plan 1 or query plan 2 might be better. Which plan does SQLite choose by default? As of version 3.6.18, without running [ANALYZE](lang_analyze.md), SQLite will choose option 2. If the [ANALYZE](lang_analyze.md) command is run in order to gather statistics, a different choice might be made if the statistics indicate that the alternative is likely to run faster.
## 7.1. Manual Control Of Join Order
SQLite almost always picks the best join order automatically. It is very rare that a developer needs to intervene to give the query planner hints about the best join order. The best policy is to make use of [PRAGMA optimize](pragma.md#pragma_optimize) to ensure that the query planner has access to up-to-date statistics on the shape of the data in the database.
This section describes techniques by which developers can control the join order in SQLite, to work around any performance problems that may arise. However, the use of these techniques is not recommended, except as a last resort.
If you do encounter a situation where SQLite is picking a suboptimal join order even after running [PRAGMA optimize](pragma.md#pragma_optimize), please report your situation on the [SQLite Community Forum](https://sqlite.org/forum) so that the SQLite maintainers can make new refinements to the query planner such that manual intervention is not required.
### 7.1.1. Manual Control Of Query Plans Using SQLITE_STAT Tables
SQLite provides the ability for advanced programmers to exercise control over the query plan chosen by the optimizer. One method for doing this is to fudge the [ANALYZE](lang_analyze.md) results in the [sqlite_stat1](fileformat2.md#stat1tab) table.
### 7.1.2. Manual Control of Query Plans using CROSS JOIN
Programmers can force SQLite to use a particular loop nesting order for a join by using the CROSS JOIN operator instead of just JOIN, INNER JOIN, NATURAL JOIN, or a "," join. Though CROSS JOINs are commutative in theory, SQLite chooses to never reorder the tables in a CROSS JOIN. Hence, the left table of a CROSS JOIN will always be in an outer loop relative to the right table.
In the following query, the optimizer is free to reorder the tables of FROM clause any way it sees fit:
SELECT \*\
FROM node AS n1,\
edge AS e,\
node AS n2\
WHERE n1.name = 'alice'\
AND n2.name = 'bob'\
AND e.orig = n1.id\
AND e.dest = n2.id;\
In the following logically equivalent formulation of the same query, the substitution of "CROSS JOIN" for the "," means that the order of tables must be N1, E, N2.
SELECT \*\
FROM node AS n1 CROSS JOIN\
edge AS e CROSS JOIN\
node AS n2\
WHERE n1.name = 'alice'\
AND n2.name = 'bob'\
AND e.orig = n1.id\
AND e.dest = n2.id;\
In the latter query, the query plan must be [option 2](#option2). Note that you must use the keyword "CROSS" in order to disable the table reordering optimization; INNER JOIN, NATURAL JOIN, JOIN, and other similar combinations work just like a comma join in that the optimizer is free to reorder tables as it sees fit. (Table reordering is also disabled on an outer join, but that is because outer joins are not associative or commutative. Reordering tables in OUTER JOIN changes the result.)
See "[The Fossil NGQP Upgrade Case Study](queryplanner-ng.md#fossilcasestudy)" for another real-world example of using CROSS JOIN to manually control the nesting order of a join. The [query planner checklist](queryplanner-ng.md#howtofix) found later in the same document provides further guidance on manual control of the query planner.
# 8. Choosing Between Multiple Indexes
Each table in the FROM clause of a query can use at most one index (except when the [OR-clause optimization](#or_opt) comes into play) and SQLite strives to use at least one index on each table. Sometimes, two or more indexes might be candidates for use on a single table. For example:
CREATE TABLE ex2(x,y,z);\
CREATE INDEX ex2i1 ON ex2(x);\
CREATE INDEX ex2i2 ON ex2(y);\
SELECT z FROM ex2 WHERE x=5 AND y=6;\
For the SELECT statement above, the optimizer can use the ex2i1 index to lookup rows of ex2 that contain x=5 and then test each row against the y=6 term. Or it can use the ex2i2 index to lookup rows of ex2 that contain y=6 then test each of those rows against the x=5 term.
When faced with a choice of two or more indexes, SQLite tries to estimate the total amount of work needed to perform the query using each option. It then selects the option that gives the least estimated work.
To help the optimizer get a more accurate estimate of the work involved in using various indexes, the user may optionally run the [ANALYZE](lang_analyze.md) command. The [ANALYZE](lang_analyze.md) command scans all indexes of database where there might be a choice between two or more indexes and gathers statistics on the selectiveness of those indexes. The statistics gathered by this scan are stored in special database tables names shows names all begin with "**sqlite_stat**". The content of these tables is not updated as the database changes so after making significant changes it might be prudent to rerun [ANALYZE](lang_analyze.md). The results of an ANALYZE command are only available to database connections that are opened after the ANALYZE command completes.
The various **sqlite_stat***N* tables contain information on how selective the various indexes are. For example, the [sqlite_stat1](fileformat2.md#stat1tab) table might indicate that an equality constraint on column x reduces the search space to 10 rows on average, whereas an equality constraint on column y reduces the search space to 3 rows on average. In that case, SQLite would prefer to use index ex2i2 since that index is more selective.
## 8.1. Disqualifying WHERE Clause Terms using Unary-"+"
*Note: Disqualifying WHERE clause terms this way is not recommended. This is a work-around. Only do this as a last resort to get the performance you need. If you find a situation where this work-around is necessary, please report the situation on the [SQLite Community Forum](https://sqlite.org/forum) so that the SQLite maintainers can try to improve the query planner such that the work-around is no longer required for your situation.*
Terms of the WHERE clause can be manually disqualified for use with indexes by prepending a unary **+** operator to the column name. The unary **+** is a no-op and will not generate any byte code in the prepared statement. However, the unary **+** operator will prevent the term from constraining an index. So, in the example above, if the query were rewritten as:
SELECT z FROM ex2 WHERE +x=5 AND y=6;\
The **+** operator on the **x** column will prevent that term from constraining an index. This would force the use of the ex2i2 index.
Note that the unary **+** operator also removes [type affinity](datatype3.md#affinity) from an expression, and in some cases this can cause subtle changes in the meaning of an expression. In the example above, if column **x** has [TEXT affinity](datatype3.md#affinity) then the comparison "x=5" will be done as text. The **+** operator removes the affinity. So the comparison "**+x=5**" will compare the text in column **x** with the numeric value 5 and will always be false.
## 8.2. Range Queries
Consider a slightly different scenario:
CREATE TABLE ex2(x,y,z);\
CREATE INDEX ex2i1 ON ex2(x);\
CREATE INDEX ex2i2 ON ex2(y);\
SELECT z FROM ex2 WHERE x BETWEEN 1 AND 100 AND y BETWEEN 1 AND 100;\
Further suppose that column x contains values spread out between 0 and 1,000,000 and column y contains values that span between 0 and 1,000. In that scenario, the range constraint on column x should reduce the search space by a factor of 10,000 whereas the range constraint on column y should reduce the search space by a factor of only 10. So the ex2i1 index should be preferred.
SQLite will make this determination, but only if it has been compiled with [SQLITE_ENABLE_STAT3](compile.md#enable_stat3) or [SQLITE_ENABLE_STAT4](compile.md#enable_stat4). The [SQLITE_ENABLE_STAT3](compile.md#enable_stat3) and [SQLITE_ENABLE_STAT4](compile.md#enable_stat4) options causes the [ANALYZE](lang_analyze.md) command to collect a histogram of column content in the [sqlite_stat3](fileformat2.md#stat3tab) or [sqlite_stat4](fileformat2.md#stat4tab) tables and to use this histogram to make a better guess at the best query to use for range constraints such as the above. The main difference between STAT3 and STAT4 is that STAT3 records histogram data for only the left-most column of an index whereas STAT4 records histogram data for all columns of an index. For single-column indexes, STAT3 and STAT4 work the same.
The histogram data is only useful if the right-hand side of the constraint is a simple compile-time constant or [parameter](lang_expr.md#varparam) and not an expression.
Another limitation of the histogram data is that it only applies to the left-most column on an index. Consider this scenario:
CREATE TABLE ex3(w,x,y,z);\
CREATE INDEX ex3i1 ON ex2(w, x);\
CREATE INDEX ex3i2 ON ex2(w, y);\
SELECT z FROM ex3 WHERE w=5 AND x BETWEEN 1 AND 100 AND y BETWEEN 1 AND 100;\
Here the inequalities are on columns x and y which are not the left-most index columns. Hence, the histogram data is useless in helping to choose between the range constraints on columns x and y.
# 9. Covering Indexes
When doing an indexed lookup of a row, the usual procedure is to do a binary search on the index to find the index entry, then extract the [rowid](lang_createtable.md#rowid) from the index and use that [rowid](lang_createtable.md#rowid) to do a binary search on the original table. Thus a typical indexed lookup involves two binary searches. If, however, all columns that were to be fetched from the table are already available in the index itself, SQLite will use the values contained in the index and will never look up the original table row. This saves one binary search for each row and can make many queries run twice as fast.
When an index contains all of the data needed for a query and when the original table never needs to be consulted, we call that index a "covering index".
# 10. ORDER BY Optimizations
SQLite attempts to use an index to satisfy the ORDER BY clause of a query when possible. When faced with the choice of using an index to satisfy WHERE clause constraints or satisfying an ORDER BY clause, SQLite does the same cost analysis described above and chooses the index that it believes will result in the fastest answer.
SQLite will also attempt to use indexes to help satisfy GROUP BY clauses and the DISTINCT keyword. If the nested loops of the join can be arranged such that rows that are equivalent for the GROUP BY or for the DISTINCT are consecutive, then the GROUP BY or DISTINCT logic can determine if the current row is part of the same group or if the current row is distinct simply by comparing the current row to the previous row. This can be much faster than the alternative of comparing each row to all prior rows.
## 10.1. Partial ORDER BY via Index
If a query contains an ORDER BY clause with multiple terms, it might be that SQLite can use indexes to cause rows to come out in the order of some prefix of the terms in the ORDER BY but that later terms in the ORDER BY are not satisfied. In that case, SQLite does block sorting. Suppose the ORDER BY clause has four terms and the natural order of the query results in rows appearing in order of the first two terms. As each row is output by the query engine and enters the sorter, the outputs in the current row corresponding to the first two terms of the ORDER BY are compared against the previous row. If they have changed, the current sort is finished and output and a new sort is started. This results in a slightly faster sort. Even bigger advantages are that many fewer rows need to be held in memory, reducing memory requirements, and outputs can begin to appear before the core query has run to completion.
# 11. Subquery Flattening
When a subquery occurs in the FROM clause of a SELECT, the simplest behavior is to evaluate the subquery into a transient table, then run the outer SELECT against the transient table. Such a plan can be suboptimal since the transient table will not have any indexes and the outer query (which is likely a join) will be forced to either do a full table scan on the transient table or else construct a [query-time index](optoverview.md#autoindex) on the transient table, neither of which is is particularly fast.
To overcome this problem, SQLite attempts to flatten subqueries in the FROM clause of a SELECT. This involves inserting the FROM clause of the subquery into the FROM clause of the outer query and rewriting expressions in the outer query that refer to the result set of the subquery. For example:
SELECT t1.a, t2.b FROM t2, (SELECT x+y AS a FROM t1 WHERE z\<100) WHERE a\>5\
Would be rewritten using query flattening as:
SELECT t1.x+t1.y AS a, t2.b FROM t2, t1 WHERE z\<100 AND a\>5\
There is a long list of conditions that must all be met in order for query flattening to occur. Some of the constraints are marked as obsolete by italic text. These extra constraints are retained in the documentation to preserve the numbering of the other constraints.
Casual readers are not expected to understand all of these rules. The point here is that flattening rules are subtle and complex. There have been multiple bugs over the years caused by over-aggressive query flattening. On the other hand, performance of complex queries and/or queries involving views tends to suffer if query flattening is more conservative.
1. *(Obsolete)*
2. *(Obsolete)*
3. If the subquery is the right operand of a LEFT JOIN then
1. the subquery may not be a join, and
2. the FROM clause of the subquery may not contain a virtual table, and
3. the outer query may not be DISTINCT.
4. The subquery is not DISTINCT.
5. *(Obsolete - subsumed into constraint 4)*
6. *(Obsolete)*
7. The subquery has a FROM clause.
8. The subquery does not use LIMIT or the outer query is not a join.
9. The subquery does not use LIMIT or the outer query does not use aggregates.
10. *(Obsolete)*
11. The subquery and the outer query do not both have ORDER BY clauses.
12. *(Obsolete - subsumed into constraint 3)*
13. The subquery and outer query do not both use LIMIT.
14. The subquery does not use OFFSET.
15. If the outer query is part of a compound select, then the subquery may not have a LIMIT clause.
16. If the outer query is an aggregate, then the subquery may not contain ORDER BY.
17. If the sub-query is a compound SELECT, then
1. all compound operators must be UNION ALL, and
2. no terms with the subquery compound may be aggregate or DISTINCT, and
3. every term within the subquery must have a FROM clause, and
4. the outer query may not be an aggregateor DISTINCT query.
5. the subquery may not contain window functions.
6. the subquery must not be the right-hand side of a LEFT JOIN.
7. either the subquery is the first element of the outer query or there are not RIGHT or FULL JOINs in any arm of the subquery.
8. the corresponding result set expressions in all arms of the compound subquery must have the same [affinity](datatype3.md#affinity).
The parent and sub-query may contain WHERE clauses. Subject to rules (11), (12) and (13), they may also contain ORDER BY, LIMIT and OFFSET clauses.
18. If the sub-query is a compound select, then all terms of the ORDER by clause of the parent must be simple references to columns of the sub-query.
19. If the subquery uses LIMIT then the outer query may not have a WHERE clause.
20. If the sub-query is a compound select, then it must not use an ORDER BY clause.
21. If the subquery uses LIMIT, then the outer query may not be DISTINCT.
22. The subquery may not be a recursive CTE.
23. If the outer query is a recursive CTE, then the sub-query may not be a compound query.
24. *(Obsolete)*
25. Neither the subquery nor the outer query may contain a [window function](windowfunctions.md) in the result set nor the ORDER BY clause.
26. The subquery may not be the right operand of a RIGHT or FULL OUTER JOIN.
27. The subquery may not contain a FULL or RIGHT JOIN unless it is the first element of the parent query. Two subcases:
1. the subquery is not a compound query.
2. the subquery is a compound query and the RIGHT JOIN occurs in any arm of the compound query. (See also (17g)).
28. The subquery is not a MATERIALIZED CTE.
Query flattening is an important optimization when views are used as each use of a view is translated into a subquery.
# 12. Subquery Co-routines
SQLite implements FROM-clause subqueries in one of three ways:
1. [Flatten](optoverview.md#flattening) the subquery into its outer query
2. Evaluate the subquery into a transient table that exists for the duration of the one SQL statement that is being evaluated, then run the outer query against that transient table.
3. Evaluate the subquery in a co-routine that runs in parallel with the outer query, providing rows to the outer query as needed.
This section describes the third technique: implementing the subquery as a co-routine.
A co-routine is like a subroutine in that it runs in the same thread as the caller and eventually returns control back to the caller. The difference is that a co-routine also has the ability to return before it has finished, and then resume where it left off the next time it is called.
When a subquery is implemented as a co-routine, byte-code is generated to implement the subquery as if it were a standalone query, except instead of returning rows of results back to the application, the co-routine yields control back to the caller after each row is computed. The caller can then use that one computed row as part of its computation, then invoke the co-routine again when it is ready for the next row.
Co-routines are better than storing the complete result set of the subquery in a transient table because co-routines use less memory. With a co-routine, only a single row of the result needs to be remembered, whereas all rows of the result must be stored for a transient table. Also, because the co-routine does not need to run to completion before the outer query begins its work, the first rows of output can appear much sooner, and if the overall query is abandoned before it has finished, less work is done overall.
On the other hand, if the result of the subquery must be scanned multiple times (because, for example, it is just one table in a join) then it is better to use a transient table to remember the entire result of the subquery, in order to avoid computing the subquery more than once.
## 12.1. Using Co-routines to Defer Work until after the Sorting
As of SQLite version 3.21.0 (2017-10-24), the query planner will always prefer to use a co-routine to implement FROM-clause subqueries that contains an ORDER BY clause and that are not part of a join when the result set of the outer query is "complex". This feature allows applications to shift expensive computations from before the sorter until after the sorter, which can result in faster operation. For example, consider this query:
SELECT expensive_function(a) FROM tab ORDER BY date DESC LIMIT 5;\
The goal of this query is to compute some value for the five most recent entries in the table. In the query above, the "expensive_function()" is invoked prior to the sort and thus is invoked on every row of the table, even rows that are ultimately omitted due to the LIMIT clause. A co-routine can be used to work around this:
SELECT expensive_function(a) FROM (\
SELECT a FROM tab ORDER BY date DESC LIMIT 5\
);\
In the revised query, the subquery implemented by a co-routine computes the five most recent values for "a". Those five values are passed from the co-routine up into the outer query where the "expensive_function()" is invoked on only the specific rows that the application cares about.
The query planner in future versions of SQLite might grow smart enough to make transformations such as the above automatically, in both directions. That is to say, future versions of SQLite might transform queries of the first form into the second, or queries written the second way into the first. As of SQLite version 3.22.0 (2018-01-22), the query planner will flatten the subquery if the outer query does not make use of any user-defined functions or subqueries in its result set. For the examples shown above, however, SQLite implements each of the queries as written.
# 13. The MIN/MAX Optimization
Queries that contain a single MIN() or MAX() aggregate function whose argument is the left-most column of an index might be satisfied by doing a single index lookup rather than by scanning the entire table. Examples:
SELECT MIN(x) FROM table;\
SELECT MAX(x)+1 FROM table;\
# 14. Automatic Query-Time Indexes
When no indexes are available to aid the evaluation of a query, SQLite might create an automatic index that lasts only for the duration of a single SQL statement. Automatic indexes are also sometimes called "Query-time indexes". Since the cost of constructing the automatic or query-time index is O(NlogN) (where N is the number of entries in the table) and the cost of doing a full table scan is only O(N), an automatic index will only be created if SQLite expects that the lookup will be run more than logN times during the course of the SQL statement. Consider an example:
CREATE TABLE t1(a,b);\
CREATE TABLE t2(c,d);\
-- Insert many rows into both t1 and t2\
SELECT \* FROM t1, t2 WHERE a=c;\
In the query above, if both t1 and t2 have approximately N rows, then without any indexes the query will require O(N\*N) time. On the other hand, creating an index on table t2 requires O(NlogN) time and using that index to evaluate the query requires an additional O(NlogN) time. In the absence of [ANALYZE](lang_analyze.md) information, SQLite guesses that N is one million and hence it believes that constructing the automatic index will be the cheaper approach.
An automatic query-time index might also be used for a subquery:
CREATE TABLE t1(a,b);\
CREATE TABLE t2(c,d);\
-- Insert many rows into both t1 and t2\
SELECT a, (SELECT d FROM t2 WHERE c=b) FROM t1;\
In this example, the t2 table is used in a subquery to translate values of the t1.b column. If each table contains N rows, SQLite expects that the subquery will run N times, and hence it will believe it is faster to construct an automatic, transient index on t2 first and then use that index to satisfy the N instances of the subquery.
The automatic indexing capability can be disabled at run-time using the [automatic_index pragma](pragma.md#pragma_automatic_index). Automatic indexing is turned on by default, but this can be changed so that automatic indexing is off by default using the [SQLITE_DEFAULT_AUTOMATIC_INDEX](compile.md#default_automatic_index) compile-time option. The ability to create automatic indexes can be completely disabled by compiling with the [SQLITE_OMIT_AUTOMATIC_INDEX](compile.md#omit_automatic_index) compile-time option.
In SQLite [version 3.8.0](releaselog/3_8_0.md) (2013-08-26) and later, an [SQLITE_WARNING_AUTOINDEX](rescode.md#warning_autoindex) message is sent to the [error log](errlog.md) every time a statement is prepared that uses an automatic index. Application developers can and should use these warnings to identify the need for new persistent indexes in the schema.
Do not confuse automatic indexes with the [internal indexes](fileformat2.md#intschema) (having names like "sqlite_autoindex\_*table*\_*N*") that are sometimes created to implement a [PRIMARY KEY constraint](lang_createtable.md#primkeyconst) or [UNIQUE constraint](lang_createtable.md#uniqueconst). The automatic indexes described here exist only for the duration of a single query, are never persisted to disk, and are only visible to a single database connection. Internal indexes are part of the implementation of PRIMARY KEY and UNIQUE constraints, are long-lasting and persisted to disk, and are visible to all database connections. The term "autoindex" appears in the names of [internal indexes](fileformat2.md#intschema) for legacy reasons and does not indicate that internal indexes and automatic indexes are related.
## 14.1. Hash Joins
An automatic index is almost the same thing as a [hash join](https://en.wikipedia.org/wiki/Hash_join). The only difference is that a B-Tree is used instead of a hash table. If you are willing to say that the transient B-Tree constructed for an automatic index is really just a fancy hash table, then a query that uses an automatic index is just a hash join.
SQLite constructs a transient index instead of a hash table in this instance because it already has a robust and high performance B-Tree implementation at hand, whereas a hash-table would need to be added. Adding a separate hash table implementation to handle this one case would increase the size of the library (which is designed for use on low-memory embedded devices) for minimal performance gain. SQLite might be enhanced with a hash-table implementation someday, but for now it seems better to continue using automatic indexes in cases where client/server database engines might use a hash join.
# 15. The Predicate Push-Down Optimization
If a subquery cannot be [flattened](optoverview.md#flattening) into the outer query, it might still be possible to enhance performance by "pushing down" WHERE clause terms from the outer query into the subquery. Consider an example:
CREATE TABLE t1(a INT, b INT);\
CREATE TABLE t2(x INT, y INT);\
CREATE VIEW v1(a,b) AS SELECT DISTINCT a, b FROM t1;\
\
SELECT x, y, b\
FROM t2 JOIN v1 ON (x=a)\
WHERE b BETWEEN 10 AND 20;\
The view v1 cannot be [flattened](optoverview.md#flattening) because it is DISTINCT. It must instead be run as a subquery with the results being stored in a transient table, then the join is performed between t2 and the transient table. The push-down optimization pushes down the "b BETWEEN 10 AND 20" term into the view. This makes the transient table smaller, and helps the subquery to run faster if there is an index on t1.b. The resulting evaluation is like this:
SELECT x, y, b\
FROM t2\
JOIN (SELECT DISTINCT a, b FROM t1 WHERE b BETWEEN 10 AND 20)\
WHERE b BETWEEN 10 AND 20;\
The WHERE-clause push-down optimization cannot always be used. For example, if the subquery contains a LIMIT, then pushing down any part of the WHERE clause from the outer query could change the result of the inner query. There are other restrictions, explained in a comment in the source code on the pushDownWhereTerms() routine that implements this optimization.
Do not confuse this optimization with the optimization by a similar name in MySQL. The MySQL push-down optimization changes the order of evaluation of WHERE-clause constraints such that those that can be evaluated using only the index and without having to find the corresponding table row are evaluated first, thus avoiding an unnecessary table row lookup if the constraint fails. For disambiguation, SQLite calls this the "MySQL push-down optimization". SQLite does do the MySQL push-down optimization too, in addition to the WHERE-clause push-down optimization. But the focus of this section is the WHERE-clause push-down optimization.
# 16. The OUTER JOIN Strength Reduction Optimization
An OUTER JOIN (either a LEFT JOIN, a RIGHT JOIN, or a FULL JOIN) can sometimes be simplified. A LEFT or RIGHT JOIN can be converted into an ordinary (INNER) JOIN, or a FULL JOIN might be converted into either a LEFT or a RIGHT JOIN. This can happen if there are terms in the WHERE clause that guarantee the same result after simplification. For example, if any column in the right-hand table of the LEFT JOIN must be non-NULL in order for the WHERE clause to be true, then the LEFT JOIN is demoted to an ordinary JOIN.
The theorem prover that determines whether a join can be simplified is imperfect. It sometimes returns a false negative. In other words, it sometimes fails to prove that reducing the strength of an OUTER JOIN is safe when in fact it is safe. For example, the prover does not know the [datetime() SQL function](lang_datefunc.md#dttm) will always return NULL if its first argument is NULL, and so it will not recognize that the LEFT JOIN in the following query could be strength-reduced:
SELECT urls.url\
FROM urls\
LEFT JOIN\
(SELECT \*\
FROM (SELECT url_id AS uid, max(retrieval_time) AS rtime\
FROM lookups GROUP BY 1 ORDER BY 1)\
WHERE uid IN (358341,358341,358341)\
) recent\
ON u.source_seed_id = recent.xyz OR u.url_id = recent.xyz\
WHERE\
DATETIME(recent.rtime) \> DATETIME('now', '-5 days');\
It is possible that future enhancements to the prover might enable it to recognize that NULL inputs to certain built-in functions always result in a NULL answer. However, not all built-in functions have that property (for example [coalesce()](lang_corefunc.md#coalesce)) and, of course, the prover will never be able to reason about [application-defined SQL functions](appfunc.md).
# 17. The Omit OUTER JOIN Optimization
Sometimes a LEFT or RIGHT JOIN can be completely omitted from a query without changing the result. This can happen if all of the following are true:
1. The query is not an aggregate
2. Either the query is DISTINCT or else the ON or USING clause on the OUTER JOIN constrains the join such that it matches only a single row
3. The right-hand table of the LEFT JOIN or the left-hand table of a RIGHT JOIN is not be used anywhere in the query outside of its own USING or ON clause.
OUTER JOIN elimination often comes up when OUTER JOINs are used inside of views, and then the view is used in such as way that none of the columns on the right-hand table of the LEFT JOIN or on the left-hand table of a RIGHT JOIN are referenced.
Here is a simple example of omitting a LEFT JOIN:
CREATE TABLE t1(ipk INTEGER PRIMARY KEY, v1);\
CREATE TABLE t2(ipk INTEGER PRIMARY KEY, v2);\
CREATE TABLE t3(ipk INTEGER PRIMARY KEY, v3);\
\
SELECT v1, v3 FROM t1 \
LEFT JOIN t2 ON (t1.ipk=t2.ipk)\
LEFT JOIN t3 ON (t1.ipk=t3.ipk)\
The t2 table is completely unused in the query above, and so the query planner is able to implement the query as if it were written:
SELECT v1, v3 FROM t1 \
LEFT JOIN t3 ON (t1.ipk=t3.ipk)\
As of this writing, only LEFT JOINs are eliminated. This optimize has not yet been generalized to work with RIGHT JOINs as RIGHT JOIN is a relatively new addition to SQLite. That asymmetry will probably be corrected in a future release.
# 18. The Constant Propagation Optimization
When a WHERE clause contains two or more equality constraints connected by the AND operator such that all of the [affinities](datatype3.md#affinity) of the various constraints are the same, then SQLite might use the transitive property of equality to construct new "virtual" constraints that can be used to simplify expressions and/or improve performance. This is called the "constant-propagation optimization".
For example, consider the following schema and query:
CREATE TABLE t1(a INTEGER PRIMARY KEY, b INT, c INT);\
SELECT \* FROM t1 WHERE a=b AND b=5;\
SQLite looks at the "a=b" and "b=5" constraints and deduces that if those two constraints are true, then it must also be the case that "a=5" is true. This means that the desired row can be looked up quickly using a value of 5 for the INTEGER PRIMARY KEY.
---
# The SQLite Zipfile Module
*Sección: Guides | Origen: https://www.sqlite.org/zipfile.html*
# 1. Overview
The zipfile module provides read/write access to simple [ZIP archives](https://en.wikipedia.org/wiki/Zip_%28file_format%29). The current implementation has the following restrictions:
- Does not support encryption.
- Does not support ZIP archives that span multiple files.
- Does not support zip64 extensions.
- The only compression algorithm supported is ["deflate"](https://zlib.net).
Some or all of these restrictions may be removed in the future.
# 2. Obtaining and Compiling Zipfile
The code for the zipfile module is found in the [ext/misc/zipfile.c](https://sqlite.org/src/file/ext/misc/zipfile.c) file of the [main SQLite source tree](https://sqlite.org/src). It may be compiled into an SQLite [loadable extension](loadext.md) using a command like:
gcc -g -fPIC -shared zipfile.c -o zipfile.so\
Alternatively, the zipfile.c file may be compiled into the application. In this case, the following function should be invoked to register the extension with each new database connection:
int sqlite3_zipfile_init(sqlite3 \*db, void\*, void\*);\
The first argument passed should be the database handle to register the extension with. The second and third arguments should both be passed 0.
Zipfile is included in most builds of the [command-line shell](cli.md).
# 3. Using Zipfile
The zipfile module provides three similar interfaces for accessing, updating and creating zip file archives:
1. A table-valued function, which provides read-only access to existing archives, either from the file-system or in-memory.
2. A virtual table, which provides read and write access to archives stored in the file-system.
3. An SQL aggregate function, which can be used to create new archives in memory.
The zipfile module provides two similar interfaces for accessing zip archives. A table-valued function, which provides read-only access to existing archives, and a virtual table interface, which provides both read and write access.
## 3.1. Table-Valued Function (read-only access)
For reading existing zip archives, the Zipfile module provides a [table-valued function](vtab.md#tabfunc2) that accepts a single argument. If the argument is a text value, then it is a path to a zip archive to read from the file-system. Or, if the argument is an SQL blob, then it is the zip archive data itself.
For example, to inspect the contents of zip archive "test.zip" from the current directory:
SELECT \* FROM zipfile('test.zip');\
Or, from the SQLite shell tool (the [readfile()](cli.md#fileio) function reads the contents of a file from the file-system and returns it as a blob):
SELECT \* FROM zipfile( readfile('test.zip') );\
The table-valued function returns one row for each record (file, directory or symbolic link) in the zip archive. Each row has the following columns:
| Column Name | Contents |
|----|----|
| name | File name/path for the zip file record. |
| mode | UNIX mode, as returned by stat(2) for the zip file record (an integer). This identifies the type of record (file, directory or symbolic link), and the associated user/group/all permissions. |
| mtime | UTC timestamp, in seconds since the UNIX epoch (an integer). |
| sz | Size of associated data in bytes after it has been uncompressed (an integer). |
| rawdata | Raw (possibly compressed) data associated with zip file entry (a blob). |
| data | If the compression method for the record is either 0 or 8 (see below), then the uncompressed data associated with the zip file entry. Or, if the compression method is not 0 or 8, this column contains a NULL value. |
| method | The compression method used to compress the data (an integer). The value 0 indicates that the data is stored in the zip archive without compression. 8 means the raw deflate algorithm. |
## 3.2. Virtual Table Interface (read/write access)
In order to create or modify an existing zip file, a "zipfile" virtual table must be created in the database schema. The CREATE VIRTUAL TABLE statement expects a path to the zip file as its only argument. For example, to write to zip file "test.zip" in the current directory, a zipfile table may be created using:
CREATE VIRTUAL TABLE temp.zip USING zipfile('test.zip');\
Such a virtual table has the same columns as the table-valued function described in the previous section. It may be read from using a SELECT statement in the same way as the table-valued function can.
Using the virtual table interface, new entries may be added to a zip archive by inserting new rows into the virtual table. Entries may be removed by deleting rows or modified by updating them.
### 3.2.1. Adding Entries to a Zip Archive
Entries may be added to a zip archive by inserting new rows. The easiest way to do this is to specify values for the "name" and "data" columns only and have zipfile fill in sensible defaults for other fields. To insert a directory into the archive, set the "data" column to NULL. For example, to add the directory "dir1" and the file "m.txt" containing the text "abcdefghi" to zip archive "test.zip":
INSERT INTO temp.zip(name, data) VALUES('dir1', NULL); *-- Add directory *\
INSERT INTO temp.zip(name, data) VALUES('m.txt', 'abcdefghi'); *-- Add regular file *\
When a directory is inserted, if the "name" value does not end with a '/' character, the zipfile module appends one. This is necessary for compatibility with other programs (most notably "info-zip") that manipulate zip archives.
To insert a symbolic link, the user must also supply a "mode" value. For example, to add a symbolic link from "link.txt" to "m.txt":
INSERT INTO temp.zip(name, mode, data) VALUES('link.txt', 'lrwxrw-rw-', 'm.txt');\
The following rules and caveats apply to the values specified as part of each INSERT statement:
| Columns | Notes |
|---|---|
| name | A non-NULL text value must be specified for the name column. It is an error if the specified name already exists in the archive. |
| mode | If NULL is inserted into the mode column, then the mode of the new archive entry is automatically set to either 33188 (-rw-r--r--) or 16877 (drwxr-xr-x), depending on whether or not the values specified for columns "sz", "data" and "rawdata" indicate that the new entry is a directory. If the specified value is an integer (or text that looks like an integer), it is inserted verbatim. If the value is not a valid UNIX mode, some programs may behave unexpectedly when extracting files from the archive. Finally, if the value specified for this column is not an integer or a NULL, then it is assumed to be a UNIX permissions string similar to those output by the "ls -l" command (e.g. "-rw-r--r--", "drwxr-xr-x" etc.). In this case, if the string cannot be parsed it is an error. |
| mtime | If NULL is inserted into the mtime column, then the timestamp of the new entry is set to the current time. Otherwise, the specified value is interpreted as an integer and used as is. |
| sz | This column must be set to NULL. If a non-NULL value is inserted into this column, or if a new non-NULL value is provided using an UPDATE statement, it is an error. |
| rawdata | This column must be set to NULL. If a non-NULL value is inserted into this column, or if a new non-NULL value is provided using an UPDATE statement, it is an error. |
| data | To insert a directory into the archive, this field must be set to NULL. In this case if a value was explicitly specified for the "mode" column, then it must be consistent with a directory (i.e. it must be true that (mode & 0040000)=0040000). Otherwise, the value inserted into this field is the file contents for a regular file, or the target of a symbolic link. |
| method | This field must be set one of integer values 0 and 8, or else to NULL. For a directory entry, any value inserted into this field is ignored. Otherwise, if it is set to 0, then the file data or symbolic link target is stored as is in the zip archive and the compression method set to 0. If it is set to 8, then the file data or link target is compressed using deflate compression before it is stored and the compression method set to 8. Finally, if a NULL value is written to this field, the zipfile module automatically decides whether or not to compress the data before storing it. |
| COLLATE binary | >COLLATE uint | >
|---|---|
> '0000123457' > '123456' > 'abc0000000010xyz' > 'abc0010xyy' > 'abc10xzz' > 'abc674xyz' > 'abc87xyz' > 'abc9xyz' |
> > '123456' > '0000123457' > 'abc9xyz' > 'abc0010xyy' > 'abc0000000010xyz' > 'abc10xzz' > 'abc87xyz' > 'abc674xyz' |
>
| CVE Number | Fix | Comments |
|---|---|---|
| CVE-2026-11822 | 3.53.2 (2026-06-03) |
An attacker who can execute arbitrary SQL (for example via SQL injection) on a system that has the SQLITE_DBCONFIG_DEFENSIVE disabled and which has FTS5 enabled, can cause a write off the end of a heap buffer. |
| CVE-2026-11824 | 3.53.2 (2026-06-03) |
This appears to be a duplicate of CVE-2026-11824. |
| CVE-2025-3277 | 3.49.1 (2025-02-18) |
A bug in the concat_ws() SQL function can cause a write past the end of an array obtained from malloc(). If an attacker can control the first argument to concat_ws(), so that the separator string is large - more than 2MB - then an integer overflow in the calculation of the size of the result buffer might cause a short malloc() and subsequent write past the end of the allocated space. Fixed by check-in 2025-02-16T10:57z. |
| CVE-2025-6965 | 3.50.2 (2025-06-28) |
An attacker who can inject arbitrary SQL statements into an application might be able to cause an integer overflow resulting in a read off the end of an array. Fixed on 2025-06-27. |
| CVE-2025-7458 | 3.42.0 (2023-05-16) |
An attacker who can inject arbitrary SQL statements into an application might be able to cause an integer overflow resulting in a read off the end of an array. Fixed on 2023-03-16. |
| CVE-2025-7709 | 3.50.3 (2025-07-17) |
An attacker who has complete control over the database content could create a corrupt FTS5 index resulting access to memory outside the bounds of an array due to integer overflow. Fixed on 2025-07-15. |
| CVE-2025-29087 | 3.49.1 (2025-02-18) |
Duplicate of CVE-2025-3277 |
| CVE-2025-29088 | 3.49.1 (2025-02-18) |
Passing out-of-bounds arguments to the C-language API routine sqlite3_db_config(db,SQLITE_DBCONFIG_LOOKASIDE,...) can lead to a crash and denial of service. Reported by Forum post 48f365daec. Complaint addressed by check-in 2025-02-17T14:16Z. |
| CVE-2025-52099 | 3.49.1 (2025-02-18) |
Duplicate of CVE-2025-29088 |
| CVE-2025-70873 | 3.52.0 (2026-03-06) |
When using the zipfile extension (not a part of standard SQLite but usually included in builds of the CLI), a malformed ZIP file input can result in an out-of-bounds read. Reported by forum post 2025-12-06T16:46:32Z and fixed in trunk by check-in 2025-12-06T23:58:09.413Z. |
| CVE-2024-0232 | 3.43.2 (2023-10-10) |
An attacker who can inject arbitrary SQL statements into an application might be able to provoke a use-after-free bug in SQLite's JSON parser that can (in theory) lead to an application crash and denial of service. See forum thread b25edc1d4662 for the bug report. |
| CVE-2023-32697 | Not a bug in SQLite | This is a bug in the SQLite JDBC library, which is a wrapper library that provides access to SQLite from Java. SQLite JDBC is created and maintained independently from SQLite. Despite the use of "SQLite" in the name, the SQLite JDBC library is not affiliated with the SQLite project in any way. The vulnerability identified by this CVE is in the separate SQLite JDBC wrapper library and does not affect SQLite itself. |
| CVE-2023-39939 | Not a bug in SQLite | This is not a bug in SQLite. This is an SQL injection bug in an application (LuxCal Web Calendar) that links against SQLite. Even though this CVE is not about SQLite, "SQLite" is mentioned in the description and so we list it here. |
| CVE-2023-39543 | Not a bug in SQLite | This is not a bug in SQLite. This is an XSS vulnerability in a separate application (LuxCal Web Calendar) that links against SQLite. The bug is in the application, not in SQLite. However "SQLite" is mentioned in the description and so we list it here. |
| CVE-2023-7104 | 3.43.1 (2023-09-11) |
This is a bug in the session extension of SQLite, not in the SQLite core. This bug is only reachable by applications that recompile SQLite using the -DSQLITE_ENABLE_SESSION compile-time option and then use the Session C-language APIs to process a changeset that has been subtly corrupted by an adversary. So this bug probably does not apply to you. See forum post f935c4708dd528d9 for additional information. |
| CVE-2022-46908 | Not a bug in the core SQLite library | This is a bug in the --safe command-line option of the command-line shell program that is available for accessing SQLite database files. The bug does not exist in the SQLite library. Nor is it an issue for the CLI as long as the user does not depend on the --safe option. It is not serious. It is debatable whether or not this is a security issue. |
| CVE-2022-38627 | Not a bug in SQLite | This is not a bug in SQLite. This is an SQL injection bug in a specific PHP application. In other words, the bug is in the PHP application code, not in SQLite. Even though this CVE is not about SQLite, "SQLite" is mentioned in the publicity about the bug and so we list it here. |
| CVE-2022-35737 | 3.39.2 (2022-07-21) |
This bug is an array-bounds overflow. The bug is only accessible when using some of the C-language APIs provided by SQLite. The bug cannot be reached using SQL nor can it be reached by providing SQLite with a corrupt database file. The bug only comes up when very long string inputs (greater than 2 billion bytes in length) are provided as arguments to a few specific C-language interfaces, and even then only under special circumstances. |
| CVE-2022-24854 | Not a bug in SQLite | This CVE describes a bug in an application that uses SQLite, not in SQLite itself. SQLite is doing everything correctly. The application grants users the ability to run SQL statements, using SQLite, that can leak or change information that those users should not normally have access to. This is purely an application bug. It does not describe a malfunction or vulnerability in SQLite. |
| CVE-2022-21227 | Not a bug in SQLite | This CVE describes a bug in a third-party packages that provides a binding for SQLite to Node.js. The bug reported is in the third-party Node.js binding, not in SQLite itself. Do not be confused by the use of the word "SQLite" in the ambiguously-worded CVE description. |
| CVE-2021-45346 | Not a bug in SQLite | This CVE is misinformation. See the discussion around SQLite forum post 53de8864ba114bf. |
| CVE-2021-42169 | Not a bug in SQLite | This CVE has nothing whatsoever to do with SQLite. It is about a bug in application that happens to use SQLite. Since SQLite is mentioned in the CVE description, the CVE is included here to emphasize that this is not an SQLite bug. |
| CVE-2021-36690 | Not a bug in the core SQLite library | This bug is not in the SQLite core library, but rather in an experimental extension that is used to implement the .expert command in the CLI. The code that contains the bug does not appear in standard SQLite builds, though it is included in the sqlite3.exe command-line tool. Applications must link against the extra source code files that implement the extension and take other deliberate actions to activate the extension before the troublesome code can be run. For the rare application that uses the troublesome extension, the consequence of this bug is that malicious SQL can cause a NULL pointer deference and denial of service. (details) |
| CVE-2021-31239 | Not a bug in the core SQLite library | This is a bug in the CLI. It allows a user with unrestricted shell access to cause a denial-of-service. Of course, there are a million easier ways for a user with unrestricted shell access to cause far worse mischief. The problem was in the appendvfs extension which is not a part of standard SQLite. (details) |
| CVE-2021-28305 | Not a bug in SQLite | This is not a bug in SQLite. The bug is in a third-party application that uses SQLite. SQLite is mentioned by name in the CVE description, however, so we have included the CVE in the list. |
| CVE-2021-23404 | Not a bug in SQLite | This is not a bug in SQLite. The bug is in a third-party application that uses SQLite and includes "sqlite" in its name. This CVE is included on the list because it mentions SQLite even though the bug has nothing to do with SQLite. |
| CVE-2021-20227 | 3.34.1 (2021-01-20) |
Malicious SQL statement causes read-after-free. No harm can come of this particular read-after-free instance, as far as anyone knows. The bug is undetectable without a memory sanitizer. The CVE claims that this bug is an RCE - a Remote Code Execution vulnerability, but that claim is incorrect. The RCE claim is misinformation. (details) |
| CVE-2021-20223 | 3.34.0 (2020-12-01) |
The problem identified by this CVE is not a vulnerability. It is a malfunction. A coding error causes FTS5 to sometimes return inconsistent and incorrect results under obscure circumstances, but no memory errors occur. (details) |
| CVE-2021-0646 | 3.32.1 (2020-05-25) |
Duplicate of CVE-2020-13434. |
| CVE-2020-15358 | 3.32.3 (2020-06-18) |
Malicious SQL statement causes a read past the end of a heap buffer. (details) |
| CVE-2020-13871 | 3.32.3 (2020-06-18) |
Malicious SQL statement causes a read-only use-after-free memory error. (details) |
| CVE-2020-13632 | 3.32.0 (2020-05-22) |
Malicious SQL statement causes a read of a NULL pointer in the matchinfo() SQL function of the FTS3 extension, resulting in denial of service. (details) |
| CVE-2020-13631 | 3.32.0 (2020-05-22) |
Malicious SQL statement (an ALTER TABLE that tries to rename a virtual table into one of its own shadow tables) causes an infinite loop and denial of service. (details) |
| CVE-2020-13630 | 3.32.0 (2020-05-22) |
Malicious SQL statement causes a read-only use-after-free, possibly resulting in an incorrect output from the snippet() SQL function of the FTS3 extension. There is no known way to exfiltrate data or crash the application using this bug. (details) |
| CVE-2020-13435 | 3.32.1 (2020-05-25) |
Malicious SQL statement causes a read access to a NULL pointer and denial of service. (details) |
| CVE-2020-13434 | 3.32.1 (2020-05-25) |
Malicious SQL statement involving the printf() SQL function results in an integer overflow which can overwrite the stack with over 2 billion bytes of 0x30 or 0x20 (ASCII '0' or ' '). Even though this is a stack overwrite, there is no known way to redirect control or otherwise escalate the level of harm. This is a denial-of-service attack only. (details) |
| CVE-2020-11656 | 3.32.0 (2020-05-22) |
Malicious SQL statement causes read-only use-after-free of memory allocation if SQLite is compile with -DSQLITE_DEBUG. Does not affect release builds. (details) |
| CVE-2020-11655 | 3.32.0 (2020-05-22) |
Malicious SQL statement causes a read using an uninitialized pointer and denial-of-service. (details) |
| CVE-2020-9327 | 3.32.0 (2020-05-22) |
Malicious SQL statement causes a read using an uninitialized pointer and denial-of-service (details) |
| CVE-2020-6405 | 3.31.0 (2020-01-22) |
Malicious SQL statement causes a NULL pointer dereference and denial-of-service (details) |
| CVE-2019-20218 | 3.31.0 (2020-01-22) |
Malicious SQL statement causes an uninitialized pointer read and denial-of-service. (details) |
| CVE-2019-19959 | 3.31.0 (2020-01-22) |
Malicious SQL statement causes a NULL pointer dereference in the Zipfile virtual table extension and denial-of-service. This is only possible when the optional Zipfile virtual table extension is deployed, which is not the case in default builds. (details) |
| CVE-2019-19926 | 3.31.0 (2020-01-22) |
Malicious SQL statement causes an uninitialized pointer read and denial-of-service. (details) |
| CVE-2019-19925 | 3.31.0 (2020-01-22) |
Malicious SQL statement causes a NULL pointer dereference and in the Zipfile virtual table extension and denial-of-service. This is only possible when the optional Zipfile virtual table extension is deployed, which is not the case in default builds. (details) |
| CVE-2019-19924 | 3.31.0 (2020-01-22) |
Malicious SQL statement causes an uninitialized pointer reference and denial-of-service. (details) |
| CVE-2019-19923 | 3.31.0 (2020-01-22) |
Malicious SQL statement causes a NULL pointer dereference and denial-of-service. (details) |
| CVE-2019-19646 | 3.31.0 (2020-01-22) |
The PRAGMA integrity_check command might cause the byte-code for a prepared statement to loop indefinitely. This might enable a denial-of-service, if the application has not taken appropriate and prudent steps to limit the run-time of SQL statements. This is not a vulnerability, as there are countless perfectly valid SQL queries, especially queries involving recursive common table expressions, that also run essentially forever. (details) |
| CVE-2019-19317 | 3.31.0 (2020-01-22) |
This CVE identifies a bug in a development check-in of SQLite. The bug never appeared in any official SQLite release. (details) |
| Name | Offset | |
|---|---|---|
| xShmLock | File | |
| WAL_WRITE_LOCK | 0 | 120 |
| WAL_CKPT_LOCK | 1 | 121 |
| WAL_RECOVER_LOCK | 2 | 122 |
| WAL_READ_LOCK(0) | 3 | 123 |
| WAL_READ_LOCK(1) | 4 | 124 |
| WAL_READ_LOCK(2) | 5 | 125 |
| WAL_READ_LOCK(3) | 6 | 126 |
| WAL_READ_LOCK(4) | 7 | 127 |
[Adobe](http://www.adobe.com/) uses SQLite as the [application file format](whentouse.md#appfileformat) for their [Photoshop Lightroom](http://www.adobe.com/products/photoshoplightroom/) product. SQLite is also a standard part of the [Adobe Integrated Runtime (AIR)](https://airsdk.harman.com). It is reported that [Acrobat Reader](http://www.adobe.com/products/acrobat/readstep2.html) also uses SQLite.
------------------------------------------------------------------------
[Airbus](http://www.airbus.com/) confirms that SQLite is being used in the flight software for the [A350 XWB](https://www.airbus.com/en/products-services/commercial-aircraft/passenger-aircraft/a350-family) family of aircraft.
------------------------------------------------------------------------
[Apple](http://www.apple.com/) uses SQLite in many (most?) of the native applications running on Mac OS-X desktops and servers and on iOS devices such as iPhones and iPods. SQLite is also used in [iTunes](http://www.apple.com/itunes/), even on non-Apple hardware.
------------------------------------------------------------------------
[Bentley Systems](http://www.bentley.com/) uses SQLite as the [application file format](aff_short.md) for their [Microstation](https://www.bentley.com/en/products/product-line/modeling-and-visualization-software/microstation) CAD/CAM product.
------------------------------------------------------------------------
[Bosch](http://www.bosch.com/) uses SQLite in the multimedia systems install on GM, Nissan, and Suzuki automobiles. ([link](http://oss.bosch-cm.com/index.html))
------------------------------------------------------------------------
The increasingly popular [Dropbox](http://www.dropbox.com/) file archiving and synchronization service is reported to use SQLite as the primary data store on the client side.
------------------------------------------------------------------------
[Expensify](https://www.expensify.com/) uses SQLite as a server-side database engine for their enterprise-scale expense reporting software.
------------------------------------------------------------------------
[Facebook](https://www.facebook.com/) uses SQLite as the SQL database engine in their [osquery](https://code.facebook.com/projects/658950180885092) product.
------------------------------------------------------------------------
We believe that [General Electric](http://www.ge.com/) uses SQLite in some product or another because they have written to the SQLite developers at least four separate times requesting the US Export Control Number for SQLite. So presumably GE is using SQLite in something that they are exporting. But nobody (outside of GE) seems to know what that might be.
------------------------------------------------------------------------
uses SQLite in their [Android](http://code.google.com/android/) cell-phone operating system, and in the [Chrome Web Browser](http://www.google.com/chrome).
------------------------------------------------------------------------
[Intuit](http://www.intuit.com/) apparently uses SQLite in [QuickBooks](http://www.quickbooks.com/) and in [TurboTax](http://turbotax.intuit.com/) to judge from some error reports from users seen [here](http://community.intuit.com/posts/database-error-sqlite-error-code1) and [here](https://ttlc.intuit.com/post/show_full/cJf8mIhC4r4jjracfArQzM/when-i-try-to-update-turbotax-i-receive-an-unexpected-error-message).
------------------------------------------------------------------------
The United States Library of Congress recognizes SQLite as a [recommended storage format](locrsf.md) for preservation of digital content.
------------------------------------------------------------------------
[McAfee](http://www.mcafee.com/) uses SQLite in its antivirus programs. Mentioned [here](http://www.mail-archive.com/sqlite-users@sqlite.org/msg16931.html) and implied [here](https://forums.mcafee.com/t5/WebAdvisor/SQLite-Temporary-Files/m-p/19512).
------------------------------------------------------------------------
[Microsoft](http://www.microsoft.com/) uses SQLite as a core component of Windows 10, and in other products.
------------------------------------------------------------------------
SQLite is the primary meta-data storage format for the [Firefox Web Browser](http://www.mozilla.com/) and the [Thunderbird Email Reader](http://www.mozilla.com/thunderbird/) from Mozilla.
------------------------------------------------------------------------
[The Navigation Data Standard](http://www.nds-association.org/) uses SQLite as its [application file format](aff_short.md).
------------------------------------------------------------------------
The popular [PHP](http://www.php.net/) programming language comes with both SQLite2 and SQLite3 built in.
------------------------------------------------------------------------
All [Python](http://docs.python.org/lib/module-sqlite3.html) distributions since Python 2.5 include SQLite.
------------------------------------------------------------------------
The [RedHat Package Manager (RPM)](https://en.wikipedia.org/wiki/RPM_Package_Manager) uses SQLite to track its state.
------------------------------------------------------------------------
There are [multiple](http://www.mail-archive.com/sqlite-users%40sqlite.org/msg27326.html) [sightings](http://www.mail-archive.com/sqlite-users%40sqlite.org/msg27332.html) of SQLite in the Skype client for Mac OS X and Windows.
------------------------------------------------------------------------
The Tcl/Tk programming language now comes with SQLite built-in. SQLite works particularly well with Tcl since SQLite was originally a Tcl extension that subsequently "escaped" into the wild.
------------------------------------------------------------------------
SQLite comes bundled with the [Xojo](http://www.xojo.com/) programming environment (formerly [REALbasic](http://www.realbasic.com/))
| | |
|----|----|
| | [Adobe](http://www.adobe.com/) uses SQLite as the [application file format](whentouse.md#appfileformat) for their [Photoshop Lightroom](http://www.adobe.com/products/photoshoplightroom/) product. SQLite is also a standard part of the [Adobe Integrated Runtime (AIR)](https://airsdk.harman.com). It is reported that [Acrobat Reader](http://www.adobe.com/products/acrobat/readstep2.html) also uses SQLite. |
| | [Airbus](http://www.airbus.com/) confirms that SQLite is being used in the flight software for the [A350 XWB](https://www.airbus.com/en/products-services/commercial-aircraft/passenger-aircraft/a350-family) family of aircraft. |
| | [Apple](http://www.apple.com/) uses SQLite in many (most?) of the native applications running on Mac OS-X desktops and servers and on iOS devices such as iPhones and iPods. SQLite is also used in [iTunes](http://www.apple.com/itunes/), even on non-Apple hardware. |
| | [Bentley Systems](http://www.bentley.com/) uses SQLite as the [application file format](aff_short.md) for their [Microstation](https://www.bentley.com/en/products/product-line/modeling-and-visualization-software/microstation) CAD/CAM product. |
| | [Bosch](http://www.bosch.com/) uses SQLite in the multimedia systems install on GM, Nissan, and Suzuki automobiles. ([link](http://oss.bosch-cm.com/index.html)) |
| | The increasingly popular [Dropbox](http://www.dropbox.com/) file archiving and synchronization service is reported to use SQLite as the primary data store on the client side. |
| | [Expensify](https://www.expensify.com/) uses SQLite as a server-side database engine for their enterprise-scale expense reporting software. |
| | [Facebook](https://www.facebook.com/) uses SQLite as the SQL database engine in their [osquery](https://code.facebook.com/projects/658950180885092) product. |
| | We believe that [General Electric](http://www.ge.com/) uses SQLite in some product or another because they have written to the SQLite developers at least four separate times requesting the US Export Control Number for SQLite. So presumably GE is using SQLite in something that they are exporting. But nobody (outside of GE) seems to know what that might be. |
| | uses SQLite in their [Android](http://code.google.com/android/) cell-phone operating system, and in the [Chrome Web Browser](http://www.google.com/chrome). |
| | [Intuit](http://www.intuit.com/) apparently uses SQLite in [QuickBooks](http://www.quickbooks.com/) and in [TurboTax](http://turbotax.intuit.com/) to judge from some error reports from users seen [here](http://community.intuit.com/posts/database-error-sqlite-error-code1) and [here](https://ttlc.intuit.com/post/show_full/cJf8mIhC4r4jjracfArQzM/when-i-try-to-update-turbotax-i-receive-an-unexpected-error-message). |
| | The United States Library of Congress recognizes SQLite as a [recommended storage format](locrsf.md) for preservation of digital content. |
| | [McAfee](http://www.mcafee.com/) uses SQLite in its antivirus programs. Mentioned [here](http://www.mail-archive.com/sqlite-users@sqlite.org/msg16931.html) and implied [here](https://forums.mcafee.com/t5/WebAdvisor/SQLite-Temporary-Files/m-p/19512). |
| | [Microsoft](http://www.microsoft.com/) uses SQLite as a core component of Windows 10, and in other products. |
| | SQLite is the primary meta-data storage format for the [Firefox Web Browser](http://www.mozilla.com/) and the [Thunderbird Email Reader](http://www.mozilla.com/thunderbird/) from Mozilla. |
| | [The Navigation Data Standard](http://www.nds-association.org/) uses SQLite as its [application file format](aff_short.md). |
| | The popular [PHP](http://www.php.net/) programming language comes with both SQLite2 and SQLite3 built in. |
| | All [Python](http://docs.python.org/lib/module-sqlite3.html) distributions since Python 2.5 include SQLite. |
| | The [RedHat Package Manager (RPM)](https://en.wikipedia.org/wiki/RPM_Package_Manager) uses SQLite to track its state. |
| | There are [multiple](http://www.mail-archive.com/sqlite-users%40sqlite.org/msg27326.html) [sightings](http://www.mail-archive.com/sqlite-users%40sqlite.org/msg27332.html) of SQLite in the Skype client for Mac OS X and Windows. |
| | The Tcl/Tk programming language now comes with SQLite built-in. SQLite works particularly well with Tcl since SQLite was originally a Tcl extension that subsequently "escaped" into the wild. |
| | SQLite comes bundled with the [Xojo](http://www.xojo.com/) programming environment (formerly [REALbasic](http://www.realbasic.com/)) |
---
# What If OpenDocument Used SQLite?
*Sección: Guides | Origen: https://www.sqlite.org/affcase1.html*
## Introduction
Suppose the [OpenDocument](http://en.wikipedia.org/wiki/OpenDocument) file format, and specifically the "ODP" OpenDocument Presentation format, were built around SQLite. Benefits would include:
- Smaller documents
- Faster File/Save times
- Faster startup times
- Less memory used
- Document versioning
- A better user experience
Note that this is only a thought experiment. We are not suggesting that OpenDocument be changed. Nor is this article a criticism of the current OpenDocument design. The point of this essay is to suggest ways to improve future file format designs.
## About OpenDocument And OpenDocument Presentation
The OpenDocument file format is used for office applications: word processors, spreadsheets, and presentations. It was originally designed for the OpenOffice suite but has since been incorporated into other desktop application suites. The OpenOffice application has been forked and renamed a few times. This author's primary use for OpenDocument is building slide presentations with either [NeoOffice](https://www.neooffice.org/neojava/en/index.php) on Mac, or [LibreOffice](http://www.libreoffice.org/) on Linux and Windows.
An OpenDocument Presentation or "ODP" file is a [ZIP archive](http://en.wikipedia.org/wiki/Zip_%28file_format%29) containing XML files describing presentation slides and separate image files for the various images that are included as part of the presentation. (OpenDocument word processor and spreadsheet files are similarly structured but are not considered by this article.) The reader can easily see the content of an ODP file by using the "zip -l" command. For example, the following is the "zip -l" output from a 49-slide presentation about SQLite from the 2014 [SouthEast LinuxFest](http://southeastlinuxfest.org/) conference:
> \
> Archive: self2014.odp\
> Length Date Time Name\
> --------- ---------- ----- ----\
> 47 2014-06-21 12:34 mimetype\
> 0 2014-06-21 12:34 Configurations2/statusbar/\
> 0 2014-06-21 12:34 Configurations2/accelerator/current.xml\
> 0 2014-06-21 12:34 Configurations2/floater/\
> 0 2014-06-21 12:34 Configurations2/popupmenu/\
> 0 2014-06-21 12:34 Configurations2/progressbar/\
> 0 2014-06-21 12:34 Configurations2/menubar/\
> 0 2014-06-21 12:34 Configurations2/toolbar/\
> 0 2014-06-21 12:34 Configurations2/images/Bitmaps/\
> 54702 2014-06-21 12:34 Pictures/10000000000001F40000018C595A5A3D.png\
> 46269 2014-06-21 12:34 Pictures/100000000000012C000000A8ED96BFD9.png\
> *... 58 other pictures omitted...*\
> 13013 2014-06-21 12:34 Pictures/10000000000000EE0000004765E03BA8.png\
> 1005059 2014-06-21 12:34 Pictures/10000000000004760000034223EACEFD.png\
> 211831 2014-06-21 12:34 content.xml\
> 46169 2014-06-21 12:34 styles.xml\
> 1001 2014-06-21 12:34 meta.xml\
> 9291 2014-06-21 12:34 Thumbnails/thumbnail.png\
> 38705 2014-06-21 12:34 Thumbnails/thumbnail.pdf\
> 9664 2014-06-21 12:34 settings.xml\
> 9704 2014-06-21 12:34 META-INF/manifest.xml\
> --------- -------\
> 10961006 78 files\
The ODP ZIP archive contains four different XML files: content.xml, styles.xml, meta.xml, and settings.xml. Those four files define the slide layout, text content, and styling. This particular presentation contains 62 images, ranging from full-screen pictures to tiny icons, each stored as a separate file in the Pictures folder. The "mimetype" file contains a single line of text that says:
> \
> application/vnd.oasis.opendocument.presentation\
The purpose of the other files and folders is presently unknown to the author but is probably not difficult to figure out.
## Limitations Of The OpenDocument Presentation Format
The use of a ZIP archive to encapsulate XML files plus resources is an elegant approach to an application file format. It is clearly superior to a custom binary file format. But using an SQLite database as the container, instead of ZIP, would be more elegant still.
A ZIP archive is basically a key/value database, optimized for the case of write-once/read-many and for a relatively small number of distinct keys (a few hundred to a few thousand) each with a large BLOB as its value. A ZIP archive can be viewed as a "pile-of-files" database. This works, but it has some shortcomings relative to an SQLite database, as follows:
1. **Incremental update is hard.**
It is difficult to update individual entries in a ZIP archive. It is especially difficult to update individual entries in a ZIP archive in a way that does not destroy the entire document if the computer loses power and/or crashes in the middle of the update. It is not impossible to do this, but it is sufficiently difficult that nobody actually does it. Instead, whenever the user selects "File/Save", the entire ZIP archive is rewritten. Hence, "File/Save" takes longer than it ought, especially on older hardware. Newer machines are faster, but it is still bothersome that changing a single character in a 50 megabyte presentation causes one to burn through 50 megabytes of the finite write life on the SSD.
2. **Startup is slow.**
In keeping with the pile-of-files theme, OpenDocument stores all slide content in a single big XML file named "content.xml". LibreOffice reads and parses this entire file just to display the first slide. LibreOffice also seems to read all images into memory as well, which makes sense seeing as when the user does "File/Save" it is going to have to write them all back out again, even though none of them changed. The net effect is that start-up is slow. Double-clicking an OpenDocument file brings up a progress bar rather than the first slide. This results in a bad user experience. The situation grows ever more annoying as the document size increases.
3. **More memory is required.**
Because ZIP archives are optimized for storing big chunks of content, they encourage a style of programming where the entire document is read into memory at startup, all editing occurs in memory, then the entire document is written to disk during "File/Save". OpenOffice and its descendants embrace that pattern.
One might argue that it is ok, in this era of multi-gigabyte desktops, to read the entire document into memory. But it is not ok. For one, the amount of memory used far exceeds the (compressed) file size on disk. So a 50MB presentation might take 200MB or more RAM. That still is not a problem if one only edits a single document at a time. But when working on a talk, this author will typically have 10 or 15 different presentations up all at the same time (to facilitate copy/paste of slides from past presentations) and so gigabytes of memory are required. Add in an open web browser or two and a few other desktop apps, and suddenly the disk is whirling and the machine is swapping. And even having just a single document is a problem when working on an inexpensive Chromebook retrofitted with Ubuntu. Using less memory is always better.
4. **Crash recovery is difficult.**
The descendants of OpenOffice tend to segfault more often than commercial competitors. Perhaps for this reason, the OpenOffice forks make periodic backups of their in-memory documents so that users do not lose all pending edits when the inevitable application crash does occur. This causes frustrating pauses in the application for the few seconds while each backup is being made. After restarting from a crash, the user is presented with a dialog box that walks them through the recovery process. Managing the crash recovery this way involves lots of extra application logic and is generally an annoyance to the user.
5. **Content is inaccessible.**
One cannot easily view, change, or extract the content of an OpenDocument presentation using generic tools. The only reasonable way to view or edit an OpenDocument document is to open it up using an application that is specifically designed to read or write OpenDocument (read: LibreOffice or one of its cousins). The situation could be worse. One can extract and view individual images (say) from a presentation using just the "zip" archiver tool. But it is not reasonable try to extract the text from a slide. Remember that all content is stored in a single "context.xml" file. That file is XML, so it is a text file. But it is not a text file that can be managed with an ordinary text editor. For the example presentation above, the content.xml file consist of exactly two lines. The first line of the file is just:
> \
> \\
The second line of the file contains 211792 characters of impenetrable XML. Yes, 211792 characters all on one line. This file is a good stress-test for a text editor. Thankfully, the file is not some obscure binary format, but in terms of accessibility, it might as well be written in Klingon.
## First Improvement: Replace ZIP with SQLite
Let us suppose that instead of using a ZIP archive to store its files, OpenDocument used a very simple SQLite database with the following single-table schema:
> \
> CREATE TABLE OpenDocTree(\
> filename TEXT PRIMARY KEY, -- Name of file\
> filesize BIGINT, -- Size of file after decompression\
> content BLOB -- Compressed file content\
> );\
For this first experiment, nothing else about the file format is changed. The OpenDocument is still a pile-of-files, only now each file is a row in an SQLite database rather than an entry in a ZIP archive. This simple change does not use the power of a relational database. Even so, this simple change shows some improvements.
Surprisingly, using SQLite in place of ZIP makes the presentation file smaller. Really. One would think that a relational database file would be larger than a ZIP archive, but at least in the case of NeoOffice that is not so. The following is an actual screen-scrape showing the sizes of the same NeoOffice presentation, both in its original ZIP archive format as generated by NeoOffice (self2014.odp), and as repacked as an SQLite database using the [SQLAR](https://sqlite.org/sqlar/doc/trunk/README.md) utility:
> \
> -rw-r--r-- 1 drh staff 10514994 Jun 8 14:32 self2014.odp\
> -rw-r--r-- 1 drh staff 10464256 Jun 8 14:37 self2014.sqlar\
> -rw-r--r-- 1 drh staff 10416644 Jun 8 14:40 zip.odp\
The SQLite database file ("self2014.sqlar") is about a half percent smaller than the equivalent ODP file! How can this be? Apparently the ZIP archive generator logic in NeoOffice is not as efficient as it could be, because when the same pile-of-files is recompressed using the command-line "zip" utility, one gets a file ("zip.odp") that is smaller still, by another half percent, as seen in the third line above. So, a well-written ZIP archive can be slightly smaller than the equivalent SQLite database, as one would expect. But the difference is slight. The key take-away is that an SQLite database is size-competitive with a ZIP archive.
The other advantage to using SQLite in place of ZIP is that the document can now be updated incrementally, without risk of corrupting the document if a power loss or other crash occurs in the middle of the update. (Remember that writes to [SQLite databases are atomic](atomiccommit.md).) True, all the content is still kept in a single big XML file ("content.xml") which must be completely rewritten if so much as a single character changes. But with SQLite, only that one file needs to change. The other 77 files in the repository can remain unaltered. They do not all have to be rewritten, which in turn makes "File/Save" run much faster and saves wear on SSDs.
## Second Improvement: Split content into smaller pieces
A pile-of-files encourages content to be stored in a few large chunks. In the case of ODP, there are just four XML files that define the layout of all slides in a presentation. An SQLite database allows storing information in a few large chunks, but SQLite is also adept and efficient at storing information in numerous smaller pieces.
So then, instead of storing all content for all slides in a single oversized XML file ("content.xml"), suppose there was a separate table for storing the content of each slide separately. The table schema might look something like this:
> \
> CREATE TABLE slide(\
> pageNumber INTEGER, -- The slide page number\
> slideContent TEXT -- Slide content as XML or JSON\
> );\
> CREATE INDEX slide_pgnum ON slide(pageNumber); -- Optional\
The content of each slide could still be stored as compressed XML. But now each page is stored separately. So when opening a new document, the application could simply run:
> \
> SELECT slideContent FROM slide WHERE pageNumber=1;\
This query will quickly and efficiently return the content of the first slide, which could then be speedily parsed and displayed to the user. Only one page needs to be read and parsed in order to render the first screen, which means that the first screen appears much faster and there is no longer a need for an annoying progress bar.
If the application wanted to keep all content in memory, it could continue reading and parsing the other pages using a background thread after drawing the first page. Or, since reading from SQLite is so efficient, the application might instead choose to reduce its memory footprint and only keep a single slide in memory at a time. Or maybe it keeps the current slide and the next slide in memory, to facilitate rapid transitions to the next slide.
Notice that dividing up the content into smaller pieces using an SQLite table gives flexibility to the implementation. The application can choose to read all content into memory at startup. Or it can read just a few pages into memory and keep the rest on disk. Or it can read just a single page into memory at a time. And different versions of the application can make different choices without having to make any changes to the file format. Such options are not available when all content is in a single big XML file in a ZIP archive.
Splitting content into smaller pieces also helps File/Save operations to go faster. Instead of having to write back the content of all pages when doing a File/Save, the application only has to write back those pages that have actually changed.
One minor downside of splitting content into smaller pieces is that compression does not work as well on shorter texts and so the size of the document might increase. But as the bulk of the document space is used to store images, a small reduction in the compression efficiency of the text content will hardly be noticeable, and is a small price to pay for an improved user experience.
## Third Improvement: Versioning
Once one is comfortable with the concept of storing each slide separately, it is a small step to support versioning of the presentation. Consider the following schema:
> \
> CREATE TABLE slide(\
> slideId INTEGER PRIMARY KEY,\
> derivedFrom INTEGER REFERENCES slide,\
> content TEXT -- XML or JSON or whatever\
> );\
> CREATE TABLE version(\
> versionId INTEGER PRIMARY KEY,\
> priorVersion INTEGER REFERENCES version,\
> checkinTime DATETIME, -- When this version was saved\
> comment TEXT, -- Description of this version\
> manifest TEXT -- List of integer slideIds\
> );\
In this schema, instead of each slide having a page number that determines its order within the presentation, each slide has a unique integer identifier that is unrelated to where it occurs in sequence. The order of slides in the presentation is determined by a list of slideIds, stored as a text string in the MANIFEST column of the VERSION table. Since multiple entries are allowed in the VERSION table, that means that multiple presentations can be stored in the same document.
On startup, the application first decides which version it wants to display. Since the versionId will naturally increase in time and one would normally want to see the latest version, an appropriate query might be:
> \
> SELECT manifest, versionId FROM version ORDER BY versionId DESC LIMIT 1;\
Or perhaps the application would rather use the most recent checkinTime:
> \
> SELECT manifest, versionId, max(checkinTime) FROM version;\
Using a single query such as the above, the application obtains a list of the slideIds for all slides in the presentation. The application then queries for the content of the first slide, and parses and displays that content, as before.
(Aside: Yes, that second query above that uses "max(checkinTime)" really does work and really does return a well-defined answer in SQLite. Such a query either returns an undefined answer or generates an error in many other SQL database engines, but in SQLite it does what you would expect: it returns the manifest and versionId of the entry that has the maximum checkinTime.)
When the user does a "File/Save", instead of overwriting the modified slides, the application can now make new entries in the SLIDE table for just those slides that have been added or altered. Then it creates a new entry in the VERSION table containing the revised manifest.
The VERSION table shown above has columns to record a check-in comment (presumably supplied by the user) and the time and date at which the File/Save action occurred. It also records the parent version to record the history of changes. Perhaps the manifest could be stored as a delta from the parent version, though typically the manifest will be small enough that storing a delta might be more trouble than it is worth. The SLIDE table also contains a derivedFrom column which could be used for delta encoding if it is determined that saving the slide content as a delta from its previous version is a worthwhile optimization.
So with this simple change, the ODP file now stores not just the most recent edit to the presentation, but a history of all historic edits. The user would normally want to see just the most recent edition of the presentation, but if desired, the user can now go backwards in time to see historical versions of the same presentation.
Or, multiple presentations could be stored within the same document.
With such a schema, the application would no longer need to make periodic backups of the unsaved changes to a separate file to avoid lost work in the event of a crash. Instead, a special "pending" version could be allocated and unsaved changes could be written into the pending version. Because only changes would need to be written, not the entire document, saving the pending changes would only involve writing a few kilobytes of content, not multiple megabytes, and would take milliseconds instead of seconds, and so it could be done frequently and silently in the background. Then when a crash occurs and the user reboots, all (or almost all) of their work is retained. If the user decides to discard unsaved changes, they simply go back to the previous version.
There are details to fill in here. Perhaps a screen can be provided that displays all historical changes (perhaps with a graph) allowing the user to select which version they want to view or edit. Perhaps some facility can be provided to merge forks that might occur in the version history. And perhaps the application should provide a means to purge old and unwanted versions. The key point is that using an SQLite database to store the content, rather than a ZIP archive, makes all of these features much, much easier to implement, which increases the possibility that they will eventually get implemented.
## And So Forth...
In the previous sections, we have seen how moving from a key/value store implemented as a ZIP archive to a simple SQLite database with just three tables can add significant capabilities to an application file format. We could continue to enhance the schema with new tables, with indexes added for performance, with triggers and views for programming convenience, and constraints to enforce consistency of content even in the face of programming errors. Further enhancement ideas include:
- Store an [automated undo/redo stack](undoredo.md) in a database table so that Undo could go back into prior edit sessions.
- Add [full text search](fts3.md#fts4) capabilities to the slide deck, or across multiple slide decks.
- Decompose the "settings.xml" file into an SQL table that is more easily viewed and edited by separate applications.
- Break out the "Presenter Notes" from each slide into a separate table, for easier access from third-party applications and/or scripts.
- Enhance the presentation concept beyond the simple linear sequence of slides to allow for side-tracks and excursions to be taken depending on how the audience is responding.
An SQLite database has a lot of capability, which this essay has only begun to touch upon. But hopefully this quick glimpse has convinced some readers that using an SQL database as an application file format is worth a second look.
Some readers might resist using SQLite as an application file format due to prior exposure to enterprise SQL databases and the caveats and limitations of those other systems. For example, many enterprise database engines advise against storing large strings or BLOBs in the database and instead suggest that large strings and BLOBs be stored as separate files and the filename stored in the database. But SQLite is not like that. Any column of an SQLite database can hold a string or BLOB up to about a gigabyte in size. And for strings and BLOBs of 100 kilobytes or less, [I/O performance is better](intern-v-extern-blob.md) than using separate files.
Some readers might be reluctant to consider SQLite as an application file format because they have been inculcated with the idea that all SQL database schemas must be factored into [Third Normal Form (3NF)](https://en.wikipedia.org/wiki/Third_normal_form) and store only small primitive data types such as strings and integers. Certainly relational theory is important and designers should strive to understand it. But, as demonstrated above, it is often quite acceptable to store complex information as XML or JSON in text fields of a database. Do what works, not what your database professor said you ought to do.
## Review Of The Benefits Of Using SQLite
In summary, the claim of this essay is that using SQLite as a container for an application file format like OpenDocument and storing lots of smaller objects in that container works out much better than using a ZIP archive holding a few larger objects. To wit:
1. An SQLite database file is approximately the same size, and in some cases smaller, than a ZIP archive holding the same information.
2. The [atomic update capabilities](atomiccommit.md) of SQLite allow small incremental changes to be safely written into the document. This reduces total disk I/O and improves File/Save performance, enhancing the user experience.
3. Startup time is reduced by allowing the application to read in only the content shown for the initial screen. This largely eliminates the need to show a progress bar when opening a new document. The document just pops up immediately, further enhancing the user experience.
4. The memory footprint of the application can be dramatically reduced by only loading content that is relevant to the current display and keeping the bulk of the content on disk. The fast query capability of SQLite make this a viable alternative to keeping all content in memory at all times. And when applications use less memory, it makes the entire computer more responsive, further enhancing the user experience.
5. The schema of an SQL database is able to represent information more directly and succinctly than a key/value database such as a ZIP archive. This makes the document content more accessible to third-party applications and scripts and facilitates advanced features such as built-in document versioning, and incremental saving of work in progress for recovery after a crash.
These are just a few of the benefits of using SQLite as an application file format — the benefits that seem most likely to improve the user experience for applications like OpenOffice. Other applications might benefit from SQLite in different ways. See the [Application File Format](appfileformat.md) document for additional ideas.
Finally, let us reiterate that this essay is a thought experiment. The OpenDocument format is well-established and already well-designed. Nobody really believes that OpenDocument should be changed to use SQLite as its container instead of ZIP. Nor is this article a criticism of OpenDocument for not choosing SQLite as its container since OpenDocument predates SQLite. Rather, the point of this article is to use OpenDocument as a concrete example of how SQLite can be used to build better application file formats for future projects.
---
# Why Is SQLite Coded In C
*Sección: Guides | Origen: https://www.sqlite.org/whyc.html*
# 1. C Is Best
> | |
> |----|
> | Note: Sections 2.0 and 3.0 of this article were added in response to comments on [Hacker News](https://news.ycombinator.com/item?id=16585120) and [Reddit](https://www.reddit.com/r/programming/comments/84fzoc/why_is_sqlite_coded_in_c/). |
Since its inception on 2000-05-29, SQLite has been implemented in generic C. C was and continues to be the best language for implementing a software library like SQLite. There are no plans to recode SQLite in any other programming language at this time.
The reasons why C is the best language to implement SQLite include:
- Performance
- Compatibility
- Low-dependency
- Stability
## 1.1. Performance
An intensively used low-level library like SQLite needs to be fast. (And SQLite is fast, see [Internal Versus External BLOBs](intern-v-extern-blob.md) and [35% Faster Than The Filesystem](fasterthanfs.md) for examples.)
C is a great language for writing fast code. C is sometimes described as "portable assembly language". It enables developers to code as close to the underlying hardware as possible while still remaining portable across platforms.
Other programming languages sometimes claim to be "as fast as C". But no other language claims to be faster than C for general-purpose programming, because none are.
## 1.2. Compatibility
Nearly all systems have the ability to call libraries written in C. This is not true of other implementation languages.
So, for example, Android applications written in Java are able to invoke SQLite (through an adaptor). Maybe it would have been more convenient for Android if SQLite had been coded in Java as that would make the interface simpler. However, on iPhone applications are coded in Objective-C or Swift, neither of which have the ability to call libraries written in Java. Thus, SQLite would be unusable on iPhones had it been written in Java.
## 1.3. Low-Dependency
Libraries written in C do not have a huge run-time dependency. In its minimum configuration, SQLite requires only the following routines from the standard C library:
|
|
**[expr:](syntax/expr.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** hide
**[ordering-term:](syntax/ordering-term.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[filter-clause:](syntax/filter-clause.md)** hide
**[window-defn:](syntax/window-defn.md)** hide
**[frame-spec:](syntax/frame-spec.md)** hide
**[ordering-term:](syntax/ordering-term.md)** show
Unlike ordinary functions, window functions cannot use the DISTINCT keyword. Also, Window functions may only appear in the result set and in the ORDER BY clause of a SELECT statement.
Window functions come in two varieties: [aggregate window functions](windowfunctions.md#aggwinfunc) and [built-in window functions](windowfunctions.md#builtins). Every aggregate window function can also work as an ordinary aggregate function, simply by omitting the OVER and FILTER clauses. Furthermore, all of the built-in [aggregate functions](lang_aggfunc.md) of SQLite can be used as an aggregate window function by adding an appropriate OVER clause. Applications can register new aggregate window functions using the [sqlite3_create_window_function()](c3ref/create_function.md) interface. The built-in window functions, however, require special-case handling in the query planner and hence new window functions that exhibit the exceptional properties found in the built-in window functions cannot be added by the application.
Here is an example using the built-in row_number() window function:
CREATE TABLE t0(x INTEGER PRIMARY KEY, y TEXT);\
INSERT INTO t0 VALUES (1, 'aaa'), (2, 'ccc'), (3, 'bbb');\
\
*-- The following SELECT statement returns:*\
*-- *\
*-- x \| y \| row_number*\
-----------------------\
*-- 1 \| aaa \| 1 *\
*-- 2 \| ccc \| 3 *\
*-- 3 \| bbb \| 2 *\
*-- *\
SELECT x, y, row_number() OVER (ORDER BY y) AS row_number FROM t0 ORDER BY x;\
The row_number() window function assigns consecutive integers to each row in order of the "ORDER BY" clause within the window-defn (in this case "ORDER BY y"). Note that this does not affect the order in which results are returned from the overall query. The order of the final output is still governed by the ORDER BY clause attached to the SELECT statement (in this case "ORDER BY x").
Named window-defn clauses may also be added to a SELECT statement using a WINDOW clause and then referred to by name within window function invocations. For example, the following SELECT statement contains two named window-defs clauses, "win1" and "win2":
SELECT x, y, row_number() OVER **win1**, rank() OVER **win2**\
FROM t0\
WINDOW **win1** AS (ORDER BY y RANGE BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW),\
**win2** AS (PARTITION BY y ORDER BY x)\
ORDER BY x;\
The WINDOW clause, when one is present, comes after any HAVING clause and before any ORDER BY.
# 2. Aggregate Window Functions
The examples in this section all assume that the database is populated as follows:
CREATE TABLE t1(a INTEGER PRIMARY KEY, b, c);\
INSERT INTO t1 VALUES (1, 'A', 'one' ),\
(2, 'B', 'two' ),\
(3, 'C', 'three'),\
(4, 'D', 'one' ),\
(5, 'E', 'two' ),\
(6, 'F', 'three'),\
(7, 'G', 'one' );\
An aggregate window function is similar to an [ordinary aggregate function](lang_aggfunc.md), except adding it to a query does not change the number of rows returned. Instead, for each row the result of the aggregate window function is as if the corresponding aggregate were run over all rows in the "window frame" specified by the OVER clause.
*-- The following SELECT statement returns:*\
*-- *\
*-- a \| b \| group_concat*\
-------------------------\
*-- 1 \| A \| A.B *\
*-- 2 \| B \| A.B.C *\
*-- 3 \| C \| B.C.D *\
*-- 4 \| D \| C.D.E *\
*-- 5 \| E \| D.E.F *\
*-- 6 \| F \| E.F.G *\
*-- 7 \| G \| F.G *\
*-- *\
SELECT a, b, group_concat(b, '.') OVER (\
ORDER BY a ROWS BETWEEN 1 PRECEDING AND 1 FOLLOWING\
) AS group_concat FROM t1;\
In the example above, the window frame consists of all rows between the previous row ("1 PRECEDING") and the following row ("1 FOLLOWING"), inclusive, where rows are sorted according to the ORDER BY clause in the window-defn (in this case "ORDER BY a"). For example, the frame for the row with (a=3) consists of rows (2, 'B', 'two'), (3, 'C', 'three') and (4, 'D', 'one'). The result of group_concat(b, '.') for that row is therefore 'B.C.D'.
All of SQLite's [aggregate functions](lang_aggfunc.md) may be used as aggregate window functions. It is also possible to [create user-defined aggregate window functions](windowfunctions.md#udfwinfunc).
## 2.1. The PARTITION BY Clause
For the purpose of computing window functions, the result set of a query is divided into one or more "partitions". A partition consists of all rows that have the same value for all terms of the PARTITION BY clause in the window-defn. If there is no PARTITION BY clause, then the entire result set of the query is a single partition. Window-function processing is performed separately for each partition.
For example:
*-- The following SELECT statement returns:*\
*-- *\
*-- c \| a \| b \| group_concat*\
---------------------------------\
*-- one \| 1 \| A \| A.D.G *\
*-- one \| 4 \| D \| D.G *\
*-- one \| 7 \| G \| G *\
*-- three \| 3 \| C \| C.F *\
*-- three \| 6 \| F \| F *\
*-- two \| 2 \| B \| B.E *\
*-- two \| 5 \| E \| E *\
*-- *\
SELECT c, a, b, group_concat(b, '.') OVER (\
PARTITION BY c ORDER BY a RANGE BETWEEN CURRENT ROW AND UNBOUNDED FOLLOWING\
) AS group_concat\
FROM t1 ORDER BY c, a;\
In the query above, the "PARTITION BY c" clause breaks the result set up into three partitions. The first partition has three rows with c=='one'. The second partition has two rows with c=='three' and the third partition has two rows with c=='two'.
In the example above, all the rows for each partition are grouped together in the final output. This is because the PARTITION BY clause is a prefix of the ORDER BY clause on the overall query. But that does not have to be the case. A partition can be composed of rows scattered about haphazardly within the result set. For example:
*-- The following SELECT statement returns:*\
*-- *\
*-- c \| a \| b \| group_concat*\
---------------------------------\
*-- one \| 1 \| A \| A.D.G *\
*-- two \| 2 \| B \| B.E *\
*-- three \| 3 \| C \| C.F *\
*-- one \| 4 \| D \| D.G *\
*-- two \| 5 \| E \| E *\
*-- three \| 6 \| F \| F *\
*-- one \| 7 \| G \| G *\
*-- *\
SELECT c, a, b, group_concat(b, '.') OVER (\
PARTITION BY c ORDER BY a RANGE BETWEEN CURRENT ROW AND UNBOUNDED FOLLOWING\
) AS group_concat\
FROM t1 ORDER BY a;\
## 2.2. Frame Specifications
The frame-spec determines which output rows are read by an aggregate window function. The frame-spec consists of four parts:
- A frame type - either ROWS, RANGE or GROUPS,
- A starting frame boundary,
- An ending frame boundary,
- An EXCLUDE clause.
Here are the syntax details:
**[frame-spec:](syntax/frame-spec.md)** hide
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
The ending frame boundary can be omitted (if the BETWEEN and AND keywords that surround the starting frame boundary are also omitted), in which case the ending frame boundary defaults to CURRENT ROW.
If the frame type is RANGE or GROUPS, then rows with the same values for all ORDER BY expressions are considered "peers". Or, if there are no ORDER BY terms, all rows are peers. Peers are always within the same frame.
The default frame-spec is:
RANGE BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW EXCLUDE NO OTHERS\
The default means that aggregate window functions read all rows from the beginning of the partition up to and including the current row and its peers. This implies that rows that have the same values for all ORDER BY expressions will also have the same value for the result of the window function (as the window frame is the same). For example:
*-- The following SELECT statement returns:*\
*-- *\
*-- a \| b \| c \| group_concat*\
-----------------------------\
*-- 1 \| A \| one \| A.D.G *\
*-- 2 \| B \| two \| A.D.G.C.F.B.E*\
*-- 3 \| C \| three \| A.D.G.C.F *\
*-- 4 \| D \| one \| A.D.G *\
*-- 5 \| E \| two \| A.D.G.C.F.B.E*\
*-- 6 \| F \| three \| A.D.G.C.F *\
*-- 7 \| G \| one \| A.D.G *\
*-- *\
SELECT a, b, c,\
group_concat(b, '.') OVER (ORDER BY c) AS group_concat\
FROM t1 ORDER BY a;\
### 2.2.1. Frame Type
There are three frame types: ROWS, GROUPS, and RANGE. The frame type determines how the starting and ending boundaries of the frame are measured.
- **ROWS**: The ROWS frame type means that the starting and ending boundaries for the frame are determined by counting individual rows relative to the current row.
- **GROUPS**: The GROUPS frame type means that the starting and ending boundaries are determined by counting "groups" relative to the current group. A "group" is a set of rows that all have equivalent values for all terms of the window ORDER BY clause. ("Equivalent" means that the [IS operator](lang_expr.md#isisnot) is true when comparing the two values.) In other words, a group consists of all peers of a row.
- **RANGE**: The RANGE frame type requires that the ORDER BY clause of the window has exactly one term. Call that term "X". With the RANGE frame type, the elements of the frame are determined by computing the value of expression X for all rows in the partition and framing those rows for which the value of X is within a certain range of the value of X for the current row. See the description in the "[\
**[expr:](syntax/expr.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
If a FILTER clause is provided, then only rows for which the *expr* is true are included in the window frame. The aggregate window still returns a value for every row, but those for which the FILTER expression evaluates to other than true are not included in the window frame for any row. For example:
*-- The following SELECT statement returns:*\
*-- *\
*-- c \| a \| b \| group_concat*\
---------------------------------\
*-- one \| 1 \| A \| A *\
*-- two \| 2 \| B \| A *\
*-- three \| 3 \| C \| A.C *\
*-- one \| 4 \| D \| A.C.D *\
*-- two \| 5 \| E \| A.C.D *\
*-- three \| 6 \| F \| A.C.D.F *\
*-- one \| 7 \| G \| A.C.D.F.G *\
*-- *\
SELECT c, a, b, group_concat(b, '.') FILTER (WHERE c!='two') OVER (\
ORDER BY a\
) AS group_concat\
FROM t1 ORDER BY a;\
# 3. Built-in Window Functions
As well as aggregate window functions, SQLite features a set of built-in window functions based on [those supported by PostgreSQL](https://www.postgresql.org/docs/10/static/functions-window.html).
Built-in window functions honor any PARTITION BY clause in the same way as aggregate window functions - each selected row is assigned to a partition and each partition is processed separately. The ways in which any ORDER BY clause affects each built-in window function is described below. Some of the window functions (rank(), dense_rank(), percent_rank() and ntile()) use the concept of "peer groups" (rows within the same partition that have the same values for all ORDER BY expressions). In these cases, it does not matter whether the frame-spec specifies ROWS, GROUPS, or RANGE. For the purposes of built-in window function processing, rows with the same values for all ORDER BY expressions are considered peers regardless of the frame type.
Most built-in window functions ignore the frame-spec, the exceptions being first_value(), last_value() and nth_value(). It is a syntax error to specify a FILTER clause as part of a built-in window function invocation.
SQLite supports the following 11 built-in window functions:
**row_number()**
The number of the row within the current partition. Rows are numbered starting from 1 in the order defined by the ORDER BY clause in the window definition, or in arbitrary order otherwise.
**rank()**
The row_number() of the first peer in each group - the rank of the current row with gaps. If there is no ORDER BY clause, then all rows are considered peers and this function always returns 1.
**dense_rank()**
The number of the current row's peer group within its partition - the rank of the current row without gaps. Rows are numbered starting from 1 in the order defined by the ORDER BY clause in the window definition. If there is no ORDER BY clause, then all rows are considered peers and this function always returns 1.
**percent_rank()**
Despite the name, this function always returns a value between 0.0 and 1.0 equal to (*rank* - 1)/(*partition-rows* - 1), where *rank* is the value returned by built-in window function rank() and *partition-rows* is the total number of rows in the partition. If the partition contains only one row, this function returns 0.0.
**cume_dist()**
The cumulative distribution. Calculated as *row-number*/*partition-rows*, where *row-number* is the value returned by row_number() for the last peer in the group and *partition-rows* the number of rows in the partition.
**ntile(N)**
Argument *N* is handled as an integer. This function divides the partition into N groups as evenly as possible and assigns an integer between 1 and *N* to each group, in the order defined by the ORDER BY clause, or in arbitrary order otherwise. If necessary, larger groups occur first. This function returns the integer value assigned to the group that the current row is a part of.
**lag(expr)\
lag(expr, offset)\
lag(expr, offset, default)**
The first form of the lag() function returns the result of evaluating expression *expr* against the previous row in the partition. Or, if there is no previous row (because the current row is the first), NULL.
If the *offset* argument is provided, then it must be a non-negative integer. In this case the value returned is the result of evaluating *expr* against the row *offset* rows before the current row within the partition. If *offset* is 0, then *expr* is evaluated against the current row. If there is no row *offset* rows before the current row, NULL is returned.
If *default* is also provided, then it is returned instead of NULL if the row identified by *offset* does not exist.
**lead(expr)\
lead(expr, offset)\
lead(expr, offset, default)**
The first form of the lead() function returns the result of evaluating expression *expr* against the next row in the partition. Or, if there is no next row (because the current row is the last), NULL.
If the *offset* argument is provided, then it must be a non-negative integer. In this case the value returned is the result of evaluating *expr* against the row *offset* rows after the current row within the partition. If *offset* is 0, then *expr* is evaluated against the current row. If there is no row *offset* rows after the current row, NULL is returned.
If *default* is also provided, then it is returned instead of NULL if the row identified by *offset* does not exist.
**first_value(expr)**
This built-in window function calculates the window frame for each row in the same way as an aggregate window function. It returns the value of *expr* evaluated against the first row in the window frame for each row.
**last_value(expr)**
This built-in window function calculates the window frame for each row in the same way as an aggregate window function. It returns the value of *expr* evaluated against the last row in the window frame for each row.
**nth_value(expr, N)**
This built-in window function calculates the window frame for each row in the same way as an aggregate window function. It returns the value of *expr* evaluated against the row *N* of the window frame. Rows are numbered within the window frame starting from 1 in the order defined by the ORDER BY clause if one is present, or in arbitrary order otherwise. If there is no *N*th row in the partition, then NULL is returned.
The examples in this section use the [previously defined T1 table](windowfunctions.md#aggwinfunc) as well as the following T2 table:
CREATE TABLE t2(a, b);\
INSERT INTO t2 VALUES('a', 'one'),\
('a', 'two'),\
('a', 'three'),\
('b', 'four'),\
('c', 'five'),\
('c', 'six');\
The following example illustrates the behaviour of the five ranking functions - row_number(), rank(), dense_rank(), percent_rank() and cume_dist().
*-- The following SELECT statement returns:*\
*-- *\
*-- a \| row_number \| rank \| dense_rank \| percent_rank \| cume_dist*\
------------------------------------------------------------------\
*-- a \| 1 \| 1 \| 1 \| 0.0 \| 0.5*\
*-- a \| 2 \| 1 \| 1 \| 0.0 \| 0.5*\
*-- a \| 3 \| 1 \| 1 \| 0.0 \| 0.5*\
*-- b \| 4 \| 4 \| 2 \| 0.6 \| 0.66*\
*-- c \| 5 \| 5 \| 3 \| 0.8 \| 1.0*\
*-- c \| 6 \| 5 \| 3 \| 0.8 \| 1.0*\
*-- *\
SELECT a AS a,\
row_number() OVER win AS row_number,\
rank() OVER win AS rank,\
dense_rank() OVER win AS dense_rank,\
percent_rank() OVER win AS percent_rank,\
cume_dist() OVER win AS cume_dist\
FROM t2\
WINDOW win AS (ORDER BY a);\
The example below uses ntile() to divide the six rows into two groups (the ntile(2) call) and into four groups (the ntile(4) call). For ntile(2), there are three rows assigned to each group. For ntile(4), there are two groups of two and two groups of one. The larger groups of two appear first.
*-- The following SELECT statement returns:*\
*-- *\
*-- a \| b \| ntile_2 \| ntile_4*\
----------------------------------\
*-- a \| one \| 1 \| 1*\
*-- a \| two \| 1 \| 1*\
*-- a \| three \| 1 \| 2*\
*-- b \| four \| 2 \| 2*\
*-- c \| five \| 2 \| 3*\
*-- c \| six \| 2 \| 4*\
*-- *\
SELECT a AS a,\
b AS b,\
ntile(2) OVER win AS ntile_2,\
ntile(4) OVER win AS ntile_4\
FROM t2\
WINDOW win AS (ORDER BY a);\
The next example demonstrates lag(), lead(), first_value(), last_value() and nth_value(). The frame-spec is ignored by both lag() and lead(), but respected by first_value(), last_value() and nth_value().
*-- The following SELECT statement returns:*\
*-- *\
*-- b \| lead \| lag \| first_value \| last_value \| nth_value_3*\
-------------------------------------------------------------\
*-- A \| C \| NULL \| A \| A \| NULL *\
*-- B \| D \| A \| A \| B \| NULL *\
*-- C \| E \| B \| A \| C \| C *\
*-- D \| F \| C \| A \| D \| C *\
*-- E \| G \| D \| A \| E \| C *\
*-- F \| n/a \| E \| A \| F \| C *\
*-- G \| n/a \| F \| A \| G \| C *\
*-- *\
SELECT b AS b,\
lead(b, 2, 'n/a') OVER win AS lead,\
lag(b) OVER win AS lag,\
first_value(b) OVER win AS first_value,\
last_value(b) OVER win AS last_value,\
nth_value(b, 3) OVER win AS nth_value_3\
FROM t1\
WINDOW win AS (ORDER BY b ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW)\
# 4. Window Chaining
Window chaining is a shorthand that allows one window to be defined in terms of another. Specifically, the shorthand allows the new window to implicitly copy the PARTITION BY and optionally ORDER BY clauses of the base window. For example, in the following:
SELECT group_concat(b, '.') OVER (\
win ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW\
)\
FROM t1\
WINDOW win AS (PARTITION BY a ORDER BY c)\
the window used by the group_concat() function is equivalent to "PARTITION BY a ORDER BY c ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW". In order to use window chaining, all of the following must be true:
- The new window definition must not include a PARTITION BY clause. The PARTITION BY clause, if there is one, must be supplied by the base window specification.
- If the base window has an ORDER BY clause, it is copied into the new window. In this case the new window must not specify an ORDER BY clause. If the base window has no ORDER BY clause, one may be specified as part of the new window definition.
- The base window may not specify a frame specification. The frame specification can only be given in the new window specification.
The two fragments of SQL below are similar, but not entirely equivalent, as the latter will fail if the definition of window "win" contains a frame specification.
SELECT group_concat(b, '.') OVER win ...\
SELECT group_concat(b, '.') OVER (win) ...\
# 5. User-Defined Aggregate Window Functions
User-defined aggregate window functions may be created using the [sqlite3_create_window_function](c3ref/create_function.md)() API. Implementing an aggregate window function is very similar to an ordinary aggregate function. Any user-defined aggregate window function may also be used as an ordinary aggregate. To implement a user-defined aggregate window function the application must supply four callback functions:
| Callback | Description |
|----|----|
| xStep | This method is required by both window aggregate and legacy aggregate function implementations. It is invoked to add a row to the current window. The function arguments, if any, corresponding to the row being added are passed to the implementation of xStep. |
| xFinal | This method is required by both window aggregate and legacy aggregate function implementations. It is invoked to return the current value of the aggregate (determined by the contents of the current window), and to free any resources allocated by earlier calls to xStep. |
| xValue | This method is only required for window aggregate functions. The presence of this method is what distinguishes a window aggregate function from a legacy aggregate function. This method is invoked to return the current value of the aggregate. Unlike xFinal, the implementation should not delete any context. |
| xInverse | This method is only required for window aggregate functions, not legacy aggregate function implementations. It is invoked to remove the oldest presently aggregated result of xStep from the current window. The function arguments, if any, are those passed to xStep for the row being removed. |
The C code below implements a simple window aggregate function named sumint(). This works in the same way as the built-in sum() function, except that it throws an exception if passed an argument that is not an integer value.
\
*/\**\
*\*\* xStep for sumint().*\
*\*\**\
*\*\* Add the value of the argument to the aggregate context (an integer).*\
*\*/*\
static void sumintStep(\
[sqlite3_context](c3ref/context.md) \*ctx,\
int nArg,\
[sqlite3_value](c3ref/value.md) \*apArg\[\]\
){\
[sqlite3_int64](c3ref/int64.md) \*pInt;\
\
assert( nArg==1 );\
if( [sqlite3_value_type](c3ref/value_blob.md)(apArg\[0\])!=SQLITE_INTEGER ){\
[sqlite3_result_error](c3ref/result_blob.md)(ctx, "invalid argument", -1);\
return;\
}\
pInt = (sqlite3_int64\*)sqlite3_aggregate_context(ctx, sizeof([sqlite3_int64](c3ref/int64.md)));\
if( pInt ){\
\*pInt += [sqlite3_value_int64](c3ref/value_blob.md)(apArg\[0\]);\
}\
}\
\
*/\**\
*\*\* xInverse for sumint().*\
*\*\**\
*\*\* This does the opposite of xStep() - subtracts the value of the argument*\
*\*\* from the current context value. The error checking can be omitted from*\
*\*\* this function, as it is only ever called after xStep() (so the aggregate*\
*\*\* context has already been allocated) and with a value that has already*\
*\*\* been passed to xStep() without error (so it must be an integer).*\
*\*/*\
static void sumintInverse(\
[sqlite3_context](c3ref/context.md) \*ctx,\
int nArg,\
[sqlite3_value](c3ref/value.md) \*apArg\[\]\
){\
[sqlite3_int64](c3ref/int64.md) \*pInt;\
assert( [sqlite3_value_type](c3ref/value_blob.md)(apArg\[0\])==SQLITE_INTEGER );\
pInt = (sqlite3_int64\*)sqlite3_aggregate_context(ctx, sizeof([sqlite3_int64](c3ref/int64.md)));\
\*pInt -= [sqlite3_value_int64](c3ref/value_blob.md)(apArg\[0\]);\
}\
\
*/\**\
*\*\* xFinal for sumint().*\
*\*\**\
*\*\* Return the current value of the aggregate window function. Because*\
*\*\* this implementation does not allocate any resources beyond the buffer*\
*\*\* returned by [sqlite3_aggregate_context](c3ref/aggregate_context.md), which is automatically freed*\
*\*\* by the system, there are no resources to free. And so this method is*\
*\*\* identical to xValue().*\
*\*/*\
static void sumintFinal([sqlite3_context](c3ref/context.md) \*ctx){\
[sqlite3_int64](c3ref/int64.md) res = 0;\
[sqlite3_int64](c3ref/int64.md) \*pInt;\
pInt = (sqlite3_int64\*)[sqlite3_aggregate_context](c3ref/aggregate_context.md)(ctx, 0);\
if( pInt ) res = \*pInt;\
[sqlite3_result_int64](c3ref/result_blob.md)(ctx, res);\
}\
\
*/\**\
*\*\* xValue for sumint().*\
*\*\**\
*\*\* Return the current value of the aggregate window function.*\
*\*/*\
static void sumintValue([sqlite3_context](c3ref/context.md) \*ctx){\
[sqlite3_int64](c3ref/int64.md) res = 0;\
[sqlite3_int64](c3ref/int64.md) \*pInt;\
pInt = (sqlite3_int64\*)[sqlite3_aggregate_context](c3ref/aggregate_context.md)(ctx, 0);\
if( pInt ) res = \*pInt;\
[sqlite3_result_int64](c3ref/result_blob.md)(ctx, res);\
}\
\
*/\**\
*\*\* Register sumint() window aggregate with database handle db.*\
*\*/*\
int register_sumint([sqlite3](c3ref/sqlite3.md) \*db){\
return [sqlite3_create_window_function](c3ref/create_function.md)(db, "sumint", 1, SQLITE_UTF8, 0,\
sumintStep, sumintFinal, sumintValue, sumintInverse, 0\
);\
}\
\
\
The following example uses the sumint() function implemented by the above C code. For each row, the window consists of the preceding row (if any), the current row and the following row (again, if any):
CREATE TABLE t3(x, y);\
INSERT INTO t3 VALUES('a', 4),\
('b', 5),\
('c', 3),\
('d', 8),\
('e', 1);\
\
*-- Assuming the database is populated using the above script, the *\
*-- following SELECT statement returns:*\
*-- *\
*-- x \| sum_y*\
--------------\
*-- a \| 9 *\
*-- b \| 12 *\
*-- c \| 16 *\
*-- d \| 12 *\
*-- e \| 9 *\
*-- *\
SELECT x, sumint(y) OVER (\
ORDER BY x ROWS BETWEEN 1 PRECEDING AND 1 FOLLOWING\
) AS sum_y\
FROM t3 ORDER BY x;\
In processing the query above, SQLite invokes the sumint callbacks as follows:
1. **xStep(4)** - add "4" to the current window.
2. **xStep(5)** - add "5" to the current window.
3. **xValue()** - invoke xValue() to obtain the value of sumint() for the row with (x='a'). The window currently consists of values 4 and 5, and so the result is 9.
4. **xStep(3)** - add "3" to the current window.
5. **xValue()** - invoke xValue() to obtain the value of sumint() for the row with (x='b'). The window currently consists of values 4, 5 and 3, and so the result is 12.
6. **xInverse(4)** - remove "4" from the window.
7. **xStep(8)** - add "8" to the current window. The window now consists of values 5, 3 and 8.
8. **xValue()** - invoked to obtain the value for the row with (x='c'). In this case, 16.
9. **xInverse(5)** - remove value "5" from the window.
10. **xStep(1)** - add value "1" to the window.
11. **xValue()** - invoked to obtain the value for row (x='d').
12. **xInverse(3)** - remove value "3" from the window. The window now contains values 8 and 1 only.
13. **xFinal()** - invoked to reclaim any allocated resources and to obtain the value for row (x='e'). 9. .
If the user were to abandon query execution by calling sqlite3_reset() or sqlite3_finalize() on the statement handle before SQLite has called xFinal(), then xFinal() is called automatically from within the sqlite3_reset() or sqlite3_finalize() call in order to reclaim any allocated resources, even though the value is not required. In this case any error returned by the xFinal implementation is silently discarded.
# 6. History
Window function support was first added to SQLite with release [version 3.25.0](releaselog/3_25_0.md) (2018-09-15). The SQLite developers used the [PostgreSQL](http://www.postgresql.org) window function documentation as their primary reference for how window functions ought to behave. Many test cases have been run against PostgreSQL to ensure that window functions operate the same way in both SQLite and PostgreSQL.
In SQLite [version 3.28.0](releaselog/3_28_0.md) (2019-04-16), windows function support was extended to include the EXCLUDE clause, GROUPS frame types, window chaining, and support for "\
**[column-def:](syntax/column-def.md)** show
**[column-constraint:](syntax/column-constraint.md)** show
**[foreign-key-clause:](syntax/foreign-key-clause.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[conflict-clause:](syntax/conflict-clause.md)** show
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
SQLite supports a limited subset of ALTER TABLE. The ALTER TABLE command in SQLite allows these alterations of an existing table: it can be renamed; a column can be renamed; a column can be added to it; or a column can be dropped from it.
# 2. ALTER TABLE RENAME
The RENAME TO syntax changes the name of table-name to new-table-name. This command cannot be used to move a table between attached databases, only to rename a table within the same database. If the table being renamed has triggers or indices, then these remain attached to the table after it has been renamed.
> **Compatibility Note:** The behavior of ALTER TABLE when renaming a table was enhanced in versions 3.25.0 (2018-09-15) and 3.26.0 (2018-12-01) in order to carry the rename operation forward into triggers and views that reference the renamed table. This is considered an improvement. Applications that depend on the older (and arguably buggy) behavior can use the [PRAGMA legacy_alter_table=ON](pragma.md#pragma_legacy_alter_table) statement or the [SQLITE_DBCONFIG_LEGACY_ALTER_TABLE](c3ref/c_dbconfig_defensive.md#sqlitedbconfiglegacyaltertable) configuration parameter on [sqlite3_db_config()](c3ref/db_config.md) interface to make ALTER TABLE RENAME behave as it did prior to version 3.25.0.
Beginning with release 3.25.0 (2018-09-15), references to the table within trigger bodies and view definitions are also renamed.
Prior to version 3.26.0 (2018-12-01), FOREIGN KEY references to a table that is renamed were only edited with [PRAGMA foreign_keys=ON](pragma.md#pragma_foreign_keys), or in other words if [foreign key constraints](foreignkeys.md) were being enforced. With [PRAGMA foreign_keys=OFF](pragma.md#pragma_foreign_keys), FOREIGN KEY constraints would not be changed when the table that the foreign key referred to (the "[parent table](foreignkeys.md#parentchild)") was renamed. Beginning with version 3.26.0, FOREIGN KEY constraints are always converted when a table is renamed, unless the [PRAGMA legacy_alter_table=ON](pragma.md#pragma_legacy_alter_table) setting is engaged. The following table summarizes the difference:
> | PRAGMA foreign_keys | PRAGMA legacy_alter_table | [Parent Table](foreignkeys.md#parentchild) references are updated | SQLite version |
> |:--:|:--:|:--:|:--:|
> | Off | Off | No | \< 3.26.0 |
> | Off | Off | Yes | \>= 3.26.0 |
> | On | Off | Yes | all |
> | Off | On | No | all |
> | On | On | Yes | all |
# 3. ALTER TABLE RENAME COLUMN
The RENAME COLUMN TO syntax changes the column-name of table table-name into new-column-name. The column name is changed both within the table definition itself and also within all indexes, triggers, and views that reference the column. If the column name change would result in a semantic ambiguity in a trigger or view, then the RENAME COLUMN fails with an error and no changes are applied.
# 4. ALTER TABLE ADD COLUMN
The ADD COLUMN syntax is used to add a new column to an existing table. The new column is always appended to the end of the list of existing columns. The [column-def](syntax/column-def.md) rule defines the characteristics of the new column. The new column may take any of the forms permissible in a [CREATE TABLE](lang_createtable.md) statement, with the following restrictions:
- The column may not have a PRIMARY KEY or UNIQUE constraint.
- The column may not have a default value of CURRENT_TIME, CURRENT_DATE, CURRENT_TIMESTAMP, or an expression in parentheses.
- If a NOT NULL constraint is specified, then the column must have a default value other than NULL.
- If [foreign key constraints](foreignkeys.md) are [enabled](pragma.md#pragma_foreign_keys) and a column with a [REFERENCES clause](syntax/foreign-key-clause.md) is added, the column must have a default value of NULL.
- The column may not be [GENERATED ALWAYS ... STORED](gencol.md), though VIRTUAL columns are allowed.
When adding a column with a [CHECK constraint](lang_createtable.md#ckconst), or a NOT NULL constraint on a [generated column](gencol.md), the added constraints are tested against all preexisting rows in the table and the ADD COLUMN fails if any constraint fails. The testing of added constraints against preexisting rows is a new enhancement as of SQLite version 3.37.0 (2021-11-27).
The ALTER TABLE command works by modifying the SQL text of the schema stored in the [sqlite_schema table](schematab.md). No changes are made to table content for renames or column addition without constraints. Because of this, the execution time of such ALTER TABLE commands is independent of the amount of data in the table and such commands will run as quickly on a table with 10 million rows as on a table with 1 row. When adding new columns that have CHECK constraints, or adding generated columns with NOT NULL constraints, or when deleting columns, then all existing data in the table must be either read (to test new constraints against existing rows) or written (to remove deleted columns). In those cases, the ALTER TABLE command takes time that is proportional to the amount of content in the table being altered.
After ADD COLUMN has been run on a database, that database will not be readable by SQLite version 3.1.3 (2005-02-20) and earlier.
# 5. ALTER TABLE DROP COLUMN
The DROP COLUMN syntax is used to remove an existing column from a table. The DROP COLUMN command removes the named column from the table, and rewrites its content to purge the data associated with that column. The DROP COLUMN command only works if the column is not referenced by any other parts of the schema and is not a PRIMARY KEY and does not have a UNIQUE constraint. Possible reasons why the DROP COLUMN command can fail include:
- The column is a PRIMARY KEY or part of one.
- The column has a UNIQUE constraint.
- The column is indexed.
- The column is named in the WHERE clause of a [partial index](partialindex.md).
- The column is named in a table or column [CHECK constraint](lang_createtable.md#ckconst) not associated with the column being dropped.
- The column is used in a [foreign key constraint](foreignkeys.md).
- The column is used in the expression of a [generated column](gencol.md).
- The column appears in a trigger or view.
## 5.1. How It Works
SQLite stores the schema as plain text in the [sqlite_schema table](schematab.md). All ALTER TABLE commands modify that text and then attempt to reparse the entire schema. The command is only successful if the schema is still valid after the text has been modified. In the case of the DROP COLUMN command, the only text modified is that the column definition is removed from the CREATE TABLE statement. The DROP COLUMN command will fail if there are any traces of the column in other parts of the schema that will prevent the schema from parsing after the CREATE TABLE statement has been modified.
# 6. ALTER TABLE ALTER COLUMN
The ability to set or drop NOT NULL constraints from a column using the ALTER TABLE ALTER COLUMN syntax was added in SQLite 3.53.0 (2026-04-09).
The "ALTER TABLE *tabname* ALTER *column* SET NOT NULL" command will not add a redundant NOT NULL constraint. If the column is already NOT NULL, then SET NOT NULL is a no-op. However, it is possible to specify a column with redundant NOT NULL constraints using CREATE TABLE. If a single column already has two or more NOT NULL constraints, the "ALTER TABLE *tabname* ALTER *column* DROP NOT NULL" command is guaranteed to remove one or more of them, but not necessarily all of them.
# 7. Disable Error Checking Using PRAGMA writable_schema=ON
ALTER TABLE will normally fail and make no changes if it encounters any entries in the [sqlite_schema table](schematab.md) that do not parse. For example, if there is a malformed VIEW or TRIGGER associated with table named "tbl1", then an attempt to rename "tbl1" to "tbl1neo" will fail because the associated views and triggers could not be parsed.
Beginning with SQLite 3.38.0 (2022-02-22), this error checking can be disabled by setting "[PRAGMA writable_schema=ON;](pragma.md#pragma_writable_schema)". When the schema is writable, ALTER TABLE silently ignores any rows of the sqlite_schema table that do not parse.
# 8. Making Other Kinds Of Table Schema Changes
The only schema altering commands directly supported by SQLite are the "[rename table](lang_altertable.md#altertabrename)", "[rename column](lang_altertable.md#altertabmvcol)", "[add column](lang_altertable.md#altertabaddcol)", "[drop column](lang_altertable.md#altertabdropcol)" commands shown above. However, applications can make other arbitrary changes to the format of a table using a simple sequence of operations. The steps to make arbitrary changes to the schema design of some table X are as follows:
1. If foreign key constraints are enabled, disable them using [PRAGMA foreign_keys=OFF](pragma.md#pragma_foreign_keys).
2. Start a transaction.
3. Remember the format of all indexes, triggers, and views associated with table X. This information will be needed in step 8 below. One way to do this is to run a query like the following: SELECT type, sql FROM sqlite_schema WHERE tbl_name='X'.
4. Use [CREATE TABLE](lang_createtable.md) to construct a new table "new_X" that is in the desired revised format of table X. Make sure that the name "new_X" does not collide with any existing table name, of course.
5. Transfer content from X into new_X using a statement like: INSERT INTO new_X SELECT ... FROM X.
6. Drop the old table X: [DROP TABLE X](lang_droptable.md).
7. Change the name of new_X to X using: ALTER TABLE new_X RENAME TO X.
8. Use [CREATE INDEX](lang_createindex.md), [CREATE TRIGGER](lang_createtrigger.md), and [CREATE VIEW](lang_createview.md) to reconstruct indexes, triggers, and views associated with table X. Perhaps use the old format of the triggers, indexes, and views saved from step 3 above as a guide, making changes as appropriate for the alteration.
9. If any views refer to table X in a way that is affected by the schema change, then drop those views using [DROP VIEW](lang_dropview.md) and recreate them with whatever changes are necessary to accommodate the schema change using [CREATE VIEW](lang_createview.md).
10. If foreign key constraints were originally enabled then run [PRAGMA foreign_key_check](pragma.md#pragma_foreign_key_check) to verify that the schema change did not break any foreign key constraints.
11. Commit the transaction started in step 2.
12. If foreign keys constraints were originally enabled, reenable them now.
**Caution:** Take care to follow the procedure above precisely. The boxes below summarize two procedures for modifying a table definition. At first glance, they both appear to accomplish the same thing. However, the procedure on the right does not always work, especially with the enhanced [rename table](lang_altertable.md#altertabrename) capabilities added by versions 3.25.0 and 3.26.0. In the procedure on the right, the initial rename of the table to a temporary name might corrupt references to that table in triggers, views, and foreign key constraints. The safe procedure on the left constructs the revised table definition using a new temporary name, then renames the table into its final name, which does not break links.
|
|
| ↑ Correct |
↑ Incorrect |
The ANALYZE command gathers statistics about tables and indices and stores the collected information in [internal tables](fileformat2.md#intschema) of the database where the query optimizer can access the information and use it to help make better query planning choices. If no arguments are given, the main database and all attached databases are analyzed. If a schema name is given as the argument, then all tables and indices in that one database are analyzed. If the argument is a table name, then only that table and the indices associated with that table are analyzed. If the argument is an index name, then only that one index is analyzed.
# 2. Recommended usage patterns
The use of ANALYZE is never required. However, if an application makes complex queries that have many possible query plans, the query planner will be better able to pick the best plan if ANALYZE has been run. This can result in significant performance improvements for some queries.
Two recommended approaches for when and how to run ANALYZE are described in the next subsections, in order of preference.
## 2.1. Periodically run "PRAGMA optimize"
The [PRAGMA optimize](pragma.md#pragma_optimize) command will automatically run ANALYZE when needed. Suggested use:
1. Applications with short-lived database connections should run "PRAGMA optimize;" once, just prior to closing each database connection.
2. Applications that use long-lived database connections should run "PRAGMA optimize=0x10002;" when the connection is first opened, and then also run "PRAGMA optimize;" periodically, perhaps once per day, or more if the database is evolving rapidly.
3. All applications should run "PRAGMA optimize;" after a schema change, especially after one or more [CREATE INDEX](lang_createindex.md) statements.
The [PRAGMA optimize](pragma.md#pragma_optimize) command is usually a no-op but it will occasionally run one or more ANALYZE subcommands on individual tables of the database if doing so will be useful to the query planner. Since SQLite version 3.46.0 (2024-05-23), the "PRAGMA optimize" command automatically limits the scope of ANALYZE subcommands so that the overall "PRAGMA optimize" command completes quickly even on enormous databases. There is no need to use [PRAGMA analysis_limit](pragma.md#pragma_analysis_limit). This is the recommended way of running ANALYZE moving forward.
The [PRAGMA optimize](pragma.md#pragma_optimize) command will normally only consider running ANALYZE on tables that have been previously queried by the same database connection or that do not have entries in the [sqlite_stat1](fileformat2.md#stat1tab) table. However, if the 0x10000 bit is added to the argument, PRAGMA optimize will examine all tables to see if they can benefit from ANALYZE, not just those that have been recently queried. There is no query history when a database connection first opens, and that is why adding the 0x10000 bit is recommended when running PRAGMA optimize on a fresh database connection.
See the [Automatically Running ANALYZE](lang_analyze.md#autoanalyze) and [Approximate ANALYZE For Large Databases](lang_analyze.md#approx) sections below for additional information.
## 2.2. Fixed results of ANALYZE
Running ANALYZE can cause SQLite to choose different query plans for subsequent queries. This is almost always a positive thing, as the query plans chosen after ANALYZE will in nearly every case be better than the query plans picked before ANALYZE. That is the whole point of ANALYZE. But there can be no proof of running ANALYZE will always be beneficial. One can construct pathological cases where running ANALYZE could make some subsequent queries run slower.
Some developers prefer that once the design of an application is frozen, SQLite will always pick the same query plans as it did during development and testing. Then if millions of copies of the application are shipped to customers, the developers are assured that all of those millions of copies are running the same query plans regardless of what data the individual customers insert into their particular databases. This can help in reproducing complaints of performance problems coming back from the field.
To achieve this objection, never run a full ANALYZE nor the "PRAGMA optimize" command in the application. Rather, only run ANALYZE during development, manually using the [command-line interface](cli.md) or similar, on a test database that is similar in size and content to live databases. Then capture the result of this one-time ANALYZE using a script like the following:
.mode list\
SELECT \
'ANALYZE sqlite_schema;' \|\|\
'DELETE FROM sqlite_stat1;' \|\|\
'INSERT INTO sqlite_stat1(tbl,idx,stat)VALUES' \|\|\
(SELECT group_concat(format('(%Q,%Q,%Q)',tbl,idx,stat),',')\
FROM sqlite_stat1) \|\|\
';ANALYZE sqlite_schema;';\
When creating a new instance of the database in deployed instances of the application, or perhaps every time the application is started up in the case of long-running applications, run the commands generated by script above. This will populate the [sqlite_stat1](fileformat2.md#stat1tab) table exactly as it was during development and testing and ensure that the query plans selected in the field are same as those selected during testing in the lab. Maybe copy/paste the string generated by the script above into a static string constant named "zStat1Init" and then invoke:
sqlite3_exec(db, zStat1Init, 0, 0, 0);\
Perhaps also add "BEGIN;" at the start of the string constant and "COMMIT;" at the end, depending on the context in which the script is run.
See the [query planner stability guarantee](queryplanner-ng.md#qpstab) for addition information.
# 3. Details
The default implementation stores all statistics in a single table named "[sqlite_stat1](fileformat2.md#stat1tab)". If SQLite is compiled with the [SQLITE_ENABLE_STAT4](compile.md#enable_stat4) option, then additional histogram data is collected and stored in [sqlite_stat4](fileformat2.md#stat4tab). Older versions of SQLite would make use of the [sqlite_stat2](fileformat2.md#stat2tab) table or [sqlite_stat3](fileformat2.md#stat3tab) table when compiled with [SQLITE_ENABLE_STAT2](compile.md#enable_stat2) or [SQLITE_ENABLE_STAT3](compile.md#enable_stat3), but all recent versions of SQLite ignore the sqlite_stat2 and sqlite_stat3 tables. Future enhancements may create additional [internal tables](fileformat2.md#intschema) with the same name pattern except with final digit larger than "4". All of these tables are collectively referred to as "statistics tables".
The content of the statistics tables can be queried using [SELECT](lang_select.md) and can be changed using the [DELETE](lang_delete.md), [INSERT](lang_insert.md), and [UPDATE](lang_update.md) commands. The [DROP TABLE](lang_droptable.md) command works on statistics tables as of SQLite version 3.7.9. (2011-11-01) The [ALTER TABLE](lang_altertable.md) command does not work on statistics tables. Appropriate care should be used when changing the content of the statistics tables as invalid content can cause SQLite to select inefficient query plans. Generally speaking, one should not modify the content of the statistics tables by any mechanism other than invoking the ANALYZE command. See "[Manual Control Of Query Plans Using SQLITE_STAT Tables](optoverview.md#manctrl)" for further information.
Statistics gathered by ANALYZE are not updated as the content of the database changes. If the content of the database changes significantly, or if the database schema changes, then one should consider rerunning the ANALYZE command in order to update the statistics.
The query planner loads the content of the statistics tables into memory when the schema is read. Hence, when an application changes the statistics tables directly, SQLite will not immediately notice the changes. An application can force the query planner to reread the statistics tables by running **ANALYZE sqlite_schema**.
# 4. Automatically Running ANALYZE
The [PRAGMA optimize](pragma.md#pragma_optimize) command will automatically run ANALYZE on individual tables on an as-needed basis. The recommended practice is for applications to invoke the [PRAGMA optimize](pragma.md#pragma_optimize) statement just before closing each database connection. Or, if the application keeps a single database connection open for a long time, then it should run "PRAGMA optimize=0x10002" when the connection is first opened and run "PRAGMA optimize;" periodically thereafter, perhaps once per day or even once per hour.
Each SQLite [database connection](c3ref/sqlite3.md) records cases when the query planner would benefit from having accurate results of ANALYZE at hand. These records are held in memory and accumulate over the life of a database connection. The [PRAGMA optimize](pragma.md#pragma_optimize) command looks at those records and runs ANALYZE on only those tables for which new or updated ANALYZE data seems likely to be useful. In most cases [PRAGMA optimize](pragma.md#pragma_optimize) will not run ANALYZE, but it will occasionally do so either for tables that have never before been analyzed, or for tables that have grown significantly since they were last analyzed.
Since the actions of [PRAGMA optimize](pragma.md#pragma_optimize) are determined to some extent by prior queries that have been evaluated on the same database connection, it is recommended that [PRAGMA optimize](pragma.md#pragma_optimize) be deferred until the database connection is closing and has thus had an opportunity to accumulate as much usage information as possible. It is also reasonable to set a timer to run [PRAGMA optimize](pragma.md#pragma_optimize) every few hours, or every few days, for database connections that stay open for a long time. When running [PRAGMA optimize](pragma.md#pragma_optimize) immediately after a database connection is opened, one can add the 0x10000 bit to the bitmask argument (thus making the command read "PRAGMA optimize=0x10002") which causes all tables to be examined, even tables that have not been queried during the current connection.
The [PRAGMA optimize](pragma.md#pragma_optimize) command was first introduced with SQLite 3.18.0 (2017-03-28) and is a no-op for all prior releases of SQLite. The [PRAGMA optimize](pragma.md#pragma_optimize) command was significantly enhanced in SQLite 3.46.0 (2024-05-23) and the advice given in this documentation is based on those enhancements. Applications that use earlier versions of SQLite should consult the corresponding documentation for better advice on the best ways to use PRAGMA optimize.
# 5. Approximate ANALYZE For Large Databases
By default, ANALYZE does a full scan of every index. This can be slow for large databases. So beginning with SQLite version 3.32.0 (2020-05-22), the [PRAGMA analysis_limit](pragma.md#pragma_analysis_limit) command can be used to limit the amount of scanning performed by ANALYZE, and thus help ANALYZE to run faster, even on very large database files. We call this running an "approximate ANALYZE".
The recommended usage pattern for the [analysis_limit](pragma.md#pragma_analysis_limit) pragma is like this:
PRAGMA analysis_limit=1000;\
This pragma tells the ANALYZE command to start a full scan of the index as it normally would. But when the number of rows visited reaches 1000 (or whatever other limit is specified by the pragma), the ANALYZE command will begin taking actions to stop the scan. If the left-most column of the index has changed at least once during the previous 1000 steps, then the analysis stops immediately. But if the left-most column has always been the same, then ANALYZE skips ahead to the first entry with a different left-most column and reads an additional 1000 rows before terminating.
The details of the effects of the analysis limit described in the previous paragraph are subject to change in future versions of SQLite. But the core idea will remain the same. An analysis limit of N will strive to limit the number of rows visited in each index to approximately N.
Values of N between 100 and 1000 are recommended. Or, to disable the analysis limit, causing ANALYZE to do a complete scan of each index, set the analysis limit to 0. The default value for the analysis limit is 0 for backwards compatibility.
The values placed in the sqlite_stat1 table by an approximate ANALYZE are not exactly the same as what would be computed by an unrestricted analysis. But they are usually close enough. The index statistics in the sqlite_stat1 table are approximations in any case, so the fact that the results of an approximate ANALYZE are slightly different from a traditional full scan ANALYZE has little practical impact. It is possible to construct a pathological case where an approximate ANALYZE is noticeably inferior to a full-scan ANALYZE, but such cases are rare in real-world problems.
A good rule of thumb seems to be to always set "PRAGMA analysis_limit=N" for N between 100 and 1000 prior to running either "ANALYZE". It used to be that this was also recommended prior to running "[PRAGMA optimize](pragma.md#pragma_optimize)", but since version 3.46.0 (2024-05-23) that happens automatically. The results are not quite as precise when using PRAGMA analysis_limit, but they are precise enough, and the fact that the results are computed so much faster means that developers are more likely to compute them. An approximate ANALYZE is better than not running ANALYZE at all.
## 5.1. Limitations of approximate ANALYZE
The content in the sqlite_stat4 table cannot be computed with anything less than a full scan. Hence, if a non-zero analysis limit is specified, the sqlite_stat4 table is not computed.
---
# ATTACH DATABASE
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_attach.html*
# 1. Overview
**[attach-stmt:](syntax/attach-stmt.md)** hide
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
The ATTACH DATABASE statement adds another database file to the current [database connection](c3ref/sqlite3.md). Database files that were previously attached can be removed using the [DETACH DATABASE](lang_detach.md) command.
# 2. Details
The filename for the database to be attached is the value of the expression that occurs before the AS keyword. The filename of the database follows the same semantics as the filename argument to [sqlite3_open()](c3ref/open.md) and [sqlite3_open_v2()](c3ref/open.md); the special name "[:memory:](inmemorydb.md)" results in an [in-memory database](inmemorydb.md) and an empty string results in a new temporary database. The filename argument can be a [URI filename](uri.md) if URI filename processing is enabled on the database connection. The default behavior is for URI filenames to be disabled, however that might change in a future release of SQLite, so application developers are advised to plan accordingly.
The name that occurs after the AS keyword is the name of the database used internally by SQLite. The schema-names 'main' and 'temp' refer to the main database and the database used for temporary tables. The main and temp databases cannot be attached or detached.
Attached databases use the same VFS as the main database unless another VFS is specified using the `vfs=NAME` URI flag.
Tables in an attached database can be referred to using the syntax *schema-name.table-name*. If the name of the table is unique across all attached databases and the main and temp databases, then the *schema-name* prefix is not required. If two or more tables in different databases have the same name and the *schema-name* prefix is not used on a table reference, then the table chosen is the one in the database that was least recently attached.
Transactions involving multiple attached databases are atomic, assuming that the main database is not "[:memory:](inmemorydb.md)" and the [journal_mode](pragma.md#pragma_journal_mode) is not [WAL](wal.md). If the main database is ":memory:" or if the journal_mode is WAL, then transactions continue to be atomic within each individual database file. But if the host computer crashes in the middle of a [COMMIT](lang_transaction.md) where two or more database files are updated, some of those files might get the changes where others might not.
There is a limit, set using [sqlite3_limit()](c3ref/limit.md) and [SQLITE_LIMIT_ATTACHED](c3ref/c_limit_attached.md#sqlitelimitattached), to the number of databases that can be simultaneously attached to a single database connection.
---
# Built-in Aggregate Functions
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_aggfunc.html*
# 1. Syntax
**[aggregate-function-invocation:](syntax/aggregate-function-invocation.md)** hide
**[expr:](syntax/expr.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
The aggregate functions shown below are available by default. There are two more aggregates grouped with the [JSON SQL functions](json1.md). Applications can define custom aggregate functions using the [sqlite3_create_function()](c3ref/create_function.md) interface.
In any aggregate function that takes a single argument, that argument can be preceded by the keyword DISTINCT. In such cases, duplicate elements are filtered before being passed into the aggregate function. For example, the function "count(distinct X)" will return the number of distinct values of column X instead of the total number of non-null values in column X.
If a FILTER clause is provided, then only rows for which the *expr* is true are included in the aggregate.
If an ORDER BY clause is provided, that clause determines the order in which the inputs to the aggregate are processed. For aggregate functions like max() and count(), the input order does not matter. But for things like [string_agg()](lang_aggfunc.md#group_concat) and [json_group_object()](json1.md#jgroupobject), the ORDER BY clause will make a difference in the result. If no ORDER BY clause is specified, the inputs to the aggregate occur in an arbitrary order that might change from one invocation to the next.
See also: [scalar functions](lang_corefunc.md) and [window functions](windowfunctions.md).
# 2. List of built-in aggregate functions
- [avg(X)](lang_aggfunc.md#avg)
- [count(\*)](lang_aggfunc.md#count)
- [count(X)](lang_aggfunc.md#count)
- [group_concat(X)](lang_aggfunc.md#group_concat)
- [group_concat(X,Y)](lang_aggfunc.md#group_concat)
- [max(X)](lang_aggfunc.md#max_agg)
- [median(X)](lang_aggfunc.md#median)
- [min(X)](lang_aggfunc.md#min_agg)
- [percentile(Y,P)](lang_aggfunc.md#percentile)
- [percentile_cont(Y,P)](lang_aggfunc.md#percentile_cont)
- [percentile_disc(Y,P)](lang_aggfunc.md#percentile_disc)
- [string_agg(X,Y)](lang_aggfunc.md#group_concat)
- [sum(X)](lang_aggfunc.md#sumunc)
- [total(X)](lang_aggfunc.md#sumunc)
# 3. Descriptions of built-in aggregate functions
**avg(*X*)**
The avg() function returns the average value of all non-NULL *X* within a group. String and BLOB values that do not look like numbers are interpreted as 0. The result of avg() is always a floating point value whenever there is at least one non-NULL input even if all inputs are integers. The result of avg() is NULL if there are no non-NULL inputs. The result of avg() is computed as [total()](lang_aggfunc.md#sumunc)/[count()](lang_aggfunc.md#count) so all of the constraints that apply to [total()](lang_aggfunc.md#sumunc) also apply to avg().
**count(*X*)\
count(\*)**
The count(X) function returns a count of the number of times that *X* is not NULL in a group. The count(\*) function (with no arguments) returns the total number of rows in the group.
**group_concat(*X*)\
group_concat(*X*,*Y*)\
string_agg(*X*,*Y*)**
The group_concat() function returns a string which is the concatenation of all non-NULL values of *X*. If parameter *Y* is present then it is used as the separator between instances of *X*. A comma (",") is used as the separator if *Y* is omitted.
The string_agg(X,Y) function is an alias for group_concat(X,Y). String_agg() is compatible with PostgreSQL and SQL-Server and group_concat() is compatible with MySQL.
The order of the concatenated elements is arbitrary unless an ORDER BY argument is included immediately after the last parameter.
**max(*X*)**
The max() aggregate function returns the maximum value of all values in the group. The maximum value is the value that would be returned last in an ORDER BY on the same column. Aggregate max() returns NULL if and only if there are no non-NULL values in the group.
**median(*X*)**
The median() function returns the median value of all non-NULL *X* within a group. The median(X) function is equivalent to [percentile_cont(X,0.5)](lang_aggfunc.md#percentile_cont). See separate documentation on the [percentile extension](percentile.md) for additional information.
The median() function is available since SQLite version 3.51.0 (2025-11-04) if [the amalgamation](amalgamation.md) is compiled using [-DSQLITE_ENABLE_PERCENTILE](compile.md#enable_percentile), or as a [loadable extension](loadext.md) in prior versions of SQLite.
**min(*X*)**
The min() aggregate function returns the minimum non-NULL value of all values in the group. The minimum value is the first non-NULL value that would appear in an ORDER BY of the column. Aggregate min() returns NULL if and only if there are no non-NULL values in the group.
**percentile(*Y*,*P*)**
The percentile(Y,P) aggregate function computes an answer X which is a value that is greater than or equal to P percent of the non-NULL inputs and which is less than or equal to 100-P percent of the inputs. The parameter P must be a number between 0.0 and 100.0. The value of P must be the same for all terms of the aggregate and may not be NULL. Y inputs must be either NULL or numeric. NULL values for Y are ignored. Any non-NULL Y input that is not numeric causes an error to be raised.
The percentile(Y,P) function is equivalent to [percentile_cont(Y,p/100.0)](lang_aggfunc.md#percentile_cont). See separate documentation on the [percentile extension](percentile.md) for additional information.
The percentile() function is available since SQLite version 3.51.0 (2025-11-04) if [the amalgamation](amalgamation.md) is compiled using [-DSQLITE_ENABLE_PERCENTILE](compile.md#enable_percentile), or as a [loadable extension](loadext.md) in prior versions of SQLite.
**percentile_cont(*Y*,*P*)**
The percentile(Y,P) aggregate function computes an answer X which is a value that is greater than or equal to fraction P of the non-NULL inputs and which is less than or equal to fraction 1.0-P of the inputs. The parameter P must be a number between 0.0 and 1.0. The value of P must be the same for all terms of the aggregate and may not be NULL. Y inputs must be either NULL or numeric. NULL values for Y are ignored. Any non-NULL Y input that is not numeric causes an error to be raised. The percentile_cont(Y,P) function works like [percentile(Y,P)](lang_aggfunc.md#percentile) except that the P value spans the range of 0.0 to 1.0 instead of 0.0 to 100.0. Thus the result of percentile_cont(Y,P) is the same as [percentile(Y,P\*100)](lang_aggfunc.md#percentile). See separate documentation on the [percentile extension](percentile.md) for additional information.
The percentile_cont() function is available since SQLite version 3.51.0 (2025-11-04) if [the amalgamation](amalgamation.md) is compiled using [-DSQLITE_ENABLE_PERCENTILE](compile.md#enable_percentile), or as a [loadable extension](loadext.md) in prior versions of SQLite.
**percentile_disc(*Y*,*P*)**
The percentile_disc(Y,P) function works like [percentile_cont(Y,P)](lang_aggfunc.md#percentile_cont) except that instead of doing a weighted average of the closest available inputs, it always returns a value that is one of the input values - the smaller of the two possible choices. See separate documentation on the [percentile extension](percentile.md) for additional information.
The percentile_cont() function is available since SQLite version 3.51.0 (2025-11-04) if [the amalgamation](amalgamation.md) is compiled using [-DSQLITE_ENABLE_PERCENTILE](compile.md#enable_percentile), or as a [loadable extension](loadext.md) in prior versions of SQLite.
**sum(*X*)\
total(*X*)**
The sum() and total() aggregate functions return the sum of all non-NULL values in the group. If there are no non-NULL input rows then sum() returns NULL but total() returns 0.0. NULL is not normally a helpful result for the sum of no rows but the SQL standard requires it and most other SQL database engines implement sum() that way so SQLite does it in the same way in order to be compatible. The non-standard total() function is provided as a convenient way to work around this design problem in the SQL language.
The result of total() is always a floating point value. The result of sum() is an integer value if all non-NULL inputs are integers. If any input to sum() is neither an integer nor a NULL, then sum() returns a floating point value which is an approximation of the mathematical sum.
Sum() will throw an "integer overflow" exception if all inputs are integers or NULL and an integer overflow occurs at any point during the computation. No overflow error is ever raised if any prior input was a floating point value. Total() never throws an integer overflow.
When summing floating-point values, if the magnitudes of the values differ wildly then the resulting sum might be imprecise due to the fact that [IEEE 754 floating point values are approximations](floatingpoint.md#fpapprox). Use the decimal_sum(X) aggregate in the [decimal extension](floatingpoint.md#decext) to obtain an exact summation of floating point numbers. Consider this test case:
> \
> CREATE TABLE t1(x REAL);\
> INSERT INTO t1 VALUES(1.55e+308),(1.23),(3.2e-16),(-1.23),(-1.55e308);\
> SELECT sum(x), decimal_sum(x) FROM t1;\
The large values ±1.55e+308 cancel each other out, but the cancellation does not occur until the end of the sum and in the meantime the large +1.55e+308 swamps the tiny 3.2e-16 value. The end result is an imprecise result for the sum(). The decimal_sum() aggregate generates an exact answer, at the cost of additional CPU and memory usage. Note also that decimal_sum() is not built into the SQLite core; it is a [loadable extension](loadext.md).
If sum of inputs is too large to represent as a IEEE 754 floating point value, then a +Infinity or -Infinity result may be returned. If very large values with differing signs are used such that the SUM() or TOTAL() function is unable to determine if the correct result is +Infinity or -Infinity or some other value in between, then the result is NULL. Hence, for example, the following query returns NULL:
> \
> WITH t1(x) AS (VALUES(1.0),(-9e+999),(2.0),(+9e+999),(3.0))\
> SELECT sum(x) FROM t1;\
---
# Built-In Mathematical SQL Functions
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_mathfunc.html*
# 1. Overview
The math functions shown below are a subgroup of [scalar functions](lang_corefunc.md) that are built into the [SQLite amalgamation source file](amalgamation.md) but are only active if the amalgamation is compiled using the [-DSQLITE_ENABLE_MATH_FUNCTIONS](compile.md#enable_math_functions) compile-time option.
The arguments to math functions can be integers, floating-point numbers, or strings that look like integers or real numbers. If any argument is NULL or a blob or a string that is not readily converted into a number, then the function will return NULL. These functions also return NULL for domain errors, such as trying to take the square root of a negative number, or compute the arccosine of a value greater than 1.0 or less than -1.0.
The values returned by these functions are often approximations. For example, the [pi()](lang_mathfunc.md#pi) function returns 3.141592653589793115997963468544185161590576171875 which is about 1.22465e-16 too small, but it is the closest approximation available for IEEE754 doubles.
- [acos(X)](lang_mathfunc.md#acos)
- [acosh(X)](lang_mathfunc.md#acosh)
- [asin(X)](lang_mathfunc.md#asin)
- [asinh(X)](lang_mathfunc.md#asinh)
- [atan(X)](lang_mathfunc.md#atan)
- [atan2(Y,X)](lang_mathfunc.md#atan2)
- [atanh(X)](lang_mathfunc.md#atanh)
- [ceil(X)](lang_mathfunc.md#ceil)
- [ceiling(X)](lang_mathfunc.md#ceil)
- [cos(X)](lang_mathfunc.md#cos)
- [cosh(X)](lang_mathfunc.md#cosh)
- [degrees(X)](lang_mathfunc.md#degrees)
- [exp(X)](lang_mathfunc.md#exp)
- [floor(X)](lang_mathfunc.md#floor)
- [ln(X)](lang_mathfunc.md#ln)
- [log(B,X)](lang_mathfunc.md#log)
- [log(X)](lang_mathfunc.md#log)
- [log10(X)](lang_mathfunc.md#log)
- [log2(X)](lang_mathfunc.md#log2)
- [mod(X,Y)](lang_mathfunc.md#mod)
- [pi()](lang_mathfunc.md#pi)
- [pow(X,Y)](lang_mathfunc.md#pow)
- [power(X,Y)](lang_mathfunc.md#pow)
- [radians(X)](lang_mathfunc.md#radians)
- [sin(X)](lang_mathfunc.md#sin)
- [sinh(X)](lang_mathfunc.md#sinh)
- [sqrt(X)](lang_mathfunc.md#sqrt)
- [tan(X)](lang_mathfunc.md#tan)
- [tanh(X)](lang_mathfunc.md#tanh)
- [trunc(X)](lang_mathfunc.md#trunc)
# 2. Descriptions of built-in scalar SQL math functions
**acos(*X*)**
Return the arccosine of X. The result is in radians.
**acosh(*X*)**
Return the hyperbolic arccosine of X.
**asin(*X*)**
Return the arcsine of X. The result is in radians.
**asinh(*X*)**
Return the hyperbolic arcsine of X.
**atan(*X*)**
Return the arctangent of X. The result is in radians.
**atan2(*Y*,*X*)**
Return the arctangent of Y/X. The result is in radians. The result is placed into correct quadrant depending on the signs of X and Y.
**atanh(*X*)**
Return the hyperbolic arctangent of X.
**ceil(*X*)\
ceiling(*X*)**
Return the first representable integer value greater than or equal to X. For positive values of X, this routine rounds away from zero. For negative values of X, this routine rounds toward zero.
**cos(*X*)**
Return the cosine of X. X is in radians.
**cosh(*X*)**
Return the hyperbolic cosine of X.
**degrees(*X*)**
Convert value X from radians into degrees.
**exp(*X*)**
Compute *e* (Euler's number, approximately 2.71828182845905) raised to the power X.
**floor(*X*)**
Return the first representable integer value less than or equal to X. For positive numbers, this function rounds toward zero. For negative numbers, this function rounds away from zero.
**ln(*X*)**
Return the natural logarithm of X.
**log(*X*)\
log10(*X*)\
log(*B*,*X*)**
Return the base-10 logarithm for X. Or, for the two-argument version, return the base-B logarithm of X.
Compatibility note: SQLite works like PostgreSQL in that the log() function computes a base-10 logarithm. Most other SQL database engines compute a natural logarithm for log(). In the two-argument version of log(B,X), the first argument is the base and the second argument is the operand. This is the same as in PostgreSQL and MySQL, but is reversed from SQL Server which uses the second argument as the base and the first argument as the operand.
**log2(*X*)**
Return the logarithm base-2 for the number X.
**mod(*X*,*Y*)**
Return the remainder after dividing X by Y. This is similar to the '%' operator, except that it works for non-integer arguments.
**pi()**
Return an approximation for π.
**pow(*X*,*Y*)\
power(*X*,*Y*)**
Compute X raised to the power Y.
**radians(*X*)**
Convert X from degrees into radians.
**sin(*X*)**
Return the sine of X. X is in radians.
**sinh(*X*)**
Return the hyperbolic sine of X.
**sqrt(*X*)**
Return the square root of X. NULL is returned if X is negative.
**tan(*X*)**
Return the tangent of X. X is in radians.
**tanh(*X*)**
Return the hyperbolic tangent of X.
**trunc(*X*)**
Return the representable integer in between X and 0 (inclusive) that is furthest away from zero. Or, in other words, return the integer part of X, rounding toward zero. The trunc() function is similar to [ceiling(X)](lang_mathfunc.md#ceil) and [floor(X)](lang_mathfunc.md#floor) except that it always rounds toward zero whereas ceiling(X) and floor(X) round up and down, respectively.
---
# Built-In Scalar SQL Functions
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_corefunc.html*
# 1. Overview
The core functions shown below are available by default. [Date & Time functions](lang_datefunc.md), [aggregate functions](lang_aggfunc.md), [window functions](windowfunctions.md), [math functions](lang_mathfunc.md), and [JSON functions](json1.md) are documented separately. An application may define additional functions written in C and added to the database engine using the [sqlite3_create_function()](c3ref/create_function.md) API.
**[simple-function-invocation:](syntax/simple-function-invocation.md)**
See the [functions within expressions](lang_expr.md#*funcinexpr) documentation for more information about how SQL function invocations fit into the context of an SQL expression.
# 2. List Of Core Functions
- [abs(X)](lang_corefunc.md#abs)
- [changes()](lang_corefunc.md#changes)
- [char(X1,X2,...,XN)](lang_corefunc.md#char)
- [coalesce(X,Y,...)](lang_corefunc.md#coalesce)
- [concat(X,...)](lang_corefunc.md#concat)
- [concat_ws(SEP,X,...)](lang_corefunc.md#concat_ws)
- [format(FORMAT,...)](lang_corefunc.md#format)
- [glob(X,Y)](lang_corefunc.md#glob)
- [hex(X)](lang_corefunc.md#hex)
- [if(B1,V1,...)](lang_corefunc.md#iif)
- [ifnull(X,Y)](lang_corefunc.md#ifnull)
- [iif(B1,V1,...)](lang_corefunc.md#iif)
- [instr(X,Y)](lang_corefunc.md#instr)
- [last_insert_rowid()](lang_corefunc.md#last_insert_rowid)
- [length(X)](lang_corefunc.md#length)
- [like(X,Y)](lang_corefunc.md#like)
- [like(X,Y,Z)](lang_corefunc.md#like)
- [likelihood(X,Y)](lang_corefunc.md#likelihood)
- [likely(X)](lang_corefunc.md#likely)
- [load_extension(X)](lang_corefunc.md#load_extension)
- [load_extension(X,Y)](lang_corefunc.md#load_extension)
- [lower(X)](lang_corefunc.md#lower)
- [ltrim(X)](lang_corefunc.md#ltrim)
- [ltrim(X,Y)](lang_corefunc.md#ltrim)
- [max(X,Y,...)](lang_corefunc.md#max_scalar)
- [min(X,Y,...)](lang_corefunc.md#min_scalar)
- [nullif(X,Y)](lang_corefunc.md#nullif)
- [octet_length(X)](lang_corefunc.md#octet_length)
- [printf(FORMAT,...)](lang_corefunc.md#printf)
- [quote(X)](lang_corefunc.md#quote)
- [random()](lang_corefunc.md#random)
- [randomblob(N)](lang_corefunc.md#randomblob)
- [replace(X,Y,Z)](lang_corefunc.md#replace)
- [round(X)](lang_corefunc.md#round)
- [round(X,Y)](lang_corefunc.md#round)
- [rtrim(X)](lang_corefunc.md#rtrim)
- [rtrim(X,Y)](lang_corefunc.md#rtrim)
- [sign(X)](lang_corefunc.md#sign)
- [soundex(X)](lang_corefunc.md#soundex)
- [sqlite_compileoption_get(N)](lang_corefunc.md#sqlite_compileoption_get)
- [sqlite_compileoption_used(X)](lang_corefunc.md#sqlite_compileoption_used)
- [sqlite_offset(X)](lang_corefunc.md#sqlite_offset)
- [sqlite_source_id()](lang_corefunc.md#sqlite_source_id)
- [sqlite_version()](lang_corefunc.md#sqlite_version)
- [substr(X,Y)](lang_corefunc.md#substr)
- [substr(X,Y,Z)](lang_corefunc.md#substr)
- [substring(X,Y)](lang_corefunc.md#substr)
- [substring(X,Y,Z)](lang_corefunc.md#substr)
- [total_changes()](lang_corefunc.md#total_changes)
- [trim(X)](lang_corefunc.md#trim)
- [trim(X,Y)](lang_corefunc.md#trim)
- [typeof(X)](lang_corefunc.md#typeof)
- [unhex(X)](lang_corefunc.md#unhex)
- [unhex(X,Y)](lang_corefunc.md#unhex)
- [unicode(X)](lang_corefunc.md#unicode)
- [unistr(X)](lang_corefunc.md#unistr)
- [unistr_quote(X)](lang_corefunc.md#unistr_quote)
- [unlikely(X)](lang_corefunc.md#unlikely)
- [upper(X)](lang_corefunc.md#upper)
- [zeroblob(N)](lang_corefunc.md#zeroblob)
# 3. Descriptions of built-in scalar SQL functions
**abs(*X*)**
The abs(X) function returns the absolute value of the numeric argument X. Abs(X) returns NULL if X is NULL. Abs(X) returns 0.0 if X is a string or blob that cannot be converted to a numeric value. If X is the integer -9223372036854775808 then abs(X) throws an integer overflow error since there is no equivalent positive 64-bit two's complement value.
**changes()**
The changes() function returns the number of database rows that were changed or inserted or deleted by the most recently completed INSERT, DELETE, or UPDATE statement, exclusive of statements in lower-level triggers. The changes() SQL function is a wrapper around the [sqlite3_changes64()](c3ref/changes.md) C/C++ function and hence follows the same rules for counting changes.
**char(*X1*,*X2*,...,*XN*)**
The char(X1,X2,...,XN) function returns a string composed of characters having the unicode code point values of integers X1 through XN, respectively.
**coalesce(*X*,*Y*,...)**
The coalesce() function returns a copy of its first non-NULL argument, or NULL if all arguments are NULL. Coalesce() must have at least 2 arguments.
**concat(*X*,...)**
The concat(...) function returns a string which is the concatenation of the string representation of all of its non-NULL arguments. If all arguments are NULL, then concat() returns an empty string.
**concat_ws(*SEP*,*X*,...)**
The concat_ws(SEP,...) function returns a string that is the concatenation of all non-null arguments beyond the first argument, using the text value of the first argument as a separator. If the first argument is NULL, then concat_ws() returns NULL. If all arguments other than the first are NULL, then concat_ws() returns an empty string.
**format(*FORMAT*,...)**
The format(FORMAT,...) SQL function works like the [sqlite3_mprintf()](c3ref/mprintf.md) C-language function and the printf() function from the standard C library. The first argument is a format string that specifies how to construct the output string using values taken from subsequent arguments. If the FORMAT argument is missing or NULL then the result is NULL. The %n format is silently ignored and does not consume an argument. The %p format is an alias for %X. The %z format is interchangeable with %s. If there are too few arguments in the argument list, missing arguments are assumed to have a NULL value, which is translated into 0 or 0.0 for numeric formats or an empty string for %s. See the [built-in printf()](printf.md) documentation for additional information.
**glob(*X*,*Y*)**
The glob(X,Y) function is equivalent to the expression "**Y GLOB X**". Note that the X and Y arguments are reversed in the glob() function relative to the infix [GLOB](lang_expr.md#glob) operator. Y is the string and X is the pattern. So, for example, the following expressions are equivalent:
> \
> name GLOB '\*helium\*'\
> glob('\*helium\*',name)\
>
If the [sqlite3_create_function()](c3ref/create_function.md) interface is used to override the glob(X,Y) function with an alternative implementation then the [GLOB](lang_expr.md#glob) operator will invoke the alternative implementation.
**hex(*X*)**
The hex() function interprets its argument as a BLOB and returns a string which is the upper-case hexadecimal rendering of the content of that blob.
If the argument *X* in "hex(*X*)" is an integer or floating point number, then "interprets its argument as a BLOB" means that the binary number is first converted into a UTF8 text representation, then that text is interpreted as a BLOB. Hence, "hex(12345678)" renders as "3132333435363738" not the binary representation of the integer value "0000000000BC614E".
See also: [unhex()](lang_corefunc.md#unhex)
**ifnull(*X*,*Y*)**
The ifnull() function returns a copy of its first non-NULL argument, or NULL if both arguments are NULL. Ifnull() must have exactly 2 arguments. The ifnull() function is equivalent to [coalesce()](lang_corefunc.md#coalesce) with two arguments.
**iif(*B1*,*V1*,...)\
if(*B1*,*V1*,...)**
The iif(B1,V1,...,BN,VN) function takes arguments in pairs. The first argument of each pair is a Boolean and the second argument is a value to return if the Boolean is true. The iif() function returns the value associated with the first true Boolean. If the number of arguments to iif() is odd, then the last argument is a value that returned if all prior Boolean arguments are false. If the number of arguments is even and all Boolean arguments are false, then NULL is returned. The iif() function requires at least two arguments. The iif() function is really a short-hand notation for a [CASE expression](lang_expr.md#case). For example, the iif(X,Y,Z) function is logically equivalent to and generates the same [bytecode](opcode.md) as the [CASE expression](lang_expr.md#case) "CASE WHEN X THEN Y ELSE Z END". The if() function is just an alternative spelling for iif().
The iif() function uses short-circuit evaluation. Arguments are only evaluated if necessary to compute the final result. So, for example, if one of the value arguments involves an expensive computation (such as an elaborate subquery) but the corresponding Boolean is false, the expensive computation never occurs. Similarly, Boolean arguments past the first one that is true are never evaluated.
The iif() function originally required exactly three arguments. The two-argument version of iif() and the ability to spell the function as "if()" were features added in SQLite version 3.48.0 (2025-01-14) The ability to accept more than 3 arguments was added in SQLite version 3.49.0 (2025-02-06).
**instr(*X*,*Y*)**
The instr(X,Y) function finds the first occurrence of string Y within string X and returns the number of prior characters plus 1, or 0 if Y is nowhere found within X. Or, if X and Y are both BLOBs, then instr(X,Y) returns one more than the number of bytes prior to the first occurrence of Y, or 0 if Y does not occur anywhere within X. If both arguments X and Y to instr(X,Y) are non-NULL and are not BLOBs then both are interpreted as strings. If either X or Y are NULL in instr(X,Y) then the result is NULL.
**last_insert_rowid()**
The last_insert_rowid() function returns the [ROWID](lang_createtable.md#rowid) of the last row insert from the database connection which invoked the function. The last_insert_rowid() SQL function is a wrapper around the [sqlite3_last_insert_rowid()](c3ref/last_insert_rowid.md) C/C++ interface function.
**length(*X*)**
For a string value X, the length(X) function returns the number of Unicode code points (not bytes) in input string X prior to the first U+0000 character. Since SQLite strings do not normally contain NUL characters, the length(X) function will usually return the total number of characters in the string X. For a blob value X, length(X) returns the number of bytes in the blob. If X is NULL then length(X) is NULL. If X is numeric then length(X) returns the length of a string representation of X.
Note that for strings, the length(X) function returns the *character* or *code-point* length of the string, not the byte length. The character length is the number of characters in the string. The character length is always different from the byte length for UTF-16 strings, and can be different from the byte length for UTF-8 strings if the string contains multi-byte characters. Use the [octet_length()](lang_corefunc.md#octet_length) function to find the byte length of a string.
For BLOB values, length(X) always returns the byte-length of the BLOB.
For string values, length(X) must read the entire string into memory in order to compute the character length. But for BLOB values, reading the whole string into memory is not necessary as SQLite already knows how many bytes are in the BLOB. Hence, for multi-megabyte values, the length(X) function is usually much faster for BLOBs than for strings, since it does not need to load the value into memory.
**like(*X*,*Y*)\
like(*X*,*Y*,*Z*)**
The like() function is used to implement the "**Y LIKE X \[ESCAPE Z\]**" expression. If the optional ESCAPE clause is present, then the like() function is invoked with three arguments. Otherwise, it is invoked with two arguments only. Note that the X and Y parameters are reversed in the like() function relative to the infix [LIKE](lang_expr.md#like) operator. X is the pattern and Y is the string to match against that pattern. Hence, the following expressions are equivalent:
> \
> name LIKE '%neon%'\
> like('%neon%',name)\
>
The [sqlite3_create_function()](c3ref/create_function.md) interface can be used to override the like() function and thereby change the operation of the [LIKE](lang_expr.md#like) operator. When overriding the like() function, it may be important to override both the two and three argument versions of the like() function. Otherwise, different code may be called to implement the [LIKE](lang_expr.md#like) operator depending on whether or not an ESCAPE clause was specified.
**likelihood(*X*,*Y*)**
The likelihood(X,Y) function returns argument X unchanged. The value Y in likelihood(X,Y) must be a floating point constant between 0.0 and 1.0, inclusive. The likelihood(X) function is a no-op that the code generator optimizes away so that it consumes no CPU cycles during run-time (that is, during calls to [sqlite3_step()](c3ref/step.md)). The purpose of the likelihood(X,Y) function is to provide a hint to the query planner that the argument X is a boolean that is true with a probability of approximately Y. The [unlikely(X)](lang_corefunc.md#unlikely) function is short-hand for likelihood(X,0.0625). The [likely(X)](lang_corefunc.md#likely) function is short-hand for likelihood(X,0.9375).
**likely(*X*)**
The likely(X) function returns the argument X unchanged. The likely(X) function is a no-op that the code generator optimizes away so that it consumes no CPU cycles at run-time (that is, during calls to [sqlite3_step()](c3ref/step.md)). The purpose of the likely(X) function is to provide a hint to the query planner that the argument X is a boolean value that is usually true. The likely(X) function is equivalent to [likelihood](lang_corefunc.md#likelihood)(X,0.9375). See also: [unlikely(X)](lang_corefunc.md#unlikely).
**load_extension(*X*)\
load_extension(*X*,*Y*)**
The load_extension(X,Y) function loads [SQLite extensions](loadext.md) out of the shared library file named X using the entry point Y. The result of load_extension() is always a NULL. If Y is omitted then the default entry point name is used. The load_extension() function raises an exception if the extension fails to load or initialize correctly.
The load_extension() function will fail if the extension attempts to modify or delete an SQL function or collating sequence. The extension can add new functions or collating sequences, but cannot modify or delete existing functions or collating sequences because those functions and/or collating sequences might be used elsewhere in the currently running SQL statement. To load an extension that changes or deletes functions or collating sequences, use the [sqlite3_load_extension()](c3ref/load_extension.md) C-language API.
For security reasons, extension loading is disabled by default and must be enabled by a prior call to [sqlite3_enable_load_extension()](c3ref/enable_load_extension.md).
**lower(*X*)**
The lower(X) function returns a copy of string X with all ASCII characters converted to lower case. The default built-in lower() function works for ASCII characters only. To do case conversions on non-ASCII characters, load the ICU extension.
**ltrim(*X*)\
ltrim(*X*,*Y*)**
The ltrim(X,Y) function returns a string formed by removing any and all characters that appear in Y from the left side of X. If the Y argument is omitted, ltrim(X) removes spaces from the left side of X.
**max(*X*,*Y*,...)**
The multi-argument max() function returns the argument with the maximum value, or return NULL if any argument is NULL. The multi-argument max() function searches its arguments from left to right for an argument that defines a collating function and uses that collating function for all string comparisons. If none of the arguments to max() define a collating function, then the BINARY collating function is used. Note that **max()** is a simple function when it has 2 or more arguments but operates as an [aggregate function](lang_aggfunc.md#max_agg) if given only a single argument.
**min(*X*,*Y*,...)**
The multi-argument min() function returns the argument with the minimum value. The multi-argument min() function searches its arguments from left to right for an argument that defines a collating function and uses that collating function for all string comparisons. If none of the arguments to min() define a collating function, then the BINARY collating function is used. Note that **min()** is a simple function when it has 2 or more arguments but operates as an [aggregate function](lang_aggfunc.md#min_agg) if given only a single argument.
**nullif(*X*,*Y*)**
The nullif(X,Y) function returns its first argument if the arguments are different and NULL if the arguments are the same. The nullif(X,Y) function searches its arguments from left to right for an argument that defines a collating function and uses that collating function for all string comparisons. If neither argument to nullif() defines a collating function then the BINARY collating function is used.
**octet_length(*X*)**
The octet_length(X) function returns the number of bytes in the encoding of text string X. If X is NULL then octet_length(X) returns NULL. If X is a BLOB value, then octet_length(X) is the same as [length(X)](lang_corefunc.md#length). If X is a numeric value, then octet_length(X) returns the number of bytes in a text rendering of that number.
Because octet_length(X) returns the number of bytes in X, not the number of characters or code-points, the value returned depends on the database encoding. The octet_length() function can return different answers for the same input string if the database encoding is UTF16 instead of UTF8.
If argument X is a table column and the value is of type text or blob, then octet_length(X) avoids reading the content of X from disk, as the byte length can be computed from metadata. Thus, octet_length(X) is efficient even if X is a column containing a multi-megabyte text or blob value.
**printf(*FORMAT*,...)**
The printf() SQL function is an alias for the [format() SQL function](lang_corefunc.md#format). The format() SQL function was originally named printf(). But the name was later changed to format() for compatibility with other database engines. The printf() name is retained as an alias so as not to break legacy code.
**quote(*X*)**
The quote(X) function returns the text of an SQL literal which is the value of its argument suitable for inclusion into an SQL statement. Strings are surrounded by single-quotes with escapes on interior quotes as needed. BLOBs are encoded as hexadecimal literals. Strings with embedded NUL characters cannot be represented as string literals in SQL and hence the returned string literal is truncated prior to the first NUL.
The [unistr_quote(X)](lang_corefunc.md#unistr_quote) function works like quote(X) except that it also escapes control characters.
**random()**
The random() function returns a pseudo-random integer between -9223372036854775807 and +9223372036854775807.
The random() function deliberately avoids generating -9223372036854775808 so that its value can always be passed to [abs()](lang_corefunc.md#abs). The random() function has behaved this way since version 3.3.5 (circa 2006) but this documentation incorrectly stated that -9223372036854775808 was a possible result until 2025-07-25.
**randomblob(*N*)**
The randomblob(N) function return an N-byte blob containing pseudo-random bytes. If N is less than 1 then a 1-byte random blob is returned.
Hint: applications can generate globally unique identifiers using this function together with [hex()](lang_corefunc.md#hex) and/or [lower()](lang_corefunc.md#lower) like this:
> hex(randomblob(16))\
> lower(hex(randomblob(16)))
**replace(*X*,*Y*,*Z*)**
The replace(X,Y,Z) function returns a string formed by substituting string Z for every occurrence of string Y in string X. The [BINARY](datatype3.md#collation) collating sequence is used for comparisons. If Y is an empty string then return X unchanged. If Z is not initially a string, it is cast to a UTF-8 string prior to processing.
**round(*X*)\
round(*X*,*Y*)**
The round(X,Y) function returns a floating-point value X rounded to Y digits to the right of the decimal point. If the Y argument is omitted or negative, it is taken to be 0.
**rtrim(*X*)\
rtrim(*X*,*Y*)**
The rtrim(X,Y) function returns a string formed by removing any and all characters that appear in Y from the right side of X. If the Y argument is omitted, rtrim(X) removes spaces from the right side of X.
**sign(*X*)**
The sign(X) function returns -1, 0, or +1 if the argument X is a numeric value that is negative, zero, or positive, respectively. If the argument to sign(X) is NULL or a BLOB or a string that cannot be losslessly converted into a number, then sign(X) returns NULL.
**soundex(*X*)**
The soundex(X) function returns a string that is the soundex encoding of the string X. The string "?000" is returned if the argument is NULL or contains no ASCII alphabetic characters. This function is omitted from SQLite by default. It is only available if the [SQLITE_SOUNDEX](compile.md#soundex) compile-time option is used when SQLite is built.
**sqlite_compileoption_get(*N*)**
The sqlite_compileoption_get() SQL function is a wrapper around the [sqlite3_compileoption_get()](c3ref/compileoption_get.md) C/C++ function. This routine returns the N-th compile-time option used to build SQLite or NULL if N is out of range. See also the [compile_options pragma](pragma.md#pragma_compile_options).
**sqlite_compileoption_used(*X*)**
The sqlite_compileoption_used() SQL function is a wrapper around the [sqlite3_compileoption_used()](c3ref/compileoption_get.md) C/C++ function. When the argument X to sqlite_compileoption_used(X) is a string which is the name of a compile-time option, this routine returns true (1) or false (0) depending on whether or not that option was used during the build.
**sqlite_offset(*X*)**
The sqlite_offset(X) function returns the byte offset in the database file for the beginning of the record from which value would be read. If X is not a column in an ordinary table, then sqlite_offset(X) returns NULL. The value returned by sqlite_offset(X) might reference either the original table or an index, depending on the query. If the value X would normally be extracted from an index, the sqlite_offset(X) returns the offset to the corresponding index record. If the value X would be extracted from the original table, then sqlite_offset(X) returns the offset to the table record.
The sqlite_offset(X) SQL function is only available if SQLite is built using the [-DSQLITE_ENABLE_OFFSET_SQL_FUNC](compile.md#enable_offset_sql_func) compile-time option.
**sqlite_source_id()**
The sqlite_source_id() function returns a string that identifies the specific version of the source code that was used to build the SQLite library. The string returned by sqlite_source_id() is the date and time that the source code was checked in followed by the SHA3-256 hash for that check-in. This function is an SQL wrapper around the [sqlite3_sourceid()](c3ref/libversion.md) C interface.
**sqlite_version()**
The sqlite_version() function returns the version string for the SQLite library that is running. This function is an SQL wrapper around the [sqlite3_libversion()](c3ref/libversion.md) C-interface.
**substr(*X*,*Y*,*Z*)\
substr(*X*,*Y*)\
substring(*X*,*Y*,*Z*)\
substring(*X*,*Y*)**
The substr(X,Y,Z) function returns a substring of input string X that begins with the Y-th character and which is Z characters long. If Z is omitted then substr(X,Y) returns all characters through the end of the string X beginning with the Y-th. The left-most character of X is number 1. If Y is negative then the first character of the substring is found by counting from the right rather than the left. If Z is negative then the abs(Z) characters preceding the Y-th character are returned. If X is a string then indices count UTF code points. If X is a BLOB then the indices count bytes.
"substring()" is an alias for "substr()" beginning with SQLite version 3.34.
**total_changes()**
The total_changes() function returns the number of row changes caused by INSERT, UPDATE or DELETE statements since the current database connection was opened. This function is a wrapper around the [sqlite3_total_changes64()](c3ref/total_changes.md) C/C++ interface.
**trim(*X*)\
trim(*X*,*Y*)**
The trim(X,Y) function returns a string formed by removing any and all characters that appear in Y from both ends of X. If the Y argument is omitted, trim(X) removes spaces from both ends of X.
**typeof(*X*)**
The typeof(X) function returns a string that indicates the [datatype](datatype3.md) of the expression X: "null", "integer", "real", "text", or "blob".
**unhex(*X*)\
unhex(*X*,*Y*)**
The unhex(X,Y) function returns a BLOB value which is the decoding of the hexadecimal string X. If X contains any characters that are not hexadecimal digits and which are not in Y, then unhex(X,Y) returns NULL. If Y is omitted, it is understood to be an empty string and hence X must be a pure hexadecimal string. All hexadecimal digits in X must occur in pairs, with both digits of each pair beginning immediately adjacent to one another, or else unhex(X,Y) returns NULL. If either parameter X or Y is NULL, then unhex(X,Y) returns NULL. The X input may contain an arbitrary mix of upper and lower case hexadecimal digits. Hexadecimal digits in Y have no affect on the translation of X. Only characters in Y that are not hexadecimal digits are ignored in X.
See also: [hex()](lang_corefunc.md#hex)
**unicode(*X*)**
The unicode(X) function returns the numeric unicode code point corresponding to the first character of the string X. If the argument to unicode(X) is not a string then the result is unspecified.
**unistr(*X*)**
The unistr(X) function interprets backslash escapes in input string X and returns a new string with those escapes converted into the actual Unicode codepoints that they represent. This function, added in SQLite version 3.50.0 (2025-05-29), is intended to work the same as in PostgreSQL, SQL Server, and Oracle. The PostgreSQL documentation says: "Unicode characters can be specified as \XXXX (4 hexadecimal digits), \\XXXXXX (6 hexadecimal digits), \uXXXX (4 hexadecimal digits), or \UXXXXXXXX (8 hexadecimal digits). To specify a backslash, write two backslashes. All other characters are taken literally."
**unistr_quote(*X*)**
The unistr_quote(X) function returns the text of an SQL literal or constant expression that encodes the value of its argument X and is suitable for inclusion into an SQL statement. In most cases, the output of unistr_quote(X) is identical to [quote(X)](lang_corefunc.md#quote). However, if X is text that contains control characters in the range U+0001 through U+001f, then those characters and any "\\ characters in X are escaped using JSON-style backslash escapes and the entire output is enclosed within "[`unistr`](lang_corefunc.md#unistr)`(`..`)`". This makes the resulting text safe for display on devices that interpret [ANSI escape codes](https://en.wikipedia.org/wiki/ANSI_escape_code).
**unlikely(*X*)**
The unlikely(X) function returns the argument X unchanged. The unlikely(X) function is a no-op that the code generator optimizes away so that it consumes no CPU cycles at run-time (that is, during calls to [sqlite3_step()](c3ref/step.md)). The purpose of the unlikely(X) function is to provide a hint to the query planner that the argument X is a boolean value that is usually not true. The unlikely(X) function is equivalent to [likelihood](lang_corefunc.md#likelihood)(X, 0.0625).
**upper(*X*)**
The upper(X) function returns a copy of input string X in which all lower-case ASCII characters are converted to their upper-case equivalent.
**zeroblob(*N*)**
The zeroblob(N) function returns a BLOB consisting of N bytes of 0x00. SQLite manages these zeroblobs very efficiently. Zeroblobs can be used to reserve space for a BLOB that is later written using [incremental BLOB I/O](c3ref/blob_open.md). This SQL function is implemented using the [sqlite3_result_zeroblob()](c3ref/result_blob.md) routine from the C/C++ interface.
---
# CREATE INDEX
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_createindex.html*
# 1. Syntax
**[create-index-stmt:](syntax/create-index-stmt.md)** hide
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[indexed-column:](syntax/indexed-column.md)** show
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](partialindex.md)".
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](c3ref/limit.md)([SQLITE_LIMIT_COLUMN](c3ref/c_limit_attached.md#sqlitelimitcolumn),...).
Indexes are removed with the [DROP INDEX](lang_dropindex.md) command.
## 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()](lang_corefunc.md#random) or [sqlite_version()](lang_corefunc.md#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](releaselog/3_9_0.md) (2015-10-14). See the [Indexes On Expressions](expridx.md) 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](fileformat2.md#schemaformat). 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](pragma.md#pragma_legacy_file_format) can be used to change or set the specific behavior for any version of SQLite.
## 1.4. NULLS FIRST and NULLS LAST
The NULLS FIRST and NULLS LAST predicates are not supported for indexes. For [sorting purposes](datatype3.md#sortorder), 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](lang_createtable.md) statement. Or if no collating sequence is otherwise defined, the built-in BINARY collating sequence is used.
---
# CREATE TABLE
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_createtable.html*
# 1. Syntax
**[create-table-stmt:](syntax/create-table-stmt.md)** hide
**[column-def:](syntax/column-def.md)** show
**[column-constraint:](syntax/column-constraint.md)** show
**[conflict-clause:](syntax/conflict-clause.md)** show
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[foreign-key-clause:](syntax/foreign-key-clause.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[table-constraint:](syntax/table-constraint.md)** show
**[conflict-clause:](syntax/conflict-clause.md)** show
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[foreign-key-clause:](syntax/foreign-key-clause.md)** show
**[indexed-column:](syntax/indexed-column.md)** show
**[table-options:](syntax/table-options.md)** show
# 2. The CREATE TABLE command
The "CREATE TABLE" command is used to create a new table in an SQLite database. A CREATE TABLE command specifies the following attributes of the new table:
- The name of the new table.
- The database in which the new table is created. Tables may be created in the main database, the temp database, or in any attached database.
- The name of each column in the table.
- The declared type of each column in the table.
- A default value or expression for each column in the table.
- A default collation sequence to use with each column.
- An optional PRIMARY KEY for the table. Both single column and composite (multiple column) primary keys are supported.
- Zero or more constraints on the table content. SQLite supports UNIQUE, NOT NULL, CHECK and FOREIGN KEY constraints.
- Optionally, a [generated column](gencol.md) constraint.
- Whether the table is a [WITHOUT ROWID](withoutrowid.md) table.
- Whether the table is subject to [strict type checking](stricttables.md).
Every CREATE TABLE statement must specify a name for the new table. Table names that begin with "sqlite\_" are reserved for internal use. It is an error to attempt to create a table with a name that starts with "sqlite\_".
If a schema-name is specified, it must be either "main", "temp", or the name of an [attached database](lang_attach.md). In this case the new table is created in the named database. If the "TEMP" or "TEMPORARY" keyword occurs between the "CREATE" and "TABLE" then the new table is created in the temp database. It is an error to specify both a schema-name and the TEMP or TEMPORARY keyword, unless the schema-name is "temp". If no schema name is specified and the TEMP keyword is not present then the table is created in the main database.
It is usually an error to attempt to create a new table in a database that already contains a table, index or view of the same name. However, if the "IF NOT EXISTS" clause is specified as part of the CREATE TABLE statement and a table or view of the same name already exists, the CREATE TABLE command simply has no effect (and no error message is returned). An error is still returned if the table cannot be created because of an existing index, even if the "IF NOT EXISTS" clause is specified.
It is not an error to create a table that has the same name as an existing [trigger](lang_createtrigger.md).
Tables are removed using the [DROP TABLE](lang_droptable.md) statement.
## 2.1. CREATE TABLE ... AS SELECT Statements
A "CREATE TABLE ... AS SELECT" statement creates and populates a database table based on the results of a SELECT statement. The table has the same number of columns as the SELECT statement returns. The name of each column is the same as the name of the corresponding column in the result set of the SELECT statement. The declared type of each column is determined by the [expression affinity](datatype3.md#expraff) of the corresponding expression in the result set of the SELECT statement, as follows:
| Expression Affinity | Column Declared Type |
|---------------------|----------------------|
| TEXT | "TEXT" |
| NUMERIC | "NUM" |
| INTEGER | "INT" |
| REAL | "REAL" |
| BLOB (a.k.a "NONE") | "" (empty string) |
A table created using CREATE TABLE AS has no PRIMARY KEY and no constraints of any kind. The default value of each column is NULL. The default collation sequence for each column of the new table is BINARY.
Tables created using CREATE TABLE AS are initially populated with the rows of data returned by the SELECT statement. Rows are assigned contiguously ascending [rowid](lang_createtable.md#rowid) values, starting with 1, in the [order](lang_select.md#orderby) that they are returned by the SELECT statement.
# 3. Column Definitions
Unless it is a CREATE TABLE ... AS SELECT statement, a CREATE TABLE includes one or more [column definitions](syntax/column-def.md), optionally followed by a list of [table constraints](syntax/table-constraint.md). Each column definition consists of the name of the column, optionally followed by the declared type of the column, then one or more optional [column constraints](syntax/column-constraint.md). Included in the definition of "column constraints" for the purposes of the previous statement are the COLLATE and DEFAULT clauses, even though these are not really constraints in the sense that they do not restrict the data that the table may contain. The other constraints - NOT NULL, CHECK, UNIQUE, PRIMARY KEY and FOREIGN KEY constraints - impose restrictions on the table data.
The number of columns in a table is limited by the [SQLITE_MAX_COLUMN](limits.md#max_column) compile-time parameter. A single row of a table cannot store more than [SQLITE_MAX_LENGTH](limits.md#max_length) bytes of data. Both of these limits can be lowered at runtime using the [sqlite3_limit()](c3ref/limit.md) C/C++ interface.
## 3.1. Column Data Types
Unlike most SQL databases, SQLite does not restrict the type of data that may be inserted into a column based on the columns declared type. Instead, SQLite uses [dynamic typing](datatype3.md). The declared type of a column is used to determine the [affinity](datatype3.md#affinity) of the column only.
## 3.2. The DEFAULT clause
The DEFAULT clause specifies a default value to use for the column if no value is explicitly provided by the user when doing an [INSERT](lang_insert.md). If there is no explicit DEFAULT clause attached to a column definition, then the default value of the column is NULL. An explicit DEFAULT clause may specify that the default value is NULL, a string constant, a blob constant, a signed-number, or any constant expression enclosed in parentheses. A default value may also be one of the special case-independent keywords CURRENT_TIME, CURRENT_DATE or CURRENT_TIMESTAMP. For the purposes of the DEFAULT clause, an expression is considered constant if it contains no sub-queries, column or table references, [bound parameters](lang_expr.md#varparam), or string literals enclosed in double-quotes instead of single-quotes.
Each time a row is inserted into the table by an INSERT statement that does not provide explicit values for all table columns the values stored in the new row are determined by their default values, as follows:
- If the default value of the column is a constant NULL, text, blob or signed-number value, then that value is used directly in the new row.
- If the default value of a column is an expression in parentheses, then the expression is evaluated once for each row inserted and the results used in the new row.
- If the default value of a column is CURRENT_TIME, CURRENT_DATE or CURRENT_TIMESTAMP, then the value used in the new row is a text representation of the current UTC date and/or time. For CURRENT_TIME, the format of the value is "HH:MM:SS". For CURRENT_DATE, "YYYY-MM-DD". The format for CURRENT_TIMESTAMP is "YYYY-MM-DD HH:MM:SS".
## 3.3. The COLLATE clause
The COLLATE clause specifies the name of a [collating sequence](datatype3.md#collation) to use as the default collation sequence for the column. If no COLLATE clause is specified, the default collation sequence is [BINARY](datatype3.md#collation).
## 3.4. The GENERATED ALWAYS AS clause
A column that includes a GENERATED ALWAYS AS clause is a [generated column](gencol.md). Generated columns are supported beginning with SQLite version 3.31.0 (2020-01-22). See the [separate documentation](gencol.md) for details on the capabilities and limitations of generated columns.
## 3.5. The PRIMARY KEY
Each table in SQLite may have at most one PRIMARY KEY. If the keywords PRIMARY KEY are added to a column definition, then the primary key for the table consists of that single column. Or, if a PRIMARY KEY clause is specified as a [table-constraint](syntax/table-constraint.md), then the primary key of the table consists of the list of columns specified as part of the PRIMARY KEY clause. The PRIMARY KEY clause must contain only column names — the use of expressions in an [indexed-column](syntax/indexed-column.md) of a PRIMARY KEY is not supported. An error is raised if more than one PRIMARY KEY clause appears in a CREATE TABLE statement. The PRIMARY KEY is optional for ordinary tables but is required for [WITHOUT ROWID](withoutrowid.md) tables.
If a table has a single column primary key and the declared type of that column is "INTEGER" and the table is not a [WITHOUT ROWID](withoutrowid.md) table, then the column is known as an [INTEGER PRIMARY KEY](lang_createtable.md#rowid). See [below](lang_createtable.md#rowid) for a description of the special properties and behaviors associated with an [INTEGER PRIMARY KEY](lang_createtable.md#rowid).
Each row in a table with a primary key must have a unique combination of values in its primary key columns. For the purposes of determining the uniqueness of primary key values, NULL values are considered distinct from all other values, including other NULLs. If an [INSERT](lang_insert.md) or [UPDATE](lang_update.md) statement attempts to modify the table content so that two or more rows have identical primary key values, that is a constraint violation.
According to the SQL standard, PRIMARY KEY should always imply NOT NULL. Unfortunately, due to a bug in some early versions, this is not the case in SQLite. Unless the column is an [INTEGER PRIMARY KEY](lang_createtable.md#rowid) or the table is a [WITHOUT ROWID](withoutrowid.md) table or a [STRICT](stricttables.md) table or the column is declared NOT NULL, SQLite allows NULL values in a PRIMARY KEY column. SQLite could be fixed to conform to the standard, but doing so might break legacy applications. Hence, it has been decided to merely document the fact that SQLite allows NULLs in most PRIMARY KEY columns.
## 3.6. UNIQUE constraints
A UNIQUE constraint is similar to a PRIMARY KEY constraint, except that a single table may have any number of UNIQUE constraints. For each UNIQUE constraint on the table, each row must contain a unique combination of values in the columns identified by the UNIQUE constraint. For the purposes of UNIQUE constraints, NULL values are considered distinct from all other values, including other NULLs. As with PRIMARY KEYs, a UNIQUE [table-constraint](syntax/table-constraint.md) clause must contain only column names — the use of expressions in an [indexed-column](syntax/indexed-column.md) of a UNIQUE [table-constraint](syntax/table-constraint.md) is not supported.
In most cases, UNIQUE and PRIMARY KEY constraints are implemented by creating a unique index in the database. (The exceptions are [INTEGER PRIMARY KEY](lang_createtable.md#rowid) and PRIMARY KEYs on [WITHOUT ROWID](withoutrowid.md) tables.) Hence, the following schemas are logically equivalent:
1. CREATE TABLE t1(a, b UNIQUE);
2. CREATE TABLE t1(a, b PRIMARY KEY);
3. CREATE TABLE t1(a, b);\
CREATE UNIQUE INDEX t1b ON t1(b);
## 3.7. CHECK constraints
A CHECK constraint may be attached to a column definition or specified as a table constraint. In practice it makes no difference. Each time a new row is inserted into the table or an existing row is updated, the expression associated with each CHECK constraint is evaluated and cast to a NUMERIC value in the same way as a [CAST expression](lang_expr.md#castexpr). If the result is zero (integer value 0 or real value 0.0), then a constraint violation has occurred. If the CHECK expression evaluates to NULL, or any other non-zero value, it is not a constraint violation. The expression of a CHECK constraint may not contain a subquery.
CHECK constraints are only verified when the table is written, not when it is read. Furthermore, verification of CHECK constraints can be temporarily disabled using the "[PRAGMA ignore_check_constraints=ON;](pragma.md#pragma_ignore_check_constraints)" statement. Hence, it is possible that a query might produce results that violate the CHECK constraints.
## 3.8. NOT NULL constraints
A NOT NULL constraint may only be attached to a column definition, not specified as a table constraint. Not surprisingly, a NOT NULL constraint dictates that the associated column may not contain a NULL value. Attempting to set the column value to NULL when inserting a new row or updating an existing one causes a constraint violation. NOT NULL constraints are not verified during queries, so a query of a column might produce a NULL value even though the column is marked as NOT NULL, if the database file is corrupt.
# 4. Constraint enforcement
Constraints are checked during [INSERT](lang_insert.md) and [UPDATE](lang_update.md) and by [PRAGMA integrity_check](pragma.md#pragma_integrity_check) and [PRAGMA quick_check](pragma.md#pragma_quick_check) and sometimes by [ALTER TABLE](lang_altertable.md). Queries and [DELETE](lang_delete.md) statements do not normally verify constraints. Hence, if a database file has been corrupted (perhaps by an external program making direct changes to the database file without going through the SQLite library) a query might return data that violates a constraint. For example:
CREATE TABLE t1(x INT CHECK( x\>3 ));\
/\* Insert a row with X less than 3 by directly writing into the\
\*\* database file using an external program \*/\
PRAGMA integrity_check; -- Reports row with x less than 3 as corrupt\
INSERT INTO t1(x) VALUES(2); -- Fails with SQLITE_CORRUPT\
SELECT x FROM t1; -- Returns an integer less than 3 in spite of the CHECK constraint\
Enforcement of CHECK constraints can be temporarily disabled using the [PRAGMA ignore_check_constraints=ON;](pragma.md#pragma_ignore_check_constraints) statement.
## 4.1. Response to constraint violations
The response to a constraint violation is determined by the [constraint conflict resolution algorithm](lang_conflict.md). Each PRIMARY KEY, UNIQUE, NOT NULL and CHECK constraint has a default conflict resolution algorithm. PRIMARY KEY, UNIQUE and NOT NULL constraints may be explicitly assigned another default conflict resolution algorithm by including a [conflict-clause](syntax/conflict-clause.md) in their definitions. Or, if a constraint definition does not include a [conflict-clause](syntax/conflict-clause.md), the default conflict resolution algorithm is ABORT. The conflict resolution algorithm for CHECK constraints is always ABORT. (For historical compatibility only, table CHECK constraints are allowed to have a conflict resolution clause, but that has no effect.) Different constraints within the same table may have different default conflict resolution algorithms. See the section titled [ON CONFLICT](lang_conflict.md) for additional information.
# 5. ROWIDs and the INTEGER PRIMARY KEY
Except for [WITHOUT ROWID](withoutrowid.md) tables, all rows within SQLite tables have a 64-bit signed integer key that uniquely identifies the row within its table. This integer is usually called the "rowid". The rowid value can be accessed using one of the special case-independent names "rowid", "oid", or "\_rowid\_" in place of a column name. If a table contains a user defined column named "rowid", "oid" or "\_rowid\_", then that name always refers the explicitly declared column and cannot be used to retrieve the integer rowid value.
The rowid (and "oid" and "\_rowid\_") is omitted in [WITHOUT ROWID](withoutrowid.md) tables. WITHOUT ROWID tables are only available in SQLite [version 3.8.2](releaselog/3_8_2.md) (2013-12-06) and later. A table that lacks the WITHOUT ROWID clause is called a "rowid table".
The data for rowid tables is stored as a B-Tree structure containing one entry for each table row, using the rowid value as the key. This means that retrieving or sorting records by rowid is fast. Searching for a record with a specific rowid, or for all records with rowids within a specified range is around twice as fast as a similar search made by specifying any other PRIMARY KEY or indexed value.
With one exception noted below, if a rowid table has a primary key that consists of a single column and the declared type of that column is "INTEGER" in any mixture of upper and lower case, then the column becomes an alias for the rowid. Such a column is usually referred to as an "integer primary key". A PRIMARY KEY column only becomes an integer primary key if the declared type name is exactly "INTEGER". Other integer type names like "INT" or "BIGINT" or "SHORT INTEGER" or "UNSIGNED INTEGER" causes the primary key column to behave as an ordinary table column with integer [affinity](datatype3.md#affinity) and a unique index, not as an alias for the rowid.
The exception mentioned above is that if the declaration of a column with declared type "INTEGER" includes an "PRIMARY KEY DESC" clause, it does not become an alias for the rowid and is not classified as an integer primary key. This quirk is not by design. It is due to a bug in early versions of SQLite. But fixing the bug could result in backwards incompatibilities. Hence, the original behavior has been retained (and documented) because odd behavior in a corner case is far better than a compatibility break. This means that the following three table declarations all cause the column "x" to be an alias for the rowid (an integer primary key):
- `CREATE TABLE t(x INTEGER PRIMARY KEY ASC, y, z);`
- `CREATE TABLE t(x INTEGER, y, z, PRIMARY KEY(x ASC));`
- `CREATE TABLE t(x INTEGER, y, z, PRIMARY KEY(x DESC));`
But the following declaration does not result in "x" being an alias for the rowid:
- `CREATE TABLE t(x INTEGER PRIMARY KEY DESC, y, z);`
Rowid values may be modified using an UPDATE statement in the same way as any other column value can, either using one of the built-in aliases ("rowid", "oid" or "\_rowid\_") or by using an alias created by an integer primary key. Similarly, an INSERT statement may provide a value to use as the rowid for each row inserted. Unlike normal SQLite columns, an integer primary key or rowid column must contain integer values. Integer primary key or rowid columns are not able to hold floating point values, strings, BLOBs, or NULLs.
If an UPDATE statement attempts to set an integer primary key or rowid column to a NULL or blob value, or to a string or real value that cannot be losslessly converted to an integer, a "datatype mismatch" error occurs and the statement is aborted. If an INSERT statement attempts to insert a blob value, or a string or real value that cannot be losslessly converted to an integer into an integer primary key or rowid column, a "datatype mismatch" error occurs and the statement is aborted.
If an INSERT statement attempts to insert a NULL value into a rowid or integer primary key column, the system chooses an integer value to use as the rowid automatically. A detailed description of how this is done is provided [separately](autoinc.md).
The [parent key](foreignkeys.md#parentchild) of a [foreign key constraint](foreignkeys.md) is not allowed to use the rowid. The parent key must use named columns only.
---
# CREATE TRIGGER
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_createtrigger.html*
# 1. Syntax
**[create-trigger-stmt:](syntax/create-trigger-stmt.md)** hide
**[delete-stmt:](syntax/delete-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[qualified-table-name:](syntax/qualified-table-name.md)** show
**[returning-clause:](syntax/returning-clause.md)** show
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[insert-stmt:](syntax/insert-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[returning-clause:](syntax/returning-clause.md)** show
**[upsert-clause:](syntax/upsert-clause.md)** show
**[column-name-list:](syntax/column-name-list.md)** show
**[indexed-column:](syntax/indexed-column.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[update-stmt:](syntax/update-stmt.md)** show
**[column-name-list:](syntax/column-name-list.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[qualified-table-name:](syntax/qualified-table-name.md)** show
**[returning-clause:](syntax/returning-clause.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
# 2. Description
The CREATE TRIGGER statement is used to add triggers to the database schema. Triggers are database operations that are automatically performed when a specified database event occurs.
Each trigger must specify that it will fire for one of the following operations: [DELETE](lang_delete.md), [INSERT](lang_insert.md), [UPDATE](lang_update.md). The trigger fires once for each row that is deleted, inserted, or updated. If the "UPDATE OF column-name" syntax is used, then the trigger will only fire if column-name appears on the left-hand side of one of the terms in the SET clause of the [UPDATE](lang_update.md) statement.
Due to an historical oversight, columns named in the "UPDATE OF" clause do not actually have to exist in the table being updated. Unrecognized column names are silently ignored. It would be more helpful if SQLite would fail the CREATE TRIGGER statement if any of the names in the "UPDATE OF" clause are not columns in the table. However, as this problem was discovered many years after SQLite was widely deployed, we have resisted fixing the problem for fear of breaking legacy applications.
At this time SQLite supports only FOR EACH ROW triggers, not FOR EACH STATEMENT triggers. Hence explicitly specifying FOR EACH ROW is optional. FOR EACH ROW implies that the SQL statements specified in the trigger may be executed (depending on the WHEN clause) for each database row being inserted, updated or deleted by the statement causing the trigger to fire.
Both the WHEN clause and the trigger actions may access elements of the row being inserted, deleted or updated using references of the form "NEW.*column-name*" and "OLD.*column-name*", where *column-name* is the name of a column from the table that the trigger is associated with. OLD and NEW references may only be used in triggers on events for which they are relevant, as follows:
| | |
|---------:|----------------------------------|
| *INSERT* | NEW references are valid |
| *UPDATE* | NEW and OLD references are valid |
| *DELETE* | OLD references are valid |
If a WHEN clause is supplied, the SQL statements specified are only executed if the WHEN clause is true. If no WHEN clause is supplied, the SQL statements are executed every time the trigger fires.
The BEFORE or AFTER keyword determines when the trigger actions will be executed relative to the insertion, modification or removal of the associated row. BEFORE is the default when neither keyword is present.
An [ON CONFLICT](lang_conflict.md) clause may be specified as part of an [UPDATE](lang_update.md) or [INSERT](lang_insert.md) action within the body of the trigger. However if an [ON CONFLICT](lang_conflict.md) clause is specified as part of the statement causing the trigger to fire, then conflict handling policy of the outer statement is used instead.
Triggers are automatically [dropped](lang_droptrigger.md) when the table that they are associated with (the *table-name* table) is [dropped](lang_droptable.md). However if the trigger actions reference other tables, the trigger is not dropped or modified if those other tables are [dropped](lang_droptable.md) or [modified](lang_altertable.md).
Triggers are removed using the [DROP TRIGGER](lang_droptrigger.md) statement.
## 2.1. Syntax Restrictions On UPDATE, DELETE, and INSERT Statements Within Triggers
The [UPDATE](lang_update.md), [DELETE](lang_delete.md), and [INSERT](lang_insert.md) statements within triggers do not support the full syntax for [UPDATE](lang_update.md), [DELETE](lang_delete.md), and [INSERT](lang_insert.md) statements. The following restrictions apply:
- The name of the table to be modified in an [UPDATE](lang_update.md), [DELETE](lang_delete.md), or [INSERT](lang_insert.md) statement must be an unqualified table name. In other words, one must use just "*tablename*" not "*database***.***tablename*" when specifying the table.
- For non-TEMP triggers, the table to be modified or queried must exist in the same database as the table or view to which the trigger is attached. TEMP triggers are not subject to the same-database rule. A TEMP trigger is allowed to query or modify any table in any [ATTACH](lang_attach.md)-ed database.
- The "INSERT INTO *table* DEFAULT VALUES" form of the [INSERT](lang_insert.md) statement is not supported.
- The INDEXED BY and NOT INDEXED clauses are not supported for [UPDATE](lang_update.md) and [DELETE](lang_delete.md) statements.
- The ORDER BY and LIMIT clauses on [UPDATE](lang_update.md) and [DELETE](lang_delete.md) statements are not supported. ORDER BY and LIMIT are not normally supported for [UPDATE](lang_update.md) or [DELETE](lang_delete.md) in any context but can be enabled for top-level statements using the [SQLITE_ENABLE_UPDATE_DELETE_LIMIT](compile.md#enable_update_delete_limit) compile-time option. However, that compile-time option only applies to top-level [UPDATE](lang_update.md) and [DELETE](lang_delete.md) statements, not [UPDATE](lang_update.md) and [DELETE](lang_delete.md) statements within triggers.
- [Common table expressions](syntax/common-table-expression.md) are not supported directly by statements inside of triggers but may be embedded within sub-selects used by statements inside of triggers.
# 3. INSTEAD OF triggers
BEFORE and AFTER triggers work only on ordinary tables. INSTEAD OF triggers work only on views.
If an INSTEAD OF INSERT trigger exists on a view, then it is possible to execute an INSERT statement against that view. No actual insert occurs. Instead, the statements contained within the trigger are run. INSTEAD OF DELETE and INSTEAD OF UPDATE triggers work the same way for DELETE and UPDATE statements against views.
Note that the [sqlite3_changes()](c3ref/changes.md) and [sqlite3_total_changes()](c3ref/total_changes.md) interfaces do not count INSTEAD OF trigger firings, but the [count_changes pragma](pragma.md#pragma_count_changes) does count INSTEAD OF trigger firing.
# 4. Some Example Triggers
Assuming that customer records are stored in the "customers" table, and that order records are stored in the "orders" table, the following UPDATE trigger ensures that all associated orders are redirected when a customer changes his or her address:
> \
> CREATE TRIGGER update_customer_address UPDATE OF address ON customers \
> BEGIN\
> UPDATE orders SET address = new.address WHERE customer_name = old.name;\
> END;\
With this trigger installed, executing the statement:
> \
> UPDATE customers SET address = '1 Main St.' WHERE name = 'Jack Jones';\
causes the following to be automatically executed:
> \
> UPDATE orders SET address = '1 Main St.' WHERE customer_name = 'Jack Jones';\
For an example of an INSTEAD OF trigger, consider the following schema:
> \
> CREATE TABLE customer(\
> cust_id INTEGER PRIMARY KEY,\
> cust_name TEXT,\
> cust_addr TEXT\
> );\
> CREATE VIEW customer_address AS\
> SELECT cust_id, cust_addr FROM customer;\
> CREATE TRIGGER cust_addr_chng\
> INSTEAD OF UPDATE OF cust_addr ON customer_address\
> BEGIN\
> UPDATE customer SET cust_addr=NEW.cust_addr\
> WHERE cust_id=NEW.cust_id;\
> END;\
With the schema above, a statement of the form:
> \
> UPDATE customer_address SET cust_addr=\$new_address WHERE cust_id=\$cust_id;\
causes the customer.cust_addr field to be updated for a specific customer entry that has customer.cust_id equal to the \$cust_id parameter. Note how the values assigned to the view are made available as fields in the special "NEW" table within the trigger body.
# 5. Cautions On The Use Of BEFORE triggers
If a BEFORE UPDATE or BEFORE DELETE trigger modifies or deletes a row that was to have been updated or deleted, then the result of the subsequent update or delete operation is undefined. Furthermore, if a BEFORE trigger modifies or deletes a row, then it is undefined whether or not AFTER triggers that would have otherwise run on those rows will in fact run.
The value of NEW.rowid is undefined in a BEFORE INSERT trigger in which the rowid is not explicitly set to an integer.
Because of the behaviors described above, programmers are encouraged to prefer AFTER triggers over BEFORE triggers.
# 6. The RAISE() function
A special SQL function RAISE() may be used within a trigger-program, with the following syntax
**[raise-function:](syntax/raise-function.md)**
When one of RAISE(ROLLBACK,...), RAISE(ABORT,...) or RAISE(FAIL,...) is called during trigger-program execution, the specified [ON CONFLICT](lang_conflict.md) processing is performed and the current query terminates. An error code of [SQLITE_CONSTRAINT](rescode.md#constraint) is returned to the application, along with the specified error message.
When RAISE(IGNORE) is called, the remainder of the current trigger program, the statement that caused the trigger program to execute and any subsequent trigger programs that would have been executed are abandoned. No database changes are rolled back. If the statement that caused the trigger program to execute is itself part of a trigger program, then that trigger program resumes execution at the beginning of the next step.
Beginning with version 3.47.0 (2024-10-21), the error-message can be an SQL expression. In older versions of SQLite, the error-message was required to be a string literal.
# 7. TEMP Triggers on Non-TEMP Tables
A trigger normally exists in the same database as the table named after the "ON" keyword in the CREATE TRIGGER statement. Except, it is possible to create a TEMP TRIGGER on a table in another database. Such a trigger will only fire when changes are made to the target table by the application that defined the trigger. Other applications that modify the database will not be able to see the TEMP trigger and hence cannot run the trigger.
When defining a TEMP trigger on a non-TEMP table, it is important to specify the database holding the non-TEMP table. For example, in the following statement, it is important to say "main.tab1" instead of just "tab1":
> \
> CREATE TEMP TRIGGER ex1 AFTER INSERT ON **main.**tab1 BEGIN ...\
Failure to specify the schema name on the target table could result in the TEMP trigger being reattached to a table with the same name in another database whenever any schema change occurs.
---
# CREATE VIEW
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_createview.html*
# 1. Syntax
**[create-view-stmt:](syntax/create-view-stmt.md)** hide
**[select-stmt:](syntax/select-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
# 2. Description
The CREATE VIEW command assigns a name to a pre-packaged [SELECT](lang_select.md) statement. Once the view is created, it can be used in the FROM clause of another [SELECT](lang_select.md) in place of a table name.
If the "TEMP" or "TEMPORARY" keyword occurs in between "CREATE" and "VIEW" then the view that is created is only visible to the [database connection](c3ref/sqlite3.md) that created it and is automatically deleted when the database connection is closed.
If a schema-name is specified, then the view is created in the specified database. It is an error to specify both a schema-name and the TEMP keyword on a VIEW, unless the schema-name is "temp". If no schema name is specified, and the TEMP keyword is not present, the VIEW is created in the main database.
You cannot [DELETE](lang_delete.md), [INSERT](lang_insert.md), or [UPDATE](lang_update.md) a view. Views are read-only in SQLite. However, in many cases you can use an [INSTEAD OF trigger](lang_createtrigger.md#instead_of_trigger) on the view to accomplish the same thing. Views are removed with the [DROP VIEW](lang_dropview.md) command.
If a column-name list follows the view-name, then that list determines the names of the columns for the view. If the column-name list is omitted, then the names of the columns in the view are derived from the names of the result-set columns in the [select-stmt](syntax/select-stmt.md). The use of column-name list is recommended. Or, if column-name list is omitted, then the result columns in the [SELECT](lang_select.md) statement that defines the view should have well-defined names using the "[AS column-alias](syntax/result-column.md)" syntax. SQLite allows you to create views that depend on automatically generated column names, but you should avoid using them since the rules used to generate column names are not a defined part of the interface and might change in future releases of SQLite.
The column-name list syntax was added in SQLite versions 3.9.0 (2015-10-14).
---
# CREATE VIRTUAL TABLE
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_createvtab.html*
**[create-virtual-table-stmt:](syntax/create-virtual-table-stmt.md)** hide
A [virtual table](vtab.md) is an interface to an external storage or computation engine that appears to be a table but does not actually store information in the database file.
In general, you can do anything with a [virtual table](vtab.md) that can be done with an ordinary table, except that you cannot create indices or triggers on a virtual table. Some virtual table implementations might impose additional restrictions. For example, many virtual tables are read-only.
The module-name is the name of an object that implements the virtual table. The module-name must be registered with the SQLite database connection using [sqlite3_create_module()](c3ref/create_module.md) or [sqlite3_create_module_v2()](c3ref/create_module.md) prior to issuing the CREATE VIRTUAL TABLE statement. The module takes zero or more comma-separated arguments. The arguments can be just about any text as long as it has balanced parentheses. The argument syntax is sufficiently general that the arguments can be made to appear as [column definitions](lang_createtable.md#tablecoldef) in a traditional [CREATE TABLE](lang_createtable.md) statement. SQLite passes the module arguments directly to the [xCreate](vtab.md#xcreate) and [xConnect](vtab.md#xconnect) methods of the module implementation without any interpretation. It is the responsibility of the module implementation to parse and interpret its own arguments.
A virtual table is destroyed using the ordinary [DROP TABLE](lang_droptable.md) statement. There is no DROP VIRTUAL TABLE statement.
---
# Database Object Name Resolution
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_naming.html*
In SQLite, a database object (a table, index, trigger or view) is identified by the name of the object and the name of the database that it resides in. Database objects may reside in the main database, the temp database, or in an [attached database](lang_attach.md).
The syntax of the [DROP TABLE](lang_droptable.md), [DROP INDEX](lang_dropindex.md), [DROP VIEW](lang_dropview.md), [DROP TRIGGER](lang_droptrigger.md), [REINDEX](lang_reindex.md), [ALTER TABLE](lang_altertable.md) and many other commands all permit the user to specify a database object either by its name alone, or by a combination of its name and the name of its database. If no database is specified as part of the object reference, then SQLite searches the main, temp and all attached databases for an object with a matching name. The temp database is searched first, followed by the main database, followed by all attached databases in the order that they were attached. The reference resolves to the first match found. For example:
\
/\* Add a table named 't1' to the temp, main and an attached database \*/\
ATTACH 'file.db' AS aux;\
CREATE TABLE t1(x, y);\
CREATE TEMP TABLE t1(x, y);\
CREATE TABLE aux.t1(x, y);\
\
DROP TABLE t1; /\* Drop table in temp database \*/\
DROP TABLE t1; /\* Drop table in main database \*/\
DROP TABLE t1; /\* Drop table in aux database \*/\
If a schema name is specified as part of an object reference, it must be either "main", or "temp" or the schema-name of an attached database. Like other SQL identifiers, schema names are case-insensitive. If a schema name is specified, then only that one schema is searched for the named object.
Most object references may only resolve to a specific type of object (for example a reference that is part of a DROP TABLE statement may only resolve to a table object, not an index, trigger or view). However in some contexts (e.g. [REINDEX](lang_reindex.md)) an object reference may be resolved to more than one type of object. When searching database schemas for a named object, objects of types that cannot be used in the context of the reference are always ignored.
---
# Date And Time Functions
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_datefunc.html*
# 1. Overview
SQLite supports seven [scalar](lang_corefunc.md) date and time functions as follows:
1. **date(***time-value, modifier, modifier, ...***)**
2. **time(***time-value, modifier, modifier, ...***)**
3. **datetime(***time-value, modifier, modifier, ...***)**
4. **julianday(***time-value, modifier, modifier, ...***)**
5. **unixepoch(***time-value, modifier, modifier, ...***)**
6. **strftime(***format, time-value, modifier, modifier, ...***)**
7. **timediff(***time-value, time-value***)**
The first six date and time functions take an optional [time-value](lang_datefunc.md#tmval) as an argument, followed by zero or more [modifiers](lang_datefunc.md#dtmods). The strftime() function also takes a format string as its first argument. The timediff() function takes exactly two arguments which are both [time-values](lang_datefunc.md#tmval).
SQLite does not have a dedicated date/time datatype. Instead, date and time values can be stored as any of the following:
> | | |
> |----|----|
> | [ISO-8601](http://en.wikipedia.org/wiki/ISO_8601) | A text string that is one of the ISO 8601 date/time values shown in [items 1 through 10 below](#tmval). Example: `'2025-05-29 14:16:00'` |
> | [Julian day number](http://en.wikipedia.org/wiki/Julian_day) | The number of days including fractional days since -4713-11-24 12:00:00 Example: `2460825.09444444` |
> | [Unix timestamp](https://en.wikipedia.org/wiki/Unix_time) | The number of seconds including fractional seconds since 1970-01-01 00:00:00 Example: `1748528160` |
These three formats are collectively known as [time-values](lang_datefunc.md#tmval). All of the date time functions accept time-values as either ISO-8601 text or as Julian day numbers. They can also be made to accept unix timestamps by adding optional modifier arguments ['auto'](lang_datefunc.md#automod) or ['unixepoch'](lang_datefunc.md#jdmod). Since the timediff() function does not accept modifiers, it can only use ISO-8601 and julian day number time-values.
The **date()** function returns the date as text in this format: YYYY-MM-DD.
The **time()** function returns the time as text in formatted as HH:MM:SS or as HH:MM:SS.SSS if the [subsec modifier](lang_datefunc.md#subsec) is used.
The **datetime()** function returns the date and time formatted as YYYY-MM-DD HH:MM:SS or as YYYY-MM-DD HH:MM:SS.SSS if the [subsec modifier](lang_datefunc.md#subsec) is used.
The **julianday()** function returns the [Julian day](http://en.wikipedia.org/wiki/Julian_day) - the fractional number of days since noon in Greenwich on November 24, 4714 B.C. ([Proleptic Gregorian calendar](http://en.wikipedia.org/wiki/Proleptic_Gregorian_calendar)).
The **unixepoch()** function returns a unix timestamp - the number of seconds since 1970-01-01 00:00:00 UTC. The unixepoch() function normally returns an integer number of seconds, but with the optional [subsec modifier](lang_datefunc.md#subsec) it will return a floating point number which is the fractional number of seconds.
The **strftime()** function returns the date formatted according to the format string specified as the first argument. The format string supports the most common substitutions found in the [strftime() function](https://pubs.opengroup.org/onlinepubs/9799919799/functions/strftime.html) from the standard C library plus two new substitutions, %f and %J. The following is a complete list of valid strftime() substitutions as of version 3.46.0 (2024-05-23). Earlier versions of SQLite might not support all substitutions. If an undefined or unsupported substitution is seen, the result is NULL.
> | | | |
> |-----|-----|-----------------------------------------------------------|
> | | | |
> | %d | | day of month: 01-31 |
> | %e | | day of month without leading zero: 1-31 |
> | %f | | fractional seconds: SS.SSS |
> | %F | | ISO 8601 date: YYYY-MM-DD |
> | %G | | ISO 8601 year corresponding to %V |
> | %g | | 2-digit ISO 8601 year corresponding to %V |
> | %H | | hour: 00-24 |
> | %I | | hour for 12-hour clock: 01-12 |
> | %j | | day of year: 001-366 |
> | %J | | Julian day number (fractional) |
> | %k | | hour without leading zero: 0-24 |
> | %l | | %I without leading zero: 1-12 |
> | %m | | month: 01-12 |
> | %M | | minute: 00-59 |
> | %p | | "AM" or "PM" depending on the hour |
> | %P | | "am" or "pm" depending on the hour |
> | %R | | ISO 8601 time: HH:MM |
> | %s | | seconds since 1970-01-01 |
> | %S | | seconds: 00-59 |
> | %T | | ISO 8601 time: HH:MM:SS |
> | %U | | week of year (00-53) - week 01 starts on the first Sunday |
> | %u | | day of week 1-7 with Monday==1 |
> | %V | | ISO 8601 week of year |
> | %w | | day of week 0-6 with Sunday==0 |
> | %W | | week of year (00-53) - week 01 starts on the first Monday |
> | %Y | | year: 0000-9999 |
> | %% | | % |
Other date and time functions can be expressed in terms of strftime():
> | | | |
> |----------------|-----|-----------------------------------|
> | **Function** | | **Equivalent strftime()** |
> | date(...) | | strftime('%F', ...) |
> | time(...) | | strftime('%T', ...) |
> | datetime(...) | | strftime('%F %T', ...) |
> | julianday(...) | | CAST(strftime('%J', ...) as REAL) |
> | unixepoch(...) | | CAST(strftime('%s', ...) as INT) |
The date(), time(), and datetime() functions all return text, and so their strftime() equivalents are exact. However, the julianday() and unixepoch() functions return numeric values. Their strftime() equivalents return a string that is the text representation of the corresponding number.
The main reasons for providing functions other than strftime() are for convenience and for efficiency. The julianday() and unixepoch() functions return real and integer values respectively, and do not incur the format conversion costs or inexactitude resulting from use of the '%J' or '%s' format specifiers with the strftime() function.
The **timediff(A,B)** function returns a string that describes the amount of time that must be added to B in order to reach time A. The format of the timediff() result is designed to be human-readable. The format is:
> (+\|-)YYYY-MM-DD HH:MM:SS.SSS
This time difference string is also an allowed modifier for the other date/time functions. The following invariant holds for time-values A and B:
> datetime(A) = datetime(B, timediff(A,B))
The length of months and years vary. February is shorter than March. Leap years are longer than non-leap years. The output from timediff() takes this all into account. The timediff() function is intended to provide a human-friendly description of the time span. If you want to know the number of days or seconds between two dates, A and B, then you can always do one of these:
> SELECT julianday(B) - julianday(A);\
> SELECT unixepoch(B) - unixepoch(A);
The timediff(A,B) might return the same result even for values A and B that span a different number of days - depending on the starting date. For example, both of the following two timediff() calls return the same result ("-0000-01-00 00:00:00.000") even though the first timespan is 28 days and the second is 31 days:
> SELECT timediff('2023-02-15','2023-03-15');\
> SELECT timediff('2023-03-15','2023-04-15');
Summary: If you want a human-friendly time span, use timediff(). If you want a precise time difference (in days or seconds) use the difference between two julianday() or unixepoch() calls.
# 2. Time Values
A time-value can be in any of the following formats shown below. The value is usually a string, though it can be an integer or floating point number in the case of format 12.
1. *YYYY-MM-DD*
2. *YYYY-MM-DD HH:MM*
3. *YYYY-MM-DD HH:MM:SS*
4. *YYYY-MM-DD HH:MM:SS.SSS*
5. *YYYY-MM-DD***T***HH:MM*
6. *YYYY-MM-DD***T***HH:MM:SS*
7. *YYYY-MM-DD***T***HH:MM:SS.SSS*
8. *HH:MM*
9. *HH:MM:SS*
10. *HH:MM:SS.SSS*
11. **now**
12. *DDDDDDDDDD*
In formats 5 through 7, the "T" is a literal character separating the date and the time, as required by [ISO-8601](http://www.w3c.org/TR/NOTE-datetime). Formats 8 through 10 that specify only a time assume a date of 2000-01-01. Format 11, the string 'now', is converted into the current date and time as obtained from the xCurrentTime method of the [sqlite3_vfs](c3ref/vfs.md) object in use. The 'now' argument to date and time functions always returns exactly the same value for multiple invocations within the same [sqlite3_step()](c3ref/step.md) call. [Universal Coordinated Time (UTC)](http://en.wikipedia.org/wiki/Coordinated_Universal_Time) is used. Format 12 is the [Julian day number](http://en.wikipedia.org/wiki/Julian_day) expressed as an integer or floating point value. Format 12 might also be interpreted as a unix timestamp if it is immediately followed either the ['auto'](lang_datefunc.md#automod) or ['unixepoch'](lang_datefunc.md#jdmod) modifier.
Formats 2 through 10 may be optionally followed by a timezone indicator of the form "*\[+-\]HH:MM*" or just "*Z*". The date and time functions use UTC or "zulu" time internally, and so the "Z" suffix is a no-op. Any non-zero "HH:MM" suffix is subtracted from the indicated date and time in order to compute zulu time. For example, all of the following time-values are equivalent:
> 2013-10-07 08:23:19.120\
> 2013-10-07T08:23:19.120Z\
> 2013-10-07 04:23:19.120-04:00\
> 2456572.84952685
In formats 4, 7, and 10, the fractional seconds value SS.SSS can have one or more digits following the decimal point. Exactly three digits are shown in the examples because only the first three digits are significant to the result, but the input string can have fewer or more than three digits and the date/time functions will still operate correctly. Similarly, format 12 is shown with 10 significant digits, but the date/time functions will really accept as many or as few digits as are necessary to represent the Julian day number.
[ISO-8601](http://www.w3c.org/TR/NOTE-datetime) supports a wide variety of alternative date/time formats, but SQLite only supports the ones specifically enumerated above.
In all functions other than timediff(), the time-value (and all modifiers) may be omitted, in which case a time value of 'now' is assumed.
# 3. Modifiers
For all date/time functions other than timediff(), the time-value argument can be followed by zero or more modifiers that alter date and/or time. Each modifier is a transformation that is applied to the time-value to its left. Modifiers are applied from left to right; order is important. The available modifiers are as follows.
1. NNN days
2. NNN hours
3. NNN minutes
4. NNN seconds
5. NNN months
6. NNN years
7. ±HH:MM
8. ±HH:MM:SS
9. ±HH:MM:SS.SSS
10. ±YYYY-MM-DD
11. ±YYYY-MM-DD HH:MM
12. ±YYYY-MM-DD HH:MM:SS
13. ±YYYY-MM-DD HH:MM:SS.SSS
14. ceiling
15. floor
16. start of month
17. start of year
18. start of day
19. weekday N
20. unixepoch
21. julianday
22. auto
23. localtime
24. utc
25. subsec
26. subsecond
The first thirteen modifiers (1 through 13) add the specified amount of time to the date and time specified by the arguments to its left. The 's' character at the end of the modifier names in 1 through 6 is optional. The NNN value can be any floating point number, with an optional '+' or '-' prefix.
The **time shift modifiers** (7 through 13) move the time-value by the number of years, months, days, hours, minutes, and/or seconds specified. An initial "+" or "-" is required for formats 10 through 13 but is optional for formats 7, 8, and 9. The changes are applied from left to right. First the year is shifted by YYYY, then the month by MM, and then day by DD, and so forth. The timediff(A,B) function returns a time shift in format 13 that shifts the time-value B into A.
Because the length of a month or year changes from one month or year to the next, ambiguities can arise when shifting a date by months and/or years. For example, what is the date one year after 2024-02-29? Is it 2025-02-28 or 2025-03-01? Or what is the date that is two months after 2023-12-31? Is it 2024-02-29 or 2024-03-02? There is no consensus on how to resolve this ambiguity, so the "**ceiling**" and "**floor**" modifiers (14 and 15) are available to let the programmer decide. If the next modifier after a time shift is "ceiling", then any ambiguity in the date is resolved by choosing the later date. The "floor" modifier resolves ambiguities by resolving to the last day of the previous month. The default behavior is "ceiling".
The "**start of**" modifiers (16 through 18) shift the date backwards to the beginning of the subject month, year or day.
The "**weekday**" modifier advances the date forward, if necessary, to the next date where the weekday number is N. Sunday is 0, Monday is 1, and so forth. If the date is already on the desired weekday, the "weekday" modifier leaves the date unchanged.
The "**unixepoch**" modifier (20) only works if it immediately follows a time-value in the DDDDDDDDDD format. This modifier causes the DDDDDDDDDD to be interpreted not as a Julian day number as it normally would be, but as [Unix Time](http://en.wikipedia.org/wiki/Unix_time) - the number of seconds since 1970. If the "unixepoch" modifier does not follow a time-value of the form DDDDDDDDDD which expresses the number of seconds since 1970 or if other modifiers separate the "unixepoch" modifier from prior DDDDDDDDDD then the behavior is undefined.
The "**julianday**" modifier must immediately follow the initial time-value which must be of the form DDDDDDDDD. Any other use of the 'julianday' modifier is an error and causes the function to return NULL. The 'julianday' modifier forces the time-value number to be interpreted as a julian-day number. As this is the default behavior, the 'julianday' modifier is scarcely more than a no-op. The only difference is that adding 'julianday' forces the DDDDDDDDD time-value format, and causes a NULL to be returned if any other time-value format is used.
The "**auto**" modifier must immediately follow the initial time-value. If the time-value is numeric (the DDDDDDDDDD format) then the 'auto' modifier causes the time-value to be interpreted as either a julian day number or a unix timestamp, depending on its magnitude. If the value is between 0.0 and 5373484.499999, then it is interpreted as a julian day number (corresponding to dates between -4713-11-24 12:00:00 and 9999-12-31 23:59:59, inclusive). For numeric values outside of the range of valid julian day numbers, but within the range of -210866760000 to 253402300799, the 'auto' modifier causes the value to be interpreted as a unix timestamp. Other numeric values are out of range and cause a NULL return. The 'auto' modifier is a no-op for ISO 8601 text time-values. The "auto" modifier is designed to work with time-values even in cases where it is not known which time-value format is stored in the database file, or in cases where the same column stores time-values in different formats on different rows. The 'auto' modifier will automatically select the appropriate format. However, there is some ambiguity. Unix timestamps for the first 63 days of 1970 will be interpreted as julian day numbers. The 'auto' modifier is very useful when the dataset is guaranteed to contain no dates within that range, but should be avoided for applications that might make use of dates in the opening months of 1970.
The "**localtime**" modifier assumes the time-value to its left is in Universal Coordinated Time (UTC) and adjusts that time value so that it is in localtime. If "localtime" follows a time that is not UTC, then the behavior is undefined. The "**utc**" modifier is the opposite of "localtime". "utc" assumes that the time-value to its left is in the local timezone and adjusts that time-value to be in UTC. If the time to the left is not in localtime, then the result of "utc" is undefined.
The "**subsecond**" modifier (which may be abbreviated as just "**subsec**") increases the resolution of the output for [datetime()](lang_datefunc.md#dttm), [time()](lang_datefunc.md#dttm), and [unixepoch()](lang_datefunc.md#uepch), and for the "%s" format string in [strftime()](lang_datefunc.md#strftm). The "subsecond" modifier has no effect on other date/time functions. The current implemention increases the resolution from seconds to milliseconds, but this might increase to a higher resolution in future releases of SQLite. When "subsec" is used with [datetime()](lang_datefunc.md#dttm) or [time()](lang_datefunc.md#dttm), the seconds field at the end is followed by a decimal point and one or more digits to show fractional seconds. When "subsec" is used with [unixepoch()](lang_datefunc.md#uepch), the result is a floating point value which is the number of seconds and fractional seconds since 1970-01-01. The "subsecond" and "subsec" modifiers have the special property that they can occur as the first argument to date/time functions (or as the first argument after the format string for strftime()). When this happens, the time-value that is normally in the first argument is understood to be "now". For example, a short cut to get the current time in seconds since 1970 with millisecond precision is to say:
> SELECT unixepoch('subsec');
# 4. Examples
Compute the current date.
> SELECT date();
Compute the last day of the current month.
> SELECT date('now','start of month','+1 month','-1 day');
Compute the date and time given a unix timestamp 1092941466.
> SELECT datetime(1092941466, 'unixepoch');\
> SELECT datetime(1092941466, 'auto'); -- Does not work for early 1970!
Compute the date and time given a unix timestamp 1092941466, and compensate for your local timezone.
> SELECT datetime(1092941466, 'unixepoch', 'localtime');
Compute the current unix timestamp.
> SELECT unixepoch();\
> SELECT strftime('%s');
Compute the number of days since the signing of the US Declaration of Independence.
> SELECT julianday('now') - julianday('1776-07-04');
Compute the number of seconds since a particular moment in 2004:
> SELECT unixepoch() - unixepoch('2004-01-01 02:34:56');
Compute the date of the first Tuesday in October for the current year.
> SELECT date('now','start of year','+9 months','weekday 2');
Compute the time since the unix epoch in seconds with millisecond precision:
> SELECT (julianday('now') - 2440587.5)\*86400.0;\
> SELECT unixepoch('now','subsec');
Compute how old Abraham Lincoln would be if he were still alive today:
> SELECT timediff('now','1809-02-12');
# 5. Caveats And Bugs
The computation of local time depends heavily on the whim of politicians and is thus difficult to get correct for all locales. In this implementation, the standard C library function localtime_r() is used to assist in the calculation of local time. The localtime_r() C function normally only works for years between 1970 and 2037. For dates outside this range, SQLite attempts to map the year into an equivalent year within this range, do the calculation, then map the year back.
These functions only work for dates between 0000-01-01 00:00:00 and 9999-12-31 23:59:59 (julian day numbers 1721059.5 through 5373484.5). For dates outside that range, the results of these functions are undefined.
Non-Vista Windows platforms only support one set of DST rules. Vista only supports two. Therefore, on these platforms, historical DST calculations will be incorrect. For example, in the US, in 2007 the DST rules changed. Non-Vista Windows platforms apply the new 2007 DST rules to all previous years as well. Vista does somewhat better getting results correct back to 1986, when the rules were also changed.
All internal computations assume the [Gregorian calendar](http://en.wikipedia.org/wiki/Gregorian_calendar) system. They also assume that every day is exactly 86400 seconds in duration; no leap seconds are incorporated.
---
# DELETE
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_delete.html*
# 1. Overview
**[delete-stmt:](syntax/delete-stmt.md)** hide
**[common-table-expression:](syntax/common-table-expression.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[qualified-table-name:](syntax/qualified-table-name.md)** show
**[returning-clause:](syntax/returning-clause.md)** show
The DELETE command removes records from the table identified by the [qualified-table-name](syntax/qualified-table-name.md).
If the WHERE clause is not present, all records in the table are deleted. If a WHERE clause is supplied, then only those rows for which the WHERE clause [boolean expression](lang_expr.md#booleanexpr) is true are deleted. 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](lang_createtrigger.md) statement:
- The table-name specified as part of a DELETE statement within a trigger body must be unqualified. In other words, the *schema-name***.** prefix on the table name is not allowed within triggers. If the table to which the trigger is attached is not in the temp database, then DELETE statements within the trigger body must operate on tables within the same database as it. If the table to which the trigger is attached is in the TEMP database, then the unqualified name of the table being deleted is resolved in the same way as it is for a top-level statement (by searching first the TEMP database, then the main database, then any other databases in the order they were attached).
- The INDEXED BY and NOT INDEXED clauses are not allowed on DELETE statements within triggers.
- The LIMIT and ORDER BY clauses (described below) are unsupported for DELETE statements within triggers.
- The RETURNING clause is not supported for triggers.
# 3. Optional LIMIT and ORDER BY clauses
If SQLite is compiled with the [SQLITE_ENABLE_UPDATE_DELETE_LIMIT](compile.md#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:
**[delete-stmt-limited:](syntax/delete-stmt-limited.md)**
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. If the result of evaluating the LIMIT clause cannot be losslessly converted to an integer value, it is an error. A negative LIMIT value is interpreted as "no limit". 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. If there is no OFFSET clause, or the calculated integer value is negative, the effective OFFSET value is zero.
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. 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.
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.
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. This means that if there is a [RETURNING clause](lang_returning.md), the rows returned by the statement probably will not be in the order specified by the ORDER BY clause.
# 4. The Truncate Optimization
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](releaselog/3_6_5.md) (2008-11-12), the truncate optimization also meant that the [sqlite3_changes()](c3ref/changes.md) and [sqlite3_total_changes()](c3ref/total_changes.md) interfaces and the [count_changes pragma](pragma.md#pragma_count_changes) will not actually return the number of deleted rows. That problem has been fixed as of [version 3.6.5](releaselog/3_6_5.md) (2008-11-12).
The truncate optimization can be permanently disabled for all queries by recompiling SQLite with the [SQLITE_OMIT_TRUNCATE_OPTIMIZATION](compile.md#omit_truncate_optimization) compile-time switch.
The truncate optimization can also be disabled at runtime using the [sqlite3_set_authorizer()](c3ref/set_authorizer.md) interface. If an authorizer callback returns [SQLITE_IGNORE](c3ref/c_deny.md) for an [SQLITE_DELETE](c3ref/c_alter_table.md) action code, then the DELETE operation will proceed but the truncate optimization will be bypassed and rows will be deleted one by one.
---
# DETACH
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_detach.html*
**[detach-stmt:](syntax/detach-stmt.md)** hide
This statement detaches an additional database connection previously attached using the [ATTACH](lang_attach.md) statement. When not in [shared cache mode](sharedcache.md), it is possible to have the same database file attached multiple times using different names, and detaching one connection to a file will leave the others intact.
In [shared cache mode](sharedcache.md), attempting to attach the same database file more than once results in an error.
---
# DROP INDEX
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_dropindex.html*
**[drop-index-stmt:](syntax/drop-index-stmt.md)** hide
The DROP INDEX statement removes an index added with the [CREATE INDEX](lang_createindex.md) statement. The index is completely removed from the disk. The only way to recover the index is to reenter the appropriate [CREATE INDEX](lang_createindex.md) command.
---
# DROP TABLE
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_droptable.html*
**[drop-table-stmt:](syntax/drop-table-stmt.md)** hide
The DROP TABLE statement removes a table added with the [CREATE TABLE](lang_createtable.md) statement. The name specified is the table name. The dropped table is completely removed from the database schema and the disk file. The table can not be recovered. All indices and triggers associated with the table are also deleted.
The optional IF EXISTS clause suppresses the error that would normally result if the table does not exist.
If [foreign key constraints](foreignkeys.md) are enabled, a DROP TABLE command performs an implicit [DELETE FROM](lang_delete.md) command before removing the table from the database schema. Any triggers attached to the table are dropped from the database schema before the implicit DELETE FROM is executed, so this cannot cause any triggers to fire. By contrast, an implicit DELETE FROM does cause any configured [foreign key actions](foreignkeys.md#fk_actions) to take place. If the implicit DELETE FROM executed as part of a DROP TABLE command violates any immediate foreign key constraints, an error is returned and the table is not dropped. If the implicit DELETE FROM causes any deferred foreign key constraints to be violated, and the violations still exist when the transaction is committed, an error is returned at the time of commit.
---
# DROP TRIGGER
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_droptrigger.html*
**[drop-trigger-stmt:](syntax/drop-trigger-stmt.md)** hide
The DROP TRIGGER statement removes a trigger created by the [CREATE TRIGGER](lang_createtrigger.md) statement. Once removed, the trigger definition is no longer present in the [sqlite_schema](schematab.md) (or sqlite_temp_schema) table and is not fired by any subsequent INSERT, UPDATE or DELETE statements.
Note that triggers are automatically dropped when the associated table is dropped.
---
# DROP VIEW
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_dropview.html*
**[drop-view-stmt:](syntax/drop-view-stmt.md)** hide
The DROP VIEW statement removes a view created by the [CREATE VIEW](lang_createview.md) statement. The view definition is removed from the database schema, but no actual data in the underlying base tables is modified.
The view to drop is identified by the view-name and optional schema-name specified as part of the DROP VIEW statement. This reference is resolved using the standard procedure for [object resolution](lang_naming.md).
If the specified view cannot be found and the IF EXISTS clause is not present, it is an error. If the specified view cannot be found and an IF EXISTS clause is present in the DROP VIEW statement, then the statement is a no-op.
---
# EXPLAIN
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_explain.html*
# 1. Syntax
**[sql-stmt:](syntax/sql-stmt.md)**
# 2. Description
An SQL statement can be preceded by the keyword "EXPLAIN" or by the phrase "EXPLAIN QUERY PLAN". Either modification causes the SQL statement to behave as a query and to return information about how the SQL statement would have operated if the EXPLAIN keyword or phrase had been omitted.
The output from EXPLAIN and EXPLAIN QUERY PLAN is intended for interactive analysis and troubleshooting only. The details of the output format are subject to change from one release of SQLite to the next. Applications should not use EXPLAIN or EXPLAIN QUERY PLAN since their exact behavior is variable and only partially documented.
When the EXPLAIN keyword appears by itself it causes the statement to behave as a query that returns the sequence of [virtual machine instructions](opcode.md) it would have used to execute the command had the EXPLAIN keyword not been present. When the EXPLAIN QUERY PLAN phrase appears, the statement returns high-level information regarding the query plan that would have been used.
The EXPLAIN QUERY PLAN command is described in [more detail here](eqp.md).
## 2.1. EXPLAIN operates at run-time, not at prepare-time
The EXPLAIN and EXPLAIN QUERY PLAN prefixes affect the behavior of running a [prepared statement](c3ref/stmt.md) using [sqlite3_step()](c3ref/step.md). The process of generating a new prepared statement using [sqlite3_prepare()](c3ref/prepare.md) or similar is (mostly) unaffected by EXPLAIN. (The exception to the previous sentence is that some special opcodes used by EXPLAIN QUERY PLAN are omitted when building an EXPLAIN QUERY PLAN prepared statement, as a performance optimization.)
This means that actions that occur during sqlite3_prepare() are unaffected by EXPLAIN.
- Some [PRAGMA](pragma.md#syntax) statements do their work during sqlite3_prepare() rather than during sqlite3_step(). Those PRAGMA statements are unaffected by EXPLAIN. They operate the same with or without the EXPLAIN prefix. The set of PRAGMA statements that are unaffected by EXPLAIN can vary from one release to the next. Some PRAGMA statements operate during sqlite3_prepare() depending on their arguments. For consistent results, avoid using EXPLAIN on PRAGMA statements.
- The [authorizer callback](c3ref/set_authorizer.md) is invoked regardless of the presence of EXPLAIN or EXPLAIN QUERY PLAN.
---
# INSERT
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_insert.html*
# 1. Overview
**[insert-stmt:](syntax/insert-stmt.md)** hide
**[common-table-expression:](syntax/common-table-expression.md)** show
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[returning-clause:](syntax/returning-clause.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[upsert-clause:](syntax/upsert-clause.md)** show
**[column-name-list:](syntax/column-name-list.md)** show
**[indexed-column:](syntax/indexed-column.md)** show
The INSERT statement comes in three basic forms.
1. **INSERT INTO** *table* **VALUES(...);**
The first form (with the "VALUES" keyword) creates one or more new rows in an existing table. If the column-name list after table-name is omitted then the number of values inserted into each row must be the same as the number of columns in the table. In this case the result of evaluating the left-most expression from each term of the VALUES list is inserted into the left-most column of each new row, and so forth for each subsequent expression. If a column-name list is specified, then the number of values in each term of the VALUE list must match the number of specified columns. Each of the named columns of the new row is populated with the results of evaluating the corresponding VALUES expression. Table columns that do not appear in the column list are populated with the [default column value](lang_createtable.md#dfltval) (specified as part of the [CREATE TABLE](lang_createtable.md) statement), or with NULL if no [default value](lang_createtable.md#dfltval) is specified.
2. **INSERT INTO** *table* **SELECT ...;**
The second form of the INSERT statement contains a [SELECT](lang_select.md) statement instead of a VALUES clause. A new entry is inserted into the table for each row of data returned by executing the SELECT statement. If a column-list is specified, the number of columns in the result of the SELECT must be the same as the number of items in the column-list. Otherwise, if no column-list is specified, the number of columns in the result of the SELECT must be the same as the number of columns in the table. Any SELECT statement, including [compound SELECTs](lang_select.md#compound) and SELECT statements with [ORDER BY](lang_select.md#orderby) and/or [LIMIT](lang_select.md#limitoffset) clauses, may be used in an INSERT statement of this form.
To avoid a parsing ambiguity, the SELECT statement should always contain a WHERE clause, even if that clause is simply "WHERE true", if the [upsert-clause](syntax/upsert-clause.md) is present. Without the WHERE clause, the parser does not know if the token "ON" is part of a join constraint on the SELECT, or the beginning of the [upsert-clause](syntax/upsert-clause.md).
3. **INSERT INTO** *table* **DEFAULT VALUES;**
The third form of an INSERT statement is with DEFAULT VALUES. The INSERT ... DEFAULT VALUES statement inserts a single new row into the named table. Each column of the new row is populated with its [default value](lang_createtable.md#dfltval), or with a NULL if no default value is specified as part of the column definition in the [CREATE TABLE](lang_createtable.md) statement. The [upsert-clause](syntax/upsert-clause.md) is not supported after DEFAULT VALUES.
The initial "INSERT" keyword can be replaced by "REPLACE" or "INSERT OR *action*" to specify an alternative constraint [conflict resolution algorithm](lang_conflict.md) to use during that one INSERT command. For compatibility with MySQL, the parser allows the use of the single keyword [REPLACE](lang_replace.md) as an alias for "INSERT OR REPLACE".
The optional "*schema-name***.**" prefix on the table-name is supported for top-level INSERT statements only. The table name must be unqualified for INSERT statements that occur within [CREATE TRIGGER](lang_createtrigger.md) statements. Similarly, the "DEFAULT VALUES" form of the INSERT statement is supported for top-level INSERT statements only and not for INSERT statements within triggers.
The optional "AS alias" phrase provides an alternative name for the table into which content is being inserted. The alias name can be used within WHERE and SET clauses of the [UPSERT](lang_upsert.md). If there is no [upsert-clause](syntax/upsert-clause.md), then the alias is pointless, but also harmless.
See the separate [UPSERT](lang_upsert.md) documentation for the additional trailing syntax that can cause an INSERT to behave as an UPDATE if the INSERT would otherwise violate a uniqueness constraint. The [upsert clause](lang_upsert.md) is not allowed on an "INSERT ... DEFAULT VALUES".
---
# REINDEX
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_reindex.html*
**[reindex-stmt:](syntax/reindex-stmt.md)** hide
The REINDEX command is used to delete and recreate indexes from scratch. This is useful when the definition of a collation sequence has changed, or when there are [indexes on expressions](expridx.md) involving a function whose definition has changed.
If the REINDEX keyword is not followed by a collation-sequence or database object identifier or the keyword "EXPRESSIONS", then all indexes in all attached databases are rebuilt.
If the REINDEX keyword is followed by a collation-sequence name, then all indexes in all attached databases that use the named collation sequences are recreated.
Or, if the argument attached to the REINDEX identifies a specific database table, then all indexes attached to the database table are rebuilt. If it identifies a specific database index, then just that index is recreated.
If the argument is "EXPRESSIONS", then all [indexes on expressions](expridx.md) are rebuilt. The ability to rebuild expression indexes in a single command like this is new as of SQLite version 3.53.0 (2026-04-09).
For a command of the form "REINDEX *name*", a match against collation-name takes precedence over a match against index-name or table-name. This ambiguity in the syntax may be avoided by always specifying a schema-name when reindexing a specific table or index. If *name* is EXPRESSIONS, then in addition to rebuilding all expression indexes, the command also rebuilds any indexes that use a collating sequence named "expressions" or the indexes of a table named "expressions" or an index named "expressions", following the precedence rules above.
---
# REPLACE
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_replace.html*
The REPLACE command is an alias for the "[INSERT OR REPLACE](lang_conflict.md)" variant of the [INSERT](lang_insert.md) command. This alias is provided for compatibility other SQL database engines. See the [INSERT](lang_insert.md) command documentation for additional information.
---
# RETURNING
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_returning.html*
# 1. Overview
**[returning-clause:](syntax/returning-clause.md)** hide
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
The RETURNING clause is not a statement itself, but a clause that can optionally appear near the end of top-level [DELETE](lang_delete.md), [INSERT](lang_insert.md), and [UPDATE](lang_update.md) statements. The effect of the RETURNING clause is to cause the statement to return one result row for each database row that is deleted, inserted, or updated. RETURNING is not standard SQL. It is an extension. SQLite's syntax for RETURNING is modelled after [PostgreSQL](https://www.postgresql.org).
The RETURNING syntax has been supported by SQLite since version 3.35.0 (2021-03-12).
## 1.1. Typical Use
The RETURNING clause is designed to provide the application with the values of columns that are filled in automatically by SQLite. For example:
CREATE TABLE t0(\
a INTEGER PRIMARY KEY,\
b DATE DEFAULT CURRENT_TIMESTAMP,\
c INTEGER\
);\
INSERT INTO t0(c) VALUES(random()) RETURNING \*;\
In the INSERT statement above, SQLite computes the values for all three columns. The RETURNING clause causes SQLite to report the chosen values back to the application. This saves the application from having to issue a separate query to figure out exactly what values were inserted.
# 2. Details
The RETURNING clause is followed by a comma-separated list of expressions. These expressions are similar to the expressions following the SELECT keyword in a [SELECT statement](lang_select.md) in that they define the values of the columns in the result set. Each expression defines the value for a single column. Each expression may be optionally followed by an AS clause that determines the name of the result column. The special "\*" expression expands into a list of all [non-hidden](vtab.md#hiddencol) columns of the table being deleted, inserted, or updated.
For INSERT and UPDATE statements, references to columns in the table being modified refer to the value of that column *after* the change has been applied. For DELETE statements, references to columns mean the value *before* the delete occurs.
The RETURNING clause only returns rows that are directly modified by the DELETE, INSERT, or UPDATE statement. The RETURNING clause does not report any additional database changes caused by [foreign key constraints](foreignkeys.md) or [triggers](lang_createtrigger.md).
A RETURNING clause for an [UPSERT](lang_upsert.md) reports both inserted and updated rows.
## 2.1. Processing Order
When a DELETE, INSERT, or UPDATE statement with a RETURNING clause is run, all of the database changes occur during the first invocation of [sqlite3_step()](c3ref/step.md). The RETURNING clause output is accumulated in memory. The first sqlite3_step() call returns one row of RETURNING output and subsequent rows of RETURNING output are returned by subsequent calls to sqlite3_step(). To put this another way, all RETURNING clause output is embargoed until after all database modification actions are completed.
This means that if a statement has a RETURNING clause that generates a large amount of output, either many rows or large string or BLOB values, then the statement might use a lot of temporary memory to hold those values while it is running.
While SQLite does guarantee that all database changes will occur before any RETURNING output is emitted, it does *not* guarantee that the order of individual RETURNING rows will match the order in which those rows were changed in the database. The output order for the RETURNING rows is arbitrary and is not necessarily related to the order in which the rows were processed internally.
## 2.2. Self-Referential Subqueries Are Indeterminate
SQLite guarantees that all database changes will occur before any RETURNING output is *emitted*, but SQLite makes no guarantees about the order in which database changes occur nor when the RETURNING output is *computed* in relation to those database changes. RETURNING clause outputs are all computed and placed in temporary storage during the first call to sqlite3_step() but the specific order of when those outputs are computed and the order in which database changes occur is unspecified. The order can change from one query to the next.
Hence if a column of RETURNING output contains a subquery that references the table being modified, then the result of that subquery might depend on unspecified behavior and hence could vary from one invocation of the query to the next.
## 2.3. ACID Changes
When the previous "*Processing Order*" section says that "database changes occur during the first invocation of sqlite3_step()", that means that the changes are stored in the private page cache of the database connection that is running the statement. It does *not* mean that the changes are actually committed. The commit does not occur until the statement finishes, and maybe not even then if the statement is part of a larger transaction. Changes to the database are still atomic, consistent, isolated, and durable (ACID). When the previous section says "changes occur", this means that internal data structures are adjusted pending a transaction commit. Some of those changes may or may not spill into the [write-ahead log](wal.md), depending on how much pressure there is on the page cache. If the page cache is not under memory pressure, then probably nothing will be written to disk until after the transaction completes, which is after sqlite3_step() returns SQLITE_DONE.
In other words, when the previous section says "database changes occur", that means that the changes occur in the memory of the specific database connection that is running the statement, *not* that the changes are written to disk.
# 3. Limitations And Caveats
1. The RETURNING clause is not available on DELETE and UPDATE statements against [virtual tables](vtab.md). This limitation might be removed in future versions of SQLite.
2. The RETURNING clause is only available in top-level DELETE, INSERT, and UPDATE statements. The RETURNING clause cannot be used by statements within triggers.
3. Even though a DML statement with a RETURNING clause returns table content, it cannot be used as a subquery. The RETURNING clause can only return data to the application. It is not currently possible to divert the RETURNING output into another table or query. PostgreSQL has the ability to use a DML statement with a RETURNING clause like a view in a [common table expressions](lang_with.md). SQLite does not currently have that ability, though that is something that might be added in a future release.
4. The rows emitted by the RETURNING clause appear in an arbitrary order. That order might change depending on the database schema, upon the specific release of SQLite used, or even from one execution of the same statement to the next. There is no way to cause the output rows to appear in a particular order. Even if SQLite is compiled with the [SQLITE_ENABLE_UPDATE_DELETE_LIMIT](compile.md#enable_update_delete_limit) option such that ORDER BY clauses are allowed on DELETE and UPDATE statements, those ORDER BY clauses do not constrain the output order of RETURNING.
5. The values emitted by the RETURNING clause are the values as seen by the top-level DELETE, INSERT, or UPDATE statement and do not reflect any subsequent value changes made by [triggers](lang_createtrigger.md). Thus, if the database includes AFTER triggers that modifies some of the values of each row inserted or updated, the RETURNING clause emits the original values that are computed before those triggers run.
6. The RETURNING clause may not contain top-level [aggregate functions](lang_aggfunc.md) or [window functions](windowfunctions.md). If there are subqueries in the RETURNING clause, those subqueries may contain aggregates and window functions, but aggregates cannot occur at the top level.
7. The RETURNING clause may only reference the table being modified. In an [UPDATE FROM](lang_update.md#upfrom) statement, the auxiliary tables named in the FROM clause may not participate in the RETURNING clause.
---
# Savepoints
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_savepoint.html*
# 1. Syntax
**[savepoint-stmt:](syntax/savepoint-stmt.md)** hide
**[release-stmt:](syntax/release-stmt.md)** hide
**[rollback-stmt:](syntax/rollback-stmt.md)** hide
# 2. Savepoints
SAVEPOINTs are a method of creating transactions, similar to [BEGIN](lang_transaction.md) and [COMMIT](lang_transaction.md), except that the SAVEPOINT and RELEASE commands are named and may be nested.
The SAVEPOINT command starts a new transaction with a name. The transaction names need not be unique. A SAVEPOINT can be started either within or outside of a [BEGIN](lang_transaction.md)...[COMMIT](lang_transaction.md). When a SAVEPOINT is the outer-most savepoint and it is not within a [BEGIN](lang_transaction.md)...[COMMIT](lang_transaction.md) then the behavior is the same as BEGIN DEFERRED TRANSACTION.
The ROLLBACK TO command reverts the state of the database back to what it was just after the corresponding SAVEPOINT. Note that unlike that plain [ROLLBACK](lang_transaction.md) command (without the TO keyword) the ROLLBACK TO command does not cancel the transaction. Instead of cancelling the transaction, the ROLLBACK TO command restarts the transaction again at the beginning. All intervening SAVEPOINTs are canceled, however.
The RELEASE command is like a [COMMIT](lang_transaction.md) for a SAVEPOINT. The RELEASE command causes all savepoints back to and including the most recent savepoint with a matching name to be removed from the transaction stack. The RELEASE of an inner transaction does not cause any changes to be written to the database file; it merely removes savepoints from the transaction stack such that it is no longer possible to ROLLBACK TO those savepoints. If a RELEASE command releases the outermost savepoint, so that the transaction stack becomes empty, then RELEASE is the same as [COMMIT](lang_transaction.md). The [COMMIT](lang_transaction.md) command may be used to release all savepoints and commit the transaction even if the transaction was originally started by a SAVEPOINT command instead of a [BEGIN](lang_transaction.md) command.
If the savepoint-name in a RELEASE command does not match any savepoint currently in the transaction stack, then no savepoints are released, the database is unchanged, and the RELEASE command returns an error.
Note that an inner transaction might commit (using the RELEASE command) but then later have its work undone by a ROLLBACK in an outer transaction. A power failure or program crash or OS crash will cause the outer-most transaction to rollback, undoing all changes that have occurred within that outer transaction, even changes that have supposedly been "committed" by the RELEASE command. Content is not actually committed on the disk until the outermost transaction commits.
There are several ways of thinking about the RELEASE command:
- Some people view RELEASE as the equivalent of COMMIT for a SAVEPOINT. This is an acceptable point of view as long as one remembers that the changes committed by an inner transaction might later be undone by a rollback in an outer transaction.
- Another view of RELEASE is that it merges a named transaction into its parent transaction, so that the named transaction and its parent become the same transaction. After RELEASE, the named transaction and its parent will commit or rollback together, whatever their fate may be.
- One can also think of savepoints as "marks" in the transaction timeline. In this view, the SAVEPOINT command creates a new mark, the ROLLBACK TO command rewinds the timeline back to a point just after the named mark, and the RELEASE command erases marks from the timeline without actually making any changes to the database.
# 3. Transaction Nesting Rules
The last transaction started will be the first transaction committed or rolled back.
The [BEGIN](lang_transaction.md) command only works if the transaction stack is empty, or in other words if there are no pending transactions. If the transaction stack is not empty when the [BEGIN](lang_transaction.md) command is invoked, then the command fails with an error.
The [COMMIT](lang_transaction.md) command commits all outstanding transactions and leaves the transaction stack empty.
The RELEASE command starts with the most recent addition to the transaction stack and releases savepoints backwards in time until it releases a savepoint with a matching savepoint-name. Prior savepoints, even savepoints with matching savepoint-names, are unchanged. If the RELEASE command causes the transaction stack to become empty (if the RELEASE command releases the outermost transaction from the stack) then the transaction commits.
The [ROLLBACK](lang_transaction.md) command without a TO clause rolls backs all transactions and leaves the transaction stack empty.
The ROLLBACK command with a TO clause rolls back transactions going backwards in time back to the most recent SAVEPOINT with a matching name. The SAVEPOINT with the matching name remains on the transaction stack, but all database changes that occurred after that SAVEPOINT was created are rolled back. If the savepoint-name in a ROLLBACK TO command does not match any SAVEPOINT on the stack, then the ROLLBACK command fails with an error and leaves the state of the database unchanged.
---
# SELECT
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_select.html*
# 1. Overview
**[select-stmt:](syntax/select-stmt.md)** hide
**[common-table-expression:](syntax/common-table-expression.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
The SELECT statement is used to query the database. The result of a SELECT is zero or more rows of data where each row has a fixed number of columns. A SELECT statement does not make any changes to the database.
The "[select-stmt](syntax/select-stmt.md)" syntax diagram above attempts to show as much of the SELECT statement syntax as possible in a single diagram, because some readers find that helpful. The following "[factored-select-stmt](syntax/factored-select-stmt.md)" is an alternative syntax diagrams that expresses the same syntax but tries to break the syntax down into smaller chunks.
**[factored-select-stmt:](syntax/factored-select-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[select-core:](syntax/select-core.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
Note that there are paths through the syntax diagrams that are not allowed in practice. Some examples:
- A [VALUES](lang_select.md#values) clause can be the first element in a [compound SELECT](lang_select.md#compound) that uses a [WITH](lang_with.md) clause, but a [simple SELECT](lang_select.md#simpleselect) that consists of just a [VALUES](lang_select.md#values) clause cannot be preceded by a [WITH](lang_with.md) clause.
- The [WITH](lang_with.md) clause must occur on the first SELECT of a [compound SELECT](lang_select.md#compound). It cannot follow a [compound-operator](syntax/compound-operator.md).
These and other similar syntax restrictions are described in the text.
The SELECT statement is the most complicated command in the SQL language. To make the description easier to follow, some of the passages below describe the way the data returned by a SELECT statement is determined as a series of steps. It is important to keep in mind that this is purely illustrative - in practice neither SQLite nor any other SQL engine is required to follow this or any other specific process.
# 2. Simple Select Processing
The core of a SELECT statement is a "simple SELECT" shown by the [select-core](syntax/select-core.md) and [simple-select-stmt](syntax/simple-select-stmt.md) syntax diagrams below. In practice, most SELECT statements are simple SELECT statements.
**[simple-select-stmt:](syntax/simple-select-stmt.md)** hide
**[common-table-expression:](syntax/common-table-expression.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[select-core:](syntax/select-core.md)** hide
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
Generating the results of a simple SELECT statement is presented as a four step process in the description below:
1. [FROM clause](lang_select.md#fromclause) processing: The input data for the simple SELECT is determined. The input data is either implicitly a single row with 0 columns (if there is no FROM clause) or is determined by the FROM clause.
2. [WHERE clause](lang_select.md#whereclause) processing: The input data is filtered using the WHERE clause expression.
3. [GROUP BY, HAVING and result-column expression](lang_select.md#resultset) processing: The set of result rows is computed by aggregating the data according to any GROUP BY clause and calculating the result-set expressions for the rows of the filtered input dataset.
4. [DISTINCT/ALL keyword](lang_select.md#distinct) processing: If the query is a "SELECT DISTINCT" query, duplicate rows are removed from the set of result rows.
There are two types of simple SELECT statement - aggregate and non-aggregate queries. A simple SELECT statement is an aggregate query if it contains either a GROUP BY clause or one or more aggregate functions in the result-set. Otherwise, if a simple SELECT contains no aggregate functions or a GROUP BY clause, it is a non-aggregate query.
## 2.1. Determination of input data (FROM clause processing)
The input data used by a simple SELECT query is a set of *N* rows each *M* columns wide.
If the FROM clause is omitted from a simple SELECT statement, then the input data is implicitly a single row zero columns wide (i.e. *N*=1 and *M*=0).
If a FROM clause is specified, the data on which a simple SELECT query operates comes from the one or more tables or subqueries (SELECT statements in parentheses) specified following the FROM keyword. A subquery specified in the table-or-subquery following the FROM clause in a simple SELECT statement is handled as if it was a table containing the data returned by executing the subquery statement. Each column of the subquery has the [collation sequence](datatype3.md#collation) and [affinity](datatype3.md#affinity) of the corresponding expression in the subquery statement.
If there is only a single table or subquery in the FROM clause, then the input data used by the SELECT statement is the contents of the named table. If there is more than one table or subquery in the FROM clause then the contents of all tables and/or subqueries are joined into a single dataset for the simple SELECT statement to operate on. Exactly how the data is combined depends on the specific [join-operator](syntax/join-operator.md) and [join-constraint](syntax/join-constraint.md) used to connect the tables or subqueries together.
All joins in SQLite are based on the cartesian product of the left and right-hand datasets. The columns of the cartesian product dataset are, in order, all the columns of the left-hand dataset followed by all the columns of the right-hand dataset. There is a row in the cartesian product dataset formed by combining each unique combination of a row from the left-hand and right-hand datasets. In other words, if the left-hand dataset consists of *Nleft* rows of *Mleft* columns, and the right-hand dataset of *Nright* rows of *Mright* columns, then the cartesian product is a dataset of *Nleft×Nright* rows, each containing *Mleft+Mright* columns.
If the join-operator is "CROSS JOIN", "INNER JOIN", "JOIN" or a comma (",") and there is no ON or USING clause, then the result of the join is simply the cartesian product of the left and right-hand datasets. If join-operator does have ON or USING clauses, those are handled according to the following bullet points:
- If there is an ON clause then the ON expression is evaluated for each row of the cartesian product as a [boolean expression](lang_expr.md#booleanexpr). Only rows for which the expression evaluates to true are included from the dataset.
- If there is a USING clause then each of the column names specified must exist in the datasets to both the left and right of the join-operator. For each pair of named columns, the expression "lhs.X = rhs.X" is evaluated for each row of the cartesian product as a [boolean expression](lang_expr.md#booleanexpr). Only rows for which all such expressions evaluate to true are included from the result set. When comparing values as a result of a USING clause, the normal rules for handling affinities, collation sequences and NULL values in comparisons apply. The column from the dataset on the left-hand side of the join-operator is considered to be on the left-hand side of the comparison operator (=) for the purposes of collation sequence and affinity precedence.
For each pair of columns identified by a USING clause, the column from the right-hand dataset is omitted from the joined dataset. This is the only difference between a USING clause and its equivalent ON constraint.
- If the NATURAL keyword is in the join-operator then an implicit USING clause is added to the join-constraints. The implicit USING clause contains each of the column names that appear in both the left and right-hand input datasets. If the left and right-hand input datasets feature no common column names, then the NATURAL keyword has no effect on the results of the join. A USING or ON clause may not be added to a join that specifies the NATURAL keyword.
- If the join-operator is a "LEFT JOIN" or "LEFT OUTER JOIN", then after the ON or USING filtering clauses have been applied, an extra row is added to the output for each row in the original left-hand input dataset that does not match any row in the right-hand dataset. The added rows contain NULL values in the columns that would normally contain values copied from the right-hand input dataset.
- If the join-operator is a "RIGHT JOIN" or "RIGHT OUTER JOIN", then after the ON or USING filtering clauses have been applied, an extra row is added to the output for each row in the original right-hand input dataset that does not match any row in the left-hand dataset. The added rows contain NULL values in the columns that would normally contain values copied from the left-hand input dataset.
- A "FULL JOIN" or "FULL OUTER JOIN" is a combination of a "LEFT JOIN" and a "RIGHT JOIN". Extra rows of output are added for each row in left dataset that matches no rows in the right, and for each row in the right dataset that matches no rows in the left. Unmatched columns are filled in with NULL.
When more than two tables are joined together as part of a FROM clause, the join operations are processed in order from left to right. In other words, the FROM clause (A join-op-1 B join-op-2 C) is computed as ((A join-op-1 B) join-op-2 C).
## 2.2. Special handling of CROSS JOIN.
There is no difference between the "INNER JOIN", "JOIN" and "," join operators. They are completely interchangeable in SQLite. The "CROSS JOIN" join operator produces the same result as the "INNER JOIN", "JOIN" and "," operators, but is [handled differently by the query optimizer](optoverview.md#crossjoin) in that it prevents the query optimizer from reordering the tables in the join. An application programmer can use the CROSS JOIN operator to directly influence the algorithm that is chosen to implement the SELECT statement. Avoid using CROSS JOIN except in specific situations where manual control of the query optimizer is desired. Avoid using CROSS JOIN early in the development of an application as doing so is a [premature optimization](http://c2.com/cgi/wiki?PrematureOptimization). The special handling of CROSS JOIN is an SQLite-specific feature and is not a part of standard SQL.
## 2.3. WHERE clause filtering.
If a WHERE clause is specified, the WHERE expression is evaluated for each row in the input data as a [boolean expression](lang_expr.md#booleanexpr). Only rows for which the WHERE clause expression evaluates to true are included from the dataset before continuing. Rows are excluded from the result if the WHERE clause evaluates to either false or NULL.
For a JOIN or INNER JOIN or CROSS JOIN, there is no difference between a constraint expression in the WHERE clause and one in the ON clause. However, for a LEFT or RIGHT or FULL OUTER JOIN, the difference is very important. In an outer join, the extra NULL rows for non-matched rows on the other operand are added after ON clause processing but before WHERE clause processing. A constraint of the form "left.x=right.y" in an ON clause will therefore allow through for the added all-NULL rows. But if that same constraint is in the WHERE clause, a NULL in one of "right.y" or "left.x" will prevent the expression "left.x=right.y" from being true, and thus exclude that row from the output.
## 2.4. Generation of the set of result rows
Once the input data from the FROM clause has been filtered by the WHERE clause expression (if any), the set of result rows for the simple SELECT are calculated. Exactly how this is done depends on whether the simple SELECT is an aggregate or non-aggregate query, and whether or not a GROUP BY clause was specified.
The list of expressions between the SELECT and FROM keywords is known as the result expression list. If a result expression is the special expression "\*" then all columns in the input data are substituted for that one expression. If the expression is the alias of a table or subquery in the FROM clause followed by ".\*" then all columns from the named table or subquery are substituted for the single expression. It is an error to use a "\*" or "alias.\*" expression in any context other than a result expression list. It is also an error to use a "\*" or "alias.\*" expression in a simple SELECT query that does not have a FROM clause.
The number of columns in the rows returned by a simple SELECT statement is equal to the number of expressions in the result expression list after substitution of \* and alias.\* expressions. Each result row is calculated by evaluating the expressions in the result expression list with respect to a single row of input data or, for aggregate queries, with respect to a group of rows.
- If the SELECT statement is **a non-aggregate query**, then each expression in the result expression list is evaluated for each row in the dataset filtered by the WHERE clause.
- If the SELECT statement is **an aggregate query without a GROUP BY** clause, then each aggregate expression in the result-set is evaluated once across the entire dataset. Each non-aggregate expression in the result-set is evaluated once for an arbitrarily selected row of the dataset. The same arbitrarily selected row is used for each non-aggregate expression. Or, if the dataset contains zero rows, then each non-aggregate expression is evaluated against a row consisting entirely of NULL values.
The single row of result-set data created by evaluating the aggregate and non-aggregate expressions in the result-set forms the result of an aggregate query without a GROUP BY clause. An aggregate query without a GROUP BY clause always returns exactly one row of data, even if there are zero rows of input data.
- If the SELECT statement is **an aggregate query with a GROUP BY** clause, then each of the expressions specified as part of the GROUP BY clause is evaluated for each row of the dataset according to the processing rules stated below for ORDER BY expressions. Each row is then assigned to a "group" based on the results; rows for which the results of evaluating the GROUP BY expressions are the same get assigned to the same group. For the purposes of grouping rows, NULL values are considered equal. The usual rules for [selecting a collation sequence](datatype3.md#collation) with which to compare text values apply when evaluating expressions in a GROUP BY clause. The expressions in the GROUP BY clause do *not* have to be expressions that appear in the result. The expressions in a GROUP BY clause may not be aggregate expressions.
If a HAVING clause is specified, it is evaluated once for each group of rows as a [boolean expression](lang_expr.md#booleanexpr). If the result of evaluating the HAVING clause is false, the group is discarded. If the HAVING clause is an aggregate expression, it is evaluated across all rows in the group. If a HAVING clause is a non-aggregate expression, it is evaluated with respect to an arbitrarily selected row from the group. The HAVING expression may refer to values, even aggregate functions, that are not in the result.
Each expression in the result-set is then evaluated once for each group of rows. If the expression is an aggregate expression, it is evaluated across all rows in the group. Otherwise, it is evaluated against a single arbitrarily chosen row from within the group. If there is more than one non-aggregate expression in the result-set, then all such expressions are evaluated for the same row.
Each group of input dataset rows contributes a single row to the set of result rows. Subject to filtering associated with the DISTINCT keyword, the number of rows returned by an aggregate query with a GROUP BY clause is the same as the number of groups of rows produced by applying the GROUP BY and HAVING clauses to the filtered input dataset.
## 2.5. Bare columns in an aggregate query
The usual case is that all column names in an aggregate query are either arguments to [aggregate functions](lang_aggfunc.md) or else appear in the GROUP BY clause. A result column which contains a column name that is not within an aggregate function and that does not appear in the GROUP BY clause (if one exists) is called a "bare" column. Example:
> \
> SELECT a, b, sum(c) FROM tab1 GROUP BY a;\
In the query above, the "a" column is part of the GROUP BY clause and so each row of the output contains one of the distinct values for "a". The "c" column is contained within the [sum()](lang_aggfunc.md#sumunc) aggregate function and so that output column is the sum of all "c" values in rows that have the same value for "a". But what is the result of the bare column "b"? The answer is that the "b" result will be the value for "b" in one of the input rows that form the aggregate.¹ The problem is that you usually do not know which input row is used to compute "b", and so in many cases the value for "b" is undefined.
Special processing occurs when the aggregate function is either [min()](lang_aggfunc.md#min_agg) or [max()](lang_aggfunc.md#max_agg). Example:
> \
> SELECT a, b, max(c) FROM tab1 GROUP BY a;\
If there is exactly one [min()](lang_aggfunc.md#max_agg) or [max()](lang_aggfunc.md#min_agg) aggregate in the query, then all bare columns in the result set take values from an input row which also contains the minimum or maximum. So in the query above, the value of the "b" column in the output will be the value of the "b" column in the input row that has the largest "c" value. There are limitations on this special behavior of [min()](lang_aggfunc.md#max_agg) and [max()](lang_aggfunc.md#min_agg):
1. If the same minimum or maximum value occurs on two or more rows, then bare values might be selected from any of those rows. The choice is arbitrary. There is no way to predict from which row the bare values will be choosen. The choice might be different for different bare columns within the same query.
2. If there are two or more [min()](lang_aggfunc.md#min_agg) or [max()](lang_aggfunc.md#max_agg) aggregates in the query, then bare column values will be taken from one of the rows on which one of the aggregates has their minimum or maximum value. The choice of which [min()](lang_aggfunc.md#min_agg) or [max()](lang_aggfunc.md#max_agg) aggregate determines the selection of bare column values is arbitrary. The choice might be different for different bare columns within the same query.
3. This special processing for [min()](lang_aggfunc.md#min_agg) or [max()](lang_aggfunc.md#max_agg) aggregates only works for the built-in implementation of those aggregates. If an application overrides the built-in [min()](lang_aggfunc.md#min_agg) or [max()](lang_aggfunc.md#max_agg) aggregates with application-defined alternatives, then the values selected for bare columns will be taken from an arbitrary row.
Most other SQL database engines disallow bare columns. If you include a bare column in a query, other database engines will usually raise an error. The ability to include bare columns in a query is an SQLite-specific extension. This is considered a feature, not a bug. See the discussion on [SQLite Forum thread 7481d2a6df8980ff](https://sqlite.org/forum/forumpost/7481d2a6df8980ff) for additional information.
### 2.5.1. Notes
1. If the aggregate is composed from one or more input rows, then a bare column will take on the value of an arbitrary row from the aggregate's input. The particular row chosen might change from one invocation to the the next. If the aggregate is empty (if the aggregate has no input rows, as happens if no rows match the WHERE clause), then the bare column can take on any arbitrary value, including values that are not found anywhere in the tables of the FROM clause.
## 2.6. Removal of duplicate rows (DISTINCT processing)
One of the ALL or DISTINCT keywords may follow the SELECT keyword in a simple SELECT statement. If the simple SELECT is a SELECT ALL, then the entire set of result rows are returned by the SELECT. If neither ALL or DISTINCT are present, then the behavior is as if ALL were specified. If the simple SELECT is a SELECT DISTINCT, then duplicate rows are removed from the set of result rows before it is returned. For the purposes of detecting duplicate rows, values are compared using the [IS DISTINCT FROM](lang_expr.md#isdf) operator. Thus two NULL values are considered to be equal. An integer is equal to a floating point number if they represent the same quantity. Text values are compared using an appropriate collation sequence. The [usual rules](datatype3.md#colrules) apply for selecting a collation sequence to compare text values. [BLOB affinity](datatype3.md#affinity) is used for DISTINCT comparisons, hence no type coercions occur.
# 3. Compound Select Statements
Two or more [simple SELECT](lang_select.md#simpleselect) statements may be connected together to form a compound SELECT using the UNION, UNION ALL, INTERSECT or EXCEPT operator, as shown by the following diagram:
**[compound-select-stmt:](syntax/compound-select-stmt.md)** hide
**[common-table-expression:](syntax/common-table-expression.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[select-core:](syntax/select-core.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
In a compound SELECT, all the constituent SELECTs must return the same number of result columns. As the components of a compound SELECT must be simple SELECT statements, they may not contain [ORDER BY](lang_select.md#orderby) or [LIMIT](lang_select.md#limitoffset) clauses. [ORDER BY](lang_select.md#orderby) and [LIMIT](lang_select.md#limitoffset) clauses may only occur at the end of the entire compound SELECT, and then only if the final element of the compound is not a [VALUES](lang_select.md#values) clause.
A compound SELECT created using the UNION ALL operator returns all the rows from the SELECT to the left of the UNION ALL operator, and all the rows from the SELECT to the right of it. The UNION operator works the same way as UNION ALL, except that duplicate rows are removed from the final result set. The INTERSECT operator returns the intersection of the results of the left and right SELECTs. The EXCEPT operator returns the subset of rows returned by the left SELECT that are not also returned by the right-hand SELECT. Duplicate rows are removed from the results of INTERSECT and EXCEPT operators before the result set is returned.
For the purposes of determining duplicate rows for the results of compound SELECT operators, NULL values are considered equal to other NULL values and distinct from all non-NULL values. The collation sequence used to compare two text values is determined as if the columns of the left and right-hand SELECT statements were the left and right-hand operands of the equals (=) operator, except that greater precedence is not assigned to a collation sequence specified with the postfix COLLATE operator. No affinity transformations are applied to any values when comparing rows as part of a compound SELECT.
When three or more simple SELECTs are connected into a compound SELECT, they group from left to right. In other words, if "A", "B" and "C" are all simple SELECT statements, (A op B op C) is processed as ((A op B) op C).
# 4. The ORDER BY clause
If a SELECT statement that returns more than one row does not have an ORDER BY clause, the order in which the rows are returned is undefined. Or, if a SELECT statement does have an ORDER BY clause, then the list of expressions attached to the ORDER BY determine the order in which rows are returned to the user.
In a [compound SELECT](lang_select.md#compound) statement, only the last or right-most [simple SELECT](lang_select.md#simpleselect) may have an ORDER BY clause. That ORDER BY clause will apply across all elements of the compound. If the right-most element of a [compound SELECT](lang_select.md#compound) is a [VALUES](lang_select.md#values) clause, then no ORDER BY clause is allowed on that statement.
Rows are first sorted based on the results of evaluating the left-most expression in the ORDER BY list, then ties are broken by evaluating the second left-most expression and so on. The order in which two rows for which all ORDER BY expressions evaluate to equal values are returned is undefined. Each ORDER BY expression may be optionally followed by one of the keywords ASC (smaller values are returned first) or DESC (larger values are returned first). If neither ASC or DESC are specified, rows are sorted in ascending (smaller values first) order by default.
SQLite considers NULL values to be smaller than any other values for sorting purposes. Hence, NULLs naturally appear at the beginning of an ASC order-by and at the end of a DESC order-by. This can be changed using the "ASC NULLS LAST" or "DESC NULLS FIRST" syntax.
Each ORDER BY expression is processed as follows:
1. If the ORDER BY expression is a constant integer K then the expression is considered an alias for the K-th column of the result set (columns are numbered from left to right starting with 1).
2. If the ORDER BY expression is an identifier that corresponds to the alias of one of the output columns, then the expression is considered an alias for that column.
3. Otherwise, if the ORDER BY expression is any other expression, it is evaluated and the returned value used to order the output rows. If the SELECT statement is a simple SELECT, then an ORDER BY may contain any arbitrary expressions. However, if the SELECT is a compound SELECT, then ORDER BY expressions that are not aliases to output columns must be exactly the same as an expression used as an output column.
For the purposes of sorting rows, values are compared in the same way as for [comparison expressions](datatype3.md#comparisons). The collation sequence used to compare two text values is determined as follows:
1. If the ORDER BY expression is assigned a collation sequence using the postfix [COLLATE operator](lang_expr.md#collateop), then the specified collation sequence is used.
2. Otherwise, if the ORDER BY expression is an alias to an expression that has been assigned a collation sequence using the postfix [COLLATE operator](lang_expr.md#collateop), then the collation sequence assigned to the aliased expression is used.
3. Otherwise, if the ORDER BY expression is a column or an alias of an expression that is a column, then the default collation sequence for the column is used.
4. Otherwise, the [BINARY](datatype3.md#collation) collation sequence is used.
In a [compound SELECT](lang_select.md#compound) statement, all ORDER BY expressions are handled as aliases for one of the result columns of the compound. If an ORDER BY expression is not an integer alias, then SQLite searches the left-most SELECT in the compound for a result column that matches either the second or third rules above. If a match is found, the search stops and the expression is handled as an alias for the result column that it has been matched against. Otherwise, the next SELECT to the right is tried, and so on. If no matching expression can be found in the result columns of any constituent SELECT, it is an error. Each term of the ORDER BY clause is processed separately and may be matched against result columns from different SELECT statements in the compound.
# 5. The LIMIT clause
The LIMIT clause is used to place an upper bound on the number of rows returned by the entire SELECT statement.
In a [compound SELECT](lang_select.md#compound), only the last or right-most [simple SELECT](lang_select.md#simpleselect) may contain a LIMIT clause. In a [compound SELECT](lang_select.md#compound), the LIMIT clause applies to the entire compound, not just the final SELECT. If the right-most [simple SELECT](lang_select.md#simpleselect) is a [VALUES clause](lang_select.md#values) then no LIMIT clause is allowed.
Any scalar expression may be used in the LIMIT clause, so long as it evaluates to an integer or a value that can be losslessly converted to an integer. If the expression evaluates to a NULL value or any other value that cannot be losslessly converted to an integer, an error is returned. If the LIMIT expression evaluates to a negative value, then there is no upper bound on the number of rows returned. Otherwise, the SELECT returns the first N rows of its result set only, where N is the value that the LIMIT expression evaluates to. Or, if the SELECT statement would return less than N rows without a LIMIT clause, then the entire result set is returned.
The expression attached to the optional OFFSET clause that may follow a LIMIT clause must also evaluate to an integer, or a value that can be losslessly converted to an integer. If an expression has an OFFSET clause, then the first M rows are omitted from the result set returned by the SELECT statement and the next N rows are returned, where M and N are the values that the OFFSET and LIMIT clauses evaluate to, respectively. Or, if the SELECT would return less than M+N rows if it did not have a LIMIT clause, then the first M rows are skipped and the remaining rows (if any) are returned. If the OFFSET clause evaluates to a negative value, the results are the same as if it had evaluated to zero.
Instead of a separate OFFSET clause, the LIMIT clause may specify two scalar expressions separated by a comma. In this case, the first expression is used as the OFFSET expression and the second as the LIMIT expression. This is counter-intuitive, as when using the OFFSET clause the second of the two expressions is the OFFSET and the first the LIMIT. This reversal of the offset and limit is intentional - it maximizes compatibility with other SQL database systems. However, to avoid confusion, programmers are strongly encouraged to use the form of the LIMIT clause that uses the "OFFSET" keyword and avoid using a LIMIT clause with a comma-separated offset.
# 6. The VALUES clause
The phrase "VALUES(*expr-list*)" means the same thing as "SELECT *expr-list*". The phrase "VALUES(*expr-list-1*),...,(*expr-list-N*)" means the same thing as "SELECT *expr-list-1* UNION ALL ... UNION ALL SELECT *expr-list-N*". Both forms are the same, except that the number of SELECT statements in a compound is limited by [SQLITE_LIMIT_COMPOUND_SELECT](c3ref/c_limit_attached.md#sqlitelimitcompoundselect) whereas the number of rows in a VALUES clause has no arbitrary limit.
There are some restrictions on the use of a VALUES clause that are not shown on the syntax diagrams:
- A VALUES clause cannot be followed by [ORDER BY](lang_select.md#orderby).
- A VALUES clause cannot be followed by [LIMIT](lang_select.md#limitoffset).
# 7. The WITH Clause
SELECT statements may be optionally preceded by a single [WITH clause](lang_with.md) that defines one or more [common table expressions](lang_with.md) for use within the SELECT statement.
# 8. Table-valued Functions In The FROM Clause
A [virtual table](vtab.md) that contains [hidden columns](vtab.md#hiddencol) can be used like a [table-valued function](vtab.md#tabfunc2) in the FROM clause. The arguments to the table-valued function become constraints on the HIDDEN columns of the virtual table. Additional information can be found in the [virtual table documentation](vtab.md#tabfunc2).
# 9. Deviations From Standard SQL
The SELECT syntax of SQLite differs slightly from standard SQL. These differences are due to several reasons:
- In the mid-2000s, there was a lot of emphasis on keeping the library footprint as small as possible, so as not to use too much space on memory-limited flip-phones and similar.
- During the early years of SQLite, the lead developer sought to follow [Postel's Law](https://en.wikipedia.org/wiki/Robustness_principle) and to be forgiving and flexible in what input was accepted.
- There were bugs in early SQLite parsers that accepts some strange inputs.
- The lead developer's knowledge of SQL was imperfect.
Whatever the origin of the input quirks, we generally avoid trying to "fix" them, as any new restrictions on the input syntax would likely cause at least some of the millions of applications that use SQLite to break. We do not want that. The goal of the SQLite development team is to preserve backwards compability to the fullest extent possible. Hence, if a syntax quirk is harmless, we leave it alone and document it here, rather than try to fix it.
## 9.1. Strange JOIN names
SQLite accepts all of the usual syntax for JOIN operators:
**[join-operator:](syntax/join-operator.md)** hide
But it does not stop there. SQLite is actually very flexible in how you specify a join operator. The general syntax is:
> *blah blah blah* **JOIN**
Where there are between 1 and 3 instances of "*blah*", each of which can be any of "CROSS", "FULL", "INNER", "LEFT", "NATURAL", "OUTER", or "RIGHT". The SQLite parser treats each of these keywords as an attribute of the join, which can be combined in any order. This creates the possibility of many new and creative join types beyond what is specified by the syntax diagram. Some of these non-standard join types are specifically disallowed. For example, you cannot say "INNER OUTER JOIN", because that would be contradictory. But you can say things like "OUTER LEFT NATURAL JOIN" which means the same as "NATURAL LEFT OUTER JOIN". Or you can say "LEFT RIGHT JOIN" which is the same as "FULL JOIN".
Remember: you *can* use these non-standard join types but you *ought not*. Stick to using standard JOIN syntax for portability with other SQL database engines.
## 9.2. Flexible join syntax
Standard SQL has tighter restrictions on join syntax than does SQLite. In standard SQL, all joins other than comma-joins, CROSS JOINs, and NATURAL joins must have either an ON clause or a USING clause and comma-joins, CROSS JOINs, and NATURAL joins must not have either an ON or USING clause. SQLite is not nearly so fussy about join syntax. SQLite will accept and process an ON or USING clause on a comma-join or CROSS JOIN, and will let you omit the ON or USING clause from any join at all. In SQLite, the only restrictions are:
- You cannot have an ON or USING clause on a NATURAL join.
- You cannot have both an ON clause and a USING clause on the same join.
SQLite even allows you to omit the ON or USING clause from an outer join, though doing so means that the outer join is unconstrained (as if the ON clause where "`ON true`") which make the outer join behave like an inner join.
## 9.3. Precedence of comma-joins and CROSS JOIN
In standard SQL, joins that use the JOIN keyword take higher precedence than comma-joins. That is to say, JOIN operators happen before comma operators. This is not the case in SQLite, where all joins have the same precedence.
Consider this example:
> \
> ... FROM t1, t2 NATURAL FULL JOIN t3 ...\
In standard SQL, the FULL JOIN between t2 and t3 would occur first, and then the result of the left join would be cross-joined against t1. But SQLite always handles all joins from left to right. Thus, SQLite will do a cross join on t1 and t2 first, then the result of that cross join will feed into the FULL JOIN with t3. Inner joins are inherently associative, so the difference is only evident if your FROM clause contains one or more outer joins.
You can work around this, and make your SQL statements portable across all systems, by observing the following stylistic rules:
- Do not mix comma-joins with the JOIN keyword. It is fine to use comma-joins, but if you do, the you should use only comma-joins for the entire FROM clause.
- Prefer LEFT JOIN over other outer join operators.
- When in doubt, use parentheses to specify the exact join order that you intend.
Any one of these suggestions is sufficient to avoid problems, and most programmers instinctively follow all of these suggestions without having to be told, and so the lack of precedence difference between comma-joins and the JOIN keyword in SQLite rarely comes up in practice. But you should be aware of the problem, in case it ever does appear.
---
# SQL Comment Syntax
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_comment.html*
**[comment-syntax:](syntax/comment-syntax.md)** hide
Comments are not SQL commands, but can occur within the text of SQL queries passed to [sqlite3_prepare_v2()](c3ref/prepare.md) and related interfaces. Comments are treated as whitespace by the parser. Comments can begin anywhere whitespace can be found, including inside expressions that span multiple lines.
SQL comments begin with two consecutive "-" characters (ASCII 0x2d) and extend up to and including the next newline character (ASCII 0x0a) or until the end of input, whichever comes first.
C-style comments begin with "/\*" and extend up to and including the next "\*/" character pair or until the end of input, whichever comes first. C-style comments can span multiple lines.
Comments can appear anywhere whitespace can occur, including inside expressions and in the middle of other SQL statements. Comments do not nest.
---
# SQL Language Expressions
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_expr.html*
# 1. Syntax
**[expr:](syntax/expr.md)** hide
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
# 2. Operators, and Parse-Affecting Attributes
SQLite understands these operators, listed in precedence1 order\
(top to bottom / highest to lowest):
| Operators 2 |
|---|
| ~ [expr] + [expr] - [expr] |
| [expr] COLLATE (collation-name) 3 |
| || -> ->> |
| * / % |
| + - |
| & | << >> |
| [expr] ESCAPE [escape-character-expr] 4 |
| < > <= >= |
| = == <> != IS IS NOT IS DISTINCT FROM IS NOT DISTINCT FROM [expr] BETWEEN5 [expr] AND [expr] IN5 MATCH5 LIKE5 REGEXP5 GLOB5 [expr] ISNULL [expr] NOTNULL [expr] NOT NULL |
| NOT [expr] |
| AND |
| OR |
If a numeric literal has a decimal point or an exponentiation clause or if it is less than -9223372036854775808 or greater than 9223372036854775807, then it is a floating point literal. Otherwise it is an integer literal. The "E" character that begins the exponentiation clause of a floating point literal can be either upper or lower case. The "." character is always used as the decimal point even if the locale setting specifies "," for this role - the use of "," for the decimal point would result in syntactic ambiguity.
Beginning in SQLite version 3.46.0 (2024-05-23), a single extra underscore ("\_") character can be added between any two digits. The underscores are purely for human readability and are ignored by SQLite.
Hexadecimal integer literals follow the C-language notation of "0x" or "0X" followed by hexadecimal digits. For example, 0x1234 means the same as 4660 and 0x8000000000000000 means the same as -9223372036854775808. Hexadecimal integer literals are interpreted as 64-bit two's-complement integers and are thus limited to sixteen significant digits of precision. Support for hexadecimal integers was added to SQLite version 3.8.6 (2014-08-15). For backwards compatibility, the "0x" hexadecimal integer notation is only understood by the SQL language parser, not by the type conversions routines. String variables that contain text formatted like hexadecimal integers are not interpreted as hexadecimal integers when coercing the string value into an integer due to a [CAST expression](lang_expr.md#castexpr) or for a [column affinity](datatype3.md#affinity) transformation or prior to performing a numeric operation or for any other run-time conversions. When coercing a string value in the format of a hexadecimal integer into an integer value, the conversion process stops when the 'x' character is seen so the resulting integer value is always zero. SQLite only understands the hexadecimal integer notation when it appears in the SQL statement text, not when it appears as part of the content of the database.
A string constant is formed by enclosing the string in single quotes ('). A single quote within the string can be encoded by putting two single quotes in a row - as in Pascal. C-style escapes using the backslash character are not supported because they are not standard SQL.
BLOB literals are string literals containing hexadecimal data and preceded by a single "x" or "X" character. Example: X'53514C697465'
A literal value can also be the token "NULL".
# 4. Parameters
A "variable" or "parameter" token specifies a placeholder in the expression for a value that is filled in at runtime using the [sqlite3_bind()](c3ref/bind_blob.md) family of C/C++ interfaces. Parameters can take several forms:
> | | | |
> |---:|----|----|
> | **?***NNN* | | A question mark followed by a number *NNN* holds a spot for the NNN-th parameter. NNN must be between 1 and [SQLITE_MAX_VARIABLE_NUMBER](limits.md#max_variable_number). |
> | **?** | | A question mark that is not followed by a number creates a parameter with a number one greater than the largest parameter number already assigned. If this means the parameter number is greater than [SQLITE_MAX_VARIABLE_NUMBER](limits.md#max_variable_number), it is an error. This parameter format is provided for compatibility with other database engines. But because it is easy to miscount the question marks, the use of this parameter format is discouraged. Programmers are encouraged to use one of the symbolic formats below or the ?NNN format above instead. |
> | **:***AAAA* | | A colon followed by an identifier name holds a spot for a [named parameter](c3ref/bind_parameter_name.md) with the name :AAAA. Named parameters are also numbered. The number assigned is one greater than the largest parameter number already assigned. If this means the parameter would be assigned a number greater than [SQLITE_MAX_VARIABLE_NUMBER](limits.md#max_variable_number), it is an error. To avoid confusion, it is best to avoid mixing named and numbered parameters. |
> | **@***AAAA* | | An "at" sign works exactly like a colon, except that the name of the parameter created is @AAAA. |
> | **\$***AAAA* | | A dollar-sign followed by an identifier name also holds a spot for a named parameter with the name \$AAAA. The identifier name in this case can include one or more occurrences of "::" and a suffix enclosed in "(...)" containing any text without whitespace. This syntax is the form of a variable name in the [Tcl programming language](http://www.tcl-lang.org/). The presence of this syntax results from the fact that SQLite is really a [Tcl extension](tclsqlite.md) that has escaped into the wild. |
Parameters that are not assigned values using [sqlite3_bind()](c3ref/bind_blob.md) are treated as NULL. The [sqlite3_bind_parameter_index()](c3ref/bind_parameter_index.md) interface can be used to translate a symbolic parameter name into its equivalent numeric index.
The maximum parameter number is set at compile-time by the [SQLITE_MAX_VARIABLE_NUMBER](limits.md#max_variable_number) macro. An individual [database connection](c3ref/sqlite3.md) D can reduce its maximum parameter number below the compile-time maximum using the [sqlite3_limit](c3ref/limit.md)(D, [SQLITE_LIMIT_VARIABLE_NUMBER](c3ref/c_limit_attached.md#sqlitelimitvariablenumber),...) interface.
# 5. The LIKE, GLOB, REGEXP, MATCH, and extract operators
The LIKE operator does a pattern matching comparison. The operand to the right of the LIKE operator contains the pattern and the left hand operand contains the string to match against the pattern. A percent symbol ("%") in the LIKE pattern matches any sequence of zero or more characters in the string. An underscore ("\_") in the LIKE pattern matches any single character in the string. Any other character matches itself or its lower/upper case equivalent (i.e. case-insensitive matching). Important Note: SQLite only understands upper/lower case for ASCII characters by default. The LIKE operator is case sensitive by default for unicode characters that are beyond the ASCII range. For example, the expression **'a' LIKE 'A'** is TRUE but **'æ' LIKE 'Æ'** is FALSE. The ICU extension to SQLite includes an enhanced version of the LIKE operator that does case folding across all unicode characters.
If the optional ESCAPE clause is present, then the expression following the ESCAPE keyword must evaluate to a string consisting of a single character. This character may be used in the LIKE pattern to include literal percent or underscore characters. The escape character followed by a percent symbol (%), underscore (\_), or a second instance of the escape character itself matches a literal percent symbol, underscore, or a single escape character, respectively.
The infix LIKE operator is implemented by calling the application-defined SQL functions [like(*Y*,*X*)](lang_corefunc.md#like) or [like(*Y*,*X*,*Z*)](lang_corefunc.md#like).
The LIKE operator can be made case sensitive using the [case_sensitive_like pragma](pragma.md#pragma_case_sensitive_like).
The GLOB operator is similar to LIKE but uses the Unix file globbing syntax for its wildcards. Also, GLOB is case sensitive, unlike LIKE. Both GLOB and LIKE may be preceded by the NOT keyword to invert the sense of the test. The infix GLOB operator is implemented by calling the function [glob(*Y*,*X*)](lang_corefunc.md#glob) and can be modified by overriding that function.
The REGEXP operator is a special syntax for the regexp() user function. No regexp() user function is defined by default and so use of the REGEXP operator will normally result in an error message. If an [application-defined SQL function](appfunc.md) named "regexp" is added at run-time, then the "*X* REGEXP *Y*" operator will be implemented as a call to "regexp(*Y*,*X*)".
The MATCH operator is a special syntax for the match() application-defined function. The default match() function implementation raises an exception and is not really useful for anything. But extensions can override the match() function with more helpful logic.
The extract operators act as a special syntax for functions "-\>"() and "-\>\>"(). Default implementations for these functions perform [JSON subcomponent extraction](json1.md#jptr), but extensions can override them for other purposes.
# 6. The BETWEEN operator
The BETWEEN operator is logically equivalent to a pair of comparisons. "*x* **BETWEEN** *y* **AND** *z*" is equivalent to "*x***\>=***y* **AND** *x***\<=***z*" except that with BETWEEN, the *x* expression is only evaluated once.
# 7. The CASE expression
A CASE expression serves a role similar to IF-THEN-ELSE in other programming languages.
The optional expression that occurs in between the CASE keyword and the first WHEN keyword is called the "base" expression. There are two fundamental forms of the CASE expression: those with a base expression and those without.
In a CASE without a base expression, each WHEN expression is evaluated and the result treated as a boolean, starting with the leftmost and continuing to the right. The result of the CASE expression is the evaluation of the THEN expression that corresponds to the first WHEN expression that evaluates to true. Or, if none of the WHEN expressions evaluate to true, the result of evaluating the ELSE expression, if any. If there is no ELSE expression and none of the WHEN expressions are true, then the overall result is NULL.
A NULL result is considered untrue when evaluating WHEN terms.
In a CASE with a base expression, the base expression is evaluated just once and the result is compared against the evaluation of each WHEN expression from left to right. The result of the CASE expression is the evaluation of the THEN expression that corresponds to the first WHEN expression for which the comparison is true. Or, if none of the WHEN expressions evaluate to a value equal to the base expression, the result of evaluating the ELSE expression, if any. If there is no ELSE expression and none of the WHEN expressions produce a result equal to the base expression, the overall result is NULL.
When comparing a base expression against a WHEN expression, the same collating sequence, affinity, and NULL-handling rules apply as if the base expression and WHEN expression are respectively the left- and right-hand operands of an **=** operator.
If the base expression is NULL then the result of the CASE is always the result of evaluating the ELSE expression if it exists, or NULL if it does not.
Both forms of the CASE expression use lazy, or short-circuit, evaluation.
The only difference between the following two CASE expressions is that the *x* expression is evaluated exactly once in the first example but might be evaluated multiple times in the second:
- \
CASE x WHEN w1 THEN r1 WHEN w2 THEN r2 ELSE r3 END\
CASE WHEN x=w1 THEN r1 WHEN x=w2 THEN r2 ELSE r3 END\
The built-in [iif(x,y,z) SQL function](lang_corefunc.md#iif) is logically equivalent to "CASE WHEN x THEN y ELSE z END". The iif() function is found in SQL Server and is included in SQLite for compatibility. Some developers prefer the iif() function because it is more concise.
# 8. The IN and NOT IN operators
The IN and NOT IN operators take an expression on the left and a list of values or a subquery on the right. When the right operand of an IN or NOT IN operator is a subquery, the subquery must have the same number of columns as there are columns in the [row value](rowvalue.md) of the left operand. The subquery on the right of an IN or NOT IN operator must be a scalar subquery if the left expression is not a [row value](rowvalue.md) expression. If the right operand of an IN or NOT IN operator is a list of values, each of those values must be scalars and the left expression must also be a scalar. The right-hand side of an IN or NOT IN operator can be a table *name* or [table-valued function](vtab.md#tabfunc2) *name* in which case the right-hand side is understood to be a subquery of the form "(SELECT \* FROM *name*)". When the right operand is an empty set, the result of IN is false and the result of NOT IN is true, regardless of the left operand and even if the left operand is NULL.
The result of an IN or NOT IN operator is determined by the following matrix:
> | Left operand > is NULL |
> Right operand > contains NULL |
> Right operand > is an empty set |
> Left operand found > within right operand |
> Result of > IN operator |
> Result of > NOT IN operator |
>
|---|---|---|---|---|---|
| no | >no | >no | >no | >false | >true | >
| does not matter | >no | >yes | >no | >false | >true | >
| no | >does not matter | >no | >yes | >true | >false | >
| no | >yes | >no | >no | >NULL | >NULL | >
| yes | >does not matter | >no | >does not matter | >NULL | >NULL | >
| Affinity of type-name | >Conversion Processing | >
|---|---|
| NONE | >Casting a value to a type-name with no affinity causes the value to be converted into a BLOB. Casting to a BLOB consists of first casting the value to TEXT in the encoding of the database connection, then interpreting the resulting byte sequence as a BLOB instead of as TEXT. | >
| TEXT | >To cast a BLOB value to TEXT, the sequence of bytes that make up the BLOB is interpreted as text encoded using the database encoding.
> Casting an INTEGER or REAL value into TEXT renders the value as if via sqlite3_snprintf() except that the resulting TEXT uses the encoding of the database connection. |
>
| REAL | >When casting a BLOB value to a REAL, the value is first converted to TEXT.
> When casting a TEXT value to REAL, the longest possible prefix of the value that can be interpreted as a real number is extracted from the TEXT value and the remainder ignored. Any leading spaces in the TEXT value are ignored when converting from TEXT to REAL. If there is no prefix that can be interpreted as a real number, the result of the conversion is 0.0. |
>
| INTEGER | >When casting a BLOB value to INTEGER, the value is first converted to TEXT.
> When casting a TEXT value to INTEGER, the longest possible prefix of the value that can be interpreted as an integer number is extracted from the TEXT value and the remainder ignored. Any leading spaces in the TEXT value when converting from TEXT to INTEGER are ignored. If there is no prefix that can be interpreted as an integer number, the result of the conversion is 0. If the prefix integer is greater than +9223372036854775807 then the result of the cast is exactly +9223372036854775807. Similarly, if the prefix integer is less than -9223372036854775808 then the result of the cast is exactly -9223372036854775808. >When casting to INTEGER, if the text looks like a floating point value with an exponent, the exponent will be ignored because it is no part of the integer prefix. For example, "CAST('123e+5' AS INTEGER)" results in 123, not in 12300000. >The CAST operator understands decimal integers only — conversion of hexadecimal integers stops at the "x" in the "0x" prefix of the hexadecimal integer string and thus result of the CAST is always zero. >A cast of a REAL value into an INTEGER results in the integer between the REAL value and zero that is closest to the REAL value. If a REAL is greater than the greatest possible signed integer (+9223372036854775807) then the result is the greatest possible signed integer and if the REAL is less than the least possible signed integer (-9223372036854775808) then the result is the least possible signed integer. >Prior to SQLite version 3.8.2 (2013-12-06), casting a REAL value greater than +9223372036854775807.0 into an integer resulted in the most negative integer, -9223372036854775808. This behavior was meant to emulate the behavior of x86/x64 hardware when doing the equivalent cast. |
>
| NUMERIC | >Casting a TEXT or BLOB value into NUMERIC yields either an INTEGER or a REAL result. If the input text looks like an integer (there is no decimal point nor exponent) and the value is small enough to fit in a 64-bit signed integer, then the result will be INTEGER. Input text that looks like floating point (there is a decimal point and/or an exponent) and the text describes a value that can be losslessly converted back and forth between IEEE 754 64-bit float and a 51-bit signed integer, then the result is INTEGER. (In the previous sentence, a 51-bit integer is specified since that is one bit less than the length of the mantissa of an IEEE 754 64-bit float and thus provides a 1-bit of margin for the text-to-float conversion operation.) Any text input that describes a value outside the range of a 64-bit signed integer yields a REAL result.
> Casting a REAL or INTEGER value to NUMERIC is a no-op, even if a real value could be losslessly converted to an integer. |
>
**[aggregate-function-invocation:](syntax/aggregate-function-invocation.md)**
**[window-function-invocation:](syntax/window-function-invocation.md)**
The OVER clause is required for [window functions](windowfunctions.md) and is prohibited otherwise. The DISTINCT keyword and the ORDER BY clause is only allowed in [aggregate functions](lang_aggfunc.md). The FILTER clause may not appear on a [simple function](lang_corefunc.md).
It is possible to have an aggregate function with the same name as a simple function, as long as the number of arguments for the two forms of the function are different. For example, the [max()](lang_aggfunc.md#max_agg) function with a single argument is an aggregate and the [max()](lang_corefunc.md#max_scalar) function with two or more arguments is a simple function. Aggregate functions can usually also be used as window functions.
---
# SQLite Keywords
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_keywords.html*
The SQL standard specifies a large number of keywords which may not be used as the names of tables, indices, columns, databases, user-defined functions, collations, virtual table modules, or any other named object. The list of keywords is so long that few people can remember them all. For most SQL code, your safest bet is to never use any English language word as the name of a user-defined object.
If you want to use a keyword as a name, you need to quote it. There are four ways of quoting keywords in SQLite:
> | | | |
> |----|----|----|
> | **'keyword'** | | A keyword in single quotes is a string literal. |
> | **"keyword"** | | A keyword in double-quotes is an identifier. |
> | **\[keyword\]** | | A keyword enclosed in square brackets is an identifier. This is not standard SQL. This quoting mechanism is used by MS Access and SQL Server and is included in SQLite for compatibility. |
> | **\`keyword\`** | | A keyword enclosed in grave accents (ASCII code 96) is an identifier. This is not standard SQL. This quoting mechanism is used by MySQL and is included in SQLite for compatibility. |
For resilience when confronted with historical SQL statements, SQLite will sometimes bend the quoting rules above:
- If a keyword in single quotes (ex: **'key'** or **'glob'**) is used in a context where an identifier is allowed but where a string literal is not allowed, then the token is understood to be an identifier instead of a string literal.
- If a keyword in double quotes (ex: **"key"** or **"glob"**) is used in a context where it cannot be resolved to an identifier but where a string literal is allowed, then the token is understood to be a string literal instead of an identifier.
Programmers are cautioned not to use the two exceptions described in the previous bullets. We emphasize that they exist only so that old and ill-formed SQL statements will run correctly. Future versions of SQLite might raise errors instead of accepting the malformed statements covered by the exceptions above.
SQLite adds new keywords from time to time when it takes on new features. So to prevent your code from being broken by future enhancements, you should normally quote any identifier that is an English language word, even if you do not have to.
The list below shows all possible keywords used by any build of SQLite regardless of [compile-time options](compile.md). Most reasonable configurations use most or all of these keywords, but some keywords may be omitted when SQL language features are disabled. Applications can use the [sqlite3_keyword_count()](c3ref/keyword_check.md), [sqlite3_keyword_name()](c3ref/keyword_check.md), and [sqlite3_keyword_check()](c3ref/keyword_check.md) interfaces to determine the keywords recognized by SQLite at run-time. Regardless of the compile-time configuration, any identifier that is not on the following 147-element list is not a keyword to the SQL parser in SQLite:
- ABORT
- ACTION
- ADD
- AFTER
- ALL
- ALTER
- ALWAYS
- ANALYZE
- AND
- AS
- ASC
- ATTACH
- AUTOINCREMENT
- BEFORE
- BEGIN
- BETWEEN
- BY
- CASCADE
- CASE
- CAST
- CHECK
- COLLATE
- COLUMN
- COMMIT
- CONFLICT
- CONSTRAINT
- CREATE
- CROSS
- CURRENT
- CURRENT_DATE
- CURRENT_TIME
- CURRENT_TIMESTAMP
- DATABASE
- DEFAULT
- DEFERRABLE
- DEFERRED
- DELETE
- DESC
- DETACH
- DISTINCT
- DO
- DROP
- EACH
- ELSE
- END
- ESCAPE
- EXCEPT
- EXCLUDE
- EXCLUSIVE
- EXISTS
- EXPLAIN
- FAIL
- FILTER
- FIRST
- FOLLOWING
- FOR
- FOREIGN
- FROM
- FULL
- GENERATED
- GLOB
- GROUP
- GROUPS
- HAVING
- IF
- IGNORE
- IMMEDIATE
- IN
- INDEX
- INDEXED
- INITIALLY
- INNER
- INSERT
- INSTEAD
- INTERSECT
- INTO
- IS
- ISNULL
- JOIN
- KEY
- LAST
- LEFT
- LIKE
- LIMIT
- MATCH
- MATERIALIZED
- NATURAL
- NO
- NOT
- NOTHING
- NOTNULL
- NULL
- NULLS
- OF
- OFFSET
- ON
- OR
- ORDER
- OTHERS
- OUTER
- OVER
- PARTITION
- PLAN
- PRAGMA
- PRECEDING
- PRIMARY
- QUERY
- RAISE
- RANGE
- RECURSIVE
- REFERENCES
- REGEXP
- REINDEX
- RELEASE
- RENAME
- REPLACE
- RESTRICT
- RETURNING
- RIGHT
- ROLLBACK
- ROW
- ROWS
- SAVEPOINT
- SELECT
- SET
- TABLE
- TEMP
- TEMPORARY
- THEN
- TIES
- TO
- TRANSACTION
- TRIGGER
- UNBOUNDED
- UNION
- UNIQUE
- UPDATE
- USING
- VACUUM
- VALUES
- VIEW
- VIRTUAL
- WHEN
- WHERE
- WINDOW
- WITH
- WITHOUT
---
# The INDEXED BY Clause
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_indexedby.html*
# 1. How INDEXED BY Works
The INDEXED BY phrase forces the [SQLite query planner](optoverview.md) to use a particular named index on a [DELETE](lang_delete.md), [SELECT](lang_select.md), or [UPDATE](lang_update.md) statement. The INDEXED BY phrase is an SQLite extension and is not portable to other SQL database engines.
**[qualified-table-name:](syntax/qualified-table-name.md)** hide
The "INDEXED BY index-name" phrase specifies that the named index must be used in order to look up values on the preceding table. If index-name does not exist or cannot be used for the query, then the preparation of the SQL statement fails. The "NOT INDEXED" clause specifies that no index shall be used when accessing the preceding table, including implied indices create by UNIQUE and PRIMARY KEY constraints. However, the [rowid](lang_createtable.md#rowid) can still be used to look up entries even when "NOT INDEXED" is specified.
Some SQL database engines provide non-standard "hint" mechanisms which can be used to give the query optimizer clues about what indices it should use for a particular statement. The INDEXED BY clause of SQLite is *not* a hinting mechanism and it should not be used as such. The INDEXED BY clause does not give the optimizer hints about which index to use; it gives the optimizer a requirement of which index to use. If the query optimizer is unable to use the index specified by the INDEXED BY clause, then the query will fail with an error.
The INDEXED BY clause is *not* intended for use in tuning the performance of a query. The intent of the INDEXED BY clause is to raise a run-time error if a schema change, such as dropping or creating an index, causes the query plan for a time-sensitive query to change. The INDEXED BY clause is designed to help detect undesirable query plan changes during regression testing. Application developers are admonished to omit all use of INDEXED BY during application design, implementation, testing, and tuning. If INDEXED BY is to be used at all, it should be inserted at the very end of the development process when "locking down" a design.
# 2. See Also
1. The [query planner checklist](queryplanner-ng.md#howtofix) describes steps that application developers should follow to resolve query planner problems. Notice the that the use of INDEXED BY is a last resort, to be used only when all other measures fail.
2. [The unary "+" operator](optoverview.md#uplus) can be used to disqualify terms in the WHERE clause from use by indices. Careful use of unary + can sometimes help prevent the query planner from choosing a poor index without restricting it to using one specific index. Careful placement of unary + operators is a better method for controlling which indices are used by a query.
3. The [sqlite3_stmt_status()](c3ref/stmt_status.md) C/C++ interface together with the [SQLITE_STMTSTATUS_FULLSCAN_STEP](c3ref/c_stmtstatus_counter.md#sqlitestmtstatusfullscanstep) and [SQLITE_STMTSTATUS_SORT](c3ref/c_stmtstatus_counter.md#sqlitestmtstatussort) verbs can be used to detect at run-time when an SQL statement is not making effective use of indices. Many applications may prefer to use the [sqlite3_stmt_status()](c3ref/stmt_status.md) interface to detect index misuse rather than the INDEXED BY phrase described here.
---
# The ON CONFLICT Clause
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_conflict.html*
**[conflict-clause:](syntax/conflict-clause.md)** hide
The ON CONFLICT clause is a non-standard extension specific to SQLite that can appear in many other SQL commands. It is given its own section in this document because it is not part of standard SQL and therefore might not be familiar.
The ON CONFLICT clause described here has been a part of SQLite since before version 3.0.0 (2004-06-18). The phrase "ON CONFLICT" is also part of [UPSERT](lang_upsert.md), which is an extension to [INSERT](lang_insert.md) added in version 3.24.0 (2018-06-04). Do not confuse these two separate uses of the "ON CONFLICT" phrase.
The syntax for the ON CONFLICT clause is as shown above for the CREATE TABLE command. For the INSERT and UPDATE commands, the keywords "ON CONFLICT" are replaced by "OR" so that the syntax reads more naturally. For example, instead of "INSERT ON CONFLICT IGNORE" we have "INSERT OR IGNORE". The keywords change but the meaning of the clause is the same either way.
The ON CONFLICT clause is allowed on [UNIQUE](lang_createtable.md#uniqueconst), [NOT NULL](lang_createtable.md#notnullconst), and [PRIMARY KEY](lang_createtable.md#primkeyconst) constraints only. The ON CONFLICT clause is not allowed on [CHECK](lang_createtable.md#ckconst) and [FOREIGN KEY constraints](foreignkeys.md). There are five conflict resolution algorithm choices: ROLLBACK, ABORT, FAIL, IGNORE, and REPLACE. The default conflict resolution algorithm is ABORT. This is what they mean:
**ROLLBACK**
When an applicable constraint violation occurs, the ROLLBACK resolution algorithm aborts the current SQL statement with an SQLITE_CONSTRAINT error and rolls back the current transaction. If no transaction is active (other than the implied transaction that is created on every command) then the ROLLBACK resolution algorithm works the same as the ABORT algorithm.
**ABORT**
When an applicable constraint violation occurs, the ABORT resolution algorithm aborts the current SQL statement with an SQLITE_CONSTRAINT error and backs out any changes made by the current SQL statement; but changes caused by prior SQL statements within the same transaction are preserved and the transaction remains active. This is the default behavior and the behavior specified by the SQL standard.
**FAIL**
When an applicable constraint violation occurs, the FAIL resolution algorithm aborts the current SQL statement with an SQLITE_CONSTRAINT error. But the FAIL resolution does not back out prior changes of the SQL statement that failed nor does it end the transaction. For example, if an UPDATE statement encountered a constraint violation on the 100th row that it attempts to update, then the first 99 row changes are preserved but changes to rows 100 and beyond never occur.
The FAIL behavior only works for uniqueness, NOT NULL, and CHECK constraints. A [foreign key constraint](foreignkeys.md) violation causes an ABORT.
**IGNORE**
When an applicable constraint violation occurs, the IGNORE resolution algorithm skips the one row that contains the constraint violation and continues processing subsequent rows of the SQL statement as if nothing went wrong. Other rows before and after the row that contained the constraint violation are inserted or updated normally. No error is returned for uniqueness, NOT NULL, and UNIQUE constraint errors when the IGNORE conflict resolution algorithm is used. However, the IGNORE conflict resolution algorithm works like ABORT for [foreign key constraint](foreignkeys.md) errors.
**REPLACE**
When a [UNIQUE](lang_createtable.md#uniqueconst) or [PRIMARY KEY](lang_createtable.md#primkeyconst) constraint violation occurs, the REPLACE algorithm deletes pre-existing rows that are causing the constraint violation prior to inserting or updating the current row and the command continues executing normally. If a [NOT NULL](lang_createtable.md#notnullconst) constraint violation occurs, the REPLACE conflict resolution replaces the NULL value with the default value for that column, or if the column has no default value, then the ABORT algorithm is used. If a [CHECK constraint](lang_createtable.md#ckconst) or [foreign key constraint](foreignkeys.md) violation occurs, the REPLACE conflict resolution algorithm works like ABORT.
When the REPLACE conflict resolution strategy deletes rows in order to satisfy a constraint, [delete triggers](lang_createtrigger.md) fire if and only if [recursive triggers](pragma.md#pragma_recursive_triggers) are enabled.
The [update hook](c3ref/update_hook.md) is not invoked for rows that are deleted by the REPLACE conflict resolution strategy. Nor does REPLACE increment the [change counter](c3ref/changes.md). The exceptional behaviors defined in this paragraph might change in a future release.
The algorithm specified in the OR clause of an INSERT or UPDATE overrides any algorithm specified in a CREATE TABLE. If no algorithm is specified anywhere, the ABORT algorithm is used.
---
# The WITH Clause
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_with.html*
# 1. Overview
**[with-clause:](syntax/with-clause.md)** hide
**[cte-table-name:](syntax/cte-table-name.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
Common Table Expressions or CTEs act like temporary [views](lang_createview.md) that exist only for the duration of a single SQL statement. There are two kinds of common table expressions: "ordinary" and "recursive". Ordinary common table expressions are helpful for making queries easier to understand by factoring subqueries out of the main SQL statement. Recursive common table expressions provide the ability to do hierarchical or recursive queries of trees and graphs, a capability that is not otherwise available in the SQL language.
All common table expressions (ordinary and recursive) are created by prepending a WITH clause in front of a [SELECT](lang_select.md), [INSERT](lang_insert.md), [DELETE](lang_delete.md), or [UPDATE](lang_update.md) statement. A single WITH clause can specify one or more common table expressions, some of which are ordinary and some of which are recursive.
# 2. Ordinary Common Table Expressions
An ordinary common table expression works as if it were a [view](lang_createview.md) that exists for the duration of a single statement. Ordinary common table expressions are useful for factoring out subqueries and making the overall SQL statement easier to read and understand.
A WITH clause can contain ordinary common table expressions even if it includes the RECURSIVE keyword. The use of RECURSIVE does not force common table expressions to be recursive.
# 3. Recursive Common Table Expressions
A recursive common table expression can be used to write a query that walks a tree or graph. A recursive common table expression has the same basic syntax as an ordinary common table expression, but with the following additional attributes:
1. The "[select-stmt](syntax/select-stmt.md)" must be a [compound select](lang_select.md#compound). That is to say, the CTE body must be two or more individual SELECT statements separated by compound operators like UNION, UNION ALL, INTERSECT, or EXCEPT.
2. One or more of the individual SELECT statements that make up the compound must be "recursive". A SELECT statement is recursive if its FROM clause contains exactly one reference to the CTE table (the table named on the left-hand side of the AS clause).
3. One or more of the SELECT statements in the compound must be non-recursive.
4. All non-recursive SELECT statements must occur before any recursive SELECT statements.
5. The recursive SELECT statements must be separated from the non-recursive SELECT statements and from each other by the UNION or UNION ALL operators. If there are two or more recursive SELECT statements, they all must be separated from each other using the same operator that separates the first recursive SELECT from the last non-recursive SELECT statement.
6. Recursive SELECT statements may not use [aggregate functions](lang_aggfunc.md) or [window functions](windowfunctions.md).
To put it another way, a recursive common table expression must look something like the following:
**[recursive-cte:](syntax/recursive-cte.md)** hide
**[cte-table-name:](syntax/cte-table-name.md)** show
In the diagram above, initial-select means one or more non-recursive SELECT statements and recursive-select means one or more recursive SELECT statements. The most common case is for there to be exactly one initial-select and exactly one recursive-select but more than one of each is allowed.
Call the table named by the [cte-table-name](syntax/cte-table-name.md) in a recursive common table expression the "recursive table". In the [recursive-cte](syntax/recursive-cte.md) bubble diagram above, the recursive table must appear exactly once in the FROM clause of each top-level SELECT statement in the recursive-select and must not appear anywhere else in either the initial-select or the recursive-select, including subqueries. The initial-select may be a [compound select](lang_select.md#compound), but it may not include an ORDER BY, LIMIT, or OFFSET. The recursive-select may also be a [compound select](lang_select.md#compound) with the restriction that all elements of that compound must be separated by the same UNION or UNION ALL operator that separates initial-select from recursive-select. The recursive-select is allowed to include an ORDER BY, LIMIT, and/or OFFSET but may not use [aggregate functions](lang_aggfunc.md) or [window functions](windowfunctions.md).
The ability for the recursive-select to be a compound was added in [version 3.34.0](releaselog/3_34_0.md) (2020-12-01). In earlier versions of SQLite, the recursive-select could only be a single simple SELECT statement.
The basic algorithm for computing the content of the recursive table is as follows:
1. Run the initial-select and add the results to a queue.
2. While the queue is not empty:
1. Extract a single row from the queue.
2. Insert that single row into the recursive table
3. Pretend that the single row just extracted is the only row in the recursive table and run the recursive-select, adding all results to the queue.
The basic procedure above may be modified by the following additional rules:
- If a UNION operator connects the initial-select with the recursive-select, then only add rows to the queue if no identical row has been previously added to the queue. Repeated rows are discarded before being added to the queue even if the repeated rows have already been extracted from the queue by the recursion step. If the operator is UNION ALL, then all rows generated by both the initial-select and the recursive-select are always added to the queue even if they are repeats. When determining if a row is repeated, NULL values compare equal to one another and not equal to any other value.
- The LIMIT clause, if present, determines the maximum number of rows that will ever be added to the recursive table in step 2b. Once the limit is reached, the recursion stops. A limit of zero means that no rows are ever added to the recursive table, and a negative limit means an unlimited number of rows may be added to the recursive table.
- The OFFSET clause, if it is present and has a positive value N, prevents the first N rows from being added to the recursive table. The first N rows are still processed by the recursive-select — they just are not added to the recursive table. Rows are not counted toward fulfilling the LIMIT until all OFFSET rows have been skipped.
- If an ORDER BY clause is present, it determines the order in which rows are extracted from the queue in step 2a. If there is no ORDER BY clause, then the order in which rows are extracted is undefined. (In the current implementation, the queue becomes a FIFO if the ORDER BY clause is omitted, but applications should not depend on that fact since it might change.)
## 3.1. Recursive Query Examples
The following query returns all integers between 1 and 1000000:
> \
> WITH RECURSIVE\
> cnt(x) AS (VALUES(1) UNION ALL SELECT x+1 FROM cnt WHERE x\<1000000)\
> SELECT x FROM cnt;\
Consider how this query works. The initial-select runs first and returns a single row with a single column "1". This one row is added to the queue. In step 2a, that one row is extracted from the queue and added to "cnt". Then the recursive-select is run in accordance with step 2c generating a single new row with value "2" to add to the queue. The queue still has one row, so step 2 repeats. The "2" row is extracted and added to the recursive table by steps 2a and 2b. Then the row containing 2 is used as if it were the complete content of the recursive table and the recursive-select is run again, resulting in a row with value "3" being added to the queue. This repeats 999999 times until finally at step 2a the only value on the queue is a row containing 1000000. That row is extracted and added to the recursive table. But this time, the WHERE clause causes the recursive-select to return no rows, so the queue remains empty and the recursion stops.
**Optimization note:** In the discussion above, statements like "insert the row into the recursive table" should be understood conceptually, not literally. It sounds as if SQLite is accumulating a huge table containing one million rows, then going back and scanning that table from top to bottom to generate the result. What really happens is that the query optimizer sees that values in the "cnt" recursive table are only used once. So as each row is added to the recursive table, that row is immediately returned as a result of the main SELECT statement and then discarded. SQLite does *not* accumulate a temporary table containing a million rows. Very little memory is needed to run the above example. However, if the example had used UNION instead of UNION ALL, then SQLite would have had to keep around all previously generated content in order to check for duplicates. For this reason, programmers should strive to use UNION ALL instead of UNION when feasible.
Here is a variation on the previous example:
> \
> WITH RECURSIVE\
> cnt(x) AS (\
> SELECT 1\
> UNION ALL\
> SELECT x+1 FROM cnt\
> LIMIT 1000000\
> )\
> SELECT x FROM cnt;\
There are two differences in this variation. The initial-select is "SELECT 1" instead of "VALUES(1)". But those are just different syntaxes for saying exactly the same thing. The other change is that the recursion is stopped by a LIMIT rather than a WHERE clause. The use of LIMIT means that when the one-millionth row is added to the "cnt" table (and returned by the main SELECT, thanks to the query optimizer) then the recursion stops immediately regardless of how many rows might be left in the queue. On more complex queries, it can sometimes be difficult to ensure that the WHERE clause will eventually cause the queue to drain and the recursion to terminate. But the LIMIT clause will always stop the recursion. So it is good practice to always include a LIMIT clause as a safety if an upper bound on the size of the recursion is known.
## 3.2. Hierarchical Query Examples
Consider a table that describes the members of an organization as well as the chain-of-command within that organization:
> \
> CREATE TABLE org(\
> name TEXT PRIMARY KEY,\
> boss TEXT REFERENCES org,\
> height INT,\
> -- other content omitted\
> );\
Every member in the organization has a name, and most members have a single boss. (The head of the whole organization has a NULL "boss" field.) The rows of the "org" table form a tree.
Here is a query that computes the average height over everyone in Alice's organization, including Alice:
> \
> WITH RECURSIVE\
> works_for_alice(n) AS (\
> VALUES('Alice')\
> UNION\
> SELECT name FROM org, works_for_alice\
> WHERE org.boss=works_for_alice.n\
> )\
> SELECT avg(height) FROM org\
> WHERE org.name IN works_for_alice;\
The next example uses two common table expressions in a single WITH clause. The following table records a family tree:
> \
> CREATE TABLE family(\
> name TEXT PRIMARY KEY,\
> mom TEXT REFERENCES family,\
> dad TEXT REFERENCES family,\
> born DATETIME,\
> died DATETIME -- NULL if still alive\
> -- other content\
> );\
The "family" table is similar to the earlier "org" table except that now there are two parents to each member. We want to know all living ancestors of Alice, from oldest to youngest. An ordinary common table expression, "parent_of", is defined first. That ordinary CTE is a view that can be used to find all parents of any individual. That ordinary CTE is then used in the "ancestor_of_alice" recursive CTE. The recursive CTE is then used in the final query:
> \
> WITH RECURSIVE\
> parent_of(name, parent) AS\
> (SELECT name, mom FROM family UNION SELECT name, dad FROM family),\
> ancestor_of_alice(name) AS\
> (SELECT parent FROM parent_of WHERE name='Alice'\
> UNION ALL\
> SELECT parent FROM parent_of JOIN ancestor_of_alice USING(name))\
> SELECT family.name FROM ancestor_of_alice, family\
> WHERE ancestor_of_alice.name=family.name\
> AND died IS NULL\
> ORDER BY born;\
## 3.3. Queries Against A Graph
Suppose you have an undirected graph where each node is identified by an integer and edges are defined by a table like this:
> \
> CREATE TABLE edge(aa INT, bb INT);\
> CREATE INDEX edge_aa ON edge(aa);\
> CREATE INDEX edge_bb ON edge(bb);\
The indexes are not required, but they do help performance for large graphs. To find all nodes of the graph that are connected to node 59, use a query similar to the following:
> \
> WITH RECURSIVE nodes(x) AS (\
> SELECT 59\
> UNION\
> SELECT aa FROM edge JOIN nodes ON bb=x\
> UNION\
> SELECT bb FROM edge JOIN nodes ON aa=x\
> )\
> SELECT x FROM nodes;\
The initial-select in this case is the simple query "SELECT 59". This establishes the base case. The recursive-select consists of the other two SELECT statements. The first recursive SELECT follows edges in the bb-to-aa direction and the second recursive SELECT follows edges in the aa-to-bb direction. UNION is used instead of UNION ALL to prevent the recursion from entering an infinite loop if the graph contains cycles.
Here is a real-world example of using a graph query against a directed graph: A version control system (VCS) will typically store the evolving versions of a project as a directed acyclic graph (DAG). Call each version of the project a "checkin". A single checkin can have zero or more parents. Most checkins (except the first) have a single parent, but in the case of a merge, a checkin might have two or three or more parents. A schema to keep track of checkins and the order in which they occur might look something like this:
> \
> CREATE TABLE checkin(\
> id INTEGER PRIMARY KEY,\
> mtime INTEGER -- timestamp when this checkin occurred\
> );\
> CREATE TABLE derivedfrom(\
> xfrom INTEGER NOT NULL REFERENCES checkin, -- parent checkin\
> xto INTEGER NOT NULL REFERENCES checkin, -- derived checkin\
> PRIMARY KEY(xfrom,xto)\
> );\
> CREATE INDEX derivedfrom_back ON derivedfrom(xto,xfrom);\
This graph is acyclic. And we assume that the mtime of every child checkin is no less than the mtime of all its parents. But unlike the earlier examples, this graph might have multiple paths of differing lengths between any two checkins.
We want to know the twenty most recent ancestors in time (out of the thousands and thousands of ancestors in the whole DAG) for checkin "@BASELINE". (A query similar to this is used by the [Fossil](http://www.fossil-scm.org/) VCS to show the N most recent ancestors of a checkin. For example:
**[commit-stmt:](syntax/commit-stmt.md)** hide
**[rollback-stmt:](syntax/rollback-stmt.md)** hide
# 2. Transactions
No reads or writes occur except within a transaction. Any command that accesses the database (basically, any SQL command, except a few [PRAGMA](pragma.md#syntax) statements) will automatically start a transaction if one is not already in effect. Automatically started transactions are committed when the last SQL statement finishes.
Transactions can be started manually using the BEGIN command. Such transactions usually persist until the next COMMIT or ROLLBACK command. But a transaction will also ROLLBACK if the database is closed or if an error occurs and the ROLLBACK conflict resolution algorithm is specified. See the documentation on the [ON CONFLICT](lang_conflict.md) clause for additional information about the ROLLBACK conflict resolution algorithm.
END TRANSACTION is an alias for COMMIT.
Transactions created using BEGIN...COMMIT do not nest. For nested transactions, use the [SAVEPOINT](lang_savepoint.md) and [RELEASE](lang_savepoint.md) commands. The "TO SAVEPOINT name" clause of the ROLLBACK command shown in the syntax diagram above is only applicable to [SAVEPOINT](lang_savepoint.md) transactions. An attempt to invoke the BEGIN command within a transaction will fail with an error, regardless of whether the transaction was started by [SAVEPOINT](lang_savepoint.md) or a prior BEGIN. The COMMIT command and the ROLLBACK command without the TO clause work the same on [SAVEPOINT](lang_savepoint.md) transactions as they do with transactions started by BEGIN.
## 2.1. Read transactions versus write transactions
SQLite supports multiple simultaneous read transactions coming from separate database connections, possibly in separate threads or processes, but only one simultaneous write transaction.
A read transaction is used for reading only. A write transaction allows both reading and writing. A read transaction is started by a SELECT statement, and a write transaction is started by statements like CREATE, DELETE, DROP, INSERT, or UPDATE (collectively "write statements"). If a write statement occurs while a read transaction is active, then the read transaction is upgraded to a write transaction if possible. If some other database connection has already modified the database or is already in the process of modifying the database, then upgrading to a write transaction is not possible and the write statement will fail with [SQLITE_BUSY](rescode.md#busy).
While a read transaction is active, any changes to the database that are implemented by separate database connections will not be seen by the database connection that started the read transaction. If database connection X is holding a read transaction, it is possible that some other database connection Y might change the content of the database while X's transaction is still open, however X will not be able to see those changes until after the transaction ends. While its read transaction is active, X will continue to see an historic snapshot of the database prior to the changes implemented by Y.
## 2.2. DEFERRED, IMMEDIATE, and EXCLUSIVE transactions
Transactions can be DEFERRED, IMMEDIATE, or EXCLUSIVE. The default transaction behavior is DEFERRED.
DEFERRED means that the transaction does not actually start until the database is first accessed. Internally, the BEGIN DEFERRED statement merely sets a flag on the database connection that turns off the automatic commit that would normally occur when the last statement finishes. This causes the transaction that is automatically started to persist until an explicit COMMIT or ROLLBACK or until a rollback is provoked by an error or an ON CONFLICT ROLLBACK clause. If the first statement after BEGIN DEFERRED is a SELECT, then a read transaction is started. Subsequent write statements will upgrade the transaction to a write transaction if possible, or return SQLITE_BUSY. If the first statement after BEGIN DEFERRED is a write statement, then a write transaction is started.
IMMEDIATE causes the database connection to start a new write immediately, without waiting for a write statement. The BEGIN IMMEDIATE might fail with [SQLITE_BUSY](rescode.md#busy) if another write transaction is already active on another database connection.
EXCLUSIVE is similar to IMMEDIATE in that a write transaction is started immediately. EXCLUSIVE and IMMEDIATE are the same in [WAL mode](wal.md), but in other journaling modes, EXCLUSIVE prevents other database connections from reading the database while the transaction is underway.
## 2.3. Implicit versus explicit transactions
An implicit transaction (a transaction that is started automatically, not a transaction started by BEGIN) is committed automatically when the last active statement finishes. A statement finishes when its last cursor closes, which is guaranteed to happen when the prepared statement is [reset](c3ref/reset.md) or [finalized](c3ref/finalize.md). Some statements might "finish" for the purpose of transaction control prior to being reset or finalized, but there is no guarantee of this. The only way to ensure that a statement has "finished" is to invoke [sqlite3_reset()](c3ref/reset.md) or [sqlite3_finalize()](c3ref/finalize.md) on that statement. An open [sqlite3_blob](c3ref/blob.md) used for incremental BLOB I/O also counts as an unfinished statement. The [sqlite3_blob](c3ref/blob.md) finishes when it is [closed](c3ref/blob_close.md).
The explicit COMMIT command runs immediately, even if there are pending [SELECT](lang_select.md) statements. However, if there are pending write operations, the COMMIT command will fail with an error code [SQLITE_BUSY](rescode.md#busy).
An attempt to execute COMMIT might also result in an [SQLITE_BUSY](rescode.md#busy) return code if another thread or process has an open read connection. When COMMIT fails in this way, the transaction remains active and the COMMIT can be retried later after the reader has had a chance to clear.
In very old versions of SQLite (before version 3.7.11 - 2012-03-20) the ROLLBACK will fail with an error code [SQLITE_BUSY](rescode.md#busy) if there are any pending queries. In more recent versions of SQLite, the ROLLBACK will proceed and pending statements will often be aborted, causing them to return an [SQLITE_ABORT](rescode.md#abort) or [SQLITE_ABORT_ROLLBACK](rescode.md#abort_rollback) error. In SQLite version 3.8.8 (2015-01-16) and later, a pending read will continue functioning after the ROLLBACK as long as the ROLLBACK does not modify the database schema.
If [PRAGMA journal_mode](pragma.md#pragma_journal_mode) is set to OFF (thus disabling the rollback journal file) then the behavior of the ROLLBACK command is undefined.
# 3. Response To Errors Within A Transaction
If certain kinds of errors occur within a transaction, the transaction may or may not be rolled back automatically. The errors that can cause an automatic rollback include:
- [SQLITE_FULL](rescode.md#full): database or disk full
- [SQLITE_IOERR](rescode.md#ioerr): disk I/O error
- [SQLITE_INTERRUPT](rescode.md#interrupt): operation interrupted by [sqlite3_interrupt()](c3ref/interrupt.md) or similar.
- [SQLITE_NOMEM](rescode.md#nomem): out of memory
For all of these errors, SQLite attempts to undo just the one statement it was working on and leave changes from prior statements within the same transaction intact and continue with the transaction. However, depending on the statement being evaluated and the point at which the error occurs, it might be necessary for SQLite to rollback and cancel the entire transaction. An application can tell which course of action SQLite took by using the [sqlite3_get_autocommit()](c3ref/get_autocommit.md) or [sqlite3_txn_state()](c3ref/txn_state.md) C-language interfaces.
An application might want to respond to the errors listed above by explicitly issuing a ROLLBACK command. In that way, the transaction state will always be the same after one of the errors above. If the transaction has already been rolled back automatically by the error response, then the ROLLBACK command will fail with an error, but no harm is caused by this.
Future versions of SQLite may extend the list of errors which might cause automatic transaction rollback. Future versions of SQLite might change the error response. In particular, we may choose to simplify the interface in future versions of SQLite by causing the errors above to force an unconditional rollback.
---
# UPDATE
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_update.html*
# 1. Overview
**[update-stmt:](syntax/update-stmt.md)** hide
**[column-name-list:](syntax/column-name-list.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[qualified-table-name:](syntax/qualified-table-name.md)** show
**[returning-clause:](syntax/returning-clause.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
An UPDATE statement is used to modify a subset of the values stored in zero or more rows of the database table identified by the [qualified-table-name](syntax/qualified-table-name.md) specified as part of the UPDATE statement.
# 2. Details
If the UPDATE statement does not have a WHERE clause, all rows in the table are modified by the UPDATE. Otherwise, the UPDATE affects only those rows for which the WHERE clause [boolean expression is true](lang_expr.md#booleanexpr). It is not an error if the WHERE clause does not evaluate to true for any row in the table - this just means that the UPDATE statement affects zero rows.
The modifications made to each row affected by an UPDATE statement are determined by the list of assignments following the SET keyword. Each assignment specifies a column-name to the left of the equals sign and a scalar expression to the right. For each affected row, the named columns are set to the values found by evaluating the corresponding scalar expressions. If a single column-name appears more than once in the list of assignment expressions, all but the rightmost occurrence is ignored. Columns that do not appear in the list of assignments are left unmodified. The scalar expressions may refer to columns of the row being updated. In this case all scalar expressions are evaluated before any assignments are made.
Beginning in SQLite [version 3.15.0](releaselog/3_15_0.md) (2016-10-14), an assignment in the SET clause can be a [parenthesized list of column names](syntax/column-name-list.md) on the left and a [row value](rowvalue.md) of the same size on the right.
The optional "OR *action*" conflict clause that follows the UPDATE keyword allows the user to nominate a specific constraint conflict resolution algorithm to use during this one UPDATE command. Refer to the section entitled [ON CONFLICT](lang_conflict.md) for additional information.
## 2.1. Restrictions on UPDATE Statements Within CREATE TRIGGER
The following additional syntax restrictions apply to UPDATE statements that occur within the body of a [CREATE TRIGGER](lang_createtrigger.md) statement.
- The table-name specified as part of an UPDATE statement within a trigger body must be unqualified. In other words, the *schema-name***.** prefix on the table name of the UPDATE is not allowed within triggers. Unless the table to which the trigger is attached is in the TEMP database, the table being updated by the trigger program must reside in the same database as it. If the table to which the trigger is attached is in the TEMP database, then the unqualified name of the table being updated is resolved in the same way as it is for a top-level statement (by searching first the TEMP database, then the main database, then any other databases in the order they were attached).
- The INDEXED BY and NOT INDEXED clauses are not allowed on UPDATE statements within triggers.
- The LIMIT and ORDER BY clauses for UPDATE are unsupported within triggers, regardless of the compilation options used to build SQLite.
## 2.2. UPDATE FROM
The UPDATE-FROM idea is an extension to SQL that allows an UPDATE statement to be driven by other tables in the database. The "target" table is the specific table that is being updated. With UPDATE-FROM you can join the target table against other tables in the database in order to help compute which rows need updating and what the new values should be on those rows. UPDATE-FROM is supported beginning in SQLite version 3.33.0 (2020-08-14).
Other relation database engines also implement UPDATE-FROM, but because the construct is not part of the SQL standards, each product implements UPDATE-FROM differently. The SQLite implementation strives to be compatible with PostgreSQL. The SQL Server and MySQL implementations of the same idea work a little differently.
As an example of how UPDATE-FROM can be useful, suppose you have a point-of-sale application that accumulates purchases in the SALES table. At the end of the day, you want to adjust the INVENTORY table according to the daily sales. To do this, you can run an UPDATE against the INVENTORY table that adjusts the quantity by the aggregated sales for the day. The statement would look like this:
UPDATE inventory\
SET quantity = quantity - daily.amt\
FROM (SELECT sum(quantity) AS amt, itemId FROM sales GROUP BY 2) AS daily\
WHERE inventory.itemId = daily.itemId;\
The subquery in the FROM clause computes the amount by which the inventory should be reduced for each itemId. That subquery is joined against the inventory table and the quantity of each affected inventory row is reduced by the appropriate amount.
The target table is not included in the FROM clause, unless the intent is to do a self-join against the target table. In the event of a self-join, the table in the FROM clause must be aliased to a different name than the target table.
If the join between the target table and the FROM clause results in multiple output rows for the same target table row, then only one of those output rows is used for updating the target table. The output row selected is arbitrary and might change from one release of SQLite to the next, or from one run to the next.
### 2.2.1. UPDATE FROM in other SQL database engines
SQL Server also supports UPDATE FROM, but in SQL Server the target table must be included in the FROM clause. In other words, the target table is named twice in the statement. With SQL Server, the inventory adjustment statement demonstrated above would be written like this:
UPDATE inventory\
SET quantity = quantity - daily.amt\
FROM inventory, \
(SELECT sum(quantity) AS amt, itemId FROM sales GROUP BY 2) AS daily\
WHERE inventory.itemId = daily.itemId;\
MySQL supports the UPDATE FROM idea, but it does so without using a FROM clause. Instead, the complete join specification is given in between the UPDATE and SET keywords. The equivalent MySQL statement would be like this:
UPDATE inventory JOIN\
(SELECT sum(quantity) AS amt, itemId FROM sales GROUP BY 2) AS daily\
USING( itemId )\
SET inventory.quantity = inventory.quantity - daily.amt;\
The MySQL UPDATE statement does not have just one target table like other systems. Any of the tables that participate in the join can be modified in the SET clause. The MySQL UPDATE syntax allows you to update multiple tables at once!
## 2.3. Optional LIMIT and ORDER BY Clauses
If SQLite is built with the [SQLITE_ENABLE_UPDATE_DELETE_LIMIT](compile.md#enable_update_delete_limit) compile-time option then the syntax of the UPDATE statement is extended with optional ORDER BY and LIMIT clauses as follows:
**[update-stmt-limited:](syntax/update-stmt-limited.md)**
If an UPDATE statement has a LIMIT clause, the maximum number of rows that will be updated is found by evaluating the accompanying expression and casting it to an integer value. A negative value is interpreted as "no limit".
If the LIMIT expression evaluates to non-negative value *N* and the UPDATE statement has an ORDER BY clause, then all rows that would be updated in the absence of the LIMIT clause are sorted according to the ORDER BY and the first *N* updated. If the UPDATE statement also has an OFFSET clause, then it is similarly evaluated and cast to an integer value. If the OFFSET expression evaluates to a non-negative value *M*, then the first *M* rows are skipped and the following *N* rows updated instead.
If the UPDATE statement has no ORDER BY clause, then all rows that would be updated in the absence of the LIMIT clause are assembled in an arbitrary order before applying the LIMIT and OFFSET clauses to determine which are actually updated.
The ORDER BY clause on an UPDATE statement is used only to determine which rows fall within the LIMIT. The order in which rows are modified is arbitrary and is not influenced by the ORDER BY clause.
---
# UPSERT
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_upsert.html*
# 1. Syntax
**[upsert-clause:](syntax/upsert-clause.md)** hide
**[column-name-list:](syntax/column-name-list.md)** show
**[expr:](syntax/expr.md)** show
**[filter-clause:](syntax/filter-clause.md)** show
**[function-arguments:](syntax/function-arguments.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[literal-value:](syntax/literal-value.md)** show
**[over-clause:](syntax/over-clause.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[raise-function:](syntax/raise-function.md)** show
**[select-stmt:](syntax/select-stmt.md)** show
**[common-table-expression:](syntax/common-table-expression.md)** show
**[compound-operator:](syntax/compound-operator.md)** show
**[join-clause:](syntax/join-clause.md)** show
**[join-constraint:](syntax/join-constraint.md)** show
**[join-operator:](syntax/join-operator.md)** show
**[ordering-term:](syntax/ordering-term.md)** show
**[result-column:](syntax/result-column.md)** show
**[table-or-subquery:](syntax/table-or-subquery.md)** show
**[window-defn:](syntax/window-defn.md)** show
**[frame-spec:](syntax/frame-spec.md)** show
**[type-name:](syntax/type-name.md)** show
**[signed-number:](syntax/signed-number.md)** show
**[indexed-column:](syntax/indexed-column.md)** show
# 2. Description
UPSERT is a clause added to [INSERT](lang_insert.md) that causes the INSERT to behave as an [UPDATE](lang_update.md) or a no-op if the INSERT would violate a uniqueness constraint. UPSERT is not standard SQL. UPSERT in SQLite follows the syntax established by PostgreSQL, with generalizations.
An UPSERT is an ordinary [INSERT](lang_insert.md) statement that is followed by one or more ON CONFLICT clauses, as shown in the syntax diagram above.
The syntax in between the "ON CONFLICT" and "DO" keywords is called the "conflict target". The conflict target specifies a uniqueness constraint that will trigger the upsert. The conflict target may be omitted on the last ON CONFLICT clause in the INSERT statement, but is required for all other ON CONFLICT clauses.
If the insert operation would cause the conflict target uniqueness constraint to fail, then the insert is omitted and the corresponding DO NOTHING or DO UPDATE operation is performed instead. The ON CONFLICT clauses are checked in the order specified. If the last ON CONFLICT clause omits the conflict target, then it will fire if any uniqueness constraint fails which is not captured by prior ON CONFLICT clauses.
Only a single ON CONFLICT clause, specifically the first ON CONFLICT clause with a matching conflict target, may run for each row of the INSERT. When an ON CONFLICT clause fires, all subsequent ON CONFLICT clauses are bypassed for that one row.
In the case of a multi-row insert, the upsert decision is made separately for each row of the insert.
The UPSERT processing happens only for uniqueness constraints. A "uniqueness constraint" is an explicit UNIQUE or PRIMARY KEY constraint within the CREATE TABLE statement, or a [unique index](lang_createindex.md#uniqueidx). UPSERT does not intervene for failed NOT NULL, CHECK, or foreign key constraints or for constraints that are implemented using triggers.
Column names in the expressions of a DO UPDATE refer to the original unchanged value of the column, before the attempted INSERT. To use the value that would have been inserted had the constraint not failed, add the special "excluded." table qualifier to the column name.
## 2.1. Examples
Some examples will help illustrate how UPSERT works:
> \
> CREATE TABLE vocabulary(word TEXT PRIMARY KEY, count INT DEFAULT 1);\
> INSERT INTO vocabulary(word) VALUES('jovial')\
> ON CONFLICT(word) DO UPDATE SET count=count+1;\
The upsert above inserts the new vocabulary word "jovial" if that word is not already in the dictionary, or if it is already in the dictionary, it increments the counter. The "count+1" expression could also be written as "vocabulary.count". PostgreSQL requires the second form, but SQLite accepts either.
> \
> CREATE TABLE phonebook(name TEXT PRIMARY KEY, phonenumber TEXT);\
> INSERT INTO phonebook(name,phonenumber) VALUES('Alice','704-555-1212')\
> ON CONFLICT(name) DO UPDATE SET phonenumber=excluded.phonenumber;\
In the second example, the expression in the DO UPDATE clause is of the form "excluded.phonenumber". The "excluded." prefix causes the "phonenumber" to refer to the value for phonenumber that would have been inserted had there been no conflict. Hence, the effect of the upsert is to insert a phonenumber of Alice if none exists, or to overwrite any prior phonenumber for Alice with the new one.
Note that the DO UPDATE clause acts only on the single row that experienced the constraint error during INSERT. It is not necessary to include a WHERE clause that restricts the action to that one row. The only use for the WHERE clause at the end of the DO UPDATE is to optionally change the DO UPDATE into a no-op depending on the original and/or new values. For example:
> \
> CREATE TABLE phonebook2(\
> name TEXT PRIMARY KEY,\
> phonenumber TEXT,\
> validDate DATE\
> );\
> INSERT INTO phonebook2(name,phonenumber,validDate)\
> VALUES('Alice','704-555-1212','2018-05-08')\
> ON CONFLICT(name) DO UPDATE SET\
> phonenumber=excluded.phonenumber,\
> validDate=excluded.validDate\
> WHERE excluded.validDate\>phonebook2.validDate;\
In this last example, the phonebook2 entry is only updated if the validDate for the newly inserted value is newer than the entry already in the table. If the table already contains an entry with the same name and a current validDate, then the WHERE clause causes the DO UPDATE to become a no-op.
## 2.2. Parsing Ambiguity
When the [INSERT](lang_insert.md) statement to which the UPSERT is attached takes its values from a [SELECT](lang_select.md) statement, there is a potential parsing ambiguity. The parser might not be able to tell if the "ON" keyword is introducing the UPSERT or if it is the ON clause of a join. To work around this, the SELECT statement should always include a WHERE clause, even if that WHERE clause is just "WHERE true".
Ambiguous use of ON:
> \
> INSERT INTO t1 SELECT \* FROM t2\
> ON CONFLICT(x) DO UPDATE SET y=excluded.y;\
Ambiguity resolved using a WHERE clause:
> \
> INSERT INTO t1 SELECT \* FROM t2 WHERE true\
> ON CONFLICT(x) DO UPDATE SET y=excluded.y;\
# 3. Limitations
UPSERT does not currently work for [virtual tables](vtab.md).
The [conflict resolution algorithm](lang_conflict.md) for the update operation of the DO UPDATE clause is always ABORT. In other words, the behavior is as if the DO UPDATE clause were actually written as "DO UPDATE OR ABORT". If the DO UPDATE clause encounters any constraint violation, the entire INSERT statement rolls back and halts. This is true even if the DO UPDATE clause is contained within an INSERT statement or a trigger that specifies some other conflict resolution algorithm.
# 4. History
UPSERT syntax was added to SQLite with version 3.24.0 (2018-06-04). The original implementation closely followed the PostgreSQL syntax in that it only permitted a single ON CONFLICT clause and it required a conflict target for on DO UPDATE. The syntax was generalized to permit multiple ON CONFLICT clauses and to allow DO UPDATE resolution without a conflict target in SQLite version 3.35.0 (2021-03-12).
---
# VACUUM
*Sección: Sql Language | Origen: https://www.sqlite.org/lang_vacuum.html*
# 1. Syntax
**[vacuum-stmt:](syntax/vacuum-stmt.md)** hide
# 2. Description
The VACUUM command rebuilds the database file, repacking it into a minimal amount of disk space. There are several reasons an application might do this:
- Unless SQLite is running in "auto_vacuum=FULL" mode, when a large amount of data is deleted from the database file it leaves behind empty space, or "free" database pages. This means the database file might be larger than strictly necessary. Running VACUUM to rebuild the database reclaims this space and reduces the size of the database file.
- Frequent inserts, updates, and deletes can cause the database file to become fragmented - where data for a single table or index is scattered around the database file. Running VACUUM ensures that each table and index is largely stored contiguously within the database file. In some cases, VACUUM may also reduce the number of partially filled pages in the database, reducing the size of the database file further.
- When content is deleted from an SQLite database, the content is not usually erased but rather the space used to hold the content is marked as being available for reuse. This can allow deleted content to be recovered by a hacker or by forensic analysis. Running VACUUM will clean the database of all traces of deleted content, thus preventing an adversary from recovering deleted content. Using VACUUM in this way is an alternative to setting [PRAGMA secure_delete=ON](pragma.md#pragma_secure_delete).
- Normally, the database [page_size](pragma.md#pragma_page_size) and whether or not the database supports [auto_vacuum](pragma.md#pragma_auto_vacuum) must be configured before the database file is actually created. However, when not in [write-ahead log](wal.md) mode, the [page_size](pragma.md#pragma_page_size) and/or [auto_vacuum](pragma.md#pragma_auto_vacuum) properties of an existing database may be changed by using the [page_size](pragma.md#pragma_page_size) and/or [pragma auto_vacuum](pragma.md#pragma_auto_vacuum) pragmas and then immediately VACUUMing the database. When in [write-ahead log](wal.md) mode, only the [auto_vacuum](pragma.md#pragma_auto_vacuum) support property can be changed using VACUUM.
By default, VACUUM operates on the main database. [Attached databases](lang_attach.md) can be vacuumed by appending the appropriate schema-name to the VACUUM statement.
**Compatibility Warning:** The ability to vacuum attached databases was added in [version 3.15.0](releaselog/3_15_0.md) (2016-10-14). Prior to that, a schema-name added to the VACUUM statement would be silently ignored and the "main" schema would be vacuumed.
## 2.1. VACUUM with an INTO clause
If the INTO clause is included, then the original database file is unchanged and a new database is created in a file named by the argument to the INTO clause. The argument is a scalar [expression](lang_expr.md), such as a text literal. The new database will contain the same logical content as the original database, fully vacuumed.
The VACUUM command with an INTO clause is an alternative to the [backup API](backup.md) for generating backup copies of a live database. The advantage of using VACUUM INTO is that the resulting backup database is minimal in size and hence the amount of filesystem I/O may be reduced. Also, all deleted content is purged from the backup, leaving behind no forensic traces. On the other hand, the [backup API](backup.md) uses fewer CPU cycles and can be executed incrementally.
The filename in the INTO clause can be an arbitrary SQL expression that evaluates to a string. The file named by the INTO clause must not previously exist, or else it must be an empty file, or the VACUUM INTO command will fail with an error.
The argument to INTO can be a [URI filename](uri.md) if URI filenames are enabled. URL filenames are enabled if any of the following are true:
- The SQLite library was compiled with [-DSQLITE_USE_URI=1](compile.md#use_uri).
- The [sqlite3_config](c3ref/config.md)([SQLITE_CONFIG_URI](c3ref/c_config_covering_index_scan.md#sqliteconfiguri),1) interfaces was invoked at start-time.
- The [database connection](c3ref/sqlite3.md) that is running the VACUUM INTO statement was originally opened using the [SQLITE_OPEN_URI](c3ref/c_open_autoproxy.md) flag.
The VACUUM INTO command is transactional in the sense that the generated output database is a consistent snapshot of the original database. However, if the VACUUM INTO command is interrupted by an unplanned shutdown or power loss, then the generated output database might be incomplete and corrupt.
However, if the [PRAGMA synchronous](pragma.md#pragma_synchronous) setting of the original database is NORMAL or FULL, then SQLite invokes fsync() or FileFlushBuffers() to sync the output database to disk after it has been written. This means that in these cases, a power failure or unplanned shutdown that occurs after the VACUUM INTO command has completed should not corrupt the database (assuming the OS, file-system and hardware are functioning correctly).
# 3. How VACUUM works
The VACUUM command works by copying the contents of the database into a temporary database file and then overwriting the original with the contents of the temporary file. When overwriting the original, a rollback journal or [write-ahead log](wal.md) WAL file is used just as it would be for any other database transaction. This means that when VACUUMing a database, as much as twice the size of the original database file is required in free disk space.
The VACUUM INTO command works the same way except that it uses the file named on the INTO clause in place of the temporary database and omits the step of copying the vacuumed database back over top of the original database.
The VACUUM command may change the [ROWIDs](lang_createtable.md#rowid) of entries in any tables that do not have an explicit [INTEGER PRIMARY KEY](lang_createtable.md#rowid).
A VACUUM will fail if there is an open transaction on the database connection that is attempting to run the VACUUM. Unfinalized SQL statements typically hold a read transaction open, so the VACUUM might fail if there are unfinalized SQL statements on the same connection. VACUUM (but not VACUUM INTO) is a write operation and so if another database connection is holding a lock that prevents writes, then the VACUUM will fail.
An alternative to using the VACUUM command to reclaim space after data has been deleted is auto-vacuum mode, enabled using the [auto_vacuum](pragma.md#pragma_auto_vacuum) pragma. When [auto_vacuum](pragma.md#pragma_auto_vacuum) is enabled for a database free pages may be reclaimed after deleting data, causing the file to shrink, without rebuilding the entire database using VACUUM. However, using [auto_vacuum](pragma.md#pragma_auto_vacuum) can lead to extra database file fragmentation. And [auto_vacuum](pragma.md#pragma_auto_vacuum) does not compact partially filled pages of the database as VACUUM does.
---
# List of SQLite Syntax Diagrams
*Sección: Syntax | Origen: https://www.sqlite.org/syntax.html*
- [aggregate-function-invocation](syntax/aggregate-function-invocation.md)
- [alter-table-stmt](syntax/alter-table-stmt.md)
- [analyze-stmt](syntax/analyze-stmt.md)
- [attach-stmt](syntax/attach-stmt.md)
- [begin-stmt](syntax/begin-stmt.md)
- [column-constraint](syntax/column-constraint.md)
- [column-def](syntax/column-def.md)
- [column-name-list](syntax/column-name-list.md)
- [comment-syntax](syntax/comment-syntax.md)
- [commit-stmt](syntax/commit-stmt.md)
- [common-table-expression](syntax/common-table-expression.md)
- [compound-operator](syntax/compound-operator.md)
- [compound-select-stmt](syntax/compound-select-stmt.md)
- [conflict-clause](syntax/conflict-clause.md)
- [create-index-stmt](syntax/create-index-stmt.md)
- [create-table-stmt](syntax/create-table-stmt.md)
- [create-trigger-stmt](syntax/create-trigger-stmt.md)
- [create-view-stmt](syntax/create-view-stmt.md)
- [create-virtual-table-stmt](syntax/create-virtual-table-stmt.md)
- [cte-table-name](syntax/cte-table-name.md)
- [delete-stmt](syntax/delete-stmt.md)
- [delete-stmt-limited](syntax/delete-stmt-limited.md)
- [detach-stmt](syntax/detach-stmt.md)
- [drop-index-stmt](syntax/drop-index-stmt.md)
- [drop-table-stmt](syntax/drop-table-stmt.md)
- [drop-trigger-stmt](syntax/drop-trigger-stmt.md)
- [drop-view-stmt](syntax/drop-view-stmt.md)
- [expr](syntax/expr.md)
- [factored-select-stmt](syntax/factored-select-stmt.md)
- [filter-clause](syntax/filter-clause.md)
- [foreign-key-clause](syntax/foreign-key-clause.md)
- [frame-spec](syntax/frame-spec.md)
- [function-arguments](syntax/function-arguments.md)
- [indexed-column](syntax/indexed-column.md)
- [insert-stmt](syntax/insert-stmt.md)
- [join-clause](syntax/join-clause.md)
- [join-constraint](syntax/join-constraint.md)
- [join-operator](syntax/join-operator.md)
- [literal-value](syntax/literal-value.md)
- [numeric-literal](syntax/numeric-literal.md)
- [ordering-term](syntax/ordering-term.md)
- [over-clause](syntax/over-clause.md)
- [pragma-stmt](syntax/pragma-stmt.md)
- [pragma-value](syntax/pragma-value.md)
- [qualified-table-name](syntax/qualified-table-name.md)
- [raise-function](syntax/raise-function.md)
- [recursive-cte](syntax/recursive-cte.md)
- [reindex-stmt](syntax/reindex-stmt.md)
- [release-stmt](syntax/release-stmt.md)
- [result-column](syntax/result-column.md)
- [returning-clause](syntax/returning-clause.md)
- [rollback-stmt](syntax/rollback-stmt.md)
- [savepoint-stmt](syntax/savepoint-stmt.md)
- [select-core](syntax/select-core.md)
- [select-stmt](syntax/select-stmt.md)
- [signed-number](syntax/signed-number.md)
- [simple-function-invocation](syntax/simple-function-invocation.md)
- [simple-select-stmt](syntax/simple-select-stmt.md)
- [sql-stmt](syntax/sql-stmt.md)
- [sql-stmt-list](syntax/sql-stmt-list.md)
- [table-constraint](syntax/table-constraint.md)
- [table-options](syntax/table-options.md)
- [table-or-subquery](syntax/table-or-subquery.md)
- [type-name](syntax/type-name.md)
- [update-stmt](syntax/update-stmt.md)
- [update-stmt-limited](syntax/update-stmt-limited.md)
- [upsert-clause](syntax/upsert-clause.md)
- [vacuum-stmt](syntax/vacuum-stmt.md)
- [window-defn](syntax/window-defn.md)
- [window-function-invocation](syntax/window-function-invocation.md)
- [with-clause](syntax/with-clause.md)
---
# Syntax Diagrams For SQLite
*Sección: Syntax | Origen: https://www.sqlite.org/syntaxdiagrams.html*
#### aggregate-function-invocation:
\
References: [expr](#expr) [filter-clause](#filter-clause) [ordering-term](#ordering-term)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_expr.html#\*funcinexpr](lang_expr.md#*funcinexpr)
#### alter-table-stmt:
Used by: [sql-stmt](#sql-stmt)\
References: [column-def](#column-def) [conflict-clause](#conflict-clause) [expr](#expr)\
See also: [lang_altertable.html](lang_altertable.md)
#### analyze-stmt:
Used by: [sql-stmt](#sql-stmt)\
See also: [lang_analyze.html](lang_analyze.md)
#### attach-stmt:
Used by: [sql-stmt](#sql-stmt)\
References: [expr](#expr)\
See also: [lang_attach.html](lang_attach.md)
#### begin-stmt:
Used by: [sql-stmt](#sql-stmt)\
See also: [lang_transaction.html](lang_transaction.md)
#### column-constraint:
Used by: [column-def](#column-def)\
References: [conflict-clause](#conflict-clause) [expr](#expr) [foreign-key-clause](#foreign-key-clause) [literal-value](#literal-value) [signed-number](#signed-number)\
See also: [gencol.html](gencol.md) [lang_altertable.html](lang_altertable.md) [lang_createtable.html](lang_createtable.md) [lang_createtable.html#tablecoldef](lang_createtable.md#tablecoldef)
#### column-def:
Used by: [alter-table-stmt](#alter-table-stmt) [create-table-stmt](#create-table-stmt)\
References: [column-constraint](#column-constraint) [type-name](#type-name)\
See also: [lang_altertable.html](lang_altertable.md) [lang_altertable.html#altertabaddcol](lang_altertable.md#altertabaddcol) [lang_createtable.html](lang_createtable.md) [lang_createtable.html#tablecoldef](lang_createtable.md#tablecoldef)
#### column-name-list:
Used by: [update-stmt](#update-stmt) [update-stmt-limited](#update-stmt-limited) [upsert-clause](#upsert-clause)\
See also: [lang_createtrigger.html](lang_createtrigger.md) [lang_insert.html](lang_insert.md) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md)
#### comment-syntax:
\
See also: [lang_comment.html](lang_comment.md)
#### commit-stmt:
Used by: [sql-stmt](#sql-stmt)\
See also: [lang_transaction.html](lang_transaction.md)
#### common-table-expression:
Used by: [compound-select-stmt](#compound-select-stmt) [delete-stmt](#delete-stmt) [delete-stmt-limited](#delete-stmt-limited) [factored-select-stmt](#factored-select-stmt) [insert-stmt](#insert-stmt) [select-stmt](#select-stmt) [simple-select-stmt](#simple-select-stmt) [update-stmt](#update-stmt) [update-stmt-limited](#update-stmt-limited)\
References: [select-stmt](#select-stmt)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### compound-operator:
Used by: [factored-select-stmt](#factored-select-stmt) [select-stmt](#select-stmt)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### compound-select-stmt:
\
References: [common-table-expression](#common-table-expression) [expr](#expr) [ordering-term](#ordering-term) [select-core](#select-core)\
See also: [lang_select.html#compound](lang_select.md#compound)
#### conflict-clause:
Used by: [alter-table-stmt](#alter-table-stmt) [column-constraint](#column-constraint) [table-constraint](#table-constraint)\
See also: [lang_altertable.html](lang_altertable.md) [lang_conflict.html](lang_conflict.md) [lang_createtable.html](lang_createtable.md) [lang_createtable.html#notnullconst](lang_createtable.md#notnullconst)
#### create-index-stmt:
Used by: [sql-stmt](#sql-stmt)\
References: [expr](#expr) [indexed-column](#indexed-column)\
See also: [lang_createindex.html](lang_createindex.md) [partialindex.html](partialindex.md)
#### create-table-stmt:
Used by: [sql-stmt](#sql-stmt)\
References: [column-def](#column-def) [select-stmt](#select-stmt) [table-constraint](#table-constraint) [table-options](#table-options)\
See also: [lang_createtable.html](lang_createtable.md)
#### create-trigger-stmt:
Used by: [sql-stmt](#sql-stmt)\
References: [delete-stmt](#delete-stmt) [expr](#expr) [insert-stmt](#insert-stmt) [select-stmt](#select-stmt) [update-stmt](#update-stmt)\
See also: [lang_createtrigger.html](lang_createtrigger.md)
#### create-view-stmt:
Used by: [sql-stmt](#sql-stmt)\
References: [select-stmt](#select-stmt)\
See also: [lang_createview.html](lang_createview.md)
#### create-virtual-table-stmt:
Used by: [sql-stmt](#sql-stmt)\
See also: [lang_createvtab.html](lang_createvtab.md)
#### cte-table-name:
Used by: [recursive-cte](#recursive-cte) [with-clause](#with-clause)\
See also: [lang_with.html](lang_with.md) [lang_with.html#recursivecte](lang_with.md#recursivecte)
#### delete-stmt:
Used by: [create-trigger-stmt](#create-trigger-stmt) [sql-stmt](#sql-stmt)\
References: [common-table-expression](#common-table-expression) [expr](#expr) [qualified-table-name](#qualified-table-name) [returning-clause](#returning-clause)\
See also: [lang_createtrigger.html](lang_createtrigger.md) [lang_delete.html](lang_delete.md)
#### delete-stmt-limited:
Used by: [sql-stmt](#sql-stmt)\
References: [common-table-expression](#common-table-expression) [expr](#expr) [ordering-term](#ordering-term) [qualified-table-name](#qualified-table-name) [returning-clause](#returning-clause)\
See also: [lang_delete.html](lang_delete.md)
#### detach-stmt:
Used by: [sql-stmt](#sql-stmt)\
See also: [lang_detach.html](lang_detach.md)
#### drop-index-stmt:
Used by: [sql-stmt](#sql-stmt)\
See also: [lang_dropindex.html](lang_dropindex.md)
#### drop-table-stmt:
Used by: [sql-stmt](#sql-stmt)\
See also: [lang_droptable.html](lang_droptable.md)
#### drop-trigger-stmt:
Used by: [sql-stmt](#sql-stmt)\
See also: [lang_droptrigger.html](lang_droptrigger.md)
#### drop-view-stmt:
Used by: [sql-stmt](#sql-stmt)\
See also: [lang_dropview.html](lang_dropview.md)
#### expr:
Used by: [aggregate-function-invocation](#aggregate-function-invocation) [alter-table-stmt](#alter-table-stmt) [attach-stmt](#attach-stmt) [column-constraint](#column-constraint) [compound-select-stmt](#compound-select-stmt) [create-index-stmt](#create-index-stmt) [create-trigger-stmt](#create-trigger-stmt) [delete-stmt](#delete-stmt) [delete-stmt-limited](#delete-stmt-limited) [factored-select-stmt](#factored-select-stmt) [filter-clause](#filter-clause) [frame-spec](#frame-spec) [function-arguments](#function-arguments) [indexed-column](#indexed-column) [insert-stmt](#insert-stmt) [join-constraint](#join-constraint) [ordering-term](#ordering-term) [over-clause](#over-clause) [raise-function](#raise-function) [result-column](#result-column) [returning-clause](#returning-clause) [select-core](#select-core) [select-stmt](#select-stmt) [simple-function-invocation](#simple-function-invocation) [simple-select-stmt](#simple-select-stmt) [table-constraint](#table-constraint) [table-or-subquery](#table-or-subquery) [update-stmt](#update-stmt) [update-stmt-limited](#update-stmt-limited) [upsert-clause](#upsert-clause) [window-defn](#window-defn) [window-function-invocation](#window-function-invocation)\
References: [filter-clause](#filter-clause) [function-arguments](#function-arguments) [literal-value](#literal-value) [over-clause](#over-clause) [raise-function](#raise-function) [select-stmt](#select-stmt) [type-name](#type-name)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### factored-select-stmt:
\
References: [common-table-expression](#common-table-expression) [compound-operator](#compound-operator) [expr](#expr) [ordering-term](#ordering-term) [select-core](#select-core)\
See also: [lang_select.html](lang_select.md)
#### filter-clause:
Used by: [aggregate-function-invocation](#aggregate-function-invocation) [expr](#expr) [window-function-invocation](#window-function-invocation)\
References: [expr](#expr)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### foreign-key-clause:
Used by: [column-constraint](#column-constraint) [table-constraint](#table-constraint)\
See also: [lang_altertable.html](lang_altertable.md) [lang_altertable.html#altertabaddcol](lang_altertable.md#altertabaddcol) [lang_createtable.html](lang_createtable.md)
#### frame-spec:
Used by: [over-clause](#over-clause) [window-defn](#window-defn)\
References: [expr](#expr)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### function-arguments:
Used by: [expr](#expr)\
References: [expr](#expr) [ordering-term](#ordering-term)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### indexed-column:
Used by: [create-index-stmt](#create-index-stmt) [table-constraint](#table-constraint) [upsert-clause](#upsert-clause)\
References: [expr](#expr)\
See also: [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtable.html#primkeyconst](lang_createtable.md#primkeyconst) [lang_createtable.html#uniqueconst](lang_createtable.md#uniqueconst) [lang_createtrigger.html](lang_createtrigger.md) [lang_insert.html](lang_insert.md) [lang_upsert.html](lang_upsert.md) [partialindex.html](partialindex.md)
#### insert-stmt:
Used by: [create-trigger-stmt](#create-trigger-stmt) [sql-stmt](#sql-stmt)\
References: [common-table-expression](#common-table-expression) [expr](#expr) [returning-clause](#returning-clause) [select-stmt](#select-stmt) [upsert-clause](#upsert-clause)\
See also: [lang_createtrigger.html](lang_createtrigger.md) [lang_insert.html](lang_insert.md)
#### join-clause:
Used by: [select-core](#select-core) [select-stmt](#select-stmt) [table-or-subquery](#table-or-subquery) [update-stmt](#update-stmt) [update-stmt-limited](#update-stmt-limited)\
References: [join-constraint](#join-constraint) [join-operator](#join-operator) [table-or-subquery](#table-or-subquery)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### join-constraint:
Used by: [join-clause](#join-clause)\
References: [expr](#expr)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#fromclause](lang_select.md#fromclause) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### join-operator:
Used by: [join-clause](#join-clause)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#fromclause](lang_select.md#fromclause) [lang_select.html#nonstd](lang_select.md#nonstd) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### literal-value:
Used by: [column-constraint](#column-constraint) [expr](#expr)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### numeric-literal:
\
See also: [lang_expr.html#litvalue](lang_expr.md#litvalue)
#### ordering-term:
Used by: [aggregate-function-invocation](#aggregate-function-invocation) [compound-select-stmt](#compound-select-stmt) [delete-stmt-limited](#delete-stmt-limited) [factored-select-stmt](#factored-select-stmt) [function-arguments](#function-arguments) [over-clause](#over-clause) [select-stmt](#select-stmt) [simple-select-stmt](#simple-select-stmt) [update-stmt-limited](#update-stmt-limited) [window-defn](#window-defn)\
References: [expr](#expr)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### over-clause:
Used by: [expr](#expr)\
References: [expr](#expr) [frame-spec](#frame-spec) [ordering-term](#ordering-term)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### pragma-stmt:
Used by: [sql-stmt](#sql-stmt)\
References: [pragma-value](#pragma-value)\
See also: [pragma.html#syntax](pragma.md#syntax)
#### pragma-value:
Used by: [pragma-stmt](#pragma-stmt)\
References: [signed-number](#signed-number)\
See also: [pragma.html#syntax](pragma.md#syntax)
#### qualified-table-name:
Used by: [delete-stmt](#delete-stmt) [delete-stmt-limited](#delete-stmt-limited) [update-stmt](#update-stmt) [update-stmt-limited](#update-stmt-limited)\
See also: [lang_createtrigger.html](lang_createtrigger.md) [lang_delete.html](lang_delete.md) [lang_indexedby.html](lang_indexedby.md) [lang_update.html](lang_update.md)
#### raise-function:
Used by: [expr](#expr)\
References: [expr](#expr)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createtrigger.html#raise](lang_createtrigger.md#raise) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### recursive-cte:
\
References: [cte-table-name](#cte-table-name)\
See also: [lang_with.html#recursivecte](lang_with.md#recursivecte)
#### reindex-stmt:
Used by: [sql-stmt](#sql-stmt)\
See also: [lang_reindex.html](lang_reindex.md)
#### release-stmt:
Used by: [sql-stmt](#sql-stmt)\
See also: [lang_savepoint.html](lang_savepoint.md)
#### result-column:
Used by: [select-core](#select-core) [select-stmt](#select-stmt)\
References: [expr](#expr)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### returning-clause:
Used by: [delete-stmt](#delete-stmt) [delete-stmt-limited](#delete-stmt-limited) [insert-stmt](#insert-stmt) [update-stmt](#update-stmt) [update-stmt-limited](#update-stmt-limited)\
References: [expr](#expr)\
See also: [lang_createtrigger.html](lang_createtrigger.md) [lang_delete.html](lang_delete.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_update.html](lang_update.md)
#### rollback-stmt:
Used by: [sql-stmt](#sql-stmt)\
See also: [lang_savepoint.html](lang_savepoint.md) [lang_transaction.html](lang_transaction.md)
#### savepoint-stmt:
Used by: [sql-stmt](#sql-stmt)\
See also: [lang_savepoint.html](lang_savepoint.md)
#### select-core:
Used by: [compound-select-stmt](#compound-select-stmt) [factored-select-stmt](#factored-select-stmt) [simple-select-stmt](#simple-select-stmt)\
References: [expr](#expr) [join-clause](#join-clause) [result-column](#result-column) [table-or-subquery](#table-or-subquery) [window-defn](#window-defn)\
See also: [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect)
#### select-stmt:
Used by: [common-table-expression](#common-table-expression) [create-table-stmt](#create-table-stmt) [create-trigger-stmt](#create-trigger-stmt) [create-view-stmt](#create-view-stmt) [expr](#expr) [insert-stmt](#insert-stmt) [sql-stmt](#sql-stmt) [table-or-subquery](#table-or-subquery) [with-clause](#with-clause)\
References: [common-table-expression](#common-table-expression) [compound-operator](#compound-operator) [expr](#expr) [join-clause](#join-clause) [ordering-term](#ordering-term) [result-column](#result-column) [table-or-subquery](#table-or-subquery) [window-defn](#window-defn)\
See also: [changes.html#version_3_35_3](changes.md#version_3_35_3) [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [lang_with.html#recursivecte](lang_with.md#recursivecte) [partialindex.html](partialindex.md) [releaselog/3_35_3.html](releaselog/3_35_3.md) [releaselog/3_35_4.html](releaselog/3_35_4.md) [releaselog/3_35_5.html](releaselog/3_35_5.md)
#### signed-number:
Used by: [column-constraint](#column-constraint) [pragma-value](#pragma-value) [type-name](#type-name)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md) [pragma.html#syntax](pragma.md#syntax)
#### simple-function-invocation:
\
References: [expr](#expr)\
See also: [lang_corefunc.html](lang_corefunc.md) [lang_expr.html#\*funcinexpr](lang_expr.md#*funcinexpr)
#### simple-select-stmt:
\
References: [common-table-expression](#common-table-expression) [expr](#expr) [ordering-term](#ordering-term) [select-core](#select-core)\
See also: [lang_select.html#simpleselect](lang_select.md#simpleselect)
#### sql-stmt:
Used by: [sql-stmt-list](#sql-stmt-list)\
References: [alter-table-stmt](#alter-table-stmt) [analyze-stmt](#analyze-stmt) [attach-stmt](#attach-stmt) [begin-stmt](#begin-stmt) [commit-stmt](#commit-stmt) [create-index-stmt](#create-index-stmt) [create-table-stmt](#create-table-stmt) [create-trigger-stmt](#create-trigger-stmt) [create-view-stmt](#create-view-stmt) [create-virtual-table-stmt](#create-virtual-table-stmt) [delete-stmt](#delete-stmt) [delete-stmt-limited](#delete-stmt-limited) [detach-stmt](#detach-stmt) [drop-index-stmt](#drop-index-stmt) [drop-table-stmt](#drop-table-stmt) [drop-trigger-stmt](#drop-trigger-stmt) [drop-view-stmt](#drop-view-stmt) [insert-stmt](#insert-stmt) [pragma-stmt](#pragma-stmt) [reindex-stmt](#reindex-stmt) [release-stmt](#release-stmt) [rollback-stmt](#rollback-stmt) [savepoint-stmt](#savepoint-stmt) [select-stmt](#select-stmt) [update-stmt](#update-stmt) [update-stmt-limited](#update-stmt-limited) [vacuum-stmt](#vacuum-stmt)\
See also: [lang.html](lang.md) [lang_explain.html](lang_explain.md)
#### sql-stmt-list:
\
References: [sql-stmt](#sql-stmt)\
See also: [lang.html](lang.md)
#### table-constraint:
Used by: [create-table-stmt](#create-table-stmt)\
References: [conflict-clause](#conflict-clause) [expr](#expr) [foreign-key-clause](#foreign-key-clause) [indexed-column](#indexed-column)\
See also: [lang_createtable.html](lang_createtable.md) [lang_createtable.html#primkeyconst](lang_createtable.md#primkeyconst) [lang_createtable.html#tablecoldef](lang_createtable.md#tablecoldef) [lang_createtable.html#uniqueconst](lang_createtable.md#uniqueconst)
#### table-options:
Used by: [create-table-stmt](#create-table-stmt)\
See also: [lang_createtable.html](lang_createtable.md)
#### table-or-subquery:
Used by: [join-clause](#join-clause) [select-core](#select-core) [select-stmt](#select-stmt) [update-stmt](#update-stmt) [update-stmt-limited](#update-stmt-limited)\
References: [expr](#expr) [join-clause](#join-clause) [select-stmt](#select-stmt)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### type-name:
Used by: [column-def](#column-def) [expr](#expr)\
References: [signed-number](#signed-number)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### update-stmt:
Used by: [create-trigger-stmt](#create-trigger-stmt) [sql-stmt](#sql-stmt)\
References: [column-name-list](#column-name-list) [common-table-expression](#common-table-expression) [expr](#expr) [join-clause](#join-clause) [qualified-table-name](#qualified-table-name) [returning-clause](#returning-clause) [table-or-subquery](#table-or-subquery)\
See also: [lang_createtrigger.html](lang_createtrigger.md) [lang_update.html](lang_update.md)
#### update-stmt-limited:
Used by: [sql-stmt](#sql-stmt)\
References: [column-name-list](#column-name-list) [common-table-expression](#common-table-expression) [expr](#expr) [join-clause](#join-clause) [ordering-term](#ordering-term) [qualified-table-name](#qualified-table-name) [returning-clause](#returning-clause) [table-or-subquery](#table-or-subquery)\
See also: [lang_update.html#upfrom](lang_update.md#upfrom)
#### upsert-clause:
Used by: [insert-stmt](#insert-stmt)\
References: [column-name-list](#column-name-list) [expr](#expr) [indexed-column](#indexed-column)\
See also: [lang_createtrigger.html](lang_createtrigger.md) [lang_insert.html](lang_insert.md) [lang_upsert.html](lang_upsert.md)
#### vacuum-stmt:
Used by: [sql-stmt](#sql-stmt)\
See also: [lang_vacuum.html](lang_vacuum.md)
#### window-defn:
Used by: [select-core](#select-core) [select-stmt](#select-stmt) [window-function-invocation](#window-function-invocation)\
References: [expr](#expr) [frame-spec](#frame-spec) [ordering-term](#ordering-term)\
See also: [lang_aggfunc.html](lang_aggfunc.md) [lang_altertable.html](lang_altertable.md) [lang_attach.html](lang_attach.md) [lang_createindex.html](lang_createindex.md) [lang_createtable.html](lang_createtable.md) [lang_createtrigger.html](lang_createtrigger.md) [lang_createview.html](lang_createview.md) [lang_delete.html](lang_delete.md) [lang_expr.html](lang_expr.md) [lang_insert.html](lang_insert.md) [lang_returning.html](lang_returning.md) [lang_select.html](lang_select.md) [lang_select.html#compound](lang_select.md#compound) [lang_select.html#simpleselect](lang_select.md#simpleselect) [lang_update.html](lang_update.md) [lang_upsert.html](lang_upsert.md) [lang_with.html](lang_with.md) [partialindex.html](partialindex.md)
#### window-function-invocation:
\
References: [expr](#expr) [filter-clause](#filter-clause) [window-defn](#window-defn)\
See also: [lang_expr.html#\*funcinexpr](lang_expr.md#*funcinexpr)
#### with-clause:
\
References: [cte-table-name](#cte-table-name) [select-stmt](#select-stmt)\
See also: [lang_with.html](lang_with.md)
---
# C/C++ Interface For SQLite Version 3
*Sección: Tools Extensions | Origen: https://www.sqlite.org/capi3ref.html*
# C-language Interface Specification for SQLite
This page is intended to be a precise and detailed specification. For a tutorial introduction, see instead:
- [SQLite In 3 Minutes Or Less](quickstart.md) and/or
- the [Introduction To The SQLite C/C++ Interface](cintro.md).
This same content is also available split out into [some smaller pages](../c3ref/intro.md).
------------------------------------------------------------------------
## Experimental And Deprecated Interfaces
SQLite interfaces can be subdivided into three categories:
1. Stable
2. Experimental
3. Deprecated
Stable interfaces will be maintained indefinitely in a backwards compatible way. An application that uses only stable interfaces should always be able to relink against a newer version of SQLite without any changes.
Experimental interfaces are subject to change. Applications that use experimental interfaces may need to be modified when upgrading to a newer SQLite release, though this is rare. When new interfaces are added to SQLite, they generally begin as experimental interfaces. After an interface has been in use for a while and the developers are confident that the design of the interface is sound and worthy of long-term support, the interface is marked as stable.
Deprecated interfaces have been superseded by better methods of accomplishing the same thing and should be avoided in new applications. Deprecated interfaces continue to be supported for the sake of backwards compatibility. At some point in the future, it is possible that deprecated interfaces may be removed.
Key points:
- Experimental interfaces are subject to change and/or removal at any time.
- Deprecated interfaces should not be used in new code and might be removed in some future release.
------------------------------------------------------------------------
## List Of Objects:
- [sqlite3](#sqlite3)
- [sqlite3_api_routines](#sqlite3_api_routines)
- [sqlite3_backup](#sqlite3_backup)
- [sqlite3_blob](#sqlite3_blob)
- [sqlite3_context](#sqlite3_context)
- [sqlite3_data_directory](#sqlite3_data_directory)
- [sqlite3_file](#sqlite3_file)
- [sqlite3_filename](#sqlite3_filename)
- [sqlite3_index_info](#sqlite3_index_info)
- [sqlite3_int64](#sqlite3_int64)
- [sqlite3_uint64](#sqlite3_int64)
- [sqlite_int64](#sqlite3_int64)
- [sqlite_uint64](#sqlite3_int64)
- [sqlite3_io_methods](#sqlite3_io_methods)
- [sqlite3_mem_methods](#sqlite3_mem_methods)
- [sqlite3_module](#sqlite3_module)
- [sqlite3_mutex](#sqlite3_mutex)
- [sqlite3_mutex_methods](#sqlite3_mutex_methods)
- [sqlite3_pcache](#sqlite3_pcache)
- [sqlite3_pcache_methods2](#sqlite3_pcache_methods2)
- [sqlite3_pcache_page](#sqlite3_pcache_page)
- [sqlite3_snapshot](#sqlite3_snapshot)
- [sqlite3_stmt](#sqlite3_stmt)
- [sqlite3_str](#sqlite3_str)
- [sqlite3_temp_directory](#sqlite3_temp_directory)
- [sqlite3_value](#sqlite3_value)
- [sqlite3_vfs](#sqlite3_vfs)
- [sqlite3_vtab](#sqlite3_vtab)
- [sqlite3_vtab_cursor](#sqlite3_vtab_cursor)
------------------------------------------------------------------------
## List Of Constants:
Also available: [list of error codes](rescode.md)
- [SQLITE_ABORT](#SQLITE_ABORT)
- [SQLITE_ABORT_ROLLBACK](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_ACCESS_EXISTS](#SQLITE_ACCESS_EXISTS)
- [SQLITE_ACCESS_READ](#SQLITE_ACCESS_EXISTS)
- [SQLITE_ACCESS_READWRITE](#SQLITE_ACCESS_EXISTS)
- [SQLITE_ALTER_TABLE](#SQLITE_ALTER_TABLE)
- [SQLITE_ANALYZE](#SQLITE_ALTER_TABLE)
- [SQLITE_ANY](#sqliteany)
- [SQLITE_ATTACH](#SQLITE_ALTER_TABLE)
- [SQLITE_AUTH](#SQLITE_ABORT)
- [SQLITE_AUTH_USER](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_BLOB](#SQLITE_BLOB)
- [SQLITE_BUSY](#SQLITE_ABORT)
- [SQLITE_BUSY_RECOVERY](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_BUSY_SNAPSHOT](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_BUSY_TIMEOUT](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CANTOPEN](#SQLITE_ABORT)
- [SQLITE_CANTOPEN_CONVPATH](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CANTOPEN_DIRTYWAL](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CANTOPEN_FULLPATH](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CANTOPEN_ISDIR](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CANTOPEN_NOTEMPDIR](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CANTOPEN_SYMLINK](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CARRAY_BLOB](#SQLITE_CARRAY_BLOB)
- [SQLITE_CARRAY_DOUBLE](#SQLITE_CARRAY_BLOB)
- [SQLITE_CARRAY_INT32](#SQLITE_CARRAY_BLOB)
- [SQLITE_CARRAY_INT64](#SQLITE_CARRAY_BLOB)
- [SQLITE_CARRAY_TEXT](#SQLITE_CARRAY_BLOB)
- [SQLITE_CHECKPOINT_FULL](#SQLITE_CHECKPOINT_FULL)
- [SQLITE_CHECKPOINT_NOOP](#SQLITE_CHECKPOINT_FULL)
- [SQLITE_CHECKPOINT_PASSIVE](#SQLITE_CHECKPOINT_FULL)
- [SQLITE_CHECKPOINT_RESTART](#SQLITE_CHECKPOINT_FULL)
- [SQLITE_CHECKPOINT_TRUNCATE](#SQLITE_CHECKPOINT_FULL)
- [SQLITE_CONFIG_COVERING_INDEX_SCAN](#sqliteconfigcoveringindexscan)
- [SQLITE_CONFIG_GETMALLOC](#sqliteconfiggetmalloc)
- [SQLITE_CONFIG_GETMUTEX](#sqliteconfiggetmutex)
- [SQLITE_CONFIG_GETPCACHE](#sqliteconfiggetpcache)
- [SQLITE_CONFIG_GETPCACHE2](#sqliteconfiggetpcache2)
- [SQLITE_CONFIG_HEAP](#sqliteconfigheap)
- [SQLITE_CONFIG_LOG](#sqliteconfiglog)
- [SQLITE_CONFIG_LOOKASIDE](#sqliteconfiglookaside)
- [SQLITE_CONFIG_MALLOC](#sqliteconfigmalloc)
- [SQLITE_CONFIG_MEMDB_MAXSIZE](#sqliteconfigmemdbmaxsize)
- [SQLITE_CONFIG_MEMSTATUS](#sqliteconfigmemstatus)
- [SQLITE_CONFIG_MMAP_SIZE](#sqliteconfigmmapsize)
- [SQLITE_CONFIG_MULTITHREAD](#sqliteconfigmultithread)
- [SQLITE_CONFIG_MUTEX](#sqliteconfigmutex)
- [SQLITE_CONFIG_PAGECACHE](#sqliteconfigpagecache)
- [SQLITE_CONFIG_PCACHE](#sqliteconfigpcache)
- [SQLITE_CONFIG_PCACHE2](#sqliteconfigpcache2)
- [SQLITE_CONFIG_PCACHE_HDRSZ](#sqliteconfigpcachehdrsz)
- [SQLITE_CONFIG_PMASZ](#sqliteconfigpmasz)
- [SQLITE_CONFIG_ROWID_IN_VIEW](#sqliteconfigrowidinview)
- [SQLITE_CONFIG_SCRATCH](#sqliteconfigscratch)
- [SQLITE_CONFIG_SERIALIZED](#sqliteconfigserialized)
- [SQLITE_CONFIG_SINGLETHREAD](#sqliteconfigsinglethread)
- [SQLITE_CONFIG_SMALL_MALLOC](#sqliteconfigsmallmalloc)
- [SQLITE_CONFIG_SORTERREF_SIZE](#sqliteconfigsorterrefsize)
- [SQLITE_CONFIG_SQLLOG](#sqliteconfigsqllog)
- [SQLITE_CONFIG_STMTJRNL_SPILL](#sqliteconfigstmtjrnlspill)
- [SQLITE_CONFIG_URI](#sqliteconfiguri)
- [SQLITE_CONFIG_WIN32_HEAPSIZE](#sqliteconfigwin32heapsize)
- [SQLITE_CONSTRAINT](#SQLITE_ABORT)
- [SQLITE_CONSTRAINT_CHECK](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CONSTRAINT_COMMITHOOK](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CONSTRAINT_DATATYPE](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CONSTRAINT_FOREIGNKEY](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CONSTRAINT_FUNCTION](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CONSTRAINT_NOTNULL](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CONSTRAINT_PINNED](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CONSTRAINT_PRIMARYKEY](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CONSTRAINT_ROWID](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CONSTRAINT_TRIGGER](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CONSTRAINT_UNIQUE](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CONSTRAINT_VTAB](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_COPY](#SQLITE_ALTER_TABLE)
- [SQLITE_CORRUPT](#SQLITE_ABORT)
- [SQLITE_CORRUPT_INDEX](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CORRUPT_SEQUENCE](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CORRUPT_VTAB](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_CREATE_INDEX](#SQLITE_ALTER_TABLE)
- [SQLITE_CREATE_TABLE](#SQLITE_ALTER_TABLE)
- [SQLITE_CREATE_TEMP_INDEX](#SQLITE_ALTER_TABLE)
- [SQLITE_CREATE_TEMP_TABLE](#SQLITE_ALTER_TABLE)
- [SQLITE_CREATE_TEMP_TRIGGER](#SQLITE_ALTER_TABLE)
- [SQLITE_CREATE_TEMP_VIEW](#SQLITE_ALTER_TABLE)
- [SQLITE_CREATE_TRIGGER](#SQLITE_ALTER_TABLE)
- [SQLITE_CREATE_VIEW](#SQLITE_ALTER_TABLE)
- [SQLITE_CREATE_VTABLE](#SQLITE_ALTER_TABLE)
- [SQLITE_DBCONFIG_DEFENSIVE](#sqlitedbconfigdefensive)
- [SQLITE_DBCONFIG_DQS_DDL](#sqlitedbconfigdqsddl)
- [SQLITE_DBCONFIG_DQS_DML](#sqlitedbconfigdqsdml)
- [SQLITE_DBCONFIG_ENABLE_ATTACH_CREATE](#sqlitedbconfigenableattachcreate)
- [SQLITE_DBCONFIG_ENABLE_ATTACH_WRITE](#sqlitedbconfigenableattachwrite)
- [SQLITE_DBCONFIG_ENABLE_COMMENTS](#sqlitedbconfigenablecomments)
- [SQLITE_DBCONFIG_ENABLE_FKEY](#sqlitedbconfigenablefkey)
- [SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER](#sqlitedbconfigenablefts3tokenizer)
- [SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION](#sqlitedbconfigenableloadextension)
- [SQLITE_DBCONFIG_ENABLE_QPSG](#sqlitedbconfigenableqpsg)
- [SQLITE_DBCONFIG_ENABLE_TRIGGER](#sqlitedbconfigenabletrigger)
- [SQLITE_DBCONFIG_ENABLE_VIEW](#sqlitedbconfigenableview)
- [SQLITE_DBCONFIG_FP_DIGITS](#sqlitedbconfigfpdigits)
- [SQLITE_DBCONFIG_LEGACY_ALTER_TABLE](#sqlitedbconfiglegacyaltertable)
- [SQLITE_DBCONFIG_LEGACY_FILE_FORMAT](#sqlitedbconfiglegacyfileformat)
- [SQLITE_DBCONFIG_LOOKASIDE](#sqlitedbconfiglookaside)
- [SQLITE_DBCONFIG_MAINDBNAME](#sqlitedbconfigmaindbname)
- [SQLITE_DBCONFIG_MAX](#SQLITE_DBCONFIG_DEFENSIVE)
- [SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE](#sqlitedbconfignockptonclose)
- [SQLITE_DBCONFIG_RESET_DATABASE](#sqlitedbconfigresetdatabase)
- [SQLITE_DBCONFIG_REVERSE_SCANORDER](#sqlitedbconfigreversescanorder)
- [SQLITE_DBCONFIG_STMT_SCANSTATUS](#sqlitedbconfigstmtscanstatus)
- [SQLITE_DBCONFIG_TRIGGER_EQP](#sqlitedbconfigtriggereqp)
- [SQLITE_DBCONFIG_TRUSTED_SCHEMA](#sqlitedbconfigtrustedschema)
- [SQLITE_DBCONFIG_WRITABLE_SCHEMA](#sqlitedbconfigwritableschema)
- [SQLITE_DBSTATUS_CACHE_HIT](#sqlitedbstatuscachehit)
- [SQLITE_DBSTATUS_CACHE_MISS](#sqlitedbstatuscachemiss)
- [SQLITE_DBSTATUS_CACHE_SPILL](#sqlitedbstatuscachespill)
- [SQLITE_DBSTATUS_CACHE_USED](#sqlitedbstatuscacheused)
- [SQLITE_DBSTATUS_CACHE_USED_SHARED](#sqlitedbstatuscacheusedshared)
- [SQLITE_DBSTATUS_CACHE_WRITE](#sqlitedbstatuscachewrite)
- [SQLITE_DBSTATUS_DEFERRED_FKS](#sqlitedbstatusdeferredfks)
- [SQLITE_DBSTATUS_LOOKASIDE_HIT](#sqlitedbstatuslookasidehit)
- [SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL](#sqlitedbstatuslookasidemissfull)
- [SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE](#sqlitedbstatuslookasidemisssize)
- [SQLITE_DBSTATUS_LOOKASIDE_USED](#sqlitedbstatuslookasideused)
- [SQLITE_DBSTATUS_MAX](#SQLITE_DBSTATUS%20options)
- [SQLITE_DBSTATUS_SCHEMA_USED](#sqlitedbstatusschemaused)
- [SQLITE_DBSTATUS_STMT_USED](#sqlitedbstatusstmtused)
- [SQLITE_DBSTATUS_TEMPBUF_SPILL](#SQLITE_DBSTATUS%20options)
- [SQLITE_DELETE](#SQLITE_ALTER_TABLE)
- [SQLITE_DENY](#SQLITE_DENY)
- [SQLITE_DESERIALIZE_FREEONCLOSE](#SQLITE_DESERIALIZE_FREEONCLOSE)
- [SQLITE_DESERIALIZE_READONLY](#SQLITE_DESERIALIZE_FREEONCLOSE)
- [SQLITE_DESERIALIZE_RESIZEABLE](#SQLITE_DESERIALIZE_FREEONCLOSE)
- [SQLITE_DETACH](#SQLITE_ALTER_TABLE)
- [SQLITE_DETERMINISTIC](#sqlitedeterministic)
- [SQLITE_DIRECTONLY](#sqlitedirectonly)
- [SQLITE_DONE](#SQLITE_ABORT)
- [SQLITE_DROP_INDEX](#SQLITE_ALTER_TABLE)
- [SQLITE_DROP_TABLE](#SQLITE_ALTER_TABLE)
- [SQLITE_DROP_TEMP_INDEX](#SQLITE_ALTER_TABLE)
- [SQLITE_DROP_TEMP_TABLE](#SQLITE_ALTER_TABLE)
- [SQLITE_DROP_TEMP_TRIGGER](#SQLITE_ALTER_TABLE)
- [SQLITE_DROP_TEMP_VIEW](#SQLITE_ALTER_TABLE)
- [SQLITE_DROP_TRIGGER](#SQLITE_ALTER_TABLE)
- [SQLITE_DROP_VIEW](#SQLITE_ALTER_TABLE)
- [SQLITE_DROP_VTABLE](#SQLITE_ALTER_TABLE)
- [SQLITE_EMPTY](#SQLITE_ABORT)
- [SQLITE_ERROR](#SQLITE_ABORT)
- [SQLITE_ERROR_KEY](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_ERROR_MISSING_COLLSEQ](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_ERROR_RESERVESIZE](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_ERROR_RETRY](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_ERROR_SNAPSHOT](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_ERROR_UNABLE](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_FAIL](#SQLITE_FAIL)
- [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE](#sqlitefcntlbeginatomicwrite)
- [SQLITE_FCNTL_BLOCK_ON_CONNECT](#sqlitefcntlblockonconnect)
- [SQLITE_FCNTL_BUSYHANDLER](#sqlitefcntlbusyhandler)
- [SQLITE_FCNTL_CHUNK_SIZE](#sqlitefcntlchunksize)
- [SQLITE_FCNTL_CKPT_DONE](#sqlitefcntlckptdone)
- [SQLITE_FCNTL_CKPT_START](#sqlitefcntlckptstart)
- [SQLITE_FCNTL_CKSM_FILE](#sqlitefcntlcksmfile)
- [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE](#sqlitefcntlcommitatomicwrite)
- [SQLITE_FCNTL_COMMIT_PHASETWO](#sqlitefcntlcommitphasetwo)
- [SQLITE_FCNTL_DATA_VERSION](#sqlitefcntldataversion)
- [SQLITE_FCNTL_EXTERNAL_READER](#sqlitefcntlexternalreader)
- [SQLITE_FCNTL_FILESTAT](#sqlitefcntlfilestat)
- [SQLITE_FCNTL_FILE_POINTER](#sqlitefcntlfilepointer)
- [SQLITE_FCNTL_GET_LOCKPROXYFILE](#SQLITE_FCNTL_BEGIN_ATOMIC_WRITE)
- [SQLITE_FCNTL_HAS_MOVED](#sqlitefcntlhasmoved)
- [SQLITE_FCNTL_JOURNAL_POINTER](#sqlitefcntljournalpointer)
- [SQLITE_FCNTL_LAST_ERRNO](#SQLITE_FCNTL_BEGIN_ATOMIC_WRITE)
- [SQLITE_FCNTL_LOCKSTATE](#sqlitefcntllockstate)
- [SQLITE_FCNTL_LOCK_TIMEOUT](#sqlitefcntllocktimeout)
- [SQLITE_FCNTL_MMAP_SIZE](#sqlitefcntlmmapsize)
- [SQLITE_FCNTL_NULL_IO](#sqlitefcntlnullio)
- [SQLITE_FCNTL_OVERWRITE](#sqlitefcntloverwrite)
- [SQLITE_FCNTL_PDB](#SQLITE_FCNTL_BEGIN_ATOMIC_WRITE)
- [SQLITE_FCNTL_PERSIST_WAL](#sqlitefcntlpersistwal)
- [SQLITE_FCNTL_POWERSAFE_OVERWRITE](#sqlitefcntlpowersafeoverwrite)
- [SQLITE_FCNTL_PRAGMA](#sqlitefcntlpragma)
- [SQLITE_FCNTL_RBU](#sqlitefcntlrbu)
- [SQLITE_FCNTL_RESERVE_BYTES](#SQLITE_FCNTL_BEGIN_ATOMIC_WRITE)
- [SQLITE_FCNTL_RESET_CACHE](#sqlitefcntlresetcache)
- [SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE](#sqlitefcntlrollbackatomicwrite)
- [SQLITE_FCNTL_SET_LOCKPROXYFILE](#SQLITE_FCNTL_BEGIN_ATOMIC_WRITE)
- [SQLITE_FCNTL_SIZE_HINT](#sqlitefcntlsizehint)
- [SQLITE_FCNTL_SIZE_LIMIT](#sqlitefcntlsizelimit)
- [SQLITE_FCNTL_SYNC](#sqlitefcntlsync)
- [SQLITE_FCNTL_SYNC_OMITTED](#sqlitefcntlsyncomitted)
- [SQLITE_FCNTL_TEMPFILENAME](#sqlitefcntltempfilename)
- [SQLITE_FCNTL_TRACE](#sqlitefcntltrace)
- [SQLITE_FCNTL_VFSNAME](#sqlitefcntlvfsname)
- [SQLITE_FCNTL_VFS_POINTER](#sqlitefcntlvfspointer)
- [SQLITE_FCNTL_WAL_BLOCK](#sqlitefcntlwalblock)
- [SQLITE_FCNTL_WIN32_AV_RETRY](#sqlitefcntlwin32avretry)
- [SQLITE_FCNTL_WIN32_GET_HANDLE](#sqlitefcntlwin32gethandle)
- [SQLITE_FCNTL_WIN32_SET_HANDLE](#sqlitefcntlwin32sethandle)
- [SQLITE_FCNTL_ZIPVFS](#sqlitefcntlzipvfs)
- [SQLITE_FLOAT](#SQLITE_BLOB)
- [SQLITE_FORMAT](#SQLITE_ABORT)
- [SQLITE_FULL](#SQLITE_ABORT)
- [SQLITE_FUNCTION](#SQLITE_ALTER_TABLE)
- [SQLITE_IGNORE](#SQLITE_DENY)
- [SQLITE_INDEX_CONSTRAINT_EQ](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_CONSTRAINT_FUNCTION](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_CONSTRAINT_GE](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_CONSTRAINT_GLOB](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_CONSTRAINT_GT](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_CONSTRAINT_IS](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_CONSTRAINT_ISNOT](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_CONSTRAINT_ISNOTNULL](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_CONSTRAINT_ISNULL](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_CONSTRAINT_LE](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_CONSTRAINT_LIKE](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_CONSTRAINT_LIMIT](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_CONSTRAINT_LT](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_CONSTRAINT_MATCH](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_CONSTRAINT_NE](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_CONSTRAINT_OFFSET](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_CONSTRAINT_REGEXP](#SQLITE_INDEX_CONSTRAINT_EQ)
- [SQLITE_INDEX_SCAN_HEX](#SQLITE_INDEX_SCAN_HEX)
- [SQLITE_INDEX_SCAN_UNIQUE](#SQLITE_INDEX_SCAN_HEX)
- [SQLITE_INNOCUOUS](#sqliteinnocuous)
- [SQLITE_INSERT](#SQLITE_ALTER_TABLE)
- [SQLITE_INTEGER](#SQLITE_BLOB)
- [SQLITE_INTERNAL](#SQLITE_ABORT)
- [SQLITE_INTERRUPT](#SQLITE_ABORT)
- [SQLITE_IOCAP_ATOMIC](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_ATOMIC16K](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_ATOMIC1K](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_ATOMIC2K](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_ATOMIC32K](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_ATOMIC4K](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_ATOMIC512](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_ATOMIC64K](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_ATOMIC8K](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_BATCH_ATOMIC](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_IMMUTABLE](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_POWERSAFE_OVERWRITE](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_SAFE_APPEND](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_SEQUENTIAL](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_SUBPAGE_READ](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOERR](#SQLITE_ABORT)
- [SQLITE_IOERR_ACCESS](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_AUTH](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_BADKEY](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_BEGIN_ATOMIC](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_BLOCKED](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_CHECKRESERVEDLOCK](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_CLOSE](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_CODEC](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_COMMIT_ATOMIC](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_CONVPATH](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_CORRUPTFS](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_DATA](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_DELETE](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_DELETE_NOENT](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_DIR_CLOSE](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_DIR_FSYNC](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_FSTAT](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_FSYNC](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_GETTEMPPATH](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_IN_PAGE](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_LOCK](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_MMAP](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_NOMEM](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_RDLOCK](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_READ](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_ROLLBACK_ATOMIC](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_SEEK](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_SHMLOCK](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_SHMMAP](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_SHMOPEN](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_SHMSIZE](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_SHORT_READ](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_TRUNCATE](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_UNLOCK](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_VNODE](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_IOERR_WRITE](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_LIMIT_ATTACHED](#sqlitelimitattached)
- [SQLITE_LIMIT_COLUMN](#sqlitelimitcolumn)
- [SQLITE_LIMIT_COMPOUND_SELECT](#sqlitelimitcompoundselect)
- [SQLITE_LIMIT_EXPR_DEPTH](#sqlitelimitexprdepth)
- [SQLITE_LIMIT_FUNCTION_ARG](#sqlitelimitfunctionarg)
- [SQLITE_LIMIT_LENGTH](#sqlitelimitlength)
- [SQLITE_LIMIT_LIKE_PATTERN_LENGTH](#sqlitelimitlikepatternlength)
- [SQLITE_LIMIT_PARSER_DEPTH](#sqlitelimitparserdepth)
- [SQLITE_LIMIT_SQL_LENGTH](#sqlitelimitsqllength)
- [SQLITE_LIMIT_TRIGGER_DEPTH](#sqlitelimittriggerdepth)
- [SQLITE_LIMIT_VARIABLE_NUMBER](#sqlitelimitvariablenumber)
- [SQLITE_LIMIT_VDBE_OP](#sqlitelimitvdbeop)
- [SQLITE_LIMIT_WORKER_THREADS](#sqlitelimitworkerthreads)
- [SQLITE_LOCKED](#SQLITE_ABORT)
- [SQLITE_LOCKED_SHAREDCACHE](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_LOCKED_VTAB](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_LOCK_EXCLUSIVE](#SQLITE_LOCK_EXCLUSIVE)
- [SQLITE_LOCK_NONE](#SQLITE_LOCK_EXCLUSIVE)
- [SQLITE_LOCK_PENDING](#SQLITE_LOCK_EXCLUSIVE)
- [SQLITE_LOCK_RESERVED](#SQLITE_LOCK_EXCLUSIVE)
- [SQLITE_LOCK_SHARED](#SQLITE_LOCK_EXCLUSIVE)
- [SQLITE_MISMATCH](#SQLITE_ABORT)
- [SQLITE_MISUSE](#SQLITE_ABORT)
- [SQLITE_MUTEX_FAST](#SQLITE_MUTEX_FAST)
- [SQLITE_MUTEX_RECURSIVE](#SQLITE_MUTEX_FAST)
- [SQLITE_MUTEX_STATIC_APP1](#SQLITE_MUTEX_FAST)
- [SQLITE_MUTEX_STATIC_APP2](#SQLITE_MUTEX_FAST)
- [SQLITE_MUTEX_STATIC_APP3](#SQLITE_MUTEX_FAST)
- [SQLITE_MUTEX_STATIC_LRU](#SQLITE_MUTEX_FAST)
- [SQLITE_MUTEX_STATIC_LRU2](#SQLITE_MUTEX_FAST)
- [SQLITE_MUTEX_STATIC_MAIN](#SQLITE_MUTEX_FAST)
- [SQLITE_MUTEX_STATIC_MEM](#SQLITE_MUTEX_FAST)
- [SQLITE_MUTEX_STATIC_MEM2](#SQLITE_MUTEX_FAST)
- [SQLITE_MUTEX_STATIC_OPEN](#SQLITE_MUTEX_FAST)
- [SQLITE_MUTEX_STATIC_PMEM](#SQLITE_MUTEX_FAST)
- [SQLITE_MUTEX_STATIC_PRNG](#SQLITE_MUTEX_FAST)
- [SQLITE_MUTEX_STATIC_VFS1](#SQLITE_MUTEX_FAST)
- [SQLITE_MUTEX_STATIC_VFS2](#SQLITE_MUTEX_FAST)
- [SQLITE_MUTEX_STATIC_VFS3](#SQLITE_MUTEX_FAST)
- [SQLITE_NOLFS](#SQLITE_ABORT)
- [SQLITE_NOMEM](#SQLITE_ABORT)
- [SQLITE_NOTADB](#SQLITE_ABORT)
- [SQLITE_NOTFOUND](#SQLITE_ABORT)
- [SQLITE_NOTICE](#SQLITE_ABORT)
- [SQLITE_NOTICE_RBU](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_NOTICE_RECOVER_ROLLBACK](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_NOTICE_RECOVER_WAL](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_NULL](#SQLITE_BLOB)
- [SQLITE_OK](#SQLITE_ABORT)
- [SQLITE_OK_LOAD_PERMANENTLY](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_OK_SYMLINK](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_OPEN_AUTOPROXY](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_CREATE](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_DELETEONCLOSE](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_EXCLUSIVE](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_EXRESCODE](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_FULLMUTEX](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_MAIN_DB](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_MAIN_JOURNAL](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_MEMORY](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_NOFOLLOW](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_NOMUTEX](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_PRIVATECACHE](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_READONLY](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_READWRITE](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_SHAREDCACHE](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_SUBJOURNAL](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_SUPER_JOURNAL](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_TEMP_DB](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_TEMP_JOURNAL](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_TRANSIENT_DB](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_URI](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_WAL](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_PERM](#SQLITE_ABORT)
- [SQLITE_PRAGMA](#SQLITE_ALTER_TABLE)
- [SQLITE_PREPARE_DONT_LOG](#sqlitepreparedontlog)
- [SQLITE_PREPARE_FROM_DDL](#sqlitepreparefromddl)
- [SQLITE_PREPARE_NORMALIZE](#sqlitepreparenormalize)
- [SQLITE_PREPARE_NO_VTAB](#sqlitepreparenovtab)
- [SQLITE_PREPARE_PERSISTENT](#sqlitepreparepersistent)
- [SQLITE_PROTOCOL](#SQLITE_ABORT)
- [SQLITE_RANGE](#SQLITE_ABORT)
- [SQLITE_READ](#SQLITE_ALTER_TABLE)
- [SQLITE_READONLY](#SQLITE_ABORT)
- [SQLITE_READONLY_CANTINIT](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_READONLY_CANTLOCK](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_READONLY_DBMOVED](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_READONLY_DIRECTORY](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_READONLY_RECOVERY](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_READONLY_ROLLBACK](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_RECURSIVE](#SQLITE_ALTER_TABLE)
- [SQLITE_REINDEX](#SQLITE_ALTER_TABLE)
- [SQLITE_REPLACE](#SQLITE_FAIL)
- [SQLITE_RESULT_SUBTYPE](#sqliteresultsubtype)
- [SQLITE_ROLLBACK](#SQLITE_FAIL)
- [SQLITE_ROW](#SQLITE_ABORT)
- [SQLITE_SAVEPOINT](#SQLITE_ALTER_TABLE)
- [SQLITE_SCANSTAT_COMPLEX](#SQLITE_SCANSTAT_COMPLEX)
- [SQLITE_SCANSTAT_EST](#sqlitescanstatest)
- [SQLITE_SCANSTAT_EXPLAIN](#sqlitescanstatexplain)
- [SQLITE_SCANSTAT_NAME](#sqlitescanstatname)
- [SQLITE_SCANSTAT_NCYCLE](#sqlitescanstatncycle)
- [SQLITE_SCANSTAT_NLOOP](#sqlitescanstatnloop)
- [SQLITE_SCANSTAT_NVISIT](#sqlitescanstatnvisit)
- [SQLITE_SCANSTAT_PARENTID](#sqlitescanstatparentid)
- [SQLITE_SCANSTAT_SELECTID](#sqlitescanstatselectid)
- [SQLITE_SCHEMA](#SQLITE_ABORT)
- [SQLITE_SCM_BRANCH](#SQLITE_SCM_BRANCH)
- [SQLITE_SCM_DATETIME](#SQLITE_SCM_BRANCH)
- [SQLITE_SCM_TAGS](#SQLITE_SCM_BRANCH)
- [SQLITE_SELECT](#SQLITE_ALTER_TABLE)
- [SQLITE_SELFORDER1](#sqliteselforder1)
- [SQLITE_SERIALIZE_NOCOPY](#SQLITE_SERIALIZE_NOCOPY)
- [SQLITE_SETLK_BLOCK_ON_CONNECT](#SQLITE_SETLK_BLOCK_ON_CONNECT)
- [SQLITE_SHM_EXCLUSIVE](#SQLITE_SHM_EXCLUSIVE)
- [SQLITE_SHM_LOCK](#SQLITE_SHM_EXCLUSIVE)
- [SQLITE_SHM_NLOCK](#SQLITE_SHM_NLOCK)
- [SQLITE_SHM_SHARED](#SQLITE_SHM_EXCLUSIVE)
- [SQLITE_SHM_UNLOCK](#SQLITE_SHM_EXCLUSIVE)
- [SQLITE_SOURCE_ID](#SQLITE_SCM_BRANCH)
- [SQLITE_STATIC](#SQLITE_STATIC)
- [SQLITE_STATUS_MALLOC_COUNT](#sqlitestatusmalloccount)
- [SQLITE_STATUS_MALLOC_SIZE](#sqlitestatusmallocsize)
- [SQLITE_STATUS_MEMORY_USED](#sqlitestatusmemoryused)
- [SQLITE_STATUS_PAGECACHE_OVERFLOW](#sqlitestatuspagecacheoverflow)
- [SQLITE_STATUS_PAGECACHE_SIZE](#sqlitestatuspagecachesize)
- [SQLITE_STATUS_PAGECACHE_USED](#sqlitestatuspagecacheused)
- [SQLITE_STATUS_PARSER_STACK](#sqlitestatusparserstack)
- [SQLITE_STATUS_SCRATCH_OVERFLOW](#sqlitestatusscratchoverflow)
- [SQLITE_STATUS_SCRATCH_SIZE](#sqlitestatusscratchsize)
- [SQLITE_STATUS_SCRATCH_USED](#sqlitestatusscratchused)
- [SQLITE_STMTSTATUS_AUTOINDEX](#sqlitestmtstatusautoindex)
- [SQLITE_STMTSTATUS_FILTER_HIT](#SQLITE_STMTSTATUS%20counter)
- [SQLITE_STMTSTATUS_FILTER_MISS](#sqlitestmtstatusfiltermiss)
- [SQLITE_STMTSTATUS_FULLSCAN_STEP](#sqlitestmtstatusfullscanstep)
- [SQLITE_STMTSTATUS_MEMUSED](#sqlitestmtstatusmemused)
- [SQLITE_STMTSTATUS_REPREPARE](#sqlitestmtstatusreprepare)
- [SQLITE_STMTSTATUS_RUN](#sqlitestmtstatusrun)
- [SQLITE_STMTSTATUS_SORT](#sqlitestmtstatussort)
- [SQLITE_STMTSTATUS_VM_STEP](#sqlitestmtstatusvmstep)
- [SQLITE_SUBTYPE](#sqlitesubtype)
- [SQLITE_SYNC_DATAONLY](#SQLITE_SYNC_DATAONLY)
- [SQLITE_SYNC_FULL](#SQLITE_SYNC_DATAONLY)
- [SQLITE_SYNC_NORMAL](#SQLITE_SYNC_DATAONLY)
- [SQLITE_TESTCTRL_ALWAYS](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_ASSERT](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_ATOF](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_BENIGN_MALLOC_HOOKS](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_BITVEC_TEST](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_BYTEORDER](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_EXPLAIN_STMT](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_EXTRA_SCHEMA_CHECKS](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_FAULT_INSTALL](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_FIRST](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_FK_NO_ACTION](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_GETOPT](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_IMPOSTER](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_INTERNAL_FUNCTIONS](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_ISINIT](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_ISKEYWORD](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_JSON_SELFCHECK](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_LAST](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_LOCALTIME_FAULT](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_LOGEST](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_NEVER_CORRUPT](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_ONCE_RESET_THRESHOLD](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_OPTIMIZATIONS](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_PARSER_COVERAGE](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_PENDING_BYTE](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_PRNG_RESET](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_PRNG_RESTORE](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_PRNG_SAVE](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_PRNG_SEED](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_RESERVE](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_RESULT_INTREAL](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_SCRATCHMALLOC](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_SEEK_COUNT](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_SORTER_MMAP](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_TRACEFLAGS](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_TUNE](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_USELONGDOUBLE](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TESTCTRL_VDBE_COVERAGE](#SQLITE_TESTCTRL_ALWAYS)
- [SQLITE_TEXT](#SQLITE_BLOB)
- [SQLITE_TOOBIG](#SQLITE_ABORT)
- [SQLITE_TRACE](#SQLITE_TRACE)
- [SQLITE_TRACE_CLOSE](#sqlitetraceclose)
- [SQLITE_TRACE_PROFILE](#sqlitetraceprofile)
- [SQLITE_TRACE_ROW](#sqlitetracerow)
- [SQLITE_TRACE_STMT](#sqlitetracestmt)
- [SQLITE_TRANSACTION](#SQLITE_ALTER_TABLE)
- [SQLITE_TRANSIENT](#SQLITE_STATIC)
- [SQLITE_TXN_NONE](#sqlitetxnnone)
- [SQLITE_TXN_READ](#sqlitetxnread)
- [SQLITE_TXN_WRITE](#sqlitetxnwrite)
- [SQLITE_UPDATE](#SQLITE_ALTER_TABLE)
- [SQLITE_UTF16](#sqliteutf16)
- [SQLITE_UTF16BE](#sqliteutf16be)
- [SQLITE_UTF16LE](#sqliteutf16le)
- [SQLITE_UTF16_ALIGNED](#sqliteutf16aligned)
- [SQLITE_UTF8](#sqliteutf8)
- [SQLITE_UTF8_ZT](#sqliteutf8zt)
- [SQLITE_VERSION](#SQLITE_SCM_BRANCH)
- [SQLITE_VERSION_NUMBER](#SQLITE_SCM_BRANCH)
- [SQLITE_VTAB_CONSTRAINT_SUPPORT](#sqlitevtabconstraintsupport)
- [SQLITE_VTAB_DIRECTONLY](#sqlitevtabdirectonly)
- [SQLITE_VTAB_INNOCUOUS](#sqlitevtabinnocuous)
- [SQLITE_VTAB_USES_ALL_SCHEMAS](#sqlitevtabusesallschemas)
- [SQLITE_WARNING](#SQLITE_ABORT)
- [SQLITE_WARNING_AUTOINDEX](#SQLITE_ABORT_ROLLBACK)
- [SQLITE_WIN32_DATA_DIRECTORY_TYPE](#SQLITE_WIN32_DATA_DIRECTORY_TYPE)
- [SQLITE_WIN32_TEMP_DIRECTORY_TYPE](#SQLITE_WIN32_DATA_DIRECTORY_TYPE)
------------------------------------------------------------------------
## List Of Functions:
Note: Functions marked with "*(exp)*" are [experimental](capi3ref.md) and functions whose names are ~~struck through~~ are [deprecated](capi3ref.md).
- [sqlite3_aggregate_context](#sqlite3_aggregate_context)
- ~~sqlite3_aggregate_count~~
- [sqlite3_auto_extension](#sqlite3_auto_extension)
- [sqlite3_autovacuum_pages](#sqlite3_autovacuum_pages)
- [sqlite3_backup_finish](#sqlite3backupfinish)
- [sqlite3_backup_init](#sqlite3backupinit)
- [sqlite3_backup_pagecount](#sqlite3backuppagecount)
- [sqlite3_backup_remaining](#sqlite3backupremaining)
- [sqlite3_backup_step](#sqlite3backupstep)
- [sqlite3_bind_blob](#sqlite3_bind_blob)
- [sqlite3_bind_blob64](#sqlite3_bind_blob)
- [sqlite3_bind_double](#sqlite3_bind_blob)
- [sqlite3_bind_int](#sqlite3_bind_blob)
- [sqlite3_bind_int64](#sqlite3_bind_blob)
- [sqlite3_bind_null](#sqlite3_bind_blob)
- [sqlite3_bind_parameter_count](#sqlite3_bind_parameter_count)
- [sqlite3_bind_parameter_index](#sqlite3_bind_parameter_index)
- [sqlite3_bind_parameter_name](#sqlite3_bind_parameter_name)
- [sqlite3_bind_pointer](#sqlite3_bind_blob)
- [sqlite3_bind_text](#sqlite3_bind_blob)
- [sqlite3_bind_text16](#sqlite3_bind_blob)
- [sqlite3_bind_text64](#sqlite3_bind_blob)
- [sqlite3_bind_value](#sqlite3_bind_blob)
- [sqlite3_bind_zeroblob](#sqlite3_bind_blob)
- [sqlite3_bind_zeroblob64](#sqlite3_bind_blob)
- [sqlite3_blob_bytes](#sqlite3_blob_bytes)
- [sqlite3_blob_close](#sqlite3_blob_close)
- [sqlite3_blob_open](#sqlite3_blob_open)
- [sqlite3_blob_read](#sqlite3_blob_read)
- [sqlite3_blob_reopen](#sqlite3_blob_reopen)
- [sqlite3_blob_write](#sqlite3_blob_write)
- [sqlite3_busy_handler](#sqlite3_busy_handler)
- [sqlite3_busy_timeout](#sqlite3_busy_timeout)
- [sqlite3_cancel_auto_extension](#sqlite3_cancel_auto_extension)
- [sqlite3_carray_bind](#sqlite3_carray_bind)
- [sqlite3_carray_bind_v2](#sqlite3_carray_bind)
- [sqlite3_changes](#sqlite3_changes)
- [sqlite3_changes64](#sqlite3_changes)
- [sqlite3_clear_bindings](#sqlite3_clear_bindings)
- [sqlite3_close](#sqlite3_close)
- [sqlite3_close_v2](#sqlite3_close)
- [sqlite3_collation_needed](#sqlite3_collation_needed)
- [sqlite3_collation_needed16](#sqlite3_collation_needed)
- [sqlite3_column_blob](#sqlite3_column_blob)
- [sqlite3_column_bytes](#sqlite3_column_blob)
- [sqlite3_column_bytes16](#sqlite3_column_blob)
- [sqlite3_column_count](#sqlite3_column_count)
- [sqlite3_column_database_name](#sqlite3_column_database_name)
- [sqlite3_column_database_name16](#sqlite3_column_database_name)
- [sqlite3_column_decltype](#sqlite3_column_decltype)
- [sqlite3_column_decltype16](#sqlite3_column_decltype)
- [sqlite3_column_double](#sqlite3_column_blob)
- [sqlite3_column_int](#sqlite3_column_blob)
- [sqlite3_column_int64](#sqlite3_column_blob)
- [sqlite3_column_name](#sqlite3_column_name)
- [sqlite3_column_name16](#sqlite3_column_name)
- [sqlite3_column_origin_name](#sqlite3_column_database_name)
- [sqlite3_column_origin_name16](#sqlite3_column_database_name)
- [sqlite3_column_table_name](#sqlite3_column_database_name)
- [sqlite3_column_table_name16](#sqlite3_column_database_name)
- [sqlite3_column_text](#sqlite3_column_blob)
- [sqlite3_column_text16](#sqlite3_column_blob)
- [sqlite3_column_type](#sqlite3_column_blob)
- [sqlite3_column_value](#sqlite3_column_blob)
- [sqlite3_commit_hook](#sqlite3_commit_hook)
- [sqlite3_compileoption_get](#sqlite3_compileoption_get)
- [sqlite3_compileoption_used](#sqlite3_compileoption_get)
- [sqlite3_complete](#sqlite3_complete)
- [sqlite3_complete16](#sqlite3_complete)
- [sqlite3_config](#sqlite3_config)
- [sqlite3_context_db_handle](#sqlite3_context_db_handle)
- [sqlite3_create_collation](#sqlite3_create_collation)
- [sqlite3_create_collation16](#sqlite3_create_collation)
- [sqlite3_create_collation_v2](#sqlite3_create_collation)
- [sqlite3_create_filename](#sqlite3_create_filename)
- [sqlite3_create_function](#sqlite3_create_function)
- [sqlite3_create_function16](#sqlite3_create_function)
- [sqlite3_create_function_v2](#sqlite3_create_function)
- [sqlite3_create_module](#sqlite3_create_module)
- [sqlite3_create_module_v2](#sqlite3_create_module)
- [sqlite3_create_window_function](#sqlite3_create_function)
- [sqlite3_data_count](#sqlite3_data_count)
- [sqlite3_database_file_object](#sqlite3_database_file_object)
- [sqlite3_db_cacheflush](#sqlite3_db_cacheflush)
- [sqlite3_db_config](#sqlite3_db_config)
- [sqlite3_db_filename](#sqlite3_db_filename)
- [sqlite3_db_handle](#sqlite3_db_handle)
- [sqlite3_db_mutex](#sqlite3_db_mutex)
- [sqlite3_db_name](#sqlite3_db_name)
- [sqlite3_db_readonly](#sqlite3_db_readonly)
- [sqlite3_db_release_memory](#sqlite3_db_release_memory)
- [sqlite3_db_status](#sqlite3_db_status)
- [sqlite3_db_status64](#sqlite3_db_status)
- [sqlite3_declare_vtab](#sqlite3_declare_vtab)
- [sqlite3_deserialize](#sqlite3_deserialize)
- [sqlite3_drop_modules](#sqlite3_drop_modules)
- [sqlite3_enable_load_extension](#sqlite3_enable_load_extension)
- [sqlite3_enable_shared_cache](#sqlite3_enable_shared_cache)
- [sqlite3_errcode](#sqlite3_errcode)
- [sqlite3_errmsg](#sqlite3_errcode)
- [sqlite3_errmsg16](#sqlite3_errcode)
- [sqlite3_error_offset](#sqlite3_errcode)
- [sqlite3_errstr](#sqlite3_errcode)
- [sqlite3_exec](#sqlite3_exec)
- [sqlite3_expanded_sql](#sqlite3_expanded_sql)
- ~~sqlite3_expired~~
- [sqlite3_extended_errcode](#sqlite3_errcode)
- [sqlite3_extended_result_codes](#sqlite3_extended_result_codes)
- [sqlite3_file_control](#sqlite3_file_control)
- [sqlite3_filename_database](#sqlite3_filename_database)
- [sqlite3_filename_journal](#sqlite3_filename_database)
- [sqlite3_filename_wal](#sqlite3_filename_database)
- [sqlite3_finalize](#sqlite3_finalize)
- [sqlite3_free](#sqlite3_free)
- [sqlite3_free_filename](#sqlite3_create_filename)
- [sqlite3_free_table](#sqlite3_free_table)
- [sqlite3_get_autocommit](#sqlite3_get_autocommit)
- [sqlite3_get_auxdata](#sqlite3_get_auxdata)
- [sqlite3_get_clientdata](#sqlite3_get_clientdata)
- [sqlite3_get_table](#sqlite3_free_table)
- ~~sqlite3_global_recover~~
- [sqlite3_hard_heap_limit64](#sqlite3_hard_heap_limit64)
- [sqlite3_initialize](#sqlite3_initialize)
- [sqlite3_interrupt](#sqlite3_interrupt)
- [sqlite3_is_interrupted](#sqlite3_interrupt)
- [sqlite3_keyword_check](#sqlite3_keyword_check)
- [sqlite3_keyword_count](#sqlite3_keyword_check)
- [sqlite3_keyword_name](#sqlite3_keyword_check)
- [sqlite3_last_insert_rowid](#sqlite3_last_insert_rowid)
- [sqlite3_libversion](#sqlite3_libversion)
- [sqlite3_libversion_number](#sqlite3_libversion)
- [sqlite3_limit](#sqlite3_limit)
- [sqlite3_load_extension](#sqlite3_load_extension)
- [sqlite3_log](#sqlite3_log)
- [sqlite3_malloc](#sqlite3_free)
- [sqlite3_malloc64](#sqlite3_free)
- ~~sqlite3_memory_alarm~~
- [sqlite3_memory_highwater](#sqlite3_memory_highwater)
- [sqlite3_memory_used](#sqlite3_memory_highwater)
- [sqlite3_mprintf](#sqlite3_mprintf)
- [sqlite3_msize](#sqlite3_free)
- [sqlite3_mutex_alloc](#sqlite3_mutex_alloc)
- [sqlite3_mutex_enter](#sqlite3_mutex_alloc)
- [sqlite3_mutex_free](#sqlite3_mutex_alloc)
- [sqlite3_mutex_held](#sqlite3_mutex_held)
- [sqlite3_mutex_leave](#sqlite3_mutex_alloc)
- [sqlite3_mutex_notheld](#sqlite3_mutex_held)
- [sqlite3_mutex_try](#sqlite3_mutex_alloc)
- [sqlite3_next_stmt](#sqlite3_next_stmt)
- [sqlite3_normalized_sql](#sqlite3_expanded_sql)
- [sqlite3_open](#sqlite3_open)
- [sqlite3_open16](#sqlite3_open)
- [sqlite3_open_v2](#sqlite3_open)
- [sqlite3_os_end](#sqlite3_initialize)
- [sqlite3_os_init](#sqlite3_initialize)
- [sqlite3_overload_function](#sqlite3_overload_function)
- [sqlite3_prepare](#sqlite3_prepare)
- [sqlite3_prepare16](#sqlite3_prepare)
- [sqlite3_prepare16_v2](#sqlite3_prepare)
- [sqlite3_prepare16_v3](#sqlite3_prepare)
- [sqlite3_prepare_v2](#sqlite3_prepare)
- [sqlite3_prepare_v3](#sqlite3_prepare)
- [sqlite3_preupdate_blobwrite](#sqlite3_preupdate_blobwrite)
- [sqlite3_preupdate_count](#sqlite3_preupdate_blobwrite)
- [sqlite3_preupdate_depth](#sqlite3_preupdate_blobwrite)
- [sqlite3_preupdate_hook](#sqlite3_preupdate_blobwrite)
- [sqlite3_preupdate_new](#sqlite3_preupdate_blobwrite)
- [sqlite3_preupdate_old](#sqlite3_preupdate_blobwrite)
- ~~sqlite3_profile~~
- [sqlite3_progress_handler](#sqlite3_progress_handler)
- [sqlite3_randomness](#sqlite3_randomness)
- [sqlite3_realloc](#sqlite3_free)
- [sqlite3_realloc64](#sqlite3_free)
- [sqlite3_release_memory](#sqlite3_release_memory)
- [sqlite3_reset](#sqlite3_reset)
- [sqlite3_reset_auto_extension](#sqlite3_reset_auto_extension)
- [sqlite3_result_blob](#sqlite3_result_blob)
- [sqlite3_result_blob64](#sqlite3_result_blob)
- [sqlite3_result_double](#sqlite3_result_blob)
- [sqlite3_result_error](#sqlite3_result_blob)
- [sqlite3_result_error16](#sqlite3_result_blob)
- [sqlite3_result_error_code](#sqlite3_result_blob)
- [sqlite3_result_error_nomem](#sqlite3_result_blob)
- [sqlite3_result_error_toobig](#sqlite3_result_blob)
- [sqlite3_result_int](#sqlite3_result_blob)
- [sqlite3_result_int64](#sqlite3_result_blob)
- [sqlite3_result_null](#sqlite3_result_blob)
- [sqlite3_result_pointer](#sqlite3_result_blob)
- [sqlite3_result_subtype](#sqlite3_result_subtype)
- [sqlite3_result_text](#sqlite3_result_blob)
- [sqlite3_result_text16](#sqlite3_result_blob)
- [sqlite3_result_text16be](#sqlite3_result_blob)
- [sqlite3_result_text16le](#sqlite3_result_blob)
- [sqlite3_result_text64](#sqlite3_result_blob)
- [sqlite3_result_value](#sqlite3_result_blob)
- [sqlite3_result_zeroblob](#sqlite3_result_blob)
- [sqlite3_result_zeroblob64](#sqlite3_result_blob)
- [sqlite3_rollback_hook](#sqlite3_commit_hook)
- [sqlite3_serialize](#sqlite3_serialize)
- [sqlite3_set_authorizer](#sqlite3_set_authorizer)
- [sqlite3_set_auxdata](#sqlite3_get_auxdata)
- [sqlite3_set_clientdata](#sqlite3_get_clientdata)
- [sqlite3_set_errmsg](#sqlite3_set_errmsg)
- [sqlite3_set_last_insert_rowid](#sqlite3_set_last_insert_rowid)
- [sqlite3_setlk_timeout](#sqlite3_setlk_timeout)
- [sqlite3_shutdown](#sqlite3_initialize)
- [sqlite3_sleep](#sqlite3_sleep)
- [sqlite3_snapshot_cmp](#sqlite3_snapshot_cmp)
- [sqlite3_snapshot_free](#sqlite3_snapshot_free)
- [sqlite3_snapshot_get](#sqlite3_snapshot_get)
- [sqlite3_snapshot_open](#sqlite3_snapshot_open)
- [sqlite3_snapshot_recover](#sqlite3_snapshot_recover)
- [sqlite3_snprintf](#sqlite3_mprintf)
- ~~sqlite3_soft_heap_limit~~
- [sqlite3_soft_heap_limit64](#sqlite3_hard_heap_limit64)
- [sqlite3_sourceid](#sqlite3_libversion)
- [sqlite3_sql](#sqlite3_expanded_sql)
- [sqlite3_status](#sqlite3_status)
- [sqlite3_status64](#sqlite3_status)
- [sqlite3_step](#sqlite3_step)
- [sqlite3_stmt_busy](#sqlite3_stmt_busy)
- [sqlite3_stmt_explain](#sqlite3_stmt_explain)
- [sqlite3_stmt_isexplain](#sqlite3_stmt_isexplain)
- [sqlite3_stmt_readonly](#sqlite3_stmt_readonly)
- [sqlite3_stmt_scanstatus](#sqlite3_stmt_scanstatus)
- [sqlite3_stmt_scanstatus_reset](#sqlite3_stmt_scanstatus_reset)
- [sqlite3_stmt_scanstatus_v2](#sqlite3_stmt_scanstatus)
- [sqlite3_stmt_status](#sqlite3_stmt_status)
- [sqlite3_str_append](#sqlite3_str_append)
- [sqlite3_str_appendall](#sqlite3_str_append)
- [sqlite3_str_appendchar](#sqlite3_str_append)
- [sqlite3_str_appendf](#sqlite3_str_append)
- [sqlite3_str_errcode](#sqlite3_str_errcode)
- [sqlite3_str_finish](#sqlite3_str_finish)
- [sqlite3_str_free](#sqlite3_str_finish)
- [sqlite3_str_length](#sqlite3_str_errcode)
- [sqlite3_str_new](#sqlite3_str_new)
- [sqlite3_str_reset](#sqlite3_str_append)
- [sqlite3_str_truncate](#sqlite3_str_append)
- [sqlite3_str_value](#sqlite3_str_errcode)
- [sqlite3_str_vappendf](#sqlite3_str_append)
- [sqlite3_strglob](#sqlite3_strglob)
- [sqlite3_stricmp](#sqlite3_stricmp)
- [sqlite3_strlike](#sqlite3_strlike)
- [sqlite3_strnicmp](#sqlite3_stricmp)
- [sqlite3_system_errno](#sqlite3_system_errno)
- [sqlite3_table_column_metadata](#sqlite3_table_column_metadata)
- [sqlite3_test_control](#sqlite3_test_control)
- ~~sqlite3_thread_cleanup~~
- [sqlite3_threadsafe](#sqlite3_threadsafe)
- [sqlite3_total_changes](#sqlite3_total_changes)
- [sqlite3_total_changes64](#sqlite3_total_changes)
- ~~sqlite3_trace~~
- [sqlite3_trace_v2](#sqlite3_trace_v2)
- ~~sqlite3_transfer_bindings~~
- [sqlite3_txn_state](#sqlite3_txn_state)
- [sqlite3_unlock_notify](#sqlite3_unlock_notify)
- [sqlite3_update_hook](#sqlite3_update_hook)
- [sqlite3_uri_boolean](#sqlite3_uri_boolean)
- [sqlite3_uri_int64](#sqlite3_uri_boolean)
- [sqlite3_uri_key](#sqlite3_uri_boolean)
- [sqlite3_uri_parameter](#sqlite3_uri_boolean)
- [sqlite3_user_data](#sqlite3_user_data)
- [sqlite3_value_blob](#sqlite3_value_blob)
- [sqlite3_value_bytes](#sqlite3_value_blob)
- [sqlite3_value_bytes16](#sqlite3_value_blob)
- [sqlite3_value_double](#sqlite3_value_blob)
- [sqlite3_value_dup](#sqlite3_value_dup)
- [sqlite3_value_encoding](#sqlite3_value_encoding)
- [sqlite3_value_free](#sqlite3_value_dup)
- [sqlite3_value_frombind](#sqlite3_value_blob)
- [sqlite3_value_int](#sqlite3_value_blob)
- [sqlite3_value_int64](#sqlite3_value_blob)
- [sqlite3_value_nochange](#sqlite3_value_blob)
- [sqlite3_value_numeric_type](#sqlite3_value_blob)
- [sqlite3_value_pointer](#sqlite3_value_blob)
- [sqlite3_value_subtype](#sqlite3_value_subtype)
- [sqlite3_value_text](#sqlite3_value_blob)
- [sqlite3_value_text16](#sqlite3_value_blob)
- [sqlite3_value_text16be](#sqlite3_value_blob)
- [sqlite3_value_text16le](#sqlite3_value_blob)
- [sqlite3_value_type](#sqlite3_value_blob)
- [sqlite3_version](#sqlite3_libversion)
- [sqlite3_vfs_find](#sqlite3_vfs_find)
- [sqlite3_vfs_register](#sqlite3_vfs_find)
- [sqlite3_vfs_unregister](#sqlite3_vfs_find)
- [sqlite3_vmprintf](#sqlite3_mprintf)
- [sqlite3_vsnprintf](#sqlite3_mprintf)
- [sqlite3_vtab_collation](#sqlite3_vtab_collation)
- [sqlite3_vtab_config](#sqlite3_vtab_config)
- [sqlite3_vtab_distinct](#sqlite3_vtab_distinct)
- [sqlite3_vtab_in](#sqlite3_vtab_in)
- [sqlite3_vtab_in_first](#sqlite3_vtab_in_first)
- [sqlite3_vtab_in_next](#sqlite3_vtab_in_first)
- [sqlite3_vtab_nochange](#sqlite3_vtab_nochange)
- [sqlite3_vtab_on_conflict](#sqlite3_vtab_on_conflict)
- [sqlite3_vtab_rhs_value](#sqlite3_vtab_rhs_value)
- [sqlite3_wal_autocheckpoint](#sqlite3_wal_autocheckpoint)
- [sqlite3_wal_checkpoint](#sqlite3_wal_checkpoint)
- [sqlite3_wal_checkpoint_v2](#sqlite3_wal_checkpoint_v2)
- [sqlite3_wal_hook](#sqlite3_wal_hook)
- [sqlite3_win32_set_directory](#sqlite3_win32_set_directory)
- [sqlite3_win32_set_directory16](#sqlite3_win32_set_directory)
- [sqlite3_win32_set_directory8](#sqlite3_win32_set_directory)
------------------------------------------------------------------------
## Flags for sqlite3_serialize
> \
> \#define SQLITE_SERIALIZE_NOCOPY 0x001 /\* Do no memory allocations \*/\
Zero or more of the following constants can be OR-ed together for the F argument to [sqlite3_serialize(D,S,P,F)](#sqlite3_serialize).
SQLITE_SERIALIZE_NOCOPY means that [sqlite3_serialize()](#sqlite3_serialize) will return a pointer to contiguous in-memory database that it is currently using, without making a copy of the database. If SQLite is not currently using a contiguous in-memory database, then this option causes [sqlite3_serialize()](#sqlite3_serialize) to return a NULL pointer. SQLite will only be using a contiguous in-memory database if it has been initialized by a prior call to [sqlite3_deserialize()](#sqlite3_deserialize).
------------------------------------------------------------------------
## Flags for sqlite3_setlk_timeout()
> \
> \#define SQLITE_SETLK_BLOCK_ON_CONNECT 0x01\
------------------------------------------------------------------------
## Maximum xShmLock index
> \
> \#define SQLITE_SHM_NLOCK 8\
The xShmLock method on [sqlite3_io_methods](#sqlite3_io_methods) may use values between 0 and this upper bound as its "offset" argument. The SQLite core will never attempt to acquire or release a lock outside of this range
------------------------------------------------------------------------
## Loadable Extension Thunk
> \
> typedef struct sqlite3_api_routines sqlite3_api_routines;\
A pointer to the opaque sqlite3_api_routines structure is passed as the third parameter to entry points of [loadable extensions](loadext.md). This structure must be typedefed in order to work around compiler warnings on some platforms.
------------------------------------------------------------------------
## Online Backup Object
> \
> typedef struct sqlite3_backup sqlite3_backup;\
The sqlite3_backup object records state information about an ongoing online backup operation. The sqlite3_backup object is created by a call to [sqlite3_backup_init()](#sqlite3backupinit) and is destroyed by a call to [sqlite3_backup_finish()](#sqlite3backupfinish).
See Also: [Using the SQLite Online Backup API](backup.md)
------------------------------------------------------------------------
## SQL Function Context Object
> \
> typedef struct sqlite3_context sqlite3_context;\
The context in which an SQL function executes is stored in an sqlite3_context object. A pointer to an sqlite3_context object is always the first parameter to [application-defined SQL functions](appfunc.md). The application-defined SQL function implementation will pass this pointer through into calls to [sqlite3_result()](#sqlite3_result_blob), [sqlite3_aggregate_context()](#sqlite3_aggregate_context), [sqlite3_user_data()](#sqlite3_user_data), [sqlite3_context_db_handle()](#sqlite3_context_db_handle), [sqlite3_get_auxdata()](#sqlite3_get_auxdata), and/or [sqlite3_set_auxdata()](#sqlite3_get_auxdata).
26 Methods using this object:
- [sqlite3_aggregate_context](#sqlite3_aggregate_context)
- [sqlite3_context_db_handle](#sqlite3_context_db_handle)
- [sqlite3_get_auxdata](#sqlite3_get_auxdata)
- [sqlite3_result_blob](#sqlite3_result_blob)
- [sqlite3_result_blob64](#sqlite3_result_blob)
- [sqlite3_result_double](#sqlite3_result_blob)
- [sqlite3_result_error](#sqlite3_result_blob)
- [sqlite3_result_error16](#sqlite3_result_blob)
- [sqlite3_result_error_code](#sqlite3_result_blob)
- [sqlite3_result_error_nomem](#sqlite3_result_blob)
- [sqlite3_result_error_toobig](#sqlite3_result_blob)
- [sqlite3_result_int](#sqlite3_result_blob)
- [sqlite3_result_int64](#sqlite3_result_blob)
- [sqlite3_result_null](#sqlite3_result_blob)
- [sqlite3_result_pointer](#sqlite3_result_blob)
- [sqlite3_result_subtype](#sqlite3_result_subtype)
- [sqlite3_result_text](#sqlite3_result_blob)
- [sqlite3_result_text16](#sqlite3_result_blob)
- [sqlite3_result_text16be](#sqlite3_result_blob)
- [sqlite3_result_text16le](#sqlite3_result_blob)
- [sqlite3_result_text64](#sqlite3_result_blob)
- [sqlite3_result_value](#sqlite3_result_blob)
- [sqlite3_result_zeroblob](#sqlite3_result_blob)
- [sqlite3_result_zeroblob64](#sqlite3_result_blob)
- [sqlite3_set_auxdata](#sqlite3_get_auxdata)
- [sqlite3_user_data](#sqlite3_user_data)
------------------------------------------------------------------------
## Name Of The Folder Holding Database Files
> \
> SQLITE_EXTERN char \*sqlite3_data_directory;\
If this global variable is made to point to a string which is the name of a folder (a.k.a. directory), then all database files specified with a relative pathname and created or accessed by SQLite when using a built-in windows [VFS](#sqlite3_vfs) will be assumed to be relative to that directory. If this variable is a NULL pointer, then SQLite assumes that all database files specified with a relative pathname are relative to the current directory for the process. Only the windows VFS makes use of this global variable; it is ignored by the unix VFS.
Changing the value of this variable while a database connection is open can result in a corrupt database.
It is not safe to read or modify this variable in more than one thread at a time. It is not safe to read or modify this variable if a [database connection](#sqlite3) is being used at the same time in a separate thread. It is intended that this variable be set once as part of process initialization and before any SQLite interface routines have been called and that this variable remain unchanged thereafter.
The [data_store_directory pragma](pragma.md#pragma_data_store_directory) may modify this variable and cause it to point to memory obtained from [sqlite3_malloc](#sqlite3_free). Furthermore, the [data_store_directory pragma](pragma.md#pragma_data_store_directory) always assumes that any string that this variable points to is held in memory obtained from [sqlite3_malloc](#sqlite3_free) and the pragma may attempt to free that memory using [sqlite3_free](#sqlite3_free). Hence, if this variable is modified directly, either it should be made NULL or made to point to memory obtained from [sqlite3_malloc](#sqlite3_free) or else the use of the [data_store_directory pragma](pragma.md#pragma_data_store_directory) should be avoided.
------------------------------------------------------------------------
## OS Interface Open File Handle
> \
> typedef struct sqlite3_file sqlite3_file;\
> struct sqlite3_file {\
> const struct sqlite3_io_methods \*pMethods; /\* Methods for an open file \*/\
> };\
An [sqlite3_file](#sqlite3_file) object represents an open file in the [OS interface layer](#sqlite3_vfs). Individual OS interface implementations will want to subclass this object by appending additional fields for their own use. The pMethods entry is a pointer to an [sqlite3_io_methods](#sqlite3_io_methods) object that defines methods for performing I/O operations on the open file.
------------------------------------------------------------------------
## File Name
> \
> typedef const char \*sqlite3_filename;\
Type [sqlite3_filename](#sqlite3_filename) is used by SQLite to pass filenames to the xOpen method of a [VFS](vfs.md). It may be cast to (const char\*) and treated as a normal, nul-terminated, UTF-8 buffer containing the filename, but may also be passed to special APIs such as:
- sqlite3_filename_database()
- sqlite3_filename_journal()
- sqlite3_filename_wal()
- sqlite3_uri_parameter()
- sqlite3_uri_boolean()
- sqlite3_uri_int64()
- sqlite3_uri_key()
------------------------------------------------------------------------
## Virtual Table Indexing Information
> \
> struct sqlite3_index_info {\
> /\* Inputs \*/\
> int nConstraint; /\* Number of entries in aConstraint \*/\
> struct sqlite3_index_constraint {\
> int iColumn; /\* Column constrained. -1 for ROWID \*/\
> unsigned char op; /\* Constraint operator \*/\
> unsigned char usable; /\* True if this constraint is usable \*/\
> int iTermOffset; /\* Used internally - xBestIndex should ignore \*/\
> } \*aConstraint; /\* Table of WHERE clause constraints \*/\
> int nOrderBy; /\* Number of terms in the ORDER BY clause \*/\
> struct sqlite3_index_orderby {\
> int iColumn; /\* Column number \*/\
> unsigned char desc; /\* True for DESC. False for ASC. \*/\
> } \*aOrderBy; /\* The ORDER BY clause \*/\
> /\* Outputs \*/\
> struct sqlite3_index_constraint_usage {\
> int argvIndex; /\* if \>0, constraint is part of argv to xFilter \*/\
> unsigned char omit; /\* Do not code a test for this constraint \*/\
> } \*aConstraintUsage;\
> int idxNum; /\* Number used to identify the index \*/\
> char \*idxStr; /\* String, possibly obtained from sqlite3_malloc \*/\
> int needToFreeIdxStr; /\* Free idxStr using sqlite3_free() if true \*/\
> int orderByConsumed; /\* True if output is already ordered \*/\
> double estimatedCost; /\* Estimated cost of using this index \*/\
> /\* Fields below are only available in SQLite 3.8.2 and later \*/\
> sqlite3_int64 estimatedRows; /\* Estimated number of rows returned \*/\
> /\* Fields below are only available in SQLite 3.9.0 and later \*/\
> int idxFlags; /\* Mask of SQLITE_INDEX_SCAN\_\* flags \*/\
> /\* Fields below are only available in SQLite 3.10.0 and later \*/\
> sqlite3_uint64 colUsed; /\* Input: Mask of columns used by statement \*/\
> };\
The sqlite3_index_info structure and its substructures is used as part of the [virtual table](vtab.md) interface to pass information into and receive the reply from the [xBestIndex](vtab.md#xbestindex) method of a [virtual table module](#sqlite3_module). The fields under \*\*Inputs\*\* are the inputs to xBestIndex and are read-only. xBestIndex inserts its results into the \*\*Outputs\*\* fields.
The aConstraint\[\] array records WHERE clause constraints of the form:
> column OP expr
where OP is =, \<, \<=, \>, or \>=. The particular operator is stored in aConstraint\[\].op using one of the [SQLITE_INDEX_CONSTRAINT\_ values](#SQLITE_INDEX_CONSTRAINT_EQ). The index of the column is stored in aConstraint\[\].iColumn. aConstraint\[\].usable is TRUE if the expr on the right-hand side can be evaluated (and thus the constraint is usable) and false if it cannot.
The optimizer automatically inverts terms of the form "expr OP column" and makes other simplifications to the WHERE clause in an attempt to get as many WHERE clause terms into the form shown above as possible. The aConstraint\[\] array only reports WHERE clause terms that are relevant to the particular virtual table being queried.
Information about the ORDER BY clause is stored in aOrderBy\[\]. Each term of aOrderBy records a column of the ORDER BY clause.
The colUsed field indicates which columns of the virtual table may be required by the current scan. Virtual table columns are numbered from zero in the order in which they appear within the CREATE TABLE statement passed to sqlite3_declare_vtab(). For the first 63 columns (columns 0-62), the corresponding bit is set within the colUsed mask if the column may be required by SQLite. If the table has at least 64 columns and any column to the right of the first 63 is required, then bit 63 of colUsed is also set. In other words, column iCol may be required if the expression (colUsed & ((sqlite3_uint64)1 \<\< (iCol\>=63 ? 63 : iCol))) evaluates to non-zero.
The [xBestIndex](vtab.md#xbestindex) method must fill aConstraintUsage\[\] with information about what parameters to pass to xFilter. If argvIndex\>0 then the right-hand side of the corresponding aConstraint\[\] is evaluated and becomes the argvIndex-th entry in argv. If aConstraintUsage\[\].omit is true, then the constraint is assumed to be fully handled by the virtual table and might not be checked again by the byte code. The aConstraintUsage\[\].omit flag is an optimization hint. When the omit flag is left in its default setting of false, the constraint will always be checked separately in byte code. If the omit flag is changed to true, then the constraint may or may not be checked in byte code. In other words, when the omit flag is true there is no guarantee that the constraint will not be checked again using byte code.
The idxNum and idxStr values are recorded and passed into the [xFilter](vtab.md#xfilter) method. [sqlite3_free()](#sqlite3_free) is used to free idxStr if and only if needToFreeIdxStr is true.
The orderByConsumed means that output from [xFilter](vtab.md#xfilter)/[xNext](vtab.md#xnext) will occur in the correct order to satisfy the ORDER BY clause so that no separate sorting step is required.
The estimatedCost value is an estimate of the cost of a particular strategy. A cost of N indicates that the cost of the strategy is similar to a linear scan of an SQLite table with N rows. A cost of log(N) indicates that the expense of the operation is similar to that of a binary search on a unique indexed field of an SQLite table with N rows.
The estimatedRows value is an estimate of the number of rows that will be returned by the strategy.
The xBestIndex method may optionally populate the idxFlags field with a mask of SQLITE_INDEX_SCAN\_\* flags. One such flag is [SQLITE_INDEX_SCAN_HEX](#SQLITE_INDEX_SCAN_HEX), which if set causes the [EXPLAIN QUERY PLAN](eqp.md) output to show the idxNum as hex instead of as decimal. Another flag is SQLITE_INDEX_SCAN_UNIQUE, which if set indicates that the query plan will return at most one row.
Additionally, if xBestIndex sets the SQLITE_INDEX_SCAN_UNIQUE flag, then SQLite also assumes that if a call to the xUpdate() method is made as part of the same statement to delete or update a virtual table row and the implementation returns SQLITE_CONSTRAINT, then there is no need to rollback any database changes. In other words, if the xUpdate() returns SQLITE_CONSTRAINT, the database contents must be exactly as they were before xUpdate was called. By contrast, if SQLITE_INDEX_SCAN_UNIQUE is not set and xUpdate returns SQLITE_CONSTRAINT, any database changes made by the xUpdate method are automatically rolled back by SQLite.
IMPORTANT: The estimatedRows field was added to the sqlite3_index_info structure for SQLite [version 3.8.2](releaselog/3_8_2.md) (2013-12-06). If a virtual table extension is used with an SQLite version earlier than 3.8.2, the results of attempting to read or write the estimatedRows field are undefined (but are likely to include crashing the application). The estimatedRows field should therefore only be used if [sqlite3_libversion_number()](#sqlite3_libversion) returns a value greater than or equal to 3008002. Similarly, the idxFlags field was added for [version 3.9.0](releaselog/3_9_0.md) (2015-10-14). It may therefore only be used if sqlite3_libversion_number() returns a value greater than or equal to 3009000.
3 Methods using this object: [sqlite3_vtab_collation()](#sqlite3_vtab_collation), [sqlite3_vtab_distinct()](#sqlite3_vtab_distinct), [sqlite3_vtab_rhs_value()](#sqlite3_vtab_rhs_value)
------------------------------------------------------------------------
## OS Interface File Virtual Methods Object
> \
> typedef struct sqlite3_io_methods sqlite3_io_methods;\
> struct sqlite3_io_methods {\
> int iVersion;\
> int (\*xClose)(sqlite3_file\*);\
> int (\*xRead)(sqlite3_file\*, void\*, int iAmt, sqlite3_int64 iOfst);\
> int (\*xWrite)(sqlite3_file\*, const void\*, int iAmt, sqlite3_int64 iOfst);\
> int (\*xTruncate)(sqlite3_file\*, sqlite3_int64 size);\
> int (\*xSync)(sqlite3_file\*, int flags);\
> int (\*xFileSize)(sqlite3_file\*, sqlite3_int64 \*pSize);\
> int (\*xLock)(sqlite3_file\*, int);\
> int (\*xUnlock)(sqlite3_file\*, int);\
> int (\*xCheckReservedLock)(sqlite3_file\*, int \*pResOut);\
> int (\*xFileControl)(sqlite3_file\*, int op, void \*pArg);\
> int (\*xSectorSize)(sqlite3_file\*);\
> int (\*xDeviceCharacteristics)(sqlite3_file\*);\
> /\* Methods above are valid for version 1 \*/\
> int (\*xShmMap)(sqlite3_file\*, int iPg, int pgsz, int, void volatile\*\*);\
> int (\*xShmLock)(sqlite3_file\*, int offset, int n, int flags);\
> void (\*xShmBarrier)(sqlite3_file\*);\
> int (\*xShmUnmap)(sqlite3_file\*, int deleteFlag);\
> /\* Methods above are valid for version 2 \*/\
> int (\*xFetch)(sqlite3_file\*, sqlite3_int64 iOfst, int iAmt, void \*\*pp);\
> int (\*xUnfetch)(sqlite3_file\*, sqlite3_int64 iOfst, void \*p);\
> /\* Methods above are valid for version 3 \*/\
> /\* Additional methods may be added in future releases \*/\
> };\
Every file opened by the [sqlite3_vfs.xOpen](#sqlite3vfsxopen) method populates an [sqlite3_file](#sqlite3_file) object (or, more commonly, a subclass of the [sqlite3_file](#sqlite3_file) object) with a pointer to an instance of this object. This object defines the methods used to perform various operations against the open file represented by the [sqlite3_file](#sqlite3_file) object.
If the [sqlite3_vfs.xOpen](#sqlite3vfsxopen) method sets the sqlite3_file.pMethods element to a non-NULL pointer, then the sqlite3_io_methods.xClose method may be invoked even if the [sqlite3_vfs.xOpen](#sqlite3vfsxopen) reported that it failed. The only way to prevent a call to xClose following a failed [sqlite3_vfs.xOpen](#sqlite3vfsxopen) is for the [sqlite3_vfs.xOpen](#sqlite3vfsxopen) to set the sqlite3_file.pMethods element to NULL.
The flags argument to xSync may be one of [SQLITE_SYNC_NORMAL](#SQLITE_SYNC_DATAONLY) or [SQLITE_SYNC_FULL](#SQLITE_SYNC_DATAONLY). The first choice is the normal fsync(). The second choice is a Mac OS X style fullsync. The [SQLITE_SYNC_DATAONLY](#SQLITE_SYNC_DATAONLY) flag may be ORed in to indicate that only the data of the file and not its inode needs to be synced.
The integer values to xLock() and xUnlock() are one of
- [SQLITE_LOCK_NONE](#SQLITE_LOCK_EXCLUSIVE),
- [SQLITE_LOCK_SHARED](#SQLITE_LOCK_EXCLUSIVE),
- [SQLITE_LOCK_RESERVED](#SQLITE_LOCK_EXCLUSIVE),
- [SQLITE_LOCK_PENDING](#SQLITE_LOCK_EXCLUSIVE), or
- [SQLITE_LOCK_EXCLUSIVE](#SQLITE_LOCK_EXCLUSIVE).
xLock() upgrades the database file lock. In other words, xLock() moves the database file lock in the direction NONE toward EXCLUSIVE. The argument to xLock() is always one of SHARED, RESERVED, PENDING, or EXCLUSIVE, never SQLITE_LOCK_NONE. If the database file lock is already at or above the requested lock, then the call to xLock() is a no-op. xUnlock() downgrades the database file lock to either SHARED or NONE. If the lock is already at or below the requested lock state, then the call to xUnlock() is a no-op. The xCheckReservedLock() method checks whether any database connection, either in this process or in some other process, is holding a RESERVED, PENDING, or EXCLUSIVE lock on the file. It returns, via its output pointer parameter, true if such a lock exists and false otherwise.
The xFileControl() method is a generic interface that allows custom VFS implementations to directly control an open file using the [sqlite3_file_control()](#sqlite3_file_control) interface. The second "op" argument is an integer opcode. The third argument is a generic pointer intended to point to a structure that may contain arguments or space in which to write return values. Potential uses for xFileControl() might be functions to enable blocking locks with timeouts, to change the locking strategy (for example to use dot-file locks), to inquire about the status of a lock, or to break stale locks. The SQLite core reserves all opcodes less than 100 for its own use. A [list of opcodes](#SQLITE_FCNTL_BEGIN_ATOMIC_WRITE) less than 100 is available. Applications that define a custom xFileControl method should use opcodes greater than 100 to avoid conflicts. VFS implementations should return [SQLITE_NOTFOUND](#SQLITE_ABORT) for file control opcodes that they do not recognize.
The xSectorSize() method returns the sector size of the device that underlies the file. The sector size is the minimum write that can be performed without disturbing other bytes in the file. The xDeviceCharacteristics() method returns a bit vector describing behaviors of the underlying device:
- [SQLITE_IOCAP_ATOMIC](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_ATOMIC512](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_ATOMIC1K](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_ATOMIC2K](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_ATOMIC4K](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_ATOMIC8K](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_ATOMIC16K](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_ATOMIC32K](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_ATOMIC64K](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_SAFE_APPEND](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_SEQUENTIAL](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_POWERSAFE_OVERWRITE](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_IMMUTABLE](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_BATCH_ATOMIC](#SQLITE_IOCAP_ATOMIC)
- [SQLITE_IOCAP_SUBPAGE_READ](#SQLITE_IOCAP_ATOMIC)
The SQLITE_IOCAP_ATOMIC property means that all writes of any size are atomic. The SQLITE_IOCAP_ATOMICnnn values mean that writes of blocks that are nnn bytes in size and are aligned to an address which is an integer multiple of nnn are atomic. The SQLITE_IOCAP_SAFE_APPEND value means that when data is appended to a file, the data is appended first then the size of the file is extended, never the other way around. The SQLITE_IOCAP_SEQUENTIAL property means that information is written to disk in the same order as calls to xWrite().
If xRead() returns SQLITE_IOERR_SHORT_READ it must also fill in the unread portions of the buffer with zeros. A VFS that fails to zero-fill short reads might seem to work. However, failure to zero-fill short reads will eventually lead to database corruption.
------------------------------------------------------------------------
## Memory Allocation Routines
> \
> typedef struct sqlite3_mem_methods sqlite3_mem_methods;\
> struct sqlite3_mem_methods {\
> void \*(\*xMalloc)(int); /\* Memory allocation function \*/\
> void (\*xFree)(void\*); /\* Free a prior allocation \*/\
> void \*(\*xRealloc)(void\*,int); /\* Resize an allocation \*/\
> int (\*xSize)(void\*); /\* Return the size of an allocation \*/\
> int (\*xRoundup)(int); /\* Round up request size to allocation size \*/\
> int (\*xInit)(void\*); /\* Initialize the memory allocator \*/\
> void (\*xShutdown)(void\*); /\* Deinitialize the memory allocator \*/\
> void \*pAppData; /\* Argument to xInit() and xShutdown() \*/\
> };\
An instance of this object defines the interface between SQLite and low-level memory allocation routines.
This object is used in only one place in the SQLite interface. A pointer to an instance of this object is the argument to [sqlite3_config()](#sqlite3_config) when the configuration option is [SQLITE_CONFIG_MALLOC](#sqliteconfigmalloc) or [SQLITE_CONFIG_GETMALLOC](#sqliteconfiggetmalloc). By creating an instance of this object and passing it to [sqlite3_config](#sqlite3_config)([SQLITE_CONFIG_MALLOC](#sqliteconfigmalloc)) during configuration, an application can specify an alternative memory allocation subsystem for SQLite to use for all of its dynamic memory needs.
Note that SQLite comes with several [built-in memory allocators](malloc.md#altalloc) that are perfectly adequate for the overwhelming majority of applications and that this object is only useful to a tiny minority of applications with specialized memory allocation requirements. This object is also used during testing of SQLite in order to specify an alternative memory allocator that simulates memory out-of-memory conditions in order to verify that SQLite recovers gracefully from such conditions.
The xMalloc, xRealloc, and xFree methods must work like the malloc(), realloc() and free() functions from the standard C library. SQLite guarantees that the second argument to xRealloc is always a value returned by a prior call to xRoundup.
xSize should return the allocated size of a memory allocation previously obtained from xMalloc or xRealloc. The allocated size is always at least as big as the requested size but may be larger.
The xRoundup method returns what would be the allocated size of a memory allocation given a particular requested size. Most memory allocators round up memory allocations at least to the next multiple of 8. Some allocators round up to a larger multiple or to a power of 2. Every memory allocation request coming in through [sqlite3_malloc()](#sqlite3_free) or [sqlite3_realloc()](#sqlite3_free) first calls xRoundup. If xRoundup returns 0, that causes the corresponding memory allocation to fail.
The xInit method initializes the memory allocator. For example, it might allocate any required mutexes or initialize internal data structures. The xShutdown method is invoked (indirectly) by [sqlite3_shutdown()](#sqlite3_initialize) and should deallocate any resources acquired by xInit. The pAppData pointer is used as the only parameter to xInit and xShutdown.
SQLite holds the [SQLITE_MUTEX_STATIC_MAIN](#SQLITE_MUTEX_FAST) mutex when it invokes the xInit method, so the xInit method need not be threadsafe. The xShutdown method is only called from [sqlite3_shutdown()](#sqlite3_initialize) so it does not need to be threadsafe either. For all other methods, SQLite holds the [SQLITE_MUTEX_STATIC_MEM](#SQLITE_MUTEX_FAST) mutex as long as the [SQLITE_CONFIG_MEMSTATUS](#sqliteconfigmemstatus) configuration option is turned on (which it is by default) and so the methods are automatically serialized. However, if [SQLITE_CONFIG_MEMSTATUS](#sqliteconfigmemstatus) is disabled, then the other methods must be threadsafe or else make their own arrangements for serialization.
SQLite will never invoke xInit() more than once without an intervening call to xShutdown().
------------------------------------------------------------------------
## Mutex Handle
> \
> typedef struct sqlite3_mutex sqlite3_mutex;\
The mutex module within SQLite defines [sqlite3_mutex](#sqlite3_mutex) to be an abstract type for a mutex object. The SQLite core never looks at the internal representation of an [sqlite3_mutex](#sqlite3_mutex). It only deals with pointers to the [sqlite3_mutex](#sqlite3_mutex) object.
Mutexes are created using [sqlite3_mutex_alloc()](#sqlite3_mutex_alloc).
------------------------------------------------------------------------
## Mutex Methods Object
> \
> typedef struct sqlite3_mutex_methods sqlite3_mutex_methods;\
> struct sqlite3_mutex_methods {\
> int (\*xMutexInit)(void);\
> int (\*xMutexEnd)(void);\
> sqlite3_mutex \*(\*xMutexAlloc)(int);\
> void (\*xMutexFree)(sqlite3_mutex \*);\
> void (\*xMutexEnter)(sqlite3_mutex \*);\
> int (\*xMutexTry)(sqlite3_mutex \*);\
> void (\*xMutexLeave)(sqlite3_mutex \*);\
> int (\*xMutexHeld)(sqlite3_mutex \*);\
> int (\*xMutexNotheld)(sqlite3_mutex \*);\
> };\
An instance of this structure defines the low-level routines used to allocate and use mutexes.
Usually, the default mutex implementations provided by SQLite are sufficient, however the application has the option of substituting a custom implementation for specialized deployments or systems for which SQLite does not provide a suitable implementation. In this case, the application creates and populates an instance of this structure to pass to sqlite3_config() along with the [SQLITE_CONFIG_MUTEX](#sqliteconfigmutex) option. Additionally, an instance of this structure can be used as an output variable when querying the system for the current mutex implementation, using the [SQLITE_CONFIG_GETMUTEX](#sqliteconfiggetmutex) option.
The xMutexInit method defined by this structure is invoked as part of system initialization by the sqlite3_initialize() function. The xMutexInit routine is called by SQLite exactly once for each effective call to [sqlite3_initialize()](#sqlite3_initialize).
The xMutexEnd method defined by this structure is invoked as part of system shutdown by the sqlite3_shutdown() function. The implementation of this method is expected to release all outstanding resources obtained by the mutex methods implementation, especially those obtained by the xMutexInit method. The xMutexEnd() interface is invoked exactly once for each call to [sqlite3_shutdown()](#sqlite3_initialize).
The remaining seven methods defined by this structure (xMutexAlloc, xMutexFree, xMutexEnter, xMutexTry, xMutexLeave, xMutexHeld and xMutexNotheld) implement the following interfaces (respectively):
- [sqlite3_mutex_alloc()](#sqlite3_mutex_alloc)
- [sqlite3_mutex_free()](#sqlite3_mutex_alloc)
- [sqlite3_mutex_enter()](#sqlite3_mutex_alloc)
- [sqlite3_mutex_try()](#sqlite3_mutex_alloc)
- [sqlite3_mutex_leave()](#sqlite3_mutex_alloc)
- [sqlite3_mutex_held()](#sqlite3_mutex_held)
- [sqlite3_mutex_notheld()](#sqlite3_mutex_held)
The only difference is that the public sqlite3_XXX functions enumerated above silently ignore any invocations that pass a NULL pointer instead of a valid mutex handle. The implementations of the methods defined by this structure are not required to handle this case. The results of passing a NULL pointer instead of a valid mutex handle are undefined (i.e. it is acceptable to provide an implementation that segfaults if it is passed a NULL pointer).
The xMutexInit() method must be threadsafe. It must be harmless to invoke xMutexInit() multiple times within the same process and without intervening calls to xMutexEnd(). Second and subsequent calls to xMutexInit() must be no-ops.
xMutexInit() must not use SQLite memory allocation ([sqlite3_malloc()](#sqlite3_free) and its associates). Similarly, xMutexAlloc() must not use SQLite memory allocation for a static mutex. However xMutexAlloc() may use SQLite memory allocation for a fast or recursive mutex.
SQLite will invoke the xMutexEnd() method when [sqlite3_shutdown()](#sqlite3_initialize) is called, but only if the prior call to xMutexInit returned SQLITE_OK. If xMutexInit fails in any way, it is expected to clean up after itself prior to returning.
------------------------------------------------------------------------
## Custom Page Cache Object
> \
> typedef struct sqlite3_pcache sqlite3_pcache;\
The sqlite3_pcache type is opaque. It is implemented by the pluggable module. The SQLite core has no knowledge of its size or internal structure and never deals with the sqlite3_pcache object except by holding and passing pointers to the object.
See [sqlite3_pcache_methods2](#sqlite3_pcache_methods2) for additional information.
------------------------------------------------------------------------
## Custom Page Cache Object
> \
> typedef struct sqlite3_pcache_page sqlite3_pcache_page;\
> struct sqlite3_pcache_page {\
> void \*pBuf; /\* The content of the page \*/\
> void \*pExtra; /\* Extra information associated with the page \*/\
> };\
The sqlite3_pcache_page object represents a single page in the page cache. The page cache will allocate instances of this object. Various methods of the page cache use pointers to instances of this object as parameters or as their return value.
See [sqlite3_pcache_methods2](#sqlite3_pcache_methods2) for additional information.
------------------------------------------------------------------------
## Name Of The Folder Holding Temporary Files
> \
> SQLITE_EXTERN char \*sqlite3_temp_directory;\
If this global variable is made to point to a string which is the name of a folder (a.k.a. directory), then all temporary files created by SQLite when using a built-in [VFS](#sqlite3_vfs) will be placed in that directory. If this variable is a NULL pointer, then SQLite performs a search for an appropriate temporary file directory.
Applications are strongly discouraged from using this global variable. It is required to set a temporary folder on Windows Runtime (WinRT). But for all other platforms, it is highly recommended that applications neither read nor write this variable. This global variable is a relic that exists for backwards compatibility of legacy applications and should be avoided in new projects.
It is not safe to read or modify this variable in more than one thread at a time. It is not safe to read or modify this variable if a [database connection](#sqlite3) is being used at the same time in a separate thread. It is intended that this variable be set once as part of process initialization and before any SQLite interface routines have been called and that this variable remain unchanged thereafter.
The [temp_store_directory pragma](pragma.md#pragma_temp_store_directory) may modify this variable and cause it to point to memory obtained from [sqlite3_malloc](#sqlite3_free). Furthermore, the [temp_store_directory pragma](pragma.md#pragma_temp_store_directory) always assumes that any string that this variable points to is held in memory obtained from [sqlite3_malloc](#sqlite3_free) and the pragma may attempt to free that memory using [sqlite3_free](#sqlite3_free). Hence, if this variable is modified directly, either it should be made NULL or made to point to memory obtained from [sqlite3_malloc](#sqlite3_free) or else the use of the [temp_store_directory pragma](pragma.md#pragma_temp_store_directory) should be avoided. Except when requested by the [temp_store_directory pragma](pragma.md#pragma_temp_store_directory), SQLite does not free the memory that sqlite3_temp_directory points to. If the application wants that memory to be freed, it must do so itself, taking care to only do so after all [database connection](#sqlite3) objects have been destroyed.
**Note to Windows Runtime users:** The temporary directory must be set prior to calling [sqlite3_open](#sqlite3_open) or [sqlite3_open_v2](#sqlite3_open). Otherwise, various features that require the use of temporary files may fail. Here is an example of how to do this using C++ with the Windows Runtime:
> \
> LPCWSTR zPath = Windows::Storage::ApplicationData::Current-\>\
> TemporaryFolder-\>Path-\>Data();\
> char zPathBuf\[MAX_PATH + 1\];\
> memset(zPathBuf, 0, sizeof(zPathBuf));\
> WideCharToMultiByte(CP_UTF8, 0, zPath, -1, zPathBuf, sizeof(zPathBuf),\
> NULL, NULL);\
> sqlite3_temp_directory = sqlite3_mprintf("%s", zPathBuf);\
------------------------------------------------------------------------
## OS Interface Object
> \
> typedef struct sqlite3_vfs sqlite3_vfs;\
> typedef void (\*sqlite3_syscall_ptr)(void);\
> struct sqlite3_vfs {\
> int iVersion; /\* Structure version number (currently 3) \*/\
> int szOsFile; /\* Size of subclassed sqlite3_file \*/\
> int mxPathname; /\* Maximum file pathname length \*/\
> sqlite3_vfs \*pNext; /\* Next registered VFS \*/\
> const char \*zName; /\* Name of this virtual file system \*/\
> void \*pAppData; /\* Pointer to application-specific data \*/\
> int (\*xOpen)(sqlite3_vfs\*, sqlite3_filename zName, sqlite3_file\*,\
> int flags, int \*pOutFlags);\
> int (\*xDelete)(sqlite3_vfs\*, const char \*zName, int syncDir);\
> int (\*xAccess)(sqlite3_vfs\*, const char \*zName, int flags, int \*pResOut);\
> int (\*xFullPathname)(sqlite3_vfs\*, const char \*zName, int nOut, char \*zOut);\
> void \*(\*xDlOpen)(sqlite3_vfs\*, const char \*zFilename);\
> void (\*xDlError)(sqlite3_vfs\*, int nByte, char \*zErrMsg);\
> void (\*(\*xDlSym)(sqlite3_vfs\*,void\*, const char \*zSymbol))(void);\
> void (\*xDlClose)(sqlite3_vfs\*, void\*);\
> int (\*xRandomness)(sqlite3_vfs\*, int nByte, char \*zOut);\
> int (\*xSleep)(sqlite3_vfs\*, int microseconds);\
> int (\*xCurrentTime)(sqlite3_vfs\*, double\*);\
> int (\*xGetLastError)(sqlite3_vfs\*, int, char \*);\
> /\*\
> \*\* The methods above are in version 1 of the sqlite_vfs object\
> \*\* definition. Those that follow are added in version 2 or later\
> \*/\
> int (\*xCurrentTimeInt64)(sqlite3_vfs\*, sqlite3_int64\*);\
> /\*\
> \*\* The methods above are in versions 1 and 2 of the sqlite_vfs object.\
> \*\* Those below are for version 3 and greater.\
> \*/\
> int (\*xSetSystemCall)(sqlite3_vfs\*, const char \*zName, sqlite3_syscall_ptr);\
> sqlite3_syscall_ptr (\*xGetSystemCall)(sqlite3_vfs\*, const char \*zName);\
> const char \*(\*xNextSystemCall)(sqlite3_vfs\*, const char \*zName);\
> /\*\
> \*\* The methods above are in versions 1 through 3 of the sqlite_vfs object.\
> \*\* New fields may be appended in future versions. The iVersion\
> \*\* value will increment whenever this happens.\
> \*/\
> };\
An instance of the sqlite3_vfs object defines the interface between the SQLite core and the underlying operating system. The "vfs" in the name of the object stands for "virtual file system". See the [VFS documentation](vfs.md) for further information.
The VFS interface is sometimes extended by adding new methods onto the end. Each time such an extension occurs, the iVersion field is incremented. The iVersion value started out as 1 in SQLite [version 3.5.0](releaselog/3_5_0.md) on 2007-09-04, then increased to 2 with SQLite [version 3.7.0](releaselog/3_7_0.md) on 2010-07-21, and then increased to 3 with SQLite [version 3.7.6](releaselog/3_7_6.md) on 2011-04-12. Additional fields may be appended to the sqlite3_vfs object and the iVersion value may increase again in future versions of SQLite. Note that due to an oversight, the structure of the sqlite3_vfs object changed in the transition from SQLite [version 3.5.9](releaselog/3_5_9.md) to [version 3.6.0](releaselog/3_6_0.md) on 2008-07-16 and yet the iVersion field was not increased.
The szOsFile field is the size of the subclassed [sqlite3_file](#sqlite3_file) structure used by this VFS. mxPathname is the maximum length of a pathname in this VFS.
Registered sqlite3_vfs objects are kept on a linked list formed by the pNext pointer. The [sqlite3_vfs_register()](#sqlite3_vfs_find) and [sqlite3_vfs_unregister()](#sqlite3_vfs_find) interfaces manage this list in a thread-safe way. The [sqlite3_vfs_find()](#sqlite3_vfs_find) interface searches the list. Neither the application code nor the VFS implementation should use the pNext pointer.
The pNext field is the only field in the sqlite3_vfs structure that SQLite will ever modify. SQLite will only access or modify this field while holding a particular static mutex. The application should never modify anything within the sqlite3_vfs object once the object has been registered.
The zName field holds the name of the VFS module. The name must be unique across all VFS modules.
SQLite guarantees that the zFilename parameter to xOpen is either a NULL pointer or string obtained from xFullPathname() with an optional suffix added. If a suffix is added to the zFilename parameter, it will consist of a single "-" character followed by no more than 11 alphanumeric and/or "-" characters. SQLite further guarantees that the string will be valid and unchanged until xClose() is called. Because of the previous sentence, the [sqlite3_file](#sqlite3_file) can safely store a pointer to the filename if it needs to remember the filename for some reason. If the zFilename parameter to xOpen is a NULL pointer then xOpen must invent its own temporary name for the file. Whenever the xFilename parameter is NULL it will also be the case that the flags parameter will include [SQLITE_OPEN_DELETEONCLOSE](#SQLITE_OPEN_AUTOPROXY).
The flags argument to xOpen() includes all bits set in the flags argument to [sqlite3_open_v2()](#sqlite3_open). Or if [sqlite3_open()](#sqlite3_open) or [sqlite3_open16()](#sqlite3_open) is used, then flags includes at least [SQLITE_OPEN_READWRITE](#SQLITE_OPEN_AUTOPROXY) \| [SQLITE_OPEN_CREATE](#SQLITE_OPEN_AUTOPROXY). If xOpen() opens a file read-only then it sets \*pOutFlags to include [SQLITE_OPEN_READONLY](#SQLITE_OPEN_AUTOPROXY). Other bits in \*pOutFlags may be set.
SQLite will also add one of the following flags to the xOpen() call, depending on the object being opened:
- [SQLITE_OPEN_MAIN_DB](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_MAIN_JOURNAL](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_TEMP_DB](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_TEMP_JOURNAL](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_TRANSIENT_DB](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_SUBJOURNAL](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_SUPER_JOURNAL](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_WAL](#SQLITE_OPEN_AUTOPROXY)
The file I/O implementation can use the object type flags to change the way it deals with files. For example, an application that does not care about crash recovery or rollback might make the open of a journal file a no-op. Writes to this journal would also be no-ops, and any attempt to read the journal would return SQLITE_IOERR. Or the implementation might recognize that a database file will be doing page-aligned sector reads and writes in a random order and set up its I/O subsystem accordingly.
SQLite might also add one of the following flags to the xOpen method:
- [SQLITE_OPEN_DELETEONCLOSE](#SQLITE_OPEN_AUTOPROXY)
- [SQLITE_OPEN_EXCLUSIVE](#SQLITE_OPEN_AUTOPROXY)
The [SQLITE_OPEN_DELETEONCLOSE](#SQLITE_OPEN_AUTOPROXY) flag means the file should be deleted when it is closed. The [SQLITE_OPEN_DELETEONCLOSE](#SQLITE_OPEN_AUTOPROXY) will be set for TEMP databases and their journals, transient databases, and subjournals.
The [SQLITE_OPEN_EXCLUSIVE](#SQLITE_OPEN_AUTOPROXY) flag is always used in conjunction with the [SQLITE_OPEN_CREATE](#SQLITE_OPEN_AUTOPROXY) flag, which are both directly analogous to the O_EXCL and O_CREAT flags of the POSIX open() API. The SQLITE_OPEN_EXCLUSIVE flag, when paired with the SQLITE_OPEN_CREATE, is used to indicate that file should always be created, and that it is an error if it already exists. It is *not* used to indicate the file should be opened for exclusive access.
At least szOsFile bytes of memory are allocated by SQLite to hold the [sqlite3_file](#sqlite3_file) structure passed as the third argument to xOpen. The xOpen method does not have to allocate the structure; it should just fill it in. Note that the xOpen method must set the sqlite3_file.pMethods to either a valid [sqlite3_io_methods](#sqlite3_io_methods) object or to NULL. xOpen must do this even if the open fails. SQLite expects that the sqlite3_file.pMethods element will be valid after xOpen returns regardless of the success or failure of the xOpen call.
The flags argument to xAccess() may be [SQLITE_ACCESS_EXISTS](#SQLITE_ACCESS_EXISTS) to test for the existence of a file, or [SQLITE_ACCESS_READWRITE](#SQLITE_ACCESS_EXISTS) to test whether a file is readable and writable, or [SQLITE_ACCESS_READ](#SQLITE_ACCESS_EXISTS) to test whether a file is at least readable. The SQLITE_ACCESS_READ flag is never actually used and is not implemented in the built-in VFSes of SQLite. The file is named by the second argument and can be a directory. The xAccess method returns [SQLITE_OK](#SQLITE_ABORT) on success or some non-zero error code if there is an I/O error or if the name of the file given in the second argument is illegal. If SQLITE_OK is returned, then non-zero or zero is written into \*pResOut to indicate whether or not the file is accessible.
SQLite will always allocate at least mxPathname+1 bytes for the output buffer xFullPathname. The exact size of the output buffer is also passed as a parameter to both methods. If the output buffer is not large enough, [SQLITE_CANTOPEN](#SQLITE_ABORT) should be returned. Since this is handled as a fatal error by SQLite, vfs implementations should endeavor to prevent this by setting mxPathname to a sufficiently large value.
The xRandomness(), xSleep(), xCurrentTime(), and xCurrentTimeInt64() interfaces are not strictly a part of the filesystem, but they are included in the VFS structure for completeness. The xRandomness() function attempts to return nBytes bytes of good-quality randomness into zOut. The return value is the actual number of bytes of randomness obtained. The xSleep() method causes the calling thread to sleep for at least the number of microseconds given. The xCurrentTime() method returns a Julian Day Number for the current date and time as a floating point value. The xCurrentTimeInt64() method returns, as an integer, the Julian Day Number multiplied by 86400000 (the number of milliseconds in a 24-hour day). SQLite will use the xCurrentTimeInt64() method to get the current date and time if that method is available (if iVersion is 2 or greater and the function pointer is not NULL) and will fall back to xCurrentTime() if xCurrentTimeInt64() is unavailable.
The xSetSystemCall(), xGetSystemCall(), and xNextSystemCall() interfaces are not used by the SQLite core. These optional interfaces are provided by some VFSes to facilitate testing of the VFS code. By overriding system calls with functions under its control, a test program can simulate faults and error conditions that would otherwise be difficult or impossible to induce. The set of system calls that can be overridden varies from one VFS to another, and from one version of the same VFS to the next. Applications that use these interfaces must be prepared for any or all of these interfaces to be NULL or for their behavior to change from one release to the next. Applications must not attempt to access any of these methods if the iVersion of the VFS is less than 3.
------------------------------------------------------------------------
## Virtual Table Instance Object
> \
> struct sqlite3_vtab {\
> const sqlite3_module \*pModule; /\* The module for this virtual table \*/\
> int nRef; /\* Number of open cursors \*/\
> char \*zErrMsg; /\* Error message from sqlite3_mprintf() \*/\
> /\* Virtual table implementations will typically add additional fields \*/\
> };\
Every [virtual table module](#sqlite3_module) implementation uses a subclass of this object to describe a particular instance of the [virtual table](vtab.md). Each subclass will be tailored to the specific needs of the module implementation. The purpose of this superclass is to define certain fields that are common to all module implementations.
Virtual tables methods can set an error message by assigning a string obtained from [sqlite3_mprintf()](#sqlite3_mprintf) to zErrMsg. The method should take care that any prior string is freed by a call to [sqlite3_free()](#sqlite3_free) prior to assigning a new string to zErrMsg. After the error message is delivered up to the client application, the string will be automatically freed by sqlite3_free() and the zErrMsg field will be zeroed.
------------------------------------------------------------------------
## Obtain Aggregate Function Context
> \
> void \*sqlite3_aggregate_context(sqlite3_context\*, int nBytes);\
Implementations of aggregate SQL functions use this routine to allocate memory for storing their state.
The first time the sqlite3_aggregate_context(C,N) routine is called for a particular aggregate function, SQLite allocates N bytes of memory, zeroes out that memory, and returns a pointer to the new memory. On second and subsequent calls to sqlite3_aggregate_context() for the same aggregate function instance, the same buffer is returned. Sqlite3_aggregate_context() is normally called once for each invocation of the xStep callback and then one last time when the xFinal callback is invoked. When no rows match an aggregate query, the xStep() callback of the aggregate function implementation is never called and xFinal() is called exactly once. In those cases, sqlite3_aggregate_context() might be called for the first time from within xFinal().
The sqlite3_aggregate_context(C,N) routine returns a NULL pointer when first called if N is less than or equal to zero or if a memory allocation error occurs.
The amount of space allocated by sqlite3_aggregate_context(C,N) is determined by the N parameter on the first successful call. Changing the value of N in any subsequent call to sqlite3_aggregate_context() within the same aggregate function instance will not resize the memory allocation. Within the xFinal callback, it is customary to set N=0 in calls to sqlite3_aggregate_context(C,N) so that no pointless memory allocations occur.
SQLite automatically frees the memory allocated by sqlite3_aggregate_context() when the aggregate query concludes.
The first parameter must be a copy of the [SQL function context](#sqlite3_context) that is the first parameter to the xStep or xFinal callback routine that implements the aggregate function.
This routine must be called from the same thread in which the aggregate SQL function is running.
------------------------------------------------------------------------
## Automatically Load Statically Linked Extensions
> \
> int sqlite3_auto_extension(void(\*xEntryPoint)(void));\
This interface causes the xEntryPoint() function to be invoked for each new [database connection](#sqlite3) that is created. The idea here is that xEntryPoint() is the entry point for a statically linked [SQLite extension](loadext.md) that is to be automatically loaded into all new database connections.
Even though the function prototype shows that xEntryPoint() takes no arguments and returns void, SQLite invokes xEntryPoint() with three arguments and expects an integer result as if the signature of the entry point were as follows:
> \
> int xEntryPoint(\
> sqlite3 \*db,\
> char \*\*pzErrMsg,\
> const struct sqlite3_api_routines \*pThunk\
> );\
If the xEntryPoint routine encounters an error, it should make \*pzErrMsg point to an appropriate error message (obtained from [sqlite3_mprintf()](#sqlite3_mprintf)) and return an appropriate [error code](rescode.md). SQLite ensures that \*pzErrMsg is NULL before calling the xEntryPoint(). SQLite will invoke [sqlite3_free()](#sqlite3_free) on \*pzErrMsg after xEntryPoint() returns. If any xEntryPoint() returns an error, the [sqlite3_open()](#sqlite3_open), [sqlite3_open16()](#sqlite3_open), or [sqlite3_open_v2()](#sqlite3_open) call that provoked the xEntryPoint() will fail.
Calling sqlite3_auto_extension(X) with an entry point X that is already on the list of automatic extensions is a harmless no-op. No entry point will be called more than once for each database connection that is opened.
See also: [sqlite3_reset_auto_extension()](#sqlite3_reset_auto_extension) and [sqlite3_cancel_auto_extension()](#sqlite3_cancel_auto_extension)
------------------------------------------------------------------------
## Autovacuum Compaction Amount Callback
> \
> int sqlite3_autovacuum_pages(\
> sqlite3 \*db,\
> unsigned int(\*)(void\*,const char\*,unsigned int,unsigned int,unsigned int),\
> void\*,\
> void(\*)(void\*)\
> );\
The sqlite3_autovacuum_pages(D,C,P,X) interface registers a callback function C that is invoked prior to each autovacuum of the database file. The callback is passed a copy of the generic data pointer (P), the schema-name of the attached database that is being autovacuumed, the size of the database file in pages, the number of free pages, and the number of bytes per page, respectively. The callback should return the number of free pages that should be removed by the autovacuum. If the callback returns zero, then no autovacuum happens. If the value returned is greater than or equal to the number of free pages, then a complete autovacuum happens.
If there are multiple ATTACH-ed database files that are being modified as part of a transaction commit, then the autovacuum pages callback is invoked separately for each file.
**The callback is not reentrant.** The callback function should not attempt to invoke any other SQLite interface. If it does, bad things may happen, including segmentation faults and corrupt database files. The callback function should be a simple function that does some arithmetic on its input parameters and returns a result.
The X parameter to sqlite3_autovacuum_pages(D,C,P,X) is an optional destructor for the P parameter. If X is not NULL, then X(P) is invoked whenever the database connection closes or when the callback is overwritten by another invocation of sqlite3_autovacuum_pages().
There is only one autovacuum pages callback per database connection. Each call to the sqlite3_autovacuum_pages() interface overrides all previous invocations for that database connection. If the callback argument (C) to sqlite3_autovacuum_pages(D,C,P,X) is a NULL pointer, then the autovacuum steps callback is canceled. The return value from sqlite3_autovacuum_pages() is normally SQLITE_OK, but might be some other error code if something goes wrong. The current implementation will only return SQLITE_OK or SQLITE_MISUSE, but other return codes might be added in future releases.
If no autovacuum pages callback is specified (the usual case) or a NULL pointer is provided for the callback, then the default behavior is to vacuum all free pages. So, in other words, the default behavior is the same as if the callback function were something like this:
> \
> unsigned int demonstration_autovac_pages_callback(\
> void \*pClientData,\
> const char \*zSchema,\
> unsigned int nDbPage,\
> unsigned int nFreePage,\
> unsigned int nBytePerPage\
> ){\
> return nFreePage;\
> }\
------------------------------------------------------------------------
## Number Of SQL Parameters
> \
> int sqlite3_bind_parameter_count(sqlite3_stmt\*);\
This routine can be used to find the number of [SQL parameters](#sqlite3_bind_blob) in a [prepared statement](#sqlite3_stmt). SQL parameters are tokens of the form "?", "?NNN", ":AAA", "\$AAA", or "@AAA" that serve as placeholders for values that are [bound](#sqlite3_bind_blob) to the parameters at a later time.
This routine actually returns the index of the largest (rightmost) parameter. For all forms except ?NNN, this will correspond to the number of unique parameters. If parameters of the ?NNN form are used, there may be gaps in the list.
See also: [sqlite3_bind()](#sqlite3_bind_blob), [sqlite3_bind_parameter_name()](#sqlite3_bind_parameter_name), and [sqlite3_bind_parameter_index()](#sqlite3_bind_parameter_index).
------------------------------------------------------------------------
## Index Of A Parameter With A Given Name
> \
> int sqlite3_bind_parameter_index(sqlite3_stmt\*, const char \*zName);\
Return the index of an SQL parameter given its name. The index value returned is suitable for use as the second parameter to [sqlite3_bind()](#sqlite3_bind_blob). A zero is returned if no matching parameter is found. The parameter name must be given in UTF-8 even if the original statement was prepared from UTF-16 text using [sqlite3_prepare16_v2()](#sqlite3_prepare) or [sqlite3_prepare16_v3()](#sqlite3_prepare).
See also: [sqlite3_bind()](#sqlite3_bind_blob), [sqlite3_bind_parameter_count()](#sqlite3_bind_parameter_count), and [sqlite3_bind_parameter_name()](#sqlite3_bind_parameter_name).
------------------------------------------------------------------------
## Name Of A Host Parameter
> \
> const char \*sqlite3_bind_parameter_name(sqlite3_stmt\*, int);\
The sqlite3_bind_parameter_name(P,N) interface returns the name of the N-th [SQL parameter](#sqlite3_bind_blob) in the [prepared statement](#sqlite3_stmt) P. SQL parameters of the form "?NNN" or ":AAA" or "@AAA" or "\$AAA" have a name which is the string "?NNN" or ":AAA" or "@AAA" or "\$AAA" respectively. In other words, the initial ":" or "\$" or "@" or "?" is included as part of the name. Parameters of the form "?" without a following integer have no name and are referred to as "nameless" or "anonymous parameters".
The first host parameter has an index of 1, not 0.
If the value N is out of range or if the N-th parameter is nameless, then NULL is returned. The returned string is always in UTF-8 encoding even if the named parameter was originally specified as UTF-16 in [sqlite3_prepare16()](#sqlite3_prepare), [sqlite3_prepare16_v2()](#sqlite3_prepare), or [sqlite3_prepare16_v3()](#sqlite3_prepare).
See also: [sqlite3_bind()](#sqlite3_bind_blob), [sqlite3_bind_parameter_count()](#sqlite3_bind_parameter_count), and [sqlite3_bind_parameter_index()](#sqlite3_bind_parameter_index).
------------------------------------------------------------------------
## Return The Size Of An Open BLOB
> \
> int sqlite3_blob_bytes(sqlite3_blob \*);\
Returns the size in bytes of the BLOB accessible via the successfully opened [BLOB handle](#sqlite3_blob) in its only argument. The incremental blob I/O routines can only read or overwrite existing blob content; they cannot change the size of a blob.
This routine only works on a [BLOB handle](#sqlite3_blob) which has been created by a prior successful call to [sqlite3_blob_open()](#sqlite3_blob_open) and which has not been closed by [sqlite3_blob_close()](#sqlite3_blob_close). Passing any other pointer in to this routine results in undefined and probably undesirable behavior.
------------------------------------------------------------------------
## Close A BLOB Handle
> \
> int sqlite3_blob_close(sqlite3_blob \*);\
This function closes an open [BLOB handle](#sqlite3_blob). The BLOB handle is closed unconditionally. Even if this routine returns an error code, the handle is still closed.
If the blob handle being closed was opened for read-write access, and if the database is in auto-commit mode and there are no other open read-write blob handles or active write statements, the current transaction is committed. If an error occurs while committing the transaction, an error code is returned and the transaction rolled back.
Calling this function with an argument that is not a NULL pointer or an open blob handle results in undefined behavior. Calling this routine with a null pointer (such as would be returned by a failed call to [sqlite3_blob_open()](#sqlite3_blob_open)) is a harmless no-op. Otherwise, if this function is passed a valid open blob handle, the values returned by the sqlite3_errcode() and sqlite3_errmsg() functions are set before returning.
------------------------------------------------------------------------
## Open A BLOB For Incremental I/O
> \
> int sqlite3_blob_open(\
> sqlite3\*,\
> const char \*zDb,\
> const char \*zTable,\
> const char \*zColumn,\
> sqlite3_int64 iRow,\
> int flags,\
> sqlite3_blob \*\*ppBlob\
> );\
This interfaces opens a [handle](#sqlite3_blob) to the BLOB located in row iRow, column zColumn, table zTable in database zDb; in other words, the same BLOB that would be selected by:
\
SELECT zColumn FROM zDb.zTable WHERE [rowid](lang_createtable.md#rowid) = iRow;\
Parameter zDb is not the filename that contains the database, but rather the symbolic name of the database. For attached databases, this is the name that appears after the AS keyword in the [ATTACH](lang_attach.md) statement. For the main database file, the database name is "main". For TEMP tables, the database name is "temp".
If the flags parameter is non-zero, then the BLOB is opened for read and write access. If the flags parameter is zero, the BLOB is opened for read-only access.
On success, [SQLITE_OK](#SQLITE_ABORT) is returned and the new [BLOB handle](#sqlite3_blob) is stored in \*ppBlob. Otherwise an [error code](rescode.md) is returned and, unless the error code is SQLITE_MISUSE, \*ppBlob is set to NULL. This means that, provided the API is not misused, it is always safe to call [sqlite3_blob_close()](#sqlite3_blob_close) on \*ppBlob after this function returns.
This function fails with SQLITE_ERROR if any of the following are true:
- Database zDb does not exist,
- Table zTable does not exist within database zDb,
- Table zTable is a WITHOUT ROWID table,
- Column zColumn does not exist,
- Row iRow is not present in the table,
- The specified column of row iRow contains a value that is not a TEXT or BLOB value,
- Column zColumn is part of an index, PRIMARY KEY or UNIQUE constraint and the blob is being opened for read/write access,
- [Foreign key constraints](foreignkeys.md) are enabled, column zColumn is part of a [child key](foreignkeys.md#parentchild) definition and the blob is being opened for read/write access.
Unless it returns SQLITE_MISUSE, this function sets the [database connection](#sqlite3) error code and message accessible via [sqlite3_errcode()](#sqlite3_errcode) and [sqlite3_errmsg()](#sqlite3_errcode) and related functions.
A BLOB referenced by sqlite3_blob_open() may be read using the [sqlite3_blob_read()](#sqlite3_blob_read) interface and modified by using [sqlite3_blob_write()](#sqlite3_blob_write). The [BLOB handle](#sqlite3_blob) can be moved to a different row of the same table using the [sqlite3_blob_reopen()](#sqlite3_blob_reopen) interface. However, the column, table, or database of a [BLOB handle](#sqlite3_blob) cannot be changed after the [BLOB handle](#sqlite3_blob) is opened.
If the row that a BLOB handle points to is modified by an [UPDATE](lang_update.md), [DELETE](lang_delete.md), or by [ON CONFLICT](lang_conflict.md) side-effects then the BLOB handle is marked as "expired". This is true if any column of the row is changed, even a column other than the one the BLOB handle is open on. Calls to [sqlite3_blob_read()](#sqlite3_blob_read) and [sqlite3_blob_write()](#sqlite3_blob_write) for an expired BLOB handle fail with a return code of [SQLITE_ABORT](#SQLITE_ABORT). Changes written into a BLOB prior to the BLOB expiring are not rolled back by the expiration of the BLOB. Such changes will eventually commit if the transaction continues to completion.
Use the [sqlite3_blob_bytes()](#sqlite3_blob_bytes) interface to determine the size of the opened blob. The size of a blob may not be changed by this interface. Use the [UPDATE](lang_update.md) SQL command to change the size of a blob.
The [sqlite3_bind_zeroblob()](#sqlite3_bind_blob) and [sqlite3_result_zeroblob()](#sqlite3_result_blob) interfaces and the built-in [zeroblob](lang_corefunc.md#zeroblob) SQL function may be used to create a zero-filled blob to read or write using the incremental-blob interface.
To avoid a resource leak, every open [BLOB handle](#sqlite3_blob) should eventually be released by a call to [sqlite3_blob_close()](#sqlite3_blob_close).
See also: [sqlite3_blob_close()](#sqlite3_blob_close), [sqlite3_blob_reopen()](#sqlite3_blob_reopen), [sqlite3_blob_read()](#sqlite3_blob_read), [sqlite3_blob_bytes()](#sqlite3_blob_bytes), [sqlite3_blob_write()](#sqlite3_blob_write).
------------------------------------------------------------------------
## Read Data From A BLOB Incrementally
> \
> int sqlite3_blob_read(sqlite3_blob \*, void \*Z, int N, int iOffset);\
This function is used to read data from an open [BLOB handle](#sqlite3_blob) into a caller-supplied buffer. N bytes of data are copied into buffer Z from the open BLOB, starting at offset iOffset.
If offset iOffset is less than N bytes from the end of the BLOB, [SQLITE_ERROR](#SQLITE_ABORT) is returned and no data is read. If N or iOffset is less than zero, [SQLITE_ERROR](#SQLITE_ABORT) is returned and no data is read. The size of the blob (and hence the maximum value of N+iOffset) can be determined using the [sqlite3_blob_bytes()](#sqlite3_blob_bytes) interface.
An attempt to read from an expired [BLOB handle](#sqlite3_blob) fails with an error code of [SQLITE_ABORT](#SQLITE_ABORT).
On success, sqlite3_blob_read() returns SQLITE_OK. Otherwise, an [error code](rescode.md) or an [extended error code](rescode.md#extrc) is returned.
This routine only works on a [BLOB handle](#sqlite3_blob) which has been created by a prior successful call to [sqlite3_blob_open()](#sqlite3_blob_open) and which has not been closed by [sqlite3_blob_close()](#sqlite3_blob_close). Passing any other pointer in to this routine results in undefined and probably undesirable behavior.
See also: [sqlite3_blob_write()](#sqlite3_blob_write).
------------------------------------------------------------------------
## Move a BLOB Handle to a New Row
> \
> int sqlite3_blob_reopen(sqlite3_blob \*, sqlite3_int64);\
This function is used to move an existing [BLOB handle](#sqlite3_blob) so that it points to a different row of the same database table. The new row is identified by the rowid value passed as the second argument. Only the row can be changed. The database, table and column on which the blob handle is open remain the same. Moving an existing [BLOB handle](#sqlite3_blob) to a new row is faster than closing the existing handle and opening a new one.
The new row must meet the same criteria as for [sqlite3_blob_open()](#sqlite3_blob_open) - it must exist and there must be either a blob or text value stored in the nominated column. If the new row is not present in the table, or if it does not contain a blob or text value, or if another error occurs, an SQLite error code is returned and the blob handle is considered aborted. All subsequent calls to [sqlite3_blob_read()](#sqlite3_blob_read), [sqlite3_blob_write()](#sqlite3_blob_write) or [sqlite3_blob_reopen()](#sqlite3_blob_reopen) on an aborted blob handle immediately return SQLITE_ABORT. Calling [sqlite3_blob_bytes()](#sqlite3_blob_bytes) on an aborted blob handle always returns zero.
This function sets the database handle error code and message.
------------------------------------------------------------------------
## Write Data Into A BLOB Incrementally
> \
> int sqlite3_blob_write(sqlite3_blob \*, const void \*z, int n, int iOffset);\
This function is used to write data into an open [BLOB handle](#sqlite3_blob) from a caller-supplied buffer. N bytes of data are copied from the buffer Z into the open BLOB, starting at offset iOffset.
On success, sqlite3_blob_write() returns SQLITE_OK. Otherwise, an [error code](rescode.md) or an [extended error code](rescode.md#extrc) is returned. Unless SQLITE_MISUSE is returned, this function sets the [database connection](#sqlite3) error code and message accessible via [sqlite3_errcode()](#sqlite3_errcode) and [sqlite3_errmsg()](#sqlite3_errcode) and related functions.
If the [BLOB handle](#sqlite3_blob) passed as the first argument was not opened for writing (the flags parameter to [sqlite3_blob_open()](#sqlite3_blob_open) was zero), this function returns [SQLITE_READONLY](#SQLITE_ABORT).
This function may only modify the contents of the BLOB; it is not possible to increase the size of a BLOB using this API. If offset iOffset is less than N bytes from the end of the BLOB, [SQLITE_ERROR](#SQLITE_ABORT) is returned and no data is written. The size of the BLOB (and hence the maximum value of N+iOffset) can be determined using the [sqlite3_blob_bytes()](#sqlite3_blob_bytes) interface. If N or iOffset are less than zero [SQLITE_ERROR](#SQLITE_ABORT) is returned and no data is written.
An attempt to write to an expired [BLOB handle](#sqlite3_blob) fails with an error code of [SQLITE_ABORT](#SQLITE_ABORT). Writes to the BLOB that occurred before the [BLOB handle](#sqlite3_blob) expired are not rolled back by the expiration of the handle, though of course those changes might have been overwritten by the statement that expired the BLOB handle or by other independent statements.
This routine only works on a [BLOB handle](#sqlite3_blob) which has been created by a prior successful call to [sqlite3_blob_open()](#sqlite3_blob_open) and which has not been closed by [sqlite3_blob_close()](#sqlite3_blob_close). Passing any other pointer in to this routine results in undefined and probably undesirable behavior.
See also: [sqlite3_blob_read()](#sqlite3_blob_read).
------------------------------------------------------------------------
## Set A Busy Timeout
> \
> int sqlite3_busy_timeout(sqlite3\*, int ms);\
This routine sets a [busy handler](#sqlite3_busy_handler) that sleeps for a specified amount of time when a table is locked. The handler will sleep multiple times until at least "ms" milliseconds of sleeping have accumulated. After at least "ms" milliseconds of sleeping, the handler returns 0 which causes [sqlite3_step()](#sqlite3_step) to return [SQLITE_BUSY](#SQLITE_ABORT).
Calling this routine with an argument less than or equal to zero turns off all busy handlers.
There can only be a single busy handler for a particular [database connection](#sqlite3) at any given moment. If another busy handler was defined (using [sqlite3_busy_handler()](#sqlite3_busy_handler)) prior to calling this routine, that other busy handler is cleared.
See also: [PRAGMA busy_timeout](pragma.md#pragma_busy_timeout)
------------------------------------------------------------------------
## Cancel Automatic Extension Loading
> \
> int sqlite3_cancel_auto_extension(void(\*xEntryPoint)(void));\
The [sqlite3_cancel_auto_extension(X)](#sqlite3_cancel_auto_extension) interface unregisters the initialization routine X that was registered using a prior call to [sqlite3_auto_extension(X)](#sqlite3_auto_extension). The [sqlite3_cancel_auto_extension(X)](#sqlite3_cancel_auto_extension) routine returns 1 if initialization routine X was successfully unregistered and it returns 0 if X was not on the list of initialization routines.
------------------------------------------------------------------------
## Reset All Bindings On A Prepared Statement
> \
> int sqlite3_clear_bindings(sqlite3_stmt\*);\
Contrary to the intuition of many, [sqlite3_reset()](#sqlite3_reset) does not reset the [bindings](#sqlite3_bind_blob) on a [prepared statement](#sqlite3_stmt). Use this routine to reset all host parameters to NULL.
------------------------------------------------------------------------
## Number Of Columns In A Result Set
> \
> int sqlite3_column_count(sqlite3_stmt \*pStmt);\
Return the number of columns in the result set returned by the [prepared statement](#sqlite3_stmt). If this routine returns 0, that means the [prepared statement](#sqlite3_stmt) returns no data (for example an [UPDATE](lang_update.md)). However, just because this routine returns a positive number does not mean that one or more rows of data will be returned. A SELECT statement will always have a positive sqlite3_column_count() but depending on the WHERE clause constraints and the table content, it might return no rows.
See also: [sqlite3_data_count()](#sqlite3_data_count)
------------------------------------------------------------------------
## Configuring The SQLite Library
> \
> int sqlite3_config(int, ...);\
The sqlite3_config() interface is used to make global configuration changes to SQLite in order to tune SQLite to the specific needs of the application. The default configuration is recommended for most applications and so this routine is usually not necessary. It is provided to support rare applications with unusual needs.
**The sqlite3_config() interface is not threadsafe. The application must ensure that no other SQLite interfaces are invoked by other threads while sqlite3_config() is running.**
The first argument to sqlite3_config() is an integer [configuration option](#SQLITE_CONFIG_COVERING_INDEX_SCAN) that determines what property of SQLite is to be configured. Subsequent arguments vary depending on the [configuration option](#SQLITE_CONFIG_COVERING_INDEX_SCAN) in the first argument.
For most configuration options, the sqlite3_config() interface may only be invoked prior to library initialization using [sqlite3_initialize()](#sqlite3_initialize) or after shutdown by [sqlite3_shutdown()](#sqlite3_initialize). The exceptional configuration options that may be invoked at any time are called "anytime configuration options". If sqlite3_config() is called after [sqlite3_initialize()](#sqlite3_initialize) and before [sqlite3_shutdown()](#sqlite3_initialize) with a first argument that is not an anytime configuration option, then the sqlite3_config() call will return SQLITE_MISUSE. Note, however, that sqlite3_config() can be called as part of the implementation of an application-defined [sqlite3_os_init()](#sqlite3_initialize).
When a configuration option is set, sqlite3_config() returns [SQLITE_OK](#SQLITE_ABORT). If the option is unknown or SQLite is unable to set the option then this routine returns a non-zero [error code](rescode.md).
------------------------------------------------------------------------
## Database Connection For Functions
> \
> sqlite3 \*sqlite3_context_db_handle(sqlite3_context\*);\
The sqlite3_context_db_handle() interface returns a copy of the pointer to the [database connection](#sqlite3) (the 1st parameter) of the [sqlite3_create_function()](#sqlite3_create_function) and [sqlite3_create_function16()](#sqlite3_create_function) routines that originally registered the application defined function.
------------------------------------------------------------------------
## Number of columns in a result set
> \
> int sqlite3_data_count(sqlite3_stmt \*pStmt);\
The sqlite3_data_count(P) interface returns the number of columns in the current row of the result set of [prepared statement](#sqlite3_stmt) P. If prepared statement P does not have results ready to return (via calls to the [sqlite3_column()](#sqlite3_column_blob) family of interfaces) then sqlite3_data_count(P) returns 0. The sqlite3_data_count(P) routine also returns 0 if P is a NULL pointer. The sqlite3_data_count(P) routine returns 0 if the previous call to [sqlite3_step](#sqlite3_step)(P) returned [SQLITE_DONE](#SQLITE_ABORT). The sqlite3_data_count(P) will return non-zero if previous call to [sqlite3_step](#sqlite3_step)(P) returned [SQLITE_ROW](#SQLITE_ABORT), except in the case of the [PRAGMA incremental_vacuum](pragma.md#pragma_incremental_vacuum) where it always returns zero since each step of that multi-step pragma returns 0 columns of data.
See also: [sqlite3_column_count()](#sqlite3_column_count)
------------------------------------------------------------------------
## Database File Corresponding To A Journal
> \
> sqlite3_file \*sqlite3_database_file_object(const char\*);\
If X is the name of a rollback or WAL-mode journal file that is passed into the xOpen method of [sqlite3_vfs](#sqlite3_vfs), then sqlite3_database_file_object(X) returns a pointer to the [sqlite3_file](#sqlite3_file) object that represents the main database file.
This routine is intended for use in custom [VFS](vfs.md) implementations only. It is not a general-purpose interface. The argument sqlite3_file_object(X) must be a filename pointer that has been passed into [sqlite3_vfs](#sqlite3_vfs).xOpen method where the flags parameter to xOpen contains one of the bits [SQLITE_OPEN_MAIN_JOURNAL](#SQLITE_OPEN_AUTOPROXY) or [SQLITE_OPEN_WAL](#SQLITE_OPEN_AUTOPROXY). Any other use of this routine results in undefined and probably undesirable behavior.
------------------------------------------------------------------------
## Flush caches to disk mid-transaction
> \
> int sqlite3_db_cacheflush(sqlite3\*);\
If a write-transaction is open on [database connection](#sqlite3) D when the [sqlite3_db_cacheflush(D)](#sqlite3_db_cacheflush) interface is invoked, any dirty pages in the pager-cache that are not currently in use are written out to disk. A dirty page may be in use if a database cursor created by an active SQL statement is reading from it, or if it is page 1 of a database file (page 1 is always "in use"). The [sqlite3_db_cacheflush(D)](#sqlite3_db_cacheflush) interface flushes caches for all schemas - "main", "temp", and any [attached](lang_attach.md) databases.
If this function needs to obtain extra database locks before dirty pages can be flushed to disk, it does so. If those locks cannot be obtained immediately and there is a busy-handler callback configured, it is invoked in the usual manner. If the required lock still cannot be obtained, then the database is skipped and an attempt made to flush any dirty pages belonging to the next (if any) database. If any databases are skipped because locks cannot be obtained, but no other error occurs, this function returns SQLITE_BUSY.
If any other error occurs while flushing dirty pages to disk (for example an IO error or out-of-memory condition), then processing is abandoned and an SQLite [error code](rescode.md) is returned to the caller immediately.
Otherwise, if no error occurs, [sqlite3_db_cacheflush()](#sqlite3_db_cacheflush) returns SQLITE_OK.
This function does not set the database handle error code or message returned by the [sqlite3_errcode()](#sqlite3_errcode) and [sqlite3_errmsg()](#sqlite3_errcode) functions.
------------------------------------------------------------------------
## Configure database connections
> \
> int sqlite3_db_config(sqlite3\*, int op, ...);\
The sqlite3_db_config() interface is used to make configuration changes to a [database connection](#sqlite3). The interface is similar to [sqlite3_config()](#sqlite3_config) except that the changes apply to a single [database connection](#sqlite3) (specified in the first argument).
The second argument to sqlite3_db_config(D,V,...) is the [configuration verb](#sqlitedbconfiglookaside) - an integer code that indicates what aspect of the [database connection](#sqlite3) is being configured. Subsequent arguments vary depending on the configuration verb.
Calls to sqlite3_db_config() return SQLITE_OK if and only if the call is considered successful.
------------------------------------------------------------------------
## Return The Filename For A Database Connection
> \
> sqlite3_filename sqlite3_db_filename(sqlite3 \*db, const char \*zDbName);\
The sqlite3_db_filename(D,N) interface returns a pointer to the filename associated with database N of connection D. If there is no attached database N on the database connection D, or if database N is a temporary or in-memory database, then this function will return either a NULL pointer or an empty string.
The string value returned by this routine is owned and managed by the database connection. The value will be valid until the database N is [DETACH](lang_detach.md)-ed or until the database connection closes.
The filename returned by this function is the output of the xFullPathname method of the [VFS](vfs.md). In other words, the filename will be an absolute pathname, even if the filename used to open the database originally was a URI or relative pathname.
If the filename pointer returned by this routine is not NULL, then it can be used as the filename input parameter to these routines:
- [sqlite3_uri_parameter()](#sqlite3_uri_boolean)
- [sqlite3_uri_boolean()](#sqlite3_uri_boolean)
- [sqlite3_uri_int64()](#sqlite3_uri_boolean)
- [sqlite3_filename_database()](#sqlite3_filename_database)
- [sqlite3_filename_journal()](#sqlite3_filename_database)
- [sqlite3_filename_wal()](#sqlite3_filename_database)
------------------------------------------------------------------------
## Find The Database Handle Of A Prepared Statement
> \
> sqlite3 \*sqlite3_db_handle(sqlite3_stmt\*);\
The sqlite3_db_handle interface returns the [database connection](#sqlite3) handle to which a [prepared statement](#sqlite3_stmt) belongs. The [database connection](#sqlite3) returned by sqlite3_db_handle is the same [database connection](#sqlite3) that was the first argument to the [sqlite3_prepare_v2()](#sqlite3_prepare) call (or its variants) that was used to create the statement in the first place.
------------------------------------------------------------------------
## Retrieve the mutex for a database connection
> \
> sqlite3_mutex \*sqlite3_db_mutex(sqlite3\*);\
This interface returns a pointer to the [sqlite3_mutex](#sqlite3_mutex) object that serializes access to the [database connection](#sqlite3) given in the argument when the [threading mode](threadsafe.md) is Serialized. If the [threading mode](threadsafe.md) is Single-thread or Multi-thread then this routine returns a NULL pointer.
------------------------------------------------------------------------
## Return The Schema Name For A Database Connection
> \
> const char \*sqlite3_db_name(sqlite3 \*db, int N);\
The sqlite3_db_name(D,N) interface returns a pointer to the schema name for the N-th database on database connection D, or a NULL pointer if N is out of range. An N value of 0 means the main database file. An N of 1 is the "temp" schema. Larger values of N correspond to various ATTACH-ed databases.
Space to hold the string that is returned by sqlite3_db_name() is managed by SQLite itself. The string might be deallocated by any operation that changes the schema, including [ATTACH](lang_attach.md) or [DETACH](lang_detach.md) or calls to [sqlite3_serialize()](#sqlite3_serialize) or [sqlite3_deserialize()](#sqlite3_deserialize), even operations that occur on a different thread. Applications that need to remember the string long-term should make their own copy. Applications that are accessing the same database connection simultaneously on multiple threads should mutex-protect calls to this API and should make their own private copy of the result prior to releasing the mutex.
------------------------------------------------------------------------
## Determine if a database is read-only
> \
> int sqlite3_db_readonly(sqlite3 \*db, const char \*zDbName);\
The sqlite3_db_readonly(D,N) interface returns 1 if the database N of connection D is read-only, 0 if it is read/write, or -1 if N is not the name of a database on connection D.
------------------------------------------------------------------------
## Free Memory Used By A Database Connection
> \
> int sqlite3_db_release_memory(sqlite3\*);\
The sqlite3_db_release_memory(D) interface attempts to free as much heap memory as possible from database connection D. Unlike the [sqlite3_release_memory()](#sqlite3_release_memory) interface, this interface is in effect even when the [SQLITE_ENABLE_MEMORY_MANAGEMENT](compile.md#enable_memory_management) compile-time option is omitted.
See also: [sqlite3_release_memory()](#sqlite3_release_memory)
------------------------------------------------------------------------
## Declare The Schema Of A Virtual Table
> \
> int sqlite3_declare_vtab(sqlite3\*, const char \*zSQL);\
The [xCreate](vtab.md#xcreate) and [xConnect](vtab.md#xconnect) methods of a [virtual table module](#sqlite3_module) call this interface to declare the format (the names and datatypes of the columns) of the virtual tables they implement.
------------------------------------------------------------------------
## Deserialize a database
> \
> int sqlite3_deserialize(\
> sqlite3 \*db, /\* The database connection \*/\
> const char \*zSchema, /\* Which DB to reopen with the deserialization \*/\
> unsigned char \*pData, /\* The serialized database content \*/\
> sqlite3_int64 szDb, /\* Number of bytes in the deserialization \*/\
> sqlite3_int64 szBuf, /\* Total size of buffer pData\[\] \*/\
> unsigned mFlags /\* Zero or more SQLITE_DESERIALIZE\_\* flags \*/\
> );\
The sqlite3_deserialize(D,S,P,N,M,F) interface causes the [database connection](#sqlite3) D to disconnect from database S and then reopen S as an in-memory database based on the serialization contained in P. If S is a NULL pointer, the main database is used. The serialized database P is N bytes in size. M is the size of the buffer P, which might be larger than N. If M is larger than N, and the SQLITE_DESERIALIZE_READONLY bit is not set in F, then SQLite is permitted to add content to the in-memory database as long as the total size does not exceed M bytes.
If the SQLITE_DESERIALIZE_FREEONCLOSE bit is set in F, then SQLite will invoke sqlite3_free() on the serialization buffer when the database connection closes. If the SQLITE_DESERIALIZE_RESIZEABLE bit is set, then SQLite will try to increase the buffer size using sqlite3_realloc64() if writes on the database cause it to grow larger than M bytes.
Applications must not modify the buffer P or invalidate it before the database connection D is closed.
The sqlite3_deserialize() interface will fail with SQLITE_BUSY if the database is currently in a read transaction or is involved in a backup operation.
It is not possible to deserialize into the TEMP database. If the S argument to sqlite3_deserialize(D,S,P,N,M,F) is "temp" then the function returns SQLITE_ERROR.
The deserialized database should not be in [WAL mode](wal.md). If the database is in WAL mode, then any attempt to use the database file will result in an [SQLITE_CANTOPEN](#SQLITE_ABORT) error. The application can set the [file format version numbers](fileformat2.md#vnums) (bytes 18 and 19) of the input database P to 0x01 prior to invoking sqlite3_deserialize(D,S,P,N,M,F) to force the database file into rollback mode and work around this limitation.
If sqlite3_deserialize(D,S,P,N,M,F) fails for any reason and if the SQLITE_DESERIALIZE_FREEONCLOSE bit is set in argument F, then [sqlite3_free()](#sqlite3_free) is invoked on argument P prior to returning.
This interface is omitted if SQLite is compiled with the [SQLITE_OMIT_DESERIALIZE](compile.md#omit_deserialize) option.
------------------------------------------------------------------------
## Remove Unnecessary Virtual Table Implementations
> \
> int sqlite3_drop_modules(\
> sqlite3 \*db, /\* Remove modules from this connection \*/\
> const char \*\*azKeep /\* Except, do not remove the ones named here \*/\
> );\
The sqlite3_drop_modules(D,L) interface removes all virtual table modules from database connection D except those named on list L. The L parameter must be either NULL or a pointer to an array of pointers to strings where the array is terminated by a single NULL pointer. If the L parameter is NULL, then all virtual table modules are removed.
See also: [sqlite3_create_module()](#sqlite3_create_module)
------------------------------------------------------------------------
## Enable Or Disable Extension Loading
> \
> int sqlite3_enable_load_extension(sqlite3 \*db, int onoff);\
So as not to open security holes in older applications that are unprepared to deal with [extension loading](loadext.md), and as a means of disabling [extension loading](loadext.md) while evaluating user-entered SQL, the following API is provided to turn the [sqlite3_load_extension()](#sqlite3_load_extension) mechanism on and off.
Extension loading is off by default. Call the sqlite3_enable_load_extension() routine with onoff==1 to turn extension loading on and call it with onoff==0 to turn it back off again.
This interface enables or disables both the C-API [sqlite3_load_extension()](#sqlite3_load_extension) and the SQL function [load_extension()](lang_corefunc.md#load_extension). Use [sqlite3_db_config](#sqlite3_db_config)(db,[SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION](#sqlitedbconfigenableloadextension),..) to enable or disable only the C-API.
**Security warning:** It is recommended that extension loading be enabled using the [SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION](#sqlitedbconfigenableloadextension) method rather than this interface, so the [load_extension()](lang_corefunc.md#load_extension) SQL function remains disabled. This will prevent SQL injections from giving attackers access to extension loading capabilities.
------------------------------------------------------------------------
## Enable Or Disable Shared Pager Cache
> \
> int sqlite3_enable_shared_cache(int);\
This routine enables or disables the sharing of the database cache and schema data structures between [connections](#sqlite3) to the same database. Sharing is enabled if the argument is true and disabled if the argument is false.
This interface is omitted if SQLite is compiled with [-DSQLITE_OMIT_SHARED_CACHE](compile.md#omit_shared_cache). The [-DSQLITE_OMIT_SHARED_CACHE](compile.md#omit_shared_cache) compile-time option is recommended because the [use of shared cache mode is discouraged](sharedcache.md#dontuse).
Cache sharing is enabled and disabled for an entire process. This is a change as of SQLite [version 3.5.0](releaselog/3_5_0.md) (2007-09-04). In prior versions of SQLite, sharing was enabled or disabled for each thread separately.
The cache sharing mode set by this interface effects all subsequent calls to [sqlite3_open()](#sqlite3_open), [sqlite3_open_v2()](#sqlite3_open), and [sqlite3_open16()](#sqlite3_open). Existing database connections continue to use the sharing mode that was in effect at the time they were opened.
This routine returns [SQLITE_OK](#SQLITE_ABORT) if shared cache was enabled or disabled successfully. An [error code](rescode.md) is returned otherwise.
Shared cache is disabled by default. It is recommended that it stay that way. In other words, do not use this routine. This interface continues to be provided for historical compatibility, but its use is discouraged. Any use of shared cache is discouraged. If shared cache must be used, it is recommended that shared cache only be enabled for individual database connections using the [sqlite3_open_v2()](#sqlite3_open) interface with the [SQLITE_OPEN_SHAREDCACHE](#SQLITE_OPEN_AUTOPROXY) flag.
Note: This method is disabled on MacOS X 10.7 and iOS version 5.0 and will always return SQLITE_MISUSE. On those systems, shared cache mode should be enabled per-database connection via [sqlite3_open_v2()](#sqlite3_open) with [SQLITE_OPEN_SHAREDCACHE](#SQLITE_OPEN_AUTOPROXY).
This interface is threadsafe on processors where writing a 32-bit integer is atomic.
See Also: [SQLite Shared-Cache Mode](sharedcache.md)
------------------------------------------------------------------------
## One-Step Query Execution Interface
> \
> int sqlite3_exec(\
> sqlite3\*, /\* An open database \*/\
> const char \*sql, /\* SQL to be evaluated \*/\
> int (\*callback)(void\*,int,char\*\*,char\*\*), /\* Callback function \*/\
> void \*, /\* 1st argument to callback \*/\
> char \*\*errmsg /\* Error msg written here \*/\
> );\
The sqlite3_exec() interface is a convenience wrapper around [sqlite3_prepare_v2()](#sqlite3_prepare), [sqlite3_step()](#sqlite3_step), and [sqlite3_finalize()](#sqlite3_finalize), that allows an application to run multiple statements of SQL without having to use a lot of C code.
The sqlite3_exec() interface runs zero or more UTF-8 encoded, semicolon-separated SQL statements passed into its 2nd argument, in the context of the [database connection](#sqlite3) passed in as its 1st argument. If the callback function of the 3rd argument to sqlite3_exec() is not NULL, then it is invoked for each result row coming out of the evaluated SQL statements. The 4th argument to sqlite3_exec() is relayed through to the 1st argument of each callback invocation. If the callback pointer to sqlite3_exec() is NULL, then no callback is ever invoked and result rows are ignored.
If an error occurs while evaluating the SQL statements passed into sqlite3_exec(), then execution of the current statement stops and subsequent statements are skipped. If the 5th parameter to sqlite3_exec() is not NULL then any error message is written into memory obtained from [sqlite3_malloc()](#sqlite3_free) and passed back through the 5th parameter. To avoid memory leaks, the application should invoke [sqlite3_free()](#sqlite3_free) on error message strings returned through the 5th parameter of sqlite3_exec() after the error message string is no longer needed. If the 5th parameter to sqlite3_exec() is not NULL and no errors occur, then sqlite3_exec() sets the pointer in its 5th parameter to NULL before returning.
If an sqlite3_exec() callback returns non-zero, the sqlite3_exec() routine returns SQLITE_ABORT without invoking the callback again and without running any subsequent SQL statements.
The 2nd argument to the sqlite3_exec() callback function is the number of columns in the result. The 3rd argument to the sqlite3_exec() callback is an array of pointers to strings obtained as if from [sqlite3_column_text()](#sqlite3_column_blob), one for each column. If an element of a result row is NULL then the corresponding string pointer for the sqlite3_exec() callback is a NULL pointer. The 4th argument to the sqlite3_exec() callback is an array of pointers to strings where each entry represents the name of a corresponding result column as obtained from [sqlite3_column_name()](#sqlite3_column_name).
If the 2nd parameter to sqlite3_exec() is a NULL pointer, a pointer to an empty string, or a pointer that contains only whitespace and/or SQL comments, then no SQL statements are evaluated and the database is not changed.
Restrictions:
- The application must ensure that the 1st parameter to sqlite3_exec() is a valid and open [database connection](#sqlite3).
- The application must not close the [database connection](#sqlite3) specified by the 1st parameter to sqlite3_exec() while sqlite3_exec() is running.
- The application must not modify the SQL statement text passed into the 2nd parameter of sqlite3_exec() while sqlite3_exec() is running.
- The application must not dereference the arrays or string pointers passed as the 3rd and 4th callback parameters after it returns.
------------------------------------------------------------------------
## Enable Or Disable Extended Result Codes
> \
> int sqlite3_extended_result_codes(sqlite3\*, int onoff);\
The sqlite3_extended_result_codes() routine enables or disables the [extended result codes](rescode.md#extrc) feature of SQLite. The extended result codes are disabled by default for historical compatibility.
------------------------------------------------------------------------
## Destroy A Prepared Statement Object
> \
> int sqlite3_finalize(sqlite3_stmt \*pStmt);\
The sqlite3_finalize() function is called to delete a [prepared statement](#sqlite3_stmt). If the most recent evaluation of the statement encountered no errors or if the statement has never been evaluated, then sqlite3_finalize() returns SQLITE_OK. If the most recent evaluation of statement S failed, then sqlite3_finalize(S) returns the appropriate [error code](rescode.md) or [extended error code](rescode.md#extrc).
The sqlite3_finalize(S) routine can be called at any point during the life cycle of [prepared statement](#sqlite3_stmt) S: before statement S is ever evaluated, after one or more calls to [sqlite3_reset()](#sqlite3_reset), or after any call to [sqlite3_step()](#sqlite3_step) regardless of whether or not the statement has completed execution.
Invoking sqlite3_finalize() on a NULL pointer is a harmless no-op.
The application must finalize every [prepared statement](#sqlite3_stmt) in order to avoid resource leaks. It is a grievous error for the application to try to use a prepared statement after it has been finalized. Any use of a prepared statement after it has been finalized can result in undefined and undesirable behavior such as segfaults and heap corruption.
------------------------------------------------------------------------
## Last Insert Rowid
> \
> sqlite3_int64 sqlite3_last_insert_rowid(sqlite3\*);\
Each entry in most SQLite tables (except for [WITHOUT ROWID](withoutrowid.md) tables) has a unique 64-bit signed integer key called the ["rowid"](lang_createtable.md#rowid). The rowid is always available as an undeclared column named ROWID, OID, or \_ROWID\_ as long as those names are not also used by explicitly declared columns. If the table has a column of type [INTEGER PRIMARY KEY](lang_createtable.md#rowid) then that column is another alias for the rowid.
The sqlite3_last_insert_rowid(D) interface usually returns the [rowid](lang_createtable.md#rowid) of the most recent successful [INSERT](lang_insert.md) into a rowid table or [virtual table](vtab.md) on database connection D. Inserts into [WITHOUT ROWID](withoutrowid.md) tables are not recorded. If no successful [INSERT](lang_insert.md)s into rowid tables have ever occurred on the database connection D, then sqlite3_last_insert_rowid(D) returns zero.
As well as being set automatically as rows are inserted into database tables, the value returned by this function may be set explicitly by [sqlite3_set_last_insert_rowid()](#sqlite3_set_last_insert_rowid)
Some virtual table implementations may INSERT rows into rowid tables as part of committing a transaction (e.g. to flush data accumulated in memory to disk). In this case subsequent calls to this function return the rowid associated with these internal INSERT operations, which leads to unintuitive results. Virtual table implementations that do write to rowid tables in this way can avoid this problem by restoring the original rowid value using [sqlite3_set_last_insert_rowid()](#sqlite3_set_last_insert_rowid) before returning control to the user.
If an [INSERT](lang_insert.md) occurs within a trigger then this routine will return the [rowid](lang_createtable.md#rowid) of the inserted row as long as the trigger is running. Once the trigger program ends, the value returned by this routine reverts to what it was before the trigger was fired.
An [INSERT](lang_insert.md) that fails due to a constraint violation is not a successful [INSERT](lang_insert.md) and does not change the value returned by this routine. Thus INSERT OR FAIL, INSERT OR IGNORE, INSERT OR ROLLBACK, and INSERT OR ABORT make no changes to the return value of this routine when their insertion fails. When INSERT OR REPLACE encounters a constraint violation, it does not fail. The INSERT continues to completion after deleting rows that caused the constraint problem so INSERT OR REPLACE will always change the return value of this interface.
For the purposes of this routine, an [INSERT](lang_insert.md) is considered to be successful even if it is subsequently rolled back.
This function is accessible to SQL statements via the [last_insert_rowid() SQL function](lang_corefunc.md#last_insert_rowid).
If a separate thread performs a new [INSERT](lang_insert.md) on the same database connection while the [sqlite3_last_insert_rowid()](#sqlite3_last_insert_rowid) function is running and thus changes the last insert [rowid](lang_createtable.md#rowid), then the value returned by [sqlite3_last_insert_rowid()](#sqlite3_last_insert_rowid) is unpredictable and might not equal either the old or the new last insert [rowid](lang_createtable.md#rowid).
------------------------------------------------------------------------
## Run-time Limits
> \
> int sqlite3_limit(sqlite3\*, int id, int newVal);\
This interface allows the size of various constructs to be limited on a connection by connection basis. The first parameter is the [database connection](#sqlite3) whose limit is to be set or queried. The second parameter is one of the [limit categories](#SQLITE_LIMIT_ATTACHED) that define a class of constructs to be size limited. The third parameter is the new limit for that construct.
If the new limit is a negative number, the limit is unchanged. For each limit category SQLITE_LIMIT\_*NAME* there is a [hard upper bound](limits.md) set at compile-time by a C preprocessor macro called [SQLITE_MAX\_*NAME*](limits.md). (The "\_LIMIT\_" in the name is changed to "\_MAX\_".) Attempts to increase a limit above its hard upper bound are silently truncated to the hard upper bound.
Regardless of whether or not the limit was changed, the [sqlite3_limit()](#sqlite3_limit) interface returns the prior value of the limit. Hence, to find the current value of a limit without changing it, simply invoke this interface with the third parameter set to -1.
Run-time limits are intended for use in applications that manage both their own internal database and also databases that are controlled by untrusted external sources. An example application might be a web browser that has its own databases for storing history and separate databases controlled by JavaScript applications downloaded off the Internet. The internal databases can be given the large, default limits. Databases managed by external sources can be given much smaller limits designed to prevent a denial of service attack. Developers might also want to use the [sqlite3_set_authorizer()](#sqlite3_set_authorizer) interface to further control untrusted SQL. The size of the database created by an untrusted script can be contained using the [max_page_count](pragma.md#pragma_max_page_count) [PRAGMA](pragma.md#syntax).
New run-time limit categories may be added in future releases.
------------------------------------------------------------------------
## Load An Extension
> \
> int sqlite3_load_extension(\
> sqlite3 \*db, /\* Load the extension into this database connection \*/\
> const char \*zFile, /\* Name of the shared library containing extension \*/\
> const char \*zProc, /\* Entry point. Derived from zFile if 0 \*/\
> char \*\*pzErrMsg /\* Put error message here if not 0 \*/\
> );\
This interface loads an SQLite extension library from the named file.
The sqlite3_load_extension() interface attempts to load an [SQLite extension](loadext.md) library contained in the file zFile. If the file cannot be loaded directly, attempts are made to load with various operating-system specific filename extensions added. So for example, if "samplelib" cannot be loaded, then names like "samplelib.so" or "samplelib.dylib" or "samplelib.dll" might be tried also.
The entry point is zProc. zProc may be 0, in which case SQLite will try to come up with an entry point name on its own. It first tries "sqlite3_extension_init". If that does not work, it tries names of the form "sqlite3_X_init" where X consists of the lower-case equivalent of all ASCII alphabetic characters or all ASCII alphanumeric characters in the filename from the last "/" to the first following "." and omitting any initial "lib". The sqlite3_load_extension() interface returns [SQLITE_OK](#SQLITE_ABORT) on success and [SQLITE_ERROR](#SQLITE_ABORT) if something goes wrong. If an error occurs and pzErrMsg is not 0, then the [sqlite3_load_extension()](#sqlite3_load_extension) interface shall attempt to fill \*pzErrMsg with error message text stored in memory obtained from [sqlite3_malloc()](#sqlite3_free). The calling function should free this memory by calling [sqlite3_free()](#sqlite3_free).
Extension loading must be enabled using [sqlite3_enable_load_extension()](#sqlite3_enable_load_extension) or [sqlite3_db_config](#sqlite3_db_config)(db,[SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION](#sqlitedbconfigenableloadextension),1,NULL) prior to calling this API, otherwise an error will be returned.
**Security warning:** It is recommended that the [SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION](#sqlitedbconfigenableloadextension) method be used to enable only this interface. The use of the [sqlite3_enable_load_extension()](#sqlite3_enable_load_extension) interface should be avoided. This will keep the SQL function [load_extension()](lang_corefunc.md#load_extension) disabled and prevent SQL injections from giving attackers access to extension loading capabilities.
See also the [load_extension() SQL function](lang_corefunc.md#load_extension).
------------------------------------------------------------------------
## Error Logging Interface
> \
> void sqlite3_log(int iErrCode, const char \*zFormat, ...);\
The [sqlite3_log()](#sqlite3_log) interface writes a message into the [error log](errlog.md) established by the [SQLITE_CONFIG_LOG](#sqliteconfiglog) option to [sqlite3_config()](#sqlite3_config). If logging is enabled, the zFormat string and subsequent arguments are used with [sqlite3_snprintf()](#sqlite3_mprintf) to generate the final output string.
The sqlite3_log() interface is intended for use by extensions such as virtual tables, collating functions, and SQL functions. While there is nothing to prevent an application from calling sqlite3_log(), doing so is considered bad form.
The zFormat string must not be NULL.
To avoid deadlocks and other threading problems, the sqlite3_log() routine will not use dynamically allocated memory. The log message is stored in a fixed-length buffer on the stack. If the log message is longer than a few hundred characters, it will be truncated to the length of the buffer.
------------------------------------------------------------------------
## Find the next prepared statement
> \
> sqlite3_stmt \*sqlite3_next_stmt(sqlite3 \*pDb, sqlite3_stmt \*pStmt);\
This interface returns a pointer to the next [prepared statement](#sqlite3_stmt) after pStmt associated with the [database connection](#sqlite3) pDb. If pStmt is NULL then this interface returns a pointer to the first prepared statement associated with the database connection pDb. If no prepared statement satisfies the conditions of this routine, it returns NULL.
The [database connection](#sqlite3) pointer D in a call to [sqlite3_next_stmt(D,S)](#sqlite3_next_stmt) must refer to an open database connection and in particular must not be a NULL pointer.
------------------------------------------------------------------------
## Overload A Function For A Virtual Table
> \
> int sqlite3_overload_function(sqlite3\*, const char \*zFuncName, int nArg);\
Virtual tables can provide alternative implementations of functions using the [xFindFunction](vtab.md#xfindfunction) method of the [virtual table module](#sqlite3_module). But global versions of those functions must exist in order to be overloaded.
This API makes sure a global version of a function with a particular name and number of parameters exists. If no such function exists before this API is called, a new function is created. The implementation of the new function always causes an exception to be thrown. So the new function is not good for anything by itself. Its only purpose is to be a placeholder function that can be overloaded by a [virtual table](vtab.md).
------------------------------------------------------------------------
## Query Progress Callbacks
> \
> void sqlite3_progress_handler(sqlite3\*, int, int(\*)(void\*), void\*);\
The sqlite3_progress_handler(D,N,X,P) interface causes the callback function X to be invoked periodically during long running calls to [sqlite3_step()](#sqlite3_step) and [sqlite3_prepare()](#sqlite3_prepare) and similar for database connection D. An example use for this interface is to keep a GUI updated during a large query.
The parameter P is passed through as the only parameter to the callback function X. The parameter N is the approximate number of [virtual machine instructions](opcode.md) that are evaluated between successive invocations of the callback X. If N is less than one then the progress handler is disabled.
Only a single progress handler may be defined at one time per [database connection](#sqlite3); setting a new progress handler cancels the old one. Setting parameter X to NULL disables the progress handler. The progress handler is also disabled by setting N to a value less than 1.
If the progress callback returns non-zero, the operation is interrupted. This feature can be used to implement a "Cancel" button on a GUI progress dialog box.
The progress handler callback must not do anything that will modify the database connection that invoked the progress handler. Note that [sqlite3_prepare_v2()](#sqlite3_prepare) and [sqlite3_step()](#sqlite3_step) both modify their database connections for the meaning of "modify" in this paragraph.
The progress handler callback would originally only be invoked from the bytecode engine. It still might be invoked during [sqlite3_prepare()](#sqlite3_prepare) and similar because those routines might force a reparse of the schema which involves running the bytecode engine. However, beginning with SQLite version 3.41.0, the progress handler callback might also be invoked directly from [sqlite3_prepare()](#sqlite3_prepare) while analyzing and generating code for complex queries.
------------------------------------------------------------------------
## Pseudo-Random Number Generator
> \
> void sqlite3_randomness(int N, void \*P);\
SQLite contains a high-quality pseudo-random number generator (PRNG) used to select random [ROWIDs](lang_createtable.md#rowid) when inserting new records into a table that already uses the largest possible [ROWID](lang_createtable.md#rowid). The PRNG is also used for the built-in random() and randomblob() SQL functions. This interface allows applications to access the same PRNG for other purposes.
A call to this routine stores N bytes of randomness into buffer P. The P parameter can be a NULL pointer.
If this routine has not been previously called or if the previous call had N less than one or a NULL pointer for P, then the PRNG is seeded using randomness obtained from the xRandomness method of the default [sqlite3_vfs](#sqlite3_vfs) object. If the previous call to this routine had an N of 1 or more and a non-NULL P then the pseudo-randomness is generated internally and without recourse to the [sqlite3_vfs](#sqlite3_vfs) xRandomness method.
------------------------------------------------------------------------
## Attempt To Free Heap Memory
> \
> int sqlite3_release_memory(int);\
The sqlite3_release_memory() interface attempts to free N bytes of heap memory by deallocating non-essential memory allocations held by the database library. Memory used to cache database pages to improve performance is an example of non-essential memory. sqlite3_release_memory() returns the number of bytes actually freed, which might be more or less than the amount requested. The sqlite3_release_memory() routine is a no-op returning zero if SQLite is not compiled with [SQLITE_ENABLE_MEMORY_MANAGEMENT](compile.md#enable_memory_management).
See also: [sqlite3_db_release_memory()](#sqlite3_db_release_memory)
------------------------------------------------------------------------
## Reset A Prepared Statement Object
> \
> int sqlite3_reset(sqlite3_stmt \*pStmt);\
The sqlite3_reset() function is called to reset a [prepared statement](#sqlite3_stmt) object back to its initial state, ready to be re-executed. Any SQL statement variables that had values bound to them using the [sqlite3_bind\_\*() API](#sqlite3_bind_blob) retain their values. Use [sqlite3_clear_bindings()](#sqlite3_clear_bindings) to reset the bindings.
The [sqlite3_reset(S)](#sqlite3_reset) interface resets the [prepared statement](#sqlite3_stmt) S back to the beginning of its program.
The return code from [sqlite3_reset(S)](#sqlite3_reset) indicates whether or not the previous evaluation of prepared statement S completed successfully. If [sqlite3_step(S)](#sqlite3_step) has never before been called on S or if [sqlite3_step(S)](#sqlite3_step) has not been called since the previous call to [sqlite3_reset(S)](#sqlite3_reset), then [sqlite3_reset(S)](#sqlite3_reset) will return [SQLITE_OK](#SQLITE_ABORT).
If the most recent call to [sqlite3_step(S)](#sqlite3_step) for the [prepared statement](#sqlite3_stmt) S indicated an error, then [sqlite3_reset(S)](#sqlite3_reset) returns an appropriate [error code](rescode.md). The [sqlite3_reset(S)](#sqlite3_reset) interface might also return an [error code](rescode.md) if there were no prior errors but the process of resetting the prepared statement caused a new error. For example, if an [INSERT](lang_insert.md) statement with a [RETURNING](lang_returning.md) clause is only stepped one time, that one call to [sqlite3_step(S)](#sqlite3_step) might return SQLITE_ROW but the overall statement might still fail and the [sqlite3_reset(S)](#sqlite3_reset) call might return SQLITE_BUSY if locking constraints prevent the database change from committing. Therefore, it is important that applications check the return code from [sqlite3_reset(S)](#sqlite3_reset) even if no prior call to [sqlite3_step(S)](#sqlite3_step) indicated a problem.
The [sqlite3_reset(S)](#sqlite3_reset) interface does not change the values of any [bindings](#sqlite3_bind_blob) on the [prepared statement](#sqlite3_stmt) S.
------------------------------------------------------------------------
## Reset Automatic Extension Loading
> \
> void sqlite3_reset_auto_extension(void);\
This interface disables all automatic extensions previously registered using [sqlite3_auto_extension()](#sqlite3_auto_extension).
------------------------------------------------------------------------
## Setting The Subtype Of An SQL Function
> \
> void sqlite3_result_subtype(sqlite3_context\*,unsigned int);\
The sqlite3_result_subtype(C,T) function causes the subtype of the result from the [application-defined SQL function](appfunc.md) with [sqlite3_context](#sqlite3_context) C to be the value T. Only the lower 8 bits of the subtype T are preserved in current versions of SQLite; higher order bits are discarded. The number of subtype bytes preserved by SQLite might increase in future releases of SQLite.
Every [application-defined SQL function](appfunc.md) that invokes this interface should include the [SQLITE_RESULT_SUBTYPE](#sqliteresultsubtype) property in its text encoding argument when the SQL function is [registered](#sqlite3_create_function). If the [SQLITE_RESULT_SUBTYPE](#sqliteresultsubtype) property is omitted from the function that invokes sqlite3_result_subtype(), then in some cases the sqlite3_result_subtype() might fail to set the result subtype.
If SQLite is compiled with -DSQLITE_STRICT_SUBTYPE=1, then any SQL function that invokes the sqlite3_result_subtype() interface and that does not have the SQLITE_RESULT_SUBTYPE property will raise an error. Future versions of SQLite might enable -DSQLITE_STRICT_SUBTYPE=1 by default.
------------------------------------------------------------------------
## Serialize a database
> \
> unsigned char \*sqlite3_serialize(\
> sqlite3 \*db, /\* The database connection \*/\
> const char \*zSchema, /\* Which DB to serialize. ex: "main", "temp", ... \*/\
> sqlite3_int64 \*piSize, /\* Write size of the DB here, if not NULL \*/\
> unsigned int mFlags /\* Zero or more SQLITE_SERIALIZE\_\* flags \*/\
> );\
The sqlite3_serialize(D,S,P,F) interface returns a pointer to memory that is a serialization of the S database on [database connection](#sqlite3) D. If S is a NULL pointer, the main database is used. If P is not a NULL pointer, then the size of the database in bytes is written into \*P.
For an ordinary on-disk database file, the serialization is just a copy of the disk file. For an in-memory database or a "TEMP" database, the serialization is the same sequence of bytes which would be written to disk if that database were backed up to disk.
The usual case is that sqlite3_serialize() copies the serialization of the database into memory obtained from [sqlite3_malloc64()](#sqlite3_free) and returns a pointer to that memory. The caller is responsible for freeing the returned value to avoid a memory leak. However, if the F argument contains the SQLITE_SERIALIZE_NOCOPY bit, then no memory allocations are made, and the sqlite3_serialize() function will return a pointer to the contiguous memory representation of the database that SQLite is currently using for that database, or NULL if no such contiguous memory representation of the database exists. A contiguous memory representation of the database will usually only exist if there has been a prior call to [sqlite3_deserialize(D,S,...)](#sqlite3_deserialize) with the same values of D and S. The size of the database is written into \*P even if the SQLITE_SERIALIZE_NOCOPY bit is set but no contiguous copy of the database exists.
After the call, if the SQLITE_SERIALIZE_NOCOPY bit had been set, the returned buffer content will remain accessible and unchanged until either the next write operation on the connection or when the connection is closed, and applications must not modify the buffer. If the bit had been clear, the returned buffer will not be accessed by SQLite after the call.
A call to sqlite3_serialize(D,S,P,F) might return NULL even if the SQLITE_SERIALIZE_NOCOPY bit is omitted from argument F if a memory allocation error occurs.
This interface is omitted if SQLite is compiled with the [SQLITE_OMIT_DESERIALIZE](compile.md#omit_deserialize) option.
------------------------------------------------------------------------
## Set Error Code And Message
> \
> int sqlite3_set_errmsg(sqlite3 \*db, int errcode, const char \*zErrMsg);\
Set the error code of the database handle passed as the first argument to errcode, and the error message to a copy of nul-terminated string zErrMsg. If zErrMsg is passed NULL, then the error message is set to the default message associated with the supplied error code. Subsequent calls to [sqlite3_errcode()](#sqlite3_errcode) and [sqlite3_errmsg()](#sqlite3_errcode) and similar will return the values set by this routine in place of what was previously set by SQLite itself.
This function returns SQLITE_OK if the error code and error message are successfully set, SQLITE_NOMEM if an OOM occurs, and SQLITE_MISUSE if the database handle is NULL or invalid.
The error code and message set by this routine remains in effect until they are changed, either by another call to this routine or until they are changed to by SQLite itself to reflect the result of some subsquent API call.
This function is intended for use by SQLite extensions or wrappers. The idea is that an extension or wrapper can use this routine to set error messages and error codes and thus behave more like a core SQLite feature from the point of view of an application.
------------------------------------------------------------------------
## Set the Last Insert Rowid value.
> \
> void sqlite3_set_last_insert_rowid(sqlite3\*,sqlite3_int64);\
The sqlite3_set_last_insert_rowid(D, R) method allows the application to set the value returned by calling sqlite3_last_insert_rowid(D) to R without inserting a row into the database.
------------------------------------------------------------------------
## Set the Setlk Timeout
> \
> int sqlite3_setlk_timeout(sqlite3\*, int ms, int flags);\
This routine is only useful in SQLITE_ENABLE_SETLK_TIMEOUT builds. If the VFS supports blocking locks, it sets the timeout in ms used by eligible locks taken on wal mode databases by the specified database handle. In non-SQLITE_ENABLE_SETLK_TIMEOUT builds, or if the VFS does not support blocking locks, this function is a no-op.
Passing 0 to this function disables blocking locks altogether. Passing -1 to this function requests that the VFS blocks for a long time - indefinitely if possible. The results of passing any other negative value are undefined.
Internally, each SQLite database handle stores two timeout values - the busy-timeout (used for rollback mode databases, or if the VFS does not support blocking locks) and the setlk-timeout (used for blocking locks on wal-mode databases). The sqlite3_busy_timeout() method sets both values, this function sets only the setlk-timeout value. Therefore, to configure separate busy-timeout and setlk-timeout values for a single database handle, call sqlite3_busy_timeout() followed by this function.
Whenever the number of connections to a wal mode database falls from 1 to 0, the last connection takes an exclusive lock on the database, then checkpoints and deletes the wal file. While it is doing this, any new connection that tries to read from the database fails with an SQLITE_BUSY error. Or, if the SQLITE_SETLK_BLOCK_ON_CONNECT flag is passed to this API, the new connection blocks until the exclusive lock has been released.
------------------------------------------------------------------------
## Suspend Execution For A Short Time
> \
> int sqlite3_sleep(int);\
The sqlite3_sleep() function causes the current thread to suspend execution for at least a number of milliseconds specified in its parameter.
If the operating system does not support sleep requests with millisecond time resolution, then the time will be rounded up to the nearest second. The number of milliseconds of sleep actually requested from the operating system is returned.
SQLite implements this interface by calling the xSleep() method of the default [sqlite3_vfs](#sqlite3_vfs) object. If the xSleep() method of the default VFS is not implemented correctly, or not implemented at all, then the behavior of sqlite3_sleep() may deviate from the description in the previous paragraphs.
If a negative argument is passed to sqlite3_sleep() the results vary by VFS and operating system. Some system treat a negative argument as an instruction to sleep forever. Others understand it to mean do not sleep at all. In SQLite version 3.42.0 and later, a negative argument passed into sqlite3_sleep() is changed to zero before it is relayed down into the xSleep method of the VFS.
------------------------------------------------------------------------
## Compare the ages of two snapshot handles.
> \
> int sqlite3_snapshot_cmp(\
> sqlite3_snapshot \*p1,\
> sqlite3_snapshot \*p2\
> );\
The sqlite3_snapshot_cmp(P1, P2) interface is used to compare the ages of two valid snapshot handles.
If the two snapshot handles are not associated with the same database file, the result of the comparison is undefined.
Additionally, the result of the comparison is only valid if both of the snapshot handles were obtained by calling sqlite3_snapshot_get() since the last time the wal file was deleted. The wal file is deleted when the database is changed back to rollback mode or when the number of database clients drops to zero. If either snapshot handle was obtained before the wal file was last deleted, the value returned by this function is undefined.
Otherwise, this API returns a negative value if P1 refers to an older snapshot than P2, zero if the two handles refer to the same database snapshot, and a positive value if P1 is a newer snapshot than P2.
This interface is only available if SQLite is compiled with the [SQLITE_ENABLE_SNAPSHOT](compile.md#enable_snapshot) option.
------------------------------------------------------------------------
## Destroy a snapshot
> \
> void sqlite3_snapshot_free(sqlite3_snapshot\*);\
The [sqlite3_snapshot_free(P)](#sqlite3_snapshot_free) interface destroys [sqlite3_snapshot](#sqlite3_snapshot) P. The application must eventually free every [sqlite3_snapshot](#sqlite3_snapshot) object using this routine to avoid a memory leak.
The [sqlite3_snapshot_free()](#sqlite3_snapshot_free) interface is only available when the [SQLITE_ENABLE_SNAPSHOT](compile.md#enable_snapshot) compile-time option is used.
------------------------------------------------------------------------
## Record A Database Snapshot
> \
> int sqlite3_snapshot_get(\
> sqlite3 \*db,\
> const char \*zSchema,\
> sqlite3_snapshot \*\*ppSnapshot\
> );\
The [sqlite3_snapshot_get(D,S,P)](#sqlite3_snapshot_get) interface attempts to make a new [sqlite3_snapshot](#sqlite3_snapshot) object that records the current state of schema S in database connection D. On success, the [sqlite3_snapshot_get(D,S,P)](#sqlite3_snapshot_get) interface writes a pointer to the newly created [sqlite3_snapshot](#sqlite3_snapshot) object into \*P and returns SQLITE_OK. If there is not already a read-transaction open on schema S when this function is called, one is opened automatically.
If a read-transaction is opened by this function, then it is guaranteed that the returned snapshot object may not be invalidated by a database writer or checkpointer until after the read-transaction is closed. This is not guaranteed if a read-transaction is already open when this function is called. In that case, any subsequent write or checkpoint operation on the database may invalidate the returned snapshot handle, even while the read-transaction remains open.
The following must be true for this function to succeed. If any of the following statements are false when sqlite3_snapshot_get() is called, SQLITE_ERROR is returned. The final value of \*P is undefined in this case.
- The database handle must not be in [autocommit mode](#sqlite3_get_autocommit).
- Schema S of [database connection](#sqlite3) D must be a [WAL mode](wal.md) database.
- There must not be a write transaction open on schema S of database connection D.
- One or more transactions must have been written to the current wal file since it was created on disk (by any connection). This means that a snapshot cannot be taken on a wal mode database with no wal file immediately after it is first opened. At least one transaction must be written to it first.
This function may also return SQLITE_NOMEM. If it is called with the database handle in autocommit mode but fails for some other reason, whether or not a read transaction is opened on schema S is undefined.
The [sqlite3_snapshot](#sqlite3_snapshot) object returned from a successful call to [sqlite3_snapshot_get()](#sqlite3_snapshot_get) must be freed using [sqlite3_snapshot_free()](#sqlite3_snapshot_free) to avoid a memory leak.
The [sqlite3_snapshot_get()](#sqlite3_snapshot_get) interface is only available when the [SQLITE_ENABLE_SNAPSHOT](compile.md#enable_snapshot) compile-time option is used.
------------------------------------------------------------------------
## Start a read transaction on an historical snapshot
> \
> int sqlite3_snapshot_open(\
> sqlite3 \*db,\
> const char \*zSchema,\
> sqlite3_snapshot \*pSnapshot\
> );\
The [sqlite3_snapshot_open(D,S,P)](#sqlite3_snapshot_open) interface either starts a new read transaction or upgrades an existing one for schema S of [database connection](#sqlite3) D such that the read transaction refers to historical [snapshot](#sqlite3_snapshot) P, rather than the most recent change to the database. The [sqlite3_snapshot_open()](#sqlite3_snapshot_open) interface returns SQLITE_OK on success or an appropriate [error code](rescode.md) if it fails.
In order to succeed, the database connection must not be in [autocommit mode](#sqlite3_get_autocommit) when [sqlite3_snapshot_open(D,S,P)](#sqlite3_snapshot_open) is called. If there is already a read transaction open on schema S, then the database handle must have no active statements (SELECT statements that have been passed to sqlite3_step() but not sqlite3_reset() or sqlite3_finalize()). SQLITE_ERROR is returned if either of these conditions is violated, or if schema S does not exist, or if the snapshot object is invalid.
A call to sqlite3_snapshot_open() will fail to open if the specified snapshot has been overwritten by a [checkpoint](wal.md#ckpt). In this case SQLITE_ERROR_SNAPSHOT is returned.
If there is already a read transaction open when this function is invoked, then the same read transaction remains open (on the same database snapshot) if SQLITE_ERROR, SQLITE_BUSY or SQLITE_ERROR_SNAPSHOT is returned. If another error code - for example SQLITE_PROTOCOL or an SQLITE_IOERR error code - is returned, then the final state of the read transaction is undefined. If SQLITE_OK is returned, then the read transaction is now open on database snapshot P.
A call to [sqlite3_snapshot_open(D,S,P)](#sqlite3_snapshot_open) will fail if the database connection D does not know that the database file for schema S is in [WAL mode](wal.md). A database connection might not know that the database file is in [WAL mode](wal.md) if there has been no prior I/O on that database connection, or if the database entered [WAL mode](wal.md) after the most recent I/O on the database connection. (Hint: Run "[PRAGMA application_id](pragma.md#pragma_application_id)" against a newly opened database connection in order to make it ready to use snapshots.)
The [sqlite3_snapshot_open()](#sqlite3_snapshot_open) interface is only available when the [SQLITE_ENABLE_SNAPSHOT](compile.md#enable_snapshot) compile-time option is used.
------------------------------------------------------------------------
## Recover snapshots from a wal file
> \
> int sqlite3_snapshot_recover(sqlite3 \*db, const char \*zDb);\
If a [WAL file](wal.md#walfile) remains on disk after all database connections close (either through the use of the [SQLITE_FCNTL_PERSIST_WAL](#sqlitefcntlpersistwal) [file control](#sqlite3_file_control) or because the last process to have the database opened exited without calling [sqlite3_close()](#sqlite3_close)) and a new connection is subsequently opened on that database and [WAL file](wal.md#walfile), the [sqlite3_snapshot_open()](#sqlite3_snapshot_open) interface will only be able to open the last transaction added to the WAL file even though the WAL file contains other valid transactions.
This function attempts to scan the WAL file associated with database zDb of database handle db and make all valid snapshots available to sqlite3_snapshot_open(). It is an error if there is already a read transaction open on the database, or if the database is not a WAL mode database.
SQLITE_OK is returned if successful, or an SQLite error code otherwise.
This interface is only available if SQLite is compiled with the [SQLITE_ENABLE_SNAPSHOT](compile.md#enable_snapshot) option.
------------------------------------------------------------------------
## Deprecated Soft Heap Limit Interface
> \
> void sqlite3_soft_heap_limit(int N);\
This is a deprecated version of the [sqlite3_soft_heap_limit64()](#sqlite3_hard_heap_limit64) interface. This routine is provided for historical compatibility only. All new applications should use the [sqlite3_soft_heap_limit64()](#sqlite3_hard_heap_limit64) interface rather than this one.
------------------------------------------------------------------------
## Evaluate An SQL Statement
> \
> int sqlite3_step(sqlite3_stmt\*);\
After a [prepared statement](#sqlite3_stmt) has been prepared using any of [sqlite3_prepare_v2()](#sqlite3_prepare), [sqlite3_prepare_v3()](#sqlite3_prepare), [sqlite3_prepare16_v2()](#sqlite3_prepare), or [sqlite3_prepare16_v3()](#sqlite3_prepare) or one of the legacy interfaces [sqlite3_prepare()](#sqlite3_prepare) or [sqlite3_prepare16()](#sqlite3_prepare), this function must be called one or more times to evaluate the statement.
The details of the behavior of the sqlite3_step() interface depend on whether the statement was prepared using the newer "vX" interfaces [sqlite3_prepare_v3()](#sqlite3_prepare), [sqlite3_prepare_v2()](#sqlite3_prepare), [sqlite3_prepare16_v3()](#sqlite3_prepare), [sqlite3_prepare16_v2()](#sqlite3_prepare) or the older legacy interfaces [sqlite3_prepare()](#sqlite3_prepare) and [sqlite3_prepare16()](#sqlite3_prepare). The use of the new "vX" interface is recommended for new applications but the legacy interface will continue to be supported.
In the legacy interface, the return value will be either [SQLITE_BUSY](#SQLITE_ABORT), [SQLITE_DONE](#SQLITE_ABORT), [SQLITE_ROW](#SQLITE_ABORT), [SQLITE_ERROR](#SQLITE_ABORT), or [SQLITE_MISUSE](#SQLITE_ABORT). With the "v2" interface, any of the other [result codes](rescode.md) or [extended result codes](rescode.md#extrc) might be returned as well.
[SQLITE_BUSY](#SQLITE_ABORT) means that the database engine was unable to acquire the database locks it needs to do its job. If the statement is a [COMMIT](lang_transaction.md) or occurs outside of an explicit transaction, then you can retry the statement. If the statement is not a [COMMIT](lang_transaction.md) and occurs within an explicit transaction then you should rollback the transaction before continuing.
[SQLITE_DONE](#SQLITE_ABORT) means that the statement has finished executing successfully. sqlite3_step() should not be called again on this virtual machine without first calling [sqlite3_reset()](#sqlite3_reset) to reset the virtual machine back to its initial state.
If the SQL statement being executed returns any data, then [SQLITE_ROW](#SQLITE_ABORT) is returned each time a new row of data is ready for processing by the caller. The values may be accessed using the [column access functions](#sqlite3_column_blob). sqlite3_step() is called again to retrieve the next row of data.
[SQLITE_ERROR](#SQLITE_ABORT) means that a run-time error (such as a constraint violation) has occurred. sqlite3_step() should not be called again on the VM. More information may be found by calling [sqlite3_errmsg()](#sqlite3_errcode). With the legacy interface, a more specific error code (for example, [SQLITE_INTERRUPT](#SQLITE_ABORT), [SQLITE_SCHEMA](#SQLITE_ABORT), [SQLITE_CORRUPT](#SQLITE_ABORT), and so forth) can be obtained by calling [sqlite3_reset()](#sqlite3_reset) on the [prepared statement](#sqlite3_stmt). In the "v2" interface, the more specific error code is returned directly by sqlite3_step().
[SQLITE_MISUSE](#SQLITE_ABORT) means that the this routine was called inappropriately. Perhaps it was called on a [prepared statement](#sqlite3_stmt) that has already been [finalized](#sqlite3_finalize) or on one that had previously returned [SQLITE_ERROR](#SQLITE_ABORT) or [SQLITE_DONE](#SQLITE_ABORT). Or it could be the case that the same database connection is being used by two or more threads at the same moment in time.
For all versions of SQLite up to and including 3.6.23.1, a call to [sqlite3_reset()](#sqlite3_reset) was required after sqlite3_step() returned anything other than [SQLITE_ROW](#SQLITE_ABORT) before any subsequent invocation of sqlite3_step(). Failure to reset the prepared statement using [sqlite3_reset()](#sqlite3_reset) would result in an [SQLITE_MISUSE](#SQLITE_ABORT) return from sqlite3_step(). But after [version 3.6.23.1](releaselog/3_6_23_1.md) (2010-03-26), sqlite3_step() began calling [sqlite3_reset()](#sqlite3_reset) automatically in this circumstance rather than returning [SQLITE_MISUSE](#SQLITE_ABORT). This is not considered a compatibility break because any application that ever receives an SQLITE_MISUSE error is broken by definition. The [SQLITE_OMIT_AUTORESET](compile.md#omit_autoreset) compile-time option can be used to restore the legacy behavior.
**Goofy Interface Alert:** In the legacy interface, the sqlite3_step() API always returns a generic error code, [SQLITE_ERROR](#SQLITE_ABORT), following any error other than [SQLITE_BUSY](#SQLITE_ABORT) and [SQLITE_MISUSE](#SQLITE_ABORT). You must call [sqlite3_reset()](#sqlite3_reset) or [sqlite3_finalize()](#sqlite3_finalize) in order to find one of the specific [error codes](rescode.md) that better describes the error. We admit that this is a goofy design. The problem has been fixed with the "v2" interface. If you prepare all of your SQL statements using [sqlite3_prepare_v3()](#sqlite3_prepare) or [sqlite3_prepare_v2()](#sqlite3_prepare) or [sqlite3_prepare16_v2()](#sqlite3_prepare) or [sqlite3_prepare16_v3()](#sqlite3_prepare) instead of the legacy [sqlite3_prepare()](#sqlite3_prepare) and [sqlite3_prepare16()](#sqlite3_prepare) interfaces, then the more specific [error codes](rescode.md) are returned directly by sqlite3_step(). The use of the "vX" interfaces is recommended.
------------------------------------------------------------------------
## Determine If A Prepared Statement Has Been Reset
> \
> int sqlite3_stmt_busy(sqlite3_stmt\*);\
The sqlite3_stmt_busy(S) interface returns true (non-zero) if the [prepared statement](#sqlite3_stmt) S has been stepped at least once using [sqlite3_step(S)](#sqlite3_step) but has neither run to completion (returned [SQLITE_DONE](#SQLITE_ABORT) from [sqlite3_step(S)](#sqlite3_step)) nor been reset using [sqlite3_reset(S)](#sqlite3_reset). The sqlite3_stmt_busy(S) interface returns false if S is a NULL pointer. If S is not a NULL pointer and is not a pointer to a valid [prepared statement](#sqlite3_stmt) object, then the behavior is undefined and probably undesirable.
This interface can be used in combination [sqlite3_next_stmt()](#sqlite3_next_stmt) to locate all prepared statements associated with a database connection that are in need of being reset. This can be used, for example, in diagnostic routines to search for prepared statements that are holding a transaction open.
------------------------------------------------------------------------
## Change The EXPLAIN Setting For A Prepared Statement
> \
> int sqlite3_stmt_explain(sqlite3_stmt \*pStmt, int eMode);\
The sqlite3_stmt_explain(S,E) interface changes the EXPLAIN setting for [prepared statement](#sqlite3_stmt) S. If E is zero, then S becomes a normal prepared statement. If E is 1, then S behaves as if its SQL text began with "[EXPLAIN](lang_explain.md)". If E is 2, then S behaves as if its SQL text began with "[EXPLAIN QUERY PLAN](eqp.md)".
Calling sqlite3_stmt_explain(S,E) might cause S to be reprepared. SQLite tries to avoid a reprepare, but a reprepare might be necessary on the first transition into EXPLAIN or EXPLAIN QUERY PLAN mode.
Because of the potential need to reprepare, a call to sqlite3_stmt_explain(S,E) will fail with SQLITE_ERROR if S cannot be reprepared because it was created using [sqlite3_prepare()](#sqlite3_prepare) instead of the newer [sqlite3_prepare_v2()](#sqlite3_prepare) or [sqlite3_prepare_v3()](#sqlite3_prepare) interfaces and hence has no saved SQL text with which to reprepare.
Changing the explain setting for a prepared statement does not change the original SQL text for the statement. Hence, if the SQL text originally began with EXPLAIN or EXPLAIN QUERY PLAN, but sqlite3_stmt_explain(S,0) is called to convert the statement into an ordinary statement, the EXPLAIN or EXPLAIN QUERY PLAN keywords will still appear in the sqlite3_sql(S) output, even though the statement now acts like a normal SQL statement.
This routine returns SQLITE_OK if the explain mode is successfully changed, or an error code if the explain mode could not be changed. The explain mode cannot be changed while a statement is active. Hence, it is good practice to call [sqlite3_reset(S)](#sqlite3_reset) immediately prior to calling sqlite3_stmt_explain(S,E).
------------------------------------------------------------------------
## Query The EXPLAIN Setting For A Prepared Statement
> \
> int sqlite3_stmt_isexplain(sqlite3_stmt \*pStmt);\
The sqlite3_stmt_isexplain(S) interface returns 1 if the prepared statement S is an EXPLAIN statement, or 2 if the statement S is an EXPLAIN QUERY PLAN. The sqlite3_stmt_isexplain(S) interface returns 0 if S is an ordinary statement or a NULL pointer.
------------------------------------------------------------------------
## Determine If An SQL Statement Writes The Database
> \
> int sqlite3_stmt_readonly(sqlite3_stmt \*pStmt);\
The sqlite3_stmt_readonly(X) interface returns true (non-zero) if and only if the [prepared statement](#sqlite3_stmt) X makes no direct changes to the content of the database file.
Note that [application-defined SQL functions](appfunc.md) or [virtual tables](vtab.md) might change the database indirectly as a side effect. For example, if an application defines a function "eval()" that calls [sqlite3_exec()](#sqlite3_exec), then the following SQL statement would change the database file through side-effects:
> \
> SELECT eval('DELETE FROM t1') FROM t2;\
But because the [SELECT](lang_select.md) statement does not change the database file directly, sqlite3_stmt_readonly() would still return true.
Transaction control statements such as [BEGIN](lang_transaction.md), [COMMIT](lang_transaction.md), [ROLLBACK](lang_transaction.md), [SAVEPOINT](lang_savepoint.md), and [RELEASE](lang_savepoint.md) cause sqlite3_stmt_readonly() to return true, since the statements themselves do not actually modify the database but rather they control the timing of when other statements modify the database. The [ATTACH](lang_attach.md) and [DETACH](lang_detach.md) statements also cause sqlite3_stmt_readonly() to return true since, while those statements change the configuration of a database connection, they do not make changes to the content of the database files on disk. The sqlite3_stmt_readonly() interface returns true for [BEGIN](lang_transaction.md) since [BEGIN](lang_transaction.md) merely sets internal flags, but the [BEGIN IMMEDIATE](lang_transaction.md) and [BEGIN EXCLUSIVE](lang_transaction.md) commands do touch the database and so sqlite3_stmt_readonly() returns false for those commands.
This routine returns false if there is any possibility that the statement might change the database file. A false return does not guarantee that the statement will change the database file. For example, an UPDATE statement might have a WHERE clause that makes it a no-op, but the sqlite3_stmt_readonly() result would still be false. Similarly, a CREATE TABLE IF NOT EXISTS statement is a read-only no-op if the table already exists, but sqlite3_stmt_readonly() still returns false for such a statement.
If prepared statement X is an [EXPLAIN](lang_explain.md) or [EXPLAIN QUERY PLAN](eqp.md) statement, then sqlite3_stmt_readonly(X) returns the same value as if the EXPLAIN or EXPLAIN QUERY PLAN prefix were omitted.
------------------------------------------------------------------------
## Zero Scan-Status Counters
> \
> void sqlite3_stmt_scanstatus_reset(sqlite3_stmt\*);\
Zero all [sqlite3_stmt_scanstatus()](#sqlite3_stmt_scanstatus) related event counters.
This API is only available if the library is built with pre-processor symbol [SQLITE_ENABLE_STMT_SCANSTATUS](compile.md#enable_stmt_scanstatus) defined.
------------------------------------------------------------------------
## Prepared Statement Status
> \
> int sqlite3_stmt_status(sqlite3_stmt\*, int op,int resetFlg);\
Each prepared statement maintains various [SQLITE_STMTSTATUS counters](#SQLITE_STMTSTATUS%20counter) that measure the number of times it has performed specific operations. These counters can be used to monitor the performance characteristics of the prepared statements. For example, if the number of table steps greatly exceeds the number of table searches or result rows, that would tend to indicate that the prepared statement is using a full table scan rather than an index.
This interface is used to retrieve and reset counter values from a [prepared statement](#sqlite3_stmt). The first argument is the prepared statement object to be interrogated. The second argument is an integer code for a specific [SQLITE_STMTSTATUS counter](#SQLITE_STMTSTATUS%20counter) to be interrogated. The current value of the requested counter is returned. If the resetFlg is true, then the counter is reset to zero after this interface call returns.
See also: [sqlite3_status()](#sqlite3_status) and [sqlite3_db_status()](#sqlite3_db_status).
------------------------------------------------------------------------
## Create A New Dynamic String Object
> \
> sqlite3_str \*sqlite3_str_new(sqlite3\*);\
The [sqlite3_str_new(D)](#sqlite3_str_new) interface allocates and initializes a new [sqlite3_str](#sqlite3_str) object. To avoid memory leaks, the object returned by [sqlite3_str_new()](#sqlite3_str_new) must be freed by a subsequent call to [sqlite3_str_finish(X)](#sqlite3_str_finish).
The [sqlite3_str_new(D)](#sqlite3_str_new) interface always returns a pointer to a valid [sqlite3_str](#sqlite3_str) object, though in the event of an out-of-memory error the returned object might be a special singleton that will silently reject new text, always return SQLITE_NOMEM from [sqlite3_str_errcode()](#sqlite3_str_errcode), always return 0 for [sqlite3_str_length()](#sqlite3_str_errcode), and always return NULL from [sqlite3_str_finish(X)](#sqlite3_str_finish). It is always safe to use the value returned by [sqlite3_str_new(D)](#sqlite3_str_new) as the sqlite3_str parameter to any of the other [sqlite3_str](#sqlite3_str) methods.
The D parameter to [sqlite3_str_new(D)](#sqlite3_str_new) may be NULL. If the D parameter in [sqlite3_str_new(D)](#sqlite3_str_new) is not NULL, then the maximum length of the string contained in the [sqlite3_str](#sqlite3_str) object will be the value set for [sqlite3_limit](#sqlite3_limit)(D,[SQLITE_LIMIT_LENGTH](#sqlitelimitlength)) instead of [SQLITE_MAX_LENGTH](limits.md#max_length).
------------------------------------------------------------------------
## String Globbing
> \
> int sqlite3_strglob(const char \*zGlob, const char \*zStr);\
The [sqlite3_strglob(P,X)](#sqlite3_strglob) interface returns zero if and only if string X matches the [GLOB](lang_expr.md#glob) pattern P. The definition of [GLOB](lang_expr.md#glob) pattern matching used in [sqlite3_strglob(P,X)](#sqlite3_strglob) is the same as for the "X GLOB P" operator in the SQL dialect understood by SQLite. The [sqlite3_strglob(P,X)](#sqlite3_strglob) function is case sensitive.
Note that this routine returns zero on a match and non-zero if the strings do not match, the same as [sqlite3_stricmp()](#sqlite3_stricmp) and [sqlite3_strnicmp()](#sqlite3_stricmp).
See also: [sqlite3_strlike()](#sqlite3_strlike).
------------------------------------------------------------------------
## String LIKE Matching
> \
> int sqlite3_strlike(const char \*zGlob, const char \*zStr, unsigned int cEsc);\
The [sqlite3_strlike(P,X,E)](#sqlite3_strlike) interface returns zero if and only if string X matches the [LIKE](lang_expr.md#like) pattern P with escape character E. The definition of [LIKE](lang_expr.md#like) pattern matching used in [sqlite3_strlike(P,X,E)](#sqlite3_strlike) is the same as for the "X LIKE P ESCAPE E" operator in the SQL dialect understood by SQLite. For "X LIKE P" without the ESCAPE clause, set the E parameter of [sqlite3_strlike(P,X,E)](#sqlite3_strlike) to 0. As with the LIKE operator, the [sqlite3_strlike(P,X,E)](#sqlite3_strlike) function is case insensitive - equivalent upper and lower case ASCII characters match one another.
The [sqlite3_strlike(P,X,E)](#sqlite3_strlike) function matches Unicode characters, though only ASCII characters are case folded.
Note that this routine returns zero on a match and non-zero if the strings do not match, the same as [sqlite3_stricmp()](#sqlite3_stricmp) and [sqlite3_strnicmp()](#sqlite3_stricmp).
See also: [sqlite3_strglob()](#sqlite3_strglob).
------------------------------------------------------------------------
## Low-level system error code
> \
> int sqlite3_system_errno(sqlite3\*);\
Attempt to return the underlying operating system error code or error number that caused the most recent I/O error or failure to open a file. The return value is OS-dependent. For example, on unix systems, after [sqlite3_open_v2()](#sqlite3_open) returns [SQLITE_CANTOPEN](#SQLITE_ABORT), this interface could be called to get back the underlying "errno" that caused the problem, such as ENOSPC, EAUTH, EISDIR, and so forth.
------------------------------------------------------------------------
## Extract Metadata About A Column Of A Table
> \
> int sqlite3_table_column_metadata(\
> sqlite3 \*db, /\* Connection handle \*/\
> const char \*zDbName, /\* Database name or NULL \*/\
> const char \*zTableName, /\* Table name \*/\
> const char \*zColumnName, /\* Column name \*/\
> char const \*\*pzDataType, /\* OUTPUT: Declared data type \*/\
> char const \*\*pzCollSeq, /\* OUTPUT: Collation sequence name \*/\
> int \*pNotNull, /\* OUTPUT: True if NOT NULL constraint exists \*/\
> int \*pPrimaryKey, /\* OUTPUT: True if column part of PK \*/\
> int \*pAutoinc /\* OUTPUT: True if column is auto-increment \*/\
> );\
The sqlite3_table_column_metadata(X,D,T,C,....) routine returns information about column C of table T in database D on [database connection](#sqlite3) X. The sqlite3_table_column_metadata() interface returns SQLITE_OK and fills in the non-NULL pointers in the final five arguments with appropriate values if the specified column exists. The sqlite3_table_column_metadata() interface returns SQLITE_ERROR if the specified column does not exist. If the column-name parameter to sqlite3_table_column_metadata() is a NULL pointer, then this routine simply checks for the existence of the table and returns SQLITE_OK if the table exists and SQLITE_ERROR if it does not. If the table name parameter T in a call to sqlite3_table_column_metadata(X,D,T,C,...) is NULL then the result is undefined behavior.
The column is identified by the second, third and fourth parameters to this function. The second parameter is either the name of the database (i.e. "main", "temp", or an attached database) containing the specified table or NULL. If it is NULL, then all attached databases are searched for the table using the same algorithm used by the database engine to resolve unqualified table references.
The third and fourth parameters to this function are the table and column name of the desired column, respectively.
Metadata is returned by writing to the memory locations passed as the 5th and subsequent parameters to this function. Any of these arguments may be NULL, in which case the corresponding element of metadata is omitted.
> Parameter
>
> Output\
> Type
>
> Description
>
> 5th
>
> const char\*
>
> Data type
>
> 6th
>
> const char\*
>
> Name of default collation sequence
>
> 7th
>
> int
>
> True if column has a NOT NULL constraint
>
> 8th
>
> int
>
> True if column is part of the PRIMARY KEY
>
> 9th
>
> int
>
> True if column is [AUTOINCREMENT](autoinc.md)
The memory pointed to by the character pointers returned for the declaration type and collation sequence is valid until the next call to any SQLite API function.
If the specified table is actually a view, an [error code](rescode.md) is returned.
If the specified column is "rowid", "oid" or "\_rowid\_" and the table is not a [WITHOUT ROWID](withoutrowid.md) table and an [INTEGER PRIMARY KEY](lang_createtable.md#rowid) column has been explicitly declared, then the output parameters are set for the explicitly declared column. If there is no [INTEGER PRIMARY KEY](lang_createtable.md#rowid) column, then the outputs for the [rowid](lang_createtable.md#rowid) are set as follows:
\
data type: "INTEGER"\
collation sequence: "BINARY"\
not null: 0\
primary key: 1\
auto increment: 0\
This function causes all database schemas to be read from disk and parsed, if that has not already been done, and returns an error if any errors are encountered while loading the schema.
------------------------------------------------------------------------
## Testing Interface
> \
> int sqlite3_test_control(int op, ...);\
The sqlite3_test_control() interface is used to read out internal state of SQLite and to inject faults into SQLite for testing purposes. The first parameter is an operation code that determines the number, meaning, and operation of all subsequent parameters.
This interface is not for use by applications. It exists solely for verifying the correct operation of the SQLite library. Depending on how the SQLite library is compiled, this interface might not exist.
The details of the operation codes, their meanings, the parameters they take, and what they do are all subject to change without notice. Unlike most of the SQLite API, this function is not guaranteed to operate consistently from one release to the next.
------------------------------------------------------------------------
## Test To See If The Library Is Threadsafe
> \
> int sqlite3_threadsafe(void);\
The sqlite3_threadsafe() function returns zero if and only if SQLite was compiled with mutexing code omitted due to the [SQLITE_THREADSAFE](compile.md#threadsafe) compile-time option being set to 0.
SQLite can be compiled with or without mutexes. When the [SQLITE_THREADSAFE](compile.md#threadsafe) C preprocessor macro is 1 or 2, mutexes are enabled and SQLite is threadsafe. When the [SQLITE_THREADSAFE](compile.md#threadsafe) macro is 0, the mutexes are omitted. Without the mutexes, it is not safe to use SQLite concurrently from more than one thread.
Enabling mutexes incurs a measurable performance penalty. So if speed is of utmost importance, it makes sense to disable the mutexes. But for maximum safety, mutexes should be enabled. The default behavior is for mutexes to be enabled.
This interface can be used by an application to make sure that the version of SQLite that it is linking against was compiled with the desired setting of the [SQLITE_THREADSAFE](compile.md#threadsafe) macro.
This interface only reports on the compile-time mutex setting of the [SQLITE_THREADSAFE](compile.md#threadsafe) flag. If SQLite is compiled with SQLITE_THREADSAFE=1 or =2 then mutexes are enabled by default but can be fully or partially disabled using a call to [sqlite3_config()](#sqlite3_config) with the verbs [SQLITE_CONFIG_SINGLETHREAD](#sqliteconfigsinglethread), [SQLITE_CONFIG_MULTITHREAD](#sqliteconfigmultithread), or [SQLITE_CONFIG_SERIALIZED](#sqliteconfigserialized). The return value of the sqlite3_threadsafe() function shows only the compile-time setting of thread safety, not any run-time changes to that setting made by sqlite3_config(). In other words, the return value from sqlite3_threadsafe() is unchanged by calls to sqlite3_config().
See the [threading mode](threadsafe.md) documentation for additional information.
------------------------------------------------------------------------
## SQL Trace Hook
> \
> int sqlite3_trace_v2(\
> sqlite3\*,\
> unsigned uMask,\
> int(\*xCallback)(unsigned,void\*,void\*,void\*),\
> void \*pCtx\
> );\
The sqlite3_trace_v2(D,M,X,P) interface registers a trace callback function X against [database connection](#sqlite3) D, using property mask M and context pointer P. If the X callback is NULL or if the M mask is zero, then tracing is disabled. The M argument should be the bitwise OR-ed combination of zero or more [SQLITE_TRACE](#SQLITE_TRACE) constants.
Each call to either sqlite3_trace(D,X,P) or sqlite3_trace_v2(D,M,X,P) overrides (cancels) all prior calls to sqlite3_trace(D,X,P) or sqlite3_trace_v2(D,M,X,P) for the [database connection](#sqlite3) D. Each database connection may have at most one trace callback.
The X callback is invoked whenever any of the events identified by mask M occur. The integer return value from the callback is currently ignored, though this may change in future releases. Callback implementations should return zero to ensure future compatibility.
A trace callback is invoked with four arguments: callback(T,C,P,X). The T argument is one of the [SQLITE_TRACE](#SQLITE_TRACE) constants to indicate why the callback was invoked. The C argument is a copy of the context pointer. The P and X arguments are pointers whose meanings depend on T.
The sqlite3_trace_v2() interface is intended to replace the legacy interfaces [sqlite3_trace()](#sqlite3_profile) and [sqlite3_profile()](#sqlite3_profile), both of which are deprecated.
------------------------------------------------------------------------
## Determine the transaction state of a database
> \
> int sqlite3_txn_state(sqlite3\*,const char \*zSchema);\
The sqlite3_txn_state(D,S) interface returns the current [transaction state](#SQLITE_TXN_NONE) of schema S in database connection D. If S is NULL, then the highest transaction state of any schema on database connection D is returned. Transaction states are (in order of lowest to highest):
1. SQLITE_TXN_NONE
2. SQLITE_TXN_READ
3. SQLITE_TXN_WRITE
If the S argument to sqlite3_txn_state(D,S) is not the name of a valid schema, then -1 is returned.
------------------------------------------------------------------------
## Unlock Notification
> \
> int sqlite3_unlock_notify(\
> sqlite3 \*pBlocked, /\* Waiting connection \*/\
> void (\*xNotify)(void \*\*apArg, int nArg), /\* Callback function to invoke \*/\
> void \*pNotifyArg /\* Argument to pass to xNotify \*/\
> );\
When running in shared-cache mode, a database operation may fail with an [SQLITE_LOCKED](#SQLITE_ABORT) error if the required locks on the shared-cache or individual tables within the shared-cache cannot be obtained. See [SQLite Shared-Cache Mode](sharedcache.md) for a description of shared-cache locking. This API may be used to register a callback that SQLite will invoke when the connection currently holding the required lock relinquishes it. This API is only available if the library was compiled with the [SQLITE_ENABLE_UNLOCK_NOTIFY](compile.md#enable_unlock_notify) C-preprocessor symbol defined.
See Also: [Using the SQLite Unlock Notification Feature](unlock_notify.md).
Shared-cache locks are released when a database connection concludes its current transaction, either by committing it or rolling it back.
When a connection (known as the blocked connection) fails to obtain a shared-cache lock and SQLITE_LOCKED is returned to the caller, the identity of the database connection (the blocking connection) that has locked the required resource is stored internally. After an application receives an SQLITE_LOCKED error, it may call the sqlite3_unlock_notify() method with the blocked connection handle as the first argument to register for a callback that will be invoked when the blocking connection's current transaction is concluded. The callback is invoked from within the [sqlite3_step](#sqlite3_step) or [sqlite3_close](#sqlite3_close) call that concludes the blocking connection's transaction.
If sqlite3_unlock_notify() is called in a multi-threaded application, there is a chance that the blocking connection will have already concluded its transaction by the time sqlite3_unlock_notify() is invoked. If this happens, then the specified callback is invoked immediately, from within the call to sqlite3_unlock_notify().
If the blocked connection is attempting to obtain a write-lock on a shared-cache table, and more than one other connection currently holds a read-lock on the same table, then SQLite arbitrarily selects one of the other connections to use as the blocking connection.
There may be at most one unlock-notify callback registered by a blocked connection. If sqlite3_unlock_notify() is called when the blocked connection already has a registered unlock-notify callback, then the new callback replaces the old. If sqlite3_unlock_notify() is called with a NULL pointer as its second argument, then any existing unlock-notify callback is canceled. The blocked connection's unlock-notify callback may also be canceled by closing the blocked connection using [sqlite3_close()](#sqlite3_close).
The unlock-notify callback is not reentrant. If an application invokes any sqlite3_xxx API functions from within an unlock-notify callback, a crash or deadlock may be the result.
Unless deadlock is detected (see below), sqlite3_unlock_notify() always returns SQLITE_OK.
**Callback Invocation Details**
When an unlock-notify callback is registered, the application provides a single void\* pointer that is passed to the callback when it is invoked. However, the signature of the callback function allows SQLite to pass it an array of void\* context pointers. The first argument passed to an unlock-notify callback is a pointer to an array of void\* pointers, and the second is the number of entries in the array.
When a blocking connection's transaction is concluded, there may be more than one blocked connection that has registered for an unlock-notify callback. If two or more such blocked connections have specified the same callback function, then instead of invoking the callback function multiple times, it is invoked once with the set of void\* context pointers specified by the blocked connections bundled together into an array. This gives the application an opportunity to prioritize any actions related to the set of unblocked database connections.
**Deadlock Detection**
Assuming that after registering for an unlock-notify callback a database waits for the callback to be issued before taking any further action (a reasonable assumption), then using this API may cause the application to deadlock. For example, if connection X is waiting for connection Y's transaction to be concluded, and similarly connection Y is waiting on connection X's transaction, then neither connection will proceed and the system may remain deadlocked indefinitely.
To avoid this scenario, the sqlite3_unlock_notify() performs deadlock detection. If a given call to sqlite3_unlock_notify() would put the system in a deadlocked state, then SQLITE_LOCKED is returned and no unlock-notify callback is registered. The system is said to be in a deadlocked state if connection A has registered for an unlock-notify callback on the conclusion of connection B's transaction, and connection B has itself registered for an unlock-notify callback when connection A's transaction is concluded. Indirect deadlock is also detected, so the system is also considered to be deadlocked if connection B has registered for an unlock-notify callback on the conclusion of connection C's transaction, where connection C is waiting on connection A. Any number of levels of indirection are allowed.
**The "DROP TABLE" Exception**
When a call to [sqlite3_step()](#sqlite3_step) returns SQLITE_LOCKED, it is almost always appropriate to call sqlite3_unlock_notify(). There is however, one exception. When executing a "DROP TABLE" or "DROP INDEX" statement, SQLite checks if there are any currently executing SELECT statements that belong to the same connection. If there are, SQLITE_LOCKED is returned. In this case there is no "blocking connection", so invoking sqlite3_unlock_notify() results in the unlock-notify callback being invoked immediately. If the application then re-attempts the "DROP TABLE" or "DROP INDEX" query, an infinite loop might be the result.
One way around this problem is to check the extended error code returned by an sqlite3_step() call. If there is a blocking connection, then the extended error code is set to SQLITE_LOCKED_SHAREDCACHE. Otherwise, in the special "DROP TABLE/INDEX" case, the extended error code is just SQLITE_LOCKED.
------------------------------------------------------------------------
## Data Change Notification Callbacks
> \
> void \*sqlite3_update_hook(\
> sqlite3\*,\
> void(\*)(void \*,int ,char const \*,char const \*,sqlite3_int64),\
> void\*\
> );\
The sqlite3_update_hook() interface registers a callback function with the [database connection](#sqlite3) identified by the first argument to be invoked whenever a row is updated, inserted or deleted in a [rowid table](rowidtable.md). Any callback set by a previous call to this function for the same database connection is overridden.
The second argument is a pointer to the function to invoke when a row is updated, inserted or deleted in a rowid table. The update hook is disabled by invoking sqlite3_update_hook() with a NULL pointer as the second parameter. The first argument to the callback is a copy of the third argument to sqlite3_update_hook(). The second callback argument is one of [SQLITE_INSERT](#SQLITE_ALTER_TABLE), [SQLITE_DELETE](#SQLITE_ALTER_TABLE), or [SQLITE_UPDATE](#SQLITE_ALTER_TABLE), depending on the operation that caused the callback to be invoked. The third and fourth arguments to the callback contain pointers to the database and table name containing the affected row. The final callback parameter is the [rowid](lang_createtable.md#rowid) of the row. In the case of an update, this is the [rowid](lang_createtable.md#rowid) after the update takes place.
The update hook is not invoked when internal system tables are modified (i.e. sqlite_sequence). The update hook is not invoked when [WITHOUT ROWID](withoutrowid.md) tables are modified.
In the current implementation, the update hook is not invoked when conflicting rows are deleted because of an [ON CONFLICT REPLACE](lang_conflict.md) clause. Nor is the update hook invoked when rows are deleted using the [truncate optimization](lang_delete.md#truncateopt). The exceptions defined in this paragraph might change in a future release of SQLite.
Whether the update hook is invoked before or after the corresponding change is currently unspecified and may differ depending on the type of change. Do not rely on the order of the hook call with regards to the final result of the operation which triggers the hook.
The update hook implementation must not do anything that will modify the database connection that invoked the update hook. Any actions to modify the database connection must be deferred until after the completion of the [sqlite3_step()](#sqlite3_step) call that triggered the update hook. Note that [sqlite3_prepare_v2()](#sqlite3_prepare) and [sqlite3_step()](#sqlite3_step) both modify their database connections for the meaning of "modify" in this paragraph.
The sqlite3_update_hook(D,C,P) function returns the P argument from the previous call on the same [database connection](#sqlite3) D, or NULL for the first call on D.
See also the [sqlite3_commit_hook()](#sqlite3_commit_hook), [sqlite3_rollback_hook()](#sqlite3_commit_hook), and [sqlite3_preupdate_hook()](#sqlite3_preupdate_blobwrite) interfaces.
------------------------------------------------------------------------
## User Data For Functions
> \
> void \*sqlite3_user_data(sqlite3_context\*);\
The sqlite3_user_data() interface returns a copy of the pointer that was the pUserData parameter (the 5th parameter) of the [sqlite3_create_function()](#sqlite3_create_function) and [sqlite3_create_function16()](#sqlite3_create_function) routines that originally registered the application defined function.
This routine must be called from the same thread in which the application-defined function is running.
------------------------------------------------------------------------
## Report the internal text encoding state of an sqlite3_value object
> \
> int sqlite3_value_encoding(sqlite3_value\*);\
The sqlite3_value_encoding(X) interface returns one of [SQLITE_UTF8](#sqliteutf8), [SQLITE_UTF16BE](#sqliteutf16be), or [SQLITE_UTF16LE](#sqliteutf16le) according to the current text encoding of the value X, assuming that X has type TEXT. If sqlite3_value_type(X) returns something other than SQLITE_TEXT, then the return value from sqlite3_value_encoding(X) is meaningless. Calls to [sqlite3_value_text(X)](#sqlite3_value_blob), [sqlite3_value_text16(X)](#sqlite3_value_blob), [sqlite3_value_text16be(X)](#sqlite3_value_blob), [sqlite3_value_text16le(X)](#sqlite3_value_blob), [sqlite3_value_bytes(X)](#sqlite3_value_blob), or [sqlite3_value_bytes16(X)](#sqlite3_value_blob) might change the encoding of the value X and thus change the return from subsequent calls to sqlite3_value_encoding(X).
This routine is intended for used by applications that test and validate the SQLite implementation. This routine is inquiring about the opaque internal state of an [sqlite3_value](#sqlite3_value) object. Ordinary applications should not need to know what the internal state of an sqlite3_value object is and hence should not need to use this interface.
------------------------------------------------------------------------
## Finding The Subtype Of SQL Values
> \
> unsigned int sqlite3_value_subtype(sqlite3_value\*);\
The sqlite3_value_subtype(V) function returns the subtype for an [application-defined SQL function](appfunc.md) argument V. The subtype information can be used to pass a limited amount of context from one SQL function to another. Use the [sqlite3_result_subtype()](#sqlite3_result_subtype) routine to set the subtype for the return value of an SQL function.
Every [application-defined SQL function](appfunc.md) that invokes this interface should include the [SQLITE_SUBTYPE](#sqlitesubtype) property in the text encoding argument when the function is [registered](#sqlite3_create_function). If the [SQLITE_SUBTYPE](#sqlitesubtype) property is omitted, then sqlite3_value_subtype() might return zero instead of the upstream subtype in some corner cases.
------------------------------------------------------------------------
## Determine The Collation For a Virtual Table Constraint
> \
> const char \*sqlite3_vtab_collation(sqlite3_index_info\*,int);\
This function may only be called from within a call to the [xBestIndex](vtab.md#xbestindex) method of a [virtual table](vtab.md). This function returns a pointer to a string that is the name of the appropriate collation sequence to use for text comparisons on the constraint identified by its arguments.
The first argument must be the pointer to the [sqlite3_index_info](#sqlite3_index_info) object that is the first parameter to the xBestIndex() method. The second argument must be an index into the aConstraint\[\] array belonging to the sqlite3_index_info structure passed to xBestIndex.
Important: The first parameter must be the same pointer that is passed into the xBestMethod() method. The first parameter may not be a pointer to a different [sqlite3_index_info](#sqlite3_index_info) object, even an exact copy.
The return value is computed as follows:
1. If the constraint comes from a WHERE clause expression that contains a [COLLATE operator](lang_expr.md#collateop), then the name of the collation specified by that COLLATE operator is returned.
2. If there is no COLLATE operator, but the column that is the subject of the constraint specifies an alternative collating sequence via a [COLLATE clause](lang_createtable.md#collateclause) on the column definition within the CREATE TABLE statement that was passed into [sqlite3_declare_vtab()](#sqlite3_declare_vtab), then the name of that alternative collating sequence is returned.
3. Otherwise, "BINARY" is returned.
------------------------------------------------------------------------
## Virtual Table Interface Configuration
> \
> int sqlite3_vtab_config(sqlite3\*, int op, ...);\
This function may be called by either the [xConnect](vtab.md#xconnect) or [xCreate](vtab.md#xcreate) method of a [virtual table](vtab.md) implementation to configure various facets of the virtual table interface.
If this interface is invoked outside the context of an xConnect or xCreate virtual table method then the behavior is undefined.
In the call sqlite3_vtab_config(D,C,...) the D parameter is the [database connection](#sqlite3) in which the virtual table is being created and which is passed in as the first argument to the [xConnect](vtab.md#xconnect) or [xCreate](vtab.md#xcreate) method that is invoking sqlite3_vtab_config(). The C parameter is one of the [virtual table configuration options](#SQLITE_VTAB_CONSTRAINT_SUPPORT). The presence and meaning of parameters after C depend on which [virtual table configuration option](#SQLITE_VTAB_CONSTRAINT_SUPPORT) is used.
------------------------------------------------------------------------
## Determine if a virtual table query is DISTINCT
> \
> int sqlite3_vtab_distinct(sqlite3_index_info\*);\
This API may only be used from within an [xBestIndex method](vtab.md#xbestindex) of a [virtual table](vtab.md) implementation. The result of calling this interface from outside of xBestIndex() is undefined and probably harmful.
The sqlite3_vtab_distinct() interface returns an integer between 0 and 3. The integer returned by sqlite3_vtab_distinct() gives the virtual table additional information about how the query planner wants the output to be ordered. As long as the virtual table can meet the ordering requirements of the query planner, it may set the "orderByConsumed" flag.
1. If the sqlite3_vtab_distinct() interface returns 0, that means that the query planner needs the virtual table to return all rows in the sort order defined by the "nOrderBy" and "aOrderBy" fields of the [sqlite3_index_info](#sqlite3_index_info) object. This is the default expectation. If the virtual table outputs all rows in sorted order, then it is always safe for the xBestIndex method to set the "orderByConsumed" flag, regardless of the return value from sqlite3_vtab_distinct().
2. If the sqlite3_vtab_distinct() interface returns 1, that means that the query planner does not need the rows to be returned in sorted order as long as all rows with the same values in all columns identified by the "aOrderBy" field are adjacent. This mode is used when the query planner is doing a GROUP BY.
3. If the sqlite3_vtab_distinct() interface returns 2, that means that the query planner does not need the rows returned in any particular order, as long as rows with the same values in all columns identified by "aOrderBy" are adjacent. Furthermore, when two or more rows contain the same values for all columns identified by "colUsed", all but one such row may optionally be omitted from the result. The virtual table is not required to omit rows that are duplicates over the "colUsed" columns, but if the virtual table can do that without too much extra effort, it could potentially help the query to run faster. This mode is used for a DISTINCT query.
4. If the sqlite3_vtab_distinct() interface returns 3, that means the virtual table must return rows in the order defined by "aOrderBy" as if the sqlite3_vtab_distinct() interface had returned 0. However if two or more rows in the result have the same values for all columns identified by "colUsed", then all but one such row may optionally be omitted. Like when the return value is 2, the virtual table is not required to omit rows that are duplicates over the "colUsed" columns, but if the virtual table can do that without too much extra effort, it could potentially help the query to run faster. This mode is used for queries that have both DISTINCT and ORDER BY clauses.
The following table summarizes the conditions under which the virtual table is allowed to set the "orderByConsumed" flag based on the value returned by sqlite3_vtab_distinct(). This table is a restatement of the previous four paragraphs:
sqlite3_vtab_distinct() return value
Rows are returned in aOrderBy order
Rows with the same value in all aOrderBy columns are adjacent
Duplicates over all colUsed columns may be omitted
0
yes
yes
no
1
no
yes
no
2
no
yes
yes
3
yes
yes
yes
For the purposes of comparing virtual table output values to see if the values are the same value for sorting purposes, two NULL values are considered to be the same. In other words, the comparison operator is "IS" (or "IS NOT DISTINCT FROM") and not "==".
If a virtual table implementation is unable to meet the requirements specified above, then it must not set the "orderByConsumed" flag in the [sqlite3_index_info](#sqlite3_index_info) object or an incorrect answer may result.
A virtual table implementation is always free to return rows in any order it wants, as long as the "orderByConsumed" flag is not set. When the "orderByConsumed" flag is unset, the query planner will add extra [bytecode](opcode.md) to ensure that the final results returned by the SQL query are ordered correctly. The use of the "orderByConsumed" flag and the sqlite3_vtab_distinct() interface is merely an optimization. Careful use of the sqlite3_vtab_distinct() interface and the "orderByConsumed" flag might help queries against a virtual table to run faster. Being overly aggressive and setting the "orderByConsumed" flag when it is not valid to do so, on the other hand, might cause SQLite to return incorrect results.
------------------------------------------------------------------------
## Identify and handle IN constraints in xBestIndex
> \
> int sqlite3_vtab_in(sqlite3_index_info\*, int iCons, int bHandle);\
This interface may only be used from within an [xBestIndex() method](vtab.md#xbestindex) of a [virtual table](vtab.md) implementation. The result of invoking this interface from any other context is undefined and probably harmful.
A constraint on a virtual table of the form "[column IN (...)](lang_expr.md#in_op)" is communicated to the xBestIndex method as a [SQLITE_INDEX_CONSTRAINT_EQ](#SQLITE_INDEX_CONSTRAINT_EQ) constraint. If xBestIndex wants to use this constraint, it must set the corresponding aConstraintUsage\[\].argvIndex to a positive integer. Then, under the usual mode of handling IN operators, SQLite generates [bytecode](opcode.md) that invokes the [xFilter() method](vtab.md#xfilter) once for each value on the right-hand side of the IN operator. Thus the virtual table only sees a single value from the right-hand side of the IN operator at a time.
In some cases, however, it would be advantageous for the virtual table to see all values on the right-hand of the IN operator all at once. The sqlite3_vtab_in() interfaces facilitates this in two ways:
1. A call to sqlite3_vtab_in(P,N,-1) will return true (non-zero) if and only if the [P-\>aConstraint](#sqlite3_index_info)\[N\] constraint is an [IN operator](lang_expr.md#in_op) that can be processed all at once. In other words, sqlite3_vtab_in() with -1 in the third argument is a mechanism by which the virtual table can ask SQLite if all-at-once processing of the IN operator is even possible.
2. A call to sqlite3_vtab_in(P,N,F) with F==1 or F==0 indicates to SQLite that the virtual table does or does not want to process the IN operator all-at-once, respectively. Thus when the third parameter (F) is non-negative, this interface is the mechanism by which the virtual table tells SQLite how it wants to process the IN operator.
The sqlite3_vtab_in(P,N,F) interface can be invoked multiple times within the same xBestIndex method call. For any given P,N pair, the return value from sqlite3_vtab_in(P,N,F) will always be the same within the same xBestIndex call. If the interface returns true (non-zero), that means that the constraint is an IN operator that can be processed all-at-once. If the constraint is not an IN operator or cannot be processed all-at-once, then the interface returns false.
All-at-once processing of the IN operator is selected if both of the following conditions are met:
1. The P-\>aConstraintUsage\[N\].argvIndex value is set to a positive integer. This is how the virtual table tells SQLite that it wants to use the N-th constraint.
2. The last call to sqlite3_vtab_in(P,N,F) for which F was non-negative had F\>=1.
If either or both of the conditions above are false, then SQLite uses the traditional one-at-a-time processing strategy for the IN constraint. If both conditions are true, then the argvIndex-th parameter to the xFilter method will be an [sqlite3_value](#sqlite3_value) that appears to be NULL, but which can be passed to [sqlite3_vtab_in_first()](#sqlite3_vtab_in_first) and [sqlite3_vtab_in_next()](#sqlite3_vtab_in_first) to find all values on the right-hand side of the IN constraint.
------------------------------------------------------------------------
## Determine If Virtual Table Column Access Is For UPDATE
> \
> int sqlite3_vtab_nochange(sqlite3_context\*);\
If the sqlite3_vtab_nochange(X) routine is called within the [xColumn](vtab.md#xcolumn) method of a [virtual table](vtab.md), then it might return true if the column is being fetched as part of an UPDATE operation during which the column value will not change. The virtual table implementation can use this hint as permission to substitute a return value that is less expensive to compute and that the corresponding [xUpdate](vtab.md#xupdate) method understands as a "no-change" value.
If the [xColumn](vtab.md#xcolumn) method calls sqlite3_vtab_nochange() and finds that the column is not changed by the UPDATE statement, then the xColumn method can optionally return without setting a result, without calling any of the [sqlite3_result_xxxxx() interfaces](#sqlite3_result_blob). In that case, [sqlite3_value_nochange(X)](#sqlite3_value_blob) will return true for the same column in the [xUpdate](vtab.md#xupdate) method.
The sqlite3_vtab_nochange() routine is an optimization. Virtual table implementations should continue to give a correct answer even if the sqlite3_vtab_nochange() interface were to always return false. In the current implementation, the sqlite3_vtab_nochange() interface does always returns false for the enhanced [UPDATE FROM](lang_update.md#upfrom) statement.
------------------------------------------------------------------------
## Determine The Virtual Table Conflict Policy
> \
> int sqlite3_vtab_on_conflict(sqlite3 \*);\
This function may only be called from within a call to the [xUpdate](vtab.md#xupdate) method of a [virtual table](vtab.md) implementation for an INSERT or UPDATE operation. The value returned is one of [SQLITE_ROLLBACK](#SQLITE_FAIL), [SQLITE_IGNORE](#SQLITE_DENY), [SQLITE_FAIL](#SQLITE_FAIL), [SQLITE_ABORT](#SQLITE_ABORT), or [SQLITE_REPLACE](#SQLITE_FAIL), according to the [ON CONFLICT](lang_conflict.md) mode of the SQL statement that triggered the call to the [xUpdate](vtab.md#xupdate) method of the [virtual table](vtab.md).
------------------------------------------------------------------------
## Constraint values in xBestIndex()
> \
> int sqlite3_vtab_rhs_value(sqlite3_index_info\*, int, sqlite3_value \*\*ppVal);\
This API may only be used from within the [xBestIndex method](vtab.md#xbestindex) of a [virtual table](vtab.md) implementation. The result of calling this interface from outside of an xBestIndex method are undefined and probably harmful.
When the sqlite3_vtab_rhs_value(P,J,V) interface is invoked from within the [xBestIndex](vtab.md#xbestindex) method of a [virtual table](vtab.md) implementation, with P being a copy of the [sqlite3_index_info](#sqlite3_index_info) object pointer passed into xBestIndex and J being a 0-based index into P-\>aConstraint\[\], then this routine attempts to set \*V to the value of the right-hand operand of that constraint if the right-hand operand is known. If the right-hand operand is not known, then \*V is set to a NULL pointer. The sqlite3_vtab_rhs_value(P,J,V) interface returns SQLITE_OK if and only if \*V is set to a value. The sqlite3_vtab_rhs_value(P,J,V) inteface returns SQLITE_NOTFOUND if the right-hand side of the J-th constraint is not available. The sqlite3_vtab_rhs_value() interface can return a result code other than SQLITE_OK or SQLITE_NOTFOUND if something goes wrong.
The sqlite3_vtab_rhs_value() interface is usually only successful if the right-hand operand of a constraint is a literal value in the original SQL statement. If the right-hand operand is an expression or a reference to some other column or a [host parameter](#sqlite3_bind_blob), then sqlite3_vtab_rhs_value() will probably return [SQLITE_NOTFOUND](#SQLITE_ABORT).
Some constraints, such as [SQLITE_INDEX_CONSTRAINT_ISNULL](#SQLITE_INDEX_CONSTRAINT_EQ) and [SQLITE_INDEX_CONSTRAINT_ISNOTNULL](#SQLITE_INDEX_CONSTRAINT_EQ), have no right-hand operand. For such constraints, sqlite3_vtab_rhs_value() always returns SQLITE_NOTFOUND.
The [sqlite3_value](#sqlite3_value) object returned in \*V is a protected sqlite3_value and remains valid for the duration of the xBestIndex method call. When xBestIndex returns, the sqlite3_value object returned by sqlite3_vtab_rhs_value() is automatically deallocated.
The "\_rhs\_" in the name of this routine is an abbreviation for "Right-Hand Side".
------------------------------------------------------------------------
## Configure an auto-checkpoint
> \
> int sqlite3_wal_autocheckpoint(sqlite3 \*db, int N);\
The [sqlite3_wal_autocheckpoint(D,N)](#sqlite3_wal_autocheckpoint) is a wrapper around [sqlite3_wal_hook()](#sqlite3_wal_hook) that causes any database on [database connection](#sqlite3) D to automatically [checkpoint](wal.md#ckpt) after committing a transaction if there are N or more frames in the [write-ahead log](wal.md) file. Passing zero or a negative value as the N parameter disables automatic checkpoints entirely.
The callback registered by this function replaces any existing callback registered using [sqlite3_wal_hook()](#sqlite3_wal_hook). Likewise, registering a callback using [sqlite3_wal_hook()](#sqlite3_wal_hook) disables the automatic checkpoint mechanism configured by this function.
The [wal_autocheckpoint pragma](pragma.md#pragma_wal_autocheckpoint) can be used to invoke this interface from SQL.
Checkpoints initiated by this mechanism are [PASSIVE](#sqlite3_wal_checkpoint_v2).
Every new [database connection](#sqlite3) defaults to having the auto-checkpoint enabled with a threshold of 1000 or [SQLITE_DEFAULT_WAL_AUTOCHECKPOINT](compile.md#default_wal_autocheckpoint) pages.
The use of this interface is only necessary if the default setting is found to be suboptimal for a particular application.
------------------------------------------------------------------------
## Checkpoint a database
> \
> int sqlite3_wal_checkpoint(sqlite3 \*db, const char \*zDb);\
The sqlite3_wal_checkpoint(D,X) is equivalent to [sqlite3_wal_checkpoint_v2](#sqlite3_wal_checkpoint_v2)(D,X,[SQLITE_CHECKPOINT_PASSIVE](#SQLITE_CHECKPOINT_FULL),0,0).
In brief, sqlite3_wal_checkpoint(D,X) causes the content in the [write-ahead log](wal.md) for database X on [database connection](#sqlite3) D to be transferred into the database file and for the write-ahead log to be reset. See the [checkpointing](wal.md#ckpt) documentation for addition information.
This interface used to be the only way to cause a checkpoint to occur. But then the newer and more powerful [sqlite3_wal_checkpoint_v2()](#sqlite3_wal_checkpoint_v2) interface was added. This interface is retained for backwards compatibility and as a convenience for applications that need to manually start a callback but which do not need the full power (and corresponding complication) of [sqlite3_wal_checkpoint_v2()](#sqlite3_wal_checkpoint_v2).
------------------------------------------------------------------------
## Checkpoint a database
> \
> int sqlite3_wal_checkpoint_v2(\
> sqlite3 \*db, /\* Database handle \*/\
> const char \*zDb, /\* Name of attached database (or NULL) \*/\
> int eMode, /\* SQLITE_CHECKPOINT\_\* value \*/\
> int \*pnLog, /\* OUT: Size of WAL log in frames \*/\
> int \*pnCkpt /\* OUT: Total number of frames checkpointed \*/\
> );\
The sqlite3_wal_checkpoint_v2(D,X,M,L,C) interface runs a checkpoint operation on database X of [database connection](#sqlite3) D in mode M. Status information is written back into integers pointed to by L and C. The M parameter must be a valid [checkpoint mode](#SQLITE_CHECKPOINT_FULL):
SQLITE_CHECKPOINT_PASSIVE
Checkpoint as many frames as possible without waiting for any database readers or writers to finish, then sync the database file if all frames in the log were checkpointed. The [busy-handler callback](#sqlite3_busy_handler) is never invoked in the SQLITE_CHECKPOINT_PASSIVE mode. On the other hand, passive mode might leave the checkpoint unfinished if there are concurrent readers or writers.
SQLITE_CHECKPOINT_FULL
This mode blocks (it invokes the [busy-handler callback](#sqlite3_busy_handler)) until there is no database writer and all readers are reading from the most recent database snapshot. It then checkpoints all frames in the log file and syncs the database file. This mode blocks new database writers while it is pending, but new database readers are allowed to continue unimpeded.
SQLITE_CHECKPOINT_RESTART
This mode works the same way as SQLITE_CHECKPOINT_FULL with the addition that after checkpointing the log file it blocks (calls the [busy-handler callback](#sqlite3_busy_handler)) until all readers are reading from the database file only. This ensures that the next writer will restart the log file from the beginning. Like SQLITE_CHECKPOINT_FULL, this mode blocks new database writer attempts while it is pending, but does not impede readers.
SQLITE_CHECKPOINT_TRUNCATE
This mode works the same way as SQLITE_CHECKPOINT_RESTART with the addition that it also truncates the log file to zero bytes just prior to a successful return.
SQLITE_CHECKPOINT_NOOP
This mode always checkpoints zero frames. The only reason to invoke a NOOP checkpoint is to access the values returned by sqlite3_wal_checkpoint_v2() via output parameters \*pnLog and \*pnCkpt.
If pnLog is not NULL, then \*pnLog is set to the total number of frames in the log file or to -1 if the checkpoint could not run because of an error or because the database is not in [WAL mode](wal.md). If pnCkpt is not NULL,then \*pnCkpt is set to the total number of checkpointed frames in the log file (including any that were already checkpointed before the function was called) or to -1 if the checkpoint could not run due to an error or because the database is not in WAL mode. Note that upon successful completion of an SQLITE_CHECKPOINT_TRUNCATE, the log file will have been truncated to zero bytes and so both \*pnLog and \*pnCkpt will be set to zero.
All calls obtain an exclusive "checkpoint" lock on the database file. If any other process is running a checkpoint operation at the same time, the lock cannot be obtained and SQLITE_BUSY is returned. Even if there is a busy-handler configured, it will not be invoked in this case.
The SQLITE_CHECKPOINT_FULL, RESTART and TRUNCATE modes also obtain the exclusive "writer" lock on the database file. If the writer lock cannot be obtained immediately, and a busy-handler is configured, it is invoked and the writer lock retried until either the busy-handler returns 0 or the lock is successfully obtained. The busy-handler is also invoked while waiting for database readers as described above. If the busy-handler returns 0 before the writer lock is obtained or while waiting for database readers, the checkpoint operation proceeds from that point in the same way as SQLITE_CHECKPOINT_PASSIVE - checkpointing as many frames as possible without blocking any further. SQLITE_BUSY is returned in this case.
If parameter zDb is NULL or points to a zero length string, then the specified operation is attempted on all WAL databases [attached](lang_attach.md) to [database connection](#sqlite3) db. In this case the values written to output parameters \*pnLog and \*pnCkpt are undefined. If an SQLITE_BUSY error is encountered when processing one or more of the attached WAL databases, the operation is still attempted on any remaining attached databases and SQLITE_BUSY is returned at the end. If any other error occurs while processing an attached database, processing is abandoned and the error code is returned to the caller immediately. If no error (SQLITE_BUSY or otherwise) is encountered while processing the attached databases, SQLITE_OK is returned.
If database zDb is the name of an attached database that is not in WAL mode, SQLITE_OK is returned and both \*pnLog and \*pnCkpt set to -1. If zDb is not NULL (or a zero length string) and is not the name of any attached database, SQLITE_ERROR is returned to the caller.
Unless it returns SQLITE_MISUSE, the sqlite3_wal_checkpoint_v2() interface sets the error information that is queried by [sqlite3_errcode()](#sqlite3_errcode) and [sqlite3_errmsg()](#sqlite3_errcode).
The [PRAGMA wal_checkpoint](pragma.md#pragma_wal_checkpoint) command can be used to invoke this interface from SQL.
------------------------------------------------------------------------
## Write-Ahead Log Commit Hook
> \
> void \*sqlite3_wal_hook(\
> sqlite3\*,\
> int(\*)(void \*,sqlite3\*,const char\*,int),\
> void\*\
> );\
The [sqlite3_wal_hook()](#sqlite3_wal_hook) function is used to register a callback that is invoked each time data is committed to a database in wal mode.
The callback is invoked by SQLite after the commit has taken place and the associated write-lock on the database released, so the implementation may read, write or [checkpoint](wal.md#ckpt) the database as required.
The first parameter passed to the callback function when it is invoked is a copy of the third parameter passed to sqlite3_wal_hook() when registering the callback. The second is a copy of the database handle. The third parameter is the name of the database that was written to - either "main" or the name of an [ATTACH](lang_attach.md)-ed database. The fourth parameter is the number of pages currently in the write-ahead log file, including those that were just committed.
The callback function should normally return [SQLITE_OK](#SQLITE_ABORT). If an error code is returned, that error will propagate back up through the SQLite code base to cause the statement that provoked the callback to report an error, though the commit will have still occurred. If the callback returns [SQLITE_ROW](#SQLITE_ABORT) or [SQLITE_DONE](#SQLITE_ABORT), or if it returns a value that does not correspond to any valid SQLite error code, the results are undefined.
A single database handle may have at most a single write-ahead log callback registered at one time. Calling [sqlite3_wal_hook()](#sqlite3_wal_hook) replaces the default behavior or previously registered write-ahead log callback.
The return value is a copy of the third parameter from the previous call, if any, or 0.
The [sqlite3_wal_autocheckpoint()](#sqlite3_wal_autocheckpoint) interface and the [wal_autocheckpoint pragma](pragma.md#pragma_wal_autocheckpoint) both invoke [sqlite3_wal_hook()](#sqlite3_wal_hook) and will overwrite any prior [sqlite3_wal_hook()](#sqlite3_wal_hook) settings.
If a write-ahead log callback is set using this function then [sqlite3_wal_checkpoint_v2()](#sqlite3_wal_checkpoint_v2) or [PRAGMA wal_checkpoint](pragma.md#pragma_wal_checkpoint) should be invoked periodically to keep the write-ahead log file from growing without bound.
Passing a NULL pointer for the callback disables automatic checkpointing entirely. To re-enable the default behavior, call sqlite3_wal_autocheckpoint(db,1000) or use [PRAGMA wal_checkpoint](pragma.md#pragma_wal_checkpoint).
------------------------------------------------------------------------
## Result Codes
> \
> \#define SQLITE_OK 0 /\* Successful result \*/\
> /\* beginning-of-error-codes \*/\
> \#define SQLITE_ERROR 1 /\* Generic error \*/\
> \#define SQLITE_INTERNAL 2 /\* Internal logic error in SQLite \*/\
> \#define SQLITE_PERM 3 /\* Access permission denied \*/\
> \#define SQLITE_ABORT 4 /\* Callback routine requested an abort \*/\
> \#define SQLITE_BUSY 5 /\* The database file is locked \*/\
> \#define SQLITE_LOCKED 6 /\* A table in the database is locked \*/\
> \#define SQLITE_NOMEM 7 /\* A malloc() failed \*/\
> \#define SQLITE_READONLY 8 /\* Attempt to write a readonly database \*/\
> \#define SQLITE_INTERRUPT 9 /\* Operation terminated by sqlite3_interrupt()\*/\
> \#define SQLITE_IOERR 10 /\* Some kind of disk I/O error occurred \*/\
> \#define SQLITE_CORRUPT 11 /\* The database disk image is malformed \*/\
> \#define SQLITE_NOTFOUND 12 /\* Unknown opcode in sqlite3_file_control() \*/\
> \#define SQLITE_FULL 13 /\* Insertion failed because database is full \*/\
> \#define SQLITE_CANTOPEN 14 /\* Unable to open the database file \*/\
> \#define SQLITE_PROTOCOL 15 /\* Database lock protocol error \*/\
> \#define SQLITE_EMPTY 16 /\* Internal use only \*/\
> \#define SQLITE_SCHEMA 17 /\* The database schema changed \*/\
> \#define SQLITE_TOOBIG 18 /\* String or BLOB exceeds size limit \*/\
> \#define SQLITE_CONSTRAINT 19 /\* Abort due to constraint violation \*/\
> \#define SQLITE_MISMATCH 20 /\* Data type mismatch \*/\
> \#define SQLITE_MISUSE 21 /\* Library used incorrectly \*/\
> \#define SQLITE_NOLFS 22 /\* Uses OS features not supported on host \*/\
> \#define SQLITE_AUTH 23 /\* Authorization denied \*/\
> \#define SQLITE_FORMAT 24 /\* Not used \*/\
> \#define SQLITE_RANGE 25 /\* 2nd parameter to sqlite3_bind out of range \*/\
> \#define SQLITE_NOTADB 26 /\* File opened that is not a database file \*/\
> \#define SQLITE_NOTICE 27 /\* Notifications from sqlite3_log() \*/\
> \#define SQLITE_WARNING 28 /\* Warnings from sqlite3_log() \*/\
> \#define SQLITE_ROW 100 /\* sqlite3_step() has another row ready \*/\
> \#define SQLITE_DONE 101 /\* sqlite3_step() has finished executing \*/\
> /\* end-of-error-codes \*/\
Many SQLite functions return an integer result code from the set shown here in order to indicate success or failure.
New error codes may be added in future versions of SQLite.
See also: [extended result code definitions](#SQLITE_ABORT_ROLLBACK)
------------------------------------------------------------------------
## Extended Result Codes
> \
> \#define SQLITE_ERROR_MISSING_COLLSEQ (SQLITE_ERROR \| (1\<\<8))\
> \#define SQLITE_ERROR_RETRY (SQLITE_ERROR \| (2\<\<8))\
> \#define SQLITE_ERROR_SNAPSHOT (SQLITE_ERROR \| (3\<\<8))\
> \#define SQLITE_ERROR_RESERVESIZE (SQLITE_ERROR \| (4\<\<8))\
> \#define SQLITE_ERROR_KEY (SQLITE_ERROR \| (5\<\<8))\
> \#define SQLITE_ERROR_UNABLE (SQLITE_ERROR \| (6\<\<8))\
> \#define SQLITE_IOERR_READ (SQLITE_IOERR \| (1\<\<8))\
> \#define SQLITE_IOERR_SHORT_READ (SQLITE_IOERR \| (2\<\<8))\
> \#define SQLITE_IOERR_WRITE (SQLITE_IOERR \| (3\<\<8))\
> \#define SQLITE_IOERR_FSYNC (SQLITE_IOERR \| (4\<\<8))\
> \#define SQLITE_IOERR_DIR_FSYNC (SQLITE_IOERR \| (5\<\<8))\
> \#define SQLITE_IOERR_TRUNCATE (SQLITE_IOERR \| (6\<\<8))\
> \#define SQLITE_IOERR_FSTAT (SQLITE_IOERR \| (7\<\<8))\
> \#define SQLITE_IOERR_UNLOCK (SQLITE_IOERR \| (8\<\<8))\
> \#define SQLITE_IOERR_RDLOCK (SQLITE_IOERR \| (9\<\<8))\
> \#define SQLITE_IOERR_DELETE (SQLITE_IOERR \| (10\<\<8))\
> \#define SQLITE_IOERR_BLOCKED (SQLITE_IOERR \| (11\<\<8))\
> \#define SQLITE_IOERR_NOMEM (SQLITE_IOERR \| (12\<\<8))\
> \#define SQLITE_IOERR_ACCESS (SQLITE_IOERR \| (13\<\<8))\
> \#define SQLITE_IOERR_CHECKRESERVEDLOCK (SQLITE_IOERR \| (14\<\<8))\
> \#define SQLITE_IOERR_LOCK (SQLITE_IOERR \| (15\<\<8))\
> \#define SQLITE_IOERR_CLOSE (SQLITE_IOERR \| (16\<\<8))\
> \#define SQLITE_IOERR_DIR_CLOSE (SQLITE_IOERR \| (17\<\<8))\
> \#define SQLITE_IOERR_SHMOPEN (SQLITE_IOERR \| (18\<\<8))\
> \#define SQLITE_IOERR_SHMSIZE (SQLITE_IOERR \| (19\<\<8))\
> \#define SQLITE_IOERR_SHMLOCK (SQLITE_IOERR \| (20\<\<8))\
> \#define SQLITE_IOERR_SHMMAP (SQLITE_IOERR \| (21\<\<8))\
> \#define SQLITE_IOERR_SEEK (SQLITE_IOERR \| (22\<\<8))\
> \#define SQLITE_IOERR_DELETE_NOENT (SQLITE_IOERR \| (23\<\<8))\
> \#define SQLITE_IOERR_MMAP (SQLITE_IOERR \| (24\<\<8))\
> \#define SQLITE_IOERR_GETTEMPPATH (SQLITE_IOERR \| (25\<\<8))\
> \#define SQLITE_IOERR_CONVPATH (SQLITE_IOERR \| (26\<\<8))\
> \#define SQLITE_IOERR_VNODE (SQLITE_IOERR \| (27\<\<8))\
> \#define SQLITE_IOERR_AUTH (SQLITE_IOERR \| (28\<\<8))\
> \#define SQLITE_IOERR_BEGIN_ATOMIC (SQLITE_IOERR \| (29\<\<8))\
> \#define SQLITE_IOERR_COMMIT_ATOMIC (SQLITE_IOERR \| (30\<\<8))\
> \#define SQLITE_IOERR_ROLLBACK_ATOMIC (SQLITE_IOERR \| (31\<\<8))\
> \#define SQLITE_IOERR_DATA (SQLITE_IOERR \| (32\<\<8))\
> \#define SQLITE_IOERR_CORRUPTFS (SQLITE_IOERR \| (33\<\<8))\
> \#define SQLITE_IOERR_IN_PAGE (SQLITE_IOERR \| (34\<\<8))\
> \#define SQLITE_IOERR_BADKEY (SQLITE_IOERR \| (35\<\<8))\
> \#define SQLITE_IOERR_CODEC (SQLITE_IOERR \| (36\<\<8))\
> \#define SQLITE_LOCKED_SHAREDCACHE (SQLITE_LOCKED \| (1\<\<8))\
> \#define SQLITE_LOCKED_VTAB (SQLITE_LOCKED \| (2\<\<8))\
> \#define SQLITE_BUSY_RECOVERY (SQLITE_BUSY \| (1\<\<8))\
> \#define SQLITE_BUSY_SNAPSHOT (SQLITE_BUSY \| (2\<\<8))\
> \#define SQLITE_BUSY_TIMEOUT (SQLITE_BUSY \| (3\<\<8))\
> \#define SQLITE_CANTOPEN_NOTEMPDIR (SQLITE_CANTOPEN \| (1\<\<8))\
> \#define SQLITE_CANTOPEN_ISDIR (SQLITE_CANTOPEN \| (2\<\<8))\
> \#define SQLITE_CANTOPEN_FULLPATH (SQLITE_CANTOPEN \| (3\<\<8))\
> \#define SQLITE_CANTOPEN_CONVPATH (SQLITE_CANTOPEN \| (4\<\<8))\
> \#define SQLITE_CANTOPEN_DIRTYWAL (SQLITE_CANTOPEN \| (5\<\<8)) /\* Not Used \*/\
> \#define SQLITE_CANTOPEN_SYMLINK (SQLITE_CANTOPEN \| (6\<\<8))\
> \#define SQLITE_CORRUPT_VTAB (SQLITE_CORRUPT \| (1\<\<8))\
> \#define SQLITE_CORRUPT_SEQUENCE (SQLITE_CORRUPT \| (2\<\<8))\
> \#define SQLITE_CORRUPT_INDEX (SQLITE_CORRUPT \| (3\<\<8))\
> \#define SQLITE_READONLY_RECOVERY (SQLITE_READONLY \| (1\<\<8))\
> \#define SQLITE_READONLY_CANTLOCK (SQLITE_READONLY \| (2\<\<8))\
> \#define SQLITE_READONLY_ROLLBACK (SQLITE_READONLY \| (3\<\<8))\
> \#define SQLITE_READONLY_DBMOVED (SQLITE_READONLY \| (4\<\<8))\
> \#define SQLITE_READONLY_CANTINIT (SQLITE_READONLY \| (5\<\<8))\
> \#define SQLITE_READONLY_DIRECTORY (SQLITE_READONLY \| (6\<\<8))\
> \#define SQLITE_ABORT_ROLLBACK (SQLITE_ABORT \| (2\<\<8))\
> \#define SQLITE_CONSTRAINT_CHECK (SQLITE_CONSTRAINT \| (1\<\<8))\
> \#define SQLITE_CONSTRAINT_COMMITHOOK (SQLITE_CONSTRAINT \| (2\<\<8))\
> \#define SQLITE_CONSTRAINT_FOREIGNKEY (SQLITE_CONSTRAINT \| (3\<\<8))\
> \#define SQLITE_CONSTRAINT_FUNCTION (SQLITE_CONSTRAINT \| (4\<\<8))\
> \#define SQLITE_CONSTRAINT_NOTNULL (SQLITE_CONSTRAINT \| (5\<\<8))\
> \#define SQLITE_CONSTRAINT_PRIMARYKEY (SQLITE_CONSTRAINT \| (6\<\<8))\
> \#define SQLITE_CONSTRAINT_TRIGGER (SQLITE_CONSTRAINT \| (7\<\<8))\
> \#define SQLITE_CONSTRAINT_UNIQUE (SQLITE_CONSTRAINT \| (8\<\<8))\
> \#define SQLITE_CONSTRAINT_VTAB (SQLITE_CONSTRAINT \| (9\<\<8))\
> \#define SQLITE_CONSTRAINT_ROWID (SQLITE_CONSTRAINT \|(10\<\<8))\
> \#define SQLITE_CONSTRAINT_PINNED (SQLITE_CONSTRAINT \|(11\<\<8))\
> \#define SQLITE_CONSTRAINT_DATATYPE (SQLITE_CONSTRAINT \|(12\<\<8))\
> \#define SQLITE_NOTICE_RECOVER_WAL (SQLITE_NOTICE \| (1\<\<8))\
> \#define SQLITE_NOTICE_RECOVER_ROLLBACK (SQLITE_NOTICE \| (2\<\<8))\
> \#define SQLITE_NOTICE_RBU (SQLITE_NOTICE \| (3\<\<8))\
> \#define SQLITE_WARNING_AUTOINDEX (SQLITE_WARNING \| (1\<\<8))\
> \#define SQLITE_AUTH_USER (SQLITE_AUTH \| (1\<\<8))\
> \#define SQLITE_OK_LOAD_PERMANENTLY (SQLITE_OK \| (1\<\<8))\
> \#define SQLITE_OK_SYMLINK (SQLITE_OK \| (2\<\<8)) /\* internal only \*/\
In its default configuration, SQLite API routines return one of 30 integer [result codes](rescode.md). However, experience has shown that many of these result codes are too coarse-grained. They do not provide as much information about problems as programmers might like. In an effort to address this, newer versions of SQLite (version 3.3.8 2006-10-09 and later) include support for additional result codes that provide more detailed information about errors. These [extended result codes](rescode.md#extrc) are enabled or disabled on a per database connection basis using the [sqlite3_extended_result_codes()](#sqlite3_extended_result_codes) API. Or, the extended code for the most recent error can be obtained using [sqlite3_extended_errcode()](#sqlite3_errcode).
------------------------------------------------------------------------
## Flags for the xAccess VFS method
> \
> \#define SQLITE_ACCESS_EXISTS 0\
> \#define SQLITE_ACCESS_READWRITE 1 /\* Used by PRAGMA temp_store_directory \*/\
> \#define SQLITE_ACCESS_READ 2 /\* Unused \*/\
These integer constants can be used as the third parameter to the xAccess method of an [sqlite3_vfs](#sqlite3_vfs) object. They determine what kind of permissions the xAccess method is looking for. With SQLITE_ACCESS_EXISTS, the xAccess method simply checks whether the file exists. With SQLITE_ACCESS_READWRITE, the xAccess method checks whether the named directory is both readable and writable (in other words, if files can be added, removed, and renamed within the directory). The SQLITE_ACCESS_READWRITE constant is currently used only by the [temp_store_directory pragma](pragma.md#pragma_temp_store_directory), though this could change in a future release of SQLite. With SQLITE_ACCESS_READ, the xAccess method checks whether the file is readable. The SQLITE_ACCESS_READ constant is currently unused, though it might be used in a future release of SQLite.
------------------------------------------------------------------------
## Authorizer Action Codes
> \
> /\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* 3rd \*\*\*\*\*\*\*\*\*\*\*\* 4th \*\*\*\*\*\*\*\*\*\*\*/\
> \#define SQLITE_CREATE_INDEX 1 /\* Index Name Table Name \*/\
> \#define SQLITE_CREATE_TABLE 2 /\* Table Name NULL \*/\
> \#define SQLITE_CREATE_TEMP_INDEX 3 /\* Index Name Table Name \*/\
> \#define SQLITE_CREATE_TEMP_TABLE 4 /\* Table Name NULL \*/\
> \#define SQLITE_CREATE_TEMP_TRIGGER 5 /\* Trigger Name Table Name \*/\
> \#define SQLITE_CREATE_TEMP_VIEW 6 /\* View Name NULL \*/\
> \#define SQLITE_CREATE_TRIGGER 7 /\* Trigger Name Table Name \*/\
> \#define SQLITE_CREATE_VIEW 8 /\* View Name NULL \*/\
> \#define SQLITE_DELETE 9 /\* Table Name NULL \*/\
> \#define SQLITE_DROP_INDEX 10 /\* Index Name Table Name \*/\
> \#define SQLITE_DROP_TABLE 11 /\* Table Name NULL \*/\
> \#define SQLITE_DROP_TEMP_INDEX 12 /\* Index Name Table Name \*/\
> \#define SQLITE_DROP_TEMP_TABLE 13 /\* Table Name NULL \*/\
> \#define SQLITE_DROP_TEMP_TRIGGER 14 /\* Trigger Name Table Name \*/\
> \#define SQLITE_DROP_TEMP_VIEW 15 /\* View Name NULL \*/\
> \#define SQLITE_DROP_TRIGGER 16 /\* Trigger Name Table Name \*/\
> \#define SQLITE_DROP_VIEW 17 /\* View Name NULL \*/\
> \#define SQLITE_INSERT 18 /\* Table Name NULL \*/\
> \#define SQLITE_PRAGMA 19 /\* Pragma Name 1st arg or NULL \*/\
> \#define SQLITE_READ 20 /\* Table Name Column Name \*/\
> \#define SQLITE_SELECT 21 /\* NULL NULL \*/\
> \#define SQLITE_TRANSACTION 22 /\* Operation NULL \*/\
> \#define SQLITE_UPDATE 23 /\* Table Name Column Name \*/\
> \#define SQLITE_ATTACH 24 /\* Filename NULL \*/\
> \#define SQLITE_DETACH 25 /\* Database Name NULL \*/\
> \#define SQLITE_ALTER_TABLE 26 /\* Database Name Table Name \*/\
> \#define SQLITE_REINDEX 27 /\* Index Name NULL \*/\
> \#define SQLITE_ANALYZE 28 /\* Table Name NULL \*/\
> \#define SQLITE_CREATE_VTABLE 29 /\* Table Name Module Name \*/\
> \#define SQLITE_DROP_VTABLE 30 /\* Table Name Module Name \*/\
> \#define SQLITE_FUNCTION 31 /\* NULL Function Name \*/\
> \#define SQLITE_SAVEPOINT 32 /\* Operation Savepoint Name \*/\
> \#define SQLITE_COPY 0 /\* No longer used \*/\
> \#define SQLITE_RECURSIVE 33 /\* NULL NULL \*/\
The [sqlite3_set_authorizer()](#sqlite3_set_authorizer) interface registers a callback function that is invoked to authorize certain SQL statement actions. The second parameter to the callback is an integer code that specifies what action is being authorized. These are the integer action codes that the authorizer callback may be passed.
These action code values signify what kind of operation is to be authorized. The 3rd and 4th parameters to the authorization callback function will be parameters or NULL depending on which of these codes is used as the second parameter. The 5th parameter to the authorizer callback is the name of the database ("main", "temp", etc.) if applicable. The 6th parameter to the authorizer callback is the name of the inner-most trigger or view that is responsible for the access attempt or NULL if this access attempt is directly from top-level SQL code.
------------------------------------------------------------------------
## Text Encodings
> \
> \#define SQLITE_UTF8 1 /\* IMP: R-37514-35566 \*/\
> \#define SQLITE_UTF16LE 2 /\* IMP: R-03371-37637 \*/\
> \#define SQLITE_UTF16BE 3 /\* IMP: R-51971-34154 \*/\
> \#define SQLITE_UTF16 4 /\* Use native byte order \*/\
> \#define SQLITE_ANY 5 /\* Deprecated \*/\
> \#define SQLITE_UTF16_ALIGNED 8 /\* sqlite3_create_collation only \*/\
> \#define SQLITE_UTF8_ZT 16 /\* Zero-terminated UTF8 \*/\
These constants define integer codes that represent the various text encodings supported by SQLite.
SQLITE_UTF8
Text is encoding as UTF-8
SQLITE_UTF16LE
Text is encoding as UTF-16 with each code point being expressed "little endian" - the least significant byte first. This is the usual encoding, for example on Windows.
SQLITE_UTF16BE
Text is encoding as UTF-16 with each code point being expressed "big endian" - the most significant byte first. This encoding is less common, but is still sometimes seen, specially on older systems.
SQLITE_UTF16
Text is encoding as UTF-16 with each code point being expressed either little endian or as big endian, according to the native endianness of the host computer.
SQLITE_ANY
This encoding value may only be used to declare the preferred text for [application-defined SQL functions](appfunc.md) created using [sqlite3_create_function()](#sqlite3_create_function) and similar. If the preferred encoding (the 4th parameter to sqlite3_create_function() - the eTextRep parameter) is SQLITE_ANY, that indicates that the function does not have a preference regarding the text encoding of its parameters and can take any text encoding that the SQLite core find convenient to supply. This option is deprecated. Please do not use it in new applications.
SQLITE_UTF16_ALIGNED
This encoding value may be used as the 3rd parameter (the eTextRep parameter) to [sqlite3_create_collation()](#sqlite3_create_collation) and similar. This encoding value means that the application-defined collating sequence created expects its input strings to be in UTF16 in native byte order, and that the start of the strings must be aligned to a 2-byte boundary.
SQLITE_UTF8_ZT
This option can only be used to specify the text encoding to strings input to [sqlite3_result_text64()](#sqlite3_result_blob) and [sqlite3_bind_text64()](#sqlite3_bind_blob). The SQLITE_UTF8_ZT encoding means that the input string (call it "z") is UTF-8 encoded and that it is zero-terminated. If the length parameter (call it "n") is non-negative, this encoding option means that the caller guarantees that z array contains at least n+1 bytes and that the z\[n\] byte has a value of zero. This option gives the same output as SQLITE_UTF8, but can be more efficient by avoiding the need to make a copy of the input string, in some cases. However, if z is allocated to hold fewer than n+1 bytes or if the z\[n\] byte is not zero, undefined behavior may result.
------------------------------------------------------------------------
## Fundamental Datatypes
> \
> \#define SQLITE_INTEGER 1\
> \#define SQLITE_FLOAT 2\
> \#define SQLITE_BLOB 4\
> \#define SQLITE_NULL 5\
> \#ifdef SQLITE_TEXT\
> \# undef SQLITE_TEXT\
> \#else\
> \# define SQLITE_TEXT 3\
> \#endif\
> \#define SQLITE3_TEXT 3\
Every value in SQLite has one of five fundamental datatypes:
- 64-bit signed integer
- 64-bit IEEE floating point number
- string
- BLOB
- NULL
These constants are codes for each of those types.
Note that the SQLITE_TEXT constant was also used in SQLite version 2 for a completely different meaning. Software that links against both SQLite version 2 and SQLite version 3 should use SQLITE3_TEXT, not SQLITE_TEXT.
------------------------------------------------------------------------
## Datatypes for the CARRAY table-valued function
> \
> \#define SQLITE_CARRAY_INT32 0 /\* Data is 32-bit signed integers \*/\
> \#define SQLITE_CARRAY_INT64 1 /\* Data is 64-bit signed integers \*/\
> \#define SQLITE_CARRAY_DOUBLE 2 /\* Data is doubles \*/\
> \#define SQLITE_CARRAY_TEXT 3 /\* Data is char\* \*/\
> \#define SQLITE_CARRAY_BLOB 4 /\* Data is struct iovec \*/\
The fifth argument to the [sqlite3_carray_bind()](#sqlite3_carray_bind) interface musts be one of the following constants, to specify the datatype of the array that is being bound into the [carray table-valued function](carray.md).
------------------------------------------------------------------------
## Checkpoint Mode Values
> \
> \#define SQLITE_CHECKPOINT_NOOP -1 /\* Do no work at all \*/\
> \#define SQLITE_CHECKPOINT_PASSIVE 0 /\* Do as much as possible w/o blocking \*/\
> \#define SQLITE_CHECKPOINT_FULL 1 /\* Wait for writers, then checkpoint \*/\
> \#define SQLITE_CHECKPOINT_RESTART 2 /\* Like FULL but wait for readers \*/\
> \#define SQLITE_CHECKPOINT_TRUNCATE 3 /\* Like RESTART but also truncate WAL \*/\
These constants define all valid values for the "checkpoint mode" passed as the third parameter to the [sqlite3_wal_checkpoint_v2()](#sqlite3_wal_checkpoint_v2) interface. See the [sqlite3_wal_checkpoint_v2()](#sqlite3_wal_checkpoint_v2) documentation for details on the meaning of each of these checkpoint modes.
------------------------------------------------------------------------
## Configuration Options
> \
> \#define SQLITE_CONFIG_SINGLETHREAD 1 /\* nil \*/\
> \#define SQLITE_CONFIG_MULTITHREAD 2 /\* nil \*/\
> \#define SQLITE_CONFIG_SERIALIZED 3 /\* nil \*/\
> \#define SQLITE_CONFIG_MALLOC 4 /\* sqlite3_mem_methods\* \*/\
> \#define SQLITE_CONFIG_GETMALLOC 5 /\* sqlite3_mem_methods\* \*/\
> \#define SQLITE_CONFIG_SCRATCH 6 /\* No longer used \*/\
> \#define SQLITE_CONFIG_PAGECACHE 7 /\* void\*, int sz, int N \*/\
> \#define SQLITE_CONFIG_HEAP 8 /\* void\*, int nByte, int min \*/\
> \#define SQLITE_CONFIG_MEMSTATUS 9 /\* boolean \*/\
> \#define SQLITE_CONFIG_MUTEX 10 /\* sqlite3_mutex_methods\* \*/\
> \#define SQLITE_CONFIG_GETMUTEX 11 /\* sqlite3_mutex_methods\* \*/\
> /\* previously SQLITE_CONFIG_CHUNKALLOC 12 which is now unused. \*/\
> \#define SQLITE_CONFIG_LOOKASIDE 13 /\* int int \*/\
> \#define SQLITE_CONFIG_PCACHE 14 /\* no-op \*/\
> \#define SQLITE_CONFIG_GETPCACHE 15 /\* no-op \*/\
> \#define SQLITE_CONFIG_LOG 16 /\* xFunc, void\* \*/\
> \#define SQLITE_CONFIG_URI 17 /\* int \*/\
> \#define SQLITE_CONFIG_PCACHE2 18 /\* sqlite3_pcache_methods2\* \*/\
> \#define SQLITE_CONFIG_GETPCACHE2 19 /\* sqlite3_pcache_methods2\* \*/\
> \#define SQLITE_CONFIG_COVERING_INDEX_SCAN 20 /\* int \*/\
> \#define SQLITE_CONFIG_SQLLOG 21 /\* xSqllog, void\* \*/\
> \#define SQLITE_CONFIG_MMAP_SIZE 22 /\* sqlite3_int64, sqlite3_int64 \*/\
> \#define SQLITE_CONFIG_WIN32_HEAPSIZE 23 /\* int nByte \*/\
> \#define SQLITE_CONFIG_PCACHE_HDRSZ 24 /\* int \*psz \*/\
> \#define SQLITE_CONFIG_PMASZ 25 /\* unsigned int szPma \*/\
> \#define SQLITE_CONFIG_STMTJRNL_SPILL 26 /\* int nByte \*/\
> \#define SQLITE_CONFIG_SMALL_MALLOC 27 /\* boolean \*/\
> \#define SQLITE_CONFIG_SORTERREF_SIZE 28 /\* int nByte \*/\
> \#define SQLITE_CONFIG_MEMDB_MAXSIZE 29 /\* sqlite3_int64 \*/\
> \#define SQLITE_CONFIG_ROWID_IN_VIEW 30 /\* int\* \*/\
These constants are the available integer configuration options that can be passed as the first argument to the [sqlite3_config()](#sqlite3_config) interface.
Most of the configuration options for sqlite3_config() will only work if invoked prior to [sqlite3_initialize()](#sqlite3_initialize) or after [sqlite3_shutdown()](#sqlite3_initialize). The few exceptions to this rule are called "anytime configuration options". Calling [sqlite3_config()](#sqlite3_config) with a first argument that is not an anytime configuration option in between calls to [sqlite3_initialize()](#sqlite3_initialize) and [sqlite3_shutdown()](#sqlite3_initialize) is a no-op that returns SQLITE_MISUSE.
The set of anytime configuration options can change (by insertions and/or deletions) from one release of SQLite to the next. As of SQLite version 3.42.0, the complete set of anytime configuration options is:
- SQLITE_CONFIG_LOG
- SQLITE_CONFIG_PCACHE_HDRSZ
New configuration options may be added in future releases of SQLite. Existing configuration options might be discontinued. Applications should check the return code from [sqlite3_config()](#sqlite3_config) to make sure that the call worked. The [sqlite3_config()](#sqlite3_config) interface will return a non-zero [error code](rescode.md) if a discontinued or unsupported configuration option is invoked.
SQLITE_CONFIG_SINGLETHREAD
There are no arguments to this option. This option sets the [threading mode](threadsafe.md) to Single-thread. In other words, it disables all mutexing and puts SQLite into a mode where it can only be used by a single thread. If SQLite is compiled with the [SQLITE_THREADSAFE=0](compile.md#threadsafe) compile-time option then it is not possible to change the [threading mode](threadsafe.md) from its default value of Single-thread and so [sqlite3_config()](#sqlite3_config) will return [SQLITE_ERROR](#SQLITE_ABORT) if called with the SQLITE_CONFIG_SINGLETHREAD configuration option.
SQLITE_CONFIG_MULTITHREAD
There are no arguments to this option. This option sets the [threading mode](threadsafe.md) to Multi-thread. In other words, it disables mutexing on [database connection](#sqlite3) and [prepared statement](#sqlite3_stmt) objects. The application is responsible for serializing access to [database connections](#sqlite3) and [prepared statements](#sqlite3_stmt). But other mutexes are enabled so that SQLite will be safe to use in a multi-threaded environment as long as no two threads attempt to use the same [database connection](#sqlite3) at the same time. If SQLite is compiled with the [SQLITE_THREADSAFE=0](compile.md#threadsafe) compile-time option then it is not possible to set the Multi-thread [threading mode](threadsafe.md) and [sqlite3_config()](#sqlite3_config) will return [SQLITE_ERROR](#SQLITE_ABORT) if called with the SQLITE_CONFIG_MULTITHREAD configuration option.
SQLITE_CONFIG_SERIALIZED
There are no arguments to this option. This option sets the [threading mode](threadsafe.md) to Serialized. In other words, this option enables all mutexes including the recursive mutexes on [database connection](#sqlite3) and [prepared statement](#sqlite3_stmt) objects. In this mode (which is the default when SQLite is compiled with [SQLITE_THREADSAFE=1](compile.md#threadsafe)) the SQLite library will itself serialize access to [database connections](#sqlite3) and [prepared statements](#sqlite3_stmt) so that the application is free to use the same [database connection](#sqlite3) or the same [prepared statement](#sqlite3_stmt) in different threads at the same time. If SQLite is compiled with the [SQLITE_THREADSAFE=0](compile.md#threadsafe) compile-time option then it is not possible to set the Serialized [threading mode](threadsafe.md) and [sqlite3_config()](#sqlite3_config) will return [SQLITE_ERROR](#SQLITE_ABORT) if called with the SQLITE_CONFIG_SERIALIZED configuration option.
SQLITE_CONFIG_MALLOC
The SQLITE_CONFIG_MALLOC option takes a single argument which is a pointer to an instance of the [sqlite3_mem_methods](#sqlite3_mem_methods) structure. The argument specifies alternative low-level memory allocation routines to be used in place of the memory allocation routines built into SQLite. SQLite makes its own private copy of the content of the [sqlite3_mem_methods](#sqlite3_mem_methods) structure before the [sqlite3_config()](#sqlite3_config) call returns.
SQLITE_CONFIG_GETMALLOC
The SQLITE_CONFIG_GETMALLOC option takes a single argument which is a pointer to an instance of the [sqlite3_mem_methods](#sqlite3_mem_methods) structure. The [sqlite3_mem_methods](#sqlite3_mem_methods) structure is filled with the currently defined memory allocation routines. This option can be used to overload the default memory allocation routines with a wrapper that simulates memory allocation failure or tracks memory usage, for example.
SQLITE_CONFIG_SMALL_MALLOC
The SQLITE_CONFIG_SMALL_MALLOC option takes a single argument of type int, interpreted as a boolean, which if true provides a hint to SQLite that it should avoid large memory allocations if possible. SQLite will run faster if it is free to make large memory allocations, but some applications might prefer to run slower in exchange for guarantees about memory fragmentation that are possible if large allocations are avoided. This hint is normally off.
SQLITE_CONFIG_MEMSTATUS
The SQLITE_CONFIG_MEMSTATUS option takes a single argument of type int, interpreted as a boolean, which enables or disables the collection of memory allocation statistics. When memory allocation statistics are disabled, the following SQLite interfaces become non-operational:
- [sqlite3_hard_heap_limit64()](#sqlite3_hard_heap_limit64)
- [sqlite3_memory_used()](#sqlite3_memory_highwater)
- [sqlite3_memory_highwater()](#sqlite3_memory_highwater)
- [sqlite3_soft_heap_limit64()](#sqlite3_hard_heap_limit64)
- [sqlite3_status64()](#sqlite3_status)
Memory allocation statistics are enabled by default unless SQLite is compiled with [SQLITE_DEFAULT_MEMSTATUS](compile.md#default_memstatus)=0 in which case memory allocation statistics are disabled by default.
SQLITE_CONFIG_SCRATCH
The SQLITE_CONFIG_SCRATCH option is no longer used.
SQLITE_CONFIG_PAGECACHE
The SQLITE_CONFIG_PAGECACHE option specifies a memory pool that SQLite can use for the database page cache with the default page cache implementation. This configuration option is a no-op if an application-defined page cache implementation is loaded using the [SQLITE_CONFIG_PCACHE2](#sqliteconfigpcache2). There are three arguments to SQLITE_CONFIG_PAGECACHE: A pointer to 8-byte aligned memory (pMem), the size of each page cache line (sz), and the number of cache lines (N). The sz argument should be the size of the largest database page (a power of two between 512 and 65536) plus some extra bytes for each page header. The number of extra bytes needed by the page header can be determined using [SQLITE_CONFIG_PCACHE_HDRSZ](#sqliteconfigpcachehdrsz). It is harmless, apart from the wasted memory, for the sz parameter to be larger than necessary. The pMem argument must be either a NULL pointer or a pointer to an 8-byte aligned block of memory of at least sz\*N bytes, otherwise subsequent behavior is undefined. When pMem is not NULL, SQLite will strive to use the memory provided to satisfy page cache needs, falling back to [sqlite3_malloc()](#sqlite3_free) if a page cache line is larger than sz bytes or if all of the pMem buffer is exhausted. If pMem is NULL and N is non-zero, then each database connection does an initial bulk allocation for page cache memory from [sqlite3_malloc()](#sqlite3_free) sufficient for N cache lines if N is positive or of -1024\*N bytes if N is negative. If additional page cache memory is needed beyond what is provided by the initial allocation, then SQLite goes to [sqlite3_malloc()](#sqlite3_free) separately for each additional cache line.
SQLITE_CONFIG_HEAP
The SQLITE_CONFIG_HEAP option specifies a static memory buffer that SQLite will use for all of its dynamic memory allocation needs beyond those provided for by [SQLITE_CONFIG_PAGECACHE](#sqliteconfigpagecache). The SQLITE_CONFIG_HEAP option is only available if SQLite is compiled with either [SQLITE_ENABLE_MEMSYS3](compile.md#enable_memsys3) or [SQLITE_ENABLE_MEMSYS5](compile.md#enable_memsys5) and returns [SQLITE_ERROR](#SQLITE_ABORT) if invoked otherwise. There are three arguments to SQLITE_CONFIG_HEAP: An 8-byte aligned pointer to the memory, the number of bytes in the memory buffer, and the minimum allocation size. If the first pointer (the memory pointer) is NULL, then SQLite reverts to using its default memory allocator (the system malloc() implementation), undoing any prior invocation of [SQLITE_CONFIG_MALLOC](#sqliteconfigmalloc). If the memory pointer is not NULL then the alternative memory allocator is engaged to handle all of SQLites memory allocation needs. The first pointer (the memory pointer) must be aligned to an 8-byte boundary or subsequent behavior of SQLite will be undefined. The minimum allocation size is capped at 2\*\*12. Reasonable values for the minimum allocation size are 2\*\*5 through 2\*\*8.
SQLITE_CONFIG_MUTEX
The SQLITE_CONFIG_MUTEX option takes a single argument which is a pointer to an instance of the [sqlite3_mutex_methods](#sqlite3_mutex_methods) structure. The argument specifies alternative low-level mutex routines to be used in place of the mutex routines built into SQLite. SQLite makes a copy of the content of the [sqlite3_mutex_methods](#sqlite3_mutex_methods) structure before the call to [sqlite3_config()](#sqlite3_config) returns. If SQLite is compiled with the [SQLITE_THREADSAFE=0](compile.md#threadsafe) compile-time option then the entire mutexing subsystem is omitted from the build and hence calls to [sqlite3_config()](#sqlite3_config) with the SQLITE_CONFIG_MUTEX configuration option will return [SQLITE_ERROR](#SQLITE_ABORT).
SQLITE_CONFIG_GETMUTEX
The SQLITE_CONFIG_GETMUTEX option takes a single argument which is a pointer to an instance of the [sqlite3_mutex_methods](#sqlite3_mutex_methods) structure. The [sqlite3_mutex_methods](#sqlite3_mutex_methods) structure is filled with the currently defined mutex routines. This option can be used to overload the default mutex allocation routines with a wrapper used to track mutex usage for performance profiling or testing, for example. If SQLite is compiled with the [SQLITE_THREADSAFE=0](compile.md#threadsafe) compile-time option then the entire mutexing subsystem is omitted from the build and hence calls to [sqlite3_config()](#sqlite3_config) with the SQLITE_CONFIG_GETMUTEX configuration option will return [SQLITE_ERROR](#SQLITE_ABORT).
SQLITE_CONFIG_LOOKASIDE
The SQLITE_CONFIG_LOOKASIDE option takes two arguments that determine the default size of [lookaside memory](malloc.md#lookaside) on each [database connection](#sqlite3). The first argument is the size of each lookaside buffer slot ("sz") and the second is the number of slots allocated to each database connection ("cnt"). SQLITE_CONFIG_LOOKASIDE sets the *default* lookaside size. The [SQLITE_DBCONFIG_LOOKASIDE](#sqlitedbconfiglookaside) option to [sqlite3_db_config()](#sqlite3_db_config) can be used to change the lookaside configuration on individual connections. The [-DSQLITE_DEFAULT_LOOKASIDE](compile.md#default_lookaside) option can be used to change the default lookaside configuration at compile-time.
SQLITE_CONFIG_PCACHE2
The SQLITE_CONFIG_PCACHE2 option takes a single argument which is a pointer to an [sqlite3_pcache_methods2](#sqlite3_pcache_methods2) object. This object specifies the interface to a custom page cache implementation. SQLite makes a copy of the [sqlite3_pcache_methods2](#sqlite3_pcache_methods2) object.
SQLITE_CONFIG_GETPCACHE2
The SQLITE_CONFIG_GETPCACHE2 option takes a single argument which is a pointer to an [sqlite3_pcache_methods2](#sqlite3_pcache_methods2) object. SQLite copies off the current page cache implementation into that object.
SQLITE_CONFIG_LOG
The SQLITE_CONFIG_LOG option is used to configure the SQLite global [error log](errlog.md). (The SQLITE_CONFIG_LOG option takes two arguments: a pointer to a function with a call signature of void(\*)(void\*,int,const char\*), and a pointer to void. If the function pointer is not NULL, it is invoked by [sqlite3_log()](#sqlite3_log) to process each logging event. If the function pointer is NULL, the [sqlite3_log()](#sqlite3_log) interface becomes a no-op. The void pointer that is the second argument to SQLITE_CONFIG_LOG is passed through as the first parameter to the application-defined logger function whenever that function is invoked. The second parameter to the logger function is a copy of the first parameter to the corresponding [sqlite3_log()](#sqlite3_log) call and is intended to be a [result code](rescode.md) or an [extended result code](rescode.md#extrc). The third parameter passed to the logger is a log message after formatting via [sqlite3_snprintf()](#sqlite3_mprintf). The SQLite logging interface is not reentrant; the logger function supplied by the application must not invoke any SQLite interface. In a multi-threaded application, the application-defined logger function must be threadsafe.
SQLITE_CONFIG_URI
The SQLITE_CONFIG_URI option takes a single argument of type int. If non-zero, then URI handling is globally enabled. If the parameter is zero, then URI handling is globally disabled. If URI handling is globally enabled, all filenames passed to [sqlite3_open()](#sqlite3_open), [sqlite3_open_v2()](#sqlite3_open), [sqlite3_open16()](#sqlite3_open) or specified as part of [ATTACH](lang_attach.md) commands are interpreted as URIs, regardless of whether or not the [SQLITE_OPEN_URI](#SQLITE_OPEN_AUTOPROXY) flag is set when the database connection is opened. If it is globally disabled, filenames are only interpreted as URIs if the SQLITE_OPEN_URI flag is set when the database connection is opened. By default, URI handling is globally disabled. The default value may be changed by compiling with the [SQLITE_USE_URI](compile.md#use_uri) symbol defined.
SQLITE_CONFIG_COVERING_INDEX_SCAN
The SQLITE_CONFIG_COVERING_INDEX_SCAN option takes a single integer argument which is interpreted as a boolean in order to enable or disable the use of covering indices for full table scans in the query optimizer. The default setting is determined by the [SQLITE_ALLOW_COVERING_INDEX_SCAN](compile.md#allow_covering_index_scan) compile-time option, or is "on" if that compile-time option is omitted. The ability to disable the use of covering indices for full table scans is because some incorrectly coded legacy applications might malfunction when the optimization is enabled. Providing the ability to disable the optimization allows the older, buggy application code to work without change even with newer versions of SQLite.
SQLITE_CONFIG_PCACHE and SQLITE_CONFIG_GETPCACHE
These options are obsolete and should not be used by new code. They are retained for backwards compatibility but are now no-ops.
SQLITE_CONFIG_SQLLOG
This option is only available if sqlite is compiled with the [SQLITE_ENABLE_SQLLOG](compile.md#enable_sqllog) pre-processor macro defined. The first argument should be a pointer to a function of type void(\*)(void\*,sqlite3\*,const char\*, int). The second should be of type (void\*). The callback is invoked by the library in three separate circumstances, identified by the value passed as the fourth parameter. If the fourth parameter is 0, then the database connection passed as the second argument has just been opened. The third argument points to a buffer containing the name of the main database file. If the fourth parameter is 1, then the SQL statement that the third parameter points to has just been executed. Or, if the fourth parameter is 2, then the connection being passed as the second parameter is being closed. The third parameter is passed NULL In this case. An example of using this configuration option can be seen in the "test_sqllog.c" source file in the canonical SQLite source tree.
SQLITE_CONFIG_MMAP_SIZE
SQLITE_CONFIG_MMAP_SIZE takes two 64-bit integer (sqlite3_int64) values that are the default mmap size limit (the default setting for [PRAGMA mmap_size](pragma.md#pragma_mmap_size)) and the maximum allowed mmap size limit. The default setting can be overridden by each database connection using either the [PRAGMA mmap_size](pragma.md#pragma_mmap_size) command, or by using the [SQLITE_FCNTL_MMAP_SIZE](#sqlitefcntlmmapsize) file control. The maximum allowed mmap size will be silently truncated if necessary so that it does not exceed the compile-time maximum mmap size set by the [SQLITE_MAX_MMAP_SIZE](compile.md#max_mmap_size) compile-time option. If either argument to this option is negative, then that argument is changed to its compile-time default.
SQLITE_CONFIG_WIN32_HEAPSIZE
The SQLITE_CONFIG_WIN32_HEAPSIZE option is only available if SQLite is compiled for Windows with the [SQLITE_WIN32_MALLOC](compile.md#win32_malloc) pre-processor macro defined. SQLITE_CONFIG_WIN32_HEAPSIZE takes a 32-bit unsigned integer value that specifies the maximum size of the created heap.
SQLITE_CONFIG_PCACHE_HDRSZ
The SQLITE_CONFIG_PCACHE_HDRSZ option takes a single parameter which is a pointer to an integer and writes into that integer the number of extra bytes per page required for each page in [SQLITE_CONFIG_PAGECACHE](#sqliteconfigpagecache). The amount of extra space required can change depending on the compiler, target platform, and SQLite version.
SQLITE_CONFIG_PMASZ
The SQLITE_CONFIG_PMASZ option takes a single parameter which is an unsigned integer and sets the "Minimum PMA Size" for the multithreaded sorter to that integer. The default minimum PMA Size is set by the [SQLITE_SORTER_PMASZ](compile.md#sorter_pmasz) compile-time option. New threads are launched to help with sort operations when multithreaded sorting is enabled (using the [PRAGMA threads](pragma.md#pragma_threads) command) and the amount of content to be sorted exceeds the page size times the minimum of the [PRAGMA cache_size](pragma.md#pragma_cache_size) setting and this value.
SQLITE_CONFIG_STMTJRNL_SPILL
The SQLITE_CONFIG_STMTJRNL_SPILL option takes a single parameter which becomes the [statement journal](tempfiles.md#stmtjrnl) spill-to-disk threshold. [Statement journals](tempfiles.md#stmtjrnl) are held in memory until their size (in bytes) exceeds this threshold, at which point they are written to disk. Or if the threshold is -1, statement journals are always held exclusively in memory. Since many statement journals never become large, setting the spill threshold to a value such as 64KiB can greatly reduce the amount of I/O required to support statement rollback. The default value for this setting is controlled by the [SQLITE_STMTJRNL_SPILL](compile.md#stmtjrnl_spill) compile-time option.
SQLITE_CONFIG_SORTERREF_SIZE
The SQLITE_CONFIG_SORTERREF_SIZE option accepts a single parameter of type (int) - the new value of the sorter-reference size threshold. Usually, when SQLite uses an external sort to order records according to an ORDER BY clause, all fields required by the caller are present in the sorted records. However, if SQLite determines based on the declared type of a table column that its values are likely to be very large - larger than the configured sorter-reference size threshold - then a reference is stored in each sorted record and the required column values loaded from the database as records are returned in sorted order. The default value for this option is to never use this optimization. Specifying a negative value for this option restores the default behavior. This option is only available if SQLite is compiled with the [SQLITE_ENABLE_SORTER_REFERENCES](compile.md#enable_sorter_references) compile-time option.
SQLITE_CONFIG_MEMDB_MAXSIZE
The SQLITE_CONFIG_MEMDB_MAXSIZE option accepts a single parameter [sqlite3_int64](#sqlite3_int64) parameter which is the default maximum size for an in-memory database created using [sqlite3_deserialize()](#sqlite3_deserialize). This default maximum size can be adjusted up or down for individual databases using the [SQLITE_FCNTL_SIZE_LIMIT](#sqlitefcntlsizelimit) [file-control](#sqlite3_file_control). If this configuration setting is never used, then the default maximum is determined by the [SQLITE_MEMDB_DEFAULT_MAXSIZE](compile.md#memdb_default_maxsize) compile-time option. If that compile-time option is not set, then the default maximum is 1073741824.
SQLITE_CONFIG_ROWID_IN_VIEW
The SQLITE_CONFIG_ROWID_IN_VIEW option enables or disables the ability for VIEWs to have a ROWID. The capability can only be enabled if SQLite is compiled with -DSQLITE_ALLOW_ROWID_IN_VIEW, in which case the capability defaults to on. This configuration option queries the current setting or changes the setting to off or on. The argument is a pointer to an integer. If that integer initially holds a value of 1, then the ability for VIEWs to have ROWIDs is activated. If the integer initially holds zero, then the ability is deactivated. Any other initial value for the integer leaves the setting unchanged. After changes, if any, the integer is written with a 1 or 0, if the ability for VIEWs to have ROWIDs is on or off. If SQLite is compiled without -DSQLITE_ALLOW_ROWID_IN_VIEW (which is the usual and recommended case) then the integer is always filled with zero, regardless if its initial value.
------------------------------------------------------------------------
## Database Connection Configuration Options
> \
> \#define SQLITE_DBCONFIG_MAINDBNAME 1000 /\* const char\* \*/\
> \#define SQLITE_DBCONFIG_LOOKASIDE 1001 /\* void\* int int \*/\
> \#define SQLITE_DBCONFIG_ENABLE_FKEY 1002 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_ENABLE_TRIGGER 1003 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER 1004 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION 1005 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE 1006 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_ENABLE_QPSG 1007 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_TRIGGER_EQP 1008 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_RESET_DATABASE 1009 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_DEFENSIVE 1010 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_WRITABLE_SCHEMA 1011 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_LEGACY_ALTER_TABLE 1012 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_DQS_DML 1013 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_DQS_DDL 1014 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_ENABLE_VIEW 1015 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_LEGACY_FILE_FORMAT 1016 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_TRUSTED_SCHEMA 1017 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_STMT_SCANSTATUS 1018 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_REVERSE_SCANORDER 1019 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_ENABLE_ATTACH_CREATE 1020 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_ENABLE_ATTACH_WRITE 1021 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_ENABLE_COMMENTS 1022 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_FP_DIGITS 1023 /\* int int\* \*/\
> \#define SQLITE_DBCONFIG_MAX 1023 /\* Largest DBCONFIG \*/\
These constants are the available integer configuration options that can be passed as the second parameter to the [sqlite3_db_config()](#sqlite3_db_config) interface.
The [sqlite3_db_config()](#sqlite3_db_config) interface is a var-args function. It takes a variable number of parameters, though always at least two. The number of parameters passed into sqlite3_db_config() depends on which of these constants is given as the second parameter. This documentation page refers to parameters beyond the second as "arguments". Thus, when this page says "the N-th argument" it means "the N-th parameter past the configuration option" or "the (N+2)-th parameter to sqlite3_db_config()".
New configuration options may be added in future releases of SQLite. Existing configuration options might be discontinued. Applications should check the return code from [sqlite3_db_config()](#sqlite3_db_config) to make sure that the call worked. The [sqlite3_db_config()](#sqlite3_db_config) interface will return a non-zero [error code](rescode.md) if a discontinued or unsupported configuration option is invoked.
SQLITE_DBCONFIG_LOOKASIDE
The SQLITE_DBCONFIG_LOOKASIDE option is used to adjust the configuration of the [lookaside memory allocator](malloc.md#lookaside) within a database connection. The arguments to the SQLITE_DBCONFIG_LOOKASIDE option are *not* in the [usual format](#dbconfigarguments). The SQLITE_DBCONFIG_LOOKASIDE option takes three arguments, not two, so that a call to [sqlite3_db_config()](#sqlite3_db_config) that uses SQLITE_DBCONFIG_LOOKASIDE should have a total of five parameters.
1. The first argument ("buf") is a pointer to a memory buffer to use for lookaside memory. The first argument may be NULL in which case SQLite will allocate the lookaside buffer itself using [sqlite3_malloc()](#sqlite3_free).
2. The second argument ("sz") is the size of each lookaside buffer slot. Lookaside is disabled if "sz" is less than 8. The "sz" argument should be a multiple of 8 less than 65536. If "sz" does not meet this constraint, it is reduced in size until it does.
3. The third argument ("cnt") is the number of slots. Lookaside is disabled if "cnt"is less than 1. that the product of "sz" and "cnt" does not exceed 2,147,418,112. The "cnt" parameter is usually chosen so that the product of "sz" and "cnt" is less than 1,000,000.
If the "buf" argument is not NULL, then it must point to a memory buffer with a size that is greater than or equal to the product of "sz" and "cnt". The buffer must be aligned to an 8-byte boundary. The lookaside memory configuration for a database connection can only be changed when that connection is not currently using lookaside memory, or in other words when the value returned by [SQLITE_DBSTATUS_LOOKASIDE_USED](#sqlitedbstatuslookasideused) is zero. Any attempt to change the lookaside memory configuration when lookaside memory is in use leaves the configuration unchanged and returns [SQLITE_BUSY](#SQLITE_ABORT). If the "buf" argument is NULL and an attempt to allocate memory based on "sz" and "cnt" fails, then lookaside is silently disabled.
The [SQLITE_CONFIG_LOOKASIDE](#sqliteconfiglookaside) configuration option can be used to set the default lookaside configuration at initialization. The [-DSQLITE_DEFAULT_LOOKASIDE](compile.md#default_lookaside) option can be used to set the default lookaside configuration at compile-time. Typical values for lookaside are 1200 for "sz" and 40 to 100 for "cnt".
SQLITE_DBCONFIG_ENABLE_FKEY
This option is used to enable or disable the enforcement of [foreign key constraints](foreignkeys.md). This is the same setting that is enabled or disabled by the [PRAGMA foreign_keys](pragma.md#pragma_foreign_keys) statement. The first argument is an integer which is 0 to disable FK enforcement, positive to enable FK enforcement or negative to leave FK enforcement unchanged. The second parameter is a pointer to an integer into which is written 0 or 1 to indicate whether FK enforcement is off or on following this call. The second parameter may be a NULL pointer, in which case the FK enforcement setting is not reported back.
SQLITE_DBCONFIG_ENABLE_TRIGGER
This option is used to enable or disable [triggers](lang_createtrigger.md). There should be two additional arguments. The first argument is an integer which is 0 to disable triggers, positive to enable triggers or negative to leave the setting unchanged. The second parameter is a pointer to an integer into which is written 0 or 1 to indicate whether triggers are disabled or enabled following this call. The second parameter may be a NULL pointer, in which case the trigger setting is not reported back.
Originally this option disabled all triggers. However, since SQLite version 3.35.0, TEMP triggers are still allowed even if this option is off. So, in other words, this option now only disables triggers in the main database schema or in the schemas of [ATTACH](lang_attach.md)-ed databases.
SQLITE_DBCONFIG_ENABLE_VIEW
This option is used to enable or disable [views](lang_createview.md). There must be two additional arguments. The first argument is an integer which is 0 to disable views, positive to enable views or negative to leave the setting unchanged. The second parameter is a pointer to an integer into which is written 0 or 1 to indicate whether views are disabled or enabled following this call. The second parameter may be a NULL pointer, in which case the view setting is not reported back.
Originally this option disabled all views. However, since SQLite version 3.35.0, TEMP views are still allowed even if this option is off. So, in other words, this option now only disables views in the main database schema or in the schemas of ATTACH-ed databases.
SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER
This option is used to enable or disable using the [fts3_tokenizer()](fts3.md#f3tknzr) function - part of the [FTS3](fts3.md) full-text search engine extension - without using bound parameters as the parameters. Doing so is disabled by default. There must be two additional arguments. The first argument is an integer. If it is passed 0, then using fts3_tokenizer() without bound parameters is disabled. If it is passed a positive value, then calling fts3_tokenizer without bound parameters is enabled. If it is passed a negative value, this setting is not modified - this can be used to query for the current setting. The second parameter is a pointer to an integer into which is written 0 or 1 to indicate the current value of this setting (after it is modified, if applicable). The second parameter may be a NULL pointer, in which case the value of the setting is not reported back. Refer to [FTS3](fts3.md) documentation for further details.
SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION
This option is used to enable or disable the [sqlite3_load_extension()](#sqlite3_load_extension) interface independently of the [load_extension()](lang_corefunc.md#load_extension) SQL function. The [sqlite3_enable_load_extension()](#sqlite3_enable_load_extension) API enables or disables both the C-API [sqlite3_load_extension()](#sqlite3_load_extension) and the SQL function [load_extension()](lang_corefunc.md#load_extension). There must be two additional arguments. When the first argument to this interface is 1, then only the C-API is enabled and the SQL function remains disabled. If the first argument to this interface is 0, then both the C-API and the SQL function are disabled. If the first argument is -1, then no changes are made to the state of either the C-API or the SQL function. The second parameter is a pointer to an integer into which is written 0 or 1 to indicate whether [sqlite3_load_extension()](#sqlite3_load_extension) interface is disabled or enabled following this call. The second parameter may be a NULL pointer, in which case the new setting is not reported back.
SQLITE_DBCONFIG_MAINDBNAME
This option is used to change the name of the "main" database schema. This option does not follow the [usual SQLITE_DBCONFIG argument format](#dbconfigarguments). This option takes exactly one additional argument so that the [sqlite3_db_config()](#sqlite3_db_config) call has a total of three parameters. The extra argument must be a pointer to a constant UTF8 string which will become the new schema name in place of "main". SQLite does not make a copy of the new main schema name string, so the application must ensure that the argument passed into SQLITE_DBCONFIG MAINDBNAME is unchanged until after the database connection closes.
SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE
Usually, when a database in [WAL mode](wal.md) is closed or detached from a database handle, SQLite checks if if there are other connections to the same database, and if there are no other database connection (if the connection being closed is the last open connection to the database), then SQLite performs a [checkpoint](wal.md#ckpt) before closing the connection and deletes the WAL file. The SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE option can be used to override that behavior. The first argument passed to this operation (the third parameter to [sqlite3_db_config()](#sqlite3_db_config)) is an integer which is positive to disable checkpoints-on-close, or zero (the default) to enable them, and negative to leave the setting unchanged. The second argument (the fourth parameter) is a pointer to an integer into which is written 0 or 1 to indicate whether checkpoints-on-close have been disabled - 0 if they are not disabled, 1 if they are.
SQLITE_DBCONFIG_ENABLE_QPSG
The SQLITE_DBCONFIG_ENABLE_QPSG option activates or deactivates the [query planner stability guarantee](queryplanner-ng.md#qpstab) (QPSG). When the QPSG is active, a single SQL query statement will always use the same algorithm regardless of values of [bound parameters](lang_expr.md#varparam). The QPSG disables some query optimizations that look at the values of bound parameters, which can make some queries slower. But the QPSG has the advantage of more predictable behavior. With the QPSG active, SQLite will always use the same query plan in the field as was used during testing in the lab. The first argument to this setting is an integer which is 0 to disable the QPSG, positive to enable QPSG, or negative to leave the setting unchanged. The second parameter is a pointer to an integer into which is written 0 or 1 to indicate whether the QPSG is disabled or enabled following this call.
SQLITE_DBCONFIG_TRIGGER_EQP
By default, the output of EXPLAIN QUERY PLAN commands does not include output for any operations performed by trigger programs. This option is used to set or clear (the default) a flag that governs this behavior. The first parameter passed to this operation is an integer - positive to enable output for trigger programs, or zero to disable it, or negative to leave the setting unchanged. The second parameter is a pointer to an integer into which is written 0 or 1 to indicate whether output-for-triggers has been disabled - 0 if it is not disabled, 1 if it is.
SQLITE_DBCONFIG_RESET_DATABASE
Set the SQLITE_DBCONFIG_RESET_DATABASE flag and then run [VACUUM](lang_vacuum.md) in order to reset a database back to an empty database with no schema and no content. The following process works even for a badly corrupted database file:
1. If the database connection is newly opened, make sure it has read the database schema by preparing then discarding some query against the database, or calling sqlite3_table_column_metadata(), ignoring any errors. This step is only necessary if the application desires to keep the database in WAL mode after the reset if it was in WAL mode before the reset.
2. sqlite3_db_config(db, SQLITE_DBCONFIG_RESET_DATABASE, 1, 0);
3. [sqlite3_exec](#sqlite3_exec)(db, "[VACUUM](lang_vacuum.md)", 0, 0, 0);
4. sqlite3_db_config(db, SQLITE_DBCONFIG_RESET_DATABASE, 0, 0);
Because resetting a database is destructive and irreversible, the process requires the use of this obscure API and multiple steps to help ensure that it does not happen by accident. Because this feature must be capable of resetting corrupt databases, and shutting down virtual tables may require access to that corrupt storage, the library must abandon any installed virtual tables without calling their xDestroy() methods.
SQLITE_DBCONFIG_DEFENSIVE
The SQLITE_DBCONFIG_DEFENSIVE option activates or deactivates the "defensive" flag for a database connection. When the defensive flag is enabled, language features that allow ordinary SQL to deliberately corrupt the database file are disabled. The disabled features include but are not limited to the following:
- The [PRAGMA writable_schema=ON](pragma.md#pragma_writable_schema) statement.
- The [PRAGMA journal_mode=OFF](pragma.md#pragma_journal_mode) statement.
- The [PRAGMA schema_version=N](pragma.md#pragma_schema_version) statement.
- Writes to the [sqlite_dbpage](dbpage.md) virtual table.
- Direct writes to [shadow tables](vtab.md#xshadowname).
SQLITE_DBCONFIG_WRITABLE_SCHEMA
The SQLITE_DBCONFIG_WRITABLE_SCHEMA option activates or deactivates the "writable_schema" flag. This has the same effect and is logically equivalent to setting [PRAGMA writable_schema=ON](pragma.md#pragma_writable_schema) or [PRAGMA writable_schema=OFF](pragma.md#pragma_writable_schema). The first argument to this setting is an integer which is 0 to disable the writable_schema, positive to enable writable_schema, or negative to leave the setting unchanged. The second parameter is a pointer to an integer into which is written 0 or 1 to indicate whether the writable_schema is enabled or disabled following this call.
SQLITE_DBCONFIG_LEGACY_ALTER_TABLE
The SQLITE_DBCONFIG_LEGACY_ALTER_TABLE option activates or deactivates the legacy behavior of the [ALTER TABLE RENAME](lang_altertable.md#altertabrename) command such that it behaves as it did prior to [version 3.24.0](releaselog/3_24_0.md) (2018-06-04). See the "Compatibility Notice" on the [ALTER TABLE RENAME documentation](lang_altertable.md#altertabrename) for additional information. This feature can also be turned on and off using the [PRAGMA legacy_alter_table](pragma.md#pragma_legacy_alter_table) statement.
SQLITE_DBCONFIG_DQS_DML
The SQLITE_DBCONFIG_DQS_DML option activates or deactivates the legacy [double-quoted string literal](quirks.md#dblquote) misfeature for DML statements only, that is DELETE, INSERT, SELECT, and UPDATE statements. The default value of this setting is determined by the [-DSQLITE_DQS](compile.md#dqs) compile-time option.
SQLITE_DBCONFIG_DQS_DDL
The SQLITE_DBCONFIG_DQS option activates or deactivates the legacy [double-quoted string literal](quirks.md#dblquote) misfeature for DDL statements, such as CREATE TABLE and CREATE INDEX. The default value of this setting is determined by the [-DSQLITE_DQS](compile.md#dqs) compile-time option.
SQLITE_DBCONFIG_TRUSTED_SCHEMA
The SQLITE_DBCONFIG_TRUSTED_SCHEMA option tells SQLite to assume that database schemas are untainted by malicious content. When the SQLITE_DBCONFIG_TRUSTED_SCHEMA option is disabled, SQLite takes additional defensive steps to protect the application from harm including:
- Prohibit the use of SQL functions inside triggers, views, CHECK constraints, DEFAULT clauses, expression indexes, partial indexes, or generated columns unless those functions are tagged with [SQLITE_INNOCUOUS](#sqliteinnocuous).
- Prohibit the use of virtual tables inside of triggers or views unless those virtual tables are tagged with [SQLITE_VTAB_INNOCUOUS](#sqlitevtabinnocuous).
This setting defaults to "on" for legacy compatibility, however all applications are advised to turn it off if possible. This setting can also be controlled using the [PRAGMA trusted_schema](pragma.md#pragma_trusted_schema) statement.
SQLITE_DBCONFIG_LEGACY_FILE_FORMAT
The SQLITE_DBCONFIG_LEGACY_FILE_FORMAT option activates or deactivates the legacy file format flag. When activated, this flag causes all newly created database files to have a schema format version number (the 4-byte integer found at offset 44 into the database header) of 1. This in turn means that the resulting database file will be readable and writable by any SQLite version back to 3.0.0 (2004-06-18). Without this setting, newly created databases are generally not understandable by SQLite versions prior to 3.3.0 (2006-01-11). As these words are written, there is now scarcely any need to generate database files that are compatible all the way back to version 3.0.0, and so this setting is of little practical use, but is provided so that SQLite can continue to claim the ability to generate new database files that are compatible with version 3.0.0.
Note that when the SQLITE_DBCONFIG_LEGACY_FILE_FORMAT setting is on, the [VACUUM](lang_vacuum.md) command will fail with an obscure error when attempting to process a table with generated columns and a descending index. This is not considered a bug since SQLite versions 3.3.0 and earlier do not support either generated columns or descending indexes.
SQLITE_DBCONFIG_STMT_SCANSTATUS
The SQLITE_DBCONFIG_STMT_SCANSTATUS option is only useful in [SQLITE_ENABLE_STMT_SCANSTATUS](compile.md#enable_stmt_scanstatus) builds. In this case, it sets or clears a flag that enables collection of run-time performance statistics used by [sqlite3_stmt_scanstatus_v2()](#sqlite3_stmt_scanstatus) and the [nexec and ncycle](bytecodevtab.md#nexec) columns of the [bytecode virtual table](bytecodevtab.md). For statistics to be collected, the flag must be set on the database handle both when the SQL statement is [prepared](#sqlite3_prepare) and when it is [stepped](#sqlite3_step). The flag is set (collection of statistics is enabled) by default.
This option takes two arguments: an integer and a pointer to an integer. The first argument is 1, 0, or -1 to enable, disable, or leave unchanged the statement scanstatus option. If the second argument is not NULL, then the value of the statement scanstatus setting after processing the first argument is written into the integer that the second argument points to.
SQLITE_DBCONFIG_REVERSE_SCANORDER
The SQLITE_DBCONFIG_REVERSE_SCANORDER option changes the default order in which tables and indexes are scanned so that the scans start at the end and work toward the beginning rather than starting at the beginning and working toward the end. Setting SQLITE_DBCONFIG_REVERSE_SCANORDER is the same as setting [PRAGMA reverse_unordered_selects](pragma.md#pragma_reverse_unordered_selects).
This option takes two arguments which are an integer and a pointer to an integer. The first argument is 1, 0, or -1 to enable, disable, or leave unchanged the reverse scan order flag, respectively. If the second argument is not NULL, then 0 or 1 is written into the integer that the second argument points to depending on if the reverse scan order flag is set after processing the first argument.
SQLITE_DBCONFIG_ENABLE_ATTACH_CREATE
The SQLITE_DBCONFIG_ENABLE_ATTACH_CREATE option enables or disables the ability of the [ATTACH DATABASE](lang_attach.md) SQL command to create a new database file if the database filed named in the ATTACH command does not already exist. This ability of ATTACH to create a new database is enabled by default. Applications can disable or reenable the ability for ATTACH to create new database files using this DBCONFIG option.
This option takes two arguments which are an integer and a pointer to an integer. The first argument is 1, 0, or -1 to enable, disable, or leave unchanged the attach-create flag, respectively. If the second argument is not NULL, then 0 or 1 is written into the integer that the second argument points to depending on if the attach-create flag is set after processing the first argument.
SQLITE_DBCONFIG_ENABLE_ATTACH_WRITE
The SQLITE_DBCONFIG_ENABLE_ATTACH_WRITE option enables or disables the ability of the [ATTACH DATABASE](lang_attach.md) SQL command to open a database for writing. This capability is enabled by default. Applications can disable or reenable this capability using the current DBCONFIG option. If this capability is disabled, the [ATTACH](lang_attach.md) command will still work, but the database will be opened read-only. If this option is disabled, then the ability to create a new database using [ATTACH](lang_attach.md) is also disabled, regardless of the value of the [SQLITE_DBCONFIG_ENABLE_ATTACH_CREATE](#sqlitedbconfigenableattachcreate) option.
This option takes two arguments which are an integer and a pointer to an integer. The first argument is 1, 0, or -1 to enable, disable, or leave unchanged the ability to ATTACH another database for writing, respectively. If the second argument is not NULL, then 0 or 1 is written into the integer to which the second argument points, depending on whether the ability to ATTACH a read/write database is enabled or disabled after processing the first argument.
SQLITE_DBCONFIG_ENABLE_COMMENTS
The SQLITE_DBCONFIG_ENABLE_COMMENTS option enables or disables the ability to include comments in SQL text. Comments are enabled by default. An application can disable or reenable comments in SQL text using this DBCONFIG option.
This option takes two arguments which are an integer and a pointer to an integer. The first argument is 1, 0, or -1 to enable, disable, or leave unchanged the ability to use comments in SQL text, respectively. If the second argument is not NULL, then 0 or 1 is written into the integer that the second argument points to depending on if comments are allowed in SQL text after processing the first argument.
SQLITE_DBCONFIG_FP_DIGITS
The SQLITE_DBCONFIG_FP_DIGITS setting is a small integer that determines the number of significant digits that SQLite will attempt to preserve when converting floating point numbers (IEEE 754 "doubles") into text. The default value 17, as of SQLite version 3.52.0. The value was 15 in all prior versions.
This option takes two arguments which are an integer and a pointer to an integer. The first argument is a small integer, between 3 and 23, or zero. The FP_DIGITS setting is changed to that small integer, or left unaltered if the first argument is zero or out of range. The second argument is a pointer to an integer. If the pointer is not NULL, then the value of the FP_DIGITS setting, after possibly being modified by the first arguments, is written into the integer to which the second argument points.
### Arguments To SQLITE_DBCONFIG Options
Most of the SQLITE_DBCONFIG options take two arguments, so that the overall call to [sqlite3_db_config()](#sqlite3_db_config) has a total of four parameters. The first argument (the third parameter to sqlite3_db_config()) is an integer. The second argument is a pointer to an integer. If the first argument is 1, then the option becomes enabled. If the first integer argument is 0, then the option is disabled. If the first argument is -1, then the option setting is unchanged. The second argument, the pointer to an integer, may be NULL. If the second argument is not NULL, then a value of 0 or 1 is written into the integer to which the second argument points, depending on whether the setting is disabled or enabled after applying any changes specified by the first argument.
While most SQLITE_DBCONFIG options use the argument format described in the previous paragraph, the [SQLITE_DBCONFIG_MAINDBNAME](#sqlitedbconfigmaindbname), [SQLITE_DBCONFIG_LOOKASIDE](#sqlitedbconfiglookaside), and [SQLITE_DBCONFIG_FP_DIGITS](#sqlitedbconfigfpdigits) options are different. See the documentation of those exceptional options for details.
------------------------------------------------------------------------
## Authorizer Return Codes
> \
> \#define SQLITE_DENY 1 /\* Abort the SQL statement with an error \*/\
> \#define SQLITE_IGNORE 2 /\* Don't allow access, but don't generate an error \*/\
The [authorizer callback function](#sqlite3_set_authorizer) must return either [SQLITE_OK](#SQLITE_ABORT) or one of these two constants in order to signal SQLite whether or not the action is permitted. See the [authorizer documentation](#sqlite3_set_authorizer) for additional information.
Note that SQLITE_IGNORE is also used as a [conflict resolution mode](#SQLITE_FAIL) returned from the [sqlite3_vtab_on_conflict()](#sqlite3_vtab_on_conflict) interface.
------------------------------------------------------------------------
## Flags for sqlite3_deserialize()
> \
> \#define SQLITE_DESERIALIZE_FREEONCLOSE 1 /\* Call sqlite3_free() on close \*/\
> \#define SQLITE_DESERIALIZE_RESIZEABLE 2 /\* Resize using sqlite3_realloc64() \*/\
> \#define SQLITE_DESERIALIZE_READONLY 4 /\* Database is read-only \*/\
The following are allowed values for the 6th argument (the F argument) to the [sqlite3_deserialize(D,S,P,N,M,F)](#sqlite3_deserialize) interface.
The SQLITE_DESERIALIZE_FREEONCLOSE means that the database serialization in the P argument is held in memory obtained from [sqlite3_malloc64()](#sqlite3_free) and that SQLite should take ownership of this memory and automatically free it when it has finished using it. Without this flag, the caller is responsible for freeing any dynamically allocated memory.
The SQLITE_DESERIALIZE_RESIZEABLE flag means that SQLite is allowed to grow the size of the database using calls to [sqlite3_realloc64()](#sqlite3_free). This flag should only be used if SQLITE_DESERIALIZE_FREEONCLOSE is also used. Without this flag, the deserialized database cannot increase in size beyond the number of bytes specified by the M parameter.
The SQLITE_DESERIALIZE_READONLY flag means that the deserialized database should be treated as read-only.
------------------------------------------------------------------------
## Function Flags
> \
> \#define SQLITE_DETERMINISTIC 0x000000800\
> \#define SQLITE_DIRECTONLY 0x000080000\
> \#define SQLITE_SUBTYPE 0x000100000\
> \#define SQLITE_INNOCUOUS 0x000200000\
> \#define SQLITE_RESULT_SUBTYPE 0x001000000\
> \#define SQLITE_SELFORDER1 0x002000000\
These constants may be ORed together with the [preferred text encoding](#sqliteutf8) as the fourth argument to [sqlite3_create_function()](#sqlite3_create_function), [sqlite3_create_function16()](#sqlite3_create_function), or [sqlite3_create_function_v2()](#sqlite3_create_function).
SQLITE_DETERMINISTIC
The SQLITE_DETERMINISTIC flag means that the new function always gives the same output when the input parameters are the same. The [abs() function](lang_corefunc.md#abs) is deterministic, for example, but [randomblob()](lang_corefunc.md#randomblob) is not. Functions must be deterministic in order to be used in certain contexts such as with the WHERE clause of [partial indexes](partialindex.md) or in [generated columns](gencol.md). SQLite might also optimize deterministic functions by factoring them out of inner loops.
SQLITE_DIRECTONLY
The SQLITE_DIRECTONLY flag means that the function may only be invoked from top-level SQL, and cannot be used in VIEWs or TRIGGERs nor in schema structures such as [CHECK constraints](lang_createtable.md#ckconst), [DEFAULT clauses](lang_createtable.md#dfltval), [expression indexes](expridx.md), [partial indexes](partialindex.md), or [generated columns](gencol.md).
The SQLITE_DIRECTONLY flag is recommended for any [application-defined SQL function](appfunc.md) that has side-effects or that could potentially leak sensitive information. This will prevent attacks in which an application is tricked into using a database file that has had its schema surreptitiously modified to invoke the application-defined function in ways that are harmful.
Some people say it is good practice to set SQLITE_DIRECTONLY on all [application-defined SQL functions](appfunc.md), regardless of whether or not they are security sensitive, as doing so prevents those functions from being used inside of the database schema, and thus ensures that the database can be inspected and modified using generic tools (such as the [CLI](cli.md)) that do not have access to the application-defined functions.
SQLITE_INNOCUOUS
The SQLITE_INNOCUOUS flag means that the function is unlikely to cause problems even if misused. An innocuous function should have no side effects and should not depend on any values other than its input parameters. The [abs() function](lang_corefunc.md#abs) is an example of an innocuous function. The [load_extension() SQL function](lang_corefunc.md#load_extension) is not innocuous because of its side effects.
SQLITE_INNOCUOUS is similar to SQLITE_DETERMINISTIC, but is not exactly the same. The [random() function](lang_corefunc.md#random) is an example of a function that is innocuous but not deterministic.
Some heightened security settings ([SQLITE_DBCONFIG_TRUSTED_SCHEMA](#sqlitedbconfigtrustedschema) and [PRAGMA trusted_schema=OFF](pragma.md#pragma_trusted_schema)) disable the use of SQL functions inside views and triggers and in schema structures such as [CHECK constraints](lang_createtable.md#ckconst), [DEFAULT clauses](lang_createtable.md#dfltval), [expression indexes](expridx.md), [partial indexes](partialindex.md), and [generated columns](gencol.md) unless the function is tagged with SQLITE_INNOCUOUS. Most built-in functions are innocuous. Developers are advised to avoid using the SQLITE_INNOCUOUS flag for application-defined functions unless the function has been carefully audited and found to be free of potentially security-adverse side-effects and information-leaks.
SQLITE_SUBTYPE
The SQLITE_SUBTYPE flag indicates to SQLite that a function might call [sqlite3_value_subtype()](#sqlite3_value_subtype) to inspect the sub-types of its arguments. This flag instructs SQLite to omit some corner-case optimizations that might disrupt the operation of the [sqlite3_value_subtype()](#sqlite3_value_subtype) function, causing it to return zero rather than the correct subtype(). All SQL functions that invoke [sqlite3_value_subtype()](#sqlite3_value_subtype) should have this property. If the SQLITE_SUBTYPE property is omitted, then the return value from [sqlite3_value_subtype()](#sqlite3_value_subtype) might sometimes be zero even though a non-zero subtype was specified by the function argument expression.
SQLITE_RESULT_SUBTYPE
The SQLITE_RESULT_SUBTYPE flag indicates to SQLite that a function might call [sqlite3_result_subtype()](#sqlite3_result_subtype) to cause a sub-type to be associated with its result. Every function that invokes [sqlite3_result_subtype()](#sqlite3_result_subtype) should have this property. If it does not, then the call to [sqlite3_result_subtype()](#sqlite3_result_subtype) might become a no-op if the function is used as a term in an [expression index](expridx.md). On the other hand, SQL functions that never invoke [sqlite3_result_subtype()](#sqlite3_result_subtype) should avoid setting this property, as the purpose of this property is to disable certain optimizations that are incompatible with subtypes.
SQLITE_SELFORDER1
The SQLITE_SELFORDER1 flag indicates that the function is an aggregate that internally orders the values provided to the first argument. The ordered-set aggregate SQL notation with a single ORDER BY term can be used to invoke this function. If the ordered-set aggregate notation is used on a function that lacks this flag, then an error is raised. Note that the ordered-set aggregate syntax is only available if SQLite is built using the -DSQLITE_ENABLE_ORDERED_SET_AGGREGATES compile-time option.
------------------------------------------------------------------------
## Conflict resolution modes
> \
> \#define SQLITE_ROLLBACK 1\
> /\* #define SQLITE_IGNORE 2 // Also used by sqlite3_authorizer() callback \*/\
> \#define SQLITE_FAIL 3\
> /\* #define SQLITE_ABORT 4 // Also an error code \*/\
> \#define SQLITE_REPLACE 5\
These constants are returned by [sqlite3_vtab_on_conflict()](#sqlite3_vtab_on_conflict) to inform a [virtual table](vtab.md) implementation of the [ON CONFLICT](lang_conflict.md) mode for the SQL statement being evaluated.
Note that the [SQLITE_IGNORE](#SQLITE_DENY) constant is also used as a potential return value from the [sqlite3_set_authorizer()](#sqlite3_set_authorizer) callback and that [SQLITE_ABORT](#SQLITE_ABORT) is also a [result code](rescode.md).
------------------------------------------------------------------------
## Standard File Control Opcodes
> \
> \#define SQLITE_FCNTL_LOCKSTATE 1\
> \#define SQLITE_FCNTL_GET_LOCKPROXYFILE 2\
> \#define SQLITE_FCNTL_SET_LOCKPROXYFILE 3\
> \#define SQLITE_FCNTL_LAST_ERRNO 4\
> \#define SQLITE_FCNTL_SIZE_HINT 5\
> \#define SQLITE_FCNTL_CHUNK_SIZE 6\
> \#define SQLITE_FCNTL_FILE_POINTER 7\
> \#define SQLITE_FCNTL_SYNC_OMITTED 8\
> \#define SQLITE_FCNTL_WIN32_AV_RETRY 9\
> \#define SQLITE_FCNTL_PERSIST_WAL 10\
> \#define SQLITE_FCNTL_OVERWRITE 11\
> \#define SQLITE_FCNTL_VFSNAME 12\
> \#define SQLITE_FCNTL_POWERSAFE_OVERWRITE 13\
> \#define SQLITE_FCNTL_PRAGMA 14\
> \#define SQLITE_FCNTL_BUSYHANDLER 15\
> \#define SQLITE_FCNTL_TEMPFILENAME 16\
> \#define SQLITE_FCNTL_MMAP_SIZE 18\
> \#define SQLITE_FCNTL_TRACE 19\
> \#define SQLITE_FCNTL_HAS_MOVED 20\
> \#define SQLITE_FCNTL_SYNC 21\
> \#define SQLITE_FCNTL_COMMIT_PHASETWO 22\
> \#define SQLITE_FCNTL_WIN32_SET_HANDLE 23\
> \#define SQLITE_FCNTL_WAL_BLOCK 24\
> \#define SQLITE_FCNTL_ZIPVFS 25\
> \#define SQLITE_FCNTL_RBU 26\
> \#define SQLITE_FCNTL_VFS_POINTER 27\
> \#define SQLITE_FCNTL_JOURNAL_POINTER 28\
> \#define SQLITE_FCNTL_WIN32_GET_HANDLE 29\
> \#define SQLITE_FCNTL_PDB 30\
> \#define SQLITE_FCNTL_BEGIN_ATOMIC_WRITE 31\
> \#define SQLITE_FCNTL_COMMIT_ATOMIC_WRITE 32\
> \#define SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE 33\
> \#define SQLITE_FCNTL_LOCK_TIMEOUT 34\
> \#define SQLITE_FCNTL_DATA_VERSION 35\
> \#define SQLITE_FCNTL_SIZE_LIMIT 36\
> \#define SQLITE_FCNTL_CKPT_DONE 37\
> \#define SQLITE_FCNTL_RESERVE_BYTES 38\
> \#define SQLITE_FCNTL_CKPT_START 39\
> \#define SQLITE_FCNTL_EXTERNAL_READER 40\
> \#define SQLITE_FCNTL_CKSM_FILE 41\
> \#define SQLITE_FCNTL_RESET_CACHE 42\
> \#define SQLITE_FCNTL_NULL_IO 43\
> \#define SQLITE_FCNTL_BLOCK_ON_CONNECT 44\
> \#define SQLITE_FCNTL_FILESTAT 45\
These integer constants are opcodes for the xFileControl method of the [sqlite3_io_methods](#sqlite3_io_methods) object and for the [sqlite3_file_control()](#sqlite3_file_control) interface.
- The [SQLITE_FCNTL_LOCKSTATE](#sqlitefcntllockstate) opcode is used for debugging. This opcode causes the xFileControl method to write the current state of the lock (one of [SQLITE_LOCK_NONE](#SQLITE_LOCK_EXCLUSIVE), [SQLITE_LOCK_SHARED](#SQLITE_LOCK_EXCLUSIVE), [SQLITE_LOCK_RESERVED](#SQLITE_LOCK_EXCLUSIVE), [SQLITE_LOCK_PENDING](#SQLITE_LOCK_EXCLUSIVE), or [SQLITE_LOCK_EXCLUSIVE](#SQLITE_LOCK_EXCLUSIVE)) into an integer that the pArg argument points to. This capability is only available if SQLite is compiled with [SQLITE_DEBUG](compile.md#debug).
- The [SQLITE_FCNTL_SIZE_HINT](#sqlitefcntlsizehint) opcode is used by SQLite to give the VFS layer a hint of how large the database file will grow to be during the current transaction. This hint is not guaranteed to be accurate but it is often close. The underlying VFS might choose to preallocate database file space based on this hint in order to help writes to the database file run faster.
- The [SQLITE_FCNTL_SIZE_LIMIT](#sqlitefcntlsizelimit) opcode is used by in-memory VFS that implements [sqlite3_deserialize()](#sqlite3_deserialize) to set an upper bound on the size of the in-memory database. The argument is a pointer to a [sqlite3_int64](#sqlite3_int64). If the integer pointed to is negative, then it is filled in with the current limit. Otherwise the limit is set to the larger of the value of the integer pointed to and the current database size. The integer pointed to is set to the new limit.
- The [SQLITE_FCNTL_CHUNK_SIZE](#sqlitefcntlchunksize) opcode is used to request that the VFS extends and truncates the database file in chunks of a size specified by the user. The fourth argument to [sqlite3_file_control()](#sqlite3_file_control) should point to an integer (type int) containing the new chunk-size to use for the nominated database. Allocating database file space in large chunks (say 1MB at a time), may reduce file-system fragmentation and improve performance on some systems.
- The [SQLITE_FCNTL_FILE_POINTER](#sqlitefcntlfilepointer) opcode is used to obtain a pointer to the [sqlite3_file](#sqlite3_file) object associated with a particular database connection. See also [SQLITE_FCNTL_JOURNAL_POINTER](#sqlitefcntljournalpointer).
- The [SQLITE_FCNTL_JOURNAL_POINTER](#sqlitefcntljournalpointer) opcode is used to obtain a pointer to the [sqlite3_file](#sqlite3_file) object associated with the journal file (either the [rollback journal](lockingv3.md#rollback) or the [write-ahead log](wal.md)) for a particular database connection. See also [SQLITE_FCNTL_FILE_POINTER](#sqlitefcntlfilepointer).
- The SQLITE_FCNTL_SYNC_OMITTED file-control is no longer used.
- The [SQLITE_FCNTL_SYNC](#sqlitefcntlsync) opcode is generated internally by SQLite and sent to the VFS immediately before the xSync method is invoked on a database file descriptor. Or, if the xSync method is not invoked because the user has configured SQLite with [PRAGMA synchronous=OFF](pragma.md#pragma_synchronous) it is invoked in place of the xSync method. In most cases, the pointer argument passed with this file-control is NULL. However, if the database file is being synced as part of a multi-database commit, the argument points to a nul-terminated string containing the transactions super-journal file name. VFSes that do not need this signal should silently ignore this opcode. Applications should not call [sqlite3_file_control()](#sqlite3_file_control) with this opcode as doing so may disrupt the operation of the specialized VFSes that do require it.
- The [SQLITE_FCNTL_COMMIT_PHASETWO](#sqlitefcntlcommitphasetwo) opcode is generated internally by SQLite and sent to the VFS after a transaction has been committed immediately but before the database is unlocked. VFSes that do not need this signal should silently ignore this opcode. Applications should not call [sqlite3_file_control()](#sqlite3_file_control) with this opcode as doing so may disrupt the operation of the specialized VFSes that do require it.
- The [SQLITE_FCNTL_WIN32_AV_RETRY](#sqlitefcntlwin32avretry) opcode is used to configure automatic retry counts and intervals for certain disk I/O operations for the windows [VFS](vfs.md) in order to provide robustness in the presence of anti-virus programs. By default, the windows VFS will retry file read, file write, and file delete operations up to 10 times, with a delay of 25 milliseconds before the first retry and with the delay increasing by an additional 25 milliseconds with each subsequent retry. This opcode allows these two values (10 retries and 25 milliseconds of delay) to be adjusted. The values are changed for all database connections within the same process. The argument is a pointer to an array of two integers where the first integer is the new retry count and the second integer is the delay. If either integer is negative, then the setting is not changed but instead the prior value of that setting is written into the array entry, allowing the current retry settings to be interrogated. The zDbName parameter is ignored.
- The [SQLITE_FCNTL_PERSIST_WAL](#sqlitefcntlpersistwal) opcode is used to set or query the persistent [Write Ahead Log](wal.md) setting. By default, the auxiliary write ahead log ([WAL file](wal.md#walfile)) and shared memory files used for transaction control are automatically deleted when the latest connection to the database closes. Setting persistent WAL mode causes those files to persist after close. Persisting the files is useful when other processes that do not have write permission on the directory containing the database file want to read the database file, as the WAL and shared memory files must exist in order for the database to be readable. The fourth parameter to [sqlite3_file_control()](#sqlite3_file_control) for this opcode should be a pointer to an integer. That integer is 0 to disable persistent WAL mode or 1 to enable persistent WAL mode. If the integer is -1, then it is overwritten with the current WAL persistence setting.
- The [SQLITE_FCNTL_POWERSAFE_OVERWRITE](#sqlitefcntlpowersafeoverwrite) opcode is used to set or query the persistent "powersafe-overwrite" or "PSOW" setting. The PSOW setting determines the [SQLITE_IOCAP_POWERSAFE_OVERWRITE](#SQLITE_IOCAP_ATOMIC) bit of the xDeviceCharacteristics methods. The fourth parameter to [sqlite3_file_control()](#sqlite3_file_control) for this opcode should be a pointer to an integer. That integer is 0 to disable zero-damage mode or 1 to enable zero-damage mode. If the integer is -1, then it is overwritten with the current zero-damage mode setting.
- The [SQLITE_FCNTL_OVERWRITE](#sqlitefcntloverwrite) opcode is invoked by SQLite after opening a write transaction to indicate that, unless it is rolled back for some reason, the entire database file will be overwritten by the current transaction. This is used by VACUUM operations.
- The [SQLITE_FCNTL_VFSNAME](#sqlitefcntlvfsname) opcode can be used to obtain the names of all [VFSes](vfs.md) in the VFS stack. The names of all VFS shims and the final bottom-level VFS are written into memory obtained from [sqlite3_malloc()](#sqlite3_free) and the result is stored in the char\* variable that the fourth parameter of [sqlite3_file_control()](#sqlite3_file_control) points to. The caller is responsible for freeing the memory when done. As with all file-control actions, there is no guarantee that this will actually do anything. Callers should initialize the char\* variable to a NULL pointer in case this file-control is not implemented. This file-control is intended for diagnostic use only.
- The [SQLITE_FCNTL_VFS_POINTER](#sqlitefcntlvfspointer) opcode finds a pointer to the top-level [VFSes](vfs.md) currently in use. The argument X in sqlite3_file_control(db,SQLITE_FCNTL_VFS_POINTER,X) must be of type "[sqlite3_vfs](#sqlite3_vfs) \*\*". This opcode will set \*X to a pointer to the top-level VFS. When there are multiple VFS shims in the stack, this opcode finds the upper-most shim only.
- Whenever a [PRAGMA](pragma.md#syntax) statement is parsed, an [SQLITE_FCNTL_PRAGMA](#sqlitefcntlpragma) file control is sent to the open [sqlite3_file](#sqlite3_file) object corresponding to the database file to which the pragma statement refers. The argument to the [SQLITE_FCNTL_PRAGMA](#sqlitefcntlpragma) file control is an array of pointers to strings (char\*\*) in which the second element of the array is the name of the pragma and the third element is the argument to the pragma or NULL if the pragma has no argument. The handler for an [SQLITE_FCNTL_PRAGMA](#sqlitefcntlpragma) file control can optionally make the first element of the char\*\* argument point to a string obtained from [sqlite3_mprintf()](#sqlite3_mprintf) or the equivalent and that string will become the result of the pragma or the error message if the pragma fails. If the [SQLITE_FCNTL_PRAGMA](#sqlitefcntlpragma) file control returns [SQLITE_NOTFOUND](#SQLITE_ABORT), then normal [PRAGMA](pragma.md#syntax) processing continues. If the [SQLITE_FCNTL_PRAGMA](#sqlitefcntlpragma) file control returns [SQLITE_OK](#SQLITE_ABORT), then the parser assumes that the VFS has handled the PRAGMA itself and the parser generates a no-op prepared statement if result string is NULL, or that returns a copy of the result string if the string is non-NULL. If the [SQLITE_FCNTL_PRAGMA](#sqlitefcntlpragma) file control returns any result code other than [SQLITE_OK](#SQLITE_ABORT) or [SQLITE_NOTFOUND](#SQLITE_ABORT), that means that the VFS encountered an error while handling the [PRAGMA](pragma.md#syntax) and the compilation of the PRAGMA fails with an error. The [SQLITE_FCNTL_PRAGMA](#sqlitefcntlpragma) file control occurs at the beginning of pragma statement analysis and so it is able to override built-in [PRAGMA](pragma.md#syntax) statements.
- The [SQLITE_FCNTL_BUSYHANDLER](#sqlitefcntlbusyhandler) file-control may be invoked by SQLite on the database file handle shortly after it is opened in order to provide a custom VFS with access to the connection's busy-handler callback. The argument is of type (void\*\*) - an array of two (void \*) values. The first (void \*) actually points to a function of type (int (\*)(void \*)). In order to invoke the connection's busy-handler, this function should be invoked with the second (void \*) in the array as the only argument. If it returns non-zero, then the operation should be retried. If it returns zero, the custom VFS should abandon the current operation.
- Applications can invoke the [SQLITE_FCNTL_TEMPFILENAME](#sqlitefcntltempfilename) file-control to have SQLite generate a temporary filename using the same algorithm that is followed to generate temporary filenames for TEMP tables and other internal uses. The argument should be a char\*\* which will be filled with the filename written into memory obtained from [sqlite3_malloc()](#sqlite3_free). The caller should invoke [sqlite3_free()](#sqlite3_free) on the result to avoid a memory leak.
- The [SQLITE_FCNTL_MMAP_SIZE](#sqlitefcntlmmapsize) file control is used to query or set the maximum number of bytes that will be used for memory-mapped I/O. The argument is a pointer to a value of type sqlite3_int64 that is an advisory maximum number of bytes in the file to memory map. The pointer is overwritten with the old value. The limit is not changed if the value originally pointed to is negative, and so the current limit can be queried by passing in a pointer to a negative number. This file-control is used internally to implement [PRAGMA mmap_size](pragma.md#pragma_mmap_size).
- The [SQLITE_FCNTL_TRACE](#sqlitefcntltrace) file control provides advisory information to the VFS about what the higher layers of the SQLite stack are doing. This file control is used by some VFS activity tracing [shims](vfs.md#shim). The argument is a zero-terminated string. Higher layers in the SQLite stack may generate instances of this file control if the [SQLITE_USE_FCNTL_TRACE](compile.md#use_fcntl_trace) compile-time option is enabled.
- The [SQLITE_FCNTL_HAS_MOVED](#sqlitefcntlhasmoved) file control interprets its argument as a pointer to an integer and it writes a boolean into that integer depending on whether or not the file has been renamed, moved, or deleted since it was first opened.
- The [SQLITE_FCNTL_WIN32_GET_HANDLE](#sqlitefcntlwin32gethandle) opcode can be used to obtain the underlying native file handle associated with a file handle. This file control interprets its argument as a pointer to a native file handle and writes the resulting value there.
- The [SQLITE_FCNTL_WIN32_SET_HANDLE](#sqlitefcntlwin32sethandle) opcode is used for debugging. This opcode causes the xFileControl method to swap the file handle with the one pointed to by the pArg argument. This capability is used during testing and only needs to be supported when SQLITE_TEST is defined.
- The [SQLITE_FCNTL_NULL_IO](#sqlitefcntlnullio) opcode sets the low-level file descriptor or file handle for the [sqlite3_file](#sqlite3_file) object such that it will no longer read or write to the database file.
- The [SQLITE_FCNTL_WAL_BLOCK](#sqlitefcntlwalblock) is a signal to the VFS layer that it might be advantageous to block on the next WAL lock if the lock is not immediately available. The WAL subsystem issues this signal during rare circumstances in order to fix a problem with priority inversion. Applications should *not* use this file-control.
- The [SQLITE_FCNTL_ZIPVFS](#sqlitefcntlzipvfs) opcode is implemented by zipvfs only. All other VFS should return SQLITE_NOTFOUND for this opcode.
- The [SQLITE_FCNTL_RBU](#sqlitefcntlrbu) opcode is implemented by the special VFS used by the RBU extension only. All other VFS should return SQLITE_NOTFOUND for this opcode.
- If the [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE](#sqlitefcntlbeginatomicwrite) opcode returns SQLITE_OK, then the file descriptor is placed in "batch write mode", which means all subsequent write operations will be deferred and done atomically at the next [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE](#sqlitefcntlcommitatomicwrite). Systems that do not support batch atomic writes will return SQLITE_NOTFOUND. Following a successful SQLITE_FCNTL_BEGIN_ATOMIC_WRITE and prior to the closing [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE](#sqlitefcntlcommitatomicwrite) or [SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE](#sqlitefcntlrollbackatomicwrite), SQLite will make no VFS interface calls on the same [sqlite3_file](#sqlite3_file) file descriptor except for calls to the xWrite method and the xFileControl method with [SQLITE_FCNTL_SIZE_HINT](#sqlitefcntlsizehint).
- The [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE](#sqlitefcntlcommitatomicwrite) opcode causes all write operations since the previous successful call to [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE](#sqlitefcntlbeginatomicwrite) to be performed atomically. This file control returns [SQLITE_OK](#SQLITE_ABORT) if and only if the writes were all performed successfully and have been committed to persistent storage. Regardless of whether or not it is successful, this file control takes the file descriptor out of batch write mode so that all subsequent write operations are independent. SQLite will never invoke SQLITE_FCNTL_COMMIT_ATOMIC_WRITE without a prior successful call to [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE](#sqlitefcntlbeginatomicwrite).
- The [SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE](#sqlitefcntlrollbackatomicwrite) opcode causes all write operations since the previous successful call to [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE](#sqlitefcntlbeginatomicwrite) to be rolled back. This file control takes the file descriptor out of batch write mode so that all subsequent write operations are independent. SQLite will never invoke SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE without a prior successful call to [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE](#sqlitefcntlbeginatomicwrite).
- The [SQLITE_FCNTL_LOCK_TIMEOUT](#sqlitefcntllocktimeout) opcode is used to configure a VFS to block for up to M milliseconds before failing when attempting to obtain a file lock using the xLock or xShmLock methods of the VFS. The parameter is a pointer to a 32-bit signed integer that contains the value that M is to be set to. Before returning, the 32-bit signed integer is overwritten with the previous value of M.
- The [SQLITE_FCNTL_BLOCK_ON_CONNECT](#sqlitefcntlblockonconnect) opcode is used to configure the VFS to block when taking a SHARED lock to connect to a wal mode database. This is used to implement the functionality associated with SQLITE_SETLK_BLOCK_ON_CONNECT.
- The [SQLITE_FCNTL_DATA_VERSION](#sqlitefcntldataversion) opcode is used to detect changes to a database file. The argument is a pointer to a 32-bit unsigned integer. The "data version" for the pager is written into the pointer. The "data version" changes whenever any change occurs to the corresponding database file, either through SQL statements on the same database connection or through transactions committed by separate database connections possibly in other processes. The [sqlite3_total_changes()](#sqlite3_total_changes) interface can be used to find if any database on the connection has changed, but that interface responds to changes on TEMP as well as MAIN and does not provide a mechanism to detect changes to MAIN only. Also, the [sqlite3_total_changes()](#sqlite3_total_changes) interface responds to internal changes only and omits changes made by other database connections. The [PRAGMA data_version](pragma.md#pragma_data_version) command provides a mechanism to detect changes to a single attached database that occur due to other database connections, but omits changes implemented by the database connection on which it is called. This file control is the only mechanism to detect changes that happen either internally or externally and that are associated with a particular attached database.
- The [SQLITE_FCNTL_CKPT_START](#sqlitefcntlckptstart) opcode is invoked from within a checkpoint in wal mode before the client starts to copy pages from the wal file to the database file.
- The [SQLITE_FCNTL_CKPT_DONE](#sqlitefcntlckptdone) opcode is invoked from within a checkpoint in wal mode after the client has finished copying pages from the wal file to the database file, but before the \*-shm file is updated to record the fact that the pages have been checkpointed.
- The EXPERIMENTAL [SQLITE_FCNTL_EXTERNAL_READER](#sqlitefcntlexternalreader) opcode is used to detect whether or not there is a database client in another process with a wal-mode transaction open on the database or not. It is only available on unix. The (void\*) argument passed with this file-control should be a pointer to a value of type (int). The integer value is set to 1 if the database is a wal mode database and there exists at least one client in another process that currently has an SQL transaction open on the database. It is set to 0 if the database is not a wal-mode db, or if there is no such connection in any other process. This opcode cannot be used to detect transactions opened by clients within the current process, only within other processes.
- The [SQLITE_FCNTL_CKSM_FILE](#sqlitefcntlcksmfile) opcode is for use internally by the [checksum VFS shim](cksumvfs.md) only.
- If there is currently no transaction open on the database, and the database is not a temp db, then the [SQLITE_FCNTL_RESET_CACHE](#sqlitefcntlresetcache) file-control purges the contents of the in-memory page cache. If there is an open transaction, or if the db is a temp-db, this opcode is a no-op, not an error.
- The [SQLITE_FCNTL_FILESTAT](#sqlitefcntlfilestat) opcode returns low-level diagnostic information about the [sqlite3_file](#sqlite3_file) objects used access the database and journal files for the given schema. The fourth parameter to [sqlite3_file_control()](#sqlite3_file_control) should be an initialized [sqlite3_str](#sqlite3_str) pointer. JSON text describing various aspects of the sqlite3_file object is appended to the sqlite3_str. The SQLITE_FCNTL_FILESTAT opcode is usually a no-op, unless compile-time options are used to enable it.
------------------------------------------------------------------------
## Virtual Table Constraint Operator Codes
> \
> \#define SQLITE_INDEX_CONSTRAINT_EQ 2\
> \#define SQLITE_INDEX_CONSTRAINT_GT 4\
> \#define SQLITE_INDEX_CONSTRAINT_LE 8\
> \#define SQLITE_INDEX_CONSTRAINT_LT 16\
> \#define SQLITE_INDEX_CONSTRAINT_GE 32\
> \#define SQLITE_INDEX_CONSTRAINT_MATCH 64\
> \#define SQLITE_INDEX_CONSTRAINT_LIKE 65\
> \#define SQLITE_INDEX_CONSTRAINT_GLOB 66\
> \#define SQLITE_INDEX_CONSTRAINT_REGEXP 67\
> \#define SQLITE_INDEX_CONSTRAINT_NE 68\
> \#define SQLITE_INDEX_CONSTRAINT_ISNOT 69\
> \#define SQLITE_INDEX_CONSTRAINT_ISNOTNULL 70\
> \#define SQLITE_INDEX_CONSTRAINT_ISNULL 71\
> \#define SQLITE_INDEX_CONSTRAINT_IS 72\
> \#define SQLITE_INDEX_CONSTRAINT_LIMIT 73\
> \#define SQLITE_INDEX_CONSTRAINT_OFFSET 74\
> \#define SQLITE_INDEX_CONSTRAINT_FUNCTION 150\
These macros define the allowed values for the [sqlite3_index_info](#sqlite3_index_info).aConstraint\[\].op field. Each value represents an operator that is part of a constraint term in the WHERE clause of a query that uses a [virtual table](vtab.md).
The left-hand operand of the operator is given by the corresponding aConstraint\[\].iColumn field. An iColumn of -1 indicates the left-hand operand is the rowid. The SQLITE_INDEX_CONSTRAINT_LIMIT and SQLITE_INDEX_CONSTRAINT_OFFSET operators have no left-hand operand, and so for those operators the corresponding aConstraint\[\].iColumn is meaningless and should not be used.
All operator values from SQLITE_INDEX_CONSTRAINT_FUNCTION through value 255 are reserved to represent functions that are overloaded by the [xFindFunction method](vtab.md#xfindfunction) of the virtual table implementation.
The right-hand operands for each constraint might be accessible using the [sqlite3_vtab_rhs_value()](#sqlite3_vtab_rhs_value) interface. Usually the right-hand operand is only available if it appears as a single constant literal in the input SQL. If the right-hand operand is another column or an expression (even a constant expression) or a parameter, then the sqlite3_vtab_rhs_value() probably will not be able to extract it. The SQLITE_INDEX_CONSTRAINT_ISNULL and SQLITE_INDEX_CONSTRAINT_ISNOTNULL operators have no right-hand operand and hence calls to sqlite3_vtab_rhs_value() for those operators will always return SQLITE_NOTFOUND.
The collating sequence to be used for comparison can be found using the [sqlite3_vtab_collation()](#sqlite3_vtab_collation) interface. For most real-world virtual tables, the collating sequence of constraints does not matter (for example because the constraints are numeric) and so the sqlite3_vtab_collation() interface is not commonly needed.
------------------------------------------------------------------------
## Virtual Table Scan Flags
> \
> \#define SQLITE_INDEX_SCAN_UNIQUE 0x00000001 /\* Scan visits at most 1 row \*/\
> \#define SQLITE_INDEX_SCAN_HEX 0x00000002 /\* Display idxNum as hex \*/\
> /\* in EXPLAIN QUERY PLAN \*/\
Virtual table implementations are allowed to set the [sqlite3_index_info](#sqlite3_index_info).idxFlags field to some combination of these bits.
------------------------------------------------------------------------
## Device Characteristics
> \
> \#define SQLITE_IOCAP_ATOMIC 0x00000001\
> \#define SQLITE_IOCAP_ATOMIC512 0x00000002\
> \#define SQLITE_IOCAP_ATOMIC1K 0x00000004\
> \#define SQLITE_IOCAP_ATOMIC2K 0x00000008\
> \#define SQLITE_IOCAP_ATOMIC4K 0x00000010\
> \#define SQLITE_IOCAP_ATOMIC8K 0x00000020\
> \#define SQLITE_IOCAP_ATOMIC16K 0x00000040\
> \#define SQLITE_IOCAP_ATOMIC32K 0x00000080\
> \#define SQLITE_IOCAP_ATOMIC64K 0x00000100\
> \#define SQLITE_IOCAP_SAFE_APPEND 0x00000200\
> \#define SQLITE_IOCAP_SEQUENTIAL 0x00000400\
> \#define SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN 0x00000800\
> \#define SQLITE_IOCAP_POWERSAFE_OVERWRITE 0x00001000\
> \#define SQLITE_IOCAP_IMMUTABLE 0x00002000\
> \#define SQLITE_IOCAP_BATCH_ATOMIC 0x00004000\
> \#define SQLITE_IOCAP_SUBPAGE_READ 0x00008000\
The xDeviceCharacteristics method of the [sqlite3_io_methods](#sqlite3_io_methods) object returns an integer which is a vector of these bit values expressing I/O characteristics of the mass storage device that holds the file that the [sqlite3_io_methods](#sqlite3_io_methods) refers to.
The SQLITE_IOCAP_ATOMIC property means that all writes of any size are atomic. The SQLITE_IOCAP_ATOMICnnn values mean that writes of blocks that are nnn bytes in size and are aligned to an address which is an integer multiple of nnn are atomic. The SQLITE_IOCAP_SAFE_APPEND value means that when data is appended to a file, the data is appended first then the size of the file is extended, never the other way around. The SQLITE_IOCAP_SEQUENTIAL property means that information is written to disk in the same order as calls to xWrite(). The SQLITE_IOCAP_POWERSAFE_OVERWRITE property means that after reboot following a crash or power loss, the only bytes in a file that were written at the application level might have changed and that adjacent bytes, even bytes within the same sector are guaranteed to be unchanged. The SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN flag indicates that a file cannot be deleted when open. The SQLITE_IOCAP_IMMUTABLE flag indicates that the file is on read-only media and cannot be changed even by processes with elevated privileges.
The SQLITE_IOCAP_BATCH_ATOMIC property means that the underlying filesystem supports doing multiple write operations atomically when those write operations are bracketed by [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE](#sqlitefcntlbeginatomicwrite) and [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE](#sqlitefcntlcommitatomicwrite).
The SQLITE_IOCAP_SUBPAGE_READ property means that it is ok to read from the database file in amounts that are not a multiple of the page size and that do not begin at a page boundary. Without this property, SQLite is careful to only do full-page reads and write on aligned pages, with the one exception that it will do a sub-page read of the first page to access the database header.
------------------------------------------------------------------------
## File Locking Levels
> \
> \#define SQLITE_LOCK_NONE 0 /\* xUnlock() only \*/\
> \#define SQLITE_LOCK_SHARED 1 /\* xLock() or xUnlock() \*/\
> \#define SQLITE_LOCK_RESERVED 2 /\* xLock() only \*/\
> \#define SQLITE_LOCK_PENDING 3 /\* xLock() only \*/\
> \#define SQLITE_LOCK_EXCLUSIVE 4 /\* xLock() only \*/\
SQLite uses one of these integer values as the second argument to calls it makes to the xLock() and xUnlock() methods of an [sqlite3_io_methods](#sqlite3_io_methods) object. These values are ordered from least restrictive to most restrictive.
The argument to xLock() is always SHARED or higher. The argument to xUnlock is either SHARED or NONE.
------------------------------------------------------------------------
## Mutex Types
> \
> \#define SQLITE_MUTEX_FAST 0\
> \#define SQLITE_MUTEX_RECURSIVE 1\
> \#define SQLITE_MUTEX_STATIC_MAIN 2\
> \#define SQLITE_MUTEX_STATIC_MEM 3 /\* sqlite3_malloc() \*/\
> \#define SQLITE_MUTEX_STATIC_MEM2 4 /\* NOT USED \*/\
> \#define SQLITE_MUTEX_STATIC_OPEN 4 /\* sqlite3BtreeOpen() \*/\
> \#define SQLITE_MUTEX_STATIC_PRNG 5 /\* sqlite3_randomness() \*/\
> \#define SQLITE_MUTEX_STATIC_LRU 6 /\* lru page list \*/\
> \#define SQLITE_MUTEX_STATIC_LRU2 7 /\* NOT USED \*/\
> \#define SQLITE_MUTEX_STATIC_PMEM 7 /\* sqlite3PageMalloc() \*/\
> \#define SQLITE_MUTEX_STATIC_APP1 8 /\* For use by application \*/\
> \#define SQLITE_MUTEX_STATIC_APP2 9 /\* For use by application \*/\
> \#define SQLITE_MUTEX_STATIC_APP3 10 /\* For use by application \*/\
> \#define SQLITE_MUTEX_STATIC_VFS1 11 /\* For use by built-in VFS \*/\
> \#define SQLITE_MUTEX_STATIC_VFS2 12 /\* For use by extension VFS \*/\
> \#define SQLITE_MUTEX_STATIC_VFS3 13 /\* For use by application VFS \*/\
The [sqlite3_mutex_alloc()](#sqlite3_mutex_alloc) interface takes a single argument which is one of these integer constants.
The set of static mutexes may change from one SQLite release to the next. Applications that override the built-in mutex logic must be prepared to accommodate additional static mutexes.
------------------------------------------------------------------------
## Flags For File Open Operations
> \
> \#define SQLITE_OPEN_READONLY 0x00000001 /\* Ok for sqlite3_open_v2() \*/\
> \#define SQLITE_OPEN_READWRITE 0x00000002 /\* Ok for sqlite3_open_v2() \*/\
> \#define SQLITE_OPEN_CREATE 0x00000004 /\* Ok for sqlite3_open_v2() \*/\
> \#define SQLITE_OPEN_DELETEONCLOSE 0x00000008 /\* VFS only \*/\
> \#define SQLITE_OPEN_EXCLUSIVE 0x00000010 /\* VFS only \*/\
> \#define SQLITE_OPEN_AUTOPROXY 0x00000020 /\* VFS only \*/\
> \#define SQLITE_OPEN_URI 0x00000040 /\* Ok for sqlite3_open_v2() \*/\
> \#define SQLITE_OPEN_MEMORY 0x00000080 /\* Ok for sqlite3_open_v2() \*/\
> \#define SQLITE_OPEN_MAIN_DB 0x00000100 /\* VFS only \*/\
> \#define SQLITE_OPEN_TEMP_DB 0x00000200 /\* VFS only \*/\
> \#define SQLITE_OPEN_TRANSIENT_DB 0x00000400 /\* VFS only \*/\
> \#define SQLITE_OPEN_MAIN_JOURNAL 0x00000800 /\* VFS only \*/\
> \#define SQLITE_OPEN_TEMP_JOURNAL 0x00001000 /\* VFS only \*/\
> \#define SQLITE_OPEN_SUBJOURNAL 0x00002000 /\* VFS only \*/\
> \#define SQLITE_OPEN_SUPER_JOURNAL 0x00004000 /\* VFS only \*/\
> \#define SQLITE_OPEN_NOMUTEX 0x00008000 /\* Ok for sqlite3_open_v2() \*/\
> \#define SQLITE_OPEN_FULLMUTEX 0x00010000 /\* Ok for sqlite3_open_v2() \*/\
> \#define SQLITE_OPEN_SHAREDCACHE 0x00020000 /\* Ok for sqlite3_open_v2() \*/\
> \#define SQLITE_OPEN_PRIVATECACHE 0x00040000 /\* Ok for sqlite3_open_v2() \*/\
> \#define SQLITE_OPEN_WAL 0x00080000 /\* VFS only \*/\
> \#define SQLITE_OPEN_NOFOLLOW 0x01000000 /\* Ok for sqlite3_open_v2() \*/\
> \#define SQLITE_OPEN_EXRESCODE 0x02000000 /\* Extended result codes \*/\
These bit values are intended for use in the 3rd parameter to the [sqlite3_open_v2()](#sqlite3_open) interface and in the 4th parameter to the [sqlite3_vfs.xOpen](#sqlite3vfsxopen) method.
Only those flags marked as "Ok for sqlite3_open_v2()" may be used as the third argument to the [sqlite3_open_v2()](#sqlite3_open) interface. The other flags have historically been ignored by sqlite3_open_v2(), though future versions of SQLite might change so that an error is raised if any of the disallowed bits are passed into sqlite3_open_v2(). Applications should not depend on the historical behavior.
Note in particular that passing the SQLITE_OPEN_EXCLUSIVE flag into [sqlite3_open_v2()](#sqlite3_open) does \*not\* cause the underlying database file to be opened using O_EXCL. Passing SQLITE_OPEN_EXCLUSIVE into [sqlite3_open_v2()](#sqlite3_open) has historically been a no-op and might become an error in future versions of SQLite.
------------------------------------------------------------------------
## Prepare Flags
> \
> \#define SQLITE_PREPARE_PERSISTENT 0x01\
> \#define SQLITE_PREPARE_NORMALIZE 0x02\
> \#define SQLITE_PREPARE_NO_VTAB 0x04\
> \#define SQLITE_PREPARE_DONT_LOG 0x10\
> \#define SQLITE_PREPARE_FROM_DDL 0x20\
These constants define various flags that can be passed into the "prepFlags" parameter of the [sqlite3_prepare_v3()](#sqlite3_prepare) and [sqlite3_prepare16_v3()](#sqlite3_prepare) interfaces.
New flags may be added in future releases of SQLite.
SQLITE_PREPARE_PERSISTENT
The SQLITE_PREPARE_PERSISTENT flag is a hint to the query planner that the prepared statement will be retained for a long time and probably reused many times. Without this flag, [sqlite3_prepare_v3()](#sqlite3_prepare) and [sqlite3_prepare16_v3()](#sqlite3_prepare) assume that the prepared statement will be used just once or at most a few times and then destroyed using [sqlite3_finalize()](#sqlite3_finalize) relatively soon. The current implementation acts on this hint by avoiding the use of [lookaside memory](malloc.md#lookaside) so as not to deplete the limited store of lookaside memory. Future versions of SQLite may act on this hint differently.
SQLITE_PREPARE_NORMALIZE
The SQLITE_PREPARE_NORMALIZE flag is a no-op. This flag used to be required for any prepared statement that wanted to use the [sqlite3_normalized_sql()](#sqlite3_expanded_sql) interface. However, the [sqlite3_normalized_sql()](#sqlite3_expanded_sql) interface is now available to all prepared statements, regardless of whether or not they use this flag.
SQLITE_PREPARE_NO_VTAB
The SQLITE_PREPARE_NO_VTAB flag causes the SQL compiler to return an error (error code SQLITE_ERROR) if the statement uses any virtual tables.
SQLITE_PREPARE_DONT_LOG
The SQLITE_PREPARE_DONT_LOG flag prevents SQL compiler errors from being sent to the error log defined by [SQLITE_CONFIG_LOG](#sqliteconfiglog). This can be used, for example, to do test compiles to see if some SQL syntax is well-formed, without generating messages on the global error log when it is not. If the test compile fails, the sqlite3_prepare_v3() call returns the same error indications with or without this flag; it just omits the call to [sqlite3_log()](#sqlite3_log) that logs the error.
SQLITE_PREPARE_FROM_DDL
The SQLITE_PREPARE_FROM_DDL flag causes the SQL compiler to enforce security constraints that would otherwise only be enforced when parsing the database schema. In other words, the SQLITE_PREPARE_FROM_DDL flag causes the SQL compiler to treat the SQL statement being prepared as if it had come from an attacker. When SQLITE_PREPARE_FROM_DDL is used and [SQLITE_DBCONFIG_TRUSTED_SCHEMA](#sqlitedbconfigtrustedschema) is off, SQL functions may only be called if they are tagged with [SQLITE_INNOCUOUS](#sqliteinnocuous) and virtual tables may only be used if they are tagged with [SQLITE_VTAB_INNOCUOUS](#sqlitevtabinnocuous). Best practice is to use the SQLITE_PREPARE_FROM_DDL option when preparing any SQL that is derived from parts of the database schema. In particular, virtual table implementations that run SQL statements that are derived from arguments to their CREATE VIRTUAL TABLE statement should always use [sqlite3_prepare_v3()](#sqlite3_prepare) and set the SQLITE_PREPARE_FROM_DDL flag to prevent bypass of the [SQLITE_DBCONFIG_TRUSTED_SCHEMA](#sqlitedbconfigtrustedschema) security checks.
------------------------------------------------------------------------
## Prepared Statement Scan Status
> \
> \#define SQLITE_SCANSTAT_COMPLEX 0x0001\
------------------------------------------------------------------------
## Prepared Statement Scan Status Opcodes
> \
> \#define SQLITE_SCANSTAT_NLOOP 0\
> \#define SQLITE_SCANSTAT_NVISIT 1\
> \#define SQLITE_SCANSTAT_EST 2\
> \#define SQLITE_SCANSTAT_NAME 3\
> \#define SQLITE_SCANSTAT_EXPLAIN 4\
> \#define SQLITE_SCANSTAT_SELECTID 5\
> \#define SQLITE_SCANSTAT_PARENTID 6\
> \#define SQLITE_SCANSTAT_NCYCLE 7\
The following constants can be used for the T parameter to the [sqlite3_stmt_scanstatus(S,X,T,V)](#sqlite3_stmt_scanstatus) interface. Each constant designates a different metric for sqlite3_stmt_scanstatus() to return.
When the value returned to V is a string, space to hold that string is managed by the prepared statement S and will be automatically freed when S is finalized.
Not all values are available for all query elements. When a value is not available, the output variable is set to -1 if the value is numeric, or to NULL if it is a string (SQLITE_SCANSTAT_NAME).
SQLITE_SCANSTAT_NLOOP
The [sqlite3_int64](#sqlite3_int64) variable pointed to by the V parameter will be set to the total number of times that the X-th loop has run.
SQLITE_SCANSTAT_NVISIT
The [sqlite3_int64](#sqlite3_int64) variable pointed to by the V parameter will be set to the total number of rows examined by all iterations of the X-th loop.
SQLITE_SCANSTAT_EST
The "double" variable pointed to by the V parameter will be set to the query planner's estimate for the average number of rows output from each iteration of the X-th loop. If the query planner's estimate was accurate, then this value will approximate the quotient NVISIT/NLOOP and the product of this value for all prior loops with the same SELECTID will be the NLOOP value for the current loop.
SQLITE_SCANSTAT_NAME
The "const char \*" variable pointed to by the V parameter will be set to a zero-terminated UTF-8 string containing the name of the index or table used for the X-th loop.
SQLITE_SCANSTAT_EXPLAIN
The "const char \*" variable pointed to by the V parameter will be set to a zero-terminated UTF-8 string containing the [EXPLAIN QUERY PLAN](eqp.md) description for the X-th loop.
SQLITE_SCANSTAT_SELECTID
The "int" variable pointed to by the V parameter will be set to the id for the X-th query plan element. The id value is unique within the statement. The select-id is the same value as is output in the first column of an [EXPLAIN QUERY PLAN](eqp.md) query.
SQLITE_SCANSTAT_PARENTID
The "int" variable pointed to by the V parameter will be set to the id of the parent of the current query element, if applicable, or to zero if the query element has no parent. This is the same value as returned in the second column of an [EXPLAIN QUERY PLAN](eqp.md) query.
SQLITE_SCANSTAT_NCYCLE
The sqlite3_int64 output value is set to the number of cycles, according to the processor time-stamp counter, that elapsed while the query element was being processed. This value is not available for all query elements - if it is unavailable the output variable is set to -1.
------------------------------------------------------------------------
## Compile-Time Library Version Numbers
> \
> \#define SQLITE_VERSION "3.53.4"\
> \#define SQLITE_VERSION_NUMBER 3053004\
> \#define SQLITE_SOURCE_ID "2026-07-24 19:02:57 bf7c7f30031888f4e796e429ab3978879485813aaca6f641c7b33e4e09459bcc"\
> \#define SQLITE_SCM_BRANCH "branch-3.53"\
> \#define SQLITE_SCM_TAGS "release version-3.53.4"\
> \#define SQLITE_SCM_DATETIME "2026-07-24T19:02:57.525Z"\
The [SQLITE_VERSION](#SQLITE_SCM_BRANCH) C preprocessor macro in the sqlite3.h header evaluates to a string literal that is the SQLite version in the format "X.Y.Z" where X is the major version number (always 3 for SQLite3) and Y is the minor version number and Z is the release number. The [SQLITE_VERSION_NUMBER](#SQLITE_SCM_BRANCH) C preprocessor macro resolves to an integer with the value (X\*1000000 + Y\*1000 + Z) where X, Y, and Z are the same numbers used in [SQLITE_VERSION](#SQLITE_SCM_BRANCH). The SQLITE_VERSION_NUMBER for any given release of SQLite will also be larger than the release from which it is derived. Either Y will be held constant and Z will be incremented or else Y will be incremented and Z will be reset to zero.
Since [version 3.6.18](releaselog/3_6_18.md) (2009-09-11), SQLite source code has been stored in the [Fossil configuration management system](http://fossil-scm.org/). The SQLITE_SOURCE_ID macro evaluates to a string which identifies a particular check-in of SQLite within its configuration management system. The SQLITE_SOURCE_ID string contains the date and time of the check-in (UTC) and a SHA1 or SHA3-256 hash of the entire source tree. If the source code has been edited in any way since it was last checked in, then the last four hexadecimal digits of the hash may be modified.
See also: [sqlite3_libversion()](#sqlite3_libversion), [sqlite3_libversion_number()](#sqlite3_libversion), [sqlite3_sourceid()](#sqlite3_libversion), [sqlite_version()](lang_corefunc.md#sqlite_version) and [sqlite_source_id()](lang_corefunc.md#sqlite_source_id).
------------------------------------------------------------------------
## Flags for the xShmLock VFS method
> \
> \#define SQLITE_SHM_UNLOCK 1\
> \#define SQLITE_SHM_LOCK 2\
> \#define SQLITE_SHM_SHARED 4\
> \#define SQLITE_SHM_EXCLUSIVE 8\
These integer constants define the various locking operations allowed by the xShmLock method of [sqlite3_io_methods](#sqlite3_io_methods). The following are the only legal combinations of flags to the xShmLock method:
- SQLITE_SHM_LOCK \| SQLITE_SHM_SHARED
- SQLITE_SHM_LOCK \| SQLITE_SHM_EXCLUSIVE
- SQLITE_SHM_UNLOCK \| SQLITE_SHM_SHARED
- SQLITE_SHM_UNLOCK \| SQLITE_SHM_EXCLUSIVE
When unlocking, the same SHARED or EXCLUSIVE flag must be supplied as was given on the corresponding lock.
The xShmLock method can transition between unlocked and SHARED or between unlocked and EXCLUSIVE. It cannot transition between SHARED and EXCLUSIVE.
------------------------------------------------------------------------
## Constants Defining Special Destructor Behavior
> \
> typedef void (\*sqlite3_destructor_type)(void\*);\
> \#define SQLITE_STATIC ((sqlite3_destructor_type)0)\
> \#define SQLITE_TRANSIENT ((sqlite3_destructor_type)-1)\
These are special values for the destructor that is passed in as the final argument to routines like [sqlite3_result_blob()](#sqlite3_result_blob). If the destructor argument is SQLITE_STATIC, it means that the content pointer is constant and will never change. It does not need to be destroyed. The SQLITE_TRANSIENT value means that the content will likely change in the near future and that SQLite should make its own private copy of the content before returning.
The typedef is necessary to work around problems in certain C++ compilers.
------------------------------------------------------------------------
## Status Parameters
> \
> \#define SQLITE_STATUS_MEMORY_USED 0\
> \#define SQLITE_STATUS_PAGECACHE_USED 1\
> \#define SQLITE_STATUS_PAGECACHE_OVERFLOW 2\
> \#define SQLITE_STATUS_SCRATCH_USED 3 /\* NOT USED \*/\
> \#define SQLITE_STATUS_SCRATCH_OVERFLOW 4 /\* NOT USED \*/\
> \#define SQLITE_STATUS_MALLOC_SIZE 5\
> \#define SQLITE_STATUS_PARSER_STACK 6\
> \#define SQLITE_STATUS_PAGECACHE_SIZE 7\
> \#define SQLITE_STATUS_SCRATCH_SIZE 8 /\* NOT USED \*/\
> \#define SQLITE_STATUS_MALLOC_COUNT 9\
These integer constants designate various run-time status parameters that can be returned by [sqlite3_status()](#sqlite3_status).
SQLITE_STATUS_MEMORY_USED
This parameter is the current amount of memory checked out using [sqlite3_malloc()](#sqlite3_free), either directly or indirectly. The figure includes calls made to [sqlite3_malloc()](#sqlite3_free) by the application and internal memory usage by the SQLite library. Auxiliary page-cache memory controlled by [SQLITE_CONFIG_PAGECACHE](#sqliteconfigpagecache) is not included in this parameter. The amount returned is the sum of the allocation sizes as reported by the xSize method in [sqlite3_mem_methods](#sqlite3_mem_methods).
SQLITE_STATUS_MALLOC_SIZE
This parameter records the largest memory allocation request handed to [sqlite3_malloc()](#sqlite3_free) or [sqlite3_realloc()](#sqlite3_free) (or their internal equivalents). Only the value returned in the \*pHighwater parameter to [sqlite3_status()](#sqlite3_status) is of interest. The value written into the \*pCurrent parameter is undefined.
SQLITE_STATUS_MALLOC_COUNT
This parameter records the number of separate memory allocations currently checked out.
SQLITE_STATUS_PAGECACHE_USED
This parameter returns the number of pages used out of the [pagecache memory allocator](malloc.md#pagecache) that was configured using [SQLITE_CONFIG_PAGECACHE](#sqliteconfigpagecache). The value returned is in pages, not in bytes.
SQLITE_STATUS_PAGECACHE_OVERFLOW
This parameter returns the number of bytes of page cache allocation which could not be satisfied by the [SQLITE_CONFIG_PAGECACHE](#sqliteconfigpagecache) buffer and where forced to overflow to [sqlite3_malloc()](#sqlite3_free). The returned value includes allocations that overflowed because they were too large (they were larger than the "sz" parameter to [SQLITE_CONFIG_PAGECACHE](#sqliteconfigpagecache)) and allocations that overflowed because no space was left in the page cache.
SQLITE_STATUS_PAGECACHE_SIZE
This parameter records the largest memory allocation request handed to the [pagecache memory allocator](malloc.md#pagecache). Only the value returned in the \*pHighwater parameter to [sqlite3_status()](#sqlite3_status) is of interest. The value written into the \*pCurrent parameter is undefined.
SQLITE_STATUS_SCRATCH_USED
No longer used.
SQLITE_STATUS_SCRATCH_OVERFLOW
No longer used.
SQLITE_STATUS_SCRATCH_SIZE
No longer used.
SQLITE_STATUS_PARSER_STACK
The \*pHighwater parameter records the deepest parser stack. The \*pCurrent value is undefined. The \*pHighwater value is only meaningful if SQLite is compiled with [YYTRACKMAXSTACKDEPTH](compile.md#yytrackmaxstackdepth).
New status parameters may be added from time to time.
------------------------------------------------------------------------
## Synchronization Type Flags
> \
> \#define SQLITE_SYNC_NORMAL 0x00002\
> \#define SQLITE_SYNC_FULL 0x00003\
> \#define SQLITE_SYNC_DATAONLY 0x00010\
When SQLite invokes the xSync() method of an [sqlite3_io_methods](#sqlite3_io_methods) object it uses a combination of these integer values as the second argument.
When the SQLITE_SYNC_DATAONLY flag is used, it means that the sync operation only needs to flush data to mass storage. Inode information need not be flushed. If the lower four bits of the flag equal SQLITE_SYNC_NORMAL, that means to use normal fsync() semantics. If the lower four bits equal SQLITE_SYNC_FULL, that means to use Mac OS X style fullsync instead of fsync().
Do not confuse the SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL flags with the [PRAGMA synchronous](pragma.md#pragma_synchronous)=NORMAL and [PRAGMA synchronous](pragma.md#pragma_synchronous)=FULL settings. The [synchronous pragma](pragma.md#pragma_synchronous) determines when calls to the xSync VFS method occur and applies uniformly across all platforms. The SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL flags determine how energetic or rigorous or forceful the sync operations are and only make a difference on Mac OSX for the default SQLite code. (Third-party VFS implementations might also make the distinction between SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL, but among the operating systems natively supported by SQLite, only Mac OSX cares about the difference.)
------------------------------------------------------------------------
## Testing Interface Operation Codes
> \
> \#define SQLITE_TESTCTRL_FIRST 5\
> \#define SQLITE_TESTCTRL_PRNG_SAVE 5\
> \#define SQLITE_TESTCTRL_PRNG_RESTORE 6\
> \#define SQLITE_TESTCTRL_PRNG_RESET 7 /\* NOT USED \*/\
> \#define SQLITE_TESTCTRL_FK_NO_ACTION 7\
> \#define SQLITE_TESTCTRL_BITVEC_TEST 8\
> \#define SQLITE_TESTCTRL_FAULT_INSTALL 9\
> \#define SQLITE_TESTCTRL_BENIGN_MALLOC_HOOKS 10\
> \#define SQLITE_TESTCTRL_PENDING_BYTE 11\
> \#define SQLITE_TESTCTRL_ASSERT 12\
> \#define SQLITE_TESTCTRL_ALWAYS 13\
> \#define SQLITE_TESTCTRL_RESERVE 14 /\* NOT USED \*/\
> \#define SQLITE_TESTCTRL_JSON_SELFCHECK 14\
> \#define SQLITE_TESTCTRL_OPTIMIZATIONS 15\
> \#define SQLITE_TESTCTRL_ISKEYWORD 16 /\* NOT USED \*/\
> \#define SQLITE_TESTCTRL_GETOPT 16\
> \#define SQLITE_TESTCTRL_SCRATCHMALLOC 17 /\* NOT USED \*/\
> \#define SQLITE_TESTCTRL_INTERNAL_FUNCTIONS 17\
> \#define SQLITE_TESTCTRL_LOCALTIME_FAULT 18\
> \#define SQLITE_TESTCTRL_EXPLAIN_STMT 19 /\* NOT USED \*/\
> \#define SQLITE_TESTCTRL_ONCE_RESET_THRESHOLD 19\
> \#define SQLITE_TESTCTRL_NEVER_CORRUPT 20\
> \#define SQLITE_TESTCTRL_VDBE_COVERAGE 21\
> \#define SQLITE_TESTCTRL_BYTEORDER 22\
> \#define SQLITE_TESTCTRL_ISINIT 23\
> \#define SQLITE_TESTCTRL_SORTER_MMAP 24\
> \#define SQLITE_TESTCTRL_IMPOSTER 25\
> \#define SQLITE_TESTCTRL_PARSER_COVERAGE 26\
> \#define SQLITE_TESTCTRL_RESULT_INTREAL 27\
> \#define SQLITE_TESTCTRL_PRNG_SEED 28\
> \#define SQLITE_TESTCTRL_EXTRA_SCHEMA_CHECKS 29\
> \#define SQLITE_TESTCTRL_SEEK_COUNT 30\
> \#define SQLITE_TESTCTRL_TRACEFLAGS 31\
> \#define SQLITE_TESTCTRL_TUNE 32\
> \#define SQLITE_TESTCTRL_LOGEST 33\
> \#define SQLITE_TESTCTRL_USELONGDOUBLE 34 /\* NOT USED \*/\
> \#define SQLITE_TESTCTRL_ATOF 34\
> \#define SQLITE_TESTCTRL_LAST 34 /\* Largest TESTCTRL \*/\
These constants are the valid operation code parameters used as the first argument to [sqlite3_test_control()](#sqlite3_test_control).
These parameters and their meanings are subject to change without notice. These values are for testing purposes only. Applications should not use any of these parameters or the [sqlite3_test_control()](#sqlite3_test_control) interface.
------------------------------------------------------------------------
## SQL Trace Event Codes
> \
> \#define SQLITE_TRACE_STMT 0x01\
> \#define SQLITE_TRACE_PROFILE 0x02\
> \#define SQLITE_TRACE_ROW 0x04\
> \#define SQLITE_TRACE_CLOSE 0x08\
These constants identify classes of events that can be monitored using the [sqlite3_trace_v2()](#sqlite3_trace_v2) tracing logic. The M argument to [sqlite3_trace_v2(D,M,X,P)](#sqlite3_trace_v2) is an OR-ed combination of one or more of the following constants. The first argument to the trace callback is one of the following constants.
New tracing constants may be added in future releases.
A trace callback has four arguments: xCallback(T,C,P,X). The T argument is one of the integer type codes above. The C argument is a copy of the context pointer passed in as the fourth argument to [sqlite3_trace_v2()](#sqlite3_trace_v2). The P and X arguments are pointers whose meanings depend on T.
SQLITE_TRACE_STMT
An SQLITE_TRACE_STMT callback is invoked when a prepared statement first begins running and possibly at other times during the execution of the prepared statement, such as at the start of each trigger subprogram. The P argument is a pointer to the [prepared statement](#sqlite3_stmt). The X argument is a pointer to a string which is the unexpanded SQL text of the prepared statement or an SQL comment that indicates the invocation of a trigger. The callback can compute the same text that would have been returned by the legacy [sqlite3_trace()](#sqlite3_profile) interface by using the X argument when X begins with "--" and invoking [sqlite3_expanded_sql(P)](#sqlite3_expanded_sql) otherwise.
SQLITE_TRACE_PROFILE
An SQLITE_TRACE_PROFILE callback provides approximately the same information as is provided by the [sqlite3_profile()](#sqlite3_profile) callback. The P argument is a pointer to the [prepared statement](#sqlite3_stmt) and the X argument points to a 64-bit integer which is approximately the number of nanoseconds that the prepared statement took to run. The SQLITE_TRACE_PROFILE callback is invoked when the statement finishes.
SQLITE_TRACE_ROW
An SQLITE_TRACE_ROW callback is invoked whenever a prepared statement generates a single row of result. The P argument is a pointer to the [prepared statement](#sqlite3_stmt) and the X argument is unused.
SQLITE_TRACE_CLOSE
An SQLITE_TRACE_CLOSE callback is invoked when a database connection closes. The P argument is a pointer to the [database connection](#sqlite3) object and the X argument is unused.
------------------------------------------------------------------------
## Allowed return values from sqlite3_txn_state()
> \
> \#define SQLITE_TXN_NONE 0\
> \#define SQLITE_TXN_READ 1\
> \#define SQLITE_TXN_WRITE 2\
These constants define the current transaction state of a database file. The [sqlite3_txn_state(D,S)](#sqlite3_txn_state) interface returns one of these constants in order to describe the transaction state of schema S in [database connection](#sqlite3) D.
SQLITE_TXN_NONE
The SQLITE_TXN_NONE state means that no transaction is currently pending.
SQLITE_TXN_READ
The SQLITE_TXN_READ state means that the database is currently in a read transaction. Content has been read from the database file but nothing in the database file has changed. The transaction state will be advanced to SQLITE_TXN_WRITE if any changes occur and there are no other conflicting concurrent write transactions. The transaction state will revert to SQLITE_TXN_NONE following a [ROLLBACK](lang_transaction.md) or [COMMIT](lang_transaction.md).
SQLITE_TXN_WRITE
The SQLITE_TXN_WRITE state means that the database is currently in a write transaction. Content has been written to the database file but has not yet committed. The transaction state will change to SQLITE_TXN_NONE at the next [ROLLBACK](lang_transaction.md) or [COMMIT](lang_transaction.md).
SQLITE_VTAB_CONSTRAINT_SUPPORT
Calls of the form [sqlite3_vtab_config](#sqlite3_vtab_config)(db,SQLITE_VTAB_CONSTRAINT_SUPPORT,X) are supported, where X is an integer. If X is zero, then the [virtual table](vtab.md) whose [xCreate](vtab.md#xcreate) or [xConnect](vtab.md#xconnect) method invoked [sqlite3_vtab_config()](#sqlite3_vtab_config) does not support constraints. In this configuration (which is the default) if a call to the [xUpdate](vtab.md#xupdate) method returns [SQLITE_CONSTRAINT](#SQLITE_ABORT), then the entire statement is rolled back as if [OR ABORT](lang_conflict.md) had been specified as part of the user's SQL statement, regardless of the actual ON CONFLICT mode specified.
If X is non-zero, then the virtual table implementation guarantees that if [xUpdate](vtab.md#xupdate) returns [SQLITE_CONSTRAINT](#SQLITE_ABORT), it will do so before any modifications to internal or persistent data structures have been made. If the [ON CONFLICT](lang_conflict.md) mode is ABORT, FAIL, IGNORE or ROLLBACK, SQLite is able to roll back a statement or database transaction, and abandon or continue processing the current SQL statement as appropriate. If the ON CONFLICT mode is REPLACE and the [xUpdate](vtab.md#xupdate) method returns [SQLITE_CONSTRAINT](#SQLITE_ABORT), SQLite handles this as if the ON CONFLICT mode had been ABORT.
Virtual table implementations that are required to handle OR REPLACE must do so within the [xUpdate](vtab.md#xupdate) method. If a call to the [sqlite3_vtab_on_conflict()](#sqlite3_vtab_on_conflict) function indicates that the current ON CONFLICT policy is REPLACE, the virtual table implementation should silently replace the appropriate rows within the xUpdate callback and return SQLITE_OK. Or, if this is not possible, it may return SQLITE_CONSTRAINT, in which case SQLite falls back to OR ABORT constraint handling.
SQLITE_VTAB_DIRECTONLY
Calls of the form [sqlite3_vtab_config](#sqlite3_vtab_config)(db,SQLITE_VTAB_DIRECTONLY) from within the the [xConnect](vtab.md#xconnect) or [xCreate](vtab.md#xcreate) methods of a [virtual table](vtab.md) implementation prohibits that virtual table from being used from within triggers and views.
SQLITE_VTAB_INNOCUOUS
Calls of the form [sqlite3_vtab_config](#sqlite3_vtab_config)(db,SQLITE_VTAB_INNOCUOUS) from within the [xConnect](vtab.md#xconnect) or [xCreate](vtab.md#xcreate) methods of a [virtual table](vtab.md) implementation identify that virtual table as being safe to use from within triggers and views. Conceptually, the SQLITE_VTAB_INNOCUOUS tag means that the virtual table can do no serious harm even if it is controlled by a malicious hacker. Developers should avoid setting the SQLITE_VTAB_INNOCUOUS flag unless absolutely necessary.
SQLITE_VTAB_USES_ALL_SCHEMAS
Calls of the form [sqlite3_vtab_config](#sqlite3_vtab_config)(db,SQLITE_VTAB_USES_ALL_SCHEMA) from within the the [xConnect](vtab.md#xconnect) or [xCreate](vtab.md#xcreate) methods of a [virtual table](vtab.md) implementation instruct the query planner to begin at least a read transaction on all schemas ("main", "temp", and any ATTACH-ed databases) whenever the virtual table is used.
------------------------------------------------------------------------
## Win32 Directory Types
> \
> \#define SQLITE_WIN32_DATA_DIRECTORY_TYPE 1\
> \#define SQLITE_WIN32_TEMP_DIRECTORY_TYPE 2\
These macros are only available on Windows. They define the allowed values for the type argument to the [sqlite3_win32_set_directory](#sqlite3_win32_set_directory) interface.
------------------------------------------------------------------------
## Run-Time Limit Categories
> \
> \#define SQLITE_LIMIT_LENGTH 0\
> \#define SQLITE_LIMIT_SQL_LENGTH 1\
> \#define SQLITE_LIMIT_COLUMN 2\
> \#define SQLITE_LIMIT_EXPR_DEPTH 3\
> \#define SQLITE_LIMIT_COMPOUND_SELECT 4\
> \#define SQLITE_LIMIT_VDBE_OP 5\
> \#define SQLITE_LIMIT_FUNCTION_ARG 6\
> \#define SQLITE_LIMIT_ATTACHED 7\
> \#define SQLITE_LIMIT_LIKE_PATTERN_LENGTH 8\
> \#define SQLITE_LIMIT_VARIABLE_NUMBER 9\
> \#define SQLITE_LIMIT_TRIGGER_DEPTH 10\
> \#define SQLITE_LIMIT_WORKER_THREADS 11\
> \#define SQLITE_LIMIT_PARSER_DEPTH 12\
These constants define various performance limits that can be lowered at run-time using [sqlite3_limit()](#sqlite3_limit). A concise description of these limits follows, and additional information is available at [Limits in SQLite](limits.md).
SQLITE_LIMIT_LENGTH
The maximum size of any string or BLOB or table row, in bytes.
SQLITE_LIMIT_SQL_LENGTH
The maximum length of an SQL statement, in bytes.
SQLITE_LIMIT_COLUMN
The maximum number of columns in a table definition or in the result set of a [SELECT](lang_select.md) or the maximum number of columns in an index or in an ORDER BY or GROUP BY clause.
SQLITE_LIMIT_EXPR_DEPTH
The maximum depth of the parse tree on any expression and the maximum nesting depth for subqueries and VIEWs
SQLITE_LIMIT_PARSER_DEPTH
The maximum depth of the LALR(1) parser stack used to analyze input SQL statements.
SQLITE_LIMIT_COMPOUND_SELECT
The maximum number of terms in a compound SELECT statement.
SQLITE_LIMIT_VDBE_OP
The maximum number of instructions in a virtual machine program used to implement an SQL statement. If [sqlite3_prepare_v2()](#sqlite3_prepare) or the equivalent tries to allocate space for more than this many opcodes in a single prepared statement, an SQLITE_NOMEM error is returned.
SQLITE_LIMIT_FUNCTION_ARG
The maximum number of arguments on a function.
SQLITE_LIMIT_ATTACHED
The maximum number of [attached databases](lang_attach.md).
SQLITE_LIMIT_LIKE_PATTERN_LENGTH
The maximum length of the pattern argument to the [LIKE](lang_expr.md#like) or [GLOB](lang_expr.md#glob) operators.
SQLITE_LIMIT_VARIABLE_NUMBER
The maximum index number of any [parameter](lang_expr.md#varparam) in an SQL statement.
SQLITE_LIMIT_TRIGGER_DEPTH
The maximum depth of recursion for triggers, and the maximum nesting depth for separate triggers.
SQLITE_LIMIT_WORKER_THREADS
The maximum number of auxiliary worker threads that a single [prepared statement](#sqlite3_stmt) may start.
------------------------------------------------------------------------
## Status Parameters for database connections
> \
> \#define SQLITE_DBSTATUS_LOOKASIDE_USED 0\
> \#define SQLITE_DBSTATUS_CACHE_USED 1\
> \#define SQLITE_DBSTATUS_SCHEMA_USED 2\
> \#define SQLITE_DBSTATUS_STMT_USED 3\
> \#define SQLITE_DBSTATUS_LOOKASIDE_HIT 4\
> \#define SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE 5\
> \#define SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL 6\
> \#define SQLITE_DBSTATUS_CACHE_HIT 7\
> \#define SQLITE_DBSTATUS_CACHE_MISS 8\
> \#define SQLITE_DBSTATUS_CACHE_WRITE 9\
> \#define SQLITE_DBSTATUS_DEFERRED_FKS 10\
> \#define SQLITE_DBSTATUS_CACHE_USED_SHARED 11\
> \#define SQLITE_DBSTATUS_CACHE_SPILL 12\
> \#define SQLITE_DBSTATUS_TEMPBUF_SPILL 13\
> \#define SQLITE_DBSTATUS_MAX 13 /\* Largest defined DBSTATUS \*/\
These constants are the available integer "verbs" that can be passed as the second argument to the [sqlite3_db_status()](#sqlite3_db_status) interface.
New verbs may be added in future releases of SQLite. Existing verbs might be discontinued. Applications should check the return code from [sqlite3_db_status()](#sqlite3_db_status) to make sure that the call worked. The [sqlite3_db_status()](#sqlite3_db_status) interface will return a non-zero error code if a discontinued or unsupported verb is invoked.
SQLITE_DBSTATUS_LOOKASIDE_USED
This parameter returns the number of lookaside memory slots currently checked out.
SQLITE_DBSTATUS_LOOKASIDE_HIT
This parameter returns the number of malloc attempts that were satisfied using lookaside memory. Only the high-water value is meaningful; the current value is always zero.
SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE
This parameter returns the number of malloc attempts that might have been satisfied using lookaside memory but failed due to the amount of memory requested being larger than the lookaside slot size. Only the high-water value is meaningful; the current value is always zero.
SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL
This parameter returns the number of malloc attempts that might have been satisfied using lookaside memory but failed due to all lookaside memory already being in use. Only the high-water value is meaningful; the current value is always zero.
SQLITE_DBSTATUS_CACHE_USED
This parameter returns the approximate number of bytes of heap memory used by all pager caches associated with the database connection. The highwater mark associated with SQLITE_DBSTATUS_CACHE_USED is always 0.
SQLITE_DBSTATUS_CACHE_USED_SHARED
This parameter is similar to DBSTATUS_CACHE_USED, except that if a pager cache is shared between two or more connections the bytes of heap memory used by that pager cache is divided evenly between the attached connections. In other words, if none of the pager caches associated with the database connection are shared, this request returns the same value as DBSTATUS_CACHE_USED. Or, if one or more of the pager caches are shared, the value returned by this call will be smaller than that returned by DBSTATUS_CACHE_USED. The highwater mark associated with SQLITE_DBSTATUS_CACHE_USED_SHARED is always 0.
SQLITE_DBSTATUS_SCHEMA_USED
This parameter returns the approximate number of bytes of heap memory used to store the schema for all databases associated with the connection - main, temp, and any [ATTACH](lang_attach.md)-ed databases. The full amount of memory used by the schemas is reported, even if the schema memory is shared with other database connections due to [shared cache mode](sharedcache.md) being enabled. The highwater mark associated with SQLITE_DBSTATUS_SCHEMA_USED is always 0.
SQLITE_DBSTATUS_STMT_USED
This parameter returns the approximate number of bytes of heap and lookaside memory used by all prepared statements associated with the database connection. The highwater mark associated with SQLITE_DBSTATUS_STMT_USED is always 0.
SQLITE_DBSTATUS_CACHE_HIT
This parameter returns the number of pager cache hits that have occurred. The highwater mark associated with SQLITE_DBSTATUS_CACHE_HIT is always 0.
SQLITE_DBSTATUS_CACHE_MISS
This parameter returns the number of pager cache misses that have occurred. The highwater mark associated with SQLITE_DBSTATUS_CACHE_MISS is always 0.
SQLITE_DBSTATUS_CACHE_WRITE
This parameter returns the number of dirty cache entries that have been written to disk. Specifically, the number of pages written to the wal file in wal mode databases, or the number of pages written to the database file in rollback mode databases. Any pages written as part of transaction rollback or database recovery operations are not included. If an IO or other error occurs while writing a page to disk, the effect on subsequent SQLITE_DBSTATUS_CACHE_WRITE requests is undefined. The highwater mark associated with SQLITE_DBSTATUS_CACHE_WRITE is always 0.
There is overlap between the quantities measured by this parameter (SQLITE_DBSTATUS_CACHE_WRITE) and SQLITE_DBSTATUS_TEMPBUF_SPILL. Resetting one will reduce the other.
SQLITE_DBSTATUS_CACHE_SPILL
This parameter returns the number of dirty cache entries that have been written to disk in the middle of a transaction due to the page cache overflowing. Transactions are more efficient if they are written to disk all at once. When pages spill mid-transaction, that introduces additional overhead. This parameter can be used to help identify inefficiencies that can be resolved by increasing the cache size.
SQLITE_DBSTATUS_DEFERRED_FKS
This parameter returns zero for the current value if and only if all foreign key constraints (deferred or immediate) have been resolved. The highwater mark is always 0.
[\[SQLITE_DBSTATUS_TEMPBUF_SPILL](#SQLITE_DBSTATUS%20options)
SQLITE_DBSTATUS_TEMPBUF_SPILL
This parameter returns the number of bytes written to temporary files on disk that could have been kept in memory had sufficient memory been available. This value includes writes to intermediate tables that are part of complex queries, external sorts that spill to disk, and writes to TEMP tables. The highwater mark is always 0.
There is overlap between the quantities measured by this parameter (SQLITE_DBSTATUS_TEMPBUF_SPILL) and SQLITE_DBSTATUS_CACHE_WRITE. Resetting one will reduce the other.
------------------------------------------------------------------------
## Status Parameters for prepared statements
> \
> \#define SQLITE_STMTSTATUS_FULLSCAN_STEP 1\
> \#define SQLITE_STMTSTATUS_SORT 2\
> \#define SQLITE_STMTSTATUS_AUTOINDEX 3\
> \#define SQLITE_STMTSTATUS_VM_STEP 4\
> \#define SQLITE_STMTSTATUS_REPREPARE 5\
> \#define SQLITE_STMTSTATUS_RUN 6\
> \#define SQLITE_STMTSTATUS_FILTER_MISS 7\
> \#define SQLITE_STMTSTATUS_FILTER_HIT 8\
> \#define SQLITE_STMTSTATUS_MEMUSED 99\
These preprocessor macros define integer codes that name counter values associated with the [sqlite3_stmt_status()](#sqlite3_stmt_status) interface. The meanings of the various counters are as follows:
SQLITE_STMTSTATUS_FULLSCAN_STEP
This is the number of times that SQLite has stepped forward in a table as part of a full table scan. Large numbers for this counter may indicate opportunities for performance improvement through careful use of indices.
SQLITE_STMTSTATUS_SORT
This is the number of sort operations that have occurred. A non-zero value in this counter may indicate an opportunity to improve performance through careful use of indices.
SQLITE_STMTSTATUS_AUTOINDEX
This is the number of rows inserted into transient indices that were created automatically in order to help joins run faster. A non-zero value in this counter may indicate an opportunity to improve performance by adding permanent indices that do not need to be reinitialized each time the statement is run.
SQLITE_STMTSTATUS_VM_STEP
This is the number of virtual machine operations executed by the prepared statement if that number is less than or equal to 2147483647. The number of virtual machine operations can be used as a proxy for the total work done by the prepared statement. If the number of virtual machine operations exceeds 2147483647 then the value returned by this statement status code is undefined.
SQLITE_STMTSTATUS_REPREPARE
This is the number of times that the prepare statement has been automatically regenerated due to schema changes or changes to [bound parameters](lang_expr.md#varparam) that might affect the query plan.
SQLITE_STMTSTATUS_RUN
This is the number of times that the prepared statement has been run. A single "run" for the purposes of this counter is one or more calls to [sqlite3_step()](#sqlite3_step) followed by a call to [sqlite3_reset()](#sqlite3_reset). The counter is incremented on the first [sqlite3_step()](#sqlite3_step) call of each cycle.
SQLITE_STMTSTATUS_FILTER_HIT\
SQLITE_STMTSTATUS_FILTER_MISS
SQLITE_STMTSTATUS_FILTER_HIT is the number of times that a join step was bypassed because a Bloom filter returned not-found. The corresponding SQLITE_STMTSTATUS_FILTER_MISS value is the number of times that the Bloom filter returned a find, and thus the join step had to be processed as normal.
SQLITE_STMTSTATUS_MEMUSED
This is the approximate number of bytes of heap memory used to store the prepared statement. This value is not actually a counter, and so the resetFlg parameter to sqlite3_stmt_status() is ignored when the opcode is SQLITE_STMTSTATUS_MEMUSED.
------------------------------------------------------------------------
## Database Snapshot
> \
> typedef struct sqlite3_snapshot {\
> unsigned char hidden\[48\];\
> } sqlite3_snapshot;\
An instance of the snapshot object records the state of a [WAL mode](wal.md) database for some specific point in history.
In [WAL mode](wal.md), multiple [database connections](#sqlite3) that are open on the same database file can each be reading a different historical version of the database file. When a [database connection](#sqlite3) begins a read transaction, that connection sees an unchanging copy of the database as it existed for the point in time when the transaction first started. Subsequent changes to the database from other connections are not seen by the reader until a new read transaction is started.
The sqlite3_snapshot object records state information about an historical version of the database file so that it is possible to later open a new read transaction that sees that historical version of the database rather than the most recent version.
1 Constructor using this object: [sqlite3_snapshot_get()](#sqlite3_snapshot_get)
1 Destructor using this object: [sqlite3_snapshot_free()](#sqlite3_snapshot_free)
3 Methods using this object: [sqlite3_snapshot_cmp()](#sqlite3_snapshot_cmp), [sqlite3_snapshot_open()](#sqlite3_snapshot_open), [sqlite3_snapshot_recover()](#sqlite3_snapshot_recover)
------------------------------------------------------------------------
## 64-Bit Integer Types
> \
> \#ifdef SQLITE_INT64_TYPE\
> typedef SQLITE_INT64_TYPE sqlite_int64;\
> \# ifdef SQLITE_UINT64_TYPE\
> typedef SQLITE_UINT64_TYPE sqlite_uint64;\
> \# else\
> typedef unsigned SQLITE_INT64_TYPE sqlite_uint64;\
> \# endif\
> \#elif defined(\_MSC_VER) \|\| defined(\_\_BORLANDC\_\_)\
> typedef \_\_int64 sqlite_int64;\
> typedef unsigned \_\_int64 sqlite_uint64;\
> \#else\
> typedef long long int sqlite_int64;\
> typedef unsigned long long int sqlite_uint64;\
> \#endif\
> typedef sqlite_int64 sqlite3_int64;\
> typedef sqlite_uint64 sqlite3_uint64;\
Because there is no cross-platform way to specify 64-bit integer types SQLite includes typedefs for 64-bit signed and unsigned integers.
The sqlite3_int64 and sqlite3_uint64 are the preferred type definitions. The sqlite_int64 and sqlite_uint64 types are supported for backwards compatibility only.
The sqlite3_int64 and sqlite_int64 types can store integer values between -9223372036854775808 and +9223372036854775807 inclusive. The sqlite3_uint64 and sqlite_uint64 types can store integer values between 0 and +18446744073709551615 inclusive.
------------------------------------------------------------------------
## Virtual Table Object
> \
> struct sqlite3_module {\
> int iVersion;\
> int (\*xCreate)(sqlite3\*, void \*pAux,\
> int argc, const char \*const\*argv,\
> sqlite3_vtab \*\*ppVTab, char\*\*);\
> int (\*xConnect)(sqlite3\*, void \*pAux,\
> int argc, const char \*const\*argv,\
> sqlite3_vtab \*\*ppVTab, char\*\*);\
> int (\*xBestIndex)(sqlite3_vtab \*pVTab, sqlite3_index_info\*);\
> int (\*xDisconnect)(sqlite3_vtab \*pVTab);\
> int (\*xDestroy)(sqlite3_vtab \*pVTab);\
> int (\*xOpen)(sqlite3_vtab \*pVTab, sqlite3_vtab_cursor \*\*ppCursor);\
> int (\*xClose)(sqlite3_vtab_cursor\*);\
> int (\*xFilter)(sqlite3_vtab_cursor\*, int idxNum, const char \*idxStr,\
> int argc, sqlite3_value \*\*argv);\
> int (\*xNext)(sqlite3_vtab_cursor\*);\
> int (\*xEof)(sqlite3_vtab_cursor\*);\
> int (\*xColumn)(sqlite3_vtab_cursor\*, sqlite3_context\*, int);\
> int (\*xRowid)(sqlite3_vtab_cursor\*, sqlite3_int64 \*pRowid);\
> int (\*xUpdate)(sqlite3_vtab \*, int, sqlite3_value \*\*, sqlite3_int64 \*);\
> int (\*xBegin)(sqlite3_vtab \*pVTab);\
> int (\*xSync)(sqlite3_vtab \*pVTab);\
> int (\*xCommit)(sqlite3_vtab \*pVTab);\
> int (\*xRollback)(sqlite3_vtab \*pVTab);\
> int (\*xFindFunction)(sqlite3_vtab \*pVtab, int nArg, const char \*zName,\
> void (\*\*pxFunc)(sqlite3_context\*,int,sqlite3_value\*\*),\
> void \*\*ppArg);\
> int (\*xRename)(sqlite3_vtab \*pVtab, const char \*zNew);\
> /\* The methods above are in version 1 of the sqlite_module object. Those\
> \*\* below are for version 2 and greater. \*/\
> int (\*xSavepoint)(sqlite3_vtab \*pVTab, int);\
> int (\*xRelease)(sqlite3_vtab \*pVTab, int);\
> int (\*xRollbackTo)(sqlite3_vtab \*pVTab, int);\
> /\* The methods above are in versions 1 and 2 of the sqlite_module object.\
> \*\* Those below are for version 3 and greater. \*/\
> int (\*xShadowName)(const char\*);\
> /\* The methods above are in versions 1 through 3 of the sqlite_module object.\
> \*\* Those below are for version 4 and greater. \*/\
> int (\*xIntegrity)(sqlite3_vtab \*pVTab, const char \*zSchema,\
> const char \*zTabName, int mFlags, char \*\*pzErr);\
> };\
This structure, sometimes called a "virtual table module", defines the implementation of a [virtual table](vtab.md). This structure consists mostly of methods for the module.
A virtual table module is created by filling in a persistent instance of this structure and passing a pointer to that instance to [sqlite3_create_module()](#sqlite3_create_module) or [sqlite3_create_module_v2()](#sqlite3_create_module). The registration remains valid until it is replaced by a different module or until the [database connection](#sqlite3) closes. The content of this structure must not change while it is registered with any database connection.
------------------------------------------------------------------------
## Virtual Table Cursor Object
> \
> struct sqlite3_vtab_cursor {\
> sqlite3_vtab \*pVtab; /\* Virtual table of this cursor \*/\
> /\* Virtual table implementations will typically add additional fields \*/\
> };\
Every [virtual table module](#sqlite3_module) implementation uses a subclass of the following structure to describe cursors that point into the [virtual table](vtab.md) and are used to loop through the virtual table. Cursors are created using the [xOpen](vtab.md#xopen) method of the module and are destroyed by the [xClose](vtab.md#xclose) method. Cursors are used by the [xFilter](vtab.md#xfilter), [xNext](vtab.md#xnext), [xEof](vtab.md#xeof), [xColumn](vtab.md#xcolumn), and [xRowid](vtab.md#xrowid) methods of the module. Each module implementation will define the content of a cursor structure to suit its own needs.
This superclass exists in order to define fields of the cursor that are common to all implementations.
------------------------------------------------------------------------
## A Handle To An Open BLOB
> \
> typedef struct sqlite3_blob sqlite3_blob;\
An instance of this object represents an open BLOB on which [incremental BLOB I/O](#sqlite3_blob_open) can be performed. Objects of this type are created by [sqlite3_blob_open()](#sqlite3_blob_open) and destroyed by [sqlite3_blob_close()](#sqlite3_blob_close). The [sqlite3_blob_read()](#sqlite3_blob_read) and [sqlite3_blob_write()](#sqlite3_blob_write) interfaces can be used to read or write small subsections of the BLOB. The [sqlite3_blob_bytes()](#sqlite3_blob_bytes) interface returns the size of the BLOB in bytes.
1 Constructor using this object: [sqlite3_blob_open()](#sqlite3_blob_open)
1 Destructor using this object: [sqlite3_blob_close()](#sqlite3_blob_close)
4 Methods using this object: [sqlite3_blob_bytes()](#sqlite3_blob_bytes), [sqlite3_blob_read()](#sqlite3_blob_read), [sqlite3_blob_reopen()](#sqlite3_blob_reopen), [sqlite3_blob_write()](#sqlite3_blob_write)
------------------------------------------------------------------------
## Database Connection Handle
> \
> typedef struct sqlite3 sqlite3;\
Each open SQLite database is represented by a pointer to an instance of the opaque structure named "sqlite3". It is useful to think of an sqlite3 pointer as an object. The [sqlite3_open()](#sqlite3_open), [sqlite3_open16()](#sqlite3_open), and [sqlite3_open_v2()](#sqlite3_open) interfaces are its constructors, and [sqlite3_close()](#sqlite3_close) and [sqlite3_close_v2()](#sqlite3_close) are its destructors. There are many other interfaces (such as [sqlite3_prepare_v2()](#sqlite3_prepare), [sqlite3_create_function()](#sqlite3_create_function), and [sqlite3_busy_timeout()](#sqlite3_busy_timeout) to name but three) that are methods on an sqlite3 object.
3 Constructors using this object: [sqlite3_open()](#sqlite3_open), [sqlite3_open16()](#sqlite3_open), [sqlite3_open_v2()](#sqlite3_open)
2 Destructors using this object: [sqlite3_close()](#sqlite3_close), [sqlite3_close_v2()](#sqlite3_close)
80 Methods using this object:
- [sqlite3_autovacuum_pages](#sqlite3_autovacuum_pages)
- [sqlite3_blob_open](#sqlite3_blob_open)
- [sqlite3_busy_handler](#sqlite3_busy_handler)
- [sqlite3_busy_timeout](#sqlite3_busy_timeout)
- [sqlite3_changes](#sqlite3_changes)
- [sqlite3_changes64](#sqlite3_changes)
- [sqlite3_collation_needed](#sqlite3_collation_needed)
- [sqlite3_collation_needed16](#sqlite3_collation_needed)
- [sqlite3_commit_hook](#sqlite3_commit_hook)
- [sqlite3_create_collation](#sqlite3_create_collation)
- [sqlite3_create_collation16](#sqlite3_create_collation)
- [sqlite3_create_collation_v2](#sqlite3_create_collation)
- [sqlite3_create_function](#sqlite3_create_function)
- [sqlite3_create_function16](#sqlite3_create_function)
- [sqlite3_create_function_v2](#sqlite3_create_function)
- [sqlite3_create_module](#sqlite3_create_module)
- [sqlite3_create_module_v2](#sqlite3_create_module)
- [sqlite3_create_window_function](#sqlite3_create_function)
- [sqlite3_db_cacheflush](#sqlite3_db_cacheflush)
- [sqlite3_db_config](#sqlite3_db_config)
- [sqlite3_db_filename](#sqlite3_db_filename)
- [sqlite3_db_mutex](#sqlite3_db_mutex)
- [sqlite3_db_name](#sqlite3_db_name)
- [sqlite3_db_readonly](#sqlite3_db_readonly)
- [sqlite3_db_release_memory](#sqlite3_db_release_memory)
- [sqlite3_db_status](#sqlite3_db_status)
- [sqlite3_db_status64](#sqlite3_db_status)
- [sqlite3_drop_modules](#sqlite3_drop_modules)
- [sqlite3_enable_load_extension](#sqlite3_enable_load_extension)
- [sqlite3_errcode](#sqlite3_errcode)
- [sqlite3_errmsg](#sqlite3_errcode)
- [sqlite3_errmsg16](#sqlite3_errcode)
- [sqlite3_error_offset](#sqlite3_errcode)
- [sqlite3_errstr](#sqlite3_errcode)
- [sqlite3_exec](#sqlite3_exec)
- [sqlite3_extended_errcode](#sqlite3_errcode)
- [sqlite3_extended_result_codes](#sqlite3_extended_result_codes)
- [sqlite3_file_control](#sqlite3_file_control)
- [sqlite3_free_table](#sqlite3_free_table)
- [sqlite3_get_autocommit](#sqlite3_get_autocommit)
- [sqlite3_get_clientdata](#sqlite3_get_clientdata)
- [sqlite3_get_table](#sqlite3_free_table)
- [sqlite3_interrupt](#sqlite3_interrupt)
- [sqlite3_is_interrupted](#sqlite3_interrupt)
- [sqlite3_last_insert_rowid](#sqlite3_last_insert_rowid)
- [sqlite3_limit](#sqlite3_limit)
- [sqlite3_load_extension](#sqlite3_load_extension)
- [sqlite3_next_stmt](#sqlite3_next_stmt)
- [sqlite3_overload_function](#sqlite3_overload_function)
- [sqlite3_prepare](#sqlite3_prepare)
- [sqlite3_prepare16](#sqlite3_prepare)
- [sqlite3_prepare16_v2](#sqlite3_prepare)
- [sqlite3_prepare16_v3](#sqlite3_prepare)
- [sqlite3_prepare_v2](#sqlite3_prepare)
- [sqlite3_prepare_v3](#sqlite3_prepare)
- [sqlite3_preupdate_blobwrite](#sqlite3_preupdate_blobwrite)
- [sqlite3_preupdate_count](#sqlite3_preupdate_blobwrite)
- [sqlite3_preupdate_depth](#sqlite3_preupdate_blobwrite)
- [sqlite3_preupdate_hook](#sqlite3_preupdate_blobwrite)
- [sqlite3_preupdate_new](#sqlite3_preupdate_blobwrite)
- [sqlite3_preupdate_old](#sqlite3_preupdate_blobwrite)
- [sqlite3_progress_handler](#sqlite3_progress_handler)
- [sqlite3_rollback_hook](#sqlite3_commit_hook)
- [sqlite3_set_authorizer](#sqlite3_set_authorizer)
- [sqlite3_set_clientdata](#sqlite3_get_clientdata)
- [sqlite3_set_errmsg](#sqlite3_set_errmsg)
- [sqlite3_set_last_insert_rowid](#sqlite3_set_last_insert_rowid)
- [sqlite3_setlk_timeout](#sqlite3_setlk_timeout)
- [sqlite3_system_errno](#sqlite3_system_errno)
- [sqlite3_table_column_metadata](#sqlite3_table_column_metadata)
- [sqlite3_total_changes](#sqlite3_total_changes)
- [sqlite3_total_changes64](#sqlite3_total_changes)
- [sqlite3_trace_v2](#sqlite3_trace_v2)
- [sqlite3_txn_state](#sqlite3_txn_state)
- [sqlite3_unlock_notify](#sqlite3_unlock_notify)
- [sqlite3_update_hook](#sqlite3_update_hook)
- [sqlite3_wal_autocheckpoint](#sqlite3_wal_autocheckpoint)
- [sqlite3_wal_checkpoint](#sqlite3_wal_checkpoint)
- [sqlite3_wal_checkpoint_v2](#sqlite3_wal_checkpoint_v2)
- [sqlite3_wal_hook](#sqlite3_wal_hook)
------------------------------------------------------------------------
## Dynamic String Object
> \
> typedef struct sqlite3_str sqlite3_str;\
An instance of the sqlite3_str object contains a dynamically-sized string under construction.
The lifecycle of an sqlite3_str object is as follows:
1. The sqlite3_str object is created using [sqlite3_str_new()](#sqlite3_str_new).
2. Text is appended to the sqlite3_str object using various methods, such as [sqlite3_str_appendf()](#sqlite3_str_append).
3. The sqlite3_str object is destroyed and the string it created is returned using the [sqlite3_str_finish()](#sqlite3_str_finish) interface.
1 Constructor using this object: [sqlite3_str_new()](#sqlite3_str_new)
2 Destructors using this object: [sqlite3_str_finish()](#sqlite3_str_finish), [sqlite3_str_free()](#sqlite3_str_finish)
10 Methods using this object:
- [sqlite3_str_append](#sqlite3_str_append)
- [sqlite3_str_appendall](#sqlite3_str_append)
- [sqlite3_str_appendchar](#sqlite3_str_append)
- [sqlite3_str_appendf](#sqlite3_str_append)
- [sqlite3_str_errcode](#sqlite3_str_errcode)
- [sqlite3_str_length](#sqlite3_str_errcode)
- [sqlite3_str_reset](#sqlite3_str_append)
- [sqlite3_str_truncate](#sqlite3_str_append)
- [sqlite3_str_value](#sqlite3_str_errcode)
- [sqlite3_str_vappendf](#sqlite3_str_append)
------------------------------------------------------------------------
## Application Defined Page Cache.
> \
> typedef struct sqlite3_pcache_methods2 sqlite3_pcache_methods2;\
> struct sqlite3_pcache_methods2 {\
> int iVersion;\
> void \*pArg;\
> int (\*xInit)(void\*);\
> void (\*xShutdown)(void\*);\
> sqlite3_pcache \*(\*xCreate)(int szPage, int szExtra, int bPurgeable);\
> void (\*xCachesize)(sqlite3_pcache\*, int nCachesize);\
> int (\*xPagecount)(sqlite3_pcache\*);\
> sqlite3_pcache_page \*(\*xFetch)(sqlite3_pcache\*, unsigned key, int createFlag);\
> void (\*xUnpin)(sqlite3_pcache\*, sqlite3_pcache_page\*, int discard);\
> void (\*xRekey)(sqlite3_pcache\*, sqlite3_pcache_page\*,\
> unsigned oldKey, unsigned newKey);\
> void (\*xTruncate)(sqlite3_pcache\*, unsigned iLimit);\
> void (\*xDestroy)(sqlite3_pcache\*);\
> void (\*xShrink)(sqlite3_pcache\*);\
> };\
The [sqlite3_config](#sqlite3_config)([SQLITE_CONFIG_PCACHE2](#sqliteconfigpcache2), ...) interface can register an alternative page cache implementation by passing in an instance of the sqlite3_pcache_methods2 structure. In many applications, most of the heap memory allocated by SQLite is used for the page cache. By implementing a custom page cache using this API, an application can better control the amount of memory consumed by SQLite, the way in which that memory is allocated and released, and the policies used to determine exactly which parts of a database file are cached and for how long.
The alternative page cache mechanism is an extreme measure that is only needed by the most demanding applications. The built-in page cache is recommended for most uses.
The contents of the sqlite3_pcache_methods2 structure are copied to an internal buffer by SQLite within the call to [sqlite3_config](#sqlite3_config). Hence the application may discard the parameter after the call to [sqlite3_config()](#sqlite3_config) returns.
The xInit() method is called once for each effective call to [sqlite3_initialize()](#sqlite3_initialize) (usually only once during the lifetime of the process). The xInit() method is passed a copy of the sqlite3_pcache_methods2.pArg value. The intent of the xInit() method is to set up global data structures required by the custom page cache implementation. If the xInit() method is NULL, then the built-in default page cache is used instead of the application defined page cache.
The xShutdown() method is called by [sqlite3_shutdown()](#sqlite3_initialize). It can be used to clean up any outstanding resources before process shutdown, if required. The xShutdown() method may be NULL.
SQLite automatically serializes calls to the xInit method, so the xInit method need not be threadsafe. The xShutdown method is only called from [sqlite3_shutdown()](#sqlite3_initialize) so it does not need to be threadsafe either. All other methods must be threadsafe in multithreaded applications.
SQLite will never invoke xInit() more than once without an intervening call to xShutdown().
SQLite invokes the xCreate() method to construct a new cache instance. SQLite will typically create one cache instance for each open database file, though this is not guaranteed. The first parameter, szPage, is the size in bytes of the pages that must be allocated by the cache. szPage will always be a power of two. The second parameter szExtra is a number of bytes of extra storage associated with each page cache entry. The szExtra parameter will be a number less than 250. SQLite will use the extra szExtra bytes on each page to store metadata about the underlying database page on disk. The value passed into szExtra depends on the SQLite version, the target platform, and how SQLite was compiled. The third argument to xCreate(), bPurgeable, is true if the cache being created will be used to cache database pages of a file stored on disk, or false if it is used for an in-memory database. The cache implementation does not have to do anything special based upon the value of bPurgeable; it is purely advisory. On a cache where bPurgeable is false, SQLite will never invoke xUnpin() except to deliberately delete a page. In other words, calls to xUnpin() on a cache with bPurgeable set to false will always have the "discard" flag set to true. Hence, a cache created with bPurgeable set to false will never contain any unpinned pages.
The xCachesize() method may be called at any time by SQLite to set the suggested maximum cache-size (number of pages stored) for the cache instance passed as the first argument. This is the value configured using the SQLite "[PRAGMA cache_size](pragma.md#pragma_cache_size)" command. As with the bPurgeable parameter, the implementation is not required to do anything with this value; it is advisory only.
The xPagecount() method must return the number of pages currently stored in the cache, both pinned and unpinned.
The xFetch() method locates a page in the cache and returns a pointer to an sqlite3_pcache_page object associated with that page, or a NULL pointer. The pBuf element of the returned sqlite3_pcache_page object will be a pointer to a buffer of szPage bytes used to store the content of a single database page. The pExtra element of sqlite3_pcache_page will be a pointer to the szExtra bytes of extra storage that SQLite has requested for each entry in the page cache.
The page to be fetched is determined by the key. The minimum key value is 1. After it has been retrieved using xFetch, the page is considered to be "pinned".
If the requested page is already in the page cache, then the page cache implementation must return a pointer to the page buffer with its content intact. If the requested page is not already in the cache, then the cache implementation should use the value of the createFlag parameter to help it determine what action to take:
createFlag
Behavior when page is not already in cache
0
Do not allocate a new page. Return NULL.
1
Allocate a new page if it is easy and convenient to do so. Otherwise return NULL.
2
Make every effort to allocate a new page. Only return NULL if allocating a new page is effectively impossible.
SQLite will normally invoke xFetch() with a createFlag of 0 or 1. SQLite will only use a createFlag of 2 after a prior call with a createFlag of 1 failed. In between the xFetch() calls, SQLite may attempt to unpin one or more cache pages by spilling the content of pinned pages to disk and synching the operating system disk cache.
xUnpin() is called by SQLite with a pointer to a currently pinned page as its second argument. If the third parameter, discard, is non-zero, then the page must be evicted from the cache. If the discard parameter is zero, then the page may be discarded or retained at the discretion of the page cache implementation. The page cache implementation may choose to evict unpinned pages at any time.
The cache must not perform any reference counting. A single call to xUnpin() unpins the page regardless of the number of prior calls to xFetch().
The xRekey() method is used to change the key value associated with the page passed as the second argument. If the cache previously contains an entry associated with newKey, it must be discarded. Any prior cache entry associated with newKey is guaranteed not to be pinned.
When SQLite calls the xTruncate() method, the cache must discard all existing cache entries with page numbers (keys) greater than or equal to the value of the iLimit parameter passed to xTruncate(). If any of these pages are pinned, they become implicitly unpinned, meaning that they can be safely discarded.
The xDestroy() method is used to delete a cache allocated by xCreate(). All resources associated with the specified cache should be freed. After calling the xDestroy() method, SQLite considers the [sqlite3_pcache\*](#sqlite3_pcache) handle invalid, and will not use it with any other sqlite3_pcache_methods2 functions.
SQLite invokes the xShrink() method when it wants the page cache to free up as much of heap memory as possible. The page cache implementation is not obligated to free any memory, but well-behaved implementations should do their best.
------------------------------------------------------------------------
## Prepared Statement Object
> \
> typedef struct sqlite3_stmt sqlite3_stmt;\
An instance of this object represents a single SQL statement that has been compiled into binary form and is ready to be evaluated.
Think of each SQL statement as a separate computer program. The original SQL text is source code. A prepared statement object is the compiled object code. All SQL must be converted into a prepared statement before it can be run.
The life-cycle of a prepared statement object usually goes like this:
1. Create the prepared statement object using [sqlite3_prepare_v2()](#sqlite3_prepare).
2. Bind values to [parameters](lang_expr.md#varparam) using the sqlite3_bind\_\*() interfaces.
3. Run the SQL by calling [sqlite3_step()](#sqlite3_step) one or more times.
4. Reset the prepared statement using [sqlite3_reset()](#sqlite3_reset) then go back to step 2. Do this zero or more times.
5. Destroy the object using [sqlite3_finalize()](#sqlite3_finalize).
6 Constructors using this object:
- [sqlite3_prepare](#sqlite3_prepare)
- [sqlite3_prepare16](#sqlite3_prepare)
- [sqlite3_prepare16_v2](#sqlite3_prepare)
- [sqlite3_prepare16_v3](#sqlite3_prepare)
- [sqlite3_prepare_v2](#sqlite3_prepare)
- [sqlite3_prepare_v3](#sqlite3_prepare)
1 Destructor using this object: [sqlite3_finalize()](#sqlite3_finalize)
53 Methods using this object:
- [sqlite3_bind_blob](#sqlite3_bind_blob)
- [sqlite3_bind_blob64](#sqlite3_bind_blob)
- [sqlite3_bind_double](#sqlite3_bind_blob)
- [sqlite3_bind_int](#sqlite3_bind_blob)
- [sqlite3_bind_int64](#sqlite3_bind_blob)
- [sqlite3_bind_null](#sqlite3_bind_blob)
- [sqlite3_bind_parameter_count](#sqlite3_bind_parameter_count)
- [sqlite3_bind_parameter_index](#sqlite3_bind_parameter_index)
- [sqlite3_bind_parameter_name](#sqlite3_bind_parameter_name)
- [sqlite3_bind_pointer](#sqlite3_bind_blob)
- [sqlite3_bind_text](#sqlite3_bind_blob)
- [sqlite3_bind_text16](#sqlite3_bind_blob)
- [sqlite3_bind_text64](#sqlite3_bind_blob)
- [sqlite3_bind_value](#sqlite3_bind_blob)
- [sqlite3_bind_zeroblob](#sqlite3_bind_blob)
- [sqlite3_bind_zeroblob64](#sqlite3_bind_blob)
- [sqlite3_clear_bindings](#sqlite3_clear_bindings)
- [sqlite3_column_blob](#sqlite3_column_blob)
- [sqlite3_column_bytes](#sqlite3_column_blob)
- [sqlite3_column_bytes16](#sqlite3_column_blob)
- [sqlite3_column_count](#sqlite3_column_count)
- [sqlite3_column_database_name](#sqlite3_column_database_name)
- [sqlite3_column_database_name16](#sqlite3_column_database_name)
- [sqlite3_column_decltype](#sqlite3_column_decltype)
- [sqlite3_column_decltype16](#sqlite3_column_decltype)
- [sqlite3_column_double](#sqlite3_column_blob)
- [sqlite3_column_int](#sqlite3_column_blob)
- [sqlite3_column_int64](#sqlite3_column_blob)
- [sqlite3_column_name](#sqlite3_column_name)
- [sqlite3_column_name16](#sqlite3_column_name)
- [sqlite3_column_origin_name](#sqlite3_column_database_name)
- [sqlite3_column_origin_name16](#sqlite3_column_database_name)
- [sqlite3_column_table_name](#sqlite3_column_database_name)
- [sqlite3_column_table_name16](#sqlite3_column_database_name)
- [sqlite3_column_text](#sqlite3_column_blob)
- [sqlite3_column_text16](#sqlite3_column_blob)
- [sqlite3_column_type](#sqlite3_column_blob)
- [sqlite3_column_value](#sqlite3_column_blob)
- [sqlite3_data_count](#sqlite3_data_count)
- [sqlite3_db_handle](#sqlite3_db_handle)
- [sqlite3_expanded_sql](#sqlite3_expanded_sql)
- [sqlite3_normalized_sql](#sqlite3_expanded_sql)
- [sqlite3_reset](#sqlite3_reset)
- [sqlite3_sql](#sqlite3_expanded_sql)
- [sqlite3_step](#sqlite3_step)
- [sqlite3_stmt_busy](#sqlite3_stmt_busy)
- [sqlite3_stmt_explain](#sqlite3_stmt_explain)
- [sqlite3_stmt_isexplain](#sqlite3_stmt_isexplain)
- [sqlite3_stmt_readonly](#sqlite3_stmt_readonly)
- [sqlite3_stmt_scanstatus](#sqlite3_stmt_scanstatus)
- [sqlite3_stmt_scanstatus_reset](#sqlite3_stmt_scanstatus_reset)
- [sqlite3_stmt_scanstatus_v2](#sqlite3_stmt_scanstatus)
- [sqlite3_stmt_status](#sqlite3_stmt_status)
------------------------------------------------------------------------
## Dynamically Typed Value Object
> \
> typedef struct sqlite3_value sqlite3_value;\
SQLite uses the sqlite3_value object to represent all values that can be stored in a database table. SQLite uses dynamic typing for the values it stores. Values stored in sqlite3_value objects can be integers, floating point values, strings, BLOBs, or NULL.
An sqlite3_value object may be either "protected" or "unprotected". Some interfaces require a protected sqlite3_value. Other interfaces will accept either a protected or an unprotected sqlite3_value. Every interface that accepts sqlite3_value arguments specifies whether or not it requires a protected sqlite3_value. The [sqlite3_value_dup()](#sqlite3_value_dup) interface can be used to construct a new protected sqlite3_value from an unprotected sqlite3_value.
The terms "protected" and "unprotected" refer to whether or not a mutex is held. An internal mutex is held for a protected sqlite3_value object but no mutex is held for an unprotected sqlite3_value object. If SQLite is compiled to be single-threaded (with [SQLITE_THREADSAFE=0](compile.md#threadsafe) and with [sqlite3_threadsafe()](#sqlite3_threadsafe) returning 0) or if SQLite is run in one of reduced mutex modes [SQLITE_CONFIG_SINGLETHREAD](#sqliteconfigsinglethread) or [SQLITE_CONFIG_MULTITHREAD](#sqliteconfigmultithread) then there is no distinction between protected and unprotected sqlite3_value objects and they can be used interchangeably. However, for maximum code portability it is recommended that applications still make the distinction between protected and unprotected sqlite3_value objects even when not strictly required.
The sqlite3_value objects that are passed as parameters into the implementation of [application-defined SQL functions](appfunc.md) are protected. The sqlite3_value objects returned by [sqlite3_vtab_rhs_value()](#sqlite3_vtab_rhs_value) are protected. The sqlite3_value object returned by [sqlite3_column_value()](#sqlite3_column_blob) is unprotected. Unprotected sqlite3_value objects may only be used as arguments to [sqlite3_result_value()](#sqlite3_result_blob), [sqlite3_bind_value()](#sqlite3_bind_blob), and [sqlite3_value_dup()](#sqlite3_value_dup). The [sqlite3_value_type()](#sqlite3_value_blob) family of interfaces require protected sqlite3_value objects.
19 Methods using this object:
- [sqlite3_value_blob](#sqlite3_value_blob)
- [sqlite3_value_bytes](#sqlite3_value_blob)
- [sqlite3_value_bytes16](#sqlite3_value_blob)
- [sqlite3_value_double](#sqlite3_value_blob)
- [sqlite3_value_dup](#sqlite3_value_dup)
- [sqlite3_value_encoding](#sqlite3_value_encoding)
- [sqlite3_value_free](#sqlite3_value_dup)
- [sqlite3_value_frombind](#sqlite3_value_blob)
- [sqlite3_value_int](#sqlite3_value_blob)
- [sqlite3_value_int64](#sqlite3_value_blob)
- [sqlite3_value_nochange](#sqlite3_value_blob)
- [sqlite3_value_numeric_type](#sqlite3_value_blob)
- [sqlite3_value_pointer](#sqlite3_value_blob)
- [sqlite3_value_subtype](#sqlite3_value_subtype)
- [sqlite3_value_text](#sqlite3_value_blob)
- [sqlite3_value_text16](#sqlite3_value_blob)
- [sqlite3_value_text16be](#sqlite3_value_blob)
- [sqlite3_value_text16le](#sqlite3_value_blob)
- [sqlite3_value_type](#sqlite3_value_blob)
------------------------------------------------------------------------
## Deprecated Functions
> \
> \#ifndef SQLITE_OMIT_DEPRECATED\
> int sqlite3_aggregate_count(sqlite3_context\*);\
> int sqlite3_expired(sqlite3_stmt\*);\
> int sqlite3_transfer_bindings(sqlite3_stmt\*, sqlite3_stmt\*);\
> int sqlite3_global_recover(void);\
> void sqlite3_thread_cleanup(void);\
> int sqlite3_memory_alarm(void(\*)(void\*,sqlite3_int64,int),\
> void\*,sqlite3_int64);\
> \#endif\
These functions are [deprecated](capi3ref.md). In order to maintain backwards compatibility with older code, these functions continue to be supported. However, new applications should avoid the use of these functions. To encourage programmers to avoid these functions, we will not explain what they do.
------------------------------------------------------------------------
## Online Backup API.
> \
> sqlite3_backup \*sqlite3_backup_init(\
> sqlite3 \*pDest, /\* Destination database handle \*/\
> const char \*zDestName, /\* Destination database name \*/\
> sqlite3 \*pSource, /\* Source database handle \*/\
> const char \*zSourceName /\* Source database name \*/\
> );\
> int sqlite3_backup_step(sqlite3_backup \*p, int nPage);\
> int sqlite3_backup_finish(sqlite3_backup \*p);\
> int sqlite3_backup_remaining(sqlite3_backup \*p);\
> int sqlite3_backup_pagecount(sqlite3_backup \*p);\
The backup API copies the content of one database into another. It is useful either for creating backups of databases or for copying in-memory databases to or from persistent files.
See Also: [Using the SQLite Online Backup API](backup.md)
SQLite holds a write transaction open on the destination database file for the duration of the backup operation. The source database is read-locked only while it is being read; it is not locked continuously for the entire backup operation. Thus, the backup may be performed on a live source database without preventing other database connections from reading or writing to the source database while the backup is underway.
To perform a backup operation:
1. **sqlite3_backup_init()** is called once to initialize the backup,
2. **sqlite3_backup_step()** is called one or more times to transfer the data between the two databases, and finally
3. **sqlite3_backup_finish()** is called to release all resources associated with the backup operation.
There should be exactly one call to sqlite3_backup_finish() for each successful call to sqlite3_backup_init().
**sqlite3_backup_init()**
The D and N arguments to sqlite3_backup_init(D,N,S,M) are the [database connection](#sqlite3) associated with the destination database and the database name, respectively. The database name is "main" for the main database, "temp" for the temporary database, or the name specified after the AS keyword in an [ATTACH](lang_attach.md) statement for an attached database. The S and M arguments passed to sqlite3_backup_init(D,N,S,M) identify the [database connection](#sqlite3) and database name of the source database, respectively. The source and destination [database connections](#sqlite3) (parameters S and D) must be different or else sqlite3_backup_init(D,N,S,M) will fail with an error.
A call to sqlite3_backup_init() will fail, returning NULL, if there is already a read or read-write transaction open on the destination database.
If an error occurs within sqlite3_backup_init(D,N,S,M), then NULL is returned and an error code and error message are stored in the destination [database connection](#sqlite3) D. The error code and message for the failed call to sqlite3_backup_init() can be retrieved using the [sqlite3_errcode()](#sqlite3_errcode), [sqlite3_errmsg()](#sqlite3_errcode), and/or [sqlite3_errmsg16()](#sqlite3_errcode) functions. A successful call to sqlite3_backup_init() returns a pointer to an [sqlite3_backup](#sqlite3_backup) object. The [sqlite3_backup](#sqlite3_backup) object may be used with the sqlite3_backup_step() and sqlite3_backup_finish() functions to perform the specified backup operation.
**sqlite3_backup_step()**
Function sqlite3_backup_step(B,N) will copy up to N pages between the source and destination databases specified by [sqlite3_backup](#sqlite3_backup) object B. If N is negative, all remaining source pages are copied. If sqlite3_backup_step(B,N) successfully copies N pages and there are still more pages to be copied, then the function returns [SQLITE_OK](#SQLITE_ABORT). If sqlite3_backup_step(B,N) successfully finishes copying all pages from source to destination, then it returns [SQLITE_DONE](#SQLITE_ABORT). If an error occurs while running sqlite3_backup_step(B,N), then an [error code](rescode.md) is returned. As well as [SQLITE_OK](#SQLITE_ABORT) and [SQLITE_DONE](#SQLITE_ABORT), a call to sqlite3_backup_step() may return [SQLITE_READONLY](#SQLITE_ABORT), [SQLITE_NOMEM](#SQLITE_ABORT), [SQLITE_BUSY](#SQLITE_ABORT), [SQLITE_LOCKED](#SQLITE_ABORT), or an [SQLITE_IOERR_XXX](#SQLITE_ABORT_ROLLBACK) extended error code.
The sqlite3_backup_step() might return [SQLITE_READONLY](#SQLITE_ABORT) if
1. the destination database was opened read-only, or
2. the destination database is using write-ahead-log journaling and the destination and source page sizes differ, or
3. the destination database is an in-memory database and the destination and source page sizes differ.
If sqlite3_backup_step() cannot obtain a required file-system lock, then the [busy-handler function](#sqlite3_busy_handler) is invoked (if one is specified). If the busy-handler returns non-zero before the lock is available, then [SQLITE_BUSY](#SQLITE_ABORT) is returned to the caller. In this case the call to sqlite3_backup_step() can be retried later. If the source [database connection](#sqlite3) is being used to write to the source database when sqlite3_backup_step() is called, then [SQLITE_LOCKED](#SQLITE_ABORT) is returned immediately. Again, in this case the call to sqlite3_backup_step() can be retried later on. If [SQLITE_IOERR_XXX](#SQLITE_ABORT_ROLLBACK), [SQLITE_NOMEM](#SQLITE_ABORT), or [SQLITE_READONLY](#SQLITE_ABORT) is returned, then there is no point in retrying the call to sqlite3_backup_step(). These errors are considered fatal. The application must accept that the backup operation has failed and pass the backup operation handle to the sqlite3_backup_finish() to release associated resources.
The first call to sqlite3_backup_step() obtains an exclusive lock on the destination file. The exclusive lock is not released until either sqlite3_backup_finish() is called or the backup operation is complete and sqlite3_backup_step() returns [SQLITE_DONE](#SQLITE_ABORT). Every call to sqlite3_backup_step() obtains a [shared lock](lockingv3.md#shared_lock) on the source database that lasts for the duration of the sqlite3_backup_step() call. Because the source database is not locked between calls to sqlite3_backup_step(), the source database may be modified mid-way through the backup process. If the source database is modified by an external process or via a database connection other than the one being used by the backup operation, then the backup will be automatically restarted by the next call to sqlite3_backup_step(). If the source database is modified by using the same database connection as is used by the backup operation, then the backup database is automatically updated at the same time.
**sqlite3_backup_finish()**
When sqlite3_backup_step() has returned [SQLITE_DONE](#SQLITE_ABORT), or when the application wishes to abandon the backup operation, the application should destroy the [sqlite3_backup](#sqlite3_backup) by passing it to sqlite3_backup_finish(). The sqlite3_backup_finish() interfaces releases all resources associated with the [sqlite3_backup](#sqlite3_backup) object. If sqlite3_backup_step() has not yet returned [SQLITE_DONE](#SQLITE_ABORT), then any active write-transaction on the destination database is rolled back. The [sqlite3_backup](#sqlite3_backup) object is invalid and may not be used following a call to sqlite3_backup_finish().
The value returned by sqlite3_backup_finish is [SQLITE_OK](#SQLITE_ABORT) if no sqlite3_backup_step() errors occurred, regardless of whether or not sqlite3_backup_step() completed. If an out-of-memory condition or IO error occurred during any prior sqlite3_backup_step() call on the same [sqlite3_backup](#sqlite3_backup) object, then sqlite3_backup_finish() returns the corresponding [error code](rescode.md).
A return of [SQLITE_BUSY](#SQLITE_ABORT) or [SQLITE_LOCKED](#SQLITE_ABORT) from sqlite3_backup_step() is not a permanent error and does not affect the return value of sqlite3_backup_finish().
**sqlite3_backup_remaining() and sqlite3_backup_pagecount()**
The sqlite3_backup_remaining() routine returns the number of pages still to be backed up at the conclusion of the most recent sqlite3_backup_step(). The sqlite3_backup_pagecount() routine returns the total number of pages in the source database at the conclusion of the most recent sqlite3_backup_step(). The values returned by these functions are only updated by sqlite3_backup_step(). If the source database is modified in a way that changes the size of the source database or the number of pages remaining, those changes are not reflected in the output of sqlite3_backup_pagecount() and sqlite3_backup_remaining() until after the next sqlite3_backup_step().
**Concurrent Usage of Database Handles**
The source [database connection](#sqlite3) may be used by the application for other purposes while a backup operation is underway or being initialized. If SQLite is compiled and configured to support threadsafe database connections, then the source database connection may be used concurrently from within other threads.
However, the application must guarantee that the destination [database connection](#sqlite3) is not passed to any other API (by any thread) after sqlite3_backup_init() is called and before the corresponding call to sqlite3_backup_finish(). SQLite does not currently check to see if the application incorrectly accesses the destination [database connection](#sqlite3) and so no error code is reported, but the operations may malfunction nevertheless. Use of the destination database connection while a backup is in progress might also cause a mutex deadlock.
If running in [shared cache mode](sharedcache.md), the application must guarantee that the shared cache used by the destination database is not accessed while the backup is running. In practice this means that the application must guarantee that the disk file being backed up to is not accessed by any connection within the process, not just the specific connection that was passed to sqlite3_backup_init().
The [sqlite3_backup](#sqlite3_backup) object itself is partially threadsafe. Multiple threads may safely make multiple concurrent calls to sqlite3_backup_step(). However, the sqlite3_backup_remaining() and sqlite3_backup_pagecount() APIs are not strictly speaking threadsafe. If they are invoked at the same time as another thread is invoking sqlite3_backup_step() it is possible that they return invalid values.
**Alternatives To Using The Backup API**
Other techniques for safely creating a consistent backup of an SQLite database include:
- The [VACUUM INTO](lang_vacuum.md#vacuuminto) command.
- The [sqlite3_rsync](rsync.md) utility program.
------------------------------------------------------------------------
## Bind array values to the CARRAY table-valued function
> \
> int sqlite3_carray_bind_v2(\
> sqlite3_stmt \*pStmt, /\* Statement to be bound \*/\
> int i, /\* Parameter index \*/\
> void \*aData, /\* Pointer to array data \*/\
> int nData, /\* Number of data elements \*/\
> int mFlags, /\* CARRAY flags \*/\
> void (\*xDel)(void\*), /\* Destructor for aData \*/\
> void \*pDel /\* Optional argument to xDel() \*/\
> );\
> int sqlite3_carray_bind(\
> sqlite3_stmt \*pStmt, /\* Statement to be bound \*/\
> int i, /\* Parameter index \*/\
> void \*aData, /\* Pointer to array data \*/\
> int nData, /\* Number of data elements \*/\
> int mFlags, /\* CARRAY flags \*/\
> void (\*xDel)(void\*) /\* Destructor for aData \*/\
> );\
The sqlite3_carray_bind_v2(S,I,P,N,F,X,D) interface binds an array value to parameter that is the first argument of the [carray() table-valued function](carray.md). The S parameter is a pointer to the [prepared statement](#sqlite3_stmt) that uses the carray() functions. I is the parameter index to be bound. I must be the index of the parameter that is the first argument to the carray() table-valued function. P is a pointer to the array to be bound, and N is the number of elements in the array. The F argument is one of constants [SQLITE_CARRAY_INT32](#SQLITE_CARRAY_BLOB), [SQLITE_CARRAY_INT64](#SQLITE_CARRAY_BLOB), [SQLITE_CARRAY_DOUBLE](#SQLITE_CARRAY_BLOB), [SQLITE_CARRAY_TEXT](#SQLITE_CARRAY_BLOB), or [SQLITE_CARRAY_BLOB](#SQLITE_CARRAY_BLOB) to indicate the datatype of the array P.
If the X argument is not a NULL pointer or one of the special values [SQLITE_STATIC](#SQLITE_STATIC) or [SQLITE_TRANSIENT](#SQLITE_STATIC), then SQLite will invoke the function X with argument D when it is finished using the data in P. The call to X(D) is a destructor for the array P. The destructor X(D) is invoked even if the call to sqlite3_carray_bind_v2() fails. If the X parameter is the special-case value [SQLITE_STATIC](#SQLITE_STATIC), then SQLite assumes that the data static and the destructor is never invoked. If the X parameter is the special-case value [SQLITE_TRANSIENT](#SQLITE_STATIC), then sqlite3_carray_bind_v2() makes its own private copy of the data prior to returning and never invokes the destructor X.
The sqlite3_carray_bind() function works the same as sqlite3_carray_bind_v2() with a D parameter set to P. In other words, sqlite3_carray_bind(S,I,P,N,F,X) is same as sqlite3_carray_bind_v2(S,I,P,N,F,X,P).
------------------------------------------------------------------------
## Count The Number Of Rows Modified
> \
> int sqlite3_changes(sqlite3\*);\
> sqlite3_int64 sqlite3_changes64(sqlite3\*);\
These functions return the number of rows modified, inserted or deleted by the most recently completed INSERT, UPDATE or DELETE statement on the database connection specified by the only parameter. The two functions are identical except for the type of the return value and that if the number of rows modified by the most recent INSERT, UPDATE, or DELETE is greater than the maximum value supported by type "int", then the return value of sqlite3_changes() is undefined. Executing any other type of SQL statement does not modify the value returned by these functions. For the purposes of this interface, a CREATE TABLE AS SELECT statement does not count as an INSERT, UPDATE or DELETE statement and hence the rows added to the new table by the CREATE TABLE AS SELECT statement are not counted.
Only changes made directly by the INSERT, UPDATE or DELETE statement are considered - auxiliary changes caused by [triggers](lang_createtrigger.md), [foreign key actions](foreignkeys.md#fk_actions) or [REPLACE](lang_replace.md) constraint resolution are not counted.
Changes to a view that are intercepted by [INSTEAD OF triggers](lang_createtrigger.md#instead_of_trigger) are not counted. The value returned by sqlite3_changes() immediately after an INSERT, UPDATE or DELETE statement run on a view is always zero. Only changes made to real tables are counted.
Things are more complicated if the sqlite3_changes() function is executed while a trigger program is running. This may happen if the program uses the [changes() SQL function](lang_corefunc.md#changes), or if some other callback function invokes sqlite3_changes() directly. Essentially:
- Before entering a trigger program the value returned by sqlite3_changes() function is saved. After the trigger program has finished, the original value is restored.
- Within a trigger program each INSERT, UPDATE and DELETE statement sets the value returned by sqlite3_changes() upon completion as normal. Of course, this value will not include any changes performed by sub-triggers, as the sqlite3_changes() value will be saved and restored after each sub-trigger has run.
This means that if the changes() SQL function (or similar) is used by the first INSERT, UPDATE or DELETE statement within a trigger, it returns the value as set when the calling statement began executing. If it is used by the second or subsequent such statement within a trigger program, the value returned reflects the number of rows modified by the previous INSERT, UPDATE or DELETE statement within the same trigger.
If a separate thread makes changes on the same database connection while [sqlite3_changes()](#sqlite3_changes) is running then the value returned is unpredictable and not meaningful.
See also:
- the [sqlite3_total_changes()](#sqlite3_total_changes) interface
- the [count_changes pragma](pragma.md#pragma_count_changes)
- the [changes() SQL function](lang_corefunc.md#changes)
- the [data_version pragma](pragma.md#pragma_data_version)
------------------------------------------------------------------------
## Closing A Database Connection
> \
> int sqlite3_close(sqlite3\*);\
> int sqlite3_close_v2(sqlite3\*);\
The sqlite3_close() and sqlite3_close_v2() routines are destructors for the [sqlite3](#sqlite3) object. Calls to sqlite3_close() and sqlite3_close_v2() return [SQLITE_OK](#SQLITE_ABORT) if the [sqlite3](#sqlite3) object is successfully destroyed and all associated resources are deallocated.
Ideally, applications should [finalize](#sqlite3_finalize) all [prepared statements](#sqlite3_stmt), [close](#sqlite3_blob_close) all [BLOB handles](#sqlite3_blob), and [finish](#sqlite3backupfinish) all [sqlite3_backup](#sqlite3_backup) objects associated with the [sqlite3](#sqlite3) object prior to attempting to close the object. If the database connection is associated with unfinalized prepared statements, BLOB handlers, and/or unfinished sqlite3_backup objects then sqlite3_close() will leave the database connection open and return [SQLITE_BUSY](#SQLITE_ABORT). If sqlite3_close_v2() is called with unfinalized prepared statements, unclosed BLOB handlers, and/or unfinished sqlite3_backups, it returns [SQLITE_OK](#SQLITE_ABORT) regardless, but instead of deallocating the database connection immediately, it marks the database connection as an unusable "zombie" and makes arrangements to automatically deallocate the database connection after all prepared statements are finalized, all BLOB handles are closed, and all backups have finished. The sqlite3_close_v2() interface is intended for use with host languages that are garbage collected, and where the order in which destructors are called is arbitrary.
If an [sqlite3](#sqlite3) object is destroyed while a transaction is open, the transaction is automatically rolled back.
The C parameter to [sqlite3_close(C)](#sqlite3_close) and [sqlite3_close_v2(C)](#sqlite3_close) must be either a NULL pointer or an [sqlite3](#sqlite3) object pointer obtained from [sqlite3_open()](#sqlite3_open), [sqlite3_open16()](#sqlite3_open), or [sqlite3_open_v2()](#sqlite3_open), and not previously closed. Calling sqlite3_close() or sqlite3_close_v2() with a NULL pointer argument is a harmless no-op.
------------------------------------------------------------------------
## Collation Needed Callbacks
> \
> int sqlite3_collation_needed(\
> sqlite3\*,\
> void\*,\
> void(\*)(void\*,sqlite3\*,int eTextRep,const char\*)\
> );\
> int sqlite3_collation_needed16(\
> sqlite3\*,\
> void\*,\
> void(\*)(void\*,sqlite3\*,int eTextRep,const void\*)\
> );\
To avoid having to register all collation sequences before a database can be used, a single callback function may be registered with the [database connection](#sqlite3) to be invoked whenever an undefined collation sequence is required.
If the function is registered using the sqlite3_collation_needed() API, then it is passed the names of undefined collation sequences as strings encoded in UTF-8. If sqlite3_collation_needed16() is used, the names are passed as UTF-16 in machine native byte order. A call to either function replaces the existing collation-needed callback.
When the callback is invoked, the first argument passed is a copy of the second argument to sqlite3_collation_needed() or sqlite3_collation_needed16(). The second argument is the database connection. The third argument is one of [SQLITE_UTF8](#sqliteutf8), [SQLITE_UTF16BE](#sqliteutf16be), or [SQLITE_UTF16LE](#sqliteutf16le), indicating the most desirable form of the collation sequence function required. The fourth parameter is the name of the required collation sequence.
The callback function should register the desired collation using [sqlite3_create_collation()](#sqlite3_create_collation), [sqlite3_create_collation16()](#sqlite3_create_collation), or [sqlite3_create_collation_v2()](#sqlite3_create_collation).
------------------------------------------------------------------------
## Source Of Data In A Query Result
> \
> const char \*sqlite3_column_database_name(sqlite3_stmt\*,int);\
> const void \*sqlite3_column_database_name16(sqlite3_stmt\*,int);\
> const char \*sqlite3_column_table_name(sqlite3_stmt\*,int);\
> const void \*sqlite3_column_table_name16(sqlite3_stmt\*,int);\
> const char \*sqlite3_column_origin_name(sqlite3_stmt\*,int);\
> const void \*sqlite3_column_origin_name16(sqlite3_stmt\*,int);\
These routines provide a means to determine the database, table, and table column that is the origin of a particular result column in a [SELECT](lang_select.md) statement. The name of the database or table or column can be returned as either a UTF-8 or UTF-16 string. The \_database\_ routines return the database name, the \_table\_ routines return the table name, and the origin\_ routines return the column name. The returned string is valid until the [prepared statement](#sqlite3_stmt) is destroyed using [sqlite3_finalize()](#sqlite3_finalize) or until the statement is automatically reprepared by the first call to [sqlite3_step()](#sqlite3_step) for a particular run or until the same information is requested again in a different encoding.
The names returned are the original un-aliased names of the database, table, and column.
The first argument to these interfaces is a [prepared statement](#sqlite3_stmt). These functions return information about the Nth result column returned by the statement, where N is the second function argument. The left-most column is column 0 for these routines.
If the Nth column returned by the statement is an expression or subquery and is not a column value, then all of these functions return NULL. These routines might also return NULL if a memory allocation error occurs. Otherwise, they return the name of the attached database, table, or column that query result column was extracted from.
As with all other SQLite APIs, those whose names end with "16" return UTF-16 encoded strings and the other functions return UTF-8.
These APIs are only available if the library was compiled with the [SQLITE_ENABLE_COLUMN_METADATA](compile.md#enable_column_metadata) C-preprocessor symbol.
If two or more threads call one or more [column metadata interfaces](#sqlite3_column_database_name) for the same [prepared statement](#sqlite3_stmt) and result column at the same time then the results are undefined.
------------------------------------------------------------------------
## Declared Datatype Of A Query Result
> \
> const char \*sqlite3_column_decltype(sqlite3_stmt\*,int);\
> const void \*sqlite3_column_decltype16(sqlite3_stmt\*,int);\
The first parameter is a [prepared statement](#sqlite3_stmt). If this statement is a [SELECT](lang_select.md) statement and the Nth column of the returned result set of that [SELECT](lang_select.md) is a table column (not an expression or subquery) then the declared type of the table column is returned. If the Nth column of the result set is an expression or subquery, then a NULL pointer is returned. The returned string is always UTF-8 encoded.
For example, given the database schema:
CREATE TABLE t1(c1 VARIANT);
and the following statement to be compiled:
SELECT c1 + 1, c1 FROM t1;
this routine would return the string "VARIANT" for the second result column (i==1), and a NULL pointer for the first result column (i==0).
SQLite uses dynamic run-time typing. So just because a column is declared to contain a particular type does not mean that the data stored in that column is of the declared type. SQLite is strongly typed, but the typing is dynamic not static. Type is associated with individual values, not with the containers used to hold those values.
------------------------------------------------------------------------
## Column Names In A Result Set
> \
> const char \*sqlite3_column_name(sqlite3_stmt\*, int N);\
> const void \*sqlite3_column_name16(sqlite3_stmt\*, int N);\
These routines return the name assigned to a particular column in the result set of a [SELECT](lang_select.md) statement. The sqlite3_column_name() interface returns a pointer to a zero-terminated UTF-8 string and sqlite3_column_name16() returns a pointer to a zero-terminated UTF-16 string. The first parameter is the [prepared statement](#sqlite3_stmt) that implements the [SELECT](lang_select.md) statement. The second parameter is the column number. The leftmost column is number 0.
The returned string pointer is valid until either the [prepared statement](#sqlite3_stmt) is destroyed by [sqlite3_finalize()](#sqlite3_finalize) or until the statement is automatically reprepared by the first call to [sqlite3_step()](#sqlite3_step) for a particular run or until the next call to sqlite3_column_name() or sqlite3_column_name16() on the same column.
If sqlite3_malloc() fails during the processing of either routine (for example during a conversion from UTF-8 to UTF-16) then a NULL pointer is returned.
The name of a result column is the value of the "AS" clause for that column, if there is an AS clause. If there is no AS clause then the name of the column is unspecified and may change from one release of SQLite to the next.
------------------------------------------------------------------------
## Commit And Rollback Notification Callbacks
> \
> void \*sqlite3_commit_hook(sqlite3\*, int(\*)(void\*), void\*);\
> void \*sqlite3_rollback_hook(sqlite3\*, void(\*)(void \*), void\*);\
The sqlite3_commit_hook() interface registers a callback function to be invoked whenever a transaction is [committed](lang_transaction.md). Any callback set by a previous call to sqlite3_commit_hook() for the same database connection is overridden. The sqlite3_rollback_hook() interface registers a callback function to be invoked whenever a transaction is [rolled back](lang_transaction.md). Any callback set by a previous call to sqlite3_rollback_hook() for the same database connection is overridden. The pArg argument is passed through to the callback. If the callback on a commit hook function returns non-zero, then the commit is converted into a rollback.
The sqlite3_commit_hook(D,C,P) and sqlite3_rollback_hook(D,C,P) functions return the P argument from the previous call of the same function on the same [database connection](#sqlite3) D, or NULL for the first call for each function on D.
The commit and rollback hook callbacks are not reentrant. The callback implementation must not do anything that will modify the database connection that invoked the callback. Any actions to modify the database connection must be deferred until after the completion of the [sqlite3_step()](#sqlite3_step) call that triggered the commit or rollback hook in the first place. Note that running any other SQL statements, including SELECT statements, or merely calling [sqlite3_prepare_v2()](#sqlite3_prepare) and [sqlite3_step()](#sqlite3_step) will modify the database connections for the meaning of "modify" in this paragraph.
Registering a NULL function disables the callback.
When the commit hook callback routine returns zero, the [COMMIT](lang_transaction.md) operation is allowed to continue normally. If the commit hook returns non-zero, then the [COMMIT](lang_transaction.md) is converted into a [ROLLBACK](lang_transaction.md). The rollback hook is invoked on a rollback that results from a commit hook returning non-zero, just as it would be with any other rollback.
For the purposes of this API, a transaction is said to have been rolled back if an explicit "ROLLBACK" statement is executed, or an error or constraint causes an implicit rollback to occur. The rollback callback is not invoked if a transaction is automatically rolled back because the database connection is closed.
See also the [sqlite3_update_hook()](#sqlite3_update_hook) interface.
------------------------------------------------------------------------
## Run-Time Library Compilation Options Diagnostics
> \
> \#ifndef SQLITE_OMIT_COMPILEOPTION_DIAGS\
> int sqlite3_compileoption_used(const char \*zOptName);\
> const char \*sqlite3_compileoption_get(int N);\
> \#else\
> \# define sqlite3_compileoption_used(X) 0\
> \# define sqlite3_compileoption_get(X) ((void\*)0)\
> \#endif\
The sqlite3_compileoption_used() function returns 0 or 1 indicating whether the specified option was defined at compile time. The SQLITE\_ prefix may be omitted from the option name passed to sqlite3_compileoption_used().
The sqlite3_compileoption_get() function allows iterating over the list of options that were defined at compile time by returning the N-th compile time option string. If N is out of range, sqlite3_compileoption_get() returns a NULL pointer. The SQLITE\_ prefix is omitted from any strings returned by sqlite3_compileoption_get().
Support for the diagnostic functions sqlite3_compileoption_used() and sqlite3_compileoption_get() may be omitted by specifying the [SQLITE_OMIT_COMPILEOPTION_DIAGS](compile.md#omit_compileoption_diags) option at compile time.
See also: SQL functions [sqlite_compileoption_used()](lang_corefunc.md#sqlite_compileoption_used) and [sqlite_compileoption_get()](lang_corefunc.md#sqlite_compileoption_get) and the [compile_options pragma](pragma.md#pragma_compile_options).
------------------------------------------------------------------------
## Determine If An SQL Statement Is Complete
> \
> int sqlite3_complete(const char \*sql);\
> int sqlite3_complete16(const void \*sql);\
These routines are useful during command-line input to determine if the currently entered text seems to form a complete SQL statement or if additional input is needed before sending the text into SQLite for parsing. These routines return 1 if the input string appears to be a complete SQL statement. A statement is judged to be complete if it ends with a semicolon token and is not a prefix of a well-formed CREATE TRIGGER statement. Semicolons that are embedded within string literals or quoted identifier names or comments are not independent tokens (they are part of the token in which they are embedded) and thus do not count as a statement terminator. Whitespace and comments that follow the final semicolon are ignored.
These routines return 0 if the statement is incomplete. If a memory allocation fails, then SQLITE_NOMEM is returned.
These routines do not parse the SQL statements and thus will not detect syntactically incorrect SQL.
If SQLite has not been initialized using [sqlite3_initialize()](#sqlite3_initialize) prior to invoking sqlite3_complete16() then sqlite3_initialize() is invoked automatically by sqlite3_complete16(). If that initialization fails, then the return value from sqlite3_complete16() will be non-zero regardless of whether or not the input SQL is complete.
The input to [sqlite3_complete()](#sqlite3_complete) must be a zero-terminated UTF-8 string.
The input to [sqlite3_complete16()](#sqlite3_complete) must be a zero-terminated UTF-16 string in native byte order.
------------------------------------------------------------------------
## Define New Collating Sequences
> \
> int sqlite3_create_collation(\
> sqlite3\*,\
> const char \*zName,\
> int eTextRep,\
> void \*pArg,\
> int(\*xCompare)(void\*,int,const void\*,int,const void\*)\
> );\
> int sqlite3_create_collation_v2(\
> sqlite3\*,\
> const char \*zName,\
> int eTextRep,\
> void \*pArg,\
> int(\*xCompare)(void\*,int,const void\*,int,const void\*),\
> void(\*xDestroy)(void\*)\
> );\
> int sqlite3_create_collation16(\
> sqlite3\*,\
> const void \*zName,\
> int eTextRep,\
> void \*pArg,\
> int(\*xCompare)(void\*,int,const void\*,int,const void\*)\
> );\
These functions add, remove, or modify a [collation](datatype3.md#collation) associated with the [database connection](#sqlite3) specified as the first argument.
The name of the collation is a UTF-8 string for sqlite3_create_collation() and sqlite3_create_collation_v2() and a UTF-16 string in native byte order for sqlite3_create_collation16(). Collation names that compare equal according to [sqlite3_strnicmp()](#sqlite3_stricmp) are considered to be the same name.
The third argument (eTextRep) must be one of the constants:
- [SQLITE_UTF8](#sqliteutf8),
- [SQLITE_UTF16LE](#sqliteutf16le),
- [SQLITE_UTF16BE](#sqliteutf16be),
- [SQLITE_UTF16](#sqliteutf16), or
- [SQLITE_UTF16_ALIGNED](#sqliteutf16aligned).
The eTextRep argument determines the encoding of strings passed to the collating function callback, xCompare. The [SQLITE_UTF16](#sqliteutf16) and [SQLITE_UTF16_ALIGNED](#sqliteutf16aligned) values for eTextRep force strings to be UTF16 with native byte order. The [SQLITE_UTF16_ALIGNED](#sqliteutf16aligned) value for eTextRep forces strings to begin on an even byte address.
The fourth argument, pArg, is an application data pointer that is passed through as the first argument to the collating function callback.
The fifth argument, xCompare, is a pointer to the collating function. Multiple collating functions can be registered using the same name but with different eTextRep parameters and SQLite will use whichever function requires the least amount of data transformation. If the xCompare argument is NULL then the collating function is deleted. When all collating functions having the same name are deleted, that collation is no longer usable.
The collating function callback is invoked with a copy of the pArg application data pointer and with two strings in the encoding specified by the eTextRep argument. The two integer parameters to the collating function callback are the length of the two strings, in bytes. The collating function must return an integer that is negative, zero, or positive if the first string is less than, equal to, or greater than the second, respectively. A collating function must always return the same answer given the same inputs. If two or more collating functions are registered to the same collation name (using different eTextRep values) then all must give an equivalent answer when invoked with equivalent strings. The collating function must obey the following properties for all strings A, B, and C:
1. If A==B then B==A.
2. If A==B and B==C then A==C.
3. If A\A.
4. If A\not called if the sqlite3_create_collation_v2() function fails. Applications that invoke sqlite3_create_collation_v2() with a non-NULL xDestroy argument should check the return code and dispose of the application data pointer themselves rather than expecting SQLite to deal with it for them. This is different from every other SQLite interface. The inconsistency is unfortunate but cannot be changed without breaking backwards compatibility.
See also: [sqlite3_collation_needed()](#sqlite3_collation_needed) and [sqlite3_collation_needed16()](#sqlite3_collation_needed).
------------------------------------------------------------------------
## Create and Destroy VFS Filenames
> \
> sqlite3_filename sqlite3_create_filename(\
> const char \*zDatabase,\
> const char \*zJournal,\
> const char \*zWal,\
> int nParam,\
> const char \*\*azParam\
> );\
> void sqlite3_free_filename(sqlite3_filename);\
These interfaces are provided for use by [VFS shim](vfs.md#shim) implementations and are not useful outside of that context.
The sqlite3_create_filename(D,J,W,N,P) allocates memory to hold a version of database filename D with corresponding journal file J and WAL file W and an array P of N URI Key/Value pairs. The result from sqlite3_create_filename(D,J,W,N,P) is a pointer to a database filename that is safe to pass to routines like:
- [sqlite3_uri_parameter()](#sqlite3_uri_boolean),
- [sqlite3_uri_boolean()](#sqlite3_uri_boolean),
- [sqlite3_uri_int64()](#sqlite3_uri_boolean),
- [sqlite3_uri_key()](#sqlite3_uri_boolean),
- [sqlite3_filename_database()](#sqlite3_filename_database),
- [sqlite3_filename_journal()](#sqlite3_filename_database), or
- [sqlite3_filename_wal()](#sqlite3_filename_database).
If a memory allocation error occurs, sqlite3_create_filename() might return a NULL pointer. The memory obtained from sqlite3_create_filename(X) must be released by a corresponding call to sqlite3_free_filename(Y).
The P parameter in sqlite3_create_filename(D,J,W,N,P) should be an array of 2\*N pointers to strings. Each pair of pointers in this array corresponds to a key and value for a query parameter. The P parameter may be a NULL pointer if N is zero. None of the 2\*N pointers in the P array may be NULL pointers and key pointers should not be empty strings. None of the D, J, or W parameters to sqlite3_create_filename(D,J,W,N,P) may be NULL pointers, though they can be empty strings.
The sqlite3_free_filename(Y) routine releases a memory allocation previously obtained from sqlite3_create_filename(). Invoking sqlite3_free_filename(Y) where Y is a NULL pointer is a harmless no-op.
If the Y parameter to sqlite3_free_filename(Y) is anything other than a NULL pointer or a pointer previously acquired from sqlite3_create_filename(), then bad things such as heap corruption or segfaults may occur. The value Y should not be used again after sqlite3_free_filename(Y) has been called. This means that if the [sqlite3_vfs.xOpen()](#sqlite3vfsxopen) method of a VFS has been called using Y, then the corresponding \[sqlite3_module.xClose() method should also be invoked prior to calling sqlite3_free_filename(Y).
------------------------------------------------------------------------
## Register A Virtual Table Implementation
> \
> int sqlite3_create_module(\
> sqlite3 \*db, /\* SQLite connection to register module with \*/\
> const char \*zName, /\* Name of the module \*/\
> const sqlite3_module \*p, /\* Methods for the module \*/\
> void \*pClientData /\* Client data for xCreate/xConnect \*/\
> );\
> int sqlite3_create_module_v2(\
> sqlite3 \*db, /\* SQLite connection to register module with \*/\
> const char \*zName, /\* Name of the module \*/\
> const sqlite3_module \*p, /\* Methods for the module \*/\
> void \*pClientData, /\* Client data for xCreate/xConnect \*/\
> void(\*xDestroy)(void\*) /\* Module destructor function \*/\
> );\
These routines are used to register a new [virtual table module](#sqlite3_module) name. Module names must be registered before creating a new [virtual table](vtab.md) using the module and before using a preexisting [virtual table](vtab.md) for the module.
The module name is registered on the [database connection](#sqlite3) specified by the first parameter. The name of the module is given by the second parameter. The third parameter is a pointer to the implementation of the [virtual table module](#sqlite3_module). The fourth parameter is an arbitrary client data pointer that is passed through into the [xCreate](vtab.md#xcreate) and [xConnect](vtab.md#xconnect) methods of the virtual table module when a new virtual table is being created or reinitialized.
The sqlite3_create_module_v2() interface has a fifth parameter which is a pointer to a destructor for the pClientData. SQLite will invoke the destructor function (if it is not NULL) when SQLite no longer needs the pClientData pointer. The destructor will also be invoked if the call to sqlite3_create_module_v2() fails. The sqlite3_create_module() interface is equivalent to sqlite3_create_module_v2() with a NULL destructor.
If the third parameter (the pointer to the sqlite3_module object) is NULL then no new module is created and any existing modules with the same name are dropped.
See also: [sqlite3_drop_modules()](#sqlite3_drop_modules)
------------------------------------------------------------------------
## Database Connection Status
> \
> int sqlite3_db_status(sqlite3\*, int op, int \*pCur, int \*pHiwtr, int resetFlg);\
> int sqlite3_db_status64(sqlite3\*,int,sqlite3_int64\*,sqlite3_int64\*,int);\
This interface is used to retrieve runtime status information about a single [database connection](#sqlite3). The first argument is the database connection object to be interrogated. The second argument is an integer constant, taken from the set of [SQLITE_DBSTATUS options](#SQLITE_DBSTATUS%20options), that determines the parameter to interrogate. The set of [SQLITE_DBSTATUS options](#SQLITE_DBSTATUS%20options) is likely to grow in future releases of SQLite.
The current value of the requested parameter is written into \*pCur and the highest instantaneous value is written into \*pHiwtr. If the resetFlg is true, then the highest instantaneous value is reset back down to the current value.
The sqlite3_db_status() routine returns SQLITE_OK on success and a non-zero [error code](rescode.md) on failure.
The sqlite3_db_status64(D,O,C,H,R) routine works exactly the same way as sqlite3_db_status(D,O,C,H,R) routine except that the C and H parameters are pointer to 64-bit integers (type: sqlite3_int64) instead of pointers to 32-bit integers, which allows larger status values to be returned. If a status value exceeds 2,147,483,647 then sqlite3_db_status() will truncate the value whereas sqlite3_db_status64() will return the full value.
See also: [sqlite3_status()](#sqlite3_status) and [sqlite3_stmt_status()](#sqlite3_stmt_status).
------------------------------------------------------------------------
## Error Codes And Messages
> \
> int sqlite3_errcode(sqlite3 \*db);\
> int sqlite3_extended_errcode(sqlite3 \*db);\
> const char \*sqlite3_errmsg(sqlite3\*);\
> const void \*sqlite3_errmsg16(sqlite3\*);\
> const char \*sqlite3_errstr(int);\
> int sqlite3_error_offset(sqlite3 \*db);\
If the most recent sqlite3\_\* API call associated with [database connection](#sqlite3) D failed, then the sqlite3_errcode(D) interface returns the numeric [result code](rescode.md) or [extended result code](rescode.md#extrc) for that API call. The sqlite3_extended_errcode() interface is the same except that it always returns the [extended result code](rescode.md#extrc) even when extended result codes are disabled.
The values returned by sqlite3_errcode() and/or sqlite3_extended_errcode() might change with each API call. Except, there are some interfaces that are guaranteed to never change the value of the error code. The error-code preserving interfaces include the following:
- sqlite3_errcode()
- sqlite3_extended_errcode()
- sqlite3_errmsg()
- sqlite3_errmsg16()
- sqlite3_error_offset()
- sqlite3_db_handle()
The sqlite3_errmsg() and sqlite3_errmsg16() return English-language text that describes the error, as either UTF-8 or UTF-16 respectively, or NULL if no error message is available. (See how SQLite handles [invalid UTF](invalidutf.md) for exceptions to this rule.) Memory to hold the error message string is managed internally. The application does not need to worry about freeing the result. However, the error string might be overwritten or deallocated by subsequent calls to other SQLite interface functions.
The sqlite3_errstr(E) interface returns the English-language text that describes the [result code](rescode.md) E, as UTF-8, or NULL if E is not a result code for which a text error message is available. Memory to hold the error message string is managed internally and must not be freed by the application.
If the most recent error references a specific token in the input SQL, the sqlite3_error_offset() interface returns the byte offset of the start of that token. The byte offset returned by sqlite3_error_offset() assumes that the input SQL is UTF-8. If the most recent error does not reference a specific token in the input SQL, then the sqlite3_error_offset() function returns -1.
When the serialized [threading mode](threadsafe.md) is in use, it might be the case that a second error occurs on a separate thread in between the time of the first error and the call to these interfaces. When that happens, the second error will be reported since these interfaces always report the most recent result. To avoid this, each thread can obtain exclusive use of the [database connection](#sqlite3) D by invoking [sqlite3_mutex_enter](#sqlite3_mutex_alloc)([sqlite3_db_mutex](#sqlite3_db_mutex)(D)) before beginning to use D and invoking [sqlite3_mutex_leave](#sqlite3_mutex_alloc)([sqlite3_db_mutex](#sqlite3_db_mutex)(D)) after all calls to the interfaces listed here are completed.
If an interface fails with SQLITE_MISUSE, that means the interface was invoked incorrectly by the application. In that case, the error code and message may or may not be set.
------------------------------------------------------------------------
## Retrieving Statement SQL
> \
> const char \*sqlite3_sql(sqlite3_stmt \*pStmt);\
> char \*sqlite3_expanded_sql(sqlite3_stmt \*pStmt);\
> \#ifdef SQLITE_ENABLE_NORMALIZE\
> const char \*sqlite3_normalized_sql(sqlite3_stmt \*pStmt);\
> \#endif\
The sqlite3_sql(P) interface returns a pointer to a copy of the UTF-8 SQL text used to create [prepared statement](#sqlite3_stmt) P if P was created by [sqlite3_prepare_v2()](#sqlite3_prepare), [sqlite3_prepare_v3()](#sqlite3_prepare), [sqlite3_prepare16_v2()](#sqlite3_prepare), or [sqlite3_prepare16_v3()](#sqlite3_prepare). The sqlite3_expanded_sql(P) interface returns a pointer to a UTF-8 string containing the SQL text of prepared statement P with [bound parameters](lang_expr.md#varparam) expanded. The sqlite3_normalized_sql(P) interface returns a pointer to a UTF-8 string containing the normalized SQL text of prepared statement P. The semantics used to normalize a SQL statement are unspecified and subject to change. At a minimum, literal values will be replaced with suitable placeholders.
For example, if a prepared statement is created using the SQL text "SELECT \$abc,:xyz" and if parameter \$abc is bound to integer 2345 and parameter :xyz is unbound, then sqlite3_sql() will return the original string, "SELECT \$abc,:xyz" but sqlite3_expanded_sql() will return "SELECT 2345,NULL".
The sqlite3_expanded_sql() interface returns NULL if insufficient memory is available to hold the result, or if the result would exceed the maximum string length determined by the [SQLITE_LIMIT_LENGTH](#sqlitelimitlength).
The [SQLITE_TRACE_SIZE_LIMIT](compile.md#trace_size_limit) compile-time option limits the size of bound parameter expansions. The [SQLITE_OMIT_TRACE](compile.md#omit_trace) compile-time option causes sqlite3_expanded_sql() to always return NULL.
The strings returned by sqlite3_sql(P) and sqlite3_normalized_sql(P) are managed by SQLite and are automatically freed when the prepared statement is finalized. The string returned by sqlite3_expanded_sql(P), on the other hand, is obtained from [sqlite3_malloc()](#sqlite3_free) and must be freed by the application by passing it to [sqlite3_free()](#sqlite3_free).
The sqlite3_normalized_sql() interface is only available if the [SQLITE_ENABLE_NORMALIZE](compile.md#enable_normalize) compile-time option is defined.
------------------------------------------------------------------------
## Translate filenames
> \
> const char \*sqlite3_filename_database(sqlite3_filename);\
> const char \*sqlite3_filename_journal(sqlite3_filename);\
> const char \*sqlite3_filename_wal(sqlite3_filename);\
These routines are available to [custom VFS implementations](vfs.md) for translating filenames between the main database file, the journal file, and the WAL file.
If F is the name of an sqlite database file, journal file, or WAL file passed by the SQLite core into the VFS, then sqlite3_filename_database(F) returns the name of the corresponding database file.
If F is the name of an sqlite database file, journal file, or WAL file passed by the SQLite core into the VFS, or if F is a database filename obtained from [sqlite3_db_filename()](#sqlite3_db_filename), then sqlite3_filename_journal(F) returns the name of the corresponding rollback journal file.
If F is the name of an sqlite database file, journal file, or WAL file that was passed by the SQLite core into the VFS, or if F is a database filename obtained from [sqlite3_db_filename()](#sqlite3_db_filename), then sqlite3_filename_wal(F) returns the name of the corresponding WAL file.
In all of the above, if F is not the name of a database, journal or WAL filename passed into the VFS from the SQLite core and F is not the return value from [sqlite3_db_filename()](#sqlite3_db_filename), then the result is undefined and is likely a memory access violation.
------------------------------------------------------------------------
## Memory Allocation Subsystem
> \
> void \*sqlite3_malloc(int);\
> void \*sqlite3_malloc64(sqlite3_uint64);\
> void \*sqlite3_realloc(void\*, int);\
> void \*sqlite3_realloc64(void\*, sqlite3_uint64);\
> void sqlite3_free(void\*);\
> sqlite3_uint64 sqlite3_msize(void\*);\
The SQLite core uses these three routines for all of its own internal memory allocation needs. "Core" in the previous sentence does not include operating-system specific [VFS](vfs.md) implementation. The Windows VFS uses native malloc() and free() for some operations.
The sqlite3_malloc() routine returns a pointer to a block of memory at least N bytes in length, where N is the parameter. If sqlite3_malloc() is unable to obtain sufficient free memory, it returns a NULL pointer. If the parameter N to sqlite3_malloc() is zero or negative then sqlite3_malloc() returns a NULL pointer.
The sqlite3_malloc64(N) routine works just like sqlite3_malloc(N) except that N is an unsigned 64-bit integer instead of a signed 32-bit integer.
Calling sqlite3_free() with a pointer previously returned by sqlite3_malloc() or sqlite3_realloc() releases that memory so that it might be reused. The sqlite3_free() routine is a no-op if it is called with a NULL pointer. Passing a NULL pointer to sqlite3_free() is harmless. After being freed, memory should neither be read nor written. Even reading previously freed memory might result in a segmentation fault or other severe error. Memory corruption, a segmentation fault, or other severe error might result if sqlite3_free() is called with a non-NULL pointer that was not obtained from sqlite3_malloc() or sqlite3_realloc().
The sqlite3_realloc(X,N) interface attempts to resize a prior memory allocation X to be at least N bytes. If the X parameter to sqlite3_realloc(X,N) is a NULL pointer then its behavior is identical to calling sqlite3_malloc(N). If the N parameter to sqlite3_realloc(X,N) is zero or negative then the behavior is exactly the same as calling sqlite3_free(X). sqlite3_realloc(X,N) returns a pointer to a memory allocation of at least N bytes in size or NULL if insufficient memory is available. If M is the size of the prior allocation, then min(N,M) bytes of the prior allocation are copied into the beginning of the buffer returned by sqlite3_realloc(X,N) and the prior allocation is freed. If sqlite3_realloc(X,N) returns NULL and N is positive, then the prior allocation is not freed.
The sqlite3_realloc64(X,N) interface works the same as sqlite3_realloc(X,N) except that N is a 64-bit unsigned integer instead of a 32-bit signed integer.
If X is a memory allocation previously obtained from sqlite3_malloc(), sqlite3_malloc64(), sqlite3_realloc(), or sqlite3_realloc64(), then sqlite3_msize(X) returns the size of that memory allocation in bytes. The value returned by sqlite3_msize(X) might be larger than the number of bytes requested when X was allocated. If X is a NULL pointer then sqlite3_msize(X) returns zero. If X points to something that is not the beginning of memory allocation, or if it points to a formerly valid memory allocation that has now been freed, then the behavior of sqlite3_msize(X) is undefined and possibly harmful.
The memory returned by sqlite3_malloc(), sqlite3_realloc(), sqlite3_malloc64(), and sqlite3_realloc64() is always aligned to at least an 8 byte boundary, or to a 4 byte boundary if the [SQLITE_4_BYTE_ALIGNED_MALLOC](compile.md#4_byte_aligned_malloc) compile-time option is used.
The pointer arguments to [sqlite3_free()](#sqlite3_free) and [sqlite3_realloc()](#sqlite3_free) must be either NULL or else pointers obtained from a prior invocation of [sqlite3_malloc()](#sqlite3_free) or [sqlite3_realloc()](#sqlite3_free) that have not yet been released.
The application must not read or write any part of a block of memory after it has been released using [sqlite3_free()](#sqlite3_free) or [sqlite3_realloc()](#sqlite3_free).
------------------------------------------------------------------------
## Convenience Routines For Running Queries
> \
> int sqlite3_get_table(\
> sqlite3 \*db, /\* An open database \*/\
> const char \*zSql, /\* SQL to be evaluated \*/\
> char \*\*\*pazResult, /\* Results of the query \*/\
> int \*pnRow, /\* Number of result rows written here \*/\
> int \*pnColumn, /\* Number of result columns written here \*/\
> char \*\*pzErrmsg /\* Error msg written here \*/\
> );\
> void sqlite3_free_table(char \*\*result);\
This is a legacy interface that is preserved for backwards compatibility. Use of this interface is not recommended.
Definition: A **result table** is a memory data structure created by the [sqlite3_get_table()](#sqlite3_free_table) interface. A result table records the complete query results from one or more queries.
The table conceptually has a number of rows and columns. But these numbers are not part of the result table itself. These numbers are obtained separately. Let N be the number of rows and M be the number of columns.
A result table is an array of pointers to zero-terminated UTF-8 strings. There are (N+1)\*M elements in the array. The first M pointers point to zero-terminated strings that contain the names of the columns. The remaining entries all point to query results. NULL values result in NULL pointers. All other values are in their UTF-8 zero-terminated string representation as returned by [sqlite3_column_text()](#sqlite3_column_blob).
A result table might consist of one or more memory allocations. It is not safe to pass a result table directly to [sqlite3_free()](#sqlite3_free). A result table should be deallocated using [sqlite3_free_table()](#sqlite3_free_table).
As an example of the result table format, suppose a query result is as follows:
> \
> Name \| Age\
> -----------------------\
> Alice \| 43\
> Bob \| 28\
> Cindy \| 21\
There are two columns (M==2) and three rows (N==3). Thus the result table has 8 entries. Suppose the result table is stored in an array named azResult. Then azResult holds this content:
> \
> azResult\[0\] = "Name";\
> azResult\[1\] = "Age";\
> azResult\[2\] = "Alice";\
> azResult\[3\] = "43";\
> azResult\[4\] = "Bob";\
> azResult\[5\] = "28";\
> azResult\[6\] = "Cindy";\
> azResult\[7\] = "21";\
The sqlite3_get_table() function evaluates one or more semicolon-separated SQL statements in the zero-terminated UTF-8 string of its 2nd parameter and returns a result table to the pointer given in its 3rd parameter.
After the application has finished with the result from sqlite3_get_table(), it must pass the result table pointer to sqlite3_free_table() in order to release the memory that was malloced. Because of the way the [sqlite3_malloc()](#sqlite3_free) happens within sqlite3_get_table(), the calling function must not try to call [sqlite3_free()](#sqlite3_free) directly. Only [sqlite3_free_table()](#sqlite3_free_table) is able to release the memory properly and safely.
The sqlite3_get_table() interface is implemented as a wrapper around [sqlite3_exec()](#sqlite3_exec). The sqlite3_get_table() routine does not have access to any internal data structures of SQLite. It uses only the public interface defined here. As a consequence, errors that occur in the wrapper layer outside of the internal [sqlite3_exec()](#sqlite3_exec) call are not reflected in subsequent calls to [sqlite3_errcode()](#sqlite3_errcode) or [sqlite3_errmsg()](#sqlite3_errcode).
------------------------------------------------------------------------
## Function Auxiliary Data
> \
> void \*sqlite3_get_auxdata(sqlite3_context\*, int N);\
> void sqlite3_set_auxdata(sqlite3_context\*, int N, void\*, void (\*)(void\*));\
These functions may be used by (non-aggregate) SQL functions to associate auxiliary data with argument values. If the same argument value is passed to multiple invocations of the same SQL function during query execution, under some circumstances the associated auxiliary data might be preserved. An example of where this might be useful is in a regular-expression matching function. The compiled version of the regular expression can be stored as auxiliary data associated with the pattern string. Then as long as the pattern string remains the same, the compiled regular expression can be reused on multiple invocations of the same function.
The sqlite3_get_auxdata(C,N) interface returns a pointer to the auxiliary data associated by the sqlite3_set_auxdata(C,N,P,X) function with the Nth argument value to the application-defined function. N is zero for the left-most function argument. If there is no auxiliary data associated with the function argument, the sqlite3_get_auxdata(C,N) interface returns a NULL pointer.
The sqlite3_set_auxdata(C,N,P,X) interface saves P as auxiliary data for the N-th argument of the application-defined function. Subsequent calls to sqlite3_get_auxdata(C,N) return P from the most recent sqlite3_set_auxdata(C,N,P,X) call if the auxiliary data is still valid or NULL if the auxiliary data has been discarded. After each call to sqlite3_set_auxdata(C,N,P,X) where X is not NULL, SQLite will invoke the destructor function X with parameter P exactly once, when the auxiliary data is discarded. SQLite is free to discard the auxiliary data at any time, including:
- when the corresponding function parameter changes, or
- when [sqlite3_reset()](#sqlite3_reset) or [sqlite3_finalize()](#sqlite3_finalize) is called for the SQL statement, or
- when sqlite3_set_auxdata() is invoked again on the same parameter, or
- during the original sqlite3_set_auxdata() call when a memory allocation error occurs.
- during the original sqlite3_set_auxdata() call if the function is evaluated during query planning instead of during query execution, as sometimes happens with [SQLITE_ENABLE_STAT4](compile.md#enable_stat4).
Note the last two bullets in particular. The destructor X in sqlite3_set_auxdata(C,N,P,X) might be called immediately, before the sqlite3_set_auxdata() interface even returns. Hence sqlite3_set_auxdata() should be called near the end of the function implementation and the function implementation should not make any use of P after sqlite3_set_auxdata() has been called. Furthermore, a call to sqlite3_get_auxdata() that occurs immediately after a corresponding call to sqlite3_set_auxdata() might still return NULL if an out-of-memory condition occurred during the sqlite3_set_auxdata() call or if the function is being evaluated during query planning rather than during query execution.
In practice, auxiliary data is preserved between function calls for function parameters that are compile-time constants, including literal values and [parameters](lang_expr.md#varparam) and expressions composed from the same.
The value of the N parameter to these interfaces should be non-negative. Future enhancements may make use of negative N values to define new kinds of function caching behavior.
These routines must be called from the same thread in which the SQL function is running.
See also: [sqlite3_get_clientdata()](#sqlite3_get_clientdata) and [sqlite3_set_clientdata()](#sqlite3_get_clientdata).
------------------------------------------------------------------------
## Database Connection Client Data
> \
> void \*sqlite3_get_clientdata(sqlite3\*,const char\*);\
> int sqlite3_set_clientdata(sqlite3\*, const char\*, void\*, void(\*)(void\*));\
These functions are used to associate one or more named pointers with a [database connection](#sqlite3). A call to sqlite3_set_clientdata(D,N,P,X) causes the pointer P to be attached to [database connection](#sqlite3) D using name N. Subsequent calls to sqlite3_get_clientdata(D,N) will return a copy of pointer P or a NULL pointer if there were no prior calls to sqlite3_set_clientdata() with the same values of D and N. Names are compared using strcmp() and are thus case sensitive. It returns 0 on success and SQLITE_NOMEM on allocation failure.
If P and X are both non-NULL, then the destructor X is invoked with argument P on the first of the following occurrences:
- An out-of-memory error occurs during the call to sqlite3_set_clientdata() which attempts to register pointer P.
- A subsequent call to sqlite3_set_clientdata(D,N,P,X) is made with the same D and N parameters.
- The database connection closes. SQLite does not make any guarantees about the order in which destructors are called, only that all destructors will be called exactly once at some point during the database connection closing process.
SQLite does not do anything with client data other than invoke destructors on the client data at the appropriate time. The intended use for client data is to provide a mechanism for wrapper libraries to store additional information about an SQLite database connection.
There is no limit (other than available memory) on the number of different client data pointers (with different names) that can be attached to a single database connection. However, the current implementation stores the content on a linked list. Insert and retrieval performance will be proportional to the number of entries. The design use case, and the use case for which the implementation is optimized, is that an application will store only small number of client data names, typically just one or two. This interface is not intended to be a generalized key/value store for thousands or millions of keys. It will work for that, but performance might be disappointing.
There is no way to enumerate the client data pointers associated with a database connection. The N parameter can be thought of as a secret key such that only code that knows the secret key is able to access the associated data.
Security Warning: These interfaces should not be exposed in scripting languages or in other circumstances where it might be possible for an attacker to invoke them. Any agent that can invoke these interfaces can probably also take control of the process.
Database connection client data is only available for SQLite version 3.44.0 (2023-11-01) and later.
See also: [sqlite3_set_auxdata()](#sqlite3_get_auxdata) and [sqlite3_get_auxdata()](#sqlite3_get_auxdata).
------------------------------------------------------------------------
## Impose A Limit On Heap Size
> \
> sqlite3_int64 sqlite3_soft_heap_limit64(sqlite3_int64 N);\
> sqlite3_int64 sqlite3_hard_heap_limit64(sqlite3_int64 N);\
These interfaces impose limits on the amount of heap memory that will be used by all database connections within a single process.
The sqlite3_soft_heap_limit64() interface sets and/or queries the soft limit on the amount of heap memory that may be allocated by SQLite. SQLite strives to keep heap memory utilization below the soft heap limit by reducing the number of pages held in the page cache as heap memory usages approaches the limit. The soft heap limit is "soft" because even though SQLite strives to stay below the limit, it will exceed the limit rather than generate an [SQLITE_NOMEM](#SQLITE_ABORT) error. In other words, the soft heap limit is advisory only.
The sqlite3_hard_heap_limit64(N) interface sets a hard upper bound of N bytes on the amount of memory that will be allocated. The sqlite3_hard_heap_limit64(N) interface is similar to sqlite3_soft_heap_limit64(N) except that memory allocations will fail when the hard heap limit is reached.
The return value from both sqlite3_soft_heap_limit64() and sqlite3_hard_heap_limit64() is the size of the heap limit prior to the call, or negative in the case of an error. If the argument N is negative then no change is made to the heap limit. Hence, the current size of heap limits can be determined by invoking sqlite3_soft_heap_limit64(-1) or sqlite3_hard_heap_limit(-1).
Setting the heap limits to zero disables the heap limiter mechanism.
The soft heap limit may not be greater than the hard heap limit. If the hard heap limit is enabled and if sqlite3_soft_heap_limit(N) is invoked with a value of N that is greater than the hard heap limit, the soft heap limit is set to the value of the hard heap limit. The soft heap limit is automatically enabled whenever the hard heap limit is enabled. When sqlite3_hard_heap_limit64(N) is invoked and the soft heap limit is outside the range of 1..N, then the soft heap limit is set to N. Invoking sqlite3_soft_heap_limit64(0) when the hard heap limit is enabled makes the soft heap limit equal to the hard heap limit.
The memory allocation limits can also be adjusted using [PRAGMA soft_heap_limit](pragma.md#pragma_soft_heap_limit) and [PRAGMA hard_heap_limit](pragma.md#pragma_hard_heap_limit).
The heap limits are not enforced in the current implementation if one or more of following conditions are true:
- The limit value is set to zero.
- Memory accounting is disabled using a combination of the [sqlite3_config](#sqlite3_config)([SQLITE_CONFIG_MEMSTATUS](#sqliteconfigmemstatus),...) start-time option and the [SQLITE_DEFAULT_MEMSTATUS](compile.md#default_memstatus) compile-time option.
- An alternative page cache implementation is specified using [sqlite3_config](#sqlite3_config)([SQLITE_CONFIG_PCACHE2](#sqliteconfigpcache2),...).
- The page cache allocates from its own memory pool supplied by [sqlite3_config](#sqlite3_config)([SQLITE_CONFIG_PAGECACHE](#sqliteconfigpagecache),...) rather than from the heap.
The circumstances under which SQLite will enforce the heap limits may change in future releases of SQLite.
------------------------------------------------------------------------
## Initialize The SQLite Library
> \
> int sqlite3_initialize(void);\
> int sqlite3_shutdown(void);\
> int sqlite3_os_init(void);\
> int sqlite3_os_end(void);\
The sqlite3_initialize() routine initializes the SQLite library. The sqlite3_shutdown() routine deallocates any resources that were allocated by sqlite3_initialize(). These routines are designed to aid in process initialization and shutdown on embedded systems. Workstation applications using SQLite normally do not need to invoke either of these routines.
A call to sqlite3_initialize() is an "effective" call if it is the first time sqlite3_initialize() is invoked during the lifetime of the process, or if it is the first time sqlite3_initialize() is invoked following a call to sqlite3_shutdown(). Only an effective call of sqlite3_initialize() does any initialization. All other calls are harmless no-ops.
A call to sqlite3_shutdown() is an "effective" call if it is the first call to sqlite3_shutdown() since the last sqlite3_initialize(). Only an effective call to sqlite3_shutdown() does any deinitialization. All other valid calls to sqlite3_shutdown() are harmless no-ops.
The sqlite3_initialize() interface is threadsafe, but sqlite3_shutdown() is not. The sqlite3_shutdown() interface must only be called from a single thread. All open [database connections](#sqlite3) must be closed and all other SQLite resources must be deallocated prior to invoking sqlite3_shutdown().
Among other things, sqlite3_initialize() will invoke sqlite3_os_init(). Similarly, sqlite3_shutdown() will invoke sqlite3_os_end().
The sqlite3_initialize() routine returns [SQLITE_OK](#SQLITE_ABORT) on success. If for some reason, sqlite3_initialize() is unable to initialize the library (perhaps it is unable to allocate a needed resource such as a mutex) it returns an [error code](rescode.md) other than [SQLITE_OK](#SQLITE_ABORT).
The sqlite3_initialize() routine is called internally by many other SQLite interfaces so that an application usually does not need to invoke sqlite3_initialize() directly. For example, [sqlite3_open()](#sqlite3_open) calls sqlite3_initialize() so the SQLite library will be automatically initialized when [sqlite3_open()](#sqlite3_open) is called if it has not been initialized already. However, if SQLite is compiled with the [SQLITE_OMIT_AUTOINIT](compile.md#omit_autoinit) compile-time option, then the automatic calls to sqlite3_initialize() are omitted and the application must call sqlite3_initialize() directly prior to using any other SQLite interface. For maximum portability, it is recommended that applications always invoke sqlite3_initialize() directly prior to using any other SQLite interface. Future releases of SQLite may require this. In other words, the behavior exhibited when SQLite is compiled with [SQLITE_OMIT_AUTOINIT](compile.md#omit_autoinit) might become the default behavior in some future release of SQLite.
The sqlite3_os_init() routine does operating-system specific initialization of the SQLite library. The sqlite3_os_end() routine undoes the effect of sqlite3_os_init(). Typical tasks performed by these routines include allocation or deallocation of static resources, initialization of global variables, setting up a default [sqlite3_vfs](#sqlite3_vfs) module, or setting up a default configuration using [sqlite3_config()](#sqlite3_config).
The application should never invoke either sqlite3_os_init() or sqlite3_os_end() directly. The application should only invoke sqlite3_initialize() and sqlite3_shutdown(). The sqlite3_os_init() interface is called automatically by sqlite3_initialize() and sqlite3_os_end() is called by sqlite3_shutdown(). Appropriate implementations for sqlite3_os_init() and sqlite3_os_end() are built into SQLite when it is compiled for Unix, Windows, or OS/2. When [built for other platforms](custombuild.md) (using the [SQLITE_OS_OTHER=1](compile.md#os_other) compile-time option) the application must supply a suitable implementation for sqlite3_os_init() and sqlite3_os_end(). An application-supplied implementation of sqlite3_os_init() or sqlite3_os_end() must return [SQLITE_OK](#SQLITE_ABORT) on success and some other [error code](rescode.md) upon failure.
------------------------------------------------------------------------
## Interrupt A Long-Running Query
> \
> void sqlite3_interrupt(sqlite3\*);\
> int sqlite3_is_interrupted(sqlite3\*);\
This function causes any pending database operation to abort and return at its earliest opportunity. This routine is typically called in response to a user action such as pressing "Cancel" or Ctrl-C where the user wants a long query operation to halt immediately.
It is safe to call this routine from a thread different from the thread that is currently running the database operation. But it is not safe to call this routine with a [database connection](#sqlite3) that is closed or might close before sqlite3_interrupt() returns.
If an SQL operation is very nearly finished at the time when sqlite3_interrupt() is called, then it might not have an opportunity to be interrupted and might continue to completion.
An SQL operation that is interrupted will return [SQLITE_INTERRUPT](#SQLITE_ABORT). If the interrupted SQL operation is an INSERT, UPDATE, or DELETE that is inside an explicit transaction, then the entire transaction will be rolled back automatically.
The sqlite3_interrupt(D) call is in effect until all currently running SQL statements on [database connection](#sqlite3) D complete. Any new SQL statements that are started after the sqlite3_interrupt() call and before the running statement count reaches zero are interrupted as if they had been running prior to the sqlite3_interrupt() call. New SQL statements that are started after the running statement count reaches zero are not effected by the sqlite3_interrupt(). A call to sqlite3_interrupt(D) that occurs when there are no running SQL statements is a no-op and has no effect on SQL statements that are started after the sqlite3_interrupt() call returns.
The [sqlite3_is_interrupted(D)](#sqlite3_interrupt) interface can be used to determine whether or not an interrupt is currently in effect for [database connection](#sqlite3) D. It returns 1 if an interrupt is currently in effect, or 0 otherwise.
------------------------------------------------------------------------
## SQL Keyword Checking
> \
> int sqlite3_keyword_count(void);\
> int sqlite3_keyword_name(int,const char\*\*,int\*);\
> int sqlite3_keyword_check(const char\*,int);\
These routines provide access to the set of SQL language keywords recognized by SQLite. Applications can use these routines to determine whether or not a specific identifier needs to be escaped (for example, by enclosing in double-quotes) so as not to confuse the parser.
The sqlite3_keyword_count() interface returns the number of distinct keywords understood by SQLite.
The sqlite3_keyword_name(N,Z,L) interface finds the 0-based N-th keyword and makes \*Z point to that keyword expressed as UTF8 and writes the number of bytes in the keyword into \*L. The string that \*Z points to is not zero-terminated. The sqlite3_keyword_name(N,Z,L) routine returns SQLITE_OK if N is within bounds and SQLITE_ERROR if not. If either Z or L are NULL or invalid pointers then calls to sqlite3_keyword_name(N,Z,L) result in undefined behavior.
The sqlite3_keyword_check(Z,L) interface checks to see whether or not the L-byte UTF8 identifier that Z points to is a keyword, returning non-zero if it is and zero if not.
The parser used by SQLite is forgiving. It is often possible to use a keyword as an identifier as long as such use does not result in a parsing ambiguity. For example, the statement "CREATE TABLE BEGIN(REPLACE,PRAGMA,END);" is accepted by SQLite, and creates a new table named "BEGIN" with three columns named "REPLACE", "PRAGMA", and "END". Nevertheless, best practice is to avoid using keywords as identifiers. Common techniques used to avoid keyword name collisions include:
- Put all identifier names inside double-quotes. This is the official SQL way to escape identifier names.
- Put identifier names inside \[...\]. This is not standard SQL, but it is what SQL Server does and so lots of programmers use this technique.
- Begin every identifier with the letter "Z" as no SQL keywords start with "Z".
- Include a digit somewhere in every identifier name.
Note that the number of keywords understood by SQLite can depend on compile-time options. For example, "VACUUM" is not a keyword if SQLite is compiled with the [-DSQLITE_OMIT_VACUUM](compile.md#omit_vacuum) option. Also, new keywords may be added to future releases of SQLite.
------------------------------------------------------------------------
## Run-Time Library Version Numbers
> \
> SQLITE_EXTERN const char sqlite3_version\[\];\
> const char \*sqlite3_libversion(void);\
> const char \*sqlite3_sourceid(void);\
> int sqlite3_libversion_number(void);\
These interfaces provide the same information as the [SQLITE_VERSION](#SQLITE_SCM_BRANCH), [SQLITE_VERSION_NUMBER](#SQLITE_SCM_BRANCH), and [SQLITE_SOURCE_ID](#SQLITE_SCM_BRANCH) C preprocessor macros but are associated with the library instead of the header file. Cautious programmers might include assert() statements in their application to verify that values returned by these interfaces match the macros in the header, and thus ensure that the application is compiled with matching library and header files.
> \
> assert( sqlite3_libversion_number()==SQLITE_VERSION_NUMBER );\
> assert( strncmp(sqlite3_sourceid(),SQLITE_SOURCE_ID,80)==0 );\
> assert( strcmp(sqlite3_libversion(),SQLITE_VERSION)==0 );\
The sqlite3_version\[\] string constant contains the text of the [SQLITE_VERSION](#SQLITE_SCM_BRANCH) macro. The sqlite3_libversion() function returns a pointer to the sqlite3_version\[\] string constant. The sqlite3_libversion() function is provided for use in DLLs since DLL users usually do not have direct access to string constants within the DLL. The sqlite3_libversion_number() function returns an integer equal to [SQLITE_VERSION_NUMBER](#SQLITE_SCM_BRANCH). The sqlite3_sourceid() function returns a pointer to a string constant whose value is the same as the [SQLITE_SOURCE_ID](#SQLITE_SCM_BRANCH) C preprocessor macro. Except if SQLite is built using an edited copy of [the amalgamation](amalgamation.md), then the last four characters of the hash might be different from [SQLITE_SOURCE_ID](#SQLITE_SCM_BRANCH).
See also: [sqlite_version()](lang_corefunc.md#sqlite_version) and [sqlite_source_id()](lang_corefunc.md#sqlite_source_id).
------------------------------------------------------------------------
## Memory Allocator Statistics
> \
> sqlite3_int64 sqlite3_memory_used(void);\
> sqlite3_int64 sqlite3_memory_highwater(int resetFlag);\
SQLite provides these two interfaces for reporting on the status of the [sqlite3_malloc()](#sqlite3_free), [sqlite3_free()](#sqlite3_free), and [sqlite3_realloc()](#sqlite3_free) routines, which form the built-in memory allocation subsystem.
The [sqlite3_memory_used()](#sqlite3_memory_highwater) routine returns the number of bytes of memory currently outstanding (malloced but not freed). The [sqlite3_memory_highwater()](#sqlite3_memory_highwater) routine returns the maximum value of [sqlite3_memory_used()](#sqlite3_memory_highwater) since the high-water mark was last reset. The values returned by [sqlite3_memory_used()](#sqlite3_memory_highwater) and [sqlite3_memory_highwater()](#sqlite3_memory_highwater) include any overhead added by SQLite in its implementation of [sqlite3_malloc()](#sqlite3_free), but not overhead added by any underlying system library routines that [sqlite3_malloc()](#sqlite3_free) may call.
The memory high-water mark is reset to the current value of [sqlite3_memory_used()](#sqlite3_memory_highwater) if and only if the parameter to [sqlite3_memory_highwater()](#sqlite3_memory_highwater) is true. The value returned by [sqlite3_memory_highwater(1)](#sqlite3_memory_highwater) is the high-water mark prior to the reset.
------------------------------------------------------------------------
## Formatted String Printing Functions
> \
> char \*sqlite3_mprintf(const char\*,...);\
> char \*sqlite3_vmprintf(const char\*, va_list);\
> char \*sqlite3_snprintf(int,char\*,const char\*, ...);\
> char \*sqlite3_vsnprintf(int,char\*,const char\*, va_list);\
These routines are work-alikes of the "printf()" family of functions from the standard C library. These routines understand most of the common formatting options from the standard library printf() plus some additional non-standard formats ([%q](printf.md#percentq), [%Q](printf.md#percentq), [%w](printf.md#percentw), and [%z](printf.md#percentz)). See the [built-in printf()](printf.md) documentation for details.
The sqlite3_mprintf() and sqlite3_vmprintf() routines write their results into memory obtained from [sqlite3_malloc64()](#sqlite3_free). The strings returned by these two routines should be released by [sqlite3_free()](#sqlite3_free). Both routines return a NULL pointer if [sqlite3_malloc64()](#sqlite3_free) is unable to allocate enough memory to hold the resulting string.
The sqlite3_snprintf() routine is similar to "snprintf()" from the standard C library. The result is written into the buffer supplied as the second parameter whose size is given by the first parameter. Note that the order of the first two parameters is reversed from snprintf(). This is an historical accident that cannot be fixed without breaking backwards compatibility. Note also that sqlite3_snprintf() returns a pointer to its buffer instead of the number of characters actually written into the buffer. We admit that the number of characters written would be a more useful return value but we cannot change the implementation of sqlite3_snprintf() now without breaking compatibility.
As long as the buffer size is greater than zero, sqlite3_snprintf() guarantees that the buffer is always zero-terminated. The first parameter "n" is the total size of the buffer, including space for the zero terminator. So the longest string that can be completely written will be n-1 characters.
The sqlite3_vsnprintf() routine is a varargs version of sqlite3_snprintf().
See also: [built-in printf()](printf.md), [printf() SQL function](lang_corefunc.md#printf)
------------------------------------------------------------------------
## Mutexes
> \
> sqlite3_mutex \*sqlite3_mutex_alloc(int);\
> void sqlite3_mutex_free(sqlite3_mutex\*);\
> void sqlite3_mutex_enter(sqlite3_mutex\*);\
> int sqlite3_mutex_try(sqlite3_mutex\*);\
> void sqlite3_mutex_leave(sqlite3_mutex\*);\
The SQLite core uses these routines for thread synchronization. Though they are intended for internal use by SQLite, code that links against SQLite is permitted to use any of these routines.
The SQLite source code contains multiple implementations of these mutex routines. An appropriate implementation is selected automatically at compile-time. The following implementations are available in the SQLite core:
- SQLITE_MUTEX_PTHREADS
- SQLITE_MUTEX_W32
- SQLITE_MUTEX_NOOP
The SQLITE_MUTEX_NOOP implementation is a set of routines that does no real locking and is appropriate for use in a single-threaded application. The SQLITE_MUTEX_PTHREADS and SQLITE_MUTEX_W32 implementations are appropriate for use on Unix and Windows.
The sqlite3_mutex_alloc() routine allocates a new mutex and returns a pointer to it. The sqlite3_mutex_alloc() routine returns NULL if it is unable to allocate the requested mutex. The argument to sqlite3_mutex_alloc() must be one of these integer constants:
- SQLITE_MUTEX_FAST
- SQLITE_MUTEX_RECURSIVE
- SQLITE_MUTEX_STATIC_MAIN
- SQLITE_MUTEX_STATIC_MEM
- SQLITE_MUTEX_STATIC_OPEN
- SQLITE_MUTEX_STATIC_PRNG
- SQLITE_MUTEX_STATIC_LRU
- SQLITE_MUTEX_STATIC_PMEM
- SQLITE_MUTEX_STATIC_APP1
- SQLITE_MUTEX_STATIC_APP2
- SQLITE_MUTEX_STATIC_APP3
- SQLITE_MUTEX_STATIC_VFS1
- SQLITE_MUTEX_STATIC_VFS2
- SQLITE_MUTEX_STATIC_VFS3
The first two constants (SQLITE_MUTEX_FAST and SQLITE_MUTEX_RECURSIVE) cause sqlite3_mutex_alloc() to create a new mutex. The new mutex is recursive when SQLITE_MUTEX_RECURSIVE is used but not necessarily so when SQLITE_MUTEX_FAST is used. The mutex implementation does not need to make a distinction between SQLITE_MUTEX_RECURSIVE and SQLITE_MUTEX_FAST if it does not want to. SQLite will only request a recursive mutex in cases where it really needs one. If a faster non-recursive mutex implementation is available on the host platform, the mutex subsystem might return such a mutex in response to SQLITE_MUTEX_FAST.
The other allowed parameters to sqlite3_mutex_alloc() (anything other than SQLITE_MUTEX_FAST and SQLITE_MUTEX_RECURSIVE) each return a pointer to a static preexisting mutex. Nine static mutexes are used by the current version of SQLite. Future versions of SQLite may add additional static mutexes. Static mutexes are for internal use by SQLite only. Applications that use SQLite mutexes should use only the dynamic mutexes returned by SQLITE_MUTEX_FAST or SQLITE_MUTEX_RECURSIVE.
Note that if one of the dynamic mutex parameters (SQLITE_MUTEX_FAST or SQLITE_MUTEX_RECURSIVE) is used then sqlite3_mutex_alloc() returns a different mutex on every call. For the static mutex types, the same mutex is returned on every call that has the same type number.
The sqlite3_mutex_free() routine deallocates a previously allocated dynamic mutex. Attempting to deallocate a static mutex results in undefined behavior.
The sqlite3_mutex_enter() and sqlite3_mutex_try() routines attempt to enter a mutex. If another thread is already within the mutex, sqlite3_mutex_enter() will block and sqlite3_mutex_try() will return SQLITE_BUSY. The sqlite3_mutex_try() interface returns [SQLITE_OK](#SQLITE_ABORT) upon successful entry. Mutexes created using SQLITE_MUTEX_RECURSIVE can be entered multiple times by the same thread. In such cases, the mutex must be exited an equal number of times before another thread can enter. If the same thread tries to enter any mutex other than an SQLITE_MUTEX_RECURSIVE more than once, the behavior is undefined.
Some systems (for example, Windows 95) do not support the operation implemented by sqlite3_mutex_try(). On those systems, sqlite3_mutex_try() will always return SQLITE_BUSY. In most cases the SQLite core only uses sqlite3_mutex_try() as an optimization, so this is acceptable behavior. The exceptions are unix builds that set the SQLITE_ENABLE_SETLK_TIMEOUT build option. In that case a working sqlite3_mutex_try() is required.
The sqlite3_mutex_leave() routine exits a mutex that was previously entered by the same thread. The behavior is undefined if the mutex is not currently entered by the calling thread or is not currently allocated.
If the argument to sqlite3_mutex_enter(), sqlite3_mutex_try(), sqlite3_mutex_leave(), or sqlite3_mutex_free() is a NULL pointer, then any of the four routines behaves as a no-op.
See also: [sqlite3_mutex_held()](#sqlite3_mutex_held) and [sqlite3_mutex_notheld()](#sqlite3_mutex_held).
------------------------------------------------------------------------
## Mutex Verification Routines
> \
> \#ifndef NDEBUG\
> int sqlite3_mutex_held(sqlite3_mutex\*);\
> int sqlite3_mutex_notheld(sqlite3_mutex\*);\
> \#endif\
The sqlite3_mutex_held() and sqlite3_mutex_notheld() routines are intended for use inside assert() statements. The SQLite core never uses these routines except inside an assert() and applications are advised to follow the lead of the core. The SQLite core only provides implementations for these routines when it is compiled with the SQLITE_DEBUG flag. External mutex implementations are only required to provide these routines if SQLITE_DEBUG is defined and if NDEBUG is not defined.
These routines should return true if the mutex in their argument is held or not held, respectively, by the calling thread.
The implementation is not required to provide versions of these routines that actually work. If the implementation does not provide working versions of these routines, it should at least provide stubs that always return true so that one does not get spurious assertion failures.
If the argument to sqlite3_mutex_held() is a NULL pointer then the routine should return 1. This seems counter-intuitive since clearly the mutex cannot be held if it does not exist. But the reason the mutex does not exist is because the build is not using mutexes. And we do not want the assert() containing the call to sqlite3_mutex_held() to fail, so a non-zero return is the appropriate thing to do. The sqlite3_mutex_notheld() interface should also return 1 when given a NULL pointer.
------------------------------------------------------------------------
## Opening A New Database Connection
> \
> int sqlite3_open(\
> const char \*filename, /\* Database filename (UTF-8) \*/\
> sqlite3 \*\*ppDb /\* OUT: SQLite db handle \*/\
> );\
> int sqlite3_open16(\
> const void \*filename, /\* Database filename (UTF-16) \*/\
> sqlite3 \*\*ppDb /\* OUT: SQLite db handle \*/\
> );\
> int sqlite3_open_v2(\
> const char \*filename, /\* Database filename (UTF-8) \*/\
> sqlite3 \*\*ppDb, /\* OUT: SQLite db handle \*/\
> int flags, /\* Flags \*/\
> const char \*zVfs /\* Name of VFS module to use \*/\
> );\
These routines open an SQLite database file as specified by the filename argument. The filename argument is interpreted as UTF-8 for sqlite3_open() and sqlite3_open_v2() and as UTF-16 in the native byte order for sqlite3_open16(). A [database connection](#sqlite3) handle is usually returned in \*ppDb, even if an error occurs. The only exception is that if SQLite is unable to allocate memory to hold the [sqlite3](#sqlite3) object, a NULL will be written into \*ppDb instead of a pointer to the [sqlite3](#sqlite3) object. If the database is opened (and/or created) successfully, then [SQLITE_OK](#SQLITE_ABORT) is returned. Otherwise an [error code](rescode.md) is returned. The [sqlite3_errmsg()](#sqlite3_errcode) or [sqlite3_errmsg16()](#sqlite3_errcode) routines can be used to obtain an English language description of the error following a failure of any of the sqlite3_open() routines.
The default encoding will be UTF-8 for databases created using sqlite3_open() or sqlite3_open_v2(). The default encoding for databases created using sqlite3_open16() will be UTF-16 in the native byte order.
Whether or not an error occurs when it is opened, resources associated with the [database connection](#sqlite3) handle should be released by passing it to [sqlite3_close()](#sqlite3_close) when it is no longer required.
The sqlite3_open_v2() interface works like sqlite3_open() except that it accepts two additional parameters for additional control over the new database connection. The flags parameter to sqlite3_open_v2() must include, at a minimum, one of the following three flag combinations:
[SQLITE_OPEN_READONLY](#SQLITE_OPEN_AUTOPROXY)
The database is opened in read-only mode. If the database does not already exist, an error is returned.
[SQLITE_OPEN_READWRITE](#SQLITE_OPEN_AUTOPROXY)
The database is opened for reading and writing if possible, or reading only if the file is write protected by the operating system. In either case the database must already exist, otherwise an error is returned. For historical reasons, if opening in read-write mode fails due to OS-level permissions, an attempt is made to open it in read-only mode. [sqlite3_db_readonly()](#sqlite3_db_readonly) can be used to determine whether the database is actually read-write.
[SQLITE_OPEN_READWRITE](#SQLITE_OPEN_AUTOPROXY) \| [SQLITE_OPEN_CREATE](#SQLITE_OPEN_AUTOPROXY)
The database is opened for reading and writing, and is created if it does not already exist. This is the behavior that is always used for sqlite3_open() and sqlite3_open16().
In addition to the required flags, the following optional flags are also supported:
[SQLITE_OPEN_URI](#SQLITE_OPEN_AUTOPROXY)
The filename can be interpreted as a URI if this flag is set.
[SQLITE_OPEN_MEMORY](#SQLITE_OPEN_AUTOPROXY)
The database will be opened as an in-memory database. The database is named by the "filename" argument for the purposes of cache-sharing, if shared cache mode is enabled, but the "filename" is otherwise ignored.
[SQLITE_OPEN_NOMUTEX](#SQLITE_OPEN_AUTOPROXY)
The new database connection will use the "multi-thread" [threading mode](threadsafe.md). This means that separate threads are allowed to use SQLite at the same time, as long as each thread is using a different [database connection](#sqlite3).
[SQLITE_OPEN_FULLMUTEX](#SQLITE_OPEN_AUTOPROXY)
The new database connection will use the "serialized" [threading mode](threadsafe.md). This means the multiple threads can safely attempt to use the same database connection at the same time. (Mutexes will block any actual concurrency, but in this mode there is no harm in trying.)
[SQLITE_OPEN_SHAREDCACHE](#SQLITE_OPEN_AUTOPROXY)
The database is opened with [shared cache](sharedcache.md) enabled, overriding the default shared cache setting provided by [sqlite3_enable_shared_cache()](#sqlite3_enable_shared_cache). The [use of shared cache mode is discouraged](sharedcache.md#dontuse) and hence shared cache capabilities may be omitted from many builds of SQLite. In such cases, this option is a no-op.
[SQLITE_OPEN_PRIVATECACHE](#SQLITE_OPEN_AUTOPROXY)
The database is opened with [shared cache](sharedcache.md) disabled, overriding the default shared cache setting provided by [sqlite3_enable_shared_cache()](#sqlite3_enable_shared_cache).
[SQLITE_OPEN_EXRESCODE](#SQLITE_OPEN_AUTOPROXY)
The database connection comes up in "extended result code mode". In other words, the database behaves as if [sqlite3_extended_result_codes(db,1)](#sqlite3_extended_result_codes) were called on the database connection as soon as the connection is created. In addition to setting the extended result code mode, this flag also causes [sqlite3_open_v2()](#sqlite3_open) to return an extended result code.
[SQLITE_OPEN_NOFOLLOW](#SQLITE_OPEN_AUTOPROXY)
The database filename is not allowed to contain a symbolic link
If the 3rd parameter to sqlite3_open_v2() is not one of the required combinations shown above optionally combined with other [SQLITE_OPEN\_\* bits](#SQLITE_OPEN_AUTOPROXY) then the behavior is undefined. Historic versions of SQLite have silently ignored surplus bits in the flags parameter to sqlite3_open_v2(), however that behavior might not be carried through into future versions of SQLite and so applications should not rely upon it. Note in particular that the SQLITE_OPEN_EXCLUSIVE flag is a no-op for sqlite3_open_v2(). The SQLITE_OPEN_EXCLUSIVE does \*not\* cause the open to fail if the database already exists. The SQLITE_OPEN_EXCLUSIVE flag is intended for use by the [VFS interface](#sqlite3_vfs) only, and not by sqlite3_open_v2().
The fourth parameter to sqlite3_open_v2() is the name of the [sqlite3_vfs](#sqlite3_vfs) object that defines the operating system interface that the new database connection should use. If the fourth parameter is a NULL pointer then the default [sqlite3_vfs](#sqlite3_vfs) object is used.
If the filename is ":memory:", then a private, temporary in-memory database is created for the connection. This in-memory database will vanish when the database connection is closed. Future versions of SQLite might make use of additional special filenames that begin with the ":" character. It is recommended that when a database filename actually does begin with a ":" character you should prefix the filename with a pathname such as "./" to avoid ambiguity.
If the filename is an empty string, then a private, temporary on-disk database will be created. This private database will be automatically deleted as soon as the database connection is closed.
### URI Filenames
If [URI filename](uri.md) interpretation is enabled, and the filename argument begins with "file:", then the filename is interpreted as a URI. URI filename interpretation is enabled if the [SQLITE_OPEN_URI](#SQLITE_OPEN_AUTOPROXY) flag is set in the third argument to sqlite3_open_v2(), or if it has been enabled globally using the [SQLITE_CONFIG_URI](#sqliteconfiguri) option with the [sqlite3_config()](#sqlite3_config) method or by the [SQLITE_USE_URI](compile.md#use_uri) compile-time option. URI filename interpretation is turned off by default, but future releases of SQLite might enable URI filename interpretation by default. See "[URI filenames](uri.md)" for additional information.
URI filenames are parsed according to RFC 3986. If the URI contains an authority, then it must be either an empty string or the string "localhost". If the authority is not an empty string or "localhost", an error is returned to the caller. The fragment component of a URI, if present, is ignored.
SQLite uses the path component of the URI as the name of the disk file which contains the database. If the path begins with a '/' character, then it is interpreted as an absolute path. If the path does not begin with a '/' (meaning that the authority section is omitted from the URI) then the path is interpreted as a relative path. On windows, the first component of an absolute path is a drive specification (e.g. "C:").
The query component of a URI may contain parameters that are interpreted either by SQLite itself, or by a [custom VFS implementation](vfs.md). SQLite and its built-in [VFSes](vfs.md) interpret the following query parameters:
- **vfs**: The "vfs" parameter may be used to specify the name of a VFS object that provides the operating system interface that should be used to access the database file on disk. If this option is set to an empty string the default VFS object is used. Specifying an unknown VFS is an error. If sqlite3_open_v2() is used and the vfs option is present, then the VFS specified by the option takes precedence over the value passed as the fourth parameter to sqlite3_open_v2().
- **mode**: The mode parameter may be set to either "ro", "rw", "rwc", or "memory". Attempting to set it to any other value is an error. If "ro" is specified, then the database is opened for read-only access, just as if the [SQLITE_OPEN_READONLY](#SQLITE_OPEN_AUTOPROXY) flag had been set in the third argument to sqlite3_open_v2(). If the mode option is set to "rw", then the database is opened for read-write (but not create) access, as if SQLITE_OPEN_READWRITE (but not SQLITE_OPEN_CREATE) had been set. Value "rwc" is equivalent to setting both SQLITE_OPEN_READWRITE and SQLITE_OPEN_CREATE. If the mode option is set to "memory" then a pure [in-memory database](inmemorydb.md) that never reads or writes from disk is used. It is an error to specify a value for the mode parameter that is less restrictive than that specified by the flags passed in the third parameter to sqlite3_open_v2().
- **cache**: The cache parameter may be set to either "shared" or "private". Setting it to "shared" is equivalent to setting the SQLITE_OPEN_SHAREDCACHE bit in the flags argument passed to sqlite3_open_v2(). Setting the cache parameter to "private" is equivalent to setting the SQLITE_OPEN_PRIVATECACHE bit. If sqlite3_open_v2() is used and the "cache" parameter is present in a URI filename, its value overrides any behavior requested by setting SQLITE_OPEN_PRIVATECACHE or SQLITE_OPEN_SHAREDCACHE flag.
- **psow**: The psow parameter indicates whether or not the [powersafe overwrite](psow.md) property does or does not apply to the storage media on which the database file resides.
- **nolock**: The nolock parameter is a boolean query parameter which if set disables file locking in rollback journal modes. This is useful for accessing a database on a filesystem that does not support locking. Caution: Database corruption might result if two or more processes write to the same database and any one of those processes uses nolock=1.
- **immutable**: The immutable parameter is a boolean query parameter that indicates that the database file is stored on read-only media. When immutable is set, SQLite assumes that the database file cannot be changed, even by a process with higher privilege, and so the database is opened read-only and all locking and change detection is disabled. Caution: Setting the immutable property on a database file that does in fact change can result in incorrect query results and/or [SQLITE_CORRUPT](#SQLITE_ABORT) errors. See also: [SQLITE_IOCAP_IMMUTABLE](#SQLITE_IOCAP_ATOMIC).
Specifying an unknown parameter in the query component of a URI is not an error. Future versions of SQLite might understand additional query parameters. See "[query parameters with special meaning to SQLite](uri.md#coreqp)" for additional information.
### URI filename examples
URI filenames
Results
file:data.db
Open the file "data.db" in the current directory.
file:/home/fred/data.db\
file:///home/fred/data.db\
file://localhost/home/fred/data.db\
Open the database file "/home/fred/data.db".
file://darkstar/home/fred/data.db
An error. "darkstar" is not a recognized authority.
file:///C:/Documents%20and%20Settings/fred/Desktop/data.db
Windows only: Open the file "data.db" on fred's desktop on drive C:. Note that the %20 escaping in this example is not strictly necessary - space characters can be used literally in URI filenames.
file:data.db?mode=ro&cache=private
Open file "data.db" in the current directory for read-only access. Regardless of whether or not shared-cache mode is enabled by default, use a private cache.
file:/home/fred/data.db?vfs=unix-dotfile
Open file "/home/fred/data.db". Use the special VFS "unix-dotfile" that uses dot-files in place of posix advisory locking.
file:data.db?mode=readonly
An error. "readonly" is not a valid option for the "mode" parameter. Use "ro" instead: "file:data.db?mode=ro".
URI hexadecimal escape sequences (%HH) are supported within the path and query components of a URI. A hexadecimal escape sequence consists of a percent sign - "%" - followed by exactly two hexadecimal digits specifying an octet value. Before the path or query components of a URI filename are interpreted, they are encoded using UTF-8 and all hexadecimal escape sequences replaced by a single byte containing the corresponding octet. If this process generates an invalid UTF-8 encoding, the results are undefined.
**Note to Windows users:** The encoding used for the filename argument of sqlite3_open() and sqlite3_open_v2() must be UTF-8, not whatever codepage is currently defined. Filenames containing international characters must be converted to UTF-8 prior to passing them into sqlite3_open() or sqlite3_open_v2().
**Note to Windows Runtime users:** The temporary directory must be set prior to calling sqlite3_open() or sqlite3_open_v2(). Otherwise, various features that require the use of temporary files may fail.
See also: [sqlite3_temp_directory](#sqlite3_temp_directory)
------------------------------------------------------------------------
## The pre-update hook.
> \
> \#if defined(SQLITE_ENABLE_PREUPDATE_HOOK)\
> void \*sqlite3_preupdate_hook(\
> sqlite3 \*db,\
> void(\*xPreUpdate)(\
> void \*pCtx, /\* Copy of third arg to preupdate_hook() \*/\
> sqlite3 \*db, /\* Database handle \*/\
> int op, /\* SQLITE_UPDATE, DELETE or INSERT \*/\
> char const \*zDb, /\* Database name \*/\
> char const \*zName, /\* Table name \*/\
> sqlite3_int64 iKey1, /\* Rowid of row about to be deleted/updated \*/\
> sqlite3_int64 iKey2 /\* New rowid value (for a rowid UPDATE) \*/\
> ),\
> void\*\
> );\
> int sqlite3_preupdate_old(sqlite3 \*, int, sqlite3_value \*\*);\
> int sqlite3_preupdate_count(sqlite3 \*);\
> int sqlite3_preupdate_depth(sqlite3 \*);\
> int sqlite3_preupdate_new(sqlite3 \*, int, sqlite3_value \*\*);\
> int sqlite3_preupdate_blobwrite(sqlite3 \*);\
> \#endif\
These interfaces are only available if SQLite is compiled using the [SQLITE_ENABLE_PREUPDATE_HOOK](compile.md#enable_preupdate_hook) compile-time option.
The [sqlite3_preupdate_hook()](#sqlite3_preupdate_blobwrite) interface registers a callback function that is invoked prior to each [INSERT](lang_insert.md), [UPDATE](lang_update.md), and [DELETE](lang_delete.md) operation on a database table. At most one preupdate hook may be registered at a time on a single [database connection](#sqlite3); each call to [sqlite3_preupdate_hook()](#sqlite3_preupdate_blobwrite) overrides the previous setting. The preupdate hook is disabled by invoking [sqlite3_preupdate_hook()](#sqlite3_preupdate_blobwrite) with a NULL pointer as the second parameter. The third parameter to [sqlite3_preupdate_hook()](#sqlite3_preupdate_blobwrite) is passed through as the first parameter to callbacks.
The preupdate hook only fires for changes to real database tables; the preupdate hook is not invoked for changes to [virtual tables](vtab.md) or to system tables like sqlite_sequence or sqlite_stat1.
The second parameter to the preupdate callback is a pointer to the [database connection](#sqlite3) that registered the preupdate hook. The third parameter to the preupdate callback is one of the constants [SQLITE_INSERT](#SQLITE_ALTER_TABLE), [SQLITE_DELETE](#SQLITE_ALTER_TABLE), or [SQLITE_UPDATE](#SQLITE_ALTER_TABLE) to identify the kind of update operation that is about to occur. The fourth parameter to the preupdate callback is the name of the database within the database connection that is being modified. This will be "main" for the main database or "temp" for TEMP tables or the name given after the AS keyword in the [ATTACH](lang_attach.md) statement for attached databases. The fifth parameter to the preupdate callback is the name of the table that is being modified.
For an UPDATE or DELETE operation on a [rowid table](rowidtable.md), the sixth parameter passed to the preupdate callback is the initial [rowid](lang_createtable.md#rowid) of the row being modified or deleted. For an INSERT operation on a rowid table, or any operation on a WITHOUT ROWID table, the value of the sixth parameter is undefined. For an INSERT or UPDATE on a rowid table the seventh parameter is the final rowid value of the row being inserted or updated. The value of the seventh parameter passed to the callback function is not defined for operations on WITHOUT ROWID tables, or for DELETE operations on rowid tables.
The sqlite3_preupdate_hook(D,C,P) function returns the P argument from the previous call on the same [database connection](#sqlite3) D, or NULL for the first call on D.
The [sqlite3_preupdate_old()](#sqlite3_preupdate_blobwrite), [sqlite3_preupdate_new()](#sqlite3_preupdate_blobwrite), [sqlite3_preupdate_count()](#sqlite3_preupdate_blobwrite), and [sqlite3_preupdate_depth()](#sqlite3_preupdate_blobwrite) interfaces provide additional information about a preupdate event. These routines may only be called from within a preupdate callback. Invoking any of these routines from outside of a preupdate callback or with a [database connection](#sqlite3) pointer that is different from the one supplied to the preupdate callback results in undefined and probably undesirable behavior.
The [sqlite3_preupdate_count(D)](#sqlite3_preupdate_blobwrite) interface returns the number of columns in the row that is being inserted, updated, or deleted.
The [sqlite3_preupdate_old(D,N,P)](#sqlite3_preupdate_blobwrite) interface writes into P a pointer to a [protected sqlite3_value](#sqlite3_value) that contains the value of the Nth column of the table row before it is updated. The N parameter must be between 0 and one less than the number of columns or the behavior will be undefined. This must only be used within SQLITE_UPDATE and SQLITE_DELETE preupdate callbacks; if it is used by an SQLITE_INSERT callback then the behavior is undefined. The [sqlite3_value](#sqlite3_value) that P points to will be destroyed when the preupdate callback returns.
The [sqlite3_preupdate_new(D,N,P)](#sqlite3_preupdate_blobwrite) interface writes into P a pointer to a [protected sqlite3_value](#sqlite3_value) that contains the value of the Nth column of the table row after it is updated. The N parameter must be between 0 and one less than the number of columns or the behavior will be undefined. This must only be used within SQLITE_INSERT and SQLITE_UPDATE preupdate callbacks; if it is used by an SQLITE_DELETE callback then the behavior is undefined. The [sqlite3_value](#sqlite3_value) that P points to will be destroyed when the preupdate callback returns.
The [sqlite3_preupdate_depth(D)](#sqlite3_preupdate_blobwrite) interface returns 0 if the preupdate callback was invoked as a result of a direct insert, update, or delete operation; or 1 for inserts, updates, or deletes invoked by top-level triggers; or 2 for changes resulting from triggers called by top-level triggers; and so forth.
When the [sqlite3_blob_write()](#sqlite3_blob_write) API is used to update a blob column, the pre-update hook is invoked with SQLITE_DELETE, because the new values are not yet available. In this case, when a callback made with op==SQLITE_DELETE is actually a write using the sqlite3_blob_write() API, the [sqlite3_preupdate_blobwrite()](#sqlite3_preupdate_blobwrite) returns the index of the column being written. In other cases, where the pre-update hook is being invoked for some other reason, including a regular DELETE, sqlite3_preupdate_blobwrite() returns -1.
See also: [sqlite3_update_hook()](#sqlite3_update_hook)
------------------------------------------------------------------------
## Deprecated Tracing And Profiling Functions
> \
> void \*sqlite3_trace(sqlite3\*,\
> void(\*xTrace)(void\*,const char\*), void\*);\
> void \*sqlite3_profile(sqlite3\*,\
> void(\*xProfile)(void\*,const char\*,sqlite3_uint64), void\*);\
These routines are deprecated. Use the [sqlite3_trace_v2()](#sqlite3_trace_v2) interface instead of the routines described here.
These routines register callback functions that can be used for tracing and profiling the execution of SQL statements.
The callback function registered by sqlite3_trace() is invoked at various times when an SQL statement is being run by [sqlite3_step()](#sqlite3_step). The sqlite3_trace() callback is invoked with a UTF-8 rendering of the SQL statement text as the statement first begins executing. Additional sqlite3_trace() callbacks might occur as each triggered subprogram is entered. The callbacks for triggers contain a UTF-8 SQL comment that identifies the trigger.
The [SQLITE_TRACE_SIZE_LIMIT](compile.md#trace_size_limit) compile-time option can be used to limit the length of [bound parameter](lang_expr.md#varparam) expansion in the output of sqlite3_trace().
The callback function registered by sqlite3_profile() is invoked as each SQL statement finishes. The profile callback contains the original statement text and an estimate of wall-clock time of how long that statement took to run. The profile callback time is in units of nanoseconds, however the current implementation is only capable of millisecond resolution so the six least significant digits in the time are meaningless. Future versions of SQLite might provide greater resolution on the profiler callback. Invoking either [sqlite3_trace()](#sqlite3_profile) or [sqlite3_trace_v2()](#sqlite3_trace_v2) will cancel the profile callback.
------------------------------------------------------------------------
## Setting The Result Of An SQL Function
> \
> void sqlite3_result_blob(sqlite3_context\*, const void\*, int, void(\*)(void\*));\
> void sqlite3_result_blob64(sqlite3_context\*,const void\*,\
> sqlite3_uint64,void(\*)(void\*));\
> void sqlite3_result_double(sqlite3_context\*, double);\
> void sqlite3_result_error(sqlite3_context\*, const char\*, int);\
> void sqlite3_result_error16(sqlite3_context\*, const void\*, int);\
> void sqlite3_result_error_toobig(sqlite3_context\*);\
> void sqlite3_result_error_nomem(sqlite3_context\*);\
> void sqlite3_result_error_code(sqlite3_context\*, int);\
> void sqlite3_result_int(sqlite3_context\*, int);\
> void sqlite3_result_int64(sqlite3_context\*, sqlite3_int64);\
> void sqlite3_result_null(sqlite3_context\*);\
> void sqlite3_result_text(sqlite3_context\*, const char\*, int, void(\*)(void\*));\
> void sqlite3_result_text64(sqlite3_context\*, const char \*z, sqlite3_uint64 n,\
> void(\*)(void\*), unsigned char encoding);\
> void sqlite3_result_text16(sqlite3_context\*, const void\*, int, void(\*)(void\*));\
> void sqlite3_result_text16le(sqlite3_context\*, const void\*, int,void(\*)(void\*));\
> void sqlite3_result_text16be(sqlite3_context\*, const void\*, int,void(\*)(void\*));\
> void sqlite3_result_value(sqlite3_context\*, sqlite3_value\*);\
> void sqlite3_result_pointer(sqlite3_context\*, void\*,const char\*,void(\*)(void\*));\
> void sqlite3_result_zeroblob(sqlite3_context\*, int n);\
> int sqlite3_result_zeroblob64(sqlite3_context\*, sqlite3_uint64 n);\
These routines are used by the xFunc or xFinal callbacks that implement SQL functions and aggregates. See [sqlite3_create_function()](#sqlite3_create_function) and [sqlite3_create_function16()](#sqlite3_create_function) for additional information.
These functions work very much like the [parameter binding](#sqlite3_bind_blob) family of functions used to bind values to host parameters in prepared statements. Refer to the [SQL parameter](#sqlite3_bind_blob) documentation for additional information.
The sqlite3_result_blob() interface sets the result from an application-defined function to be the BLOB whose content is pointed to by the second parameter and which is N bytes long where N is the third parameter.
The sqlite3_result_zeroblob(C,N) and sqlite3_result_zeroblob64(C,N) interfaces set the result of the application-defined function to be a BLOB containing all zero bytes and N bytes in size.
The sqlite3_result_double() interface sets the result from an application-defined function to be a floating point value specified by its 2nd argument.
The sqlite3_result_error() and sqlite3_result_error16() functions cause the implemented SQL function to throw an exception. SQLite uses the string pointed to by the 2nd parameter of sqlite3_result_error() or sqlite3_result_error16() as the text of an error message. SQLite interprets the error message string from sqlite3_result_error() as UTF-8. SQLite interprets the string from sqlite3_result_error16() as UTF-16 using the same [byte-order determination rules](#byteorderdeterminationrules) as [sqlite3_bind_text16()](#sqlite3_bind_blob). If the third parameter to sqlite3_result_error() or sqlite3_result_error16() is negative then SQLite takes as the error message all text up through the first zero character. If the third parameter to sqlite3_result_error() or sqlite3_result_error16() is non-negative then SQLite takes that many bytes (not characters) from the 2nd parameter as the error message. The sqlite3_result_error() and sqlite3_result_error16() routines make a private copy of the error message text before they return. Hence, the calling function can deallocate or modify the text after they return without harm. The sqlite3_result_error_code() function changes the error code returned by SQLite as a result of an error in a function. By default, the error code is SQLITE_ERROR. A subsequent call to sqlite3_result_error() or sqlite3_result_error16() resets the error code to SQLITE_ERROR.
The sqlite3_result_error_toobig() interface causes SQLite to throw an error indicating that a string or BLOB is too long to represent.
The sqlite3_result_error_nomem() interface causes SQLite to throw an error indicating that a memory allocation failed.
The sqlite3_result_int() interface sets the return value of the application-defined function to be the 32-bit signed integer value given in the 2nd argument. The sqlite3_result_int64() interface sets the return value of the application-defined function to be the 64-bit signed integer value given in the 2nd argument.
The sqlite3_result_null() interface sets the return value of the application-defined function to be NULL.
The sqlite3_result_text(), sqlite3_result_text16(), sqlite3_result_text16le(), and sqlite3_result_text16be() interfaces set the return value of the application-defined function to be a text string which is represented as UTF-8, UTF-16 native byte order, UTF-16 little endian, or UTF-16 big endian, respectively. The sqlite3_result_text64(C,Z,N,D,E) interface sets the return value of an application-defined function to be a text string in an encoding specified the E parameter, which must be one of [SQLITE_UTF8](#sqliteutf8), [SQLITE_UTF8_ZT](#sqliteutf8zt), [SQLITE_UTF16](#sqliteutf16), [SQLITE_UTF16BE](#sqliteutf16be), or [SQLITE_UTF16LE](#sqliteutf16le). The special value [SQLITE_UTF8_ZT](#sqliteutf8zt) means that the result text is both UTF-8 and zero-terminated. In other words, SQLITE_UTF8_ZT means that the Z array holds at least N+1 bytes and that the Z\[N\] is zero. SQLite takes the text result from the application from the 2nd parameter of the sqlite3_result_text\* interfaces. If the 3rd parameter to any of the sqlite3_result_text\* interfaces other than sqlite3_result_text64() is negative, then SQLite computes the string length itself by searching the 2nd parameter for the first zero character. If the 3rd parameter to the sqlite3_result_text\* interfaces is non-negative, then as many bytes (not characters) of the text pointed to by the 2nd parameter are taken as the application-defined function result. If the 3rd parameter is non-negative, then it must be the byte offset into the string where the NUL terminator would appear if the string were NUL terminated. If any NUL characters occur in the string at a byte offset that is less than the value of the 3rd parameter, then the resulting string will contain embedded NULs and the result of expressions operating on strings with embedded NULs is undefined. If the 4th parameter to the sqlite3_result_text\* interfaces or sqlite3_result_blob is a non-NULL pointer, then SQLite calls that function as the destructor on the text or BLOB result when it has finished using that result. If the 4th parameter to the sqlite3_result_text\* interfaces or to sqlite3_result_blob is the special constant SQLITE_STATIC, then SQLite assumes that the text or BLOB result is in constant space and does not copy the content of the parameter nor call a destructor on the content when it has finished using that result. If the 4th parameter to the sqlite3_result_text\* interfaces or sqlite3_result_blob is the special constant SQLITE_TRANSIENT then SQLite makes a copy of the result into space obtained from [sqlite3_malloc()](#sqlite3_free) before it returns.
For the sqlite3_result_text16(), sqlite3_result_text16le(), and sqlite3_result_text16be() routines, and for sqlite3_result_text64() when the encoding is not UTF8, if the input UTF16 begins with a byte-order mark (BOM, U+FEFF) then the BOM is removed from the string and the rest of the string is interpreted according to the byte-order specified by the BOM. The byte-order specified by the BOM at the beginning of the text overrides the byte-order specified by the interface procedure. So, for example, if sqlite3_result_text16le() is invoked with text that begins with bytes 0xfe, 0xff (a big-endian byte-order mark) then the first two bytes of input are skipped and the remaining input is interpreted as UTF16BE text.
For UTF16 input text to the sqlite3_result_text16(), sqlite3_result_text16be(), sqlite3_result_text16le(), and sqlite3_result_text64() routines, if the text contains invalid UTF16 characters, the invalid characters might be converted into the unicode replacement character, U+FFFD.
The sqlite3_result_value() interface sets the result of the application-defined function to be a copy of the [unprotected sqlite3_value](#sqlite3_value) object specified by the 2nd parameter. The sqlite3_result_value() interface makes a copy of the [sqlite3_value](#sqlite3_value) so that the [sqlite3_value](#sqlite3_value) specified in the parameter may change or be deallocated after sqlite3_result_value() returns without harm. A [protected sqlite3_value](#sqlite3_value) object may always be used where an [unprotected sqlite3_value](#sqlite3_value) object is required, so either kind of [sqlite3_value](#sqlite3_value) object can be used with this interface.
The sqlite3_result_pointer(C,P,T,D) interface sets the result to an SQL NULL value, just like [sqlite3_result_null(C)](#sqlite3_result_blob), except that it also associates the host-language pointer P or type T with that NULL value such that the pointer can be retrieved within an [application-defined SQL function](appfunc.md) using [sqlite3_value_pointer()](#sqlite3_value_blob). If the D parameter is not NULL, then it is a pointer to a destructor for the P parameter. SQLite invokes D with P as its only argument when SQLite is finished with P. The T parameter should be a static string and preferably a string literal. The sqlite3_result_pointer() routine is part of the [pointer passing interface](bindptr.md) added for SQLite 3.20.0.
If these routines are called from within a different thread than the one containing the application-defined function that received the [sqlite3_context](#sqlite3_context) pointer, the results are undefined.
------------------------------------------------------------------------
## SQLite Runtime Status
> \
> int sqlite3_status(int op, int \*pCurrent, int \*pHighwater, int resetFlag);\
> int sqlite3_status64(\
> int op,\
> sqlite3_int64 \*pCurrent,\
> sqlite3_int64 \*pHighwater,\
> int resetFlag\
> );\
These interfaces are used to retrieve runtime status information about the performance of SQLite, and optionally to reset various highwater marks. The first argument is an integer code for the specific parameter to measure. Recognized integer codes are of the form [SQLITE_STATUS\_...](#SQLITE_STATUS_MALLOC_COUNT). The current value of the parameter is returned into \*pCurrent. The highest recorded value is returned in \*pHighwater. If the resetFlag is true, then the highest record value is reset after \*pHighwater is written. Some parameters do not record the highest value. For those parameters nothing is written into \*pHighwater and the resetFlag is ignored. Other parameters record only the highwater mark and not the current value. For these latter parameters nothing is written into \*pCurrent.
The sqlite3_status() and sqlite3_status64() routines return SQLITE_OK on success and a non-zero [error code](rescode.md) on failure.
If either the current value or the highwater mark is too large to be represented by a 32-bit integer, then the values returned by sqlite3_status() are undefined.
See also: [sqlite3_db_status()](#sqlite3_db_status)
------------------------------------------------------------------------
## Prepared Statement Scan Status
> \
> int sqlite3_stmt_scanstatus(\
> sqlite3_stmt \*pStmt, /\* Prepared statement for which info desired \*/\
> int idx, /\* Index of loop to report on \*/\
> int iScanStatusOp, /\* Information desired. SQLITE_SCANSTAT\_\* \*/\
> void \*pOut /\* Result written here \*/\
> );\
> int sqlite3_stmt_scanstatus_v2(\
> sqlite3_stmt \*pStmt, /\* Prepared statement for which info desired \*/\
> int idx, /\* Index of loop to report on \*/\
> int iScanStatusOp, /\* Information desired. SQLITE_SCANSTAT\_\* \*/\
> int flags, /\* Mask of flags defined below \*/\
> void \*pOut /\* Result written here \*/\
> );\
These interfaces return information about the predicted and measured performance for pStmt. Advanced applications can use this interface to compare the predicted and the measured performance and issue warnings and/or rerun [ANALYZE](lang_analyze.md) if discrepancies are found.
Since this interface is expected to be rarely used, it is only available if SQLite is compiled using the [SQLITE_ENABLE_STMT_SCANSTATUS](compile.md#enable_stmt_scanstatus) compile-time option.
The "iScanStatusOp" parameter determines which status information to return. The "iScanStatusOp" must be one of the [scanstatus options](#SQLITE_SCANSTAT_EST) or the behavior of this interface is undefined. The requested measurement is written into a variable pointed to by the "pOut" parameter.
The "flags" parameter must be passed a mask of flags. At present only one flag is defined - [SQLITE_SCANSTAT_COMPLEX](#SQLITE_SCANSTAT_COMPLEX). If SQLITE_SCANSTAT_COMPLEX is specified, then status information is available for all elements of a query plan that are reported by "[EXPLAIN QUERY PLAN](eqp.md)" output. If SQLITE_SCANSTAT_COMPLEX is not specified, then only query plan elements that correspond to query loops (the "SCAN..." and "SEARCH..." elements of the EXPLAIN QUERY PLAN output) are available. Invoking API sqlite3_stmt_scanstatus() is equivalent to calling sqlite3_stmt_scanstatus_v2() with a zeroed flags parameter.
Parameter "idx" identifies the specific query element to retrieve statistics for. Query elements are numbered starting from zero. A value of -1 may retrieve statistics for the entire query. If idx is out of range - less than -1 or greater than or equal to the total number of query elements used to implement the statement - a non-zero value is returned and the variable that pOut points to is unchanged.
See also: [sqlite3_stmt_scanstatus_reset()](#sqlite3_stmt_scanstatus_reset) and the [nexec and ncycle](bytecodevtab.md#nexec) columns of the [bytecode virtual table](bytecodevtab.md).
------------------------------------------------------------------------
## Add Content To A Dynamic String
> \
> void sqlite3_str_appendf(sqlite3_str\*, const char \*zFormat, ...);\
> void sqlite3_str_vappendf(sqlite3_str\*, const char \*zFormat, va_list);\
> void sqlite3_str_append(sqlite3_str\*, const char \*zIn, int N);\
> void sqlite3_str_appendall(sqlite3_str\*, const char \*zIn);\
> void sqlite3_str_appendchar(sqlite3_str\*, int N, char C);\
> void sqlite3_str_reset(sqlite3_str\*);\
> void sqlite3_str_truncate(sqlite3_str\*,int N);\
These interfaces add or remove content to an sqlite3_str object previously obtained from [sqlite3_str_new()](#sqlite3_str_new).
The [sqlite3_str_appendf(X,F,...)](#sqlite3_str_append) and [sqlite3_str_vappendf(X,F,V)](#sqlite3_str_append) interfaces uses the [built-in printf](printf.md) functionality of SQLite to append formatted text onto the end of [sqlite3_str](#sqlite3_str) object X.
The [sqlite3_str_append(X,S,N)](#sqlite3_str_append) method appends exactly N bytes from string S onto the end of the [sqlite3_str](#sqlite3_str) object X. N must be non-negative. S must contain at least N non-zero bytes of content. To append a zero-terminated string in its entirety, use the [sqlite3_str_appendall()](#sqlite3_str_append) method instead.
The [sqlite3_str_appendall(X,S)](#sqlite3_str_append) method appends the complete content of zero-terminated string S onto the end of [sqlite3_str](#sqlite3_str) object X.
The [sqlite3_str_appendchar(X,N,C)](#sqlite3_str_append) method appends N copies of the single-byte character C onto the end of [sqlite3_str](#sqlite3_str) object X. This method can be used, for example, to add whitespace indentation.
The [sqlite3_str_reset(X)](#sqlite3_str_append) method resets the string under construction inside [sqlite3_str](#sqlite3_str) object X back to zero bytes in length.
The [sqlite3_str_truncate(X,N)](#sqlite3_str_append) method changes the length of the string under construction to be N bytes or less. This routine is a no-op if N is negative or if the string is already N bytes or smaller in size.
These methods do not return a result code. If an error occurs, that fact is recorded in the [sqlite3_str](#sqlite3_str) object and can be recovered by a subsequent call to [sqlite3_str_errcode(X)](#sqlite3_str_errcode).
------------------------------------------------------------------------
## Status Of A Dynamic String
> \
> int sqlite3_str_errcode(sqlite3_str\*);\
> int sqlite3_str_length(sqlite3_str\*);\
> char \*sqlite3_str_value(sqlite3_str\*);\
These interfaces return the current status of an [sqlite3_str](#sqlite3_str) object.
If any prior errors have occurred while constructing the dynamic string in sqlite3_str X, then the [sqlite3_str_errcode(X)](#sqlite3_str_errcode) method will return an appropriate error code. The [sqlite3_str_errcode(X)](#sqlite3_str_errcode) method returns [SQLITE_NOMEM](#SQLITE_ABORT) following any out-of-memory error, or [SQLITE_TOOBIG](#SQLITE_ABORT) if the size of the dynamic string exceeds [SQLITE_MAX_LENGTH](limits.md#max_length), or [SQLITE_OK](#SQLITE_ABORT) if there have been no errors.
The [sqlite3_str_length(X)](#sqlite3_str_errcode) method returns the current length, in bytes, of the dynamic string under construction in [sqlite3_str](#sqlite3_str) object X. The length returned by [sqlite3_str_length(X)](#sqlite3_str_errcode) does not include the zero-termination byte.
The [sqlite3_str_value(X)](#sqlite3_str_errcode) method returns a pointer to the current content of the dynamic string under construction in X. The value returned by [sqlite3_str_value(X)](#sqlite3_str_errcode) is managed by the sqlite3_str object X and might be freed or altered by any subsequent method on the same [sqlite3_str](#sqlite3_str) object. Applications must not use the pointer returned by [sqlite3_str_value(X)](#sqlite3_str_errcode) after any subsequent method call on the same object. Applications may change the content of the string returned by [sqlite3_str_value(X)](#sqlite3_str_errcode) as long as they do not write into any bytes outside the range of 0 to [sqlite3_str_length(X)](#sqlite3_str_errcode) and do not read or write any byte after any subsequent sqlite3_str method call.
------------------------------------------------------------------------
## Finalize A Dynamic String
> \
> char \*sqlite3_str_finish(sqlite3_str\*);\
> void sqlite3_str_free(sqlite3_str\*);\
The [sqlite3_str_finish(X)](#sqlite3_str_finish) interface destroys the sqlite3_str object X and returns a pointer to a memory buffer obtained from [sqlite3_malloc64()](#sqlite3_free) that contains the constructed string. The calling application should pass the returned value to [sqlite3_free()](#sqlite3_free) to avoid a memory leak. The [sqlite3_str_finish(X)](#sqlite3_str_finish) interface may return a NULL pointer if any errors were encountered during construction of the string. The [sqlite3_str_finish(X)](#sqlite3_str_finish) interface might also return a NULL pointer if the string in [sqlite3_str](#sqlite3_str) object X is zero bytes long.
The [sqlite3_str_free(X)](#sqlite3_str_finish) interface destroys both the sqlite3_str object X and the string content it contains. Calling sqlite3_str_free(X) is the equivalent of calling [sqlite3_free](#sqlite3_free)(sqlite3_str_finish(X)).
------------------------------------------------------------------------
## String Comparison
> \
> int sqlite3_stricmp(const char \*, const char \*);\
> int sqlite3_strnicmp(const char \*, const char \*, int);\
The [sqlite3_stricmp()](#sqlite3_stricmp) and [sqlite3_strnicmp()](#sqlite3_stricmp) APIs allow applications and extensions to compare the contents of two buffers containing UTF-8 strings in a case-independent fashion, using the same definition of "case independence" that SQLite uses internally when comparing identifiers.
------------------------------------------------------------------------
## Total Number Of Rows Modified
> \
> int sqlite3_total_changes(sqlite3\*);\
> sqlite3_int64 sqlite3_total_changes64(sqlite3\*);\
These functions return the total number of rows inserted, modified or deleted by all [INSERT](lang_insert.md), [UPDATE](lang_update.md) or [DELETE](lang_delete.md) statements completed since the database connection was opened, including those executed as part of trigger programs. The two functions are identical except for the type of the return value and that if the number of rows modified by the connection exceeds the maximum value supported by type "int", then the return value of sqlite3_total_changes() is undefined. Executing any other type of SQL statement does not affect the value returned by sqlite3_total_changes().
Changes made as part of [foreign key actions](foreignkeys.md#fk_actions) are included in the count, but those made as part of REPLACE constraint resolution are not. Changes to a view that are intercepted by INSTEAD OF triggers are not counted.
The [sqlite3_total_changes(D)](#sqlite3_total_changes) interface only reports the number of rows that changed due to SQL statement run against database connection D. Any changes by other database connections are ignored. To detect changes against a database file from other database connections use the [PRAGMA data_version](pragma.md#pragma_data_version) command or the [SQLITE_FCNTL_DATA_VERSION](#sqlitefcntldataversion) [file control](#sqlite3_file_control).
If a separate thread makes changes on the same database connection while [sqlite3_total_changes()](#sqlite3_total_changes) is running then the value returned is unpredictable and not meaningful.
See also:
- the [sqlite3_changes()](#sqlite3_changes) interface
- the [count_changes pragma](pragma.md#pragma_count_changes)
- the [changes() SQL function](lang_corefunc.md#changes)
- the [data_version pragma](pragma.md#pragma_data_version)
- the [SQLITE_FCNTL_DATA_VERSION](#sqlitefcntldataversion) [file control](#sqlite3_file_control)
------------------------------------------------------------------------
## Obtain Values For URI Parameters
> \
> const char \*sqlite3_uri_parameter(sqlite3_filename z, const char \*zParam);\
> int sqlite3_uri_boolean(sqlite3_filename z, const char \*zParam, int bDefault);\
> sqlite3_int64 sqlite3_uri_int64(sqlite3_filename, const char\*, sqlite3_int64);\
> const char \*sqlite3_uri_key(sqlite3_filename z, int N);\
These are utility routines, useful to [custom VFS implementations](vfs.md), that check if a database file was a URI that contained a specific query parameter, and if so obtains the value of that query parameter.
The first parameter to these interfaces (hereafter referred to as F) must be one of:
- A database filename pointer created by the SQLite core and passed into the xOpen() method of a VFS implementation, or
- A filename obtained from [sqlite3_db_filename()](#sqlite3_db_filename), or
- A new filename constructed using [sqlite3_create_filename()](#sqlite3_create_filename).
If the F parameter is not one of the above, then the behavior is undefined and probably undesirable. Older versions of SQLite were more tolerant of invalid F parameters than newer versions.
If F is a suitable filename (as described in the previous paragraph) and if P is the name of the query parameter, then sqlite3_uri_parameter(F,P) returns the value of the P parameter if it exists or a NULL pointer if P does not appear as a query parameter on F. If P is a query parameter of F and it has no explicit value, then sqlite3_uri_parameter(F,P) returns a pointer to an empty string.
The sqlite3_uri_boolean(F,P,B) routine assumes that P is a boolean parameter and returns true (1) or false (0) according to the value of P. The sqlite3_uri_boolean(F,P,B) routine returns true (1) if the value of query parameter P is one of "yes", "true", or "on" in any case or if the value begins with a non-zero number. The sqlite3_uri_boolean(F,P,B) routines returns false (0) if the value of query parameter P is one of "no", "false", or "off" in any case or if the value begins with a numeric zero. If P is not a query parameter on F or if the value of P does not match any of the above, then sqlite3_uri_boolean(F,P,B) returns (B!=0).
The sqlite3_uri_int64(F,P,D) routine converts the value of P into a 64-bit signed integer and returns that integer, or D if P does not exist. If the value of P is something other than an integer, then zero is returned.
The sqlite3_uri_key(F,N) returns a pointer to the name (not the value) of the N-th query parameter for filename F, or a NULL pointer if N is less than zero or greater than the number of query parameters minus 1. The N value is zero-based so N should be 0 to obtain the name of the first query parameter, 1 for the second parameter, and so forth.
If F is a NULL pointer, then sqlite3_uri_parameter(F,P) returns NULL and sqlite3_uri_boolean(F,P,B) returns B. If F is not a NULL pointer and is not a database file pathname pointer that the SQLite core passed into the xOpen VFS method, then the behavior of this routine is undefined and probably undesirable.
Beginning with SQLite [version 3.31.0](releaselog/3_31_0.md) (2020-01-22) the input F parameter can also be the name of a rollback journal file or WAL file in addition to the main database file. Prior to version 3.31.0, these routines would only work if F was the name of the main database file. When the F parameter is the name of the rollback journal or WAL file, it has access to all the same query parameters as were found on the main database file.
See the [URI filename](uri.md) documentation for additional information.
------------------------------------------------------------------------
## Obtaining SQL Values
> \
> const void \*sqlite3_value_blob(sqlite3_value\*);\
> double sqlite3_value_double(sqlite3_value\*);\
> int sqlite3_value_int(sqlite3_value\*);\
> sqlite3_int64 sqlite3_value_int64(sqlite3_value\*);\
> void \*sqlite3_value_pointer(sqlite3_value\*, const char\*);\
> const unsigned char \*sqlite3_value_text(sqlite3_value\*);\
> const void \*sqlite3_value_text16(sqlite3_value\*);\
> const void \*sqlite3_value_text16le(sqlite3_value\*);\
> const void \*sqlite3_value_text16be(sqlite3_value\*);\
> int sqlite3_value_bytes(sqlite3_value\*);\
> int sqlite3_value_bytes16(sqlite3_value\*);\
> int sqlite3_value_type(sqlite3_value\*);\
> int sqlite3_value_numeric_type(sqlite3_value\*);\
> int sqlite3_value_nochange(sqlite3_value\*);\
> int sqlite3_value_frombind(sqlite3_value\*);\
**Summary:**
> **sqlite3_value_blob**
>
> →
>
> BLOB value
>
> **sqlite3_value_double**
>
> →
>
> REAL value
>
> **sqlite3_value_int**
>
> →
>
> 32-bit INTEGER value
>
> **sqlite3_value_int64**
>
> →
>
> 64-bit INTEGER value
>
> **sqlite3_value_pointer**
>
> →
>
> Pointer value
>
> **sqlite3_value_text**
>
> →
>
> UTF-8 TEXT value
>
> **sqlite3_value_text16**
>
> →
>
> UTF-16 TEXT value in the native byteorder
>
> **sqlite3_value_text16be**
>
> →
>
> UTF-16be TEXT value
>
> **sqlite3_value_text16le**
>
> →
>
> UTF-16le TEXT value
>
>
>
>
>
>
>
> **sqlite3_value_bytes**
>
> →
>
> Size of a BLOB or a UTF-8 TEXT in bytes
>
> **sqlite3_value_bytes16 **
>
> →
>
> Size of UTF-16 TEXT in bytes
>
> **sqlite3_value_type**
>
> →
>
> Default datatype of the value
>
> **sqlite3_value_numeric_type **
>
> →
>
> Best numeric datatype of the value
>
> **sqlite3_value_nochange **
>
> →
>
> True if the column is unchanged in an UPDATE against a virtual table.
>
> **sqlite3_value_frombind **
>
> →
>
> True if value originated from a [bound parameter](lang_expr.md#varparam)
**Details:**
These routines extract type, size, and content information from [protected sqlite3_value](#sqlite3_value) objects. Protected sqlite3_value objects are used to pass parameter information into the functions that implement [application-defined SQL functions](appfunc.md) and [virtual tables](vtab.md).
These routines work only with [protected sqlite3_value](#sqlite3_value) objects. Any attempt to use these routines on an [unprotected sqlite3_value](#sqlite3_value) is not threadsafe.
These routines work just like the corresponding [column access functions](#sqlite3_column_blob) except that these routines take a single [protected sqlite3_value](#sqlite3_value) object pointer instead of a [sqlite3_stmt\*](#sqlite3_stmt) pointer and an integer column number.
The sqlite3_value_text16() interface extracts a UTF-16 string in the native byte-order of the host machine. The sqlite3_value_text16be() and sqlite3_value_text16le() interfaces extract UTF-16 strings as big-endian and little-endian respectively.
If [sqlite3_value](#sqlite3_value) object V was initialized using [sqlite3_bind_pointer(S,I,P,X,D)](#sqlite3_bind_blob) or [sqlite3_result_pointer(C,P,X,D)](#sqlite3_result_blob) and if X and Y are strings that compare equal according to strcmp(X,Y), then sqlite3_value_pointer(V,Y) will return the pointer P. Otherwise, sqlite3_value_pointer(V,Y) returns a NULL. The sqlite3_bind_pointer() routine is part of the [pointer passing interface](bindptr.md) added for SQLite 3.20.0.
The sqlite3_value_type(V) interface returns the [datatype code](#SQLITE_BLOB) for the initial datatype of the [sqlite3_value](#sqlite3_value) object V. The returned value is one of [SQLITE_INTEGER](#SQLITE_BLOB), [SQLITE_FLOAT](#SQLITE_BLOB), [SQLITE_TEXT](#SQLITE_BLOB), [SQLITE_BLOB](#SQLITE_BLOB), or [SQLITE_NULL](#SQLITE_BLOB). Other interfaces might change the datatype for an sqlite3_value object. For example, if the datatype is initially SQLITE_INTEGER and sqlite3_value_text(V) is called to extract a text value for that integer, then subsequent calls to sqlite3_value_type(V) might return SQLITE_TEXT. Whether or not a persistent internal datatype conversion occurs is undefined and may change from one release of SQLite to the next.
The sqlite3_value_numeric_type() interface attempts to apply numeric affinity to the value. This means that an attempt is made to convert the value to an integer or floating point. If such a conversion is possible without loss of information (in other words, if the value is a string that looks like a number) then the conversion is performed. Otherwise no conversion occurs. The [datatype](#SQLITE_BLOB) after conversion is returned.
Within the [xUpdate](vtab.md#xupdate) method of a [virtual table](vtab.md), the sqlite3_value_nochange(X) interface returns true if and only if the column corresponding to X is unchanged by the UPDATE operation that the xUpdate method call was invoked to implement and if the prior [xColumn](vtab.md#xcolumn) method call that was invoked to extract the value for that column returned without setting a result (probably because it queried [sqlite3_vtab_nochange()](#sqlite3_vtab_nochange) and found that the column was unchanging). Within an [xUpdate](vtab.md#xupdate) method, any value for which sqlite3_value_nochange(X) is true will in all other respects appear to be a NULL value. If sqlite3_value_nochange(X) is invoked anywhere other than within an [xUpdate](vtab.md#xupdate) method call for an UPDATE statement, then the return value is arbitrary and meaningless.
The sqlite3_value_frombind(X) interface returns non-zero if the value X originated from one of the [sqlite3_bind()](#sqlite3_bind_blob) interfaces. If X comes from an SQL literal value, or a table column, or an expression, then sqlite3_value_frombind(X) returns zero.
Please pay particular attention to the fact that the pointer returned from [sqlite3_value_blob()](#sqlite3_value_blob), [sqlite3_value_text()](#sqlite3_value_blob), or [sqlite3_value_text16()](#sqlite3_value_blob) can be invalidated by a subsequent call to [sqlite3_value_bytes()](#sqlite3_value_blob), [sqlite3_value_bytes16()](#sqlite3_value_blob), [sqlite3_value_text()](#sqlite3_value_blob), or [sqlite3_value_text16()](#sqlite3_value_blob).
These routines must be called from the same thread as the SQL function that supplied the [sqlite3_value\*](#sqlite3_value) parameters.
As long as the input parameter is correct, these routines can only fail if an out-of-memory error occurs while trying to do a UTF8→UTF16 or UTF16→UTF8 conversion. If an out-of-memory error occurs, then the return value from these routines is the same as if the column had contained an SQL NULL value. If the input sqlite3_value was not obtained from [sqlite3_value_dup()](#sqlite3_value_dup), then valid SQL NULL returns can also be distinguished from out-of-memory errors after extracting the value by invoking the [sqlite3_errcode()](#sqlite3_errcode) immediately after the suspicious return value is obtained and before any other SQLite interface is called on the same [database connection](#sqlite3). If the input sqlite3_value was obtained from sqlite3_value_dup() then it is disconnected from the database connection and so sqlite3_errcode() will not work. In that case, the only way to distinguish an out-of-memory condition from a true SQL NULL is to invoke sqlite3_value_type() on the input to see if it is NULL prior to trying to extract the value.
------------------------------------------------------------------------
## Copy And Free SQL Values
> \
> sqlite3_value \*sqlite3_value_dup(const sqlite3_value\*);\
> void sqlite3_value_free(sqlite3_value\*);\
The sqlite3_value_dup(V) interface makes a copy of the [sqlite3_value](#sqlite3_value) object V and returns a pointer to that copy. The [sqlite3_value](#sqlite3_value) returned is a [protected sqlite3_value](#sqlite3_value) object even if the input is not. The sqlite3_value_dup(V) interface returns NULL if V is NULL or if a memory allocation fails. If V is a [pointer value](bindptr.md), then the result of sqlite3_value_dup(V) is a NULL value.
The sqlite3_value_free(V) interface frees an [sqlite3_value](#sqlite3_value) object previously obtained from [sqlite3_value_dup()](#sqlite3_value_dup). If V is a NULL pointer then sqlite3_value_free(V) is a harmless no-op.
------------------------------------------------------------------------
## Virtual File System Objects
> \
> sqlite3_vfs \*sqlite3_vfs_find(const char \*zVfsName);\
> int sqlite3_vfs_register(sqlite3_vfs\*, int makeDflt);\
> int sqlite3_vfs_unregister(sqlite3_vfs\*);\
A virtual filesystem (VFS) is an [sqlite3_vfs](#sqlite3_vfs) object that SQLite uses to interact with the underlying operating system. Most SQLite builds come with a single default VFS that is appropriate for the host computer. New VFSes can be registered and existing VFSes can be unregistered. The following interfaces are provided.
The sqlite3_vfs_find() interface returns a pointer to a VFS given its name. Names are case sensitive. Names are zero-terminated UTF-8 strings. If there is no match, a NULL pointer is returned. If zVfsName is NULL then the default VFS is returned.
New VFSes are registered with sqlite3_vfs_register(). Each new VFS becomes the default VFS if the makeDflt flag is set. The same VFS can be registered multiple times without injury. To make an existing VFS into the default VFS, register it again with the makeDflt flag set. If two different VFSes with the same name are registered, the behavior is undefined. If a VFS is registered with a name that is NULL or an empty string, then the behavior is undefined.
Unregister a VFS with the sqlite3_vfs_unregister() interface. If the default VFS is unregistered, another VFS is chosen as the default. The choice for the new VFS is arbitrary.
------------------------------------------------------------------------
## Find all elements on the right-hand side of an IN constraint.
> \
> int sqlite3_vtab_in_first(sqlite3_value \*pVal, sqlite3_value \*\*ppOut);\
> int sqlite3_vtab_in_next(sqlite3_value \*pVal, sqlite3_value \*\*ppOut);\
These interfaces are only useful from within the [xFilter() method](vtab.md#xfilter) of a [virtual table](vtab.md) implementation. The result of invoking these interfaces from any other context is undefined and probably harmful.
The X parameter in a call to sqlite3_vtab_in_first(X,P) or sqlite3_vtab_in_next(X,P) should be one of the parameters to the xFilter method which invokes these routines, and specifically a parameter that was previously selected for all-at-once IN constraint processing using the [sqlite3_vtab_in()](#sqlite3_vtab_in) interface in the [xBestIndex method](vtab.md#xbestindex). If the X parameter is not an xFilter argument that was selected for all-at-once IN constraint processing, then these routines return [SQLITE_ERROR](#SQLITE_ABORT).
Use these routines to access all values on the right-hand side of the IN constraint using code like the following:
> \
> for(rc=sqlite3_vtab_in_first(pList, &pVal);\
> rc==SQLITE_OK && pVal;\
> rc=sqlite3_vtab_in_next(pList, &pVal)\
> ){\
> // do something with pVal\
> }\
> if( rc!=SQLITE_DONE ){\
> // an error has occurred\
> }\
On success, the sqlite3_vtab_in_first(X,P) and sqlite3_vtab_in_next(X,P) routines return SQLITE_OK and set \*P to point to the first or next value on the RHS of the IN constraint. If there are no more values on the right hand side of the IN constraint, then \*P is set to NULL and these routines return [SQLITE_DONE](#SQLITE_ABORT). The return value might be some other value, such as SQLITE_NOMEM, in the event of a malfunction.
The \*ppOut values returned by these routines are only valid until the next call to either of these routines or until the end of the xFilter method from which these routines were called. If the virtual table implementation needs to retain the \*ppOut values for longer, it must make copies. The \*ppOut values are [protected](#sqlite3_value).
------------------------------------------------------------------------
## Win32 Specific Interface
> \
> int sqlite3_win32_set_directory(\
> unsigned long type, /\* Identifier for directory being set or reset \*/\
> void \*zValue /\* New value for directory being set or reset \*/\
> );\
> int sqlite3_win32_set_directory8(unsigned long type, const char \*zValue);\
> int sqlite3_win32_set_directory16(unsigned long type, const void \*zValue);\
These interfaces are available only on Windows. The [sqlite3_win32_set_directory](#sqlite3_win32_set_directory) interface is used to set the value associated with the [sqlite3_temp_directory](#sqlite3_temp_directory) or [sqlite3_data_directory](#sqlite3_data_directory) variable, to zValue, depending on the value of the type parameter. The zValue parameter should be NULL to cause the previous value to be freed via [sqlite3_free](#sqlite3_free); a non-NULL value will be copied into memory obtained from [sqlite3_malloc](#sqlite3_free) prior to being used. The [sqlite3_win32_set_directory](#sqlite3_win32_set_directory) interface returns [SQLITE_OK](#SQLITE_ABORT) to indicate success, [SQLITE_ERROR](#SQLITE_ABORT) if the type is unsupported, or [SQLITE_NOMEM](#SQLITE_ABORT) if memory could not be allocated. The value of the [sqlite3_data_directory](#sqlite3_data_directory) variable is intended to act as a replacement for the current directory on the sub-platforms of Win32 where that concept is not present, e.g. WinRT and UWP. The [sqlite3_win32_set_directory8](#sqlite3_win32_set_directory) and [sqlite3_win32_set_directory16](#sqlite3_win32_set_directory) interfaces behave exactly the same as the sqlite3_win32_set_directory interface except the string parameter must be UTF-8 or UTF-16, respectively.
------------------------------------------------------------------------
## Binding Values To Prepared Statements
> \
> int sqlite3_bind_blob(sqlite3_stmt\*, int, const void\*, int n, void(\*)(void\*));\
> int sqlite3_bind_blob64(sqlite3_stmt\*, int, const void\*, sqlite3_uint64,\
> void(\*)(void\*));\
> int sqlite3_bind_double(sqlite3_stmt\*, int, double);\
> int sqlite3_bind_int(sqlite3_stmt\*, int, int);\
> int sqlite3_bind_int64(sqlite3_stmt\*, int, sqlite3_int64);\
> int sqlite3_bind_null(sqlite3_stmt\*, int);\
> int sqlite3_bind_text(sqlite3_stmt\*,int,const char\*,int,void(\*)(void\*));\
> int sqlite3_bind_text16(sqlite3_stmt\*, int, const void\*, int, void(\*)(void\*));\
> int sqlite3_bind_text64(sqlite3_stmt\*, int, const char\*, sqlite3_uint64,\
> void(\*)(void\*), unsigned char encoding);\
> int sqlite3_bind_value(sqlite3_stmt\*, int, const sqlite3_value\*);\
> int sqlite3_bind_pointer(sqlite3_stmt\*, int, void\*, const char\*,void(\*)(void\*));\
> int sqlite3_bind_zeroblob(sqlite3_stmt\*, int, int n);\
> int sqlite3_bind_zeroblob64(sqlite3_stmt\*, int, sqlite3_uint64);\
In the SQL statement text input to [sqlite3_prepare_v2()](#sqlite3_prepare) and its variants, literals may be replaced by a [parameter](lang_expr.md#varparam) that matches one of the following templates:
- ?
- ?NNN
- :VVV
- @VVV
- \$VVV
In the templates above, NNN represents an integer literal, and VVV represents an alphanumeric identifier. The values of these parameters (also called "host parameter names" or "SQL parameters") can be set using the sqlite3_bind\_\*() routines defined here.
The first argument to the sqlite3_bind\_\*() routines is always a pointer to the [sqlite3_stmt](#sqlite3_stmt) object returned from [sqlite3_prepare_v2()](#sqlite3_prepare) or its variants.
The second argument is the index of the SQL parameter to be set. The leftmost SQL parameter has an index of 1. When the same named SQL parameter is used more than once, second and subsequent occurrences have the same index as the first occurrence. The index for named parameters can be looked up using the [sqlite3_bind_parameter_index()](#sqlite3_bind_parameter_index) API if desired. The index for "?NNN" parameters is the value of NNN. The NNN value must be between 1 and the [sqlite3_limit()](#sqlite3_limit) parameter [SQLITE_LIMIT_VARIABLE_NUMBER](#sqlitelimitvariablenumber) (default value: 32766).
The third argument is the value to bind to the parameter. If the third parameter to sqlite3_bind_text() or sqlite3_bind_text16() or sqlite3_bind_blob() is a NULL pointer then the fourth parameter is ignored and the end result is the same as sqlite3_bind_null(). If the third parameter to sqlite3_bind_text() is not NULL, then it should be a pointer to well-formed UTF8 text. If the third parameter to sqlite3_bind_text16() is not NULL, then it should be a pointer to well-formed UTF16 text. If the third parameter to sqlite3_bind_text64() is not NULL, then it should be a pointer to a well-formed unicode string that is either UTF8 if the sixth parameter is SQLITE_UTF8 or SQLITE_UTF8_ZT, or UTF16 otherwise.
The byte-order of UTF16 input text is determined by the byte-order mark (BOM, U+FEFF) found in the first character, which is removed, or in the absence of a BOM the byte order is the native byte order of the host machine for sqlite3_bind_text16() or the byte order specified in the 6th parameter for sqlite3_bind_text64(). If UTF16 input text contains invalid unicode characters, then SQLite might change those invalid characters into the unicode replacement character: U+FFFD.
In those routines that have a fourth argument, its value is the number of bytes in the parameter. To be clear: the value is the number of bytes in the value, not the number of characters. If the fourth parameter to sqlite3_bind_text() or sqlite3_bind_text16() is negative, then the length of the string is the number of bytes up to the first zero terminator. If the fourth parameter to sqlite3_bind_blob() is negative, then the behavior is undefined. If a non-negative fourth parameter is provided to sqlite3_bind_text() or sqlite3_bind_text16() or sqlite3_bind_text64() then that parameter must be the byte offset where the NUL terminator would occur assuming the string were NUL terminated. If any NUL characters occur at byte offsets less than the value of the fourth parameter then the resulting string value will contain embedded NULs. The result of expressions involving strings with embedded NULs is undefined.
The fifth argument to the BLOB and string binding interfaces controls or indicates the lifetime of the object referenced by the third parameter. These three options exist: (1) A destructor to dispose of the BLOB or string after SQLite has finished with it may be passed. It is called to dispose of the BLOB or string even if the call to the bind API fails, except the destructor is not called if the third parameter is a NULL pointer or the fourth parameter is negative. (2) The special constant, [SQLITE_STATIC](#SQLITE_STATIC), may be passed to indicate that the application remains responsible for disposing of the object. In this case, the object and the provided pointer to it must remain valid until either the prepared statement is finalized or the same SQL parameter is bound to something else, whichever occurs sooner. (3) The constant, [SQLITE_TRANSIENT](#SQLITE_STATIC), may be passed to indicate that the object is to be copied prior to the return from sqlite3_bind\_\*(). The object and pointer to it must remain valid until then. SQLite will then manage the lifetime of its private copy.
The sixth argument (the E argument) to sqlite3_bind_text64(S,K,Z,N,D,E) must be one of [SQLITE_UTF8](#sqliteutf8), [SQLITE_UTF8_ZT](#sqliteutf8zt), [SQLITE_UTF16](#sqliteutf16), [SQLITE_UTF16BE](#sqliteutf16be), or [SQLITE_UTF16LE](#sqliteutf16le) to specify the encoding of the text in the third parameter, Z. The special value [SQLITE_UTF8_ZT](#sqliteutf8zt) means that the string argument is both UTF-8 encoded and is zero-terminated. In other words, SQLITE_UTF8_ZT means that the Z array is allocated to hold at least N+1 bytes and that the Z\[N\] byte is zero. If the E argument to sqlite3_bind_text64(S,K,Z,N,D,E) is not one of the allowed values shown above, or if the text encoding is different from the encoding specified by the sixth parameter, then the behavior is undefined.
The sqlite3_bind_zeroblob() routine binds a BLOB of length N that is filled with zeroes. A zeroblob uses a fixed amount of memory (just an integer to hold its size) while it is being processed. Zeroblobs are intended to serve as placeholders for BLOBs whose content is later written using [incremental BLOB I/O](#sqlite3_blob_open) routines. A negative value for the zeroblob results in a zero-length BLOB.
The sqlite3_bind_pointer(S,I,P,T,D) routine causes the I-th parameter in [prepared statement](#sqlite3_stmt) S to have an SQL value of NULL, but to also be associated with the pointer P of type T. D is either a NULL pointer or a pointer to a destructor function for P. SQLite will invoke the destructor D with a single argument of P when it is finished using P, even if the call to sqlite3_bind_pointer() fails. Due to a historical design quirk, results are undefined if D is SQLITE_TRANSIENT. The T parameter should be a static string, preferably a string literal. The sqlite3_bind_pointer() routine is part of the [pointer passing interface](bindptr.md) added for SQLite 3.20.0.
If any of the sqlite3_bind\_\*() routines are called with a NULL pointer for the [prepared statement](#sqlite3_stmt) or with a prepared statement for which [sqlite3_step()](#sqlite3_step) has been called more recently than [sqlite3_reset()](#sqlite3_reset), then the call will return [SQLITE_MISUSE](#SQLITE_ABORT). If any sqlite3_bind\_() routine is passed a [prepared statement](#sqlite3_stmt) that has been finalized, the result is undefined and probably harmful.
Bindings are not cleared by the [sqlite3_reset()](#sqlite3_reset) routine. Unbound parameters are interpreted as NULL.
The sqlite3_bind\_\* routines return [SQLITE_OK](#SQLITE_ABORT) on success or an [error code](rescode.md) if anything goes wrong. [SQLITE_TOOBIG](#SQLITE_ABORT) might be returned if the size of a string or BLOB exceeds limits imposed by [sqlite3_limit](#sqlite3_limit)([SQLITE_LIMIT_LENGTH](#sqlitelimitlength)) or [SQLITE_MAX_LENGTH](limits.md#max_length). [SQLITE_RANGE](#SQLITE_ABORT) is returned if the parameter index is out of range. [SQLITE_NOMEM](#SQLITE_ABORT) is returned if malloc() fails.
See also: [sqlite3_bind_parameter_count()](#sqlite3_bind_parameter_count), [sqlite3_bind_parameter_name()](#sqlite3_bind_parameter_name), and [sqlite3_bind_parameter_index()](#sqlite3_bind_parameter_index).
------------------------------------------------------------------------
## Compiling An SQL Statement
> \
> int sqlite3_prepare(\
> sqlite3 \*db, /\* Database handle \*/\
> const char \*zSql, /\* SQL statement, UTF-8 encoded \*/\
> int nByte, /\* Maximum length of zSql in bytes. \*/\
> sqlite3_stmt \*\*ppStmt, /\* OUT: Statement handle \*/\
> const char \*\*pzTail /\* OUT: Pointer to unused portion of zSql \*/\
> );\
> int sqlite3_prepare_v2(\
> sqlite3 \*db, /\* Database handle \*/\
> const char \*zSql, /\* SQL statement, UTF-8 encoded \*/\
> int nByte, /\* Maximum length of zSql in bytes. \*/\
> sqlite3_stmt \*\*ppStmt, /\* OUT: Statement handle \*/\
> const char \*\*pzTail /\* OUT: Pointer to unused portion of zSql \*/\
> );\
> int sqlite3_prepare_v3(\
> sqlite3 \*db, /\* Database handle \*/\
> const char \*zSql, /\* SQL statement, UTF-8 encoded \*/\
> int nByte, /\* Maximum length of zSql in bytes. \*/\
> unsigned int prepFlags, /\* Zero or more SQLITE_PREPARE\_ flags \*/\
> sqlite3_stmt \*\*ppStmt, /\* OUT: Statement handle \*/\
> const char \*\*pzTail /\* OUT: Pointer to unused portion of zSql \*/\
> );\
> int sqlite3_prepare16(\
> sqlite3 \*db, /\* Database handle \*/\
> const void \*zSql, /\* SQL statement, UTF-16 encoded \*/\
> int nByte, /\* Maximum length of zSql in bytes. \*/\
> sqlite3_stmt \*\*ppStmt, /\* OUT: Statement handle \*/\
> const void \*\*pzTail /\* OUT: Pointer to unused portion of zSql \*/\
> );\
> int sqlite3_prepare16_v2(\
> sqlite3 \*db, /\* Database handle \*/\
> const void \*zSql, /\* SQL statement, UTF-16 encoded \*/\
> int nByte, /\* Maximum length of zSql in bytes. \*/\
> sqlite3_stmt \*\*ppStmt, /\* OUT: Statement handle \*/\
> const void \*\*pzTail /\* OUT: Pointer to unused portion of zSql \*/\
> );\
> int sqlite3_prepare16_v3(\
> sqlite3 \*db, /\* Database handle \*/\
> const void \*zSql, /\* SQL statement, UTF-16 encoded \*/\
> int nByte, /\* Maximum length of zSql in bytes. \*/\
> unsigned int prepFlags, /\* Zero or more SQLITE_PREPARE\_ flags \*/\
> sqlite3_stmt \*\*ppStmt, /\* OUT: Statement handle \*/\
> const void \*\*pzTail /\* OUT: Pointer to unused portion of zSql \*/\
> );\
To execute an SQL statement, it must first be compiled into a byte-code program using one of these routines. Or, in other words, these routines are constructors for the [prepared statement](#sqlite3_stmt) object.
The preferred routine to use is [sqlite3_prepare_v2()](#sqlite3_prepare). The [sqlite3_prepare()](#sqlite3_prepare) interface is legacy and should be avoided. [sqlite3_prepare_v3()](#sqlite3_prepare) has an extra ["prepFlags" option](#sqlitepreparefromddl) that is sometimes needed for special purpose or to pass along security restrictions.
The use of the UTF-8 interfaces is preferred, as SQLite currently does all parsing using UTF-8. The UTF-16 interfaces are provided as a convenience. The UTF-16 interfaces work by converting the input text into UTF-8, then invoking the corresponding UTF-8 interface.
The first argument, "db", is a [database connection](#sqlite3) obtained from a prior successful call to [sqlite3_open()](#sqlite3_open), [sqlite3_open_v2()](#sqlite3_open) or [sqlite3_open16()](#sqlite3_open). The database connection must not have been closed.
The second argument, "zSql", is the statement to be compiled, encoded as either UTF-8 or UTF-16. The sqlite3_prepare(), sqlite3_prepare_v2(), and sqlite3_prepare_v3() interfaces use UTF-8, and sqlite3_prepare16(), sqlite3_prepare16_v2(), and sqlite3_prepare16_v3() use UTF-16.
If the nByte argument is negative, then zSql is read up to the first zero terminator. If nByte is positive, then it is the maximum number of bytes read from zSql. When nByte is positive, zSql is read up to the first zero terminator or until the nByte bytes have been read, whichever comes first. If nByte is zero, then no prepared statement is generated. If the caller knows that the supplied string is nul-terminated, then there is a small performance advantage to passing an nByte parameter that is the number of bytes in the input string *including* the nul-terminator. Note that nByte measures the length of the input in bytes, not characters, even for the UTF-16 interfaces.
If pzTail is not NULL then \*pzTail is made to point to the first byte past the end of the first SQL statement in zSql. These routines only compile the first statement in zSql, so \*pzTail is left pointing to what remains uncompiled.
\*ppStmt is left pointing to a compiled [prepared statement](#sqlite3_stmt) that can be executed using [sqlite3_step()](#sqlite3_step). If there is an error, \*ppStmt is set to NULL. If the input text contains no SQL (if the input is an empty string or a comment) then \*ppStmt is set to NULL. The calling procedure is responsible for deleting the compiled SQL statement using [sqlite3_finalize()](#sqlite3_finalize) after it has finished with it. ppStmt may not be NULL.
On success, the sqlite3_prepare() family of routines return [SQLITE_OK](#SQLITE_ABORT); otherwise an [error code](rescode.md) is returned.
The sqlite3_prepare_v2(), sqlite3_prepare_v3(), sqlite3_prepare16_v2(), and sqlite3_prepare16_v3() interfaces are recommended for all new programs. The older interfaces (sqlite3_prepare() and sqlite3_prepare16()) are retained for backwards compatibility, but their use is discouraged. In the "vX" interfaces, the prepared statement that is returned (the [sqlite3_stmt](#sqlite3_stmt) object) contains a copy of the original SQL text. This causes the [sqlite3_step()](#sqlite3_step) interface to behave differently in three ways:
If the database schema changes, instead of returning [SQLITE_SCHEMA](#SQLITE_ABORT) as it always used to do, [sqlite3_step()](#sqlite3_step) will automatically recompile the SQL statement and try to run it again. As many as [SQLITE_MAX_SCHEMA_RETRY](compile.md#max_schema_retry) retries will occur before sqlite3_step() gives up and returns an error.
When an error occurs, [sqlite3_step()](#sqlite3_step) will return one of the detailed [error codes](rescode.md) or [extended error codes](rescode.md#extrc). The legacy behavior was that [sqlite3_step()](#sqlite3_step) would only return a generic [SQLITE_ERROR](#SQLITE_ABORT) result code and the application would have to make a second call to [sqlite3_reset()](#sqlite3_reset) in order to find the underlying cause of the problem. With the "v2" prepare interfaces, the underlying reason for the error is returned immediately.
If the specific value bound to a [host parameter](lang_expr.md#varparam) in the WHERE clause might influence the choice of query plan for a statement, then the statement will be automatically recompiled, as if there had been a schema change, on the first [sqlite3_step()](#sqlite3_step) call following any change to the [bindings](#sqlite3_bind_blob) of that [parameter](lang_expr.md#varparam). The specific value of a WHERE-clause [parameter](lang_expr.md#varparam) might influence the choice of query plan if the parameter is the left-hand side of a [LIKE](lang_expr.md#like) or [GLOB](lang_expr.md#glob) operator or if the parameter is compared to an indexed column and the [SQLITE_ENABLE_STAT4](compile.md#enable_stat4) compile-time option is enabled.
sqlite3_prepare_v3() differs from sqlite3_prepare_v2() only in having the extra prepFlags parameter, which is a bit array consisting of zero or more of the [SQLITE_PREPARE\_\*](#sqlitepreparepersistent) flags. The sqlite3_prepare_v2() interface works exactly the same as sqlite3_prepare_v3() with a zero prepFlags parameter.
------------------------------------------------------------------------
## Compile-Time Authorization Callbacks
> \
> int sqlite3_set_authorizer(\
> sqlite3\*,\
> int (\*xAuth)(void\*,int,const char\*,const char\*,const char\*,const char\*),\
> void \*pUserData\
> );\
This routine registers an authorizer callback with a particular [database connection](#sqlite3), supplied in the first argument. The authorizer callback is invoked as SQL statements are being compiled by [sqlite3_prepare()](#sqlite3_prepare) or its variants [sqlite3_prepare_v2()](#sqlite3_prepare), [sqlite3_prepare_v3()](#sqlite3_prepare), [sqlite3_prepare16()](#sqlite3_prepare), [sqlite3_prepare16_v2()](#sqlite3_prepare), and [sqlite3_prepare16_v3()](#sqlite3_prepare). At various points during the compilation process, as logic is being created to perform various actions, the authorizer callback is invoked to see if those actions are allowed. The authorizer callback should return [SQLITE_OK](#SQLITE_ABORT) to allow the action, [SQLITE_IGNORE](#SQLITE_DENY) to disallow the specific action but allow the SQL statement to continue to be compiled, or [SQLITE_DENY](#SQLITE_DENY) to cause the entire SQL statement to be rejected with an error. If the authorizer callback returns any value other than [SQLITE_IGNORE](#SQLITE_DENY), [SQLITE_OK](#SQLITE_ABORT), or [SQLITE_DENY](#SQLITE_DENY) then the [sqlite3_prepare_v2()](#sqlite3_prepare) or equivalent call that triggered the authorizer will fail with an error message.
When the callback returns [SQLITE_OK](#SQLITE_ABORT), that means the operation requested is ok. When the callback returns [SQLITE_DENY](#SQLITE_DENY), the [sqlite3_prepare_v2()](#sqlite3_prepare) or equivalent call that triggered the authorizer will fail with an error message explaining that access is denied.
The first parameter to the authorizer callback is a copy of the third parameter to the sqlite3_set_authorizer() interface. The second parameter to the callback is an integer [action code](#SQLITE_ALTER_TABLE) that specifies the particular action to be authorized. The third through sixth parameters to the callback are either NULL pointers or zero-terminated strings that contain additional details about the action to be authorized. Applications must always be prepared to encounter a NULL pointer in any of the third through the sixth parameters of the authorization callback.
If the action code is [SQLITE_READ](#SQLITE_ALTER_TABLE) and the callback returns [SQLITE_IGNORE](#SQLITE_DENY) then the [prepared statement](#sqlite3_stmt) statement is constructed to substitute a NULL value in place of the table column that would have been read if [SQLITE_OK](#SQLITE_ABORT) had been returned. The [SQLITE_IGNORE](#SQLITE_DENY) return can be used to deny an untrusted user access to individual columns of a table. When a table is referenced by a [SELECT](lang_select.md) but no column values are extracted from that table (for example in a query like "SELECT count(\*) FROM tab") then the [SQLITE_READ](#SQLITE_ALTER_TABLE) authorizer callback is invoked once for that table with a column name that is an empty string. If the action code is [SQLITE_DELETE](#SQLITE_ALTER_TABLE) and the callback returns [SQLITE_IGNORE](#SQLITE_DENY) then the [DELETE](lang_delete.md) operation proceeds but the [truncate optimization](lang_delete.md#truncateopt) is disabled and all rows are deleted individually.
An authorizer is used when [preparing](#sqlite3_prepare) SQL statements from an untrusted source, to ensure that the SQL statements do not try to access data they are not allowed to see, or that they do not try to execute malicious statements that damage the database. For example, an application may allow a user to enter arbitrary SQL queries for evaluation by a database. But the application does not want the user to be able to make arbitrary changes to the database. An authorizer could then be put in place while the user-entered SQL is being [prepared](#sqlite3_prepare) that disallows everything except [SELECT](lang_select.md) statements.
Applications that need to process SQL from untrusted sources might also consider lowering resource limits using [sqlite3_limit()](#sqlite3_limit) and limiting database size using the [max_page_count](pragma.md#pragma_max_page_count) [PRAGMA](pragma.md#syntax) in addition to using an authorizer.
Only a single authorizer can be in place on a database connection at a time. Each call to sqlite3_set_authorizer overrides the previous call. Disable the authorizer by installing a NULL callback. The authorizer is disabled by default.
The authorizer callback must not do anything that will modify the database connection that invoked the authorizer callback. Note that [sqlite3_prepare_v2()](#sqlite3_prepare) and [sqlite3_step()](#sqlite3_step) both modify their database connections for the meaning of "modify" in this paragraph.
When [sqlite3_prepare_v2()](#sqlite3_prepare) is used to prepare a statement, the statement might be re-prepared during [sqlite3_step()](#sqlite3_step) due to a schema change. Hence, the application should ensure that the correct authorizer callback remains in place during the [sqlite3_step()](#sqlite3_step).
Note that the authorizer callback is invoked only during [sqlite3_prepare()](#sqlite3_prepare) or its variants. Authorization is not performed during statement evaluation in [sqlite3_step()](#sqlite3_step), unless as stated in the previous paragraph, sqlite3_step() invokes sqlite3_prepare_v2() to reprepare a statement after a schema change.
------------------------------------------------------------------------
## Test For Auto-Commit Mode
> \
> int sqlite3_get_autocommit(sqlite3\*);\
The sqlite3_get_autocommit() interface returns non-zero or zero if the given database connection is or is not in autocommit mode, respectively. Autocommit mode is on by default. Autocommit mode is disabled by a [BEGIN](lang_transaction.md) statement. Autocommit mode is re-enabled by a [COMMIT](lang_transaction.md) or [ROLLBACK](lang_transaction.md).
If certain kinds of errors occur on a statement within a multi-statement transaction (errors including [SQLITE_FULL](#SQLITE_ABORT), [SQLITE_IOERR](#SQLITE_ABORT), [SQLITE_NOMEM](#SQLITE_ABORT), [SQLITE_BUSY](#SQLITE_ABORT), and [SQLITE_INTERRUPT](#SQLITE_ABORT)) then the transaction might be rolled back automatically. The only way to find out whether SQLite automatically rolled back the transaction after an error is to use this function.
If another thread changes the autocommit status of the database connection while this routine is running, then the return value is undefined.
------------------------------------------------------------------------
## Register A Callback To Handle SQLITE_BUSY Errors
> \
> int sqlite3_busy_handler(sqlite3\*,int(\*)(void\*,int),void\*);\
The sqlite3_busy_handler(D,X,P) routine sets a callback function X that might be invoked with argument P whenever an attempt is made to access a database table associated with [database connection](#sqlite3) D when another thread or process has the table locked. The sqlite3_busy_handler() interface is used to implement [sqlite3_busy_timeout()](#sqlite3_busy_timeout) and [PRAGMA busy_timeout](pragma.md#pragma_busy_timeout).
If the busy callback is NULL, then [SQLITE_BUSY](#SQLITE_ABORT) is returned immediately upon encountering the lock. If the busy callback is not NULL, then the callback might be invoked with two arguments.
The first argument to the busy handler is a copy of the void\* pointer which is the third argument to sqlite3_busy_handler(). The second argument to the busy handler callback is the number of times that the busy handler has been invoked previously for the same locking event. If the busy callback returns 0, then no additional attempts are made to access the database and [SQLITE_BUSY](#SQLITE_ABORT) is returned to the application. If the callback returns non-zero, then another attempt is made to access the database and the cycle repeats.
The presence of a busy handler does not guarantee that it will be invoked when there is lock contention. If SQLite determines that invoking the busy handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY](#SQLITE_ABORT) to the application instead of invoking the busy handler. Consider a scenario where one process is holding a read lock that it is trying to promote to a reserved lock and a second process is holding a reserved lock that it is trying to promote to an exclusive lock. The first process cannot proceed because it is blocked by the second and the second process cannot proceed because it is blocked by the first. If both processes invoke the busy handlers, neither will make any progress. Therefore, SQLite returns [SQLITE_BUSY](#SQLITE_ABORT) for the first process, hoping that this will induce the first process to release its read lock and allow the second process to proceed.
The default busy callback is NULL.
There can only be a single busy handler defined for each [database connection](#sqlite3). Setting a new busy handler clears any previously set handler. Note that calling [sqlite3_busy_timeout()](#sqlite3_busy_timeout) or evaluating [PRAGMA busy_timeout=N](pragma.md#pragma_busy_timeout) will change the busy handler and thus clear any previously set busy handler.
The busy callback should not take any actions which modify the database connection that invoked the busy handler. In other words, the busy handler is not reentrant. Any such actions result in undefined behavior.
A busy handler must not close the database connection or [prepared statement](#sqlite3_stmt) that invoked the busy handler.
------------------------------------------------------------------------
## Result Values From A Query
> \
> const void \*sqlite3_column_blob(sqlite3_stmt\*, int iCol);\
> double sqlite3_column_double(sqlite3_stmt\*, int iCol);\
> int sqlite3_column_int(sqlite3_stmt\*, int iCol);\
> sqlite3_int64 sqlite3_column_int64(sqlite3_stmt\*, int iCol);\
> const unsigned char \*sqlite3_column_text(sqlite3_stmt\*, int iCol);\
> const void \*sqlite3_column_text16(sqlite3_stmt\*, int iCol);\
> sqlite3_value \*sqlite3_column_value(sqlite3_stmt\*, int iCol);\
> int sqlite3_column_bytes(sqlite3_stmt\*, int iCol);\
> int sqlite3_column_bytes16(sqlite3_stmt\*, int iCol);\
> int sqlite3_column_type(sqlite3_stmt\*, int iCol);\
**Summary:**
> **sqlite3_column_blob**
>
> →
>
> BLOB result
>
> **sqlite3_column_double**
>
> →
>
> REAL result
>
> **sqlite3_column_int**
>
> →
>
> 32-bit INTEGER result
>
> **sqlite3_column_int64**
>
> →
>
> 64-bit INTEGER result
>
> **sqlite3_column_text**
>
> →
>
> UTF-8 TEXT result
>
> **sqlite3_column_text16**
>
> →
>
> UTF-16 TEXT result
>
> **sqlite3_column_value**
>
> →
>
> The result as an [unprotected sqlite3_value](#sqlite3_value) object.
>
>
>
>
>
>
>
> **sqlite3_column_bytes**
>
> →
>
> Size of a BLOB or a UTF-8 TEXT result in bytes
>
> **sqlite3_column_bytes16 **
>
> →
>
> Size of UTF-16 TEXT in bytes
>
> **sqlite3_column_type**
>
> →
>
> Default datatype of the result
**Details:**
These routines return information about a single column of the current result row of a query. In every case the first argument is a pointer to the [prepared statement](#sqlite3_stmt) that is being evaluated (the [sqlite3_stmt\*](#sqlite3_stmt) that was returned from [sqlite3_prepare_v2()](#sqlite3_prepare) or one of its variants) and the second argument is the index of the column for which information should be returned. The leftmost column of the result set has the index 0. The number of columns in the result can be determined using [sqlite3_column_count()](#sqlite3_column_count).
If the SQL statement does not currently point to a valid row, or if the column index is out of range, the result is undefined. These routines may only be called when the most recent call to [sqlite3_step()](#sqlite3_step) has returned [SQLITE_ROW](#SQLITE_ABORT) and neither [sqlite3_reset()](#sqlite3_reset) nor [sqlite3_finalize()](#sqlite3_finalize) have been called subsequently. If any of these routines are called after [sqlite3_reset()](#sqlite3_reset) or [sqlite3_finalize()](#sqlite3_finalize) or after [sqlite3_step()](#sqlite3_step) has returned something other than [SQLITE_ROW](#SQLITE_ABORT), the results are undefined. If [sqlite3_step()](#sqlite3_step) or [sqlite3_reset()](#sqlite3_reset) or [sqlite3_finalize()](#sqlite3_finalize) are called from a different thread while any of these routines are pending, then the results are undefined.
The first six interfaces (\_blob, \_double, \_int, \_int64, \_text, and \_text16) each return the value of a result column in a specific data format. If the result column is not initially in the requested format (for example, if the query returns an integer but the sqlite3_column_text() interface is used to extract the value) then an automatic type conversion is performed.
The sqlite3_column_type() routine returns the [datatype code](#SQLITE_BLOB) for the initial data type of the result column. The returned value is one of [SQLITE_INTEGER](#SQLITE_BLOB), [SQLITE_FLOAT](#SQLITE_BLOB), [SQLITE_TEXT](#SQLITE_BLOB), [SQLITE_BLOB](#SQLITE_BLOB), or [SQLITE_NULL](#SQLITE_BLOB). The return value of sqlite3_column_type() can be used to decide which of the first six interface should be used to extract the column value. The value returned by sqlite3_column_type() is only meaningful if no automatic type conversions have occurred for the value in question. After a type conversion, the result of calling sqlite3_column_type() is undefined, though harmless. Future versions of SQLite may change the behavior of sqlite3_column_type() following a type conversion.
If the result is a BLOB or a TEXT string, then the sqlite3_column_bytes() or sqlite3_column_bytes16() interfaces can be used to determine the size of that BLOB or string.
If the result is a BLOB or UTF-8 string then the sqlite3_column_bytes() routine returns the number of bytes in that BLOB or string. If the result is a UTF-16 string, then sqlite3_column_bytes() converts the string to UTF-8 and then returns the number of bytes. If the result is a numeric value then sqlite3_column_bytes() uses [sqlite3_snprintf()](#sqlite3_mprintf) to convert that value to a UTF-8 string and returns the number of bytes in that string. If the result is NULL, then sqlite3_column_bytes() returns zero.
If the result is a BLOB or UTF-16 string then the sqlite3_column_bytes16() routine returns the number of bytes in that BLOB or string. If the result is a UTF-8 string, then sqlite3_column_bytes16() converts the string to UTF-16 and then returns the number of bytes. If the result is a numeric value then sqlite3_column_bytes16() uses [sqlite3_snprintf()](#sqlite3_mprintf) to convert that value to a UTF-16 string and returns the number of bytes in that string. If the result is NULL, then sqlite3_column_bytes16() returns zero.
The values returned by [sqlite3_column_bytes()](#sqlite3_column_blob) and [sqlite3_column_bytes16()](#sqlite3_column_blob) do not include the zero terminators at the end of the string. For clarity: the values returned by [sqlite3_column_bytes()](#sqlite3_column_blob) and [sqlite3_column_bytes16()](#sqlite3_column_blob) are the number of bytes in the string, not the number of characters.
Strings returned by sqlite3_column_text() and sqlite3_column_text16(), even empty strings, are always zero-terminated. The return value from sqlite3_column_blob() for a zero-length BLOB is a NULL pointer.
Strings returned by sqlite3_column_text16() always have the endianness which is native to the platform, regardless of the text encoding set for the database.
**Warning:** The object returned by [sqlite3_column_value()](#sqlite3_column_blob) is an [unprotected sqlite3_value](#sqlite3_value) object. In a multithreaded environment, an unprotected sqlite3_value object may only be used safely with [sqlite3_bind_value()](#sqlite3_bind_blob) and [sqlite3_result_value()](#sqlite3_result_blob). If the [unprotected sqlite3_value](#sqlite3_value) object returned by [sqlite3_column_value()](#sqlite3_column_blob) is used in any other way, including calls to routines like [sqlite3_value_int()](#sqlite3_value_blob), [sqlite3_value_text()](#sqlite3_value_blob), or [sqlite3_value_bytes()](#sqlite3_value_blob), the behavior is not threadsafe. Hence, the sqlite3_column_value() interface is normally only useful within the implementation of [application-defined SQL functions](appfunc.md) or [virtual tables](vtab.md), not within top-level application code.
These routines may attempt to convert the datatype of the result. For example, if the internal representation is FLOAT and a text result is requested, [sqlite3_snprintf()](#sqlite3_mprintf) is used internally to perform the conversion automatically. The following table details the conversions that are applied:
> Internal\
> Type
>
> Requested\
> Type
>
> Conversion
>
> NULL
>
> INTEGER
>
> Result is 0
>
> NULL
>
> FLOAT
>
> Result is 0.0
>
> NULL
>
> TEXT
>
> Result is a NULL pointer
>
> NULL
>
> BLOB
>
> Result is a NULL pointer
>
> INTEGER
>
> FLOAT
>
> Convert from integer to float
>
> INTEGER
>
> TEXT
>
> ASCII rendering of the integer
>
> INTEGER
>
> BLOB
>
> Same as INTEGER-\>TEXT
>
> FLOAT
>
> INTEGER
>
> [CAST](lang_expr.md#castexpr) to INTEGER
>
> FLOAT
>
> TEXT
>
> ASCII rendering of the float
>
> FLOAT
>
> BLOB
>
> [CAST](lang_expr.md#castexpr) to BLOB
>
> TEXT
>
> INTEGER
>
> [CAST](lang_expr.md#castexpr) to INTEGER
>
> TEXT
>
> FLOAT
>
> [CAST](lang_expr.md#castexpr) to REAL
>
> TEXT
>
> BLOB
>
> No change
>
> BLOB
>
> INTEGER
>
> [CAST](lang_expr.md#castexpr) to INTEGER
>
> BLOB
>
> FLOAT
>
> [CAST](lang_expr.md#castexpr) to REAL
>
> BLOB
>
> TEXT
>
> [CAST](lang_expr.md#castexpr) to TEXT, ensure zero terminator
Note that when type conversions occur, pointers returned by prior calls to sqlite3_column_blob(), sqlite3_column_text(), and/or sqlite3_column_text16() may be invalidated. Type conversions and pointer invalidations might occur in the following cases:
- The initial content is a BLOB and sqlite3_column_text() or sqlite3_column_text16() is called. A zero-terminator might need to be added to the string.
- The initial content is UTF-8 text and sqlite3_column_bytes16() or sqlite3_column_text16() is called. The content must be converted to UTF-16.
- The initial content is UTF-16 text and sqlite3_column_bytes() or sqlite3_column_text() is called. The content must be converted to UTF-8.
Conversions between UTF-16be and UTF-16le are always done in place and do not invalidate a prior pointer, though of course the content of the buffer that the prior pointer references will have been modified. Other kinds of conversion are done in place when it is possible, but sometimes they are not possible and in those cases prior pointers are invalidated.
The safest policy is to invoke these routines in one of the following ways:
- sqlite3_column_text() followed by sqlite3_column_bytes()
- sqlite3_column_blob() followed by sqlite3_column_bytes()
- sqlite3_column_text16() followed by sqlite3_column_bytes16()
In other words, you should call sqlite3_column_text(), sqlite3_column_blob(), or sqlite3_column_text16() first to force the result into the desired format, then invoke sqlite3_column_bytes() or sqlite3_column_bytes16() to find the size of the result. Do not mix calls to sqlite3_column_text() or sqlite3_column_blob() with calls to sqlite3_column_bytes16(), and do not mix calls to sqlite3_column_text16() with calls to sqlite3_column_bytes().
The pointers returned are valid until a type conversion occurs as described above, or until [sqlite3_step()](#sqlite3_step) or [sqlite3_reset()](#sqlite3_reset) or [sqlite3_finalize()](#sqlite3_finalize) is called. The memory space used to hold strings and BLOBs is freed automatically. Do not pass the pointers returned from [sqlite3_column_blob()](#sqlite3_column_blob), [sqlite3_column_text()](#sqlite3_column_blob), etc. into [sqlite3_free()](#sqlite3_free).
As long as the input parameters are correct, these routines will only fail if an out-of-memory error occurs during a format conversion. Only the following subset of interfaces are subject to out-of-memory errors:
- sqlite3_column_blob()
- sqlite3_column_text()
- sqlite3_column_text16()
- sqlite3_column_bytes()
- sqlite3_column_bytes16()
If an out-of-memory error occurs, then the return value from these routines is the same as if the column had contained an SQL NULL value. Valid SQL NULL returns can be distinguished from out-of-memory errors by invoking the [sqlite3_errcode()](#sqlite3_errcode) immediately after the suspect return value is obtained and before any other SQLite interface is called on the same [database connection](#sqlite3).
------------------------------------------------------------------------
## Low-Level Control Of Database Files
> \
> int sqlite3_file_control(sqlite3\*, const char \*zDbName, int op, void\*);\
The [sqlite3_file_control()](#sqlite3_file_control) interface makes a direct call to the xFileControl method for the [sqlite3_io_methods](#sqlite3_io_methods) object associated with a particular database identified by the second argument. The name of the database is "main" for the main database or "temp" for the TEMP database, or the name that appears after the AS keyword for databases that are added using the [ATTACH](lang_attach.md) SQL command. A NULL pointer can be used in place of "main" to refer to the main database file. The third and fourth parameters to this routine are passed directly through to the second and third parameters of the xFileControl method. The return value of the xFileControl method becomes the return value of this routine.
A few opcodes for [sqlite3_file_control()](#sqlite3_file_control) are handled directly by the SQLite core and never invoke the sqlite3_io_methods.xFileControl method. The [SQLITE_FCNTL_FILE_POINTER](#sqlitefcntlfilepointer) value for the op parameter causes a pointer to the underlying [sqlite3_file](#sqlite3_file) object to be written into the space pointed to by the 4th parameter. The [SQLITE_FCNTL_JOURNAL_POINTER](#sqlitefcntljournalpointer) works similarly except that it returns the [sqlite3_file](#sqlite3_file) object associated with the journal file instead of the main database. The [SQLITE_FCNTL_VFS_POINTER](#sqlitefcntlvfspointer) opcode returns a pointer to the underlying [sqlite3_vfs](#sqlite3_vfs) object for the file. The [SQLITE_FCNTL_DATA_VERSION](#sqlitefcntldataversion) returns the data version counter from the pager.
If the second parameter (zDbName) does not match the name of any open database file, then SQLITE_ERROR is returned. This error code is not remembered and will not be recalled by [sqlite3_errcode()](#sqlite3_errcode) or [sqlite3_errmsg()](#sqlite3_errcode). The underlying xFileControl method might also return SQLITE_ERROR. There is no way to distinguish between an incorrect zDbName and an SQLITE_ERROR return from the underlying xFileControl method.
See also: [file control opcodes](#SQLITE_FCNTL_BEGIN_ATOMIC_WRITE)
------------------------------------------------------------------------
## Create Or Redefine SQL Functions
> \
> int sqlite3_create_function(\
> sqlite3 \*db,\
> const char \*zFunctionName,\
> int nArg,\
> int eTextRep,\
> void \*pApp,\
> void (\*xFunc)(sqlite3_context\*,int,sqlite3_value\*\*),\
> void (\*xStep)(sqlite3_context\*,int,sqlite3_value\*\*),\
> void (\*xFinal)(sqlite3_context\*)\
> );\
> int sqlite3_create_function16(\
> sqlite3 \*db,\
> const void \*zFunctionName,\
> int nArg,\
> int eTextRep,\
> void \*pApp,\
> void (\*xFunc)(sqlite3_context\*,int,sqlite3_value\*\*),\
> void (\*xStep)(sqlite3_context\*,int,sqlite3_value\*\*),\
> void (\*xFinal)(sqlite3_context\*)\
> );\
> int sqlite3_create_function_v2(\
> sqlite3 \*db,\
> const char \*zFunctionName,\
> int nArg,\
> int eTextRep,\
> void \*pApp,\
> void (\*xFunc)(sqlite3_context\*,int,sqlite3_value\*\*),\
> void (\*xStep)(sqlite3_context\*,int,sqlite3_value\*\*),\
> void (\*xFinal)(sqlite3_context\*),\
> void(\*xDestroy)(void\*)\
> );\
> int sqlite3_create_window_function(\
> sqlite3 \*db,\
> const char \*zFunctionName,\
> int nArg,\
> int eTextRep,\
> void \*pApp,\
> void (\*xStep)(sqlite3_context\*,int,sqlite3_value\*\*),\
> void (\*xFinal)(sqlite3_context\*),\
> void (\*xValue)(sqlite3_context\*),\
> void (\*xInverse)(sqlite3_context\*,int,sqlite3_value\*\*),\
> void(\*xDestroy)(void\*)\
> );\
These functions (collectively known as "function creation routines") are used to add SQL functions or aggregates or to redefine the behavior of existing SQL functions or aggregates. The only differences between the three "sqlite3_create_function\*" routines are the text encoding expected for the second parameter (the name of the function being created) and the presence or absence of a destructor callback for the application data pointer. Function sqlite3_create_window_function() is similar, but allows the user to supply the extra callback functions needed by [aggregate window functions](windowfunctions.md#aggwinfunc).
The first parameter is the [database connection](#sqlite3) to which the SQL function is to be added. If an application uses more than one database connection then application-defined SQL functions must be added to each database connection separately.
The second parameter is the name of the SQL function to be created or redefined. The length of the name is limited to 255 bytes in a UTF-8 representation, exclusive of the zero-terminator. Note that the name length limit is in UTF-8 bytes, not characters nor UTF-16 bytes. Any attempt to create a function with a longer name will result in [SQLITE_MISUSE](#SQLITE_ABORT) being returned.
The third parameter (nArg) is the number of arguments that the SQL function or aggregate takes. If this parameter is -1, then the SQL function or aggregate may take any number of arguments between 0 and the limit set by [sqlite3_limit](#sqlite3_limit)([SQLITE_LIMIT_FUNCTION_ARG](#sqlitelimitfunctionarg)). If the third parameter is less than -1 or greater than 127 then the behavior is undefined.
The fourth parameter, eTextRep, specifies what [text encoding](#sqliteutf8) this SQL function prefers for its parameters. The application should set this parameter to [SQLITE_UTF16LE](#sqliteutf16le) if the function implementation invokes [sqlite3_value_text16le()](#sqlite3_value_blob) on an input, or [SQLITE_UTF16BE](#sqliteutf16be) if the implementation invokes [sqlite3_value_text16be()](#sqlite3_value_blob) on an input, or [SQLITE_UTF16](#sqliteutf16) if [sqlite3_value_text16()](#sqlite3_value_blob) is used, or [SQLITE_UTF8](#sqliteutf8) otherwise. The same SQL function may be registered multiple times using different preferred text encodings, with different implementations for each encoding. When multiple implementations of the same function are available, SQLite will pick the one that involves the least amount of data conversion.
The fourth parameter may optionally be ORed with [SQLITE_DETERMINISTIC](#sqlitedeterministic) to signal that the function will always return the same result given the same inputs within a single SQL statement. Most SQL functions are deterministic. The built-in [random()](lang_corefunc.md#random) SQL function is an example of a function that is not deterministic. The SQLite query planner is able to perform additional optimizations on deterministic functions, so use of the [SQLITE_DETERMINISTIC](#sqlitedeterministic) flag is recommended where possible.
The fourth parameter may also optionally include the [SQLITE_DIRECTONLY](#sqlitedirectonly) flag, which if present prevents the function from being invoked from within VIEWs, TRIGGERs, CHECK constraints, generated column expressions, index expressions, or the WHERE clause of partial indexes.
For best security, the [SQLITE_DIRECTONLY](#sqlitedirectonly) flag is recommended for all application-defined SQL functions that do not need to be used inside of triggers, views, CHECK constraints, or other elements of the database schema. This flag is especially recommended for SQL functions that have side effects or reveal internal application state. Without this flag, an attacker might be able to modify the schema of a database file to include invocations of the function with parameters chosen by the attacker, which the application will then execute when the database file is opened and read.
The fifth parameter is an arbitrary pointer. The implementation of the function can gain access to this pointer using [sqlite3_user_data()](#sqlite3_user_data).
The sixth, seventh and eighth parameters passed to the three "sqlite3_create_function\*" functions, xFunc, xStep and xFinal, are pointers to C-language functions that implement the SQL function or aggregate. A scalar SQL function requires an implementation of the xFunc callback only; NULL pointers must be passed as the xStep and xFinal parameters. An aggregate SQL function requires an implementation of xStep and xFinal and NULL pointer must be passed for xFunc. To delete an existing SQL function or aggregate, pass NULL pointers for all three function callbacks.
The sixth, seventh, eighth and ninth parameters (xStep, xFinal, xValue and xInverse) passed to sqlite3_create_window_function are pointers to C-language callbacks that implement the new function. xStep and xFinal must both be non-NULL. xValue and xInverse may either both be NULL, in which case a regular aggregate function is created, or must both be non-NULL, in which case the new function may be used as either an aggregate or aggregate window function. More details regarding the implementation of aggregate window functions are [available here](windowfunctions.md#udfwinfunc).
If the final parameter to sqlite3_create_function_v2() or sqlite3_create_window_function() is not NULL, then it is the destructor for the application data pointer. The destructor is invoked when the function is deleted, either by being overloaded or when the database connection closes. The destructor is also invoked if the call to sqlite3_create_function_v2() fails. When the destructor callback is invoked, it is passed a single argument which is a copy of the application data pointer which was the fifth parameter to sqlite3_create_function_v2().
It is permitted to register multiple implementations of the same functions with the same name but with either differing numbers of arguments or differing preferred text encodings. SQLite will use the implementation that most closely matches the way in which the SQL function is used. A function implementation with a non-negative nArg parameter is a better match than a function implementation with a negative nArg. A function where the preferred text encoding matches the database encoding is a better match than a function where the encoding is different. A function where the encoding difference is between UTF16le and UTF16be is a closer match than a function where the encoding difference is between UTF8 and UTF16.
Built-in functions may be overloaded by new application-defined functions.
An application-defined function is permitted to call other SQLite interfaces. However, such calls must not close the database connection nor finalize or reset the prepared statement in which the function is running.
------------------------------------------------------------------------
---
# Command Line Shell For SQLite
*Sección: Tools Extensions | Origen: https://www.sqlite.org/cli.html*
# 1. Getting Started
The SQLite project provides a command-line program named **sqlite3** (or **sqlite3.exe** on Windows) that allows the user to run SQL statements interactively against an SQLite database. This document provides a brief introduction on how to use the **sqlite3** program.
## 1.1. SQLite command-line program versus the SQLite library
The SQLite library is code that implements an SQL database engine. The "sqlite3" command-line program or "CLI" is an application that accepts user input and passes it down into the SQLite library for evaluation. Understand that these are two different things. When somebody says "SQLite" or "sqlite3" they might be referring to either the SQLite library itself, or the CLI that provides a human interface to the library. You will often need to use context to figure out exactly which of these two things the speaker is referring to.
This document is about the CLI, not the underlying SQLite library.
## 1.2. GUI Alternatives To The CLI
The **sqlite3** program is written by and for the core SQLite developers and is the officially supported way to accessing SQLite database files interactively. However, some users might prefer a Graphical User Interface (GUI). Several such programs are available from third-parties. One of those is [Visual DB](https://visualdb.com/sqlite), a sponsor of the SQLite project:
> [
](https://visualdb.com/sqlite)
Thanks to Visual DB for helping us make SQLite better for everyone!
## 1.3. Starting the CLI
Start the **sqlite3** program by typing "sqlite3" at the command prompt, optionally followed by the name of the file that holds the SQLite database (or [ZIP archive](#zipdb)). If the named file does not exist, a new database file with the given name will be created automatically. If no database file is specified on the command-line, a transient in-memory database is used. This in-memory database is deleted when the program exits.
On startup, the **sqlite3** program will show a brief banner message then prompt you to enter SQL. Type in SQL statements (terminated by a semicolon), press "Enter" and the SQL will be executed.
For example, to create a new SQLite database named "ex1.db" with a single table named "tbl1", you might do this:
\$ **sqlite3 ex1.db**\
SQLite version 3.36.0 2021-06-18 18:36:39\
Enter ".help" for usage hints.\
sqlite\> **create table tbl1(one text, two int);**\
sqlite\> **insert into tbl1 values('hello!',10),('goodbye',20);**\
sqlite\> **select \* from tbl1;**\
┌───────────┬─────┐\
│ one │ two │\
├───────────┼─────┤\
│ 'hello!' │ 10 │\
│ 'goodbye' │ 20 │\
└───────────┴─────┘\
sqlite\>\
Terminate the sqlite3 program by typing your system End-Of-File character (usually a Control-D). Use the interrupt character (usually a Control-C) to stop a long-running SQL statement.
Make sure you type a semicolon at the end of each SQL command! The sqlite3 program looks for a semicolon to know when your SQL command is complete. If you omit the semicolon, sqlite3 will give you a continuation prompt and wait for you to enter more text to complete the SQL command. This feature allows you to enter SQL commands that span multiple lines. For example:
sqlite\> **CREATE TABLE tbl2 (**\
...\> ** f1 varchar(30) primary key,**\
...\> ** f2 text,**\
...\> ** f3 real**\
...\> **);**\
sqlite\>\
## 1.4. Double-click Startup On Windows
Windows users can double-click on the **sqlite3.exe** icon to cause the command-line shell to pop-up a terminal window running SQLite. However, because double-clicking starts the sqlite3.exe without command-line arguments, no database file will have been specified, so SQLite will use a transient in-memory database that is deleted when the session exits. To use a persistent disk file as the database, enter the ".open" command immediately after the terminal window starts up:
SQLite version 3.36.0 2021-06-18 18:36:39\
Enter ".help" for usage hints.\
Connected to a transient in-memory database.\
Use ".open FILENAME" to reopen on a persistent database.\
sqlite\> **.open ex1.db**\
sqlite\>\
The example above causes the database file named "ex1.db" to be opened and used. The "ex1.db" file is created if it does not previously exist. You might want to use a full pathname to ensure that the file is in the directory that you think it is in. Use forward-slashes as the directory separator character. In other words use "c:/work/ex1.db", not "c:\work\ex1.db".
Alternatively, you can create a new database using the default temporary storage, then save that database into a disk file using the ".save" command:
SQLite version 3.36.0 2021-06-18 18:36:39\
Enter ".help" for usage hints.\
Connected to a transient in-memory database.\
Use ".open FILENAME" to reopen on a persistent database.\
sqlite\> *... many SQL commands omitted ...*\
sqlite\> **.save ex1.db**\
sqlite\>\
Be careful when using the ".save" command as it will overwrite any preexisting database files having the same name without prompting for confirmation. As with the ".open" command, you might want to use a full pathname with forward-slash directory separators to avoid ambiguity.
## 1.5. Running The CLI In A Web Browser
It is possible to compile the CLI using [Emscripten](https://en.wikipedia.org/wiki/Emscripten) so that it runs inside a web-browser. You can experiment with recent versions of the CLI at | Option | Purpose |
|---|---|
| ‑‑verbose | If present, output a more verbose report for each query analyzed. |
| ‑‑sample PERCENT | This parameter defaults to 0, causing the ".expert" command to recommend indexes based on the query and database schema alone. This is similar to the way the SQLite query planner selects indexes for queries if the user has not run the ANALYZE command on the database to generate data distribution statistics. If this option is passed a non-zero argument, the ".expert" command generates similar data distribution statistics for all indexes considered based on PERCENT percent of the rows currently stored in each database table. For databases with unusual data distributions, this may lead to better index recommendations, particularly if the application intends to run ANALYZE. For small databases and modern CPUs, there is usually no reason not to pass "--sample 100". However, gathering data distribution statistics can be expensive for large database tables. If the operation is too slow, try passing a smaller value for the --sample option. |
| json_each() | jsonb_each() | json_tree() | jsonb_tree() | |
| Recursively walk the substructure of the input JSON, or parse only a single layer | single layer | single layer | recursive | recursive |
| The "value" column returns text or JSONB for 'array' and 'object' | text | JSONB | text | JSONB |
| Supported since SQLite version... | 3.9.0 (2015-10-14) |
3.51.0 (2025-11-04) |
3.9.0 (2015-10-14) |
3.51.0 (2025-11-04) |
**[pragma-value:](syntax/pragma-value.md)** hide
**[signed-number:](syntax/signed-number.md)** show
A pragma can take either zero or one argument. The argument may be either in parentheses or it may be separated from the pragma name by an equal sign. The two syntaxes yield identical results. In many pragmas, the argument is a boolean. The boolean can be one of:
**1 yes true on\
0 no false off**
Keyword arguments can optionally appear in quotes. (Example: `'yes' [FALSE]`.) Some pragmas take a string literal as their argument. When a pragma takes a keyword argument, it will usually also take a numeric equivalent as well. For example, "0" and "no" mean the same thing, as does "1" and "yes". When querying the value of a setting, many pragmas return the number rather than the keyword.
A pragma may have an optional schema-name before the pragma name. The schema-name is the name of an [ATTACH](lang_attach.md)-ed database or "main" or "temp" for the main and the TEMP databases. If the optional schema name is omitted, "main" is assumed. In some pragmas, the schema name is meaningless and is simply ignored. In the documentation below, pragmas for which the schema name is meaningful are shown with a "*schema.*" prefix.
------------------------------------------------------------------------
## PRAGMA functions
PRAGMAs that return results and that have no side-effects can be accessed from ordinary [SELECT](lang_select.md) statements as [table-valued functions](vtab.md#tabfunc2). For each participating PRAGMA, the corresponding table-valued function has the same name as the PRAGMA with a 7-character "pragma\_" prefix. The PRAGMA argument and schema, if any, are passed as arguments to the table-valued function, with the schema as an optional, last argument.
For example, information about the columns in an index can be read using the [index_info pragma](pragma.md#pragma_index_info) as follows:
> \
> PRAGMA index_info('idx52');\
Or, the same content can be read using:
> \
> SELECT \* FROM pragma_index_info('idx52');\
The advantage of the table-valued function format is that the query can return just a subset of the PRAGMA columns, can include a WHERE clause, can use aggregate functions, and the table-valued function can be just one of several data sources in a join. For example, to get a list of all indexed columns in a schema, one could query:
> \
> SELECT DISTINCT m.name \|\| '.' \|\| ii.name AS 'indexed-columns'\
> FROM sqlite_schema AS m,\
> pragma_index_list(m.name) AS il,\
> pragma_index_info(il.name) AS ii\
> WHERE m.type='table'\
> ORDER BY 1;\
Additional notes:
- Table-valued functions exist only for built-in PRAGMAs, not for PRAGMAs defined using the [SQLITE_FCNTL_PRAGMA](c3ref/c_fcntl_begin_atomic_write.md#sqlitefcntlpragma) file control.
- Table-valued functions exist only for PRAGMAs that return results and that have no side-effects.
- This feature could be used to implement [information schema](https://en.wikipedia.org/wiki/Information_schema) by first creating a separate schema using
> \
> [ATTACH](lang_attach.md) ':memory:' AS 'information_schema';\
Then creating [VIEWs](lang_createview.md) in that schema that implement the official information schema tables using table-valued PRAGMA functions.
- The table-valued functions for PRAGMA feature was added in SQLite version 3.16.0 (2017-01-02). Prior versions of SQLite cannot use this feature.
------------------------------------------------------------------------
## List Of PRAGMAs
- [analysis_limit](pragma.md#pragma_analysis_limit)
- [application_id](pragma.md#pragma_application_id)
- [auto_vacuum](pragma.md#pragma_auto_vacuum)
- [automatic_index](pragma.md#pragma_automatic_index)
- [busy_timeout](pragma.md#pragma_busy_timeout)
- [cache_size](pragma.md#pragma_cache_size)
- [cache_spill](pragma.md#pragma_cache_spill)
- [~~case_sensitive_like¹~~](pragma.md#pragma_case_sensitive_like)
- [cell_size_check](pragma.md#pragma_cell_size_check)
- [checkpoint_fullfsync](pragma.md#pragma_checkpoint_fullfsync)
- [collation_list](pragma.md#pragma_collation_list)
- [compile_options](pragma.md#pragma_compile_options)
- [~~count_changes¹~~](pragma.md#pragma_count_changes)
- [~~data_store_directory¹~~](pragma.md#pragma_data_store_directory)
- [data_version](pragma.md#pragma_data_version)
- [database_list](pragma.md#pragma_database_list)
- [~~default_cache_size¹~~](pragma.md#pragma_default_cache_size)
- [defer_foreign_keys](pragma.md#pragma_defer_foreign_keys)
- [~~empty_result_callbacks¹~~](pragma.md#pragma_empty_result_callbacks)
- [encoding](pragma.md#pragma_encoding)
- [foreign_key_check](pragma.md#pragma_foreign_key_check)
- [foreign_key_list](pragma.md#pragma_foreign_key_list)
- [foreign_keys](pragma.md#pragma_foreign_keys)
- [freelist_count](pragma.md#pragma_freelist_count)
- [~~full_column_names¹~~](pragma.md#pragma_full_column_names)
- [fullfsync](pragma.md#pragma_fullfsync)
- [function_list](pragma.md#pragma_function_list)
- [hard_heap_limit](pragma.md#pragma_hard_heap_limit)
- [ignore_check_constraints](pragma.md#pragma_ignore_check_constraints)
- [incremental_vacuum](pragma.md#pragma_incremental_vacuum)
- [index_info](pragma.md#pragma_index_info)
- [index_list](pragma.md#pragma_index_list)
- [index_xinfo](pragma.md#pragma_index_xinfo)
- [integrity_check](pragma.md#pragma_integrity_check)
- [journal_mode](pragma.md#pragma_journal_mode)
- [journal_size_limit](pragma.md#pragma_journal_size_limit)
- [legacy_alter_table](pragma.md#pragma_legacy_alter_table)
- [legacy_file_format](pragma.md#pragma_legacy_file_format)
- [locking_mode](pragma.md#pragma_locking_mode)
- [max_page_count](pragma.md#pragma_max_page_count)
- [mmap_size](pragma.md#pragma_mmap_size)
- [module_list](pragma.md#pragma_module_list)
- [optimize](pragma.md#pragma_optimize)
- [page_count](pragma.md#pragma_page_count)
- [page_size](pragma.md#pragma_page_size)
- [parser_trace²](pragma.md#pragma_parser_trace)
- [pragma_list](pragma.md#pragma_pragma_list)
- [query_only](pragma.md#pragma_query_only)
- [quick_check](pragma.md#pragma_quick_check)
- [read_uncommitted](pragma.md#pragma_read_uncommitted)
- [recursive_triggers](pragma.md#pragma_recursive_triggers)
- [reverse_unordered_selects](pragma.md#pragma_reverse_unordered_selects)
- [schema_version³](pragma.md#pragma_schema_version)
- [secure_delete](pragma.md#pragma_secure_delete)
- [~~short_column_names¹~~](pragma.md#pragma_short_column_names)
- [shrink_memory](pragma.md#pragma_shrink_memory)
- [soft_heap_limit](pragma.md#pragma_soft_heap_limit)
- [stats³](pragma.md#pragma_stats)
- [synchronous](pragma.md#pragma_synchronous)
- [table_info](pragma.md#pragma_table_info)
- [table_list](pragma.md#pragma_table_list)
- [table_xinfo](pragma.md#pragma_table_xinfo)
- [temp_store](pragma.md#pragma_temp_store)
- [~~temp_store_directory¹~~](pragma.md#pragma_temp_store_directory)
- [threads](pragma.md#pragma_threads)
- [trusted_schema](pragma.md#pragma_trusted_schema)
- [user_version](pragma.md#pragma_user_version)
- [vdbe_addoptrace²](pragma.md#pragma_vdbe_addoptrace)
- [vdbe_debug²](pragma.md#pragma_vdbe_debug)
- [vdbe_listing²](pragma.md#pragma_vdbe_listing)
- [vdbe_trace²](pragma.md#pragma_vdbe_trace)
- [wal_autocheckpoint](pragma.md#pragma_wal_autocheckpoint)
- [wal_checkpoint](pragma.md#pragma_wal_checkpoint)
- [writable_schema³](pragma.md#pragma_writable_schema)
Notes:
1. Pragmas whose names are ~~struck through~~ are deprecated. Do not use them. They exist for historical compatibility.
2. These pragmas are only available in builds using non-standard compile-time options.
3. These pragmas are used for testing SQLite and are not recommended for use in application programs.
PRAGMA analysis_limit
------------------------------------------------------------------------
**PRAGMA analysis_limit;\
PRAGMA analysis_limit =** *N***;**
Query or change a limit on the [approximate ANALYZE](lang_analyze.md#approx) setting. This is the approximate number of rows examined in each index by the [ANALYZE](lang_analyze.md) command. If the argument *N* is omitted, then the analysis limit is unchanged. If the limit is zero, then the analysis limit is disabled and the ANALYZE command will examine all rows of each index. If N is greater than zero, then the analysis limit is set to N and subsequent ANALYZE commands will stop analyzing each index after it has examined approximately N rows. If N is a negative number or something other than an integer value, then the pragma behaves as if the N argument was omitted. In all cases, the value returned is the new analysis limit used for subsequent ANALYZE commands.
This pragma can be used to help the ANALYZE command run faster on large databases. The results of analysis are not as good when only part of each index is examined, but the results are usually good enough. Setting N to 100 or 1000 allows the ANALYZE command to run quickly, even on enormous database files.
This pragma was added in SQLite version 3.32.0 (2020-05-22). The current implementation only uses the lower 31 bits of the N value - higher order bits are silently ignored. Future versions of SQLite might begin using higher order bits.
Beginning with SQLite version 3.46.0 (2024-05-23), the recommended way of running [ANALYZE](lang_analyze.md) is with the [PRAGMA optimize](pragma.md#pragma_optimize) command. The [PRAGMA optimize](pragma.md#pragma_optimize) will automatically set a reasonable, temporary analysis limit that ensures that the [PRAGMA optimize](pragma.md#pragma_optimize) command will finish quickly even on enormous databases. Applications that use the [PRAGMA optimize](pragma.md#pragma_optimize) instead of running [ANALYZE](lang_analyze.md) directly do not need to set an analysis limit. PRAGMA application_id
------------------------------------------------------------------------
**PRAGMA** *schema.***application_id;\
PRAGMA** *schema.***application_id =** *integer* **;**
The application_id PRAGMA is used to query or set the 32-bit signed big-endian "Application ID" integer located at offset 68 into the [database header](fileformat2.md#database_header). Applications that use SQLite as their [application file-format](appfileformat.md) should set the Application ID integer to a unique integer so that utilities such as [file(1)](http://www.darwinsys.com/file/) can determine the specific file type rather than just reporting "SQLite3 Database". A list of assigned application IDs can be seen by consulting the [magic.txt](https://sqlite.org/src/artifact?ci=trunk&filename=magic.txt) file in the SQLite source repository.
See also the [user_version pragma](pragma.md#pragma_user_version). PRAGMA auto_vacuum
------------------------------------------------------------------------
**PRAGMA** *schema.***auto_vacuum;\
PRAGMA** *schema.***auto_vacuum =** *0 \| NONE \| 1 \| FULL \| 2 \| INCREMENTAL***;**
Query or set the auto-vacuum status in the database.
The default setting for auto-vacuum is 0 or "none", unless the [SQLITE_DEFAULT_AUTOVACUUM](compile.md#default_autovacuum) compile-time option is used. The "none" setting means that auto-vacuum is disabled. When auto-vacuum is disabled and data is deleted from a database, the database file remains the same size. Unused database file pages are added to a "[freelist](fileformat2.md#freelist)" and reused for subsequent inserts. So no database file space is lost. However, the database file does not shrink. In this mode the [VACUUM](lang_vacuum.md) command can be used to rebuild the entire database file and thus reclaim unused disk space.
When the auto-vacuum mode is 1 or "full", the freelist pages are moved to the end of the database file and the database file is truncated to remove the freelist pages at every transaction commit. Note, however, that auto-vacuum only truncates the freelist pages from the file. Auto-vacuum does not defragment the database nor repack individual database pages the way that the [VACUUM](lang_vacuum.md) command does. In fact, because it moves pages around within the file, auto-vacuum can actually make fragmentation worse.
Auto-vacuuming is only possible if the database stores some additional information that allows each database page to be traced backwards to its referrer. Therefore, auto-vacuuming must be turned on before any tables are created. It is not possible to enable or disable auto-vacuum after a table has been created.
When the value of auto-vacuum is 2 or "incremental" then the additional information needed to do auto-vacuuming is stored in the database file but auto-vacuuming does not occur automatically at each commit as it does with auto_vacuum=full. In incremental mode, the separate [incremental_vacuum](pragma.md#pragma_incremental_vacuum) pragma must be invoked to cause the auto-vacuum to occur.
The database connection can be changed between full and incremental autovacuum mode at any time. However, changing from "none" to "full" or "incremental" can only occur when the database is new (no tables have yet been created) or by running the [VACUUM](lang_vacuum.md) command. To change auto-vacuum modes, first use the auto_vacuum pragma to set the new desired mode, then invoke the [VACUUM](lang_vacuum.md) command to reorganize the entire database file. To change from "full" or "incremental" back to "none" always requires running [VACUUM](lang_vacuum.md) even on an empty database.
When the auto_vacuum pragma is invoked with no arguments, it returns the current auto_vacuum mode.
PRAGMA automatic_index
------------------------------------------------------------------------
**PRAGMA automatic_index;\
PRAGMA automatic_index =** *boolean***;**
Query, set, or clear the [automatic indexing](optoverview.md#autoindex) capability.
[Automatic indexing](optoverview.md#autoindex) is enabled by default as of [version 3.7.17](releaselog/3_7_17.md) (2013-05-20), but this might change in future releases of SQLite. PRAGMA busy_timeout
------------------------------------------------------------------------
**PRAGMA busy_timeout;\
PRAGMA busy_timeout =** *milliseconds***;**
Query or change the setting of the [busy timeout](c3ref/busy_timeout.md). This pragma is an alternative to the [sqlite3_busy_timeout()](c3ref/busy_timeout.md) C-language interface which is made available as a pragma for use with language bindings that do not provide direct access to [sqlite3_busy_timeout()](c3ref/busy_timeout.md).
Each database connection can only have a single [busy handler](c3ref/busy_handler.md). This PRAGMA sets the busy handler for the process, possibly overwriting any previously set busy handler. PRAGMA cache_size
------------------------------------------------------------------------
**PRAGMA** *schema.***cache_size;\
PRAGMA** *schema.***cache_size =** *pages***;\
PRAGMA** *schema.***cache_size = -***kibibytes***;**
Query or change the suggested maximum number of database disk pages that SQLite will hold in memory at once per open database file. Whether or not this suggestion is honored is at the discretion of the [Application Defined Page Cache](c3ref/pcache_methods2.md). The default page cache that is built into SQLite honors the request, however alternative application-defined page cache implementations may choose to interpret the suggested cache size in different ways or to ignore it altogether. The default suggested cache size is -2000, which means the cache size is limited to 2048000 bytes of memory. The default suggested cache size can be altered using the [SQLITE_DEFAULT_CACHE_SIZE](compile.md#default_cache_size) compile-time options. The TEMP database has a default suggested cache size of 0 pages.
If the argument N is positive then the suggested cache size is set to N. If the argument N is negative, then the number of cache pages is adjusted to be a number of pages that would use approximately abs(N\*1024) bytes of memory based on the current page size. SQLite remembers the number of pages in the page cache, not the amount of memory used. So if you set the cache size using a negative number and subsequently change the page size (using the [PRAGMA page_size](pragma.md#pragma_page_size) command) then the maximum amount of cache memory will go up or down in proportion to the change in page size.
*Backwards compatibility note:* The behavior of cache_size with a negative N was different prior to [version 3.7.10](releaselog/3_7_10.md) (2012-01-16). In earlier versions, the number of pages in the cache was set to the absolute value of N.
When you change the cache size using the cache_size pragma, the change only endures for the current session. The cache size reverts to the default value when the database is closed and reopened.
The default page cache implemention does not allocate the full amount of cache memory all at once. Cache memory is allocated in smaller chunks on an as-needed basis. The page_cache setting is a (suggested) upper bound on the amount of memory that the cache can use, not the amount of memory it will use all of the time. This is the behavior of the default page cache implementation, but an [application defined page cache](c3ref/pcache_methods2.md) is free to behave differently if it wants. PRAGMA cache_spill
------------------------------------------------------------------------
**PRAGMA cache_spill;\
PRAGMA cache_spill=***boolean***;\
PRAGMA** *schema.***cache_spill=*N*;**
The cache_spill pragma enables or disables the ability of the pager to spill dirty cache pages to the database file in the middle of a transaction. Cache_spill is enabled by default and most applications should leave it that way as cache spilling is usually advantageous. However, a cache spill has the side-effect of acquiring an [EXCLUSIVE lock](lockingv3.md#excl_lock) on the database file. Hence, some applications that have large long-running transactions may want to disable cache spilling in order to prevent the application from acquiring an exclusive lock on the database until the moment that the transaction [COMMIT](lang_transaction.md)s.
The "PRAGMA cache_spill=*N*" form of this pragma sets a minimum cache size threshold required for spilling to occur. The number of pages in cache must exceed both the cache_spill threshold and the maximum cache size set by the [PRAGMA cache_size](pragma.md#pragma_cache_size) statement in order for spilling to occur.
The "PRAGMA cache_spill=*boolean*" form of this pragma applies across all databases attached to the database connection. But the "PRAGMA cache_spill=*N*" form of this statement only applies to the "main" schema or whatever other schema is specified as part of the statement. PRAGMA case_sensitive_like
------------------------------------------------------------------------
**PRAGMA case_sensitive_like =** *boolean***;**
The default behavior of the [LIKE](lang_expr.md#like) operator is to ignore case for ASCII characters. Hence, by default **'a' LIKE 'A'** is true. The case_sensitive_like pragma installs a new application-defined LIKE function that is either case sensitive or insensitive depending on the value of the case_sensitive_like pragma. When case_sensitive_like is disabled, the default LIKE behavior is expressed. When case_sensitive_like is enabled, case becomes significant. So, for example, **'a' LIKE 'A'** is false but **'a' LIKE 'a'** is still true.
This pragma uses [sqlite3_create_function()](c3ref/create_function.md) to overload the LIKE and GLOB functions, which may override previous implementations of LIKE and GLOB registered by the application. This pragma only changes the behavior of the SQL [LIKE](lang_expr.md#like) operator. It does not change the behavior of the [sqlite3_strlike()](c3ref/strlike.md) C-language interface, which is always case insensitive.
**WARNING:** If a database uses the LIKE operator anywhere in the schema, such as in a [CHECK constraint](lang_createtable.md#ckconst) or in an [expression index](expridx.md) or in the WHERE clause of a [partial index](partialindex.md), then changing the definition of the LIKE operator using this PRAGMA can cause the database to appear to be corrupt. [PRAGMA integrity_check](pragma.md#pragma_integrity_check) will report errors. The database is not really corrupt in that changing the behavior of LIKE back to the way it was when the schema was defined and the database was populated will clear the problem. If the use of LIKE occurs only in indexes, then the problem can be cleared by running [REINDEX](lang_reindex.md). Nevertheless, the use of the case_sensitive_like pragma is discouraged.
**This pragma is deprecated** and exists for backwards compatibility only. New applications should avoid using this pragma. Older applications should discontinue use of this pragma at the earliest opportunity. This pragma may be omitted from the build when SQLite is compiled using [SQLITE_OMIT_DEPRECATED](compile.md#omit_deprecated).
PRAGMA cell_size_check
------------------------------------------------------------------------
**PRAGMA cell_size_check\
PRAGMA cell_size_check =** *boolean***;**
The cell_size_check pragma enables or disables additional sanity checking on database b-tree pages as they are initially read from disk. With cell size checking enabled, database corruption is detected earlier and is less likely to "spread". However, there is a small performance hit for doing the extra checks and so cell size checking is turned off by default. PRAGMA checkpoint_fullfsync
------------------------------------------------------------------------
**PRAGMA checkpoint_fullfsync\
PRAGMA checkpoint_fullfsync =** *boolean***;**
Query or change the fullfsync flag for [checkpoint](wal.md#ckpt) operations. If this flag is set, then the F_FULLFSYNC syncing method is used during checkpoint operations on systems that support F_FULLFSYNC. The default value of the checkpoint_fullfsync flag is off. Only Mac OS-X supports F_FULLFSYNC.
If the [fullfsync](pragma.md#pragma_fullfsync) flag is set, then the F_FULLFSYNC syncing method is used for all sync operations and the checkpoint_fullfsync setting is irrelevant.
PRAGMA collation_list
------------------------------------------------------------------------
**PRAGMA collation_list;**
Return a list of the collating sequences defined for the current database connection.
PRAGMA compile_options
------------------------------------------------------------------------
**PRAGMA compile_options;**
This pragma returns the names of [compile-time options](compile.md) used when building SQLite, one option per row. The "SQLITE\_" prefix is omitted from the returned option names. See also the [sqlite3_compileoption_get()](c3ref/compileoption_get.md) C/C++ interface and the [sqlite_compileoption_get()](lang_corefunc.md#sqlite_compileoption_get) SQL functions.
PRAGMA count_changes
------------------------------------------------------------------------
**PRAGMA count_changes;\
PRAGMA count_changes =** boolean**;**
Query or change the count-changes flag. Normally, when the count-changes flag is not set, [INSERT](lang_insert.md), [UPDATE](lang_update.md) and [DELETE](lang_delete.md) statements return no data. When count-changes is set, each of these commands returns a single row of data consisting of one integer value - the number of rows inserted, modified or deleted by the command. The returned change count does not include any insertions, modifications or deletions performed by triggers, any changes made automatically by [foreign key actions](foreignkeys.md#fk_actions), or updates caused by an [upsert](lang_upsert.md).
Another way to get the row change counts is to use the [sqlite3_changes()](c3ref/changes.md) or [sqlite3_total_changes()](c3ref/total_changes.md) interfaces. There is a subtle difference, though. When an INSERT, UPDATE, or DELETE is run against a view using an [INSTEAD OF trigger](lang_createtrigger.md#instead_of_trigger), the count_changes pragma reports the number of rows in the view that fired the trigger, whereas [sqlite3_changes()](c3ref/changes.md) and [sqlite3_total_changes()](c3ref/total_changes.md) do not.
**This pragma is deprecated** and exists for backwards compatibility only. New applications should avoid using this pragma. Older applications should discontinue use of this pragma at the earliest opportunity. This pragma may be omitted from the build when SQLite is compiled using [SQLITE_OMIT_DEPRECATED](compile.md#omit_deprecated).
PRAGMA data_store_directory
------------------------------------------------------------------------
**PRAGMA data_store_directory;\
PRAGMA data_store_directory = '***directory-name***';**
Query or change the value of the [sqlite3_data_directory](c3ref/data_directory.md) global variable, which windows operating-system interface backends use to determine where to store database files specified using a relative pathname.
Changing the data_store_directory setting is not threadsafe. Never change the data_store_directory setting if another thread within the application is running any SQLite interface at the same time. Doing so results in undefined behavior. Changing the data_store_directory setting writes to the [sqlite3_data_directory](c3ref/data_directory.md) global variable and that global variable is not protected by a mutex.
This facility is provided for WinRT which does not have an OS mechanism for reading or changing the current working directory. The use of this pragma in any other context is discouraged and may be disallowed in future releases.
**This pragma is deprecated** and exists for backwards compatibility only. New applications should avoid using this pragma. Older applications should discontinue use of this pragma at the earliest opportunity. This pragma may be omitted from the build when SQLite is compiled using [SQLITE_OMIT_DEPRECATED](compile.md#omit_deprecated).
PRAGMA data_version
------------------------------------------------------------------------
**PRAGMA** *schema.***data_version;**
The "PRAGMA data_version" command provides an indication that the database file has been modified. Interactive programs that hold database content in memory or that display database content on-screen can use the PRAGMA data_version command to determine if they need to flush and reload their memory or update the screen display.
The integer values returned by two invocations of "PRAGMA data_version" from the same connection will be different if changes were committed to the database by any other connection in the interim. The "PRAGMA data_version" value is unchanged for commits made on the same database connection. The behavior of "PRAGMA data_version" is the same for all database connections, including database connections in separate processes and [shared cache](sharedcache.md) database connections.
The "PRAGMA data_version" value is a local property of each database connection and so values returned by two concurrent invocations of "PRAGMA data_version" on separate database connections are often different even though the underlying database is identical. It is only meaningful to compare the "PRAGMA data_version" values returned by the same database connection at two different points in time. PRAGMA database_list
------------------------------------------------------------------------
**PRAGMA database_list;**
This pragma works like a query to return one row for each database attached to the current database connection. The second column is "main" for the main database file, "temp" for the database file used to store TEMP objects, or the name of the ATTACHed database for other database files. The third column is the name of the database file itself, or an empty string if the database is not associated with a file.
PRAGMA default_cache_size
------------------------------------------------------------------------
**PRAGMA** *schema.***default_cache_size;\
PRAGMA** *schema.***default_cache_size =** *Number-of-pages***;**
This pragma queries or sets the suggested maximum number of pages of disk cache that will be allocated per open database file. The difference between this pragma and [cache_size](pragma.md#pragma_cache_size) is that the value set here persists across database connections. The value of the default cache size is stored in the 4-byte big-endian integer located at offset 48 in the header of the database file.
**This pragma is deprecated** and exists for backwards compatibility only. New applications should avoid using this pragma. Older applications should discontinue use of this pragma at the earliest opportunity. This pragma may be omitted from the build when SQLite is compiled using [SQLITE_OMIT_DEPRECATED](compile.md#omit_deprecated).
PRAGMA defer_foreign_keys
------------------------------------------------------------------------
**PRAGMA defer_foreign_keys\
PRAGMA defer_foreign_keys =** *boolean***;**
When the defer_foreign_keys [PRAGMA](pragma.md#syntax) is on, enforcement of all [foreign key constraints](foreignkeys.md) is delayed until the outermost transaction is committed. The defer_foreign_keys pragma defaults to OFF so that foreign key constraints are only deferred if they are created as "DEFERRABLE INITIALLY DEFERRED". The defer_foreign_keys pragma is automatically switched off at each COMMIT or ROLLBACK. Hence, the defer_foreign_keys pragma must be separately enabled for each transaction. This pragma is only meaningful if foreign key constraints are enabled, of course.
The [sqlite3_db_status](c3ref/db_status.md)(db,[SQLITE_DBSTATUS_DEFERRED_FKS](c3ref/c_dbstatus_options.md#sqlitedbstatusdeferredfks),...) C-language interface can be used during a transaction to determine if there are deferred and unresolved foreign key constraints.
Caution: Setting "defer_foreign_keys=0" resets the internal foreign-key tracking state of the database connection, so that it becomes possible to commit the current transaction even if there are foreign key violations.
PRAGMA empty_result_callbacks
------------------------------------------------------------------------
**PRAGMA empty_result_callbacks;\
PRAGMA empty_result_callbacks =** *boolean***;**
Query or change the empty-result-callbacks flag.
The empty-result-callbacks flag affects the [sqlite3_exec()](c3ref/exec.md) API only. Normally, when the empty-result-callbacks flag is cleared, the callback function supplied to the [sqlite3_exec()](c3ref/exec.md) is not invoked for commands that return zero rows of data. When empty-result-callbacks is set in this situation, the callback function is invoked exactly once, with the third parameter set to 0 (NULL). This is to enable programs that use the [sqlite3_exec()](c3ref/exec.md) API to retrieve column-names even when a query returns no data.
**This pragma is deprecated** and exists for backwards compatibility only. New applications should avoid using this pragma. Older applications should discontinue use of this pragma at the earliest opportunity. This pragma may be omitted from the build when SQLite is compiled using [SQLITE_OMIT_DEPRECATED](compile.md#omit_deprecated).
PRAGMA encoding
------------------------------------------------------------------------
**PRAGMA encoding;\
PRAGMA encoding = 'UTF-8';\
PRAGMA encoding = 'UTF-16';\
PRAGMA encoding = 'UTF-16le';\
PRAGMA encoding = 'UTF-16be';**
In first form, if the main database has already been created, then this pragma returns the text encoding used by the main database, one of 'UTF-8', 'UTF-16le' (little-endian UTF-16 encoding) or 'UTF-16be' (big-endian UTF-16 encoding). If the main database has not already been created, then the value returned is the text encoding that will be used to create the main database, if it is created by this session.
The second through fifth forms of this pragma set the encoding that the main database will be created with if it is created by this session. The string 'UTF-16' is interpreted as "UTF-16 encoding using native machine byte-ordering". It is not possible to change the text encoding of a database after it has been created and any attempt to do so will be silently ignored.
If no encoding is first set with this pragma, then the encoding with which the main database will be created defaults to one determined by the [API used to open the connection](c3ref/open.md).
Once an encoding has been set for a database, it cannot be changed.
Databases created by the [ATTACH](lang_attach.md) command always use the same encoding as the main database. An attempt to [ATTACH](lang_attach.md) a database with a different text encoding from the "main" database will fail.
PRAGMA foreign_key_check
------------------------------------------------------------------------
**PRAGMA** *schema.***foreign_key_check;\
PRAGMA** *schema.***foreign_key_check(***table-name***);**
The foreign_key_check pragma checks the database, or the table called "*table-name*", for [foreign key constraints](foreignkeys.md) that are violated. The foreign_key_check pragma returns one row output for each foreign key violation. There are four columns in each result row. The first column is the name of the table that contains the REFERENCES clause. The second column is the [rowid](lang_createtable.md#rowid) of the row that contains the invalid REFERENCES clause, or NULL if the child table is a [WITHOUT ROWID](withoutrowid.md) table. The third column is the name of the table that is referred to. The fourth column is the index of the specific foreign key constraint that failed. The fourth column in the output of the foreign_key_check pragma is the same integer as the first column in the output of the [foreign_key_list pragma](pragma.md#pragma_foreign_key_list). When a "*table-name*" is specified, the only foreign key constraints checked are those created by REFERENCES clauses in the CREATE TABLE statement for *table-name*.
PRAGMA foreign_key_list
------------------------------------------------------------------------
**PRAGMA foreign_key_list(***table-name***);**
This pragma returns one row for each [foreign key constraint](foreignkeys.md) created by a REFERENCES clause in the CREATE TABLE statement of table "*table-name*". PRAGMA foreign_keys
------------------------------------------------------------------------
**PRAGMA foreign_keys;\
PRAGMA foreign_keys =** *boolean***;**
Query, set, or clear the enforcement of [foreign key constraints](foreignkeys.md).
This pragma is a no-op within a transaction; foreign key constraint enforcement may only be enabled or disabled when there is no pending [BEGIN](lang_transaction.md) or [SAVEPOINT](lang_savepoint.md).
Changing the foreign_keys setting affects the execution of all statements prepared using the database connection, including those prepared before the setting was changed. Any existing statements prepared using the legacy [sqlite3_prepare()](c3ref/prepare.md) interface may fail with an [SQLITE_SCHEMA](rescode.md#schema) error after the foreign_keys setting is changed.
As of SQLite [version 3.6.19](releaselog/3_6_19.md), the default setting for foreign key enforcement is OFF. However, that might change in a future release of SQLite. The default setting for foreign key enforcement can be specified at compile-time using the [SQLITE_DEFAULT_FOREIGN_KEYS](compile.md#default_foreign_keys) preprocessor macro. To minimize future problems, applications should set the foreign key enforcement flag as required by the application and not depend on the default setting. PRAGMA freelist_count
------------------------------------------------------------------------
**PRAGMA** *schema.***freelist_count;**
Return the number of unused pages in the database file.
PRAGMA full_column_names
------------------------------------------------------------------------
**PRAGMA full_column_names;\
PRAGMA full_column_names =** *boolean***;**
Query or change the full_column_names flag. This flag together with the [short_column_names](pragma.md#pragma_short_column_names) flag determine the way SQLite assigns names to result columns of [SELECT](lang_select.md) statements. Result columns are named by applying the following rules in order:
1. If there is an AS clause on the result, then the name of the column is the right-hand side of the AS clause.
2. If the result is a general expression, not just the name of a source table column, then the name of the result is a copy of the expression text.
3. If the [short_column_names](pragma.md#pragma_short_column_names) pragma is ON, then the name of the result is the name of the source table column without the source table name prefix: COLUMN.
4. If both pragmas [short_column_names](pragma.md#pragma_short_column_names) and [full_column_names](pragma.md#pragma_full_column_names) are OFF then case (2) applies.
5. The name of the result column is a combination of the source table and source column name: TABLE.COLUMN
**This pragma is deprecated** and exists for backwards compatibility only. New applications should avoid using this pragma. Older applications should discontinue use of this pragma at the earliest opportunity. This pragma may be omitted from the build when SQLite is compiled using [SQLITE_OMIT_DEPRECATED](compile.md#omit_deprecated).
PRAGMA fullfsync
------------------------------------------------------------------------
**PRAGMA fullfsync\
PRAGMA fullfsync =** *boolean***;**
Query or change the fullfsync flag. This flag determines whether or not the F_FULLFSYNC syncing method is used on systems that support it. The default value of the fullfsync flag is off. Only Mac OS X supports F_FULLFSYNC.
See also [checkpoint_fullfsync](pragma.md#pragma_checkpoint_fullfsync).
PRAGMA function_list
------------------------------------------------------------------------
**PRAGMA function_list;**
This pragma returns a list of SQL functions known to the database connection. Each row of the result describes a single calling signature for a single SQL function. Some SQL functions will have multiple rows in the result set if they can (for example) be invoked with a varying number of arguments or can accept text in various encodings. PRAGMA hard_heap_limit
------------------------------------------------------------------------
**PRAGMA hard_heap_limit\
PRAGMA hard_heap_limit=***N*
This pragma invokes the [sqlite3_hard_heap_limit64()](c3ref/hard_heap_limit64.md) interface with the argument N, if N is specified and N is a positive integer that is less than the current hard heap limit. The hard_heap_limit pragma always returns the same integer that would be returned by the [sqlite3_hard_heap_limit64](c3ref/hard_heap_limit64.md)(-1) C-language function. That is to say, it always returns the value of the hard heap limit that is set after any changes imposed by this PRAGMA.
This pragma can only lower the heap limit, never raise it. The C-language interface [sqlite3_hard_heap_limit64()](c3ref/hard_heap_limit64.md) must be used to raise the heap limit.
See also the [soft_heap_limit pragma](pragma.md#pragma_soft_heap_limit). PRAGMA ignore_check_constraints
------------------------------------------------------------------------
**PRAGMA ignore_check_constraints =** *boolean***;**
This pragma enables or disables the enforcement of CHECK constraints. The default setting is off, meaning that CHECK constraints are enforced by default.
PRAGMA incremental_vacuum
------------------------------------------------------------------------
**PRAGMA** *schema.***incremental_vacuum***(N)***;\
PRAGMA** *schema.***incremental_vacuum;**
The incremental_vacuum pragma causes up to *N* pages to be removed from the [freelist](fileformat2.md#freelist). The database file is truncated by the same amount. The incremental_vacuum pragma has no effect if the database is not in [auto_vacuum=incremental](#pragma_auto_vacuum) mode or if there are no pages on the freelist. If there are fewer than *N* pages on the freelist, or if *N* is less than 1, or if the "(*N*)" argument is omitted, then the entire freelist is cleared.
PRAGMA index_info
------------------------------------------------------------------------
**PRAGMA** *schema.***index_info(***index-name***);**
This pragma returns one row for each key column in the named index. A key column is a column that is actually named in the [CREATE INDEX](lang_createindex.md) index statement or [UNIQUE constraint](lang_createtable.md#uniqueconst) or [PRIMARY KEY constraint](lang_createtable.md#primkeyconst) that created the index. Index entries also usually contain auxiliary columns that point back to the table row being indexed. The auxiliary index-columns are not shown by the index_info pragma, but they are listed by the [index_xinfo pragma](pragma.md#pragma_index_xinfo).
Output columns from the index_info pragma are as follows:
1. The rank of the column within the index. (0 means left-most.)
2. The rank of the column within the table being indexed. A value of -1 means [rowid](lang_createtable.md#rowid) and a value of -2 means that an [expression](expridx.md) is being used.
3. The name of the column being indexed. This columns is NULL if the column is the [rowid](lang_createtable.md#rowid) or an [expression](expridx.md).
If there is no index named *index-name* but there is a [WITHOUT ROWID](withoutrowid.md) table with that name, then (as of SQLite [version 3.30.0](releaselog/3_30_0.md) on 2019-10-04) this pragma returns the PRIMARY KEY columns of the WITHOUT ROWID table as they are used in the records of the underlying b-tree, which is to say with duplicate columns removed. PRAGMA index_list
------------------------------------------------------------------------
**PRAGMA** *schema.***index_list(***table-name***);**
This pragma returns one row for each index associated with the given table.
Output columns from the index_list pragma are as follows:
1. A sequence number assigned to each index for internal tracking purposes.
2. The name of the index.
3. "1" if the index is UNIQUE and "0" if not.
4. "c" if the index was created by a [CREATE INDEX](lang_createindex.md) statement, "u" if the index was created by a [UNIQUE constraint](lang_createtable.md#uniqueconst), or "pk" if the index was created by a [PRIMARY KEY constraint](lang_createtable.md#primkeyconst).
5. "1" if the index is a [partial index](partialindex.md) and "0" if not.
PRAGMA index_xinfo
------------------------------------------------------------------------
**PRAGMA** *schema.***index_xinfo(***index-name***);**
This pragma returns information about every column in an index. Unlike this [index_info pragma](pragma.md#pragma_index_info), this pragma returns information about every column in the index, not just the key columns. (A key column is a column that is actually named in the [CREATE INDEX](lang_createindex.md) index statement or [UNIQUE constraint](lang_createtable.md#uniqueconst) or [PRIMARY KEY constraint](lang_createtable.md#primkeyconst) that created the index. Auxiliary columns are additional columns needed to locate the table entry that corresponds to each index entry.)
Output columns from the index_xinfo pragma are as follows:
1. The rank of the column within the index. (0 means left-most. Key columns come before auxiliary columns.)
2. The rank of the column within the table being indexed, or -1 if the index-column is the [rowid](lang_createtable.md#rowid) of the table being indexed and -2 if the [index is on an expression](expridx.md).
3. The name of the column being indexed, or NULL if the index-column is the [rowid](lang_createtable.md#rowid) of the table being indexed or an [expression](expridx.md).
4. 1 if the index-column is sorted in reverse (DESC) order by the index and 0 otherwise.
5. The name for the [collating sequence](datatype3.md#collation) used to compare values in the index-column.
6. 1 if the index-column is a key column and 0 if the index-column is an auxiliary column.
If there is no index named *index-name* but there is a [WITHOUT ROWID](withoutrowid.md) table with that name, then (as of SQLite [version 3.30.0](releaselog/3_30_0.md) on 2019-10-04) this pragma returns the columns of the WITHOUT ROWID table as they are used in the records of the underlying b-tree, which is to say with de-duplicated PRIMARY KEY columns first followed by data columns. PRAGMA integrity_check
------------------------------------------------------------------------
**PRAGMA** *schema.***integrity_check;\
PRAGMA** *schema.***integrity_check(***N***)\
PRAGMA** *schema.***integrity_check(***TABLENAME***)**
This pragma does a low-level formatting and consistency check of the database. The integrity_check pragma look for:
- Table or index entries that are out of sequence
- Misformatted records
- Missing pages
- Missing or surplus index entries
- UNIQUE, CHECK, and NOT NULL constraint errors
- Integrity of the freelist
- Sections of the database that are used more than once, or not at all
If the integrity_check pragma finds problems, strings are returned (as multiple rows with a single column per row) which describe the problems. Pragma integrity_check will return at most *N* errors before the analysis quits, with N defaulting to 100. If pragma integrity_check finds no errors, a single row with the value 'ok' is returned.
The usual case is that the entire database file is checked. However, if the argument is *TABLENAME*, then checking is only performed for the the table named and its associated indexes. This is called a "partial integrity check". Because only a subset of the database is checked, errors such as unused sections of the file or duplication use of the same section of the file by two or more tables cannot be detected. The freelist is only verified on a partial integrity check if *TABLENAME* is [sqlite_schema](schematab.md) or one of its aliases. Support for partial integrity checks was added with version 3.33.0 (2020-08-14).
PRAGMA integrity_check does not find [FOREIGN KEY](foreignkeys.md) errors. Use the [PRAGMA foreign_key_check](pragma.md#pragma_foreign_key_check) command to find errors in FOREIGN KEY constraints.
See also the [PRAGMA quick_check](pragma.md#pragma_quick_check) command which does most of the checking of PRAGMA integrity_check but runs much faster.
PRAGMA journal_mode
------------------------------------------------------------------------
**PRAGMA** *schema.***journal_mode;\
PRAGMA** *schema.***journal_mode = *DELETE \| TRUNCATE \| PERSIST \| MEMORY \| WAL \| OFF***
This pragma queries or sets the journal mode for databases associated with the current [database connection](c3ref/sqlite3.md).
The first form of this pragma queries the current journaling mode for *database*. When *database* is omitted, the "main" database is queried.
The second form changes the journaling mode for "*database*" or for all attached databases if "*database*" is omitted. The new journal mode is returned. If the journal mode could not be changed, the original journal mode is returned.
The DELETE journaling mode is the default. In the DELETE mode, the rollback journal is deleted at the conclusion of each transaction. Indeed, the delete operation is the action that causes the transaction to commit. (See the document titled [Atomic Commit In SQLite](atomiccommit.md) for additional detail.)
The TRUNCATE journaling mode commits transactions by truncating the rollback journal to zero-length instead of deleting it. On many systems, truncating a file is much faster than deleting the file since the containing directory does not need to be changed.
The PERSIST journaling mode prevents the rollback journal from being deleted at the end of each transaction. Instead, the header of the journal is overwritten with zeros. This will prevent other database connections from rolling the journal back. The PERSIST journaling mode is useful as an optimization on platforms where deleting or truncating a file is much more expensive than overwriting the first block of a file with zeros. See also: [PRAGMA journal_size_limit](pragma.md#pragma_journal_size_limit) and [SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT](compile.md#default_journal_size_limit).
The MEMORY journaling mode stores the rollback journal in volatile RAM. This saves disk I/O but at the expense of database safety and integrity. If the application using SQLite crashes in the middle of a transaction when the MEMORY journaling mode is set, then the database file will very likely [go corrupt](howtocorrupt.md#cfgerr).
The WAL journaling mode uses a [write-ahead log](wal.md) instead of a rollback journal to implement transactions. The WAL journaling mode is persistent; after being set it stays in effect across multiple database connections and after closing and reopening the database. A database in WAL journaling mode can only be accessed by SQLite [version 3.7.0](releaselog/3_7_0.md) (2010-07-21) or later.
The OFF journaling mode disables the rollback journal completely. No rollback journal is ever created and hence there is never a rollback journal to delete. The OFF journaling mode disables the atomic commit and rollback capabilities of SQLite. The [ROLLBACK](lang_transaction.md) command no longer works; it behaves in an undefined way. Applications must avoid using the [ROLLBACK](lang_transaction.md) command when the journal mode is OFF. If the application crashes in the middle of a transaction when the OFF journaling mode is set, then the database file will very likely [go corrupt](howtocorrupt.md#cfgerr). Without a journal, there is no way for a statement to unwind partially completed operations following a constraint error. This might also leave the database in a corrupted state. For example, if a duplicate entry causes a [CREATE UNIQUE INDEX](lang_createindex.md) statement to fail half-way through, it will leave behind a partially created, and hence corrupt, index. Because OFF journaling mode allows the database file to be corrupted using ordinary SQL, it is disabled when [SQLITE_DBCONFIG_DEFENSIVE](c3ref/c_dbconfig_defensive.md#sqlitedbconfigdefensive) is enabled.
Note that the journal_mode for an [in-memory database](inmemorydb.md) is either MEMORY or OFF and can not be changed to a different value. An attempt to change the journal_mode of an [in-memory database](inmemorydb.md) to any setting other than MEMORY or OFF is ignored. Note also that the journal_mode cannot be changed while a transaction is active.
PRAGMA journal_size_limit
------------------------------------------------------------------------
**PRAGMA** *schema.***journal_size_limit\
PRAGMA** *schema.***journal_size_limit =** *N* **;**
If a database connection is operating in [exclusive locking mode](pragma.md#pragma_locking_mode) or in [persistent journal mode](pragma.md#pragma_journal_mode) (PRAGMA journal_mode=persist) then after committing a transaction the [rollback journal](lockingv3.md#rollback) file may remain in the file-system. This increases performance for subsequent transactions since overwriting an existing file is faster than append to a file, but it also consumes file-system space. After a large transaction (e.g. a [VACUUM](lang_vacuum.md)), the rollback journal file may consume a very large amount of space.
Similarly, in [WAL mode](wal.md), the write-ahead log file is not truncated following a [checkpoint](wal.md#ckpt). Instead, SQLite reuses the existing file for subsequent WAL entries since overwriting is faster than appending.
The journal_size_limit pragma may be used to limit the size of rollback-journal and WAL files left in the file-system after transactions or checkpoints. Each time a transaction is committed or a WAL file resets, SQLite compares the size of the rollback journal file or WAL file left in the file-system to the size limit set by this pragma and if the journal or WAL file is larger it is truncated to the limit.
The second form of the pragma listed above is used to set a new limit in bytes for the specified database. A negative number implies no limit. To always truncate rollback journals and WAL files to their minimum size, set the journal_size_limit to zero. Both the first and second forms of the pragma listed above return a single result row containing a single integer column - the value of the journal size limit in bytes. The default journal size limit is -1 (no limit). The [SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT](compile.md#default_journal_size_limit) preprocessor macro can be used to change the default journal size limit at compile-time.
This pragma only operates on the single database specified prior to the pragma name (or on the "main" database if no database is specified.) There is no way to change the journal size limit on all attached databases using a single PRAGMA statement. The size limit must be set separately for each attached database. PRAGMA legacy_alter_table
------------------------------------------------------------------------
**PRAGMA legacy_alter_table;\
PRAGMA legacy_alter_table = *boolean***
This pragma sets or queries the value of the legacy_alter_table flag. When this flag is on, the [ALTER TABLE RENAME](lang_altertable.md#altertabrename) command (for changing the name of a table) works as it did in SQLite 3.24.0 (2018-06-04) and earlier. More specifically, when this flag is on the [ALTER TABLE RENAME](lang_altertable.md#altertabrename) command only rewrites the initial occurrence of the table name in its [CREATE TABLE](lang_createtable.md) statement and in any associated [CREATE INDEX](lang_createindex.md) and [CREATE TRIGGER](lang_createtrigger.md) statements. Other references to the table are unmodified, including:
- References to the table within the bodies of triggers and views.
- References to the table within CHECK constraints in the original CREATE TABLE statement.
- References to the table within the WHERE clauses of [partial indexes](partialindex.md).
The default setting for this pragma is OFF, which means that all references to the table anywhere in the schema are converted to the new name.
This pragma is provided as a work-around for older programs that contain code that expect the incomplete behavior of [ALTER TABLE RENAME](lang_altertable.md#altertabrename) found in older versions of SQLite. New applications should leave this flag turned off.
For compatibility with older [virtual table](vtab.md) implementations, this flag is turned on temporarily while the [sqlite3_module.xRename](vtab.md#xrename) method is being run. The value of this flag is restored after the [sqlite3_module.xRename](vtab.md#xrename) method finishes.
The legacy alter table behavior can also be toggled on and off using the [SQLITE_DBCONFIG_LEGACY_ALTER_TABLE](c3ref/c_dbconfig_defensive.md#sqlitedbconfiglegacyaltertable) option to the [sqlite3_db_config()](c3ref/db_config.md) interface.
The legacy alter table behavior is a per-connection setting. Turning this features on or off affects all attached database files within the [database connection](c3ref/sqlite3.md). The setting does not persist. Changing this setting in one connection does not affect any other connections. PRAGMA legacy_file_format
------------------------------------------------------------------------
**PRAGMA legacy_file_format;**
This pragma no longer functions. It has become a no-op. The capabilities formerly provided by PRAGMA legacy_file_format are now available using the [SQLITE_DBCONFIG_LEGACY_FILE_FORMAT](c3ref/c_dbconfig_defensive.md#sqlitedbconfiglegacyfileformat) option to the [sqlite3_db_config()](c3ref/db_config.md) C-language interface.
PRAGMA locking_mode
------------------------------------------------------------------------
**PRAGMA** *schema.***locking_mode;\
PRAGMA** *schema.***locking_mode = *NORMAL \| EXCLUSIVE***
This pragma sets or queries the database connection locking-mode. The locking-mode is either NORMAL or EXCLUSIVE.
In NORMAL locking-mode (the default unless overridden at compile-time using [SQLITE_DEFAULT_LOCKING_MODE](compile.md#default_locking_mode)), a database connection unlocks the database file at the conclusion of each read or write transaction. When the locking-mode is set to EXCLUSIVE, the database connection never releases file-locks. The first time the database is read in EXCLUSIVE mode, a shared lock is obtained and held. The first time the database is written, an exclusive lock is obtained and held.
Database locks obtained by a connection in EXCLUSIVE mode may be released either by closing the database connection, or by setting the locking-mode back to NORMAL using this pragma and then accessing the database file (for read or write). Simply setting the locking-mode to NORMAL is not enough - locks are not released until the next time the database file is accessed.
There are three reasons to set the locking-mode to EXCLUSIVE.
1. The application wants to prevent other processes from accessing the database file.
2. The number of system calls for filesystem operations is reduced, possibly resulting in a small performance increase.
3. [WAL](wal.md) databases can be accessed in EXCLUSIVE mode without the use of shared memory. ([Additional information](wal.md#noshm))
When the locking_mode pragma specifies a particular database, for example:
> PRAGMA **main.**locking_mode=EXCLUSIVE;
then the locking mode applies only to the named database. If no database name qualifier precedes the "locking_mode" keyword then the locking mode is applied to all databases, including any new databases added by subsequent [ATTACH](lang_attach.md) commands.
The "temp" database (in which TEMP tables and indices are stored) and [in-memory databases](inmemorydb.md) always uses exclusive locking mode. The locking mode of temp and [in-memory databases](inmemorydb.md) cannot be changed. All other databases use the normal locking mode by default and are affected by this pragma.
If the locking mode is EXCLUSIVE when first entering [WAL journal mode](wal.md), then the locking mode cannot be changed to NORMAL until after exiting WAL journal mode. If the locking mode is NORMAL when first entering WAL journal mode, then the locking mode can be changed between NORMAL and EXCLUSIVE and back again at any time and without needing to exit WAL journal mode.
PRAGMA max_page_count
------------------------------------------------------------------------
**PRAGMA** *schema.***max_page_count;\
PRAGMA** *schema.***max_page_count =** *N***;**
Query or set the maximum number of pages in the database file. Both forms of the pragma return the maximum page count. The second form attempts to modify the maximum page count. The maximum page count cannot be reduced below the current database size.
PRAGMA mmap_size
------------------------------------------------------------------------
\
**PRAGMA** *schema.***mmap_size;\
PRAGMA** *schema.***mmap_size=***N*
Query or change the maximum number of bytes that are set aside for memory-mapped I/O on a single database. The first form (without an argument) queries the current limit. The second form (with a numeric argument) sets the limit for the specified database, or for all databases if the optional database name is omitted. In the second form, if the database name is omitted, the limit that is set becomes the default limit for all databases that are added to the [database connection](c3ref/sqlite3.md) by subsequent [ATTACH](lang_attach.md) statements.
The argument N is the maximum number of bytes of the database file that will be accessed using memory-mapped I/O. If N is zero then memory mapped I/O is disabled. If N is negative, then the limit reverts to the default value determined by the most recent [sqlite3_config](c3ref/config.md)([SQLITE_CONFIG_MMAP_SIZE](c3ref/c_config_covering_index_scan.md#sqliteconfigmmapsize)), or to the compile time default determined by [SQLITE_DEFAULT_MMAP_SIZE](compile.md#default_mmap_size) if no start-time limit has been set.
The [PRAGMA mmap_size](pragma.md#pragma_mmap_size) statement will never increase the amount of address space used for memory-mapped I/O above the hard limit set by the [SQLITE_MAX_MMAP_SIZE](compile.md#max_mmap_size) compile-time option, nor the hard limit set at startup-time by the second argument to sqlite3_config([SQLITE_CONFIG_MMAP_SIZE](c3ref/c_config_covering_index_scan.md#sqliteconfigmmapsize))
The size of the memory-mapped I/O region cannot be changed while the memory-mapped I/O region is in active use, to avoid unmapping memory out from under running SQL statements. For this reason, the mmap_size pragma may be a no-op if the prior mmap_size is non-zero and there are other SQL statements running concurrently on the same [database connection](c3ref/sqlite3.md).
PRAGMA module_list
------------------------------------------------------------------------
**PRAGMA module_list;**
This pragma returns a list of [virtual table](vtab.md) modules registered with the database connection. PRAGMA optimize
------------------------------------------------------------------------
**PRAGMA optimize;\
PRAGMA optimize(***MASK***);\
PRAGMA** *schema***.optimize;\
PRAGMA** *schema***.optimize(***MASK***);**
Attempt to optimize the database. All schemas are optimized in the first two forms, and only the specified schema is optimized in the latter two.
In most applications, using PRAGMA optimize as follows will help SQLite to achieve the best possible query performance:
1. Applications with short-lived database connections should run "PRAGMA optimize;" once, just prior to closing each database connection.
2. Applications that use long-lived database connections should run "PRAGMA optimize=0x10002;" when the connection is first opened, and then also run "PRAGMA optimize;" periodically, perhaps once per day or once per hour.
3. All applications should run "PRAGMA optimize;" after a schema change, especially after one or more [CREATE INDEX](lang_createindex.md) statements.
This pragma is usually a no-op or nearly so and is very fast. On the occasions where it does need to run ANALYZE on one or more tables, it sets a temporary [analysis limit](pragma.md#pragma_analysis_limit), valid for the duration of this pragma only, that prevents the ANALYZE invocations from running for too long.
Recommended practice is that applications with short-lived database connections should run "PRAGMA optimize" once when the database connection closes. Applications with long-lived database connections should run "PRAGMA optimize=0x10002" when the database connection first opens, then run "PRAGMA optimize" again at periodic intervals - perhaps once per day. All applications should run "PRAGMA optimize" after schema changes, especially [CREATE INDEX](lang_createindex.md).
The details of optimizations performed by this pragma are expected to change and improve over time. Applications should anticipate that this pragma will perform new optimizations in future releases.
The optional MASK argument is a bitmask of optimizations to perform:
0x00001
Debugging mode. Do not actually perform any optimizations but instead return one line of text for each optimization that would have been done. Off by default.
0x00002
Run [ANALYZE](lang_analyze.md) on tables that might benefit. On by default.
0x00010
When running [ANALYZE](lang_analyze.md), set a temporary [PRAGMA analysis_limit](pragma.md#pragma_analysis_limit) to prevent excess run-time. On by default.
0x10000
Check the size of all tables, not just tables that have been recently used, to see if any have grown and shrunk significantly and hence might benefit from being re-analyzed. Off by default.
The default MASK is 0xfffe.
To see all optimizations that would have been done without actually doing them, run "PRAGMA optimize(-1)".
**Determination Of When To Run Analyze**
In the current implementation, a table is analyzed if and only if all of the following are true:
1. MASK bit 0x02 is set.
2. The table is an ordinary table, not a view or virtual table.
3. The table name does not begin with "sqlite\_".
4. One or more of the following are true:
1. The 0x10000 bit of MASK is set
2. One or more indexes on the table lack entries in the sqlite_stat1 table.
3. The query planner used sqlite_stat1 statistics for one or more indexes of this table at some point during the lifetime of the current database connection.
5. One or more of the following are true:
1. One or more indexes on the table lack entries in the sqlite_stat1 table.
2. The number of rows in the table has increased or decreased by 10-fold since the last time ANALYZE was run on the table.
The rules for when tables are analyzed are likely to change in future releases. New MASK values may be added in the future. Future versions of this pragma might accept a string literal argument instead of a bit mask, though the bit mask argument will continue to be supported for backwards compatibility. PRAGMA page_count
------------------------------------------------------------------------
**PRAGMA** *schema.***page_count;**
Return the total number of pages in the database file.
PRAGMA page_size
------------------------------------------------------------------------
**PRAGMA** *schema.***page_size;\
PRAGMA** *schema.***page_size =** *bytes***;**
Query or set the page size of the database. The page size must be a power of two between 512 and 65536 inclusive.
When a new database is created, SQLite assigns a page size to the database based on platform and filesystem. For many years, the default page size was almost always 1024 bytes, but beginning with SQLite [version 3.12.0](releaselog/3_12_0.md) (2016-03-29), the default page size increased to 4096. The default page size is recommended for most applications.
Specifying a new page size does not change the page size immediately. Instead, the new page size is remembered and is used to set the page size when the database is first created, if it does not already exist when the page_size pragma is issued, or at the next [VACUUM](lang_vacuum.md) command that is run on the same database connection while not in [WAL mode](wal.md).
The [SQLITE_DEFAULT_PAGE_SIZE](compile.md#default_page_size) compile-time option can be used to change the default page size assigned to new databases. PRAGMA parser_trace
------------------------------------------------------------------------
**PRAGMA parser_trace =** *boolean***;**
If SQLite has been compiled with the [SQLITE_DEBUG](compile.md#debug) compile-time option, then the parser_trace pragma can be used to turn on tracing for the SQL parser used internally by SQLite. This feature is used for debugging SQLite itself.
This pragma is intended for use when debugging SQLite itself. It is only available when the [SQLITE_DEBUG](compile.md#debug) compile-time option is used.
PRAGMA pragma_list
------------------------------------------------------------------------
**PRAGMA pragma_list;**
This pragma returns a list of PRAGMA commands known to the database connection. PRAGMA query_only
------------------------------------------------------------------------
**PRAGMA query_only;\
PRAGMA query_only =** *boolean***;**
The query_only pragma prevents data changes on database files when enabled. When this pragma is enabled, any attempt to CREATE, DELETE, DROP, INSERT, or UPDATE will result in an [SQLITE_READONLY](rescode.md#readonly) error. However, the database is not truly read-only. You can still run a [checkpoint](wal.md#ckpt) or a [COMMIT](lang_transaction.md) and the return value of the [sqlite3_db_readonly()](c3ref/db_readonly.md) routine is not affected.
PRAGMA quick_check
------------------------------------------------------------------------
**PRAGMA** *schema.***quick_check;\
PRAGMA** *schema.***quick_check(***N***)**\
PRAGMA *schema.***quick_check(***TABLENAME***)**
The pragma is like [integrity_check](pragma.md#pragma_integrity_check) except that it does not verify UNIQUE constraints and does not verify that index content matches table content. By skipping UNIQUE and index consistency checks, quick_check is able to run faster. PRAGMA quick_check runs in O(N) time whereas [PRAGMA integrity_check](pragma.md#pragma_integrity_check) requires O(NlogN) time where N is the total number of rows in the database. Otherwise the two pragmas are the same.
PRAGMA read_uncommitted
------------------------------------------------------------------------
**PRAGMA read_uncommitted;\
PRAGMA read_uncommitted =** *boolean***;**
Query, set, or clear READ UNCOMMITTED isolation. The default isolation level for SQLite is SERIALIZABLE. Any process or thread can select READ UNCOMMITTED isolation, but SERIALIZABLE will still be used except between connections that share a common page and schema cache. Cache sharing is enabled using the [sqlite3_enable_shared_cache()](c3ref/enable_shared_cache.md) API. Cache sharing is disabled by default.
See [SQLite Shared-Cache Mode](sharedcache.md) for additional information.
PRAGMA recursive_triggers
------------------------------------------------------------------------
**PRAGMA recursive_triggers;\
PRAGMA recursive_triggers =** *boolean***;**
Query, set, or clear the recursive trigger capability.
Changing the recursive_triggers setting affects the execution of all statements prepared using the database connection, including those prepared before the setting was changed. Any existing statements prepared using the legacy [sqlite3_prepare()](c3ref/prepare.md) interface may fail with an [SQLITE_SCHEMA](rescode.md#schema) error after the recursive_triggers setting is changed.
Prior to SQLite [version 3.6.18](releaselog/3_6_18.md) (2009-09-11), recursive triggers were not supported. The behavior of SQLite was always as if this pragma was set to OFF. Support for recursive triggers was added in version 3.6.18 but was initially turned OFF by default, for compatibility. Recursive triggers may be turned on by default in future versions of SQLite.
The depth of recursion for triggers has a hard upper limit set by the [SQLITE_MAX_TRIGGER_DEPTH](limits.md#max_trigger_depth) compile-time option and a run-time limit set by [sqlite3_limit](c3ref/limit.md)(db,[SQLITE_LIMIT_TRIGGER_DEPTH](c3ref/c_limit_attached.md#sqlitelimittriggerdepth),...).
PRAGMA reverse_unordered_selects
------------------------------------------------------------------------
**PRAGMA reverse_unordered_selects;\
PRAGMA reverse_unordered_selects =** *boolean***;**
When enabled, this PRAGMA causes many [SELECT](lang_select.md) statements without an ORDER BY clause to emit their results in the reverse order from what they normally would. This can help debug applications that are making invalid assumptions about the result order. The reverse_unordered_selects pragma works for most SELECT statements, however the query planner may sometimes choose an algorithm that is not easily reversed, in which case the output will appear in the same order regardless of the reverse_unordered_selects setting.
SQLite makes no guarantees about the order of results if a SELECT omits the ORDER BY clause. Even so, the order of results does not change from one run to the next, and so many applications mistakenly come to depend on the arbitrary output order whatever that order happens to be. However, sometimes new versions of SQLite will contain optimizer enhancements that will cause the output order of queries without ORDER BY clauses to shift. When that happens, applications that depend on a certain output order might malfunction. By running the application multiple times with this pragma both disabled and enabled, cases where the application makes faulty assumptions about output order can be identified and fixed early, reducing problems that might be caused by linking against a different version of SQLite.
PRAGMA schema_version
------------------------------------------------------------------------
**PRAGMA** *schema.***schema_version;\
PRAGMA** *schema.***schema_version =** *integer* ;
The schema_version pragma will get or set the value of the schema-version integer at offset 40 in the [database header](fileformat2.md#database_header).
SQLite automatically increments the schema-version whenever the schema changes. As each SQL statement runs, the schema version is checked to ensure that the schema has not changed since the SQL statement was [prepared](c3ref/prepare.md). Subverting this mechanism by using "PRAGMA schema_version=N" to change the value of the schema_version may cause SQL statement to run using an obsolete schema, which can lead to incorrect answers and/or [database corruption](howtocorrupt.md#cfgerr). It is always safe to read the schema_version, but changing the schema_version can cause problems. For this reason, attempts to change the value of schema_version are a silent no-op when [defensive mode](c3ref/c_dbconfig_defensive.md#sqlitedbconfigdefensive) is enabled for a database connection.
**Warning:** Misuse of this pragma can result in [database corruption](howtocorrupt.md#cfgerr).
For the purposes of this pragma, the [VACUUM](lang_vacuum.md) command is considered a schema change, since [VACUUM](lang_vacuum.md) will usually alter the "rootpage" values for entries in the [sqlite_schema table](schematab.md).
See also the [application_id pragma](pragma.md#pragma_application_id) and [user_version pragma](pragma.md#pragma_user_version). PRAGMA secure_delete
------------------------------------------------------------------------
**PRAGMA** *schema.***secure_delete;\
PRAGMA** *schema.***secure_delete =** *boolean*\|**FAST**
Query or change the secure-delete setting. When secure_delete is on, SQLite overwrites deleted content with zeros. The default setting for secure_delete is determined by the [SQLITE_SECURE_DELETE](compile.md#secure_delete) compile-time option and is normally off. The off setting for secure_delete improves performance by reducing the number of CPU cycles and the amount of disk I/O. Applications that wish to avoid leaving forensic traces after content is deleted or updated should enable the secure_delete pragma prior to performing the delete or update, or else run [VACUUM](lang_vacuum.md) after the delete or update.
The "fast" setting for secure_delete (added circa 2017-08-01) is an intermediate setting in between "on" and "off". When secure_delete is set to "fast", SQLite will overwrite deleted content with zeros only if doing so does not increase the amount of I/O. In other words, the "fast" setting uses more CPU cycles but does not use more I/O. This has the effect of purging all old content from [b-tree pages](fileformat2.md#btree), but leaving forensic traces on [freelist pages](fileformat2.md#freelist).
When there are [attached databases](lang_attach.md) and no database is specified in the pragma, all databases have their secure-delete setting altered. The secure-delete setting for newly attached databases is the setting of the main database at the time the ATTACH command is evaluated.
When multiple database connections share the same cache, changing the secure-delete flag on one database connection changes it for them all.
**Limitation:** The secure_delete pragma only causes deleted content to be scrubbed from ordinary tables. If [virtual tables](vtab.md) store content in [shadow tables](vtab.md#xshadowname), then deleting content from the virtual table does not necessarily remove forensic traces from the shadow tables. In particular, the [FTS3](fts3.md) and [FTS5](fts5.md) virtual tables that come bundled with SQLite might leave forensic traces in their shadow tables even if the secure_delete pragma is enabled.
PRAGMA short_column_names
------------------------------------------------------------------------
**PRAGMA short_column_names;\
PRAGMA short_column_names =** *boolean***;**
Query or change the short-column-names flag. This flag affects the way SQLite names columns of data returned by [SELECT](lang_select.md) statements. See the [full_column_names](pragma.md#pragma_full_column_names) pragma for full details.
**This pragma is deprecated** and exists for backwards compatibility only. New applications should avoid using this pragma. Older applications should discontinue use of this pragma at the earliest opportunity. This pragma may be omitted from the build when SQLite is compiled using [SQLITE_OMIT_DEPRECATED](compile.md#omit_deprecated).
PRAGMA shrink_memory
------------------------------------------------------------------------
**PRAGMA shrink_memory**
This pragma causes the database connection on which it is invoked to free up as much memory as it can, by calling [sqlite3_db_release_memory()](c3ref/db_release_memory.md).
PRAGMA soft_heap_limit
------------------------------------------------------------------------
**PRAGMA soft_heap_limit\
PRAGMA soft_heap_limit=***N*
This pragma invokes the [sqlite3_soft_heap_limit64()](c3ref/hard_heap_limit64.md) interface with the argument N, if N is specified and is a non-negative integer. The soft_heap_limit pragma always returns the same integer that would be returned by the [sqlite3_soft_heap_limit64](c3ref/hard_heap_limit64.md)(-1) C-language function.
See also the [hard_heap_limit pragma](pragma.md#pragma_hard_heap_limit). PRAGMA stats
------------------------------------------------------------------------
**PRAGMA stats;**
This pragma returns auxiliary information about tables and indices. The returned information is used during testing to help verify that the query planner is operating correctly. The format and meaning of this pragma will likely change from one release to the next. Because of its volatility, the behavior and output format of this pragma are deliberately undocumented.
The intended use of this pragma is only for testing and validation of SQLite. This pragma is subject to change without notice and is not recommended for use by application programs.
PRAGMA synchronous
------------------------------------------------------------------------
**PRAGMA** *schema.***synchronous;\
PRAGMA** *schema.***synchronous =** *0 \| OFF \| 1 \| NORMAL \| 2 \| FULL \| 3 \| EXTRA***;**
Query or change the setting of the "synchronous" flag. The first (query) form will return the synchronous setting as an integer. The second form changes the synchronous setting. The meanings of the various synchronous settings are as follows:
**EXTRA** (3)
EXTRA synchronous is like FULL with the addition that the directory containing a [rollback journal](lockingv3.md#rollback) is synced after that journal is unlinked to commit a transaction in DELETE mode. EXTRA provides additional durability if the commit is followed closely by a power loss. Without EXTRA, depending on the underlying filesystem, it is possible that a single transaction that commits right before a power loss might get rolled back upon reboot. The database will not go corrupt. But the last transaction might go missing, thus violating durability, if EXTRA is not set.
EXTRA is no different from FULL in [WAL mode](wal.md).
**FULL** (2)
When synchronous is FULL (2), the SQLite database engine will use the xSync method of the [VFS](vfs.md) to ensure that all content is safely written to the disk surface prior to continuing. This ensures that an operating system crash or power failure will not corrupt the database.
FULL is the default synchronous mode for a [rollback journal](lockingv3.md#rollback). FULL is atomic, consistent, isolated, and durable (ACID) in [WAL mode](wal.md) and is atomic, consistent, and isolated with a [rollback journal](lockingv3.md#rollback). FULL might also be durable using a rollback journal, depending on the underlying filesystem. FULL is not necessarily durable across a power loss in rollback mode, so if durability is desired, it is best to set the synchronous mode to EXTRA.
**NORMAL** (1)
When synchronous is NORMAL (1), the SQLite database engine will still sync at the most critical moments, but less often than in FULL mode. There is a very small (though non-zero) chance that a power failure at just the wrong time could corrupt the database in [journal_mode](pragma.md#pragma_journal_mode)=DELETE on an older filesystem. [WAL mode](wal.md) is safe from corruption with synchronous=NORMAL, and probably DELETE mode is safe too on modern filesystems. WAL mode is always consistent with synchronous=NORMAL, but WAL mode does lose durability. A transaction committed in WAL mode with synchronous=NORMAL might roll back following a power loss or system crash. Transactions are durable across application crashes regardless of the synchronous setting or journal mode.
The synchronous=NORMAL setting provides the best balance between performance and safety for most applications running in [WAL mode](wal.md). You lose durability across power lose with synchronous NORMAL in WAL mode, but that is not important for most applications. Transactions are still atomic, consistent, and isolated, which are the most important characteristics in most use cases.
**OFF** (0)
With synchronous OFF (0), SQLite continues without syncing as soon as it has handed data off to the operating system. If the application running SQLite crashes, the data will be safe, but the database [might become corrupted](howtocorrupt.md#cfgerr) if the operating system crashes or the computer loses power before that data has been written to non-volatile storage. On the other hand, commits can be much faster with synchronous OFF.
Setting synchronous to OFF is a good option when creating a new database from scratch, in a scenario where the process of creating the database can be repeated if a power loss occurs in the middle, and when performance is critical.
Here is the matrix:
Rollback Mode
WAL Mode
EXTRA
ACID
ACID
FULL
Maybe not durable
ACID
NORMAL
Maybe not consistent
Maybe not durable
OFF
Not consistent
Not consistent
In [WAL](wal.md) mode when synchronous is NORMAL (1), the WAL file is synchronized before each [checkpoint](wal.md#ckpt) and the database file is synchronized after each completed [checkpoint](wal.md#ckpt) and the WAL file header is synchronized when a WAL file begins to be reused after a checkpoint, but no sync operations occur during most transactions. With synchronous=FULL in WAL mode, an additional sync operation of the WAL file happens after each transaction commit. The extra WAL sync following each transaction helps ensure that transactions are durable across a power loss. Transactions are consistent with or without the extra syncs provided by synchronous=FULL. If durability is not a concern, then synchronous=NORMAL is normally all one needs in WAL mode.
The TEMP schema always has synchronous=OFF since the content of of TEMP is ephemeral and is not expected to survive a power outage. Attempts to change the synchronous setting for TEMP are silently ignored.
See also the [fullfsync](pragma.md#pragma_fullfsync) and [checkpoint_fullfsync](pragma.md#pragma_checkpoint_fullfsync) pragmas.
PRAGMA table_info
------------------------------------------------------------------------
**PRAGMA** *schema.***table_info(***table-name***);**
This pragma returns one row for each normal column in the named table. Columns in the result set include: "name" (its name); "type" (data type if given, else ''); "notnull" (whether or not the column can be NULL); "dflt_value" (the default value for the column); and "pk" (either zero for columns that are not part of the primary key, or the 1-based index of the column within the primary key).
The "cid" column should not be taken to mean more than "rank within the current result set".
The table named in the table_info pragma can also be a view.
This pragma does not show information about [generated columns](gencol.md) or [hidden columns](vtab.md#hiddencol). Use [PRAGMA table_xinfo](pragma.md#pragma_table_xinfo) to get a more complete list of columns that includes generated and hidden columns. PRAGMA table_list
------------------------------------------------------------------------
**PRAGMA table_list;\
PRAGMA** *schema.***table_list;\
PRAGMA table_list(***table-name***);**
This pragma returns information about the tables and views in the schema, one table per row of output. The table_list pragma first appeared in SQLite version 3.37.0 (2021-11-27). As of its initial release the columns returned by the table_list pragma include those listed below. Future versions of SQLite will probably add additional columns of output.
1. **schema**: the schema in which the table or view appears (for example "main" or "temp").
2. **name**: the name of the table or view.
3. **type**: the type of object - one of "table", "view", "shadow" (for [shadow tables](vtab.md#xshadowname)), or "virtual" for [virtual tables](vtab.md).
4. **ncol**: the number of columns in the table, including [generated columns](gencol.md) and [hidden columns](vtab.md#hiddencol).
5. **wr**: 1 if the table is a [WITHOUT ROWID](withoutrowid.md) table or 0 if is not.
6. **strict**: 1 if the table is a [STRICT table](stricttables.md) or 0 if it is not.
7. *Additional columns will likely be added in future releases.*
The default behavior is to show all tables in all schemas. If the *schema.* name appears before the pragma, then only tables in that one schema are shown. If a *table-name* argument is supplied, then only information about that one table is returned. PRAGMA table_xinfo
------------------------------------------------------------------------
**PRAGMA** *schema.***table_xinfo(***table-name***);**
This pragma returns one row for each column in the named table, including [generated columns](gencol.md) and [hidden columns](vtab.md#hiddencol). The output has the same columns as for [PRAGMA table_info](pragma.md#pragma_table_info) plus a column, "hidden", whose value signifies a normal column (0), a dynamic or stored generated column (2 or 3), or a hidden column in a virtual table (1). The rows for which this field is non-zero are those omitted for [PRAGMA table_info](pragma.md#pragma_table_info). PRAGMA temp_store
------------------------------------------------------------------------
**PRAGMA temp_store;\
PRAGMA temp_store =** *0 \| DEFAULT \| 1 \| FILE \| 2 \| MEMORY***;**
Query or change the setting of the "**temp_store**" parameter. When temp_store is DEFAULT (0), the compile-time C preprocessor macro [SQLITE_TEMP_STORE](compile.md#temp_store) is used to determine where temporary tables and indices are stored. When temp_store is MEMORY (2) [temporary tables](inmemorydb.md#temp_db) and indices are kept as if they were in pure [in-memory databases](inmemorydb.md). When temp_store is FILE (1) [temporary tables](inmemorydb.md#temp_db) and indices are stored in a file. The [temp_store_directory](pragma.md#pragma_temp_store_directory) pragma can be used to specify the directory containing temporary files when **FILE** is specified. When the temp_store setting is changed, all existing temporary tables, indices, triggers, and views are immediately deleted.
It is possible for the library compile-time C preprocessor symbol [SQLITE_TEMP_STORE](compile.md#temp_store) to override this pragma setting. The following table summarizes the interaction of the [SQLITE_TEMP_STORE](compile.md#temp_store) preprocessor macro and the temp_store pragma:
> | SQLITE_TEMP_STORE | >PRAGMA > temp_store |
> Storage used for > TEMP tables and indices |
>
|---|---|---|
| 0 | >any | >file | >
| 1 | >0 | >file | >
| 1 | >1 | >file | >
| 1 | >2 | >memory | >
| 2 | >0 | >memory | >
| 2 | >1 | >file | >
| 2 | >2 | >memory | >
| 3 | >any | >memory | >
| Character | Values | Description |
|---|---|---|
| p | 1 | The number of matchable phrases in the query. |
| c | 1 | The number of user defined columns in the FTS table (i.e. not including the docid or the FTS hidden column). |
| x | 3 * cols * phrases | For each distinct combination of a phrase and table column, the following three values:
hits_this_row = array[3 * (c + p*cols) + 0] hits_all_rows = array[3 * (c + p*cols) + 1] docs_with_hits = array[3 * (c + p*cols) + 2] |
| y | cols * phrases | For each distinct combination of a phrase and table column, the number of usable phrase matches that appear in the column. This is usually identical to the first value in each set of three returned by the matchinfo 'x' flag. However, the number of hits reported by the 'y' flag is zero for any phrase that is part of a sub-expression that does not match the current row. This makes a difference for expressions that contain AND operators that are descendants of OR operators. For example, consider the expression:
a OR (b AND c) and the document: "a c d" The matchinfo 'x' flag would report a single hit for the phrases "a" and "c". However, the 'y' directive reports the number of hits for "c" as zero, as it is part of a sub-expression that does not match the document - (b AND c). For queries that do not contain AND operators descended from OR operators, the result values returned by 'y' are always the same as those returned by 'x'. The first value in the array of integer values corresponds to the leftmost column of the table (column 0) and the first phrase in the query (phrase 0). The values corresponding to other column/phrase combinations may be located using the following formula: hits_for_phrase_p_column_c = array[c + p*cols] For queries that use OR expressions, or those that use LIMIT or return many rows, the 'y' matchinfo option may be faster than 'x'. |
| b | ((cols+31)/32) * phrases | The matchinfo 'b' flag provides similar information to the matchinfo 'y' flag, but in a more compact form. Instead of the precise number of hits, 'b' provides a single boolean flag for each phrase/column combination. If the phrase is present in the column at least once (i.e. if the corresponding integer output of 'y' would be non-zero), the corresponding flag is set. Otherwise cleared.
If the table has 32 or fewer columns, a single unsigned integer is output for each phrase in the query. The least significant bit of the integer is set if the phrase appears at least once in column 0. The second least significant bit is set if the phrase appears once or more in column 1. And so on. If the table has more than 32 columns, an extra integer is added to the output of each phrase for each extra 32 columns or part thereof. Integers corresponding to the same phrase are clumped together. For example, if a table with 45 columns is queried for two phrases, 4 integers are output. The first corresponds to phrase 0 and columns 0-31 of the table. The second integer contains data for phrase 0 and columns 32-44, and so on. For example, if nCol is the number of columns in the table, to determine if phrase p is present in column c: p_is_in_c = array[p * ((nCol+31)/32)] & (1 << (c % 32)) |
| n | 1 | The number of rows in the FTS4 table. This value is only available when querying FTS4 tables, not FTS3. |
| a | cols | For each column, the average number of tokens in the text values stored in the column (considering all rows in the FTS4 table). This value is only available when querying FTS4 tables, not FTS3. |
| l | cols | For each column, the length of the value stored in the current row of the FTS4 table, in tokens. This value is only available when querying FTS4 tables, not FTS3. And only if the "matchinfo=fts3" directive was not specified as part of the "CREATE VIRTUAL TABLE" statement used to create the FTS4 table. |
| s | cols | For each column, the length of the longest subsequence of phrase matches that the column value has in common with the query text. For example, if a table column contains the text 'a b c d e' and the query is 'a c "d e"', then the length of the longest common subsequence is 2 (phrase "c" followed by phrase "d e"). |
| Column Name | Column Contents |
|---|---|
| term | Contains the text of the term for this row. |
| col | This column may contain either the text value '*' (i.e. a single character, U+002a) or an integer between 0 and N-1, where N is again the number of user-defined columns in the corresponding FTS table. |
| documents | This column always contains an integer value greater than zero. If the "col" column contains the value '*', then this column contains the number of rows of the FTS table that contain at least one instance of the term (in any column). If col contains an integer value, then this column contains the number of rows of the FTS table that contain at least one instance of the term in the column identified by the col value. As usual, the columns of the FTS table are numbered from left to right, starting with zero. |
| occurrences | This column also always contains an integer value greater than zero. If the "col" column contains the value '*', then this column contains the total number of instances of the term in all rows of the FTS table (in any column). Otherwise, if col contains an integer value, then this column contains the total number of instances of the term that appear in the FTS table column identified by the col value. |
| languageid (hidden) | This column determines which languageid is used to extract vocabulary from the FTS3/4 table. The default value for languageid is 0. If an alternative language is specified in WHERE clause constraints, then that alternative is used instead of 0. There can only be a single languageid per query. In other words, the WHERE clause cannot contain a range constraint or IN operator on the languageid. |
| Column | Interpretation |
|---|---|
| level | Between them, the contents of the "level" and "idx" fields define the relative age of the segment b-tree. The smaller the value stored in the "level" field, the more recently the segment b-tree was created. If two segment b-trees are of the same "level", the segment with the larger value stored in the "idx" column is more recent. The PRIMARY KEY constraint on the %_segdir table prevents any two segments from having the same value for both the "level" and "idx" fields. |
| idx | See above. |
| start_block | The blockid that corresponds to the node with the smallest blockid that belongs to this segment b-tree. Or zero if the entire segment b-tree fits on the root node. If it exists, this node is always a leaf node. |
| leaves_end_block | The blockid that corresponds to the leaf node with the largest blockid that belongs to this segment b-tree. Or zero if the entire segment b-tree fits on the root node. |
| end_block | This field may contain either an integer or a text field consisting of two integers separated by a space character (unicode codepoint 0x20).
The first, or only, integer is the blockid that corresponds to the interior node with the largest blockid that belongs to this segment b-tree. Or zero if the entire segment b-tree fits on the root node. If it exists, this node is always an interior node. The second integer, if it is present, is the aggregate size of all data stored on leaf pages in bytes. If the value is negative, then the segment is the output of an unfinished incremental-merge operation, and the absolute value is current size in bytes. |
| root | Blob containing the root node of the segment b-tree. |