Schema Change

Why It Shows Up

Plugin Check found `$wpdb` access that queries the database directly, changes schema, or bypasses normal caching expectations.

Why It Matters

Direct queries can be correct, but they are easier to make unsafe, slower at scale, and harder for WordPress to cache or filter.

How to Fix

• Use WordPress APIs such as post, term, metadata, option, or user functions when they fit the task.
• If direct SQL is necessary, prepare dynamic values and add a clear caching strategy for repeated reads.
• Keep schema changes in activation or upgrade routines and make them idempotent.

References