如何在WordPress中用循环检测数据库记录是否存在并重试创建？

Got it, let's tackle your two specific WordPress needs with practical, safe code examples that align with best practices.

In WordPress, you should always rely on the built-in $wpdb class instead of raw SQL queries for security and compatibility. Here's how to build a loop that checks for a specific record, with safeguards to avoid infinite loops and database overload:

First, define your target record's unique identifier (this could be a post ID, user ID, or custom unique field—adjust based on your use case). Then set a maximum number of retries and a short delay between checks to avoid overwhelming your server.

// Define check parameters
$target_post_id = 123; // Example: the post we're adding lat/lng data for
$max_retries = 5;
$retry_delay = 2; // Seconds between each check
$retry_count = 0;
$record_exists = false;

// Loop to check for the record
while ( $retry_count < $max_retries && !$record_exists ) {
    // Use $wpdb to query if the GEOMyWP record exists
    // Adjust the table name and WHERE clause to match GEOMyWP's actual structure
    $record_exists = $wpdb->get_var(
        $wpdb->prepare(
            "SELECT COUNT(*) FROM {$wpdb->prefix}geo_my_wp_locations WHERE post_id = %d",
            $target_post_id
        )
    ) > 0;

    if ( !$record_exists ) {
        sleep( $retry_delay );
        $retry_count++;
    }
}

// Post-loop result handling
if ( $record_exists ) {
    echo "Record found after {$retry_count} retries!";
} else {
    echo "Failed to locate the record after {$max_retries} attempts.";
}

Note: Replace {$wpdb->prefix}geo_my_wp_locations with the actual table name GEOMyWP uses (you can confirm this via phpMyAdmin or your hosting database tool). The post_id is just an example—use whatever unique field ties your record to the content you're working with.

Now let's tie this check logic into retrying the GEOMyWP function when it fails. The core idea is: run the function, verify if the record was created, and if not, retry the function and re-check until we hit the max retry limit.

// Define your parameters
$target_post_id = 123;
$lat = 40.7128; // Example latitude
$lng = -74.0060; // Example longitude
$max_retries = 5;
$retry_delay = 2;
$retry_count = 0;
$record_created = false;

// Loop to attempt creation and verify success
while ( $retry_count < $max_retries && !$record_created ) {
    // Run GEOMyWP's default function to add the location record
    // Adjust this to match the exact GEOMyWP function you're using
    gmw_save_location( array(
        'post_id' => $target_post_id,
        'lat'     => $lat,
        'lng'     => $lng,
        // Add any other required parameters for the function
    ) );

    // Check if the record exists now
    $record_created = $wpdb->get_var(
        $wpdb->prepare(
            "SELECT COUNT(*) FROM {$wpdb->prefix}geo_my_wp_locations WHERE post_id = %d AND lat = %f AND lng = %f",
            $target_post_id,
            $lat,
            $lng
        )
    ) > 0;

    if ( !$record_created ) {
        sleep( $retry_delay );
        $retry_count++;
        error_log( "GEOMyWP location save failed for post {$target_post_id}, retrying (attempt {$retry_count}/{$max_retries})" );
    }
}

// Final result handling
if ( $record_created ) {
    echo "Successfully created the record after {$retry_count} attempts!";
} else {
    echo "Failed to create the record after {$max_retries} attempts. Check your error logs for details.";
}

Key Tips: #

• Error Logging: Adding error_log() helps you debug why the function is failing occasionally—you can check your WordPress error log for clues like missing parameters or database connection issues.
• Avoid Infinite Loops: Always set a $max_retries limit so the loop doesn't run indefinitely if something is broken (like invalid lat/lng values).
• Database Safety: Using $wpdb->prepare() prevents SQL injection attacks—never skip this step when passing dynamic values to queries.
• GEOMyWP Function Check: Double-check the exact parameters required for the GEOMyWP function you're using (e.g., gmw_save_location)—missing or incorrect parameters are a common reason for occasional failures.

内容的提问来源于stack exchange，提问作者RobbTe