[wp-trac] [WordPress Trac] #20316: Garbage collect transients

[WordPress Trac]

#20316: Garbage collect transients
----------------------------------------------+------------------
 Reporter:  nacin                             |       Owner:
     Type:  enhancement                       |      Status:  new
 Priority:  normal                            |   Milestone:  3.7
Component:  Database                          |     Version:
 Severity:  normal                            |  Resolution:
 Keywords:  dev-feedback has-patch 3.7-early  |
----------------------------------------------+------------------

Comment (by Rarst):

 The issue is much like users keeping important files in recycle bin (which
 I actually encountered in real life :) It happens, but you cannot make
 decisions for everyone based on some people doing things that are Really
 Bad Idea.

 > If programmers were only using it for cacheing, then I think the problem
 of huge amounts of un-cleared, expired transients wouldn't exist (or at
 least, not to the extent it does)

 You make assumption here that caching use cases do not produce transients
 garbage. There is no basis for that. Garbage produced comes from faults
 (or natural limits) in implementation, not the functional intent of that
 implementation (be it right or wrong in regards to API purpose).

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