Bug #50139 | Deletion of a MysqlModel deletes also the tables in a diagram | ||
---|---|---|---|
Submitted: | 7 Jan 2010 14:34 | Modified: | 21 May 2010 21:26 |
Reporter: | Petronel Laviniu Malutan | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
Version: | 5.2 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | delete MysqlModel |
[7 Jan 2010 14:34]
Petronel Laviniu Malutan
[8 Jan 2010 11:56]
Susanne Ebrecht
Verified as described.
[21 Apr 2010 21:26]
Alfredo Kojima
I am not sure I understand the issue. If I create 2 diagrams, copy objects from the 1st to the 2nd and delete the 1st, the objects in the 2nd diagram remain intact. If by "deleting model" you mean you are deleting the original Schema/Database, then that is the expected behaviour, since the objects you've pasted into the 2nd diagram are probably in the original Schema as well. Diagrams are just graphical representations of your database objects, if you delete the database objects themselves, they will be gone from the model. What you want to do is to cut/paste the objects from the imported Schema into the other schema. You can do that by selecting the object, Cut them and then go to the other Schema and Paste them. On a separate note, apparently this is a common operation, so I'll file a feature request for directly moving selected database objects into another schema.
[21 May 2010 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".