Bug #43276 Schemata qualifiers always generated for Stored Procedures
Submitted: 28 Feb 13:56 Modified: 12 Nov 12:54
Reporter: Petr Vones
Status: Closed
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.0.30 OS:Microsoft Windows (Windows Server 2003 Std)
Assigned to: Alexander Musienko Target Version:WB52
Tags: TTREV, PROCEDURE, schema qualifier
Triage: Triaged: D3 (Medium) / R2 (Low) / E2 (Low)

[28 Feb 13:56] Petr Vones
Description:
Forward Engineer to SQL Script function always generates schema qualifier for Stored
Procedure names regardless of "Omit schemata qualifiers from output" checkbox is checked
or not. 

Note: it works correctly for table names

How to repeat:
1. Create new Routine with default name "routine1"

DELIMITER //

CREATE PROCEDURE `mydb`.`routine1` ()
BEGIN
  SELECT * FROM MyTable
END//

2. File | Export | Forward Engineer to SQL Script
3. Check "Omit schemata qualifiers from output" option in the dialog
4. Enter an output file Name
5. Next
6. Finish

Expected: The procedure name is generated without "mydb" schema prefix in resulted SQL
script file.

Actual: The procedure name has "mydb" schema prefix in resulted SQL script file.
[1 Mar 3:15] Miguel Solorzano
Thank you for bug report. Related to the bug report:
http://bugs.mysql.com/bug.php?id=43058
[11 Nov 22:24] Johannes Taxacher
fixed in sourcecode. fix will be included in 5.2.7
[12 Nov 12:54] Tony Bedford
An entry was added to the 5.2.7 changelog:

Forward Engineer SQL CREATE Script generated schema qualifiers for Stored Procedure names
regardless of the setting of the Omit schemata qualifiers from output checkbox. This
resulted in the generated script containing Stored Procedure names prefixed by the schema
name.