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

WordPress Trac noreply at wordpress.org
Thu Sep 12 23:21:56 UTC 2013

#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 DavidAnderson):

 My "or at least, not to the extent it does" was intended to acknowledge
 that there is transient garbage from caching use cases. But, from
 following the discussion of this issue since the start of this year, that
 doesn't seem to me to be where the interest in the bug is coming from.

 The Recycle Bin analogy suggests that people using the Transient API for
 non-caching uses are novices or a bit stupid. That's not my experience
 from where I've seen people discussing the Transient API on mailing lists.
 Basically up until this point, "transient API = only for cacheing" has
 been a reality only in the documentation, not in the vast majority of
 implementations (e.g. unless you deploy memcached or another very
 specialised use-case, in which you'll know what you're doing). The patch
 for this bug enforces that reality in a way that will cause a lot of pain
 for programmers that I think is unnecessary. Sticking to principles has
 its place, but in the real world I foresee a lot of trouble from this

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

More information about the wp-trac mailing list