MySQL Bugs: #60750: Unexpected error when executing query on a connection that's opened twice

Bug #60750	Unexpected error when executing query on a connection that's opened twice
Submitted:	4 Apr 2011 9:04	Modified:	7 May 2011 16:20
Reporter:	R B	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.33b CE	OS:	Windows (W7 x64, XP 32-bit)
Assigned to:		CPU Architecture:	Any

Description:
Unexpected error when executing query on a connection that's opened twice

How to repeat:
On the home screen. I've multiple UNIQUE connections to different hosts and databases; NO default schema set.

1. I open up connection named e.g. DB_SERVER.
2. Select the schema by double-clicking on the schema.
3. execute a query on any table
4. Go to the home screen.
5. Open up connection as mentioned in step 1. In my example DB_Server.
6. You see the last executed query.
7. You close that most top tab named SQL Editor (DB_Server) that tab is created in step 5.
8. Go to the top most tab created in step 1.
9. Excute a query.
10. Unexpected error occured

Suggested fix:
Open the existing top most tab of that connection and add a new Query tab

Verified just as decribed on 32-bit Windows XP. 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 Db_sql_editor.exec_sql(Db_sql_editor* , basic_string<char\,std::char_traits<char>\,std::allocator<char> >* , shared_ptr<Sql_editor>* , Boolean , Boolean , Boolean )
   at MySQL.GUI.Workbench.Db_sql_editor.exec_sql(String sql, Boolean active_editor, Boolean wrap_with_non_std_delimiter)
   at MySQL.GUI.Workbench.DbSqlEditor.DoExecuteSqlScript(Boolean currentStatementOnly)
   at MySQL.GUI.Workbench.DbSqlEditor.ExecuteSqlScript()
   at MySQL.Grt.RunWrappedDelegate0<void\,void\,MySQL::Grt::DelegateSlot0<void\,void>::ManagedDelegate>.native_callback()
   at sigc.pointer_functor0<void>.()(pointer_functor0<void>* )
   at sigc.adaptor_functor<sigc::pointer_functor0<void> >.()(adaptor_functor<sigc::pointer_functor0<void> >* )
   at sigc.internal.slot_call0<sigc::pointer_functor0<void>,void>.call_it(slot_rep* rep)
   at mforms.ToolBarItem.callback(ToolBarItem* )
   at MySQL.Forms.ToolBarItemImpl.OnItemActivation(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.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)

marked bug #60763 as duplicate

marked bug #60631 as a duplicate

Wouldn't this be a duplicate of #60631 rather than the other way around?

Glenn, technically you're right, but sometimes it happens that a bug is handled out of order of reporting, in which case the older one ends up being marked as a duplicate of a newer. It's nothing personal :)

Noted in 5.2.34 changelog.

Opening a connection twice resulted in unexpected errors when executing 
queries on the connection.

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

Bug: http://bugs.mysql.com/bug.php?id=61996 marked as duplicate of this one.

Ok. everybody marked it as duplicate. So far so good. Is there anyone working on a solution / patch for this?

Did you try the latest version?