| Bug #60779 | Edit Table Data throws unexpected error | ||
|---|---|---|---|
| Submitted: | 6 Apr 2011 12:31 | Modified: | 14 May 2011 10:10 |
| Reporter: | Sebastian Stütz | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Workbench: SQL Editor | Severity: | S2 (Serious) |
| Version: | 5.2.33 CE 7508 | OS: | Windows (7 x64) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | edit table data | ||
[6 Apr 2011 12:31]
Sebastian Stütz
[6 Apr 2011 13:06]
Valeriy Kravchuk
What exact version of server, 5.x.y, are you working with? Can you send complete CREATE TABLE statement for the table you tried to edit?
[6 Apr 2011 13:28]
Sebastian Stütz
I downloaded installed the MySQL Server yesterday. It's the latest package for Windows x64. The Server is running on a separate machine in the local network. Creating new tables in SQL Editor is working fine when using the assistant. However, sending CREATE TABLE in the Query Field fail (same error).
[6 Apr 2011 13:34]
Sebastian Stütz
Problem does not depend on the actual configuration of the table. Even the simplest tables show this error. Furthermore: It seems that this error pops up for all manual code in the Query Field, e.g. "drop table `test_schema`.`new_table`;" did not work. But deleting the table worked when I used the assistant for Dropping the Table afterwards (which used the very same piece of code).
[6 Apr 2011 16:31]
MySQL Verification Team
I couldn't repeat on Vista 64-bit.
[7 Apr 2011 16:49]
Alfredo Kojima
Please repeat the bug and when it happens, right click on the blank area below the icon in the exception window and select Copy Stack Trace, to paste that here.
[8 Apr 2011 7:02]
Sebastian Stütz
For me it's easy to repeat since it happens all the time ;) Thx in advance! Stack Trace: Exception = System.Runtime.InteropServices.SEHException Message = Eine externe Komponente hat eine Ausnahme ausgelöst. FullText = System.Runtime.InteropServices.SEHException (0x80004005): Eine externe Komponente hat eine Ausnahme ausgelöst. bei 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 ) bei MySQL.GUI.Workbench.Db_sql_editor.exec_sql(String sql, Boolean active_editor, Boolean wrap_with_non_std_delimiter) bei MySQL.GUI.Workbench.DbSqlEditor.DoExecuteSqlScript(Boolean currentStatementOnly) bei MySQL.GUI.Workbench.DbSqlEditor.ExecuteSqlScript() bei MySQL.GUI.Workbench.DbSqlEditor.OnPartialRefresh(Int32 what) bei MySQL.Grt.RunWrappedDelegate1<void\,void\,int\,int\,MySQL::Grt::DelegateSlot1<void\,void\,int\,int>::ManagedDelegate>.native_callback(Int32* a1) bei sigc.pointer_functor1<int const &,void>.()(pointer_functor1<int const \&\,void>* , Int32* _A_a1) bei sigc.adaptor_functor<sigc::pointer_functor1<int const &,void> >.operator()<int const &>(adaptor_functor<sigc::pointer_functor1<int const \&\,void> >* , Int32* _A_arg1) bei sigc.internal.slot_call1<sigc::pointer_functor1<int const &,void>,void,int const &>.call_it(slot_rep* rep, Int32* a_1) bei sigc.slot1<void,int const &>.()(slot1<void\,int const \&>* , Int32* _A_a1) bei sigc.adaptor_functor<sigc::slot<void,int const &,sigc::nil,sigc::nil,sigc::nil,sigc::nil,sigc::nil,sigc::nil> >.operator()<int const &>(adaptor_functor<sigc::slot<void\,int const \&\,sigc::nil\,sigc::nil\,sigc::nil\,sigc::nil\,sigc::nil\,sigc::nil> >* , Int32* _A_arg1) bei sigc.internal.slot_call1<sigc::slot<void,int const &,sigc::nil,sigc::nil,sigc::nil,sigc::nil,sigc::nil,sigc::nil>,void,int const >.call_it(slot_rep* rep, Int32* a_1) bei MySQL.Grt.ListModel.activate_popup_item_for_nodes(String name, List`1 nodes) bei MySQL.GUI.Workbench.ModelOverviewForm.PopupActionHandler(Object sender, EventArgs e) bei System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) bei System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e) bei System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) bei System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) bei System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) bei System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met) bei System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) bei System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea) bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) bei System.Windows.Forms.Control.WndProc(Message& m) bei System.Windows.Forms.ScrollableControl.WndProc(Message& m) bei System.Windows.Forms.ToolStrip.WndProc(Message& m) bei System.Windows.Forms.ToolStripDropDown.WndProc(Message& m) bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
[18 Apr 2011 22:42]
MySQL Verification Team
Could you please provide like Valeriy asked before: create table statement and the MySQL Server version. Thanks.
[26 Apr 2011 2:46]
Alfredo Kojima
What's the name of the connection being used? The stack trace looks similar to the one from bug #60700
[26 Apr 2011 7:46]
Sebastian Stütz
Server Version: 5.5.11 Error does not depend on content of CREATE TABLE statement - even simplest tables throw this error when trying to edit them. Connection: Local TCP/IP Network, DB on standard port (3306) ODBC 5.1.8 win x64 is installed (on other machine 32bit, makes no difference) Establishing connection, Database Administration and creation of tables work fine. No Error when editing table data with HeidiSQL.
[27 Apr 2011 17:00]
Valeriy Kravchuk
I have to repeat Alfredo's question: What's the name of the connection being used?
[2 May 2011 10:46]
Sebastian Stütz
[SOLUTION] The connection contained symbol ":". After removing symbol the error vanished...
[14 May 2011 10:11]
Valeriy Kravchuk
So, this must be a duplicate of bug #60700.
