Bug #50002 'default schema' is not respected when reverse-engineering
Submitted: 30 Dec 2009 17:12 Modified: 10 Jan 2013 22:26
Reporter: Walter Stanish Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.11 OSS Beta 4842 OS:Windows
Assigned to: CPU Architecture:Any
Tags: DEFAULT, schema, schemata, UI

[30 Dec 2009 17:12] Walter Stanish
When reverse engineering a database, the schema is not selected automatically even if you specify a default schema in the dialog box.

How to repeat:
 - Start MySQL
 - New model
 - Reverse engineer
 - Enter details, including 'default schema'
 - Proceed
 - When the list of databases/schema appear, the previously specified schema is not pre-selected (arguably, this screen should not appear at all)

Suggested fix:
Pre-select the default schema on the 'Select the Schemata to Reverse Engineer' step of the popup dialog.
[5 Jan 2010 10:32] Valeriy Kravchuk
It is by design that default schema is not taken into account for reverse-engineering or syncronization. Anyway, this sounds like a reasonable feature request to consider.
[7 Jan 2010 12:11] Johannes Taxacher
right, we'd remove he field in the wizards/dialogs where its not used
[10 Jan 2013 22:26] Philip Olson
Fixed as of the upcoming MySQL Workbench 5.2.46 release, and here's the changelog entry:

 The "Default Schema" setting was ignored by the "Reverse Engineer
 Database" wizard.

Thank you for the bug report.