Title: SQLite Database Integration 3.1 compatibility
Last modified: October 7, 2026

---

# SQLite Database Integration 3.1 compatibility

 *  [Jan Jakeš](https://wordpress.org/support/users/janjakes/)
 * (@janjakes)
 * [1 day, 12 hours ago](https://wordpress.org/support/topic/sqlite-database-integration-3-1-compatibility/)
 * Hi AI1WM,
 * We want to let you know that SQLite Database Integration 3.1 introduces [`DB_PATH`](https://github.com/WordPress/sqlite-database-integration/pull/512)
   and [randomized database storage](https://github.com/WordPress/sqlite-database-integration/pull/502).
   Two compatibility points appear relevant to All-in-One WP Migration:
    - **Database-file exclusion:** In version 7.111, `Ai1wm_Export_Enumerate_Content::
      execute()` excludes `FQDB`. Please prefer `DB_PATH`, falling back to `FQDB`
      for older versions. When both constants are defined differently, WordPress
      uses `DB_PATH`, so the current exclusion targets the wrong file.
    - **Storage metadata during restore:** Managed databases now live under `wp-
      content/database/.ht.<random>/.ht.sqlite`, with `wp-content/database/db-path.
      php` recording their location. Please check that restoring files does not 
      overwrite the destination’s path metadata while excluding the corresponding
      SQLite database. This restore concern still needs an end-to-end check.
 * Existing database paths and older SQLite integration versions should remain supported.
 * Tracking issue: [https://github.com/WordPress/sqlite-database-integration/issues/513](https://github.com/WordPress/sqlite-database-integration/issues/513).
 * Thanks for looking into this.

Viewing 1 replies (of 1 total)

 *  Plugin Author [Yani](https://wordpress.org/support/users/yaniiliev/)
 * (@yaniiliev)
 * [1 day, 10 hours ago](https://wordpress.org/support/topic/sqlite-database-integration-3-1-compatibility/#post-19039026)
 * Hi Jan,
 * Thanks for the detailed heads-up, and for tracking this in issue #513
 * I’ve passed this to our product team to investigate against current All-in-One
   WP Migration. We’ll follow up here once we have a fix or a clearer plan. If there’s
   anything else we should watch for on the Playground / Studio side, feel free 
   to add it on this thread.
 * Thanks again for reaching out.

Viewing 1 replies (of 1 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fsqlite-database-integration-3-1-compatibility%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/all-in-one-wp-migration/assets/icon-256x256.png?rev=2458334)
 * [All-in-One WP Migration and Backup](https://wordpress.org/plugins/all-in-one-wp-migration/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/all-in-one-wp-migration/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/all-in-one-wp-migration/)
 * [Active Topics](https://wordpress.org/support/plugin/all-in-one-wp-migration/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/all-in-one-wp-migration/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/all-in-one-wp-migration/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Yani](https://wordpress.org/support/users/yaniiliev/)
 * Last activity: [1 day, 10 hours ago](https://wordpress.org/support/topic/sqlite-database-integration-3-1-compatibility/#post-19039026)
 * Status: not a support question