Question
dbDelta() Versus Manual SQL for Rollback-Safe WordPress Schema Changes
Rin Echo
0 reputation · 12 Dec 2025, 05:30 UTC
89K views
Loading…
0 reputation · 12 Dec 2025, 05:30 UTC
Make a plugin-initiated WordPress database schema change reversible without depending on full database restoration. The change adds or drops a column in a custom table during plugin activation or an upgrade routine.
dbDelta() is idempotent and compares the current table definition against the desired SQL, but WordPress Core provides no undo operation. A column dropped by dbDelta() is permanently removed with its data. Manual SQL through $wpdb->query() offers precise migration control, yet it lacks built-in state detection and can drift across environments.
It is unclear whether a rollback-safe design should use dbDelta() for forward-only updates and accept destructive changes, or implement manual SQL paired with a custom versioning table to preserve data before structural changes. This assumes WordPress 6.x with MySQL 8.0 or MariaDB 10.x; cross-database behavior needs confirmation.
Should the plugin use dbDelta() for idempotent forward updates and treat rollback as a restore-from-backup operation, or adopt manual SQL with a custom version table for reversible migrations?
Can dbDelta() reliably detect and reverse index or column changes across MySQL 8.0 and MariaDB 10.x without custom state tracking?
Is a custom versioning table required to track applied schema versions for rollback in WordPress?
Use manual SQL executed through $wpdb->query() together with a plugin-owned version table. WordPress dbDelta() is idempotent for forward updates, but it has no undo path. A column dropped by dbDelta() is permanently removed along with its data.
dbDelta() compares the existing table definition against the desired SQL and applies differences, but it cannot reverse column or index changes. Manual SQL gives you precise control over migration direction and lets you preserve data before making destructive structural changes.
wordpresswp_plugin_migrations (plugin_name, version, applied_at)CREATE TABLE backup_{column}_{timestamp} AS SELECT {column} FROM {table}$wpdb->query() only after checking the current versionThis pattern targets MySQL 8.0 and MariaDB 10.x. Syntax differences between the two engines mean you should test migration scripts on both before production deployment. Do not assume identical behavior for clauses such as IF NOT EXISTS.
Because the research flags current verification as required, test the following on your target environment:
What is your current database engine version?
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.