Bug #19428 | Reverse ingenering | ||
---|---|---|---|
Submitted: | 28 Apr 2006 18:59 | Modified: | 30 May 2006 1:21 |
Reporter: | Dan Granroth | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench Preview | Severity: | S3 (Non-critical) |
Version: | OS: | 1.0.6 Beta | |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[28 Apr 2006 18:59]
Dan Granroth
[28 Apr 2006 22:47]
MySQL Verification Team
Thank you for the bug report. Which OS version are you using? and could you please provide a project file and attach it here for to test on my side?. Thanks in advance.
[30 Apr 2006 1:21]
MySQL Verification Team
Thank you for the feedback. Sorry I was unable to repeat or I didn't understand you what you meant. Please decribe step by step i.e: which database you selected? Thanks in advance.
[4 May 2006 17:53]
Andy Weston
I had the same problem, not a great first impression. Using the Windows version of workbench, all running locally. Created a brand new schema with a single new table called Products. Went through the reverse engineering screens and a drop database command was created for my schema. It seemed to be confused when it ran into the "information_schema" instead of mine. --Andy
[30 May 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".