Repository navigation
Add commands to export and import SQLite databases #327
Description
For increased compatibility with SQLite, it would be nice to be able to:
- Import a SQLite database into a MySQL database.
- Import a MySQL database into a SQLite database.
- Export a MySQL database to a SQLite database.
- Export a SQLite database to a MySQL database.
I think these features could live inside of wp db export and wp db import.
Activity
wojtekn commentedon Jun 10, 2024
We could consider to have SQLite-MySQL and MySQL-SQLite implementation a part of https://github.com/wordPress/sqlite-database-integration/.
wojtekn commentedon Jun 13, 2024
I talked with @schlessera and came up with the proposed plan:
DB_Command::import()andDB_Command::export()to use the new library--dialectoption for wp db export to let the user choose MySQL or SQLite dialectThen, other WP tools, like Sandbox Site powered by Playground or the sqlite-database-integration plugin, could reuse the import/export library.
Any thoughts? What feedback do you have?
CC @danielbachhuber @adamziel
danielbachhuber commentedon Jun 14, 2024
This seems reasonable, although I would prefer to implement as a WP-CLI command first and then figure out the abstraction. I think the abstraction could quickly rabbit hole into zero progress.
schlessera commentedon Jun 18, 2024
@danielbachhuber I get the concern, but I think the entire point here is to build something reusable. The way WP-CLI commands are usually built just results in spaghetti code that can hardly be salvaged - unless you have a strict conceptual separation from the start, at which point a distribution via a separate package is just a minor detail.
With a separate package, we can reuse that package on 2 or more fronts at the same time to make sure we exchange data.
I'll help with the architectural design to ensure we do this iteratively and don't get stuck along the way.
danielbachhuber commentedon Jun 18, 2024
@schlessera Ok. We need a version of this in the short term, though. @wojtekn Maybe our first draft can be an internal implementation, and then we can produce a final version as a public library?
adamziel commentedon Jun 19, 2024
+1 on separating this from a start. Starting as an internal implementation sounds good if that's later turned into a reusable library.
All these combinations are covered by a single, existing exporter.
The existing Sandbox Site plugin produces a MySQL-compliant dump from either MySQL or SQLite. That dump can then be imported into MySQL verbatim, or into SQLite using the SQLite database integration plugin.
mysqldumpis great as an option when it's available. When it isn't installed or accessible (proc_open may be disabled) the PHP exporter fallback would still be useful. That's the only way we could eventually make it a part of WordPress core.Looping in @brandonpayton.
wojtekn commentedon Jul 24, 2024
We work on that under #259
vadimkantorov commentedon Oct 10, 2024
Some additional considerations:
.dbfile - in many circumstances we need this, and not the sql dump file (even if in sqlite dialect)This feature idea is especially pertinent given that Sqlite integration is rapidly developing:
But even outside this context, having a single-file binary-file backup is nice to have and work with.