fix(restore): replace USE statements with target database during restore

[CebRazvan]

Summary

Fixes #3436

When restoring a MySQL/MariaDB backup to a different database, the SQL dump may contain USE \original_database`` statements that override the target database specified in the restore dialog. This causes data to be restored into the wrong database, potentially overwriting production data.

Problem

SQL dumps created by mysqldump/mariadb-dump include explicit database selection:

-- MariaDB dump


USE `production_db`;


DROP TABLE IF EXISTS `users`;


CREATE TABLE `users` ...


INSERT INTO `users` VALUES ...

When a user restores this backup into a different database (e.g., dev_db):

mariadb -u user -p dev_db < backup.sql

The USE \production_db`statement inside the dump switches the context toproduction_db, and all subsequent DROP TABLE, CREATE TABLE, and INSERTcommands execute against the **production database** instead of the intendeddev_db`.

Result: Production database is overwritten with old backup data. Critical data loss.

Solution

Added a sed filter to replace all USE \...`` statements with the target database name before piping to mysql/mariadb:

# Before (vulnerable)


... | docker exec -i $CONTAINER_ID sh -c "mariadb -u user -p db_name"



# After (safe)


... | sed "s/USE \`[^\`]*\`/USE \`db_name\`/g" | docker exec -i $CONTAINER_ID sh -c "mariadb -u user -p db_name"

This ensures all USE statements in the dump are rewritten to point to the user-specified target database.

Changes

• packages/server/src/utils/restore/utils.ts:

  • Updated getMariadbRestoreCommand() - added sed filter for USE statements

  • Updated getMysqlRestoreCommand() - added sed filter for USE statements

Testing

• Tested restore of MariaDB backup to same database name - works
• Tested restore of MariaDB backup to different database name - USE statements correctly replaced
• Verified sed regex handles multiple USE statements in dump
• Verified database comments (e.g., -- Database: xyz) are not affected

Checklist

• You created a dedicated branch based on the canary branch.
• You have read the suggestions in the CONTRIBUTING.md file
• You have tested this PR in your local instance.

Note: The sed regex was tested manually on real MariaDB dump files. Full integration testing in Dokploy instance was not performed but the change is minimal and isolated.

Issues related

closes #3436