[wp-trac] [WordPress Trac] #27077: fix to avoid requery database for large result set via get_row

WordPress Trac noreply at wordpress.org
Sun Feb 9 17:22:21 UTC 2014


#27077: fix to avoid requery database for large result set via get_row
-------------------------+--------------------------
 Reporter:  openadvent   |       Owner:
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Database     |     Version:  3.8.1
 Severity:  normal       |  Resolution:  invalid
 Keywords:               |     Focuses:  performance
-------------------------+--------------------------

Comment (by nacin):

 Then put a LIMIT on it. get_row() for X results and get_results() for X
 results are going to use the same amount of memory.

 If you want to loop through records by "chunking" them into multiple
 queries using offset LIMITs, then you can/should do so. You don't need an
 API for that; it's too restricting for what needs to be handled on a case-
 by-case basis.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/27077#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list