Bug #61786 Use Default schema not being set when forward engineering

• Submitted: 7 Jul 2011 16:42
• Modified: 4 Sep 2012 7:56
• Reporter: Reinaldo Novoa
• Status: Closed
• Category: MySQL Workbench: Modeling
• Severity: S3 (Non-critical)
• Version: 5.2.31, 5.2.34
• OS: MacOS (snow lepoard)
• CPU Architecture: Any
• Tags: default schema, forward egineering

[7 Jul 2011 16:42] Reinaldo Novoa

Description:
Use default schema when set in the Manage connections is not respectedleading to no DB being used for the commands of forward engineering.

How to repeat:
Manage connections and set a default schema
forward engineer from your model
omit schema qualifiers
continue till errors are received

note username and pass nust be able to administer multiple DBs
Default DB for use in Manage connections is then lost and has to be reset

Suggested fix:
Include the default schema field in the connection when forward engineering.

[7 Jul 2011 16:48] Valeriy Kravchuk

Please, check if the same problem still happens with recent version, 5.2.34.

[7 Jul 2011 17:02] Reinaldo Novoa

Same error in 5.2.34 rev7780

Executing SQL script in server
ERROR: Error 1046: No database selected

[9 Jul 2011 16:57] Valeriy Kravchuk

Verified just as described on Mac OS X 10.5.x. Default schema is not taken into account.

[4 Sep 2012 7:56] Philip Olson

Fixed as of the upcoming 5.2.43, and here's the changelog entry:

 The "Forward Engineering" wizard did not utilize the "Use Default Schema" 
 setting that is set in the "Manage Connections" configuration table.

Thank you for the report.