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

 I totally see what you're saying, but isn't the reason why this ticket has
 come to exist (and garnered so much interest) that lots of programmers are
 using the transient API simply as generic temporary data storage (without
 respect to the documentation stating that its intention is for cacheing?).

 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). If the ticket is responding to that on-
 the-ground situation, then the solution seems like the nuclear option so
 that programmers learn about the officially supported uses of the
 transient API the hard way.

 i.e. if the transient API is not meant to be used for generic temporary
 storage, then this ticket should just be ignored, as it deals with an
 officially non-existent problem. If on the other hand we recognise that it
 *is* widely used that way, then the solution (killing off lots of data, a
 few times a year) is much worse than the problem (excessive growth in
 database size).

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