[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:  2nd-opinion   |     Focuses:  performance
--------------------------+------------------------------

Comment (by shmulikk):

 Hi @dd32
 Thanks for looking into it. For some reason I didn't not get any
 notification and I just happened to re-check the status here.

 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.
 This means that the fact that I'm adding a caching plugin might actually
 hurt me because it will never fall back to the options table, thus
 functionality and performance are affected because the original code that
 try to use transients will fall back to its own defaults or re-run of
 logic due to the missing data.

 This is specially true to the cron issue I've mentioned above in one of my
 comments.

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