Bug #34927 | Reverse Engineering of Database failed | ||
---|---|---|---|
Submitted: | 28 Feb 2008 14:04 | Modified: | 15 Oct 2009 14:44 |
Reporter: | Chris Oosthuizen | Email Updates: | |
Status: | Unsupported | Impact on me: | |
Category: | MySQL Workbench | Severity: | S2 (Serious) |
Version: | 5.0 | OS: | Windows (XP SP 3) |
Assigned to: | CPU Architecture: | Any | |
Tags: | CHECKED |
[28 Feb 2008 14:04]
Chris Oosthuizen
[28 Feb 2008 14:21]
MySQL Verification Team
Thank you for the bug report. Could you please provide a dump file of the database which failed when doing the reverse engineer?. Thanks in advance.
[28 Feb 2008 16:49]
Sergei Tkachenko
I'm pretty sure it's a duplicate of: Bug #32534: Error in Reverse engineering Bug #32997: Failed to load schemata - reverse engineer database Please check if it applies to your case and either confirm the problem or close the bug.
[28 Feb 2008 17:12]
Chris Oosthuizen
This is not a duplicate or even similar to Bug# 32997. Please refer to the stated system information and MySql version
[28 Feb 2008 19:46]
Sergei Tkachenko
Deployed schema using provided script on clean installation of MySql Server Version 6.0.3-alpha-community. Failed to reproduce. Tables, vies, routines, triggers where fetched without errors and whole schema was successfully rev-enged. Did you update server from previous version?
[28 Feb 2008 19:57]
Chris Oosthuizen
Screenshot of error
Attachment: rev_eng_error.doc (application/msword, text), 98.00 KiB.
[28 Feb 2008 19:59]
Chris Oosthuizen
I just performed a clean install of MySql Server 6.0.3-alpha-community. The problem still appeares as originally reported
[28 Feb 2008 20:05]
Sergei Tkachenko
Did you update server from previous version?
[28 Feb 2008 20:08]
Sergei Tkachenko
Did you recreate DB data also?
[28 Feb 2008 20:11]
Chris Oosthuizen
No, I did not update it from previous version. I uninstalled version 5.1, then installed 6.0.3. Also, I noticed in the script I sent you (generated by mysqldump), that the trigger on lookupdataset table is commented out. When I the script I sent you, then reverse engineer, it works. The problem seem to be that Workbench fails when reverse engineering trigger (and stored procedures?)
[28 Feb 2008 20:18]
Sergei Tkachenko
Deployed schema that I tried does contain that trigger from your script. Please try to execute 'mysql_system_tables_fix.sql' script against your DBMS with root privileges as described in solution for Bug #32534. That script is located in 'share' subdir of your MySQL DBMS installation dir.
[28 Feb 2008 20:41]
Chris Oosthuizen
Just performed the suggested fix by running 'mysql_system_tables_fix.sql' script against my DBMS with root privileges. Workbench still behaves the same way - i.e. produces error
[28 Feb 2008 20:45]
Sergei Tkachenko
ok. can you see results of queries like: select * from information_schema.routines; select * from information_schema.triggers;
[28 Feb 2008 20:57]
Chris Oosthuizen
When I perform the 'select * from information_schema.routines;' query, it returns all the stored procedure and functions. When I perform the select * from information_schema.triggers;' query, I get the one that is defined on the lookupdataset table
[28 Feb 2008 21:30]
Sergei Tkachenko
Thanks for your time. I managed to repeat it. Seems that DBMS client lib will need update to work with Falcon. Putting this issue in todo list, but note, officially we support server of 5.0 and 5.1 brunches for now.
[29 Feb 2008 6:07]
Valeriy Kravchuk
Looks like we can consider this bug as "Verified" based on recent comments.
[19 Feb 2009 14:12]
Susanne Ebrecht
This needs re-verifying when Workbench 5.1 for Windows is out.
[2 Apr 2009 8:43]
Susanne Ebrecht
Still in 5.1 because the effort to fixing this is very huge. MySQL 6.0 still is alpha. As long as it is not RC there is none hurry to fix this.
[15 Oct 2009 14:44]
Susanne Ebrecht
MySQL server version 6.0 project is canceled. So there is no need for Workbench to support this server version. Our QA will test Workbench anyway with new outcomming servers as soon as they will get RC.