Direct database calls without caching in db-optimize.php

[CoachBirgit]

Description

Line 84 makes a direct $wpdb call without using the WordPress object cache. The Plugin Checker flags this because repeated calls to the same query waste database resources.

Action needed

Wrap the query result with wp_cache_get() / wp_cache_set(), or add an inline PHPCS ignore comment with a justification if caching doesn't make sense for this operation (database optimization results change every time, so caching may be inappropriate here).

// phpcs:ignore WordPress.DB.DirectDatabaseQuery.DirectQuery, WordPress.DB.DirectDatabaseQuery.NoCaching -- Optimization results are not cacheable.

PHPCS rules

• WordPress.DB.DirectDatabaseQuery.DirectQuery (WARNING)
• WordPress.DB.DirectDatabaseQuery.NoCaching (WARNING)

[ivdimova]

All items from this issue were already resolved. Running phpcs directly against includes/abilities/db-optimize.php produces zero warnings.

The file already has:

• ✅ phpcs:ignore WordPress.DB.DirectDatabaseQuery.DirectQuery, WordPress.DB.DirectDatabaseQuery.NoCaching with justification (lines 80-81)
• ✅ phpcs:ignore WordPress.DB.DirectDatabaseQuery.DirectQuery, WordPress.DB.DirectDatabaseQuery.NoCaching on the OPTIMIZE TABLE loop (line 89)
• ✅ Documented rationale: optimization results change every run, so caching is inappropriate here

Closing as already resolved.