Bug #60977 Executing a sql script via "Workbench Scripting Shell" fails

• Submitted: 26 Apr 2011 9:21
• Modified: 20 Jun 2011 19:08
• Reporter: Hans-Joachim Ballin
• Status: Closed
• Category: MySQL Workbench: SQL Editor
• Severity: S3 (Non-critical)
• Version: 5.2.33b
• OS: Windows (7 - 64bit, XP 32-bit)
• CPU Architecture: Any
• Tags: Workbench Scripting Shell Open Script

[26 Apr 2011 9:21] Hans-Joachim Ballin

Description:
Executing a sql script via "Workbench Scripting Shell" creates a "bug report message".

How to repeat:
- Open "MySQL Workbench 5.2 CE"
- Open "Workbench Scripting Shell" by using the following menu steps "Scripting" -> "Open Script..."
- Load a SQL script.
- Select "Execute script" command from menu bar (on top)
- BINGO, the execution ends in a bug report immediately.

Suggested fix:
n/a
- Using SQL Editor instead will bypass the problem.

[26 Apr 2011 9:40] Valeriy Kravchuk

Thank you for the bug report. Verified on 32-bit Windows XP also. 

Stack trace is:

Exception = System.Runtime.InteropServices.SEHException
Message = External component has thrown an exception.
FullText = System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
   at MySQL.Forms.ButtonImpl.button_click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[26 Apr 2011 15:05] Alfredo Kojima

The scripting shell is not meant to be used for executing SQL scripts, you must – as you found out – use the SQL Editor for that. The scripting shell is for Workbench scripts, in Lua or Python. However the crash is a bug and must be fixed.

[27 Apr 2011 17:05] Valeriy Kravchuk

Bug #60477 was marked as a duplicate of this one.

[20 Jun 2011 19:08] Paul DuBois

Noted in 5.2.34 changelog.

Executing an SQL script using the scripting shell is not supported,
but attempts to do so resulted in a Workbench crash rather than an
error.