fix(dev-env): use -o so myloader drops existing tables before import

[WRasada]

Problem

vip dev-env import sql fails for every MyDumper-format dump imported into an environment that has any pre-existing tables — which is all of them, since a fresh dev-env ships with the default WordPress tables. myloader exits with code 133 (SIGTRAP via GLib g_error) after:

** (myloader): CRITICAL **: Thread N using connection M - ERROR 1050: Table 'wp_...' already exists
** (myloader): ERROR **: Thread N: issue restoring ...-schema.sql

Retrying after a partial import fails instantly for the same reason.

Root cause

vip-container-images#1463 bumped mydumper 0.18.1 → 0.21.3 in the php image. In myloader ≥ 0.20, --overwrite-tables was deprecated in favor of -o/--drop-table and re-registered as a bare boolean that no longer sets the purge mode, which stays at its default FAIL (myloader_arguments.c#L206, myloader_restore_job.c#L43). No DROP TABLE is ever issued — the overwrite_table() switch falls through to its This should not happen branch — and the first colliding CREATE TABLE is fatal.

Fix

Pass -o instead of the long flag in getImportArgs() (src/commands/dev-env-import-sql.ts). -o is correct on every myloader version:

myloader	-o resolves to
≤ 0.19	short form of --overwrite-tables
≥ 0.20	short form of --drop-table, defaulting to DROP mode

Testing

• Reproduced the 133/ERROR 1050 failure against a populated dev-env DB with --overwrite-tables; instant failure (<1s).
• With -o, myloader emits Dropping table or view (if exists) ... per table and a 201,721-table production-scale dump imports over a populated database end to end.

Changelog Description

Fixed

• Dev-env: Fixed SQL imports of MyDumper-format backups failing with ERROR 1050: Table already exists when the local database contains existing tables

Related

• Refs PLTFRM-22 / PLTFRM-1032 (prior MyDumper import escalations)
• Companion PRs: fix(dev-env): recompute mydumper section sizes after search-replace #2872 (search-replace size fix), fix(validations): avoid ENGINE != InnoDB false positives on row data #2873 (ENGINE validation), perf(dev-env): tune local database performance defaults #2874 (DB tuning)

🤖 Generated with Claude Code

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud