WordPress 6.5, support for new WAL2 in SQLite

1.3.8

WordPress 6.5 Compatible

Fix DELETE ... LIMIT bug

Do DELETE ... LIMIT so it works on all SQLite compiles.

There's a compilation option in SQLite that allows it to handle LIMIT clauses on DELETE operations. It's not always turned on. So, we have to do transaction-size-limited DELETEs in a portable way.

1.3.6 Fewer timeouts.

This release should have fewer timeouts.

• Clean up in chunks in an attempt to reduce contention delays and timeouts.
• Do PRAGMA wal_checkpoint(RESTART) when cleaning up, and also occasionally, to prevent the write-ahead log from growing without bound on busy systems.
• Retry three times if cache updates time out.
• Increase default cache size to 16MiB for new users.

1.3.5 Allow use after close, fix php8 deprecations

php8, allow use after close.

1.3.4 Reduce transaction duration, order multiple puts, support mmap

Support mmap_size.

1.3.2 Avoid VACUUM operation on SQLite database.

Do not VACUUM the database except when commanded to purge all cache entries.

1.3.1 Purge old entries with resilience to disabled WP_Cron.

1.3.1 -- Cleanup and tag.

Support get_multiple. Purge to control cache size growth.

This release includes optimization for get_multiple, fetching cache entries by range of names where possible.

This release allows users to set a target size for cached data. Hourly it purges the oldest cache entries (least recently updated) to reduce the cache size to the target size.

1.2.3 Use WP_CACHE_KEY_SALT correctly.

#27 Sanitize WP_CACHE_KEY_SALT before using it in a filename.

1.2.2 avoid error-handling fault

#25 Fix error recovery defect. Props to Steven Sullivan.