Bug #35263 validation violation should be instantaniously reported/corrected
Submitted: 13 Mar 2008 10:26 Modified: 30 May 2013 11:34
Reporter: Gert van de Venis Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.0.15 RC OS:Any
Assigned to: CPU Architecture:Any
Tags: OSS, validation violation

[13 Mar 2008 10:26] Gert van de Venis
Description:
Error checking/preventing/correction of the model should be done while creating entities that violate the validation rules. This prevents confusion and failing export scripts to be generated. 

How to repeat:
A few examples:
- When i create a new column in a table i can easily click away after providing a name for the column, without being warned about the fact that i didn't provide a type for it. 
- I can easily create two or more fk_names without being warned i may have accidentally violated the "no double identifiers" rule!
- I can define column and fk_names that are longer than the maximum allowed length of 64 bytes (if i recall right).

Suggested fix:
Provide error checking/correction possibility when creating columns and relations that violate validation.
[13 Mar 2008 12:09] MySQL Verification Team
Thank you for the bug report.
[19 Mar 2008 8:43] Gert van de Venis
Not solved yet in the RC
[30 May 2013 11:34] Mike Lischke
Forcing people into a certain workflow is not a good idea. Validation must be done at a later time when things have settled down, not during the heavy change phase.