Bug #37687 Trigger changes in the database are not detected on synchronization

• Submitted: 27 Jun 2008 7:48
• Modified: 3 Aug 2008 16:14
• Reporter: Jan Juricek
• Status: No Feedback
• Category: MySQL Workbench
• Severity: S3 (Non-critical)
• Version: 5.0.23
• OS: Windows
• CPU Architecture: Any
• Tags: synchronization, trigger

[27 Jun 2008 7:48] Jan Juricek

Description:
If I add, delete or change a trigger via mysql command line and then try to synchronize database state with my workbench model, no changes of triggers are detected and existing triggers in the database are not transfered to the model.

I hope this is not planned behavior.

How to repeat:
- Synchronize your model with the database
- Add a trigger to some table
- Try to synchronize -> no trigger changes found

[27 Jun 2008 7:50] Jan Juricek

I'm sorry I forgot to fill in the Version field. Version of the Workbench is 5.0.23

[27 Jun 2008 13:54] MySQL Verification Team

Thank you for the bug report.

[3 Jul 2008 16:14] Johannes Taxacher

Jan,

would it be possible to provide a script/WB-file which shows that behaviour?
when i add a trigger to a table on database side and then synch the model WB correctly recognizes this and (per default) adds a drop statement (if I change the sync direction the trigger is added to the model).
does the added trigger show up on the filter page of the wizard?

thx

[3 Aug 2008 23:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".