[wp-trac] [WordPress Trac] #19866: Allow specifications of any wp_posts field(s) in WP_Query

WordPress Trac noreply at wordpress.org
Mon Feb 2 14:45:07 UTC 2015

#19866: Allow specifications of any wp_posts field(s) in WP_Query
 Reporter:  bigdawggi        |       Owner:
     Type:  enhancement      |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Query            |     Version:
 Severity:  normal           |  Resolution:  wontfix
 Keywords:  has-patch close  |     Focuses:

Comment (by boonebgorges):

 I understand the memory issue and I'm sympathetic. However, cases where
 you *legitimately* need 1000 posts are exceedingly rare, and we should not
 optimize for cases where people are _doing_it_wrong(). In real life cases,
 where you might pull 10 or 20 or even 100 posts, the memory overhead is
 close to negligible.

 More importantly, any immediate performance gain that you get from cherry-
 picking post fields is immediately offset when you introduce a persistent
 cache, because, for reasons discussed above, these kinds of queries cannot
 interact properly with the cache (at least, not without a rewrite of the
 way that `WP_Query` primes and accesses post caches).

Ticket URL: <https://core.trac.wordpress.org/ticket/19866#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

More information about the wp-trac mailing list