| Bug #52939 | synchronize model with Database (triggers) | ||
|---|---|---|---|
| Submitted: | 19 Apr 2010 10:34 | Modified: | 10 May 2010 10:49 |
| Reporter: | R B | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench: Modeling | Severity: | S2 (Serious) |
| Version: | 5.2.19 | OS: | Windows (Vista Enterprise 64bit) |
| Assigned to: | Alexander Musienko | CPU Architecture: | Any |
[19 Apr 2010 13:20]
MySQL Verification Team
Please attach you model file using private mode then only MySQL developer will have access. Thanks in advance.
[19 Apr 2010 14:55]
R B
After the fault I also added a trigger manually! I think then this error occurs while merging the model with the database
[19 Apr 2010 16:15]
MySQL Verification Team
Thank you for the feedback. Verified as described.
[7 May 2010 15:38]
Johannes Taxacher
fix confirmed in repository
[10 May 2010 10:49]
Tony Bedford
An entry has been added to the 5.2.21 changelog: Synchronize to live database failed when the model contained triggers.
Description: I use triggers -- Trigger DDL Statements DELIMITER $$ USE `acintegrate`$$CREATE TRIGGER update_lastedited_company AFTER UPDATE ON `Company` FOR EACH ROW CALL UpdateLastEditedContactinformation(NEW.CompanyId)$$ At the Synchronize Progress part it fails halfway "Apply changes to database" is checked and then the workbench throws a popup error without any message about the cause. The Synchronize Progress form is still visible and in the 'Show Logs' the message is Executing SQL script in server SQL script execution finished: statements: 13 succeeded, 0 failed The trigger calls a routine which is also created from the model. The triggers are not added to the database. Synchronizing worked before I added the triggers. But in the 'Review DB Changes' part there's nothing to be seen in the SQL about triggers. I created the model in 5.2.16 and there I got the error which was listed at http://docs.sun.com/source/mysql-workbench/wb-change-history.html at bug http://bugs.mysql.com/bug.php?id=51467 therefore I upgraded to the latest version 5.2.19 and then the above appeared. How to repeat: I don't know Suggested fix: I don't know