Bug #73575 Loading a dump from an UNC path fails
Submitted: 13 Aug 2014 15:17 Modified: 17 Sep 2015 22:36
Reporter: Daniël van Eeden (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S3 (Non-critical)
Version:6.1.7 OS:Windows (7)
Assigned to: CPU Architecture:Any

[13 Aug 2014 15:17] Daniël van Eeden
Description:
Loading a dump from non-UNC paths works, from UNC fails.

16:48:28 Restoring \\foo.local\data$\Users\myuser\Mijn Documenten\dumps\Dump20140813.sql
Running: mysql.exe --defaults-file="c:\users\myuser\appdata\local\temp\tmpojfxm0.cnf"  --protocol=pipe --user=root --default-character-set=utf8 --comments --database=mydb < "\\foo.local\\data\$\\Users\\myuser\\Mijn Documenten\\dumps\\Dump20140813.sql"
The system cannot find the file specified.

Operation failed with exitcode 1
16:48:29 Import of \\foo.local\data$\Users\myuser\Mijn Documenten\dumps\Dump20140813.sql has finished with 1 errors

How to repeat:
Try to restore a sql dump file from an UNC path.
Maybe the $ char breaks it somewhere?
[14 Aug 2014 7:14] MySQL Verification Team
Hello Daniël,

Thank you for the report.

I'm seeing different error message when trying to import(but from windows explorer I can access the same file without any issues) a file with UNC path..

12:41:43 Restoring \\mysqlsup99\d$\ushastry\setups\bug.sql\test_bug.sql
Running: mysql.exe --defaults-file="c:\users\ushastry\appdata\local\temp\tmpg8g0fy.cnf"  --protocol=pipe --user=root --default-character-set=utf8 --comments --database=test < "\\mysqlsup99\\d\$\\ushastry\\setups\\bug.sql\\test_bug.sql"
The network name cannot be found.

Operation failed with exitcode 1
12:41:44 Import of \\mysqlsup99\d$\ushastry\setups\bug.sql\test_bug.sql has finished with 1 errors

Thanks,
Umesh
[17 Sep 2015 22:36] Philip Olson
Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 6.3.5 release, and here's the changelog entry:

The import and export process did not always function with network
folders.

Thank you for the bug report.