Description:
When creating new schemas I like to bash out the SQL into a file and then use that file to create a model. I find writing the bones of a script much faster than creating each entity in a model one by one. I can then go ahead and make any tweaks/changes in the model.
However, I sometimes find I have made a mistake in my SQL script, and I don't find out about it after MySQL Workbench has imported a bunch of models. If there were errors, Workbench carries on as best it can and produces a broken model.
Suffice it to say, I don't relish unpicking problems/inconsistencies in my model due to a typo or omission in my SQL script.
If MySQL Workbench had an ability to validate a script to check there are no errors in syntax before creating a possibly broken model, it would save me a bunch of time. It would be handy feature in general, not just for the modelling component.
How to repeat:
Create a new ERD model from an SQL file that has syntax errors.
Suggested fix:
Syntax validation before going ahead and creating the model.
