$conf, $runtime; function_exists('chdir') AND chdir(APP_PATH); $r = 'mysql' == $conf['cache']['type'] ? website_set('runtime', $runtime) : cache_set('runtime', $runtime); } function runtime_truncate() { global $conf; 'mysql' == $conf['cache']['type'] ? website_set('runtime', '') : cache_delete('runtime'); } register_shutdown_function('runtime_save'); ?>custom field - Why orderbyb meta_value_num won't affect the generated SQL Query order?|Programmer puzzle solving
最新消息:Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)

custom field - Why orderbyb meta_value_num won't affect the generated SQL Query order?

matteradmin9PV0评论

I've exhausted myself with this and I couldn't figure out why when I do this

$myposts = new WP_Query( array('numberposts' => 5,
'offset' => '0',
'post_type' => 'noticias',
'orderby' => 'meta_value_num',
'order' => 'DESC',
'post_status' => 'publish',
'meta_key' => '_countview'
));

wordpress queries the db with the following SQL:

SELECT SQL_CALC_FOUND_ROWS wp_posts.ID 
FROM wp_posts INNER JOIN wp_postmeta ON (wp_posts.ID = wp_postmeta.post_id) 
WHERE 1=1 
 AND wp_posts.post_type = 'noticias' 
 AND (wp_posts.post_status = 'publish') 
 AND (wp_postmeta.meta_key = '_countview' ) 
GROUP BY wp_posts.ID ORDER BY wp_posts.post_date ASC LIMIT 0, 5

did something change for 3.4 and i'm missing the syntax?

Post a comment

comment list (0)

  1. No comments so far