Bug #61851 transactions fault across connections
Submitted: 13 Jul 2011 8:48 Modified: 13 Jul 2011 13:25
Reporter: Andrew Ramsay Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.34 revision 7780 OS:Windows (XP professional)
Assigned to: CPU Architecture:Any

[13 Jul 2011 8:48] Andrew Ramsay
Description:
When making two connections to the same database initiate a transaction in one connection. attempting to start a transaction in the second connection after a transaction has taken place in the first connection (i.e. even if the transaction in the first connection has committed) causes the "Report a bug" to appear stating:

Mysql Workbench unexpected error.
External component has thrown an exception

How to repeat:
Start Mysql Workbench
open a connection to a database
open a second connection to the same database
in the first connection - START TRANSACTION
in the first connection - do something e.g. select contents of a table
in the first connection - COMMIT
in the second connection - START TRANSACTION    <- this will error

Suggested fix:
each connection made in workbench should act as a separate connection e.g. the same as if one was made using command-line mysql and the other was made using workbench - each has no knowledge of the other.
[13 Jul 2011 11:32] Valeriy Kravchuk
Thank you for the bug report. Verified with version 5.2.34.2 on 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)
[13 Jul 2011 13:25] Alfredo Kojima
This is a duplicate of bug #61791
[13 Jul 2011 13:27] Alfredo Kojima
duplicate of bug #61367