MySQL Bugs: #39479: Model Validation issues

Bug #39479	Model Validation issues
Submitted:	16 Sep 2008 14:20	Modified:	20 Oct 2009 11:14
Reporter:	Roland Bouman	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.0.25	OS:	Any
Assigned to:	Johannes Taxacher	CPU Architecture:	Any
Tags:	CHECKED

Description:
A couple of issues with the way model validation is implemented in workbench

1) The validation plugins cannot be configured. By default they are extremely picky - they often generate warnings that I feel are unwarranted. I can give a list, but the point is this: The user has no way of telling the plugin

- which sub functions should be tested at all
- how severe a failure to validate is considered by the user

2) The output of validation is lacking. I cannot sort on severity, nor can I sort or group by object type and/or name. I do have a "Time" column which does not seem to serve any purpose (other than debugging plugins). Another thing that is missing is the resolution. Many errors have a simple resolution such as:

"FK has inconsistent type" (solution: make the type in the fk table match that of the referenced table) or "Invalid default value NULL" (remove the default value declaration)

3) The output is just that - output. I would like to dbl click a validation output item and end up in an editor that allows me to fix the issue.

4) It seems like a great feature if the user can create a new validation method by selecting a bunch of predefined ones, as well as custom plugins. Even if you can do this in a plugin, think of all they guys and galls that don't feel the urge to hack lua. A GUI to drag existing plugins into a sequence doesn't seem that hard to offer?

5) When validate sakila.film (from the sakila sample database) it complains that "G" is not a valid value for "rating". However, it is. I suspect that the enum validation has a bug.

How to repeat:
see desc

Suggested fix:
see desc

Thank you for the bug report.

To clarify the "resolution": In many cases, there are simple fixes that can at least be suggested, and if it is really clear cut, maybe the issue can offer buttons so th user can click them to actually fix the issue

Hello Roland,

after re-re-re-view this I saw that we never answered you.

These are too much wishes in a single bug report. We will discuss your wishes and will split them.

Many thanks for writing a feature request.

After long discussion we decided that we won't change this behaviour in foreseeable future.

Thank you for your interests in MySQL Workbench.

P.S.: Some of your wishes are already implemented.