dwood

Ended up solving this as follows (“BSNKind” is a 9-digit unique field) in a cfdb_form_data filter:

/* Delete possible existing submission for same BSN. */
$bsn = $form_data->posted_data["BSNKind"];
if (!empty($bsn) && preg_match("/^\d{9}$/", $bsn)) {

    $submit_time = $wpdb->get_var("SELECT DISTINCT(submit_time) FROM wp_cf7dbplugin_submits WHERE field_name = 'BSNKind' AND field_value = '$bsn'");

    /* LIMIT 21 is a hacky attempt to prevent a disaster if
     * there's something wonky with $submit_time... Submission
     * currently has max 21 fields. */
    if (!empty($submit_time) && is_numeric($submit_time))
        $wpdb->query("DELETE FROM wp_cf7dbplugin_submits WHERE submit_time = $submit_time LIMIT 21");

}

Does that all look safe enough, or is there any way I could end up lying face-down in a pool of blood somewhere with an empty database…? 😉

Thanks,

David

Hmmm, possibly partially answering my own question ;-), in the function “is_already_submitted” on http://cfdbplugin.com/?page_id=904 you iterate through a filtered set looking for the unique value in question. If you find it, you set $found = true. Is there any way I could just do a delete there, or is that validation code read-only? Then instead of “if already exists update; else insert” I could just do “if already exists delete; then insert no matter what”…

Thanks,

David