Resolved Fix definers if MySQL user is renamed during migration

[nineproof]

When Plesk Migrator has to rename a MySQL user during migration due to a conflict,
showing this warning message in the log:

MySQL database user with the name 'wordpress_0' already exists on target server. Database user 'wordpress_0' from the source server will be renamed to 'wordpress_02' on the target server.​

the DEFINER of stored procedures, views, AFTER triggers, events won't be changed accordingly, causing disruption of the migrated site, with errors like:

The user specified as a definer ('wordpress_1'@'%') does not exist.​

Seems the the issue won't involve just BEFORE triggers. No warnings are shown in the log.

 

[Mr.D]

Hello, we have created Plesk Migrator issue PMT-4065. It will be investigated and fixed in future releases if will be confirmed.

 

[Mr.D]

Hello,

We have investigated this behavior and confirmed more one software issue PMT-4073.
The issue PMT-4065 describe slightly different situation.