MySQL Bugs: #57007: create new table bogus when having more than one physical schemata

Bug #57007	create new table bogus when having more than one physical schemata
Submitted:	24 Sep 2010 14:40	Modified:	27 Sep 2010 7:53
Reporter:	Markus Warg	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	5.2.20 / 5.2.28	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	annoying

Description:
I usually open up an EER and start adding tables to that EER when I have work to do.

Now, having more than one physical schemata in one workbench file, you have a big problem: you do not see at first glance, to which physical schemata the table was added.

Usually having one EER per physical schemata, I expect that new tables in EER1 go to schemata 1.

How to repeat:
Create new workbench file, create two schemata, create two EER diagrams.

Open EER1, add table, open EER2, add table.

You now have one table in each EER, BUT both tables were created in one schemata. There is no easy way to move the tables from one to the other schemata (you can cut&paste in the physical schemata view, but that renders relations useless).

Suggested fix:
It would be very helpful just to SEE to which schemata a table will be added, it would be even better if you could select a schemata in EER view / catalog tree. Add new table then creates the table in the selected schemata.

Right now the only way to go is close EER, select schemata, add table to schemata, open EER and drag tables from catalog to diagram.

Hi Markus,

when you select the table-tool on the canvas, 4 additional dropdowns appear in the main toolbar which show (and let you select) schema, engine, collation and figure-color.
is this what you've been looking for?

Oops, yes. Seems I need to apologize for beeing snowblind on that.