Large SELECT Query Warning
-
I got this error in my logs, not a big deal for me since just testing your plugin out at the moment, but thought you should know about it, seems like you may want to optimize this MySQL query:
[10-Jun-2018 11:03:20 UTC] WordPress database error The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay for query SELECT l.*
FROM bbq_gamipress_logs AS l
LEFT JOIN bbq_gamipress_logs_meta AS lm0 ON ( l.log_id = lm0.log_id ) LEFT JOIN bbq_gamipress_logs_meta AS lm1 ON ( l.log_id = lm1.log_id )
WHERE l.user_id = ’59’
AND ( ( l.type = ‘event_trigger’ ) AND ( l.trigger_type = ‘gamipress_bp_group_publish_activity’ ) AND ( lm0.meta_key = ‘_gamipress_activity_id’ AND lm0.meta_value = ‘398’ ) AND ( lm1.meta_key = ‘_gamipress_group_id’ AND lm1.meta_value = ’17’ ) )
ORDER BY l.date DESC
LIMIT 1 made by do_action(‘wp_ajax_post_update’), WP_Hook->do_action, WP_Hook->apply_filters, bp_legacy_theme_post_update, groups_post_update, do_action(‘bp_groups_posted_update’), WP_Hook->do_action, WP_Hook->apply_filters, gamipress_bp_group_publish_activity, do_action(‘gamipress_bp_group_publish_activity’), WP_Hook->do_action, WP_Hook->apply_filters, gamipress_trigger_event, apply_filters(‘gamipress_user_deserves_trigger’), WP_Hook->apply_filters, gamipress_bp_trigger_duplicity_check, gamipress_get_user_last_log
- The topic ‘Large SELECT Query Warning’ is closed to new replies.
