Oliver Jones

With respect, your statement "it would be preferable to avoid altering the indexes on live sites if possible" is _contrary to good practice_ for managing busy databases. It's a routine...

For what it's worth, my Database Performance health-check module for Performance Lab checks database connection latency. https://github.com/WordPress/performance/issues/455#issuecomment-1201217876

If you use a persistent object cache (presumably any of them, not just the SQLite one) transients are stored there, and not in the main database. That accounts for this...

Is it possible the SQLite version on @morganwdavis 's server/php installation is prior to 3.24? If so, it will gack on SQLite's UPSERT (ON CONFLICT) syntax. https://www.plumislandmedia.net/reference/sqlite3-in-php-some-notes/#upsert Just a thought.

Notes: UPSERT a/k/a **ON DUPLICATE KEY UPDATE** This has different syntax on SQLite, and doesn't exist at all prior to version 3.24. **SELECT DISTINCT meta_key FROM wp_postmeta WHERE meta_key NOT...

It's `NOT LIKE '\_%' . That is, it's NOT LIKE any string that begins with an underscore.

Upgrading the version of SQLite used in the php extension is difficult or impossible for the customers of must hosting providers. The most likely way to make it happen is...

My proposed fix to #16 handles deactivation correctly. Double-activation is still a problem.

The plugin also says "myisam" for storage engine instead of "innodb". It would be good to expose the actual SQLite version, but we can't do that directly with db_version because...

The actual version of SQLite in use depends on the version installed as the php extension on each host. I've never seen anything before 3.7 in the wild. A variety...