[wp-trac] [WordPress Trac] #33276: redundant wp_using_ext_object_cache check in get/set_transient

[WordPress Trac]

#33276: redundant wp_using_ext_object_cache check in get/set_transient
--------------------------+------------------------------
 Reporter:  shmulikk      |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Cache API     |     Version:  2.8
 Severity:  normal        |  Resolution:
 Keywords:  close         |     Focuses:  performance
--------------------------+------------------------------
Changes (by dd32):

 * keywords:  2nd-opinion => close


Comment:

 > Baiscally you are right with claim that all code should deal with not
 being able to get transients.
 > The problem is that once an external caching plugin is used - the
 transients will completely fail, while the options mechanism will
 gracefully fall back.

 I understand the issue here, but I don't think this is something we can
 handle in Core gracefully in a manner that is appropriate for the vast
 majority of sites that actually rely upon object caches.
 If you're running an object cache on a large site, falling back to the
 database would be disastrous for a site in the event the object cache went
 unavailable.

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