Bug #83605 | Clicking the "i" (information) icon on a partitioned table results in an error | ||
---|---|---|---|
Submitted: | 28 Oct 2016 17:57 | Modified: | 7 Jun 2018 19:15 |
Reporter: | Heiko Ebens | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 6.3.8 | OS: | Windows (Windows Server 2012 R2) |
Assigned to: | CPU Architecture: | Any |
[28 Oct 2016 17:57]
Heiko Ebens
[28 Oct 2016 22:39]
MySQL Verification Team
Error dialog
Attachment: error_bug#83605.png (image/png, text), 160.45 KiB.
[28 Oct 2016 22:40]
MySQL Verification Team
Thank you for the bug report.
[5 May 2017 18:32]
John Mirsberger
In the Navigator pane under SCHEMAS, right clicking and then choosing "Table Inspector" on a partitioned table, I get the following error alert message: Unhandled exception: in method 'TreeNodeRef_set_int', argument 3 of type 'int' The wb.log error is the same as initial bug reporter's. Also, clicking the 'i' gives me the same "error calling Python module function SQLIDEUtils.showInspector" error alert message. I am using MySQL Workbench 6.3.9 build 10690321 CE (64 bit).
[2 May 2018 20:35]
Mark Anderson
This bug still using workbench 6.3.9 and SQL Server 5.7.18 (win64) Log File Below - 14:30:48 [ERR][ python]: error calling SQLIDEUtils.showInspectorTraceback (most recent call last): 14:30:48 [ERR][ python]: File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE\modules\sqlide_grt.py", line 607, in showInspector 14:30:48 [ERR][ python]: show_table_inspector(editor, table_insp) 14:30:48 [ERR][ python]: File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE\modules\sqlide_tableman_ext.py", line 40, in show_table_inspector 14:30:48 [ERR][ python]: tinspect.show_table(schema, table) 14:30:48 [ERR][ python]: File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE\modules\sqlide_tableman_ext.py", line 1138, in show_table 14:30:48 [ERR][ python]: tab.show_table(schema, table) 14:30:48 [ERR][ python]: File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE\modules\sqlide_tableman_ext.py", line 809, in show_table 14:30:48 [ERR][ python]: self.refresh() 14:30:48 [ERR][ python]: File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE\modules\sqlide_catalogman_ext.py", line 364, in refresh 14:30:48 [ERR][ python]: self.preload_data(self.get_query()) 14:30:48 [ERR][ python]: File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE\modules\sqlide_catalogman_ext.py", line 348, in preload_data 14:30:48 [ERR][ python]: node.set_int(i, rset.intFieldValueByName(field) or 0) 14:30:48 [ERR][ python]: File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE\mforms.py", line 2302, in set_int 14:30:48 [ERR][ python]: def set_int(self, *args): return _mforms.TreeNodeRef_set_int(self, *args) 14:30:48 [ERR][ python]: TypeError: in method 'TreeNodeRef_set_int', argument 3 of type 'int'
[4 May 2018 21:29]
Randy Taylor
I also get this - error calling Python module function SQLIDEUtils.showInspector when clicking the "I" on a 40 Gb range partitioned table - I also get - Unhandled exception: in method 'TreeNodeRef_set_int', argument 3 of type 'int' error when I attempt to open "Table Inspector" on the same table. The mysql version is 5.6.36 - mysql workbench version 6.3.10 - there are 930M rows currently in my table and I am seeing this on multiple databases with similar row counts and partitioning.
[29 May 2018 11:00]
Miguel Tadeu Mota
Posted by developer: This issue doesn't seem to be happening any more.
[7 Jun 2018 19:15]
Christine Cole
Posted by developer: Fixed as of the upcoming MySQL Workbench 8.0.12 release, and here's the changelog entry: An error message was returned when an attempt was made to inspect a partitioned table using either the information icon or the context menu. Thank you for the bug report.
[30 Mar 2020 6:36]
J B
Unfortunately, this was not resolved. I am receiving the exact same error in MySQL Worbench v8.0.19 build 15713499 CE (64 bits) community. FWIW, my use case is attempting to access a MySQL DB hosted on in Heroku (so, ultimately, AWS) by JawsDB. For some reason (still working on why) INSERT privileges have been revoked from my user. Not sure if that's relevant. I am able to click the (i) and get the expected result on other database instances, so it's not completely MySQL Workbench... the program is just mishandling some type of error state. Thanks! -jb