Bug #75454 WB doesn't accept relative paths for .SQL file argument
Submitted: 8 Jan 2015 18:08 Modified: 19 Jan 2017 18:39
Reporter: Todd Farmer (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:6.1 OS:Any
Assigned to: CPU Architecture:Any

[8 Jan 2015 18:08] Todd Farmer
Description:
MySQL Workbench allows users to start MySQL Workbench with an optional argument of a .SQL script file or WB model file:

C:\Users\tofarmer\Downloads>"C:\Program Files (x86)\MySQL\MySQL Workbench 6.1 CE\MySQLWorkbench.exe" -help

C:\Users\tofarmer\Downloads>MySQLWorkbench.exe [<options>] [<name of a model file or sql script>]

The following does not work:

C:\Users\tofarmer\Downloads>"C:\Program Files (x86)\MySQL\MySQL Workbench 6.1 CE\MySQLWorkbench.exe" test.sql

This does:

C:\Users\tofarmer\Downloads>"C:\Program Files (x86)\MySQL\MySQL Workbench 6.1 CE\MySQLWorkbench.exe" C:\Users\tofarmer\Downloads\test.sql

How to repeat:
Try to start WB with an argument to a .SQL file which is *not* an absolute path.

Suggested fix:
Add support for relative paths.
[19 Jan 2017 18:39] Christine Cole
Fixed as of the upcoming Workbench 6.3.9 release, and here's the changelog entry:

Starting MySQL Workbench from the command line with an optional argument
of a script or model file required the absolute (or fully qualified) path
name of the file.

Thank you for the bug report.