Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

SQLite Database Integration · Version history

SQLite Database Integration changelog and version history

Latest version
3.1.3
Nov 3, 2026 (5 days ago)
Releases
35
since 2024
In the last year
16
about one every 23 days
Tested up to
WordPress 7.1.4
PHP 7.2 or later

Releases each year

  • 20243 releases
  • 202517 releases
  • 202615 releases

202615 releases

  1. SQLite Database Integration 3.1.3Latest

    • Fix BINARY and VARBINARY column defaults (#596)
    • Quote SQLite identifiers in LOCK TABLES, SHOW TABLES, and compound primary key indexes (#599)
    • Name lexer tokens after the MySQL grammar and default to MySQL 8.4.10 (#607)
    • Fix MySQL lexer correctness issues (#584)
    • Require MySQL proxy authentication and default to loopback (#540)
    • Speed up PHPUnit and avoid E2E setup timeouts (#579)
    • Fix reserved prefix checks for case variants and foreign keys (#580)

  2. SQLite Database Integration 3.1.2

    • Allow configuring the SQLite busy timeout with SQLITE_BUSY_TIMEOUT (#558)
    • Keep the user transaction active after a failed statement (#536)
    • Support odd-length 0x hexadecimal literals (#573)
    • Fix rebuilds of legacy text and binary columns (#565)
    • Use '0' column defaults in non-strict INSERT statements (#569)
    • Roll back failed OPTIMIZE TABLE and REPAIR TABLE rebuilds (#567)
    • Remove the Rust parser extension (#566)
    • Preserve AUTO_INCREMENT counters when rebuilding tables (#561)
    • Fix ALTER TABLE ... ADD (...) for columns, indexes, and constraints (#557)
    • Fix ON UPDATE CURRENT_TIMESTAMP for explicit values and unchanged rows (#560)
    • Normalize zero defaults in date and time columns (#542)
    • Add support for ALTER COLUMN with SET DEFAULT and DROP DEFAULT (#555)

  3. SQLite Database Integration 3.1.1

    • Support date arithmetic with INTERVAL operators (#539)
    • Fix ROLLBACK as the first transaction of a connection (#537)
    • Fix matching a foreign key reference to a unique key with a different case (#534)
    • Fix FOUND_ROWS() without SQL_CALC_FOUND_ROWS (#533)
    • Fix unique keys and foreign key restore without stringified fetches (#532)
    • Fix CREATE TEMPORARY TABLE IF NOT EXISTS and DROP TEMPORARY TABLE as the first temporary table (#524)
    • Fix a warning for a foreign key referencing a table with a shorter unique key (#523)
    • Fix temporary table lookup without stringified fetches and with a different case (#522)

  4. SQLite Database Integration 3.1.0

    • SQLite Database Integration 3.1 is here! 🎉
    • This release improves database storage and configuration and fixes several MySQL compatibility issues.
    • What’s new
    • Version 3.1 improves how WordPress sites store, locate, and protect their SQLite databases. It also fixes SQL behavior and export compatibility:
    • Randomized database paths: The default database location is now a randomized directory under wp-content/database/, recorded in wp-content/database/db-path.php. (#502)
    • DB_PATH: Configure the database with one full-path constant, also available at runtime for integrations. (#512)
    • SQL compatibility: Fix IF() condition evaluation and make TRADITIONAL enable its component SQL modes. (#518, #509)
    • WordPress table collations: Default to utf8mb4_unicode_520_ci for new tables created with WordPress’s charset settings, improving exports to MariaDB. Existing tables keep their recorded collation. (#514)
    • Documentation: A new plugin README and expanded FAQ explain database storage and secure configuration. (#520)
    • For more information about database paths and secure configuration, read the database storage guide.
    • Upgrading to 3.1
    • Upgrading an existing SQLite site is straightforward:
    • Back up your SQLite database.
    • Update the plugin to version 3.1.
    • Existing .ht.sqlite and .ht.sqlite.php databases move to the randomized layout automatically unless a database file path is explicitly configured.
    • To properly secure the database, set DB_PATH in wp-config.php to an absolute file path outside the web root that your web server does not expose. Its directory must be writable by PHP. Changing DB_PATH does not move an existing database.
    • Breaking changes
    • Review these changes if you use custom database settings or integrations:
    • Database paths: Default database files now move to randomized paths under wp-content/database/. Explicitly configured file paths stay unchanged. Integrations, including backup and migration tools, must read DB_PATH after WordPress loads instead of assuming a fixed filename.
    • Legacy constants: DB_DIR and DB_FILE are now deprecated. They and the previously deprecated FQDB and FQDBDIR remain supported, but DB_PATH takes precedence. Conflicting values trigger warnings.
    • Absolute paths: Relative database file and directory paths are now rejected. :memory: remains available for in-memory databases.
    • Thank you
    • Thank you to everyone who contributed, tested, and helped update integrations.
    • Changes since 3.0.2: v3.0.2...v3.1.0

  5. SQLite Database Integration 3.0.2

    • Fix schema reconstruction with native numeric results (#506)
    • Fix lexer edge cases and string handling (#505)
    • Preserve index prefix lengths and order in SHOW CREATE TABLE primary keys (#500)
    • Align savepoint handling with MySQL semantics (#496)

  6. SQLite Database Integration 3.0.1

    • Mark the plugin as compatible with WordPress 7.1 (#497)
    • Fix fresh multisite database setup (#492)

  7. SQLite Database Integration 3.0.0

    • SQLite Database Integration 3 is here! 🎉
    • This release introduces an all-new SQLite database driver for WordPress, rebuilt from the ground up. Its purpose-built MySQL lexer, parser, and emulation layer deliver broader compatibility, more accurate behavior, and a stronger foundation for future improvements.
    • The 3.0 release spans nearly two years of work, featuring 160 pull requests and 1,075 commits from 15 contributors.
    • What’s new
    • The new driver advances SQLite support for WordPress, plugins, database tools, and other MySQL-based applications. These improvements include:
    • New SQL engine: The pure-PHP lexer and parser provide extensive coverage of the official MySQL grammar.
    • Broad query support: Complex joins, subqueries, CTEs, unions, and other advanced queries are now supported.
    • Schema emulation: WordPress and database tools can query emulated MySQL INFORMATION_SCHEMA tables.
    • Schema introspection: SHOW and DESCRIBE statements provide accurate MySQL-like metadata.
    • Improved data handling: Types, casts, defaults, auto-increment, values, and escaping better match MySQL.
    • Refined MySQL semantics: Better emulation of SQL modes, variables, functions, transactions, and errors.
    • Better concurrency: Write-ahead logging and fewer locks reduce blocking between readers and writers.
    • PDO API: The new driver implements the PDO MySQL API, supporting many MySQL-based tools and applications.
    • Extensive testing: Test suites cover parsing, translation, metadata, concurrency, PDO, and end-to-end workflows.
    • For more information about the new driver and its architecture, read the driver announcement.
    • Modular design
    • The project was redesigned as a set of focused packages, separating the core driver from its WordPress integration:
    • SQLite Database Integration: The WordPress plugin powered by MySQL on SQLite.
    • MySQL on SQLite: A standalone PDO MySQL drop-in for running MySQL-based PHP applications on SQLite.
    • MySQL proxy (experimental): A MySQL wire protocol bridge to PDO-compatible drivers for clients outside PHP.
    • This architecture opens the driver to new integrations, applications, and development tools beyond WordPress.
    • Upgrading to 3.0
    • Upgrading an existing SQLite site is straightforward:
    • Back up your SQLite database.
    • Update the plugin to version 3.0.
    • On first connection, the new driver automatically initializes its metadata without changing your tables or content.
    • If you used the new driver preview, you can now delete the WP_SQLITE_AST_DRIVER flag.
    • Breaking changes
    • Most WordPress sites need no changes. Review the following if you use a custom setup:
    • New driver:

  8. SQLite Database Integration 2.2.23

    • Add Query Monitor 4.0 support (#357)
    • Translate MySQL CONVERT() expressions to SQLite (#356)

  9. SQLite Database Integration 2.2.22

    • Support INSERT without INTO keyword (#354)
    • Add tests for MySQL row-level locking clauses (#342)
    • Improve automated deploy setup.

  10. SQLite Database Integration 2.2.21

    • Monorepo setup + release automation (#334)
    • Rework release workflow (#350)
    • Fix incorrect PHP polyfill implementations (#338)

  11. SQLite Database Integration 2.2.20

  12. SQLite Database Integration 2.2.19

  13. SQLite Database Integration 2.2.18

  14. SQLite Database Integration 2.2.17

  15. SQLite Database Integration 2.2.16

202517 releases

  1. SQLite Database Integration 2.2.15

  2. SQLite Database Integration 2.2.14

  3. SQLite Database Integration 2.2.13

  4. SQLite Database Integration 2.2.12

  5. SQLite Database Integration 2.2.11

  6. SQLite Database Integration 2.2.10

  7. SQLite Database Integration 2.2.9

  8. SQLite Database Integration 2.2.8

  9. SQLite Database Integration 2.2.7

  10. SQLite Database Integration 2.2.6

  11. SQLite Database Integration 2.2.5

  12. SQLite Database Integration 2.2.4

  13. SQLite Database Integration 2.2.3

  14. SQLite Database Integration 2.2.2

  15. SQLite Database Integration 2.2.1

  16. SQLite Database Integration 2.2.0

  17. SQLite Database Integration 2.1.16

20243 releases

  1. SQLite Database Integration 2.1.15

  2. SQLite Database Integration 2.1.14

  3. SQLite Database Integration 2.1.13

Questions about SQLite Database Integration’s releases

What is the latest version of SQLite Database Integration?

3.1.3, released on Nov 3, 2026 (5 days ago). It’s tested up to WordPress 7.1.4 and needs PHP 7.2 or later.

How often is SQLite Database Integration updated?

16 releases in the last year, about one every 23 days. Its first release on WordPress.org dates from August 2024.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in SQLite Database Integration’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.