[wp-trac] [WordPress Trac] #14254: update_meta_cache fails; query too large?

[WordPress Trac]

#14254: update_meta_cache fails; query too large?
--------------------------+-----------------------
 Reporter:  newpixel      |       Owner:
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:  3.7
Component:  Cache         |     Version:  2.9.2
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |
--------------------------+-----------------------

Comment (by nacin):

 The limit is not bad but it is tough to get around it when you want to.
 Either a `$force = false` parameter, or have update_meta_cache() that
 wraps a force_update_meta_cache() that ignores any limit.

 You have to think that if someone is doing an unbounded query on massive
 amounts of data (deliberately), they should know to turn off the cache
 priming.

 Or: maybe we should chunk this. If we get greater than 200 IDs, then break
 them into groups of 100 and do individual queries. That's better than
 timing out, but at the same time, maybe follows the spirit of cache-
 priming a bit better than not priming the cache at all.

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