Bug #44063 | Triggers incorrectly generated when Forward Engineering SQL CREATE Script | ||
---|---|---|---|
Submitted: | 3 Apr 2009 7:03 | Modified: | 31 Jan 2012 7:21 |
Reporter: | Sean Parr | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S2 (Serious) |
Version: | 5.0.30 | OS: | Windows (XP SP2) |
Assigned to: | CPU Architecture: | Any | |
Tags: | forward engineer, trigger, workbench |
[3 Apr 2009 7:03]
Sean Parr
[3 Apr 2009 10:56]
Valeriy Kravchuk
Thank you for the problem report. Did you use the same name for all your triggers? I can't repeat this problem, so can you, please, send .mwb file that demonstrates it?
[3 Apr 2009 16:34]
Sean Parr
You were right. I had the same name for the triggers. I had validated the schema, but Validation does not catch this. There was also no error at the time of creating/saving the trigger, which would have been helpful. Should this bug report be used to identify the validation problem or should a new bug be created?
[3 Apr 2009 17:37]
Valeriy Kravchuk
Yes, it looks like a Validation bug. I'll try to repeat it and will change Synopsis accordingly.
[5 Apr 2009 14:10]
Valeriy Kravchuk
Indeed, WB allows to create triggers on different tables with the same name, and even SE's validations do NOT catch this problem.
[5 Apr 2009 14:12]
Valeriy Kravchuk
Model with two triggers having the same name
Attachment: triggers.mwb (application/octet-stream, text), 4.49 KiB.
[31 Jan 2012 7:21]
Philip Olson
Fixed as of 5.2.38: Workbench now detects duplicated trigger names while using the "Model, Validation (MySQL), Validate all" and "Model, Validation (MySQL), Check integrity" sequences.