RequirementsMicrosoft Windows XP64 / Vista64 / Windows 7 64 / Windows 8 64 / Windows 10 64
Date addedFeb 08, 2019
SQLite 32-bit is an in-process library that actualizes an independent, serverless, zero-arrangement, value-based SQL database motor. The code for SQLite is in general society space and is subsequently free for use for any reason, business or private. Download SQLite Offline Installer Setup 32bit for Windows PC! SQLite 32-bit is the most generally conveyed database on the planet with a larger number of utilizations than we can tally, including a few prominent ventures.
- Exchanges are nuclear, reliable, secluded, and strong (ACID) even after framework crashes and power disappointments.
- Zero-design - no setup or organization required.
- Full SQL usage with cutting edge highlights like fractional lists and normal table articulations. (Overlooked highlights)
- A total database is put away in a solitary cross-stage plate record. Awesome for use as an application document organize.
- Backings terabyte-sized databases and gigabyte-sized strings and blobs. (See limits.html.)
- Little code impression: under 500KiB completely designed or significantly less with discretionary highlights precluded.
- Basic, simple to utilize API.
- Written in ANSI-C. TCL ties included. Ties for many different dialects accessible independently.
- Very much remarked source code with 100% branch test inclusion.
- Accessible as a solitary ANSI-C source-code document that is anything but difficult to incorporate and henceforth is anything but difficult to include into a bigger venture.
- Independent: no outside conditions.
- Cross-stage: Android, *BSD, iOS, Linux, Mac, Solaris, VxWorks, and Windows (Win32, WinCE, WinRT) are upheld out of the container. Simple to port to different frameworks.
- Sources are in the general population space. Use for any reason.
- Accompanies an independent summon line interface (CLI) customer that can be utilized to control SQLite databases.
- Added the VACUUM INTO command
- Issue an SQLITE_WARNING message on the error log if a double-quoted string literal is used.
- The sqlite3_normalized_sql() interface works on any prepared statement created using sqlite3_prepare_v2() or sqlite3_prepare_v3(). It is no longer necessary to use sqlite3_prepare_v3() with SQLITE_PREPARE_NORMALIZE in order to use sqlite3_normalized_sql()
- Added the remove_diacritics=2 option to FTS3 and FTS5
- Added the SQLITE_PREPARE_NO_VTAB option to sqlite3_prepare_v3(). Use that option to prevent circular references to shadow tables from causing resource leaks
Enhancements to the sqlite3_deserialize() interface:
- Add the SQLITE_FCNTL_SIZE_LIMIT file-control 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(SQLITE_CONFIG_MEMDB_MAXSIZE) and/or SQLITE_MEMDB_DEFAULT_MAXSIZE.
- Honor the SQLITE_DESERIALIZE_READONLY flag, which was previously described in the documentation, but was previously a no-op
- Enhance the "deserialize" command of the TCL Interface to give it new "--maxsize N" and "--readonly BOOLEAN" options
Enhancements to the CLI, mostly to support testing and debugging of the SQLite library itself:
- Add support for ".open --hexdb". The "dbtotxt" utility program used to generate the text for the "hexdb" is added to the source tree
- Add support for the "--maxsize N" option on ".open --deserialize"
- Add the "--memtrace" command-line option, to show all memory allocations and deallocations
- Add the ".eqp trace" option on builds with SQLITE_DEBUG, to enable bytecode program listing with indentation and PRAGMA vdbe_trace all in one step
- Add the ".progress" command for accessing the sqlite3_progress_handler() interface
- Add the "--async" option to the ".backup" command
- Add options "--expanded", "--normalized", "--plain", "--profile", "--row", "--stmt", and "--close" to the ".trace" command
- Omit deprecated PRAGMA statements when compiling with SQLITE_OMIT_DEPRECATED
- Increased robustness against malicious SQL that is run against a maliciously corrupted database
- Do not use a partial index to do a table scan on an IN operator
- Fix the query flattener so that it works on queries that contain subqueries that use window functions
- Ensure that ALTER TABLE modifies table and column names embedded in WITH clauses that are part of views and triggers
- Fix a parser bug that prevented the use of parentheses around table-valued functions
- Fix a problem with the OR optimization on indexes on expressions
- Fix a problem with the LEFT JOIN strength reduction optimization in which the optimization was being applied inappropriately due to an IS NOT NULL operator
- Fix the REPLACE 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
- Fix a problem with the use of window functions used within correlated subqueries
- Fix the ALTER TABLE RENAME COLUMN command so that it works for tables that have redundant UNIQUE constraints
- Fix a bug that caused zeroblob values to be truncated when inserted into a table that uses an expression index