[wp-trac] [WordPress Trac] #63070: Flushing object cache removes all transients

WordPress Trac noreply at wordpress.org
Wed Apr 23 15:29:06 UTC 2025


#63070: Flushing object cache removes all transients
-------------------------+--------------------------
 Reporter:  deploysk     |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  General      |     Version:
 Severity:  normal       |  Resolution:  wontfix
 Keywords:  close        |     Focuses:  performance
-------------------------+--------------------------
Changes (by joemcgill):

 * status:  new => closed
 * resolution:   => wontfix
 * milestone:  Awaiting Review =>


Comment:

 I agree with @flixos90. The other thing to keep in mind is that transients
 were given their name due to the fact that they cannot always be expected
 to exist in the database.

 [https://developer.wordpress.org/apis/transients/ Quoting @rmccue from the
 Transient API docs:]

 > Everyone seems to misunderstand how transient expiration works, so the
 long and short of it is: transient expiration times are a maximum time.
 There is no minimum age. Transients might disappear one second after you
 set them, or 24 hours, but they will never be around after the expiration
 time.

 If you have a feature that depends on the data always existing, it is
 better to store that data as an option, rather than as a transient.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/63070#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list