Bug #105387 | work bench crashes when trying to create a new model | ||
---|---|---|---|
Submitted: | 29 Oct 2021 14:52 | Modified: | 11 Nov 2021 18:58 |
Reporter: | mark edwards | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S2 (Serious) |
Version: | 8.0.27 | OS: | Windows (Microsoft Windows 10 Home) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[29 Oct 2021 14:52]
mark edwards
[29 Oct 2021 19:47]
MySQL Verification Team
Thank you for the bug report. I couldn't repeat this issue, please attach screenshots of step by step to repeat the issue (use the tab Files to attach the screenshots files).
[29 Oct 2021 23:50]
mark edwards
step one
Attachment: error-1.png (image/png, text), 255.06 KiB.
[29 Oct 2021 23:51]
mark edwards
step two
Attachment: error-2.png (image/png, text), 157.33 KiB.
[29 Oct 2021 23:51]
mark edwards
step three
Attachment: error-3.png (image/png, text), 212.35 KiB.
[31 Oct 2021 14:30]
mark edwards
ER Builder seems to be a good drop-in replacement for the Workbench modeling tool.
[31 Oct 2021 14:31]
mark edwards
https://soft-builder.com/erbuilder-data-modeler/
[2 Nov 2021 8:37]
MySQL Verification Team
Hello mark edwards, Thank you for the feedback and details. I tried to reproduce your issue on windows 10 with workbench 8.0.27 and followed exact steps but I am not seeing any issues at my end. Regards, Ashwini Patil
[2 Nov 2021 16:22]
mark edwards
ok i see four options: 1) you send me a special mysql-workbench "debug" version that captures a lot more errors 2) you screen-share with me & i demonstrate the problem 3) i send you the results of mysqldump (minus the data) & you try it 4) we forget the whole thing and i use that er-model tool. fwiw, this has now happened on a couple different computers.
[11 Nov 2021 17:42]
mark edwards
no replies - so i am going to assume this will not be fixed anytime soon. fwiw, i tried to reload the db WITHOUT any data, then DROPPED each table individually, yet even with an empty DB (no data no tables) it still happened. so my idea of uploading up a mysqldump file proving the problem is obviously not going to work. and removing/reinstall did not help either. this all started when workbench started enforcing the SSL rule.
[11 Nov 2021 17:51]
mark edwards
i still think the workbench developers should send me some sort of special diagnostic version that has more comprehensive error trapping.
[11 Nov 2021 18:58]
mark edwards
ok i figured out what i was doing wrong - i was selecting Database-->connectToDatabase rather than Database-->reverseEngineer. HOWEVER, it still seems odd that this would crash workbench.