| Bug #32809 | File-->Import-->Reverse Engene... ignores selected schema in Physical Schema | ||
|---|---|---|---|
| Submitted: | 28 Nov 2007 11:08 | Modified: | 10 Jan 2008 18:11 |
| Reporter: | Heinz Schweitzer (Gold Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
| Version: | 5.0.9 | OS: | Windows (XP SP2) |
| Assigned to: | Sergei Tkachenko | CPU Architecture: | Any |
| Tags: | qc | ||
[28 Nov 2007 21:03]
Valeriy Kravchuk
Thank you for a bug report. Verified just as described.
[17 Dec 2007 10:20]
Michael G. Zinner
We are looking into adding a catalog.currentSchema and let it respond to the current schema tab selected on the model overview page. All plugins would then operate on this schema if no explicit schema is defined.
[10 Jan 2008 18:11]
Sergei Tkachenko
Import plugin was changed to take into account selected schema. Note: selected schema will be used only for statements without explicitly specified schema & only until first 'use schema' statement, which will change active schema for subsequent statements from the script. Changes will go into v5.0.12.
Description: File-->Import-->Reverse Engeneering... ignores selected schema in Physical Schema WorkBench: 5.0.9 OSS (software Rendering) OS: Windows XP Hardware: Intel(R) Pentium(R) M processor 1600MHz, 512 MB RAM How to repeat: You need a MYSQL create script. Start empty WorkBench 5.0.9 OSS (software Rendering) In the 'Physical Schemta' pane create a new schema using the '+' sign at the right side. tab with labe 'new_schema1' is created. Select this tab. Form the windows menue now do File-->Import-->Reverse Engeneering from MYSQL create script Select a script and say open. ---> the import ends up in the very first schema ('mydb') at the left side. The expected result would be to import the create script into the selected schema (new_schema1)