Skip to content

Add comment explaining db_fallback TTL refresh asymmetry in persist_throttle_state #16

@mrtwebdesign

Description

@mrtwebdesign

Source: PR #4 follow-up review (minor)

Problem

persist_throttle_state() refreshes TTL on unchanged state for object cache and APCu (lines 529-535) but skips db_fallback. This is correct because wp_options has no TTL, but the asymmetry is subtle.

Fix

Add a one-line comment on the early return explaining: "db_fallback uses wp_options which has no expiry — no refresh needed."

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationeffort: lowMinutes to ~1 hourpriority: lowNice to have, no urgency

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions