Bug #108694 Supporting the 'source' command in SQL Editor just like on the command line
Submitted: 5 Oct 2022 15:55 Modified: 6 Oct 2022 12:43
Reporter: Tom Corcoran Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[5 Oct 2022 15:55] Tom Corcoran
The standard https://github.com/datacharmer/test_db/blob/master/employees.sql includes:
SELECT 'LOADING departments' as 'INFO';
source load_departments.dump ;

I was informed that "The SQL file is perfectly valid, when used with the MySQL command line shell." https://github.com/datacharmer/test_db/issues/35#issuecomment-1267168373

However, in Workbench, source is underlined in red and gives the error: "source is not valid at this position"

IMHO, the workbench SQL editor and the MySQL command line should support the same coo=mmands. Please, can the SQL editor be updated to support source?

It makes no sense that it does not. Especially with the employee database being advertised through the MySql documentation.

This was discussed over 2 years ago: https://forums.mysql.com/read.php?10,685467,685502 but I am now raising it formerly here.

Please can someone from the team take this on and make the employee database install error free out of the box.

How to repeat:
1. Download the employee sample database from https://github.com/datacharmer/test_db
2. Open employees.sql in the SQL editor and see the red parks under source at the bottom

Suggested fix:
Update the Workbench editor to support the same commands as the MySQl command line.
[6 Oct 2022 12:43] MySQL Verification Team
Hello Tom Corcoran,

Thank you for the bug report.
Imho this is duplicate of Bug #63999, please see Bug #63999.

Ashwini Patil