4 ms·
Thank you. (I wrote this three years ago.) https://billpg.com/dear-wordpress-please-stop-using-mysql/ https://billpg.com/dear-wordpress-please-stop-using-mysql/
by billpg 4y ago
Thank you. (I wrote this three years ago.)
https://billpg.com/dear-wordpress-please-stop-using-mysql/ https://billpg.com/dear-wordpress-please-stop-using-mysql/
Short version: With MySQL, I can't simply backup or deploy a copy of WP by zipping up a folder full of files. The database has to be backed-up and deployed separately but in sync with the folder of files too. Moving to an architecture where the database are files inside that folder would simplify all of this.
- jkingsman 4y agoWhat are your thoughts on plugin backward compatibility? That could create a lot of issues. (To be clear, I /love/ the idea of sqlite being the default; I just genuinely can't figure out a way around the plugin headache.)
- billpg 4y agoIf running WP this way becomes popular, plugins will adapt and advertise themselves as compatible with SQLite.
- todotask 4y agoI assume there is also a need to backup and deployment for web server configuration too?
- andai 4y agoIt isn't safe to copy a SQLite database because the file might be in the middle of a transaction. You need to use the ".backup" command instead.
- Neil44 4y agoThis is true, but because most Wordpress sites hardly ever do inserts etc it’s probably not going to be an issue in this scenario.
- billpg 4y agoIf that's true, that's a flaw in SQLite. The plug might be pulled at any moment and you can't stop it.
- billpg 4y agoI am incorrect in this regard.
- axelthegerman 4y agoYou can use litestream for proper sqlite replication