Bug #50428 Separated Export for Multiple Schemas
Submitted: 18 Jan 2010 22:48 Modified: 20 Jan 2010 3:05
Reporter: Javier Ortiz Email Updates:
Status: Verified Impact on me:
Category:MySQL Workbench Severity:S4 (Feature request)
Version:5.2.11 beta OS:Any
Assigned to: CPU Architecture:Any

[18 Jan 2010 22:48] Javier Ortiz
Having multiple schems defined in the same file is really cool but it gets annoying to export separate squemas to different files. First the wizard only provides for remebering one output file. That's OK, but sometimes you want to keep the sql for each schema separated. If you select drop schema option it'll output statements to clear all schemas (even if you only export tables from one schema)

How to repeat:
Have a project with multiple schemas. Try to export one.

Suggested fix:
Provide a checkbox list of available schemas (selected all by default) to export. Provide SQL Export options for each (unless a checkbox to use same options for all is selected).

Each Schema should have its own set of properties and remeber those values (like the current implementation does but only for one group of settings)
[19 Jan 2010 11:58] Johannes Taxacher
thanks for this request. Using our filter page its currently only possible to filter out objects inside schemas (by using wildcards its working well to exclude all objects of a certaing schema) but not schemas themselves. Thats why the option "drop schema objects" always generates drop statements for all schemas contained in the model.
[19 Jan 2010 11:59] Johannes Taxacher
current workaround would be to delete the offending DROP SCHEMA statements before advancing to he "execute" step in export wizard
[20 Jan 2010 3:05] Javier Ortiz
That's what I did but I think that the export tool is not as flexible as the rest of thetool.