SQLite Database Integration
Exécutez WordPress sur SQLite.
Choix
Yes — SQLite Database Integration is a safe, well-maintained plugin to use in 2026. It runs on 5K+ sites, is rated 4.6/5 and was last updated 2 weeks ago, and scores 82/100 on our health check.
- Développé activement — Dernière mise à jour il y a 2 semaines
- Testé avec le dernier WordPress (7.1)
- Momentum — Téléchargements en hausse de 57,9 % par rapport aux 30 jours précédents
Comment s'accumule-t-il ?
Côte à côte sur les installations, les mises à jour, les évaluations et le supportTéléchargements quotidiens
Les pics de téléchargement suivent généralement une nouvelle version - chaque site qui met à jour automatiquement compte comme un téléchargement.
Classements
Where SQLite Database Integration stands todayWordPress.org Classements de recherche
Position en direct dans la recherche de plugins, Top 100| Mot-clé | Position |
|---|---|
| base de données | #11 |
| SQLite | #2 |
Adoption de version
Part de sites actifs par version.
Répartition des notes
★★★★★★★★★★ 4.6 from 12 reviews
About SQLite Database Integration
From the official readme · v3.1.3Description
Exécutez WordPress sur SQLite.
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.
The plugin replaces the default MySQL database layer with an SQLite-backed implementation. WordPress continues to use its standard wpdb API while the plugin translates and emulates MySQL queries for SQLite.
What the plugin provides
- No database server. Your site’s data is stored in a local SQLite database.
- Guided setup. The installation screen checks for the required PHP extension, write access, and conflicting database drop-ins before enabling SQLite.
- Purpose-built compatibility. A MySQL parser and emulation layer adapt MySQL syntax and behavior for SQLite.
- Useful diagnostics. SQLite details appear in Site Health, and Query Monitor is supported.
Important: 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.
The plugin requires the PDO SQLite PHP extension and SQLite 3.37.0 or newer.
Journal de modifications
Major release with an all-new SQLite driver. Requires SQLite 3.37.0 or newer. Back up your SQLite database before updating.
3.1.3
- Fix
BINARYandVARBINARYcolumn 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)
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
0xhexadecimal literals (#573) - Fix rebuilds of legacy text and binary columns (#565)
- Use
'0'column defaults in non-strictINSERTstatements (#569) - Roll back failed
OPTIMIZE TABLEandREPAIR TABLErebuilds (#567) - Remove the Rust parser extension (#566)
- Preserve
AUTO_INCREMENTcounters when rebuilding tables (#561) - Fix
ALTER TABLE ... ADD (...)for columns, indexes, and constraints (#557) - Fix
ON UPDATE CURRENT_TIMESTAMPfor explicit values and unchanged rows (#560) - Normalize zero defaults in date and time columns (#542)
- Add support for
ALTER COLUMNwithSET DEFAULTandDROP DEFAULT(#555)
3.1.1
- Support date arithmetic with
INTERVALoperators (#539) - Fix
ROLLBACKas 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()withoutSQL_CALC_FOUND_ROWS(#533) - Fix unique keys and foreign key restore without stringified fetches (#532)
- Fix
CREATE TEMPORARY TABLE IF NOT EXISTSandDROP TEMPORARY TABLEas 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)
3.1.0
SQLite Database Integration 3.1 is here! 🎉
This release improves database storage and configuration and fixes several MySQL compatibility issues.
Quoi de neuf
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 inwp-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 makeTRADITIONALenable its component SQL modes. (#518, #509) - WordPress table collations: Default to
utf8mb4_unicode_520_cifor 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 readDB_PATHafter WordPress loads instead of assuming a fixed filename. - Legacy constants:
DB_DIRandDB_FILEare now deprecated. They and the previously deprecatedFQDBandFQDBDIRremain supported, butDB_PATHtakes precedence. Conflicting values trigger warnings. - Absolute paths: Relative database file and directory paths are now rejected.
:memory:remains available for in-memory databases.
Merci
Thank you to everyone who contributed, tested, and helped update integrations.
Changes since 3.0.2: v3.0.2...v3.1.0
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 TABLEprimary keys (#500) - Align savepoint handling with MySQL semantics (#496)
3.0.1
Pour les développeurs
Est-ce votre plugin ? Montrez les chiffres.
Ajoutez un badge en direct à votre site, docs ou github readme. Il se met à jour par lui-même - aucun compte n'est nécessaire.
Best SQLite Database Integration alternatives
Tous les plugins de base de données →FAQ
SQLite Database Integration: quick answers
Réponses directes, extraites des données en direct WordPress.org.
Source : WordPress.org
Is SQLite Database Integration free?
Yes. SQLite Database Integration is free to download and use from the official WordPress.org plugin directory.
Is SQLite Database Integration safe to use in 2026?
Yes — SQLite Database Integration is a safe, well-maintained plugin to use in 2026. It runs on 5K+ sites, is rated 4.6/5 and was last updated 2 weeks ago, and scores 82/100 on our health check.
How many websites use SQLite Database Integration?
SQLite Database Integration is active on 5K+ WordPress websites and has been downloaded 1,141,786 times since it launched in January 2023. It was downloaded 237,620 times in the last 30 days.
Does SQLite Database Integration work with WordPress 7.1?
Yes. The developer has tested SQLite Database Integration up to WordPress 7.1.5, the latest release. It requires WordPress 6.4 or newer.
What PHP version does SQLite Database Integration need?
SQLite Database Integration requires PHP 7.2 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was SQLite Database Integration last updated?
The latest version, 3.1.3, was released on November 3, 2026 (2 weeks ago).
Who makes SQLite Database Integration?
SQLite Database Integration is developed and maintained by WordPress.org.
What are the best alternatives to SQLite Database Integration?
The most popular alternatives to SQLite Database Integration are Search Regex (100K+ installs), WP-Sweep (100K+ installs) and Advanced Database Cleaner (100K+ installs).
Propulsé par PageForge
Un modèle et une feuille de calcul. Une vraie page pour chaque recherche.
PageForge transforme chaque ligne d'un CSV en une page WordPress avec son propre titre, URL, SEO et schéma, construit sur la mise en page que vous Déjà conçu. Gratuit sur WordPress.org.
- CSV et XLSX, plus Google Sheets sur les professionnels et les entreprises
- Son propre titre, URL, SEO champs et schéma pour chaque page
- Fonctionne avec l'éditeur de blocs, Elementor, Divi et Avada
- Gratuit sur WordPress.org, pas de carte de crédit
