Bug #62695 | Running a simple database create script, MySQL Workbench had Unexpected Error | ||
---|---|---|---|
Submitted: | 12 Oct 2011 9:22 | Modified: | 14 Nov 2011 7:04 |
Reporter: | Paul Warner | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 5.2.35 CE Revision 7915 | OS: | Windows (Windows 7 Home Premium) |
Assigned to: | CPU Architecture: | Any |
[12 Oct 2011 9:22]
Paul Warner
[12 Oct 2011 11:45]
Valeriy Kravchuk
Please, check if the same problem happens with a newer version, 5.2.35.
[13 Oct 2011 10:38]
Paul Warner
Ok, more details, now with the latest version of the Workbench (5.2.35 CE Revision 7915): 1. Open the workbench, log in to a local mysql instance, set one database as the default schema. 2. Select 'Scripting' at the top, select 'Open script'. A Windows Explorer instance opens to my folder, I doubleclick my .sql file. 3. A popup opens with the message: "Unsupported Execution This script editor is meant for developing Workbench plugins and scripts. SQL scripts should be opened and executed in the SQL Editor." I click ok. Then, the first time I tested this with this latest version of the workbench, the workbench crashed and exited. I just tried it again, and got only the informative message, but the application did not crash. I don't *think* I did anything different the second time...??? But now I know I did the wrong thing! :-)
[13 Oct 2011 10:43]
Valeriy Kravchuk
Hm, I can not get the crash opening arbitrary .sql files this with 5.2.35 on 32-bit Windows XP. Just informative error message.
[13 Oct 2011 11:59]
Alfredo Kojima
How big is the script you're trying to run?
[15 Nov 2011 7: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".