<?php
/**
 * Uninstall.
 *
 * Removes everything the plugin stored. The SMTP password is in there, so
 * leaving it behind after the site owner has deliberately deleted the plugin
 * would be the worst kind of residue.
 *
 * @package PigeonMail
 */

declare( strict_types=1 );

defined( 'WP_UNINSTALL_PLUGIN' ) || exit;

delete_option( 'pigeon_mail_settings' );
delete_option( 'pigeon_mail_last_error' );
delete_option( 'pigeon_mail_stats' );
delete_option( 'pigeon_mail_failure_dismissed' );

// Per-user test results are short-lived transients, but a site removing the
// plugin mid-test should not keep them either.
global $wpdb;

// The transients are named per user, so they can only be found by their prefix. This runs once, on
// uninstall, where there is no cache worth consulting and the options table is the only place they live.
// phpcs:ignore WordPress.DB.DirectDatabaseQuery.DirectQuery, WordPress.DB.DirectDatabaseQuery.NoCaching
$pigeon_mail_transients = $wpdb->get_col(
	$wpdb->prepare(
		"SELECT option_name FROM {$wpdb->options} WHERE option_name LIKE %s",
		$wpdb->esc_like( '_transient_pigeon_mail_' ) . '%'
	)
);

foreach ( (array) $pigeon_mail_transients as $pigeon_mail_option ) {
	delete_option( $pigeon_mail_option );
	delete_option( str_replace( '_transient_', '_transient_timeout_', (string) $pigeon_mail_option ) );
}