Major release with an all-new SQLite driver. Requires SQLite 3.37.0 or newer. Back up your SQLite database before updating.<\/p>"},"ratings":{"1":1,"2":0,"3":0,"4":1,"5":10},"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["2.1.13","2.1.14","2.1.15","2.1.16","2.2.0","2.2.1","2.2.10","2.2.11","2.2.12","2.2.13","2.2.14","2.2.15","2.2.16","2.2.17","2.2.18","2.2.19","2.2.2","2.2.20","2.2.21","2.2.22","2.2.23","2.2.3","2.2.4","2.2.5","2.2.6","2.2.7","2.2.8","2.2.9","3.0.0","3.0.1","3.0.2","3.1.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[153,28201],"plugin_category":[54,59],"plugin_contributors":[78740,226274,182429,236628,77594,236629,221146],"plugin_business_model":[],"class_list":["post-168657","plugin","type-plugin","status-publish","hentry","plugin_tags-database","plugin_tags-sqlite","plugin_category-security-and-spam-protection","plugin_category-utilities-and-tools","plugin_contributors-aristath","plugin_contributors-berislavgrgicak","plugin_contributors-bpayton","plugin_contributors-janjakes","plugin_contributors-wordpressdotorg","plugin_contributors-zaerl","plugin_contributors-zieladam","plugin_committers-aristath","plugin_committers-berislavgrgicak","plugin_committers-bpayton","plugin_committers-githubsync","plugin_committers-janjakes","plugin_committers-wordpressdotorg","plugin_committers-zaerl","plugin_committers-zieladam"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/sqlite-database-integration.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
Run WordPress on SQLite.<\/strong><\/p>\n\n The SQLite plugin is a community, feature plugin. The intent is to allow testing an SQLite integration with WordPress and gather feedback, with the goal of eventually landing it in WordPress core.<\/p>\n\n The plugin replaces the default MySQL database layer with an SQLite-backed implementation. WordPress continues to use its standard Important:<\/strong> Enabling SQLite creates a separate, empty database; it does not migrate an existing site. If you enable it on a site that uses MySQL or MariaDB, WordPress will ask you to set up the site again. Disabling the plugin reconnects WordPress to the previous database with its data unchanged. Changes made while using SQLite are not transferred.<\/p>\n\n The plugin requires the PDO SQLite PHP extension and SQLite 3.37.0 or newer.<\/p>\n\n\n The primary purpose of the plugin is to test WordPress with SQLite and gather feedback, with the goal of eventually including the integration in WordPress core.<\/p>\n\n Read the original proposal on the Make WordPress Core blog<\/a> and the call for testing<\/a> for more context.<\/p><\/dd>\n Yes, but keep reliable backups and make sure SQLite is a good fit for your site's traffic. SQLite supports concurrent reads but allows only one writer at a time, so MySQL or MariaDB may be a better fit for sites with heavy concurrent write traffic. Test your workload, themes, and plugins before switching.<\/p><\/dd>\n No. Enabling SQLite starts a fresh WordPress installation in a separate database. Your existing MySQL or MariaDB database remains unchanged, but its content is not copied to SQLite.<\/p>\n\n Disabling the plugin reconnects WordPress to the previous database. Content created while using SQLite is not transferred back.<\/p><\/dd>\n By default, the SQLite database is stored in a randomized path<\/strong> under For example:<\/p>\n\n The random path makes the database location difficult to guess when it is not otherwise protected. We recommend setting Integrations should always read To properly secure the SQLite database<\/strong>, define the Caution:<\/strong> An explicit The value of In addition to the WordPress and PHP versions listed above, the plugin requires the PDO SQLite PHP extension and SQLite 3.37.0 or newer. The setup screen also needs write access to the Feedback helps improve the integration. For troubleshooting, questions, suggestions, or feature requests, open an issue in the SQLite GitHub repository<\/a>.<\/p><\/dd>\n Contributions are welcome through the SQLite Database Integration repository on GitHub<\/a>.<\/p><\/dd>\n Yes. The plugin replaces the default MySQL-based database layer with an SQLite-backed implementation. WordPress continues to use the SQLite Database Integration 3.1 is here! \ud83c\udf89<\/strong><\/p>\n\n This release improves database storage and configuration<\/strong> and fixes several MySQL compatibility issues.<\/p>\n\n What's new<\/strong><\/p>\n\n Version 3.1 improves how WordPress sites store, locate, and protect their SQLite databases. It also fixes SQL behavior and export compatibility:<\/p>\n\n For more information about database paths and secure configuration, read the database storage guide<\/a>.<\/p>\n\n Upgrading to 3.1<\/strong><\/p>\n\n Upgrading an existing SQLite site is straightforward:<\/p>\n\n Existing To properly secure the database<\/strong>, set Breaking changes<\/strong><\/p>\n\n Review these changes if you use custom database settings or integrations:<\/p>\n\n Thank you<\/strong><\/p>\n\n Thank you to everyone who contributed, tested, and helped update integrations.<\/p>\n\n Changes since 3.0.2:<\/strong> SQLite Database Integration 3 is here! \ud83c\udf89<\/strong><\/p>\n\n This release introduces an all-new SQLite database driver for WordPress<\/strong>, 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.<\/p>\n\n The 3.0 release spans nearly two years of work, featuring 160 pull requests<\/a> and 1,075 commits from 15 contributors.<\/p>\n\n What's new<\/strong><\/p>\n\n The new driver advances SQLite support for WordPress, plugins, database tools, and other MySQL-based applications. These improvements include:<\/p>\n\n For more information about the new driver and its architecture, read the driver announcement<\/a>.<\/p>\n\n Modular design<\/strong><\/p>\n\n The project was redesigned as a set of focused packages, separating the core driver from its WordPress integration:<\/p>\n\n This architecture opens the driver to new integrations, applications, and development tools beyond WordPress.<\/p>\n\n Upgrading to 3.0<\/strong><\/p>\n\n Upgrading an existing SQLite site is straightforward:<\/p>\n\n On first connection, the new driver automatically initializes its metadata without changing your tables or content.<\/p>\n\n If you used the new driver preview, you can now delete the Breaking changes<\/strong><\/p>\n\n Most WordPress sites need no changes. Review the following if you use a custom setup:<\/p>\n\nwpdb<\/code> API while the plugin translates and emulates MySQL queries for SQLite.<\/p>\n\nWhat the plugin provides<\/h4>\n\n
\n
\n
What is the purpose of this plugin?<\/h3><\/dt>\n
Can I use this plugin on my production site?<\/h3><\/dt>\n
Will this plugin migrate my existing site to SQLite?<\/h3><\/dt>\n
Where is the SQLite database stored?<\/h3><\/dt>\n
WP_CONTENT_DIR . '\/database'<\/code>. The full path is recorded in db-path.php<\/code> and exposed by the DB_PATH<\/code> constant at runtime.<\/p>\n\n\n
WP_CONTENT_DIR . '\/database\/.ht.020a33c5d9e5407e8e93b43e55abf62e\/.ht.sqlite'<\/code><\/li>\nWP_CONTENT_DIR . '\/database\/db-path.php'<\/code> as return __DIR__ . '\/...';<\/code><\/li>\nDB_PATH<\/code><\/li>\n<\/ol>\n\nDB_PATH<\/code> to an explicit, protected path<\/strong> outside the web root that your web server does not expose.<\/p>\n\nDB_PATH<\/code> after WordPress loads instead of assuming a fixed database path.<\/p><\/dd>\nHow can I configure the database location?<\/h3><\/dt>\n
DB_PATH<\/code> constant to an explicit path<\/strong> that is protected from public web access. An explicit DB_PATH<\/code> value is used as-is without randomization. Define it in wp-config.php<\/code>:<\/p>\n\n\/\/ Use protected DB path that is not exposed by the web server.\ndefine( 'DB_PATH', '\/private\/wordpress\/database.sqlite' );\n<\/code><\/pre>\n\nDB_PATH<\/code> must point to a protected<\/strong> location that your web server does not expose. Store the database outside the web root and make sure it's protected.<\/p>\n\nDB_PATH<\/code> must be an absolute path to the SQLite database file, or :memory:<\/code> for an in-memory SQLite database. The database directory must be writable by PHP. Changing DB_PATH<\/code> selects a different database without moving an existing one.<\/p><\/dd>\nWhat does the plugin require?<\/h3><\/dt>\n
wp-content<\/code> directory and will detect conflicting database drop-ins.<\/p><\/dd>\nWhere can I submit my plugin feedback?<\/h3><\/dt>\n
How can I contribute to the plugin?<\/h3><\/dt>\n
Does this plugin change how WordPress queries are executed?<\/h3><\/dt>\n
wpdb<\/code> API, while queries are internally adapted to SQLite syntax and behavior.<\/p><\/dd>\n\n<\/dl>\n\n\n3.1.0<\/h4>\n\n
\n
wp-content\/database\/<\/code>, recorded in wp-content\/database\/db-path.php<\/code>. (#502<\/a>)<\/li>\nDB_PATH<\/code>:<\/strong> Configure the database with one full-path constant, also available at runtime for integrations. (#512<\/a>)<\/li>\nIF()<\/code> condition evaluation and make TRADITIONAL<\/code> enable its component SQL modes. (#518<\/a>, #509<\/a>)<\/li>\nutf8mb4_unicode_520_ci<\/code> for new tables created with WordPress's charset settings, improving exports to MariaDB. Existing tables keep their recorded collation. (#514<\/a>)<\/li>\n\n
.ht.sqlite<\/code> and .ht.sqlite.php<\/code> databases move to the randomized layout automatically unless a database file path is explicitly configured.<\/p>\n\nDB_PATH<\/code> in wp-config.php<\/code> 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<\/code> does not move an existing database.<\/p>\n\n\n
wp-content\/database\/<\/code>. Explicitly configured file paths stay unchanged. Integrations, including backup and migration tools, must read DB_PATH<\/code> after WordPress loads instead of assuming a fixed filename.<\/li>\nDB_DIR<\/code> and DB_FILE<\/code> are now deprecated. They and the previously deprecated FQDB<\/code> and FQDBDIR<\/code> remain supported, but DB_PATH<\/code> takes precedence. Conflicting values trigger warnings.<\/li>\n:memory:<\/code> remains available for in-memory databases.<\/li>\n<\/ul>\n\nv3.0.2...v3.1.0<\/code><\/a><\/p>\n\n3.0.2<\/h4>\n\n
\n
SHOW CREATE TABLE<\/code> primary keys (#500<\/a>)<\/li>\n3.0.1<\/h4>\n\n
\n
3.0.0<\/h4>\n\n
\n
INFORMATION_SCHEMA<\/code> tables.<\/li>\nSHOW<\/code> and DESCRIBE<\/code> statements provide accurate MySQL-like metadata.<\/li>\n\n
\n
WP_SQLITE_AST_DRIVER<\/code> flag.<\/p>\n\n\n
\n
WP_SQLITE_AST_DRIVER<\/code> feature flag was removed.<\/li>\n<\/ul><\/li>\n\n
3.37.0<\/code> or newer is required.<\/li>\nWP_SQLITE_UNSAFE_ENABLE_UNSUPPORTED_VERSIONS<\/code> opt-in enables limited SQLite 3.27.0<\/code>\u20133.36.x<\/code> support.<\/li>\n<\/ul><\/li>\nDB_NAME<\/code> is required:<\/strong>\n\n\n
\n
WAL<\/code><\/a>. Account for -wal<\/code> and -shm<\/code> sidecar files.<\/li>\n