[wp-trac] [WordPress Trac] #14080: Needless wp_cache_delete() inside set_theme_mod()

[WordPress Trac]

#14080: Needless wp_cache_delete() inside set_theme_mod()
--------------------------+-------------------------------------------------
 Reporter:  shidouhikari  |        Owner:        
     Type:  defect (bug)  |       Status:  closed
 Priority:  normal        |    Milestone:  3.1   
Component:  Cache         |      Version:        
 Severity:  normal        |   Resolution:  fixed 
 Keywords:                |  
--------------------------+-------------------------------------------------

Comment(by gazouteast):

 Huh?

 Do What?

 So the cache is saved to the database for recall, but cache delete does
 not remove it from the database?

 That's a bit like the garbage collectors coming round, looking in your
 garbage bin, then walking away without emptying it.

 Maybe I was right - maybe that is exactly the cause of the wp_options
 bloat and it was nothing at all to do with MagPie?

 In terms of having parallel update and delete calls, yes I can see where
 an update should override a delete, but then there are also times when a
 delete should override an update.

 Seems to me, what is needed is a conditional periodic purge function (not
 just at version upgrade) -
 - Check table for expired cache objects
 - identify creating function or plugin from cached object
 - check for function or plugin existence
 - if function or plugin does not exist, delete cache transient

 Some pretty heavyweight plugins fail to clean up behind themselves -
 Popularity Contest being one of them.  It now looks like even core
 dashboard widgets do that too.  This problem is bigger than it first
 appears.

 Suggest - reopen ticket and leave for community feedback.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/14080#comment:8>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software