| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 11 months |
| seen | Jul 2 '12 at 5:49 | |
| stats | profile views | 3 |
|
May 22 |
comment |
Alter SQL query to return posts with unique custom field value, no duplicate values Yep, just asking if there was a significant difference in performance when querying a lower number like 30 as opposed to the full list of posts. Could you elaborate on why it would not only be faster, but safer as well? |
|
May 22 |
awarded | Scholar |
|
May 22 |
accepted | Alter SQL query to return posts with unique custom field value, no duplicate values |
|
May 22 |
comment |
Alter SQL query to return posts with unique custom field value, no duplicate values I'm going with the 2nd loop idea you suggested! One question though: setting "posts_per_page" retrieves all posts. Is there a performance issue from a database call like this (from a list of 2000 posts)? Would it be better to set it to 20-30, just to make sure that when the doubles are removed in the 1st loop, i will still have enough posts for the 2nd loop. |
|
May 22 |
asked | Alter SQL query to return posts with unique custom field value, no duplicate values |