Bug #62259 | executing 800 select statements from the sql editor window of MySQL Workbench | ||
---|---|---|---|
Submitted: | 25 Aug 2011 12:32 | Modified: | 4 Nov 2014 3:40 |
Reporter: | Michael Vitale | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 5.2.34 | OS: | Windows (windows 7 64 bit) |
Assigned to: | CPU Architecture: | Any |
[25 Aug 2011 12:32]
Michael Vitale
[25 Aug 2011 12:54]
Alfredo Kojima
Hi Since displaying 800 select resultsets at once is not practical and resource exhaustive, as you noticed, what would be the expected or desired outcome of such operation, in your opinion?
[25 Aug 2011 23:43]
Michael Vitale
Let the user determine what is practical by placing a new parameter in the SQL Editor preferences that limits SQL statements to a certain value. Otherwise, let the user's computer bear the brunt of CPU and/or memory consumption, and not try to make Workbench control the user's intentions.
[26 Aug 2011 7:08]
Valeriy Kravchuk
I've got no problems running 1440+ simple (select 1) queries on this old XP: MySQL Workbench CE for Windows version 5.2.34 Configuration Directory: C:\Documents and Settings\Satellite\Application Data\MySQL\Workbench Data Directory: C:\Program Files\MySQL\MySQL Workbench 5.2 CE Cairo Version: 1.8.8 Rendering Mode: OpenGL is not available on this system, so GDI is used for rendering. OS: Microsoft Windows XP Home Edition Service Pack 3 (build 2600) CPU: Intel(R) Pentium(R) M processor 1.86GHz, 1.0 GiB RAM Active video adapter: Mobile Intel(R) 915GM/GMS,910GML Express Chipset Family Installed video RAM: 128 MB Current video mode: 1280 x 768 x 4294967296 colors Used bit depth: 32 Driver version: 6.14.10.3943 Installed display drivers: ialmrnt5.dll Current user language: Ukrainian so, this may have something to do with newer Windows versions or non-administrator accounts. Anyway, I think the request to have an option to limit number of output tabs created (to prevent resource-related problems) is reasonable.
[5 Sep 2011 17:18]
Armando Lopez Valencia
Confirmed on Windows7x64.
[5 Sep 2011 17:19]
Armando Lopez Valencia
Stack Trace: Exception = System.ComponentModel.Win32Exception Message = Error creating window handle. FullText = System.ComponentModel.Win32Exception (0x80004005): Error creating window handle. at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp) at System.Windows.Forms.Control.CreateHandle() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.OnVisibleChanged(EventArgs e) at System.Windows.Forms.ButtonBase.OnVisibleChanged(EventArgs e) at System.Windows.Forms.Control.OnParentVisibleChanged(EventArgs e) at System.Windows.Forms.Control.OnVisibleChanged(EventArgs e) at System.Windows.Forms.ScrollableControl.OnVisibleChanged(EventArgs e) at System.Windows.Forms.Form.OnVisibleChanged(EventArgs e) at System.Windows.Forms.Control.SetVisibleCore(Boolean value) at System.Windows.Forms.Form.SetVisibleCore(Boolean value) at System.Windows.Forms.Control.set_Visible(Boolean value) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.RunDialog(Form form) at System.Windows.Forms.Form.ShowDialog(IWin32Window owner) at System.Windows.Forms.Form.ShowDialog() at MySQL.GUI.Workbench.ExceptionDialog.Show(String message, String info) at MySQL.GUI.Workbench.Program.HandleException(Object o) at MySQL.GUI.Workbench.Program.OnGuiUnhandledException(Object sender, ThreadExceptionEventArgs e) at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t) at System.Windows.Forms.Timer.TimerNativeWindow.OnThreadException(Exception e) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg) at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.Run(ApplicationContext context) at MySQL.GUI.Workbench.Program.Main(String[] Args)
[31 Oct 2014 21:07]
Johannes Taxacher
Posted by developer: new preference setting working as described. fix confirmed in 6.2.4.12419