Bug #22399 fails to reverse engineer schema
| Submitted: | 15 Sep 2006 17:28 | Modified: | 18 Oct 2006 14:21 |
|---|---|---|---|
| Reporter: | Ariel Glenn | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Workbench Preview | Severity: | S2 (Serious) |
| Version: | 5.0r3 | OS: | Linux (Fedora Core 5) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
[15 Sep 2006 17:28]
Ariel Glenn
[18 Sep 2006 14:21]
MySQL Verification Team
Thank you for the bug report. I was unable to repeat on Suse 10.0/Fedora Core 5. Could you please provide a dump sample of the schema you tried? Thanks in advance.
[14 Oct 2006 17:29]
fx pottier
Hi there, same for me : Error calling ReverseEngineeringMysql.reverseEngineer: Could not get routines when i try to reverse a schema (i did try different ones => same result). My system : Fedora Core 5
[14 Oct 2006 17:32]
fx pottier
sorry i forgot to mention the package : mysql-workbench-5.0r4-1fc5
[18 Oct 2006 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".
[3 Feb 2007 10:09]
Alec de Zegher
Hi, I have exact the same problem on MacOSX 10.4 (Tiger) and Workbench 1.29a. 1) Connection: 10.0.0.2 with correct username and password 2) Selecting a database 3 Error Error log: Fetching schemata... Schemata fetched. Reverse engineering schema...Error calling ReverseEngineeringMysql.reverseEngineer: Could not get routines.The schema(ta) could not be reverse engineered (error: 0) Could not get routines. (SHOW PROCEDURE STATUS; MySQL Error 1146: Table 'mysql.proc' doesn't exist)
[3 Feb 2007 10:30]
Alec de Zegher
I found the error: I did a bad upgrade from 4.1 to 5.0 (mysql.proc is apperently a new file created in MySQL 5.0) This post helped me: http://bugs.mysql.com/bug.php?id=24271
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.055 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.